redhat 7.0 upgrade woes
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Gerry Creager n5jxs gerry at cs.tamu.eduThu Mar 8 05:40:37 PST 2001
- Previous message: redhat 7.0 upgrade woes
- Next message: Power-managment of slave nodes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Josip Loncaric wrote: > > One problem I've seen in upgrading 6.2->6.2+updates->7.0->7.0+updates is > that Red Hat messed up version numbering on about a dozen packages, > which then did not get updated to 7.0 versions. The most obvious > problem was gnorpm. Since the updated 6.2 version appeared newer than > the updated 7.0 version, gnorpm did not get replaced (but the underlying > libc did) so afterwards gnorpm refused to work (complaining about a > missing shared library). > > The fix for this is to install the correct gnorpm (and other misnumbered > packages) using the rpm -Uvh --force ... command, at least until Red Hat > addresses these version numbering problems. Hopefully, you had not already installed the RPM updates! If youhad, or at least, since I had, even --force didn't help! -- Gerry Creager -- gerry at cs.tamu.edu Network Engineering |Research focusing on Academy for Advanced Telecommunications |Satellite Geodesy and and Learning Technologies |Geodetic Control Texas A&M University 979.458.4020 (Phone) -- 979.847.8578 (Fax)
- Previous message: redhat 7.0 upgrade woes
- Next message: Power-managment of slave nodes
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
