Description of problem: Yesterday I have installed RHEL3-U9 due some testing. Today I have tried to install the "gaim" package, i.e perform: up2date -i gaim with package "pidgin" already installed (didn't know before, that these two exclude them each other :o(. So 1, # rpm -q pidgin pidgin-1.5.1-1.el3 2, up2date -i gaim -> Fetching Obsoletes list for channel: rhel-i386-as-3... Fetching Obsoletes list for channel: rhn-tools-rhel-3-as-i386... Fetching rpm headers... ######################################## Name Version Rel ---------------------------------------------------------- gaim 1.5.0 11.el3 i386 Testing package set / solving RPM inter-dependencies... ######################################## There was a fatal RPM error. The message was: Failed running rpm transaction 3, From up2date log: . . . [Wed Oct 17 16:00:02 2007] up2date updating login info [Wed Oct 17 16:00:02 2007] up2date logging into up2date server [Wed Oct 17 16:00:02 2007] up2date successfully retrieved authentication token from up2date server [Wed Oct 17 16:00:02 2007] up2date availablePackageList from network [Wed Oct 17 16:00:06 2007] up2date allAvailablePackageList from network [Wed Oct 17 16:00:10 2007] up2date installing packages: [] [Wed Oct 17 16:00:10 2007] up2date Failed running rpm transaction - %pre %pro failure ?. Version-Release number of selected component (if applicable): up2date-4.5.5-8.el3 How reproducible: Always Steps to Reproduce: 1. Just reproduce the steps above 2. 3. Actual results: Failed running rpm transaction Expected results: up2date should complain, that gaim can't be installed while the "pidgin" packages (which provides gaim) is installed. The "up2date" process should end with no error. Additional info:
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.