~50% of all unhandled exceptions in production coming from python are from us
not having an entry for em64t as a possible package arch. Add it.
On second thoughts, dont add it, because it's not valid (its just x86_64)
throw an invalid arch fault or something.
+1 to throwing a reasonable fault.
Ok, so now if you attempt to sync up a package profile with a package that has
an odd arch, we return fault 45.
A quick n' dirty way to test this is to append a package with a spurious arch to
your package profile, like:
pkg_list.append(['foobar', '1', '1', '', 'em64t'])
at line 173 in /usr/share/rhn/up2date_client/rpmUtils.py
Then use rhnreg_ks and note the informative error message.