glibc update refusing to proceed. File ownership problem

I am Gianluca · 2012-07-15 10:57:02

I have some problems after trying to upgrade glibc.
I've previusly update my system with the 'pacman -Syu --ignore glibc' command.

$ pacman -Su
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (1): glibc-2.16.0-2

Total Installed Size:   33.94 MiB
Net Upgrade Size:       0.00 MiB

Proceed with installation? [Y/n] y
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded.

So, following the wiki there are no packages which own files in /lib, except from glibc.

$ find /lib -exec pacman -Qo -- {} +
error: cannot determine ownership of directory '/lib'
/lib/libnss_dns-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libm-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libnss_compat.so.2 is owned by glibc 2.16.0-1
/lib/ld-linux.so.2 is owned by glibc 2.16.0-1
/lib/libBrokenLocale-2.16.so is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/libnss_nis-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libutil-2.16.so is owned by glibc 2.16.0-1
/lib/libresolv-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/libthread_db-1.0.so is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/libdl-2.16.so is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libSegFault.so is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/ld-2.16.so is owned by glibc 2.16.0-1
/lib/libutil.so.1 is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libresolv.so.2 is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
error: cannot determine ownership of directory '/lib/modules'
error: cannot determine ownership of directory '/lib/modules/3.3.7-1-ARCH'
error: cannot determine ownership of directory '/lib/modules/3.3.7-1-ARCH/misc'
error: No package owns /lib/modules/3.3.7-1-ARCH/misc/vmblock.ko
error: No package owns /lib/modules/3.3.7-1-ARCH/misc/vsock.ko
error: No package owns /lib/modules/3.3.7-1-ARCH/misc/vmci.ko
error: No package owns /lib/modules/3.3.7-1-ARCH/misc/vmmon.ko
error: No package owns /lib/modules/3.3.7-1-ARCH/misc/vmnet.ko
error: cannot determine ownership of directory '/lib/modules/3.1.9-2-ARCH'
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.usbmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.isapnpmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ccwmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.seriomap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.inputmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ofmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.pcimap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ieee1394map
error: cannot determine ownership of directory '/lib/modules/3.3.6-1-ARCH'
error: cannot determine ownership of directory '/lib/modules/3.3.6-1-ARCH/misc'
error: No package owns /lib/modules/3.3.6-1-ARCH/misc/vmblock.ko
error: No package owns /lib/modules/3.3.6-1-ARCH/misc/vsock.ko
error: No package owns /lib/modules/3.3.6-1-ARCH/misc/vmci.ko
error: No package owns /lib/modules/3.3.6-1-ARCH/misc/vmmon.ko
error: No package owns /lib/modules/3.3.6-1-ARCH/misc/vmnet.ko
error: cannot determine ownership of directory '/lib/modules/3.3.5-1-ARCH'
error: cannot determine ownership of directory '/lib/modules/3.3.5-1-ARCH/misc'
error: No package owns /lib/modules/3.3.5-1-ARCH/misc/vmblock.ko
error: No package owns /lib/modules/3.3.5-1-ARCH/misc/vsock.ko
error: No package owns /lib/modules/3.3.5-1-ARCH/misc/vmci.ko
error: No package owns /lib/modules/3.3.5-1-ARCH/misc/vmmon.ko
error: No package owns /lib/modules/3.3.5-1-ARCH/misc/vmnet.ko
error: cannot determine ownership of directory '/lib/modules/3.4.2-3-ck'
error: cannot determine ownership of directory '/lib/modules/3.4.2-3-ck/misc'
error: No package owns /lib/modules/3.4.2-3-ck/misc/vsock.ko
error: No package owns /lib/modules/3.4.2-3-ck/misc/vmci.ko
error: No package owns /lib/modules/3.4.2-3-ck/misc/vmmon.ko
error: cannot determine ownership of directory '/lib/modules/2.6.39-ARCH'
error: cannot determine ownership of directory '/lib/modules/2.6.39-ARCH/updates'
error: No package owns /lib/modules/2.6.39-ARCH/updates/acerhdf.ko
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/libnss_db.so.2 is owned by glibc 2.16.0-1

Before deleting or moving something I've done also the next step.

$ grep '^lib/' /var/lib/pacman/local/*/files
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-linux.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil.so.1

At this point I've deleted the /lib/modules/ directory and moved all the files from /lib/ to /usr/lib/.
The problem is that now I cannot prosegue with the next step. What did I wrong?

$ sudo pacman -Su
bash: /usr/bin/sudo: No such file or directory

UPDATE: I cannot open Firefox, Chromium, Terminal, File Manager, etc. Seems that everything is broken.

Failed to execute command "exo-open --launch FileManager %u". Failed to execute child process "exo-open" (No such file or directory)

The problem is that I don't have a back-up of the /lib/modules/ directory, because for don't lost time I open Thunar as root and delete it manually.

Last edited by I am Gianluca (2012-07-15 11:18:26)

dikos · 2012-07-15 11:17:01

Zamboniman wrote:

Well, reading this thread has been interesting. People seem to be randomly moving things, deleting things, forcing things, and generally messing up their systems.
I can understand why. This has been one of the more frustrating upgrades in my history with Arch. However, take a deep breath, calm down, and take it a step at a time.
Here's Zamboniman's quick guide to upgrading glibc:
There you go. I hope this helps a few of you.

Thanks ! that totaly solved my problem with glibc upgrade, all works like good clock !

Miles28 · 2012-07-15 11:32:58

Thanks so much Zamboniman.

progandy · 2012-07-15 11:35:55

I am Gianluca wrote:

At this point I've deleted the /lib/modules/ directory and moved all the files from /lib/ to /usr/lib/.
The problem is that now I cannot prosegue with the next step. What did I wrong?

You should not have moved the files to usr/lib. Only deleting /lib/modules should have been enough.

Last edited by progandy (2012-07-15 11:38:05)

I am Gianluca · 2012-07-15 12:56:42

progandy wrote:

I am Gianluca wrote:
At this point I've deleted the /lib/modules/ directory and moved all the files from /lib/ to /usr/lib/.
The problem is that now I cannot prosegue with the next step. What did I wrong?
You should not have moved the files to usr/lib. Only deleting /lib/modules should have been enough.

Is there a way to recognise which files I moved? They were about 15.

progandy · 2012-07-15 13:11:04

I am Gianluca wrote:

Is there a way to recognise which files I moved? They were about 15.

You have posted your find-output for /lib. So move everything back that is owned by glibc.
To get a working system again, a symlink from /lib/ld-linux.so.2 to /usr/lib/ld-2.16.so is probably enough, but then you will have errors when upgrading glibc. If you force the update then, it could work, but I don't know if that is a good idea.

Last edited by progandy (2012-07-15 13:11:51)

einhard · 2012-07-15 13:15:58

After glibc update /lib is owned by apache-ant . I don't get it, why? This package doesn't have any files in /lib or /usr/lib. If I uninstall it, the ownership comes back to glibc.

killer1804 · 2012-07-15 13:37:18

I have my own way of solving the problem:
try to:
1. pacman -Syu --ignore glbc
2. cp /lib/* /usr/lib/ (or copy with mc, if you have a directory with files in )
3. pacman -S --force glibc

what do you think about it?

cfr · 2012-07-15 13:43:01

killer1804 wrote:

I have my own way of solving the problem:
try to:
1. pacman -Syu --ignore glbc
2. cp /lib/* /usr/lib/ (or copy with mc, if you have a directory with files in )
3. pacman -S --force glibc
what do you think about it?

Why would you do this given that the wiki explicitly says NOT to force the upgrade of glibc?

Even if it works now, it will not be as clean and I'm guessing could give you issues later because you will have moved a bunch of stuff from /lib/ to /usr/lib/ rather than taking care of it properly. For example, you will have moved /lib/modules/, files left over from packages you no longer have installed, stuff from AUR which has not been properly updated...

I am Gianluca · 2012-07-15 13:50:07

progandy wrote:

I am Gianluca wrote:
Is there a way to recognise which files I moved? They were about 15.
You have posted your find-output for /lib. So move everything back that is owned by glibc.
To get a working system again, a symlink from /lib/ld-linux.so.2 to /usr/lib/ld-2.16.so is probably enough, but then you will have errors when upgrading glibc. If you force the update then, it could work, but I don't know if that is a good idea.

Ok. Now the problem is how move everything back to /lib?
I couldn't start any program except LibreOffice. So, I've restarted the system thinking that I could use the console. Unfortunately I've encountered a kernel panic during the boot.

 ...
:: running cleanup hook [udev]
switch_root: failed to execute /sbin/init: No such file or directory
[3.701029] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[3.701031]
[3.701170]
 Pid: 1, comm: switch_root Tainted: G I 3.4.4-5-ck #1
[3.701243] Call Trace:
[3.701315] [<c04a65b9>] ? printk+0x1d/0x1f
[3.701385] [<c04a64a5>] panic+0x81/0x7f0
[3.701457] [<c013abb0>] do_exit+0x790/0x7f0
[3.701529] [<c13aea4>] do_group_exit+0x34/0xa0
[3.701600] [<c013af28>] sys_exit_group+0x18/0x20
[3.701671] [<c04aed5f>] sysenter_do_call+0x12/0x28

How can I get over it?

cfr · 2012-07-15 13:51:03

einhard wrote:

After glibc update /lib is owned by apache-ant . I don't get it, why? This package doesn't have any files in /lib or /usr/lib. If I uninstall it, the ownership comes back to glibc.

Something seems not quite right... I have apache-ant installed and pkgfile tells me that /lib is owned by glibc:

$ pacman -Ss apache-ant
extra/apache-ant 1.8.4-1 [installed]
    A java-based build tool
$ pkgfile /lib
core/glibc

pacman, however, believes differently:

$ \pacman -Qo /lib
/lib is owned by apache-ant 1.8.4-1

Note that pacman is aliased to pacmatic so I used \pacman to get the original command. (pacmatic follows pacman and also says apache-ant.)

I don't understand why. It is very odd. Perhaps somebody who knows something about pacman could explain it?

EDIT: Note that my upgrade was perfectly smooth. I did need to read the notes on the Developers' wiki and use a couple of the techniques there, but nothing untoward happened and the final upgrade of glibc proceeded without incident. Machine rebooted fine afterwards. System seems happy. (Or no more unhappy than before, anyway. )

Last edited by cfr (2012-07-15 13:58:57)

shaurz · 2012-07-15 13:54:35

If anyone else had the boot problem where it times out looking for the root fs, this is how I fixed it.

Boot a Live CD/USB image, chroot:

mount /dev/sda3 /mnt
mount -o bind /dev /mnt/dev
mount -t proc /proc /mnt/proc
mount -t sysfs /sys /mnt/sys
chroot /mnt bash

Then force a kernel update

pacman -Syy
pacman -S linux

For good measure I also re-installed glibc. Note: I did all this AFTER fixing /lib to be a symlink.

killer1804 · 2012-07-15 13:56:51

cfr wrote:

because you will have moved a bunch of stuff

Im not moved - im a copy. if you moved files from /lib to somewhere - it will break the system, because system will "lost" files from /lib, because, after upgrade glibc -system will be search lib's in /usr/lib, because after upgrade /lib will be a symlink to /usr/lib.
if you copy files, then, after "upgrade glibc with --force" the pacman also will removed /lib and create "lib -> /usr/lib", but in this case, system can find required libraries in /usr/lib.

cfr · 2012-07-15 14:05:38

killer1804 wrote:

cfr wrote:
because you will have moved a bunch of stuff
Im not moved - im a copy. if you moved files from /lib to somewhere - it will break the system, because system will "lost" files from /lib, because, after upgrade glibc -system will be search lib's in /usr/lib, because after upgrade /lib will be a symlink to /usr/lib.
if you copy files, then, after "upgrade glibc with --force" the pacman also will removed /lib and create "lib -> /usr/lib", but in this case, system can find required libraries in /usr/lib.

Yes, but post-upgrade they have effectively been moved. So instead of clearing up the contents of /lib/modules or files from ufw/hal/udev-compat, for example, you will have moved everything to /usr/lib/. You are effectively chucking your neglected laundry into a cupboard rather than doing the washing. The room will look just as tidy but your smelly socks are still there somewhere.

progandy · 2012-07-15 14:13:58

I am Gianluca wrote:

progandy wrote:
I am Gianluca wrote:
Is there a way to recognise which files I moved? They were about 15.
You have posted your find-output for /lib. So move everything back that is owned by glibc.
To get a working system again, a symlink from /lib/ld-linux.so.2 to /usr/lib/ld-2.16.so is probably enough, but then you will have errors when upgrading glibc. If you force the update then, it could work, but I don't know if that is a good idea.
Ok. Now the problem is how move everything back to /lib?

Use the first four steps from here to get a shell with read-write access https://bbs.archlinux.org/viewtopic.php … 1#p1127251

Last edited by progandy (2012-07-15 14:14:23)

killer1804 · 2012-07-15 14:27:30

cfr wrote:

The room will look just as tidy but your smelly socks are still there somewhere.

Yes, but we can do something like "pacman -Qo /lib/* | grep -v glibc", uninstall (whis pacman -R %pakegename%) all non glib's librarys, and install them later, if we will need. Before copying glibc's librarys we can delet all garbage from /lib.
I know the official way to upgrade glibc, but it was not help for me. Im delete all, other than glibc's libraries from /lib - but pacman still tell me "/lib is exists...", so that upgrading gone with the problems for me.

nos09 · 2012-07-15 14:43:17

The system upgrade was successful with 'pacman -Syu --ignore glibc', now I can't upgrade glibc... here is the outpupt of ownerships of /lib directory -

find /lib -exec pacman -Qo -- {} +
error: cannot determine ownership of directory '/lib'
error: cannot determine ownership of directory '/lib/modules'
error: cannot determine ownership of directory '/lib/modules/3.3.7-1-ARCH'
error: No package owns /lib/modules/3.3.7-1-ARCH/modules.symbols
error: No package owns /lib/modules/3.3.7-1-ARCH/modules.dep
error: No package owns /lib/modules/3.3.7-1-ARCH/modules.softdep
error: cannot determine ownership of directory '/lib/modules/3.3.7-1-ARCH/misc'
error: No package owns /lib/modules/3.3.7-1-ARCH/modules.devname
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
/lib/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libthread_db-1.0.so is owned by glibc 2.16.0-1
/lib/libnss_nis-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libm-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/libdl-2.16.so is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/libSegFault.so is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/ld-2.16.so is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_dns-2.16.so is owned by glibc 2.16.0-1
/lib/ld-linux.so.2 is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/libresolv-2.16.so is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_compat.so.2 is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libnss_db.so.2 is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/libutil.so.1 is owned by glibc 2.16.0-1
/lib/libutil-2.16.so is owned by glibc 2.16.0-1
/lib/libresolv.so.2 is owned by glibc 2.16.0-1

cfr · 2012-07-15 14:45:53

killer1804 wrote:

Yes, but we can do something like "pacman -Qo /lib/* | grep -v glibc", uninstall (whis pacman -R %pakegename%) all non glib's librarys, and install them later, if we will need. Before copying glibc's librarys we can delet all garbage from /lib.

That is much better but I didn't see you mention this step originally. Unless I missed it, my objection was primarily to your instructions as stated.

I know the official way to upgrade glibc, but it was not help for me. Im delete all, other than glibc's libraries from /lib - but pacman still tell me "/lib is exists...", so that upgrading gone with the problems for me.

That suggests something odd was happening. If you'd uninstalled whatever had stuff under /lib except glibc, what exactly was it complaining about? Did you have stuff which wasn't owned at all? (I did and I dealt with those files on a case-by-case basis.)

The point is that you shouldn't NEED to force the upgrade of glibc so if you are finding you can't upgrade otherwise, there has to be some reason for that and I think it would be better to address that issue rather than utilising your work around. I accept that your solution is better than most of the other things which people have arbitrarily tried but I don't think it is as satisfactory as following the procedures suggested in the wiki and taking the time to figure out any wrinkles.

fatboy · 2012-07-15 14:46:58

rm -r /lib/modules/

Last edited by fatboy (2012-07-15 14:47:18)

guelfi · 2012-07-15 14:49:53

If you don't use kernel 3.3.7, delete /lib/modules and try again.

Edit: too slow.

Last edited by guelfi (2012-07-15 14:50:17)

Arctus · 2012-07-15 14:52:11

Alternatively, if you want a more "safe" method, you can examine the content of the folder and remove the packages. In my case, the content belonged to packages "linux" and "nvidia", which I solved using:

pacman -Rdd nvidia linux
pacman -Syu --ignore glibc
pacman -S glibc
pacman -S nvidia linux

fatboy · 2012-07-15 14:59:08

Arctus wrote:

Alternatively, if you want a more "safe" method, you can examine the content of the folder and remove the packages. In my case, the content belonged to packages "linux" and "nvidia", which I solved using:
pacman -Rdd nvidia linux
pacman -Syu --ignore glibc
pacman -S glibc
pacman -S nvidia linux

I don't think you need to remove linux

fsckd · 2012-07-15 15:09:52

mod action: Merged nos09's thread, original title "can't upgrade glibc".

killer1804 · 2012-07-15 15:17:18

cfr wrote:

That suggests something odd was happening. If you'd uninstalled whatever had stuff under /lib except glibc, what exactly was it complaining about? Did you have stuff which wasn't owned at all? (I did and I dealt with those files on a case-by-case basis.)

Well...now I think the problem was that I did not delete the directory "modules" from /lib.
Im try to "pacman -S glibc", but take an pacman's error "/lib is exists"
After that i take a mistake - i moved stuff from /lib to /usr/lib and broke my Arch.
After that im boot up from my usb-disk and make a symlink from /usr/lib to /lib, boot to arch and make pacman -S glibc, pacman tell me something like "libc-2.16.so is exist", and im do "pacman -S --force glibc" - now its will work, but were problems whis kde - kde's settings is gone to default.
Now all seems fine, and work properly
After that im login to my test machine and try solution, which suggested.
Upgrading system on test machine will passed with no problems.

Last edited by killer1804 (2012-07-15 15:18:56)

rejoin · 2012-07-15 15:29:02

Hi again (my previous post was by guest53290),
everything is ok now! I booted an live cd and did a pacman -r /mnt -U /var/cache/pacman/pkg/glibc-2.16.0-2-x86_64.pkg.tar.xz rebooted and now more kernel panic!
Cheers

Arch Linux

#51 2012-07-15 10:57:02

Re: glibc update refusing to proceed. File ownership problem

#52 2012-07-15 11:17:01

Re: glibc update refusing to proceed. File ownership problem

#53 2012-07-15 11:32:58

Re: glibc update refusing to proceed. File ownership problem

#54 2012-07-15 11:35:55

Re: glibc update refusing to proceed. File ownership problem

#55 2012-07-15 12:56:42

Re: glibc update refusing to proceed. File ownership problem

#56 2012-07-15 13:11:04

Re: glibc update refusing to proceed. File ownership problem

#57 2012-07-15 13:15:58

Re: glibc update refusing to proceed. File ownership problem

#58 2012-07-15 13:37:18

Re: glibc update refusing to proceed. File ownership problem

#59 2012-07-15 13:43:01

Re: glibc update refusing to proceed. File ownership problem

#60 2012-07-15 13:50:07

Re: glibc update refusing to proceed. File ownership problem

#61 2012-07-15 13:51:03

Re: glibc update refusing to proceed. File ownership problem

#62 2012-07-15 13:54:35

Re: glibc update refusing to proceed. File ownership problem

#63 2012-07-15 13:56:51

Re: glibc update refusing to proceed. File ownership problem

#64 2012-07-15 14:05:38

Re: glibc update refusing to proceed. File ownership problem

#65 2012-07-15 14:13:58

Re: glibc update refusing to proceed. File ownership problem

#66 2012-07-15 14:27:30

Re: glibc update refusing to proceed. File ownership problem

#67 2012-07-15 14:43:17

Re: glibc update refusing to proceed. File ownership problem

#68 2012-07-15 14:45:53

Re: glibc update refusing to proceed. File ownership problem

#69 2012-07-15 14:46:58

Re: glibc update refusing to proceed. File ownership problem

#70 2012-07-15 14:49:53

Re: glibc update refusing to proceed. File ownership problem

#71 2012-07-15 14:52:11

Re: glibc update refusing to proceed. File ownership problem

#72 2012-07-15 14:59:08

Re: glibc update refusing to proceed. File ownership problem

#73 2012-07-15 15:09:52

Re: glibc update refusing to proceed. File ownership problem

#74 2012-07-15 15:17:18

Re: glibc update refusing to proceed. File ownership problem

#75 2012-07-15 15:29:02

Re: glibc update refusing to proceed. File ownership problem

Board footer