YUM ERASE ... wants to erase 1208 packages?

[MPvDdB]

Hello,

Using FC12 as a basis vor Amahi and started to use it more and more from that point. Started to Linux some time ago and am using Debian and its variants mostly. Som experience with Yum is scarce at the moment.

Ran into problems with old transactions not finished and did what was advised: <g> checking for problems. That solved it. Great. So I decided to look into Yum options a little more.

Found YUM Check and it produced:

Yum check
Loaded plugins: fastestmirror, presto, refresh-packagekit
glibc-2.11.2-1.i686 is a duplicate with glibc-2.11.1-4.i686
glibc-2.11.2-1.i686 has missing requires of config(glibc) = ('0', '2.11.2', '1')
glibc-2.11.2-1.i686 has missing requires of glibc-common = ('0', '2.11.2', '1')
Error: check all

OK looked for RESOLVEDEP of the glibc-2.11.1-4.i686 first and it did not find any.

So I told YUM to ERASE it. Shock and horror after a long wait and a looong list of packages being set to be erased it offered to erase 1208 packages!! Of course I denied politely first. There are lot of base-packages in that list, am I about to ruïn the complete current setup? Leaving me in an unbootable / unusable state?

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

[PabloTwo]

It's most likely that your rpmbdb is slightly corrupted. I would first do:

rpm -q glibc-common

to see what rpm has to say about whether it's installed or not (it most certainly must be, or your system wouldn't even run). You could also try

yum install glibc-common

just to see what happens. But I think what will fix the problem is most likely

rpm --rebuilddb

[MPvDdB]

Thanks

Yes it is installed but there is also a newer version (sse YUM CHECK results in the original post) and it having nothing that depends on it (or do I misunderstand the RESOLVEDEP results?) I thought it better to clean it out.

Your second command "just to see what happens" gives the following results:

-- quote output from: yum install glibc-common

Setting up Install Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: glibc-common = 2.11.1-4 for package: glibc-2.11.1-4.i686
---> Package glibc-common.i686 0:2.11.2-1 set to be updated
--> Processing Dependency: glibc = 2.11.2-1 for package: glibc-common-2.11.2-1.i686
--> Finished Dependency Resolution
Error: Package: glibc-common-2.11.2-1.i686 (updates)
Requires: glibc = 2.11.2-1
Installed: glibc-2.11.1-4.i686 (installed)
Available: glibc-2.11-2.i686 (fedora)
Available: glibc-2.11.2-1.i686 (updates)
Error: Package: glibc-2.11.1-4.i686 (installed)
Requires: glibc-common = 2.11.1-4
Removing: glibc-common-2.11.1-4.i686 (installed)
Available: glibc-common-2.11-2.i686 (fedora)
Installing: glibc-common-2.11.2-1.i686 (updates)
You could try using --skip-broken to work around the problem
glibc-2.11.2-1.i686 is a duplicate with glibc-2.11.1-4.i686
glibc-2.11.2-1.i686 has missing requires of config(glibc) = ('0', '2.11.2', '1')
glibc-2.11.2-1.i686 has missing requires of glibc-common = ('0', '2.11.2', '1')

-------- end quote output from: yum install glibc-common

I will try the rebuild now.

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

---------- Post added at 09:41 PM CDT ---------- Previous post was at 09:36 PM CDT ----------

Thanks again,

The rebuild of the RPM DB solved <g> one line of the previous YUM CHECK output.

It now reads:

yum check
Loaded plugins: fastestmirror, presto, refresh-packagekit
glibc-2.11.2-1.i686 is a duplicate with glibc-2.11.1-4.i686
glibc-2.11.2-1.i686 has missing requires of glibc-common = ('0', '2.11.2', '1')

the second line with "has missing requires" in the quote of the prior messages has now vanished.

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

[Hlingler]

glibc-2.11.2-1.i686 is a duplicate with glibc-2.11.1-4.i686

Please post results:
uname -r
su
yum repolist
package-cleanup --dupes
package-cleanup --problems

V

[sidebrnz]

Checking, resolvedep seems to show what dependencies a package has, not what depends on it. Thus, glibc-common needs no other packages installed, but many other packages need it. See the difference?

[PabloTwo]

Originally Posted by sidebrnz

.....Thus, glibc-common needs no other packages installed, but many other packages need it.

Not quite. Try: rpm -qR glibc-common which shows the --requires.
You'll see, among other things, it needs glibc of the same matching version.

[MPvDdB]

Thanks, I understand what you are trying to say.

I got the RESOLVEDEP from the list of acceptable (and explained) commands of YUM <enter>.

There it says: resolvedep Determine which package provides the given dependency

Well <g> that leaves a world of ambigue interpretations open, don't you think so?

Tried some variations of updating glibc but without much succes. Am doing a YUM UPDATE now first. A lot comes by, but I fear it will not solve this problem with GLIBC versions. Running into the same problem to make version 2 to get all its dependencies.

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

---------- Post added at 10:45 PM CDT ---------- Previous post was at 10:41 PM CDT ----------

Originally Posted by PabloTwo

Not quite. Try: rpm -qR glibc-common which shows the --requires.

You'll see, among other things, it needs glibc of the same matching version.

I did it gave the following output:

# rpm -qR glibc-common
/bin/bash
/bin/sh
/usr/sbin/build-locale-archive
/usr/sbin/tzdata-update
config(glibc-common) = 2.11.1-4
glibc = 2.11.1-4
libc.so.6
libc.so.6(GLIBC_2.0)
libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.1.1)
libc.so.6(GLIBC_2.10)
libc.so.6(GLIBC_2.2)
libc.so.6(GLIBC_2.3)
libdl.so.2
libdl.so.2(GLIBC_2.0)
libdl.so.2(GLIBC_2.1)
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
tzdata >= 2003a
rpmlib(PayloadIsXz) <= 5.2-1

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

[PabloTwo]

After your update, you should have:

glibc-2.11.2-1.i686
glibc-common-2.11.2-1.i686

But then, I think you already had those both installed. If so, there should not be installed glibc-2.11.1-4.i686 which was the previous version and which should have been erased from your system when the newer version of glibc was installed during the "cleanup" process of yum when that update occurred.

If, after the current updates finish, you still have two versions of glibc, you may need to delete the older one using the rpm command. After the updates, show the result of:

rpm -qa | grep glibc

[MPvDdB]

Originally Posted by Hlingler

Please post results:

uname -r
su
yum repolist
package-cleanup --dupes
package-cleanup --problems

V

OK here it goes:


# uname -r
2.6.31.5-127.fc12.i686.PAE

# su

# yum repolist
Loaded plugins: fastestmirror, presto, refresh-packagekit
Loading mirror speeds from cached hostfile
* fedora: ftp.nluug.nl
* rpmfusion-free: download1.rpmfusion.org
* rpmfusion-free-updates: download1.rpmfusion.org
* rpmfusion-nonfree: download1.rpmfusion.org
* rpmfusion-nonfree-updates: download1.rpmfusion.org
* updates: ftp.nluug.nl
repo id repo name status
adobe-linux-i386 Adobe Systems Incorporated 18
amahi Amahi repository for Fedora 12 143
fedora Fedora 12 - i386 15366
rpmfusion-free RPM Fusion for Fedora 12 - Free 383
rpmfusion-free-updates RPM Fusion for Fedora 12 - Free - Updates 1281
rpmfusion-nonfree RPM Fusion for Fedora 12 - Nonfree 124
rpmfusion-nonfree-updates RPM Fusion for Fedora 12 - Nonfree - Updates 502
updates Fedora 12 - i386 - Updates 6952
repolist: 24769

# package-cleanup --dupes
Loaded plugins: fastestmirror, presto, refresh-packagekit
glibc-2.11.2-1.i686
glibc-2.11.1-4.i686

# package-cleanup --problems
Loaded plugins: fastestmirror, presto, refresh-packagekit
Package glibc-2.11.2-1.i686 requires glibc-common = ('0', '2.11.2', '1')


Hooray I thought, we have gotten rid of the old version but YUM CHECK showed it still existed.

# yum check
Loaded plugins: fastestmirror, presto, refresh-packagekit
glibc-2.11.2-1.i686 is a duplicate with glibc-2.11.1-4.i686
glibc-2.11.2-1.i686 has missing requires of glibc-common = ('0', '2.11.2', '1')
Error: check all



I did not reboot of course because that is a Windows trick. So it may still be in use in existing sessions, preventing it from being removed at this time?

I am not particularly keen on restarting now, becuase the new version has missing dependencies I think, so it being a key-component to make the FC12 run at all ....

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

---------- Post added 2010-07-26 at 12:14 AM CDT ---------- Previous post was 2010-07-25 at 11:24 PM CDT ----------

Originally Posted by PabloTwo

After your update, you should have:

glibc-2.11.2-1.i686
glibc-common-2.11.2-1.i686

But then, I think you already had those both installed. If so, there should not be installed glibc-2.11.1-4.i686 which was the previous version and which should have been erased from your system when the newer version of glibc was installed during the "cleanup" process of yum when that update occurred.
rpm -qa | grep glibc

Is it thinkable that the old version was not removed because the new versions had dependencies missing, making it unusable perhaps? So the system prevented becoming totally unusable because of a not working GLIBC version only, by keeping the old one around as a fallback?

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

---------- Post added at 12:16 AM CDT ---------- Previous post was at 12:14 AM CDT ----------

Output of: rpm -qa | grep glibc

glibc-common-2.11.1-4.i686
glibc-2.11.2-1.i686
glibc-2.11.1-4.i686

So the common part version 2-1 is still not (fully) available I think.

[PabloTwo]

Originally Posted by MPvDdB

Output of: rpm -qa | grep glibc

glibc-common-2.11.1-4.i686
glibc-2.11.2-1.i686
glibc-2.11.1-4.i686

So the common part version 2-1 is still not (fully) available I think.

Well, the glibc-common-2.11.2-1.i686 is available ( I have it on my F12 i686 install ). I don't know what happened that you updated to glibc-2.11.2-1.i686 without also updating to glibc-common-2.11.2-1.i686 since each is a dependency of the other.

Since these are mission critical packages, I'm not sure which is the best and safest way to get glibc-common-2.11.2.-1.i686 installed and then the 2.11.1-4.i686 versions of glibc and glibc-common removed. You already tried 'yum install glibc-common', so how about trying:

yum update glibc-common

But then, if you just did a 'yum update' then that should have already worked, which it apparently didn't. Unless someone can think of a better solution, I would do:

wget -c http://mirror.pnl.gov/fedora/linux/updates/12/i386/glibc-common-2.11.2-1.i686.rpm
su
rpm -Uvh --replacepkgs --replacefiles glibc-common-2.11.2-1.i686.rpm
reboot

Then, when you're rebooted, do,

su
package-cleanup --cleandupes

[Hlingler]

# package-cleanup --dupes
Loaded plugins: fastestmirror, presto, refresh-packagekit
glibc-2.11.2-1.i686
glibc-2.11.1-4.i686

# package-cleanup --problems
Loaded plugins: fastestmirror, presto, refresh-packagekit
Package glibc-2.11.2-1.i686 requires glibc-common = ('0', '2.11.2', '1')

This is a whole lot of far-tooning around, when it's obvious that there are (illegal) duplicate packages and resultant dependency problems. You now have a circular dilemma: can't get new glibc-common because it duplicates installed glibc-common, but can't remove old (installed) glibc-common because it would remove 1208 packages (and possibly cripple the system if forcibly removed without a replacement in-place). At this point, your best option is to do as Paul says: manually download and forcibly update to the newer glibc-common, then purge older glibc (again forcibly if necessary).

You must have had a failed update at some time in the past (aborted/crashed) that caused the duplicates problem.

V

[MPvDdB]

Thanks,

The result from the third line rpm-command:

# rpm -Uvh --replacepkgs --replacefiles glibc-common-2.11.2-1.i686.rpm

error: Failed dependencies:
glibc-common = 2.11.1-4 is needed by (ïnstalled) glibc-2.11.1-4.i686

Is this to be an expected result? Should I reboot anyway?

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

---------- Post added at 03:35 AM CDT ---------- Previous post was at 03:22 AM CDT ----------

Thanks,

Don know what far-tooning means, but the duplicates where obvious from the beginning as you say (even to me). So that is why I tried to clean them with the shock and horror experience of the 1208 (also essential) packages in the list about to removed. I have a little bit of experience and feared the cripling of the system if I let it go ahead of course (someone else might have thouhgt: "the system is knowing what it does, it will not remove essential packages, so I hit y as an answer". I know one is working with root-credentials in such cases, but anyway I would expect a core-set of mandatory system-packages to be protected better to prevent the system becoming crippled.

kindest regards
from Leeuwarden, NL
Peter van Dobben de Bruijn

[PabloTwo]

This is getting sticker and stickier. OK, before forcing the issue here, insure that glibc-2.11.2.-1.i686 is actually installed by using:

rpm -V glibc-2.11.2-1.i686

Here's what I get on my system with that command:

BASH:~/-> rpm -V glibc-2.11.2-1.i686
..?......    /usr/sbin/glibc_post_upgrade.i686

If that reports no errors except for the one above which would be normal in this case, then force the install of glibc-common-2.11.2.-1.i686 with:

rpm -Uvh --replacepkgs --replacefiles --nodeps glibc-common-2.11.2-1.i686.rpm

Keep in mind that you can't actually have two complete separate installed versions of either glibc or glibc-common, as they both would contain files of the same name and location. I am hoping that 'package-cleanup --cleandupes' is actually smart enough to know this and thus wouldn't blow away either or both of glibc and glibc-common, but would only remove files specific to the earlier version(s) and adjust the package meta-data to indicate it's removal..

Take this one step at a time. So just do the forced install of glibc-common-2.11.2-1 first and see what's what after that.

It might be prudent to have any files that are really important to you backed up at this time, just in case.

[MPvDdB]

Rply to the rpm -V glib

is as follows:

Unsatisfied dependencies for glibc-2.11.2-1.i686:
glibc-common = 2.11.2-1 is needed by glibc-2.11.2-1.i686

I fear <g> that does not qualify as "without errors"?

[PabloTwo]

I didn't expect an answer like that but not all that surprizing. Here is another tact, which should better insure system integrity.

wget -c http://mirror.pnl.gov/fedora/linux/updates/12/i386/glibc-2.11.2-1.i686.rpm
su
rpm -Uvh --replacepkgs --replacefiles --nodeps glibc-common-2.11.2-1.i686.rpm glibc-2.11.2-1.i686.rpm

That would force the install/reinstall of both updated packages together. Then we'll deal with the old version 'dupes' afterwards.