Description of problem: When upgrading from RHEL4.6 to RHEL4.7 unpacking of pvm package failed. This causes the entire upgrade (up2date -fu) to exit with code of 1. Subsequent run of up2date -fu shows other packages not upgraded. Version-Release number of selected component (if applicable): pvm-3.4.5-12.el4 How reproducible: always Steps to Reproduce: 1. Install RHEL4.6 with pvm-3.4.4-21 (@everything) 2. Upgrade to RHEL4.7 via rhn.webqa (with up2date -fu) 3. Actual results: Unpack error when installing pvm package. As a result the systems ends up with missing pvm packages (old one removed and new one not installed due to error). Actual error message: 334:pvm ########################################### [100%] error: unpacking of archive failed on file /usr/share/pvm3/bin/LINUXIA64: cpio: rename Expected results: pvm is upgraded to newer version Additional info: seeing this on ia64 and x86_64, not on ppc, s390*
Steps to Reproduce: 1. Install RHEL4.6 with pvm-3.4.4-21 (@everything) 2. Remove openmpi* and lam* packages (see bug #443795) 2. Upgrade to RHEL4.7 via rhn.webqa (with up2date -fu)
OK, I can see why this is happening (and it makes me wonder how the rhel3 upgrade to pvm ever got through QA, it would have the same problem...but then again this whole process has merely proven that the rhel3 pvm update was partially complete at best). I'm going to investigate an alternative fix for pvmgetarch...will update this bug shortly.
OK, I've created a patch to pvmgetarch that reverts the arch naming back to what it was prior to this update, and I've eliminated the symlinks in the package entirely. The problem was that the symlinks couldn't be laid down during the upgrade because valid directories with the same name already existed from the package being upgraded, which happens because we install the new package *before* we remove the old files from the old package, so those directories where in the way. With my new patch, it should go back to working like it did prior to the update and use specific arch directories in all cases.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0744.html