From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
While setting up up2date to check packages from both the official
RHEL3 repo, and the jpackage repo, an attempt to up2date bombs like so:
[root@gatekeeper root]# up2date -u
Fetching Obsoletes list for channel: rhel-i386-es-3...
Fetching Obsoletes list for channel: rhel-i386-es-3-extras...
Fetching Obsoletes list for channel: jpackage15-rhes-3...
Fetching Obsoletes list for channel: jpackage15-generic...
Fetching rpm headers...
Name Version Rel
bcel 5.1 1jpp
jakarta-commons-collections 2.1.1 1jpp
jakarta-commons-dbcp 1.2.1 1jpp
jakarta-commons-logging 1.0.4 1jpp
jakarta-commons-pool 1.2 1jpp
mx4j 1.1.1 6
tomcat5 5.0.27 2jpp
tomcat5-admin-webapps 5.0.27 2jpp
xalan-j2 2.6.0 1jpp
xerces-j2 2.6.2 3jpp
xml-commons-resolver 1.1 2jpp
Testing package set / solving RPM inter-dependencies...
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1174, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 772, in main
File "/usr/sbin/up2date", line 1066, in batchRun
File "up2dateBatch.py", line 74, in run
File "up2dateBatch.py", line 159, in __dryRun
File "up2date.py", line 398, in dryRun
File "depSolver.py", line 728, in solvedep
File "depSolver.py", line 695, in process_deps
File "depSolver.py", line 508, in __dependencies
ValueError: list.remove(x): x not in list
Sometimes the above bombout happens, sometimes the dependancy solver
will hang for a number of hours (until killed manually).
I am not sure whether the mx4j package has something to do with this -
it is apparently incompatible with the jpackage stuff, and being more
recent than the jpackage stuff up2date is continually insisting on
trying to install it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.