From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
I'm trying to upgrade a few systems from rhel3 to rhel4 using the
'--upgrade-to-release' option to up2date, but I keep running into
problems with dependencies. The command given is
up2date --upgrade-to-release=4WS -k /mnt/test -uf
and the result I get is
Unresolvable chain of dependencies:
gtkam-gimp 0.1.7-6 requires libgimp-1.2.so.0
gtkam-gimp 0.1.7-6 requires libgimpui-1.2.so.0
redhat-config-nfs 1.0.13-6 requires /usr/bin/python2.2
udev-039-10.8.EL4 requires kernel < 0:2.6
The complete output is attached. The first three I can work around,
but it's an error nonetheless, and the last one is more complex. I
can't find much documentation for the 'upgrade-to-release' option. Is
it even supposed to work when upgrading from one major release to
another, and is this method of upgrading at all recommended?
We have 1000+ rhel boxes, so an easy, well-documented and automated
method of upgrading would be neat. Kickstart upgrade is certainly
cool, but a simple up2date command would be far better :)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run 'up2date --upgrade-to-release=4WS' on an rhel3 system
Actual Results: The error message described above.
Expected Results: The system is upgraded and just need a reboot to be
a fully working rhel4 system.
Created attachment 111157 [details]
Output from 'up2date --upgrade-to-release=4WS'
--upgrade-to-release will be removed in future versions. It
is a deprecated feature.
The supported upgrade path is via anaconda (aka, the
installer). RHEL3 to RHEL$ upgrades require additional
changes other than simply upgrading all the packages.
Ok, I thought that might be the case. Thanks for clearing it up, and
for the quick response. Have a nice weekend :)