Transterrestrial Musings

Defend Free Speech!

Amazon Honor System Click Here to Pay

Site designed by

Powered by
Movable Type 4.0
Biting Commentary about Infinity, and Beyond!

« The Obamunist Party | Main | I'm Shocked, Shocked »

Fedora Upgrade Woes

OK, so I followed Pete's advice, and tried an upgrade from Core 7 to Core 8 via yum (yes, I know that Core 9 will be out shortly, but I figure it would probably be a mistake to go directly from 7 to 9, based on previous experience). Everything went fine until the end, when it failed with this message:

--> Processing Conflict: glibc-common conflicts glibc < 2.7
Error: No Package Matching glibc.i686

So, now what?

[Evening update]

OK, I ended up having to completely blow away glibc. Unsurprisingly, it broke my installation, with no obvious way to fix it. But it allowed me (finally) to do an ftp upgrade via a rescue CD. I'm now running FC8.


0 TrackBacks

Listed below are links to blogs that reference this entry: Fedora Upgrade Woes.

TrackBack URL for this entry:


Orion wrote:

Google is your friend. You have both old and new versions of the glibc libraries installed. Remove the old one and try again.

Sigivald wrote:

See, this sort of thing is why I simply never use packaging systems in linux, and don't upgrade things without a specific reason.

I've seen yum/rpm do it; I've seen apt/dpkg do it, and from what I hear from the lunatics that use gentoo, emerge can do it too.

Bad or ridiculous dependencies (want this console software? well, you gotta install a complete X system, because the jackhat that made the package for the distribution decided that the X frontend to that was so vital it should be baked in), terrible error-reporting... a mess.

But of course that does you no good - if Orion's comment wasn't helpful, I'd fire up an irc client, and go to #fedora on the Freenode network.

Pete Zaitcev wrote:

Post-factum, I suspect it was either an old glibc like Origon surmised, or a plain bug. The glibc instances (like kernel and a few other packages) are helpfuly (or "helpfuly") made non-conflicting on purpose: you can have several of them installed simultaneously, should your application mix require it. One can keep them unknowingly for years, until an upgrade stumbles.

Notice that glibc.i686 was a 32-bit version, and your installation was a 64-bit one. Some odd 32-bit package pinned an ancient glibc, I would guess. Maybe Sun's Java (which only comes in 32-bit version, if you want Web plugin). Removing that one package should not in any way hose the whole installation, because x86_64 uses 64-bit binaries in preference (unlike, for instance, PPC).

We will never know what it was exactly. I should be glad it ended well.

Habitat Hermit wrote:

Since nobody said it: glibc is the GNU C language library and just about everything important is in C and more often than not uses glibc. So it's almost always a crucial piece of Linux systems and messing it up usually makes everything pear-shaped sooner or later.

Not trying to sound like a know-it-all: I run Xubuntu for a reason ^_^;

David Bush wrote:

Debian and Ubuntu have aptitude, which for me does an excellent job of not only warning before installation if there is a dependency conflict, but provides a list of actions to scroll through ("keep foo in current state", OR "upgrade foo and bar" etc.) to resolve the issue. I don't know yet how well it handles version upgrades. I will find out next week.

Leave a comment

Note: The comment system is functional, but timing out when returning a response page. If you have submitted a comment, DON'T RESUBMIT IT IF/WHEN IT HANGS UP AND GIVES YOU A "500" PAGE. Simply click your browser "Back" button to the post page, and then refresh to see your comment.

About this Entry

This page contains a single entry by Rand Simberg published on April 11, 2008 7:05 AM.

The Obamunist Party was the previous entry in this blog.

I'm Shocked, Shocked is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Powered by Movable Type 4.1