Description of problem: If you have %_repackage_all_erasures set to 1, and you have imported one gpg key into the database, ever importation of a gpg key thereafter will generate a repackaged package with a name like: /var/TKLC/backout/pkg/gpg-pubkey-5072e1f5-3e3ea30c.(none).rpm Rollbacks complain with a complaint of: error: failed to stat /view/crosson_dev_bcr_13681/vobs/software/platform: Stale NFS file handle but they do seem to work. Version-Release number of selected component (if applicable): 4.2-0.69 How reproducible: every time. Steps to Reproduce: 1. Import a key. 2. Import another key. 3. Look in the %_repackage_dir. Actual results: You should find a repackaged package with the name gpg-pubkey. Expected results: No repackage of public keys. Additional info:
Yes, gpg-pubkey packages can/will cause problems, because I forgot to add a "noarch" tag. Uncommenting #ifdef NOTYET (void) rpmdbSetIteratorRE(mi, RPMTAG_NAME, RPMMIRE_DEFAULT, '!gpg-pubkey'); #endif in IDTXload() lib/rpminstall.c is probably needed as well, the other place to fix is in lib/transaction.c where erasures are repackaged, skipping packages named "gpg-pubkey". All pending, awaiting a coherent repackage policy.
James is this still valid against rpm 4.4.x branch?
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. f you are currently still running Red Hat Linux 7.3 or 9, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Closing as CANTFIX.