Problem with nonstandard architecture names

[Hartman, Peter]

Hello,

I'm having trouble building a kit using an rpm with a nonstandard
architecture name. My kit uses several RPMs, such as:
"rpm-a.x86_64.rpm", "rpm-b.i386.rpm", and "rpm-c.em64t.rpm". The problem
stems from trying to add rpm-c.em64t.rpm to the kit.

The first problem I run into is that when buildkit attempts to build the
kit with an em64t rpm, it does not create the proper symlink for the rpm
to the packages directory, and thus it does not get added to the kit.
This I've gotten around by changing the rpm package name to
rpm-c.noarch.rpm. Not exactly the proper way to fix this, but it works.

The next problem I run into is during installation. I've examined the
installation of the kit as it is added through
kitops/repoman/ngedit/cfmsync, and I find that during the cfmsync step,
when it calls yum to actually install the rpm, yum cannot resolve the
rpm-c.noarch.rpm dependency.

I've requested the owner of the rpm-c.em64t.rpm to build their packages
using x86_64, but until I get a new package, can anyone think of a way
to get around this?

Peter Hartman
***@intel.com
Ph:[phone]
Fx:[phone]
CH:FX1-149