Axel Thimm wrote : > > All my servers running 7.0 and 7.3 are now using rpm 4.1.1 and yum > > 2.0.x, but I must admit that I got a weird problem on many of them > > after the upgrade which required "rm -f /usr/lib/rpm/Pubkeys" to get > > rpm working again... so I really wouldn't recommend mass-deploying that > > update in the current state of things (rpm bug with sigs needing to be > > fixed?). > > I haven't seen that, if you have a spare 7.3 machine, could you test > whether ATrpms' 4.2 rpms also mess up with the Pubkeys? Thanks! I haven't been able to track down the cause. On 6 identical servers of a cluster for instance (same hardware, same set of packages), some would exhibit the problem, while some others not... very strange. I do make an extensive use of gpg checking, previously from gnupg itself and "rpm -K" calls from autoupdate, then from within rpm itself through yum. Probably just a corner-case, but given the complexity of the upgrade, there may be many others, and I know for myself that I got hit really hard by this one, and don't think an average user could have solved it easily (I had to ask jbj for help...). But upgrading 7.x releases to rpm 4.0.5 is another story, and I would favor that one for a mass-upgrade. It seems much safer, as there are less semantics changes and less possible side-effects. No using yum 2.x though :-( Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 1 (Yarrow) - Linux kernel 2.4.22-1.2115.nptl Load : 1.01 0.77 0.82
