Many Mandriva 2007 users have probably already experienced this notorious bug in the distro. More about it here:
V3 binary RPM's are installed in some cases incorrectly as source RPM's, causing a severe database corruption and crippling the whole system.
This is a very common problem I've seen on at least 10 computers running Mandriva 2007. I actually find it odd no-one has started thread about it here yet. I am trying to stick only with the official sources now (+ contrib & PLF) and the new version of rpm in the testing-branch (http://club.mandriva.com/xwiki/bin/v.../MirrorFinder2
) fixes the actual bug from the package manager (HIGHLY recommended BEFORE you run into this problem!). However, I have questions:
1) How can I actually fix all these corrupted systems? Recovering /var/lib/rpm from an old backup (just after the system installation) does not help. "rm -f /var/lib/rpm/__* && rpm --rebuilddb
" does not help. I can't possibly trace every single RPM packet that has been installed to them. And would removing those old V3 packets even fix it?
2) HOW do I actually identify incompatible RPM packets (V3)? "file packet.rpm
" shows "V3" or "sticky V3" even for the official RPM packets tagged with "mdv2007" on the Mandriva installation DVD. How to identify too old and incompatible RPM files? Mandriva 2007 only supports V4 RPM format.
While I find Mandriva 2007 to be very stable and relatively bug-free, this package management bug is even more serious than the one SuSE 10.1 had. It cripples the whole system and I have no idea how to fix those systems without a full re-install.