_Still_ continuing the saga of the text mode (not expert) upgrade of
a Sony Vaio PCG-SR1K from RH7.0+bits+Ximian 1.4...
Reached "Checking package dependencies" without any opportunity
to customise the package selection. It had a think and then told
I got half a dozen packages which anaconda couldn't suggest
associated dependencies for. They were all from Ximian Gnome
1.4: ammonite, gnome-games, gnucash(I believe there was a guile
issue with these two), and some others.
It gave me three options: install suggested dependencies, ignore
suggested dependencies, or don't upgrade the packages with dodgy
Did you know that you can pick the first, and it will cheerfully
go off and try to do the upgrade, regardless of the dependency
I wass dropped straight into the upgrade from this with no
opportunity to add or remove anything.
On completing the upgrade, I had a quick look in /tmp/upgrade.log
and tons and tons of Gnome stuff had not been upgrades:
rpm -qa | grep ximian showed me dozens and dozens of Ximian rpms.
I don't know whether they were epoched, or whether this was an
anaconda error, or what.
In addition, Ximian has a few extra packages such as doorman ("welcome
to Gnome, would you like to register?") which may cause trouble if left
lying about. Not sure what to do about those.
I have half a mind to simply refuse to upgrade a machine with Ximian GNOME
No matter who has what kind of mind (or what portions :-) we need to have some
resolution for this. Ximian with Red Hat is just too appealing to the masses so
we HAVE to have an answer.
This defect considered SHOULD-FIX for Fairfax gold-release.
We have to address this - either we technically cannot support upgrading all the
various incarnations of the Ximian GNOME packages, or else we come up with a way
to gut it through the upgrade and then tell them they are on their own to get
GNOME working again.
I've added a large warning dialog when we find ximian or helixcode or eazel rpms
on the system.