Red Hat Bugzilla – Bug 27158
up2date fails dependency check when -a option used
Last modified: 2015-01-07 18:43:25 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.18-mosix i686; en-US; 0.7) Gecko/20010111 up2date gives error message 'There was a fatal RPM error. The message was: Don't know how to handle dependency sense "1"' when option -a is used. Reproducible: Always Steps to Reproduce: 1. Run the command "up2date --nosig -ua" Actual Results: [root@man /root]# up2date --nosig -ua Retrieving list of all available packages... Removing installed packages from list of updates... 100.0% Removing packages marked to skip from list... 100.0% Getting headers for available packages... 100.0% Removing packages with files marked to skip from list... 100.0% Getting headers for skipped packages... 100.0% Testing package set / solving RPM inter-dependencies... There was a fatal RPM error. The message was: Don't know how to handle dependency sense "1" If the -a option is omitted, the command completes as expected. All software on the system has been updated (i.e., its current). The command: "up2date --nosig -la" returns a very long list of packages that are evidently not currently installed on my system. If the exact list is important, please contact me and I will provide it.
Assigned QA to jturner
I was trying to use up2date with the "Display all packages available, not only those installed on the system" flag turned on by up2date-config. up2date (GUI) just sat there for ever until I killed it. I then tried to do a up2date --nosig --list -a and go the following: # up2date --nosig --list -a Retrieving list of all available packages... Removing installed packages from list of updates... 100.0% Removing packages marked to skip from list... 100.0% Getting headers for available packages... 100.0% Removing packages with files marked to skip from list... There was a fatal RPM error. The message was: error reading from database # This is under RedHat 7.0 / i386 (up2date 2.1.7)
failed because of a conflict. *** This bug has been marked as a duplicate of 28369 ***