Multiple times I've tried an ftp updgrade (through the
infomagic mirror) and each time the upgrade has failed while
checking the rpm dependency database. I get a python
exception error (output looks like it's checking files
against the database) and then I'm afforded the opportunity
to reboot my computer or go into debug mode... unfortunately
I know nothing about python and can't help there.
This is repeatable... I can't upgrade redhat-6.1 at all. I'm
upgrading from a 6.0 box, which had been upgraded from 5.x,
and previous from that 4.x... so this box has seen numerous
upgrades over the years. Understand, this is an "Upgrade",
not a fresh install.
Looking through some of the other bugs listed I wanted point out that
I only have three ext2 filesystems and a swap filesystem on this disk,
and am not using RAID. Also: No NTFS filesystems.
This is the same as my submitted bug #5545.. And I hope it's resolved
I am getting the same error. I do have three partitions, the last of
which is a Win98 FAT32 partition. I repeatedly get this error after
about 55Mb of downloads - the Python installer hangs for a while and
then I get the error dialog.
My system is:
Intel Celeron 400MHz
256 MB RAM
13GB Seagate HD with Swap, Linux and Win98 partitions
NE2000 Compatible Ethernet
I was doing the RH6.0 -> 6.1 ftp upgrade
I had the same problem, but was able to work around it.
The rpm database of the 6.0 had some conficts.
I rebuild the datebase and removed a conflicting package (an old kde
version). (I don;t know an easy way to see what the conflicts are...)
After that the upgrade worked.
------- Additional Comments From 11/05/99 23:56 -------
A possible fix for this has been posted to linux.redhat.install and
comp.lang.python by pacman.com (Alan Curry) who claims
it's a behaviour change in wu-ftpd 2.6 interacting with a bug in
There are a couple of possible problems going on here. One is that the server
name and the path to the source files for FTP installs must be specified in a
pretty specific format. You must provide the FQDN or IP address for the server
and you must *NOT* put a trailing slash on the end of the path to the source
files. Not doing the above will result in the error message quoted in 5545.
The other thing that could be happening is this problem that the person above
posted the fix to.
Am closing out this bug, seeing as there has been no activity for a few months.