Is there any particular reason that the rpm and popt version on the distro image is from freshrpms.net? I've noticed a couple of incidents of broken-ness because of this:

[root@li2-112 tmp]# rpm -ivh rpm-python-4.1-1.06.i386.rpm
warning: rpm-python-4.1-1.06.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e
error: Failed dependencies:
rpm = 4.1 is needed by rpm-python-4.1-1.06

To be a little more clear:

I do realize that RPM 4.1 is broken an unmaintainable, but it is part of Red Hat Linux 8.

Unfortunately, I did run into quite a bit of grief yesterday with some software that *exptected* exactly version 4.1. While it was something I was easily able to work around, it would have been nice to have it documented somewhere that this was not *stock*.

Btw, once you run RPM 4.1.1 on your RPM database, it seems to be irreversibly changed so that RPM 4.1 will no longer work correctly. Just something to keep in mind.

The process I used to generate that distro was to apt-get dist-upgrade from a 7.X image (and then a few other modifications to follow through)...

Here's a possibly dumb question: FreshRPMs != RedHat Mirror?

Could this have been avoided by modifying which sources APT uses (/etc/apt/sources.list) to point to a genuine RedHat repository instead of FreshRPMs before performing the upgrade to 8.0?

-Chris

The freshrpms repository has rebuilds on some packages with higher package numbers, so they would take precedence over the RH shipped ones.

I belive that is correct - if you set your sources to be only a RH repository, it would then contain only the RH packages - however, I'm not too familiar with apt.