glibc update refusing to proceed. File ownership problem

ArchLinuxSA · 2012-07-18 20:19:58

Barrucadu wrote:

ArchLinuxSA wrote:
I followed this post https://wiki.archlinux.org/index.php/De … iki:usrlib and I have deleted the /lib direcotry. Now I cannot boot my system, so I am really in a serious issue, any help would be appreciated.
No, you misread it, it doesn't say to delete /lib.

Thank you for your reply which is really appreciated. Is there a way to recover my system?

Barrucadu · 2012-07-18 20:34:19

The same solution as for pretty much everyone else: boot a livecd, mount your partitions, and reinstall the broken packages.

ERiS · 2012-07-19 03:35:48

Hi, I followed the great wiki instructions and was able to update my computer.

At the end I tried to verify the symlink is correct, and I got:

lrwxrwxrwx 1 root root 7 Jul  7 06:09 /lib -> usr/lib/

( Note that there is a forward slash ( / ) at the end. )

instead of:

lrwxrwxrwx   1 root root     7 Jul 11 21:10 lib -> usr/lib

( No forward slash )

Is it okay that way?

One time I had some Irssi problems because of an extra slash, so I want to make sure. Thanks everyone.

RaisedFist · 2012-07-19 07:10:42

@ERis: if you did 'ls -ld /lib' there will be a slash, if you're in / and do 'ls -ld lib' of course there will be no slash in front.

W.F.Cody · 2012-07-19 08:02:37

I also got bitten by this and was VERY happy that I had a busybox binary statically linked against musl libc in my PATH. Thanks to that I could remove /lib after glibc installation broke halfway during installation and could manually extract the package from /var/cache/pacman/pkg

in fact, it could perhaps be a good idea to have a static busybox by default in a fallback directory in the PATH

viking60 · 2012-07-19 09:51:55

I thought a success story could be fitting by now; I have successfully updated two different laptops! I noticed that plymouth was the owner for some files in module so I uninstalled it (and re-installed it afterwords)..
Then I deleted some not owned files and directories where there was nothing to uninstall (while sending prayers).
I did not move anything! The wiki works - kind of - but I would like to see some serious "this could eat your hamster" warnings. And I do understand that some people have been tempted to move stuff manually to /usr/lib.
And I feel a bit sorry for them when they get the" you YOU you have broke your system" -from the Moderators. They already feel bad enough
I agree though that the devs of Arch are doing a fantastic job (and I doubt that they would get offended by the occasional user fubaring their system) I appreciate it - thanks!

This has been a bit bumpy though; luckily I approached this like stroking a Hedgehog - very carefully.

ephan · 2012-07-19 13:33:48

progandy wrote:

ephan wrote:
Strike0 wrote:
@ephan: After the mounts, did you reinstall the version of glibc you unintentionally deleted?
I can't install glib if I can't boot, can I? So, the answer is no.
boot from cd. Mount root, /var and /boot. Install glibc from cache in mounted arch. pacman -U -r /mnt/arch /mnt/arch/var/cache/pacman/pkg/glibc.... Unmount. Reboot.

I did all that, but I don't think i have a /var partition. I mounted /boot and /root, and tried that. However, I got "Cannot open package file" on "/mnt/arch/var/cache/pacman/pkg/glibc-2.1"

Any ideas? Thank you.

Barrucadu · 2012-07-19 13:56:18

ephan wrote:

I did all that, but I don't think i have a /var partition. I mounted /boot and /root, and tried that. However, I got "Cannot open package file" on "/mnt/arch/var/cache/pacman/pkg/glibc-2.1"
Any ideas? Thank you.

Try giving the full name of the file.

ephan · 2012-07-19 14:26:14

Barrucadu wrote:

ephan wrote:
I did all that, but I don't think i have a /var partition. I mounted /boot and /root, and tried that. However, I got "Cannot open package file" on "/mnt/arch/var/cache/pacman/pkg/glibc-2.1"
Any ideas? Thank you.
Try giving the full name of the file.

I did give it:

"error: /mnt/arch/var/cache/pacman/pkg/glibc-2.1: cannot open package file"

nomorewindows · 2012-07-19 14:33:18

ephan wrote:

Barrucadu wrote:
ephan wrote:
I did all that, but I don't think i have a /var partition. I mounted /boot and /root, and tried that. However, I got "Cannot open package file" on "/mnt/arch/var/cache/pacman/pkg/glibc-2.1"
Any ideas? Thank you.
Try giving the full name of the file.
I did give it:
"error: /mnt/arch/var/cache/pacman/pkg/glibc-2.1: cannot open package file"

glibc-2.1 should include glibc-2.1-x-architecture.pkg.tar.xz
do an ls of the /mnt/arch/var/cache/pacman/pkg directory.

Last edited by nomorewindows (2012-07-19 14:33:34)

ephan · 2012-07-19 14:40:46

I tried a glib-2.16-0-2 or something, and I got a /mnt/arch/lib exists in filesystem AND a ton of /mnt/arch/usr/lib/lib(...).so.... exists in filesystems.~

Should I delete what it says (exists in filesystem) or use glib-2.15?

EDIT
I deleted all it claimed to "already exist in filesystem", installation worked, I rebooted, and Arch install worked. Everything works, thanks!

Last edited by ephan (2012-07-19 16:23:59)

nomorewindows · 2012-07-19 17:45:22

I found out that if you haven't updated some machines in a while and don't have at least glibc-2.16.0-1 installed at the time of this update, you may not be able to update your system. All of the current packages that depend on glibc require at least glibc-2.16.0-1 before proceeding to glibc-2.16.0-2. You'll have to pull the glibc-2.16.0-1 from somewhere and install it before updating to glibc-2.16.0-2.

Last edited by nomorewindows (2012-07-19 17:47:33)

progandy · 2012-07-19 19:29:03

nomorewindows wrote:

I found out that if you haven't updated some machines in a while and don't have at least glibc-2.16.0-1 installed at the time of this update, you may not be able to update your system. All of the current packages that depend on glibc require at least glibc-2.16.0-1 before proceeding to glibc-2.16.0-2. You'll have to pull the glibc-2.16.0-1 from somewhere and install it before updating to glibc-2.16.0-2.

Allan has created a mirror for glibc 2.16.0-1 for his core-install instructions: http://allanmcrae.com/2012/07/updating- … e-install/

hbernier · 2012-07-19 19:54:38

I have not broken my system.

I followed the steps on the wiki, performing an update ignoring glibc, then upgrading glibc.
I backed up and moved files with no owners. All other files are owned by glibc 2.16.0-1.

Now when I run

find /lib -exec pacman -Qo -- {} + | grep -v "glibc 2.16.0-1"

I get

error: cannot determine ownership of directory '/lib'

If I try to update using

sudo pacman -Su

I get

error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
Errors occurred, no packages were upgraded.

I have posted the complete output of the find command below, without the grep. As you will note, all files are owned by glibc, yet glibc does not update.
Is there a 'safe' way to update my system at this point? Is it normal that glibc does not own /lib? Is this the problem?

error: cannot determine ownership of directory '/lib'
/lib/libnss_dns-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/ld-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/ld-linux-x86-64.so.2 is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/libnsl-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/libSegFault.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libc-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/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
/lib/libBrokenLocale-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_nis-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/libutil-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/libresolv.so.2 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-1.0.so is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libm-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/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libutil.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.so.2 is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1

progandy · 2012-07-19 20:04:05

/lib must not contain any subfolders. Backup or move contained files and remove the empty folders.

hbernier · 2012-07-19 20:06:56

@progandy
It doesn't.

[user@something lib]$ ls -l
total 4084
-rwxr-xr-x 1 root root  165328 Jul  2 10:33 ld-2.16.so
lrwxrwxrwx 1 root root      10 Jul  2 10:33 ld-linux-x86-64.so.2 -> ld-2.16.so
-rwxr-xr-x 1 root root   14952 Jul  2 10:33 libanl-2.16.so
lrwxrwxrwx 1 root root      14 Jul  2 10:33 libanl.so.1 -> libanl-2.16.so
-rwxr-xr-x 1 root root    6256 Jul  2 10:33 libBrokenLocale-2.16.so
lrwxrwxrwx 1 root root      23 Jul  2 10:33 libBrokenLocale.so.1 -> libBrokenLocale-2.16.so
-rwxr-xr-x 1 root root 1997041 Jul  2 10:33 libc-2.16.so
-rwxr-xr-x 1 root root  190840 Jul  2 10:33 libcidn-2.16.so
lrwxrwxrwx 1 root root      15 Jul  2 10:33 libcidn.so.1 -> libcidn-2.16.so
-rwxr-xr-x 1 root root   35112 Jul  2 10:33 libcrypt-2.16.so
lrwxrwxrwx 1 root root      16 Jul  2 10:33 libcrypt.so.1 -> libcrypt-2.16.so
lrwxrwxrwx 1 root root      12 Jul  2 10:33 libc.so.6 -> libc-2.16.so
-rwxr-xr-x 1 root root   14624 Jul  2 10:33 libdl-2.16.so
lrwxrwxrwx 1 root root      13 Jul  2 10:33 libdl.so.2 -> libdl-2.16.so
-rwxr-xr-x 1 root root 1022320 Jul  2 10:33 libm-2.16.so
-rwxr-xr-x 1 root root   18760 Jul  2 10:33 libmemusage.so
lrwxrwxrwx 1 root root      12 Jul  2 10:33 libm.so.6 -> libm-2.16.so
-rwxr-xr-x 1 root root   89064 Jul  2 10:33 libnsl-2.16.so
lrwxrwxrwx 1 root root      14 Jul  2 10:33 libnsl.so.1 -> libnsl-2.16.so
-rwxr-xr-x 1 root root   31608 Jul  2 10:33 libnss_compat-2.16.so
lrwxrwxrwx 1 root root      21 Jul  2 10:33 libnss_compat.so.2 -> libnss_compat-2.16.so
-rwxr-xr-x 1 root root   31120 Jul  2 10:33 libnss_db-2.16.so
lrwxrwxrwx 1 root root      17 Jul  2 10:33 libnss_db.so.2 -> libnss_db-2.16.so
-rwxr-xr-x 1 root root   22912 Jul  2 10:33 libnss_dns-2.16.so
lrwxrwxrwx 1 root root      18 Jul  2 10:33 libnss_dns.so.2 -> libnss_dns-2.16.so
-rwxr-xr-x 1 root root   52112 Jul  2 10:33 libnss_files-2.16.so
lrwxrwxrwx 1 root root      20 Jul  2 10:33 libnss_files.so.2 -> libnss_files-2.16.so
-rwxr-xr-x 1 root root   22944 Jul  2 10:33 libnss_hesiod-2.16.so
lrwxrwxrwx 1 root root      21 Jul  2 10:33 libnss_hesiod.so.2 -> libnss_hesiod-2.16.so
-rwxr-xr-x 1 root root   47656 Jul  2 10:33 libnss_nis-2.16.so
-rwxr-xr-x 1 root root   51696 Jul  2 10:33 libnss_nisplus-2.16.so
lrwxrwxrwx 1 root root      22 Jul  2 10:33 libnss_nisplus.so.2 -> libnss_nisplus-2.16.so
lrwxrwxrwx 1 root root      18 Jul  2 10:33 libnss_nis.so.2 -> libnss_nis-2.16.so
-rwxr-xr-x 1 root root    6280 Jul  2 10:33 libpcprofile.so
-rwxr-xr-x 1 root root  137982 Jul  2 10:33 libpthread-2.16.so
lrwxrwxrwx 1 root root      18 Jul  2 10:33 libpthread.so.0 -> libpthread-2.16.so
-rwxr-xr-x 1 root root   84808 Jul  2 10:33 libresolv-2.16.so
lrwxrwxrwx 1 root root      17 Jul  2 10:33 libresolv.so.2 -> libresolv-2.16.so
-rwxr-xr-x 1 root root   31744 Jul  2 10:33 librt-2.16.so
lrwxrwxrwx 1 root root      13 Jul  2 10:33 librt.so.1 -> librt-2.16.so
-rwxr-xr-x 1 root root   18688 Jul  2 10:33 libSegFault.so
-rwxr-xr-x 1 root root   38383 Jul  2 10:33 libthread_db-1.0.so
lrwxrwxrwx 1 root root      19 Jul  2 10:33 libthread_db.so.1 -> libthread_db-1.0.so
-rwxr-xr-x 1 root root   10640 Jul  2 10:33 libutil-2.16.so
lrwxrwxrwx 1 root root      15 Jul  2 10:33 libutil.so.1 -> libutil-2.16.so

ploub · 2012-07-19 20:08:31

nomorewindows wrote:

I found out that if you haven't updated some machines in a while and don't have at least glibc-2.16.0-1 installed at the time of this update, you may not be able to update your system. All of the current packages that depend on glibc require at least glibc-2.16.0-1 before proceeding to glibc-2.16.0-2. You'll have to pull the glibc-2.16.0-1 from somewhere and install it before updating to glibc-2.16.0-2.

How I wish I'd read that before hosing my system...preparing to reinstall right now

hbernier · 2012-07-19 20:10:26

@ploub
That's not the issue for me, all files are currently owned by glibc 2.16.0-1.

Last edited by hbernier (2012-07-19 20:15:05)

nomorewindows · 2012-07-19 20:40:12

ploub wrote:

nomorewindows wrote:
I found out that if you haven't updated some machines in a while and don't have at least glibc-2.16.0-1 installed at the time of this update, you may not be able to update your system. All of the current packages that depend on glibc require at least glibc-2.16.0-1 before proceeding to glibc-2.16.0-2. You'll have to pull the glibc-2.16.0-1 from somewhere and install it before updating to glibc-2.16.0-2.
How I wish I'd read that before hosing my system...preparing to reinstall right now

The file you need is at http://pkgbuild.com/~allan/ (from the above post)

I am Gianluca · 2012-07-19 21:21:29

Am I the only one that have this result?

$ sudo pacman -Su
Password: 
:: 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
glibc: /usr/lib/ld-2.16.so exists in filesystem
glibc: /usr/lib/ld-linux.so.2 exists in filesystem
glibc: /usr/lib/libBrokenLocale-2.16.so exists in filesystem
glibc: /usr/lib/libBrokenLocale.so.1 exists in filesystem
glibc: /usr/lib/libSegFault.so exists in filesystem
glibc: /usr/lib/libanl-2.16.so exists in filesystem
glibc: /usr/lib/libanl.so.1 exists in filesystem
glibc: /usr/lib/libc-2.16.so exists in filesystem
glibc: /usr/lib/libc.so.6 exists in filesystem
glibc: /usr/lib/libcidn-2.16.so exists in filesystem
glibc: /usr/lib/libcidn.so.1 exists in filesystem
glibc: /usr/lib/libcrypt-2.16.so exists in filesystem
glibc: /usr/lib/libcrypt.so.1 exists in filesystem
glibc: /usr/lib/libdl-2.16.so exists in filesystem
glibc: /usr/lib/libdl.so.2 exists in filesystem
glibc: /usr/lib/libm-2.16.so exists in filesystem
glibc: /usr/lib/libm.so.6 exists in filesystem
glibc: /usr/lib/libmemusage.so exists in filesystem
glibc: /usr/lib/libnsl-2.16.so exists in filesystem
glibc: /usr/lib/libnsl.so.1 exists in filesystem
glibc: /usr/lib/libnss_compat-2.16.so exists in filesystem
glibc: /usr/lib/libnss_compat.so.2 exists in filesystem
glibc: /usr/lib/libnss_db-2.16.so exists in filesystem
glibc: /usr/lib/libnss_db.so.2 exists in filesystem
glibc: /usr/lib/libnss_dns-2.16.so exists in filesystem
glibc: /usr/lib/libnss_dns.so.2 exists in filesystem
glibc: /usr/lib/libnss_files-2.16.so exists in filesystem
glibc: /usr/lib/libnss_files.so.2 exists in filesystem
glibc: /usr/lib/libnss_hesiod-2.16.so exists in filesystem
glibc: /usr/lib/libnss_hesiod.so.2 exists in filesystem
glibc: /usr/lib/libnss_nis-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nis.so.2 exists in filesystem
glibc: /usr/lib/libnss_nisplus-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nisplus.so.2 exists in filesystem
glibc: /usr/lib/libpcprofile.so exists in filesystem
glibc: /usr/lib/libpthread-2.16.so exists in filesystem
glibc: /usr/lib/libpthread.so.0 exists in filesystem
glibc: /usr/lib/libresolv-2.16.so exists in filesystem
glibc: /usr/lib/libresolv.so.2 exists in filesystem
glibc: /usr/lib/librt-2.16.so exists in filesystem
glibc: /usr/lib/librt.so.1 exists in filesystem
glibc: /usr/lib/libthread_db-1.0.so exists in filesystem
glibc: /usr/lib/libthread_db.so.1 exists in filesystem
glibc: /usr/lib/libutil-2.16.so exists in filesystem
glibc: /usr/lib/libutil.so.1 exists in filesystem
Errors occurred, no packages were upgraded.

nomorewindows · 2012-07-19 21:22:20

How did you do that?

ERiS · 2012-07-19 21:22:42

RaisedFist:

@ERis: if you did 'ls -ld /lib' there will be a slash, if you're in / and do 'ls -ld lib' of course there will be no slash in front.

In all cases there were slashes at the end:

~ ✻  ls -ld /lib
lrwxrwxrwx 1 root root 7 Jul  7 06:09 /lib -> usr/lib/

/ ✻  ls -ld /lib
lrwxrwxrwx 1 root root 7 Jul  7 06:09 /lib -> usr/lib/

/ ✻  ls -ld lib
lrwxrwxrwx 1 root root 7 Jul  7 06:09 lib -> usr/lib/

However it doesn't seem to be an issue, I had to go to sleep so I rebooted, and today it seems fine.

I am Gianluca · 2012-07-19 21:42:38

nomorewindows wrote:

How did you do that?

This is the story of my glibc update: link
After this I fix my system following the advice of progandy: link

and

# rm -Rf lib
# ln -s usr/lib lib

So, I rebooted and open a terminal session:

# sudo -Syu --ignore glibc
# sudo -Su
Password: 
:: 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
glibc: /usr/lib/ld-2.16.so exists in filesystem
glibc: /usr/lib/ld-linux.so.2 exists in filesystem
glibc: /usr/lib/libBrokenLocale-2.16.so exists in filesystem
glibc: /usr/lib/libBrokenLocale.so.1 exists in filesystem
glibc: /usr/lib/libSegFault.so exists in filesystem
glibc: /usr/lib/libanl-2.16.so exists in filesystem
glibc: /usr/lib/libanl.so.1 exists in filesystem
glibc: /usr/lib/libc-2.16.so exists in filesystem
glibc: /usr/lib/libc.so.6 exists in filesystem
glibc: /usr/lib/libcidn-2.16.so exists in filesystem
glibc: /usr/lib/libcidn.so.1 exists in filesystem
glibc: /usr/lib/libcrypt-2.16.so exists in filesystem
glibc: /usr/lib/libcrypt.so.1 exists in filesystem
glibc: /usr/lib/libdl-2.16.so exists in filesystem
glibc: /usr/lib/libdl.so.2 exists in filesystem
glibc: /usr/lib/libm-2.16.so exists in filesystem
glibc: /usr/lib/libm.so.6 exists in filesystem
glibc: /usr/lib/libmemusage.so exists in filesystem
glibc: /usr/lib/libnsl-2.16.so exists in filesystem
glibc: /usr/lib/libnsl.so.1 exists in filesystem
glibc: /usr/lib/libnss_compat-2.16.so exists in filesystem
glibc: /usr/lib/libnss_compat.so.2 exists in filesystem
glibc: /usr/lib/libnss_db-2.16.so exists in filesystem
glibc: /usr/lib/libnss_db.so.2 exists in filesystem
glibc: /usr/lib/libnss_dns-2.16.so exists in filesystem
glibc: /usr/lib/libnss_dns.so.2 exists in filesystem
glibc: /usr/lib/libnss_files-2.16.so exists in filesystem
glibc: /usr/lib/libnss_files.so.2 exists in filesystem
glibc: /usr/lib/libnss_hesiod-2.16.so exists in filesystem
glibc: /usr/lib/libnss_hesiod.so.2 exists in filesystem
glibc: /usr/lib/libnss_nis-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nis.so.2 exists in filesystem
glibc: /usr/lib/libnss_nisplus-2.16.so exists in filesystem
glibc: /usr/lib/libnss_nisplus.so.2 exists in filesystem
glibc: /usr/lib/libpcprofile.so exists in filesystem
glibc: /usr/lib/libpthread-2.16.so exists in filesystem
glibc: /usr/lib/libpthread.so.0 exists in filesystem
glibc: /usr/lib/libresolv-2.16.so exists in filesystem
glibc: /usr/lib/libresolv.so.2 exists in filesystem
glibc: /usr/lib/librt-2.16.so exists in filesystem
glibc: /usr/lib/librt.so.1 exists in filesystem
glibc: /usr/lib/libthread_db-1.0.so exists in filesystem
glibc: /usr/lib/libthread_db.so.1 exists in filesystem
glibc: /usr/lib/libutil-2.16.so exists in filesystem
glibc: /usr/lib/libutil.so.1 exists in filesystem
Errors occurred, no packages were upgraded.

hbernier · 2012-07-19 21:51:21

With the help of Earnestly, Tom^ and many others from the irc channel, we discovered a missing file in the /lib directory was the culprit. The file belonged to a dependency of google-earth, ld-lsb. What's interesting is that this particular insight was not gleaned from pacman -Su --debug.

The command which yielded this insight was:

 pacman -Qk --debug

My issue is now resolved cleanly and without damaging my system.

nomorewindows · 2012-07-19 23:04:46

hbernier wrote:

With the help of Earnestly, Tom^ and many others from the irc channel, we discovered a missing file in the /lib directory was the culprit. The file belonged to a dependency of google-earth, ld-lsb. What's interesting is that this particular insight was not gleaned from pacman -Su --debug.
The command which yielded this insight was:
 pacman -Qk --debug 
My issue is now resolved cleanly and without damaging my system.

pacman -Qo is what I used as I was going through the /lib directory and subdirectories.

Arch Linux

#201 2012-07-18 20:19:58

Re: glibc update refusing to proceed. File ownership problem

#202 2012-07-18 20:34:19

Re: glibc update refusing to proceed. File ownership problem

#203 2012-07-19 03:35:48

Re: glibc update refusing to proceed. File ownership problem

#204 2012-07-19 07:10:42

Re: glibc update refusing to proceed. File ownership problem

#205 2012-07-19 08:02:37

Re: glibc update refusing to proceed. File ownership problem

#206 2012-07-19 09:51:55

Re: glibc update refusing to proceed. File ownership problem

#207 2012-07-19 13:33:48

Re: glibc update refusing to proceed. File ownership problem

#208 2012-07-19 13:56:18

Re: glibc update refusing to proceed. File ownership problem

#209 2012-07-19 14:26:14

Re: glibc update refusing to proceed. File ownership problem

#210 2012-07-19 14:33:18

Re: glibc update refusing to proceed. File ownership problem

#211 2012-07-19 14:40:46

Re: glibc update refusing to proceed. File ownership problem

#212 2012-07-19 17:45:22

Re: glibc update refusing to proceed. File ownership problem

#213 2012-07-19 19:29:03

Re: glibc update refusing to proceed. File ownership problem

#214 2012-07-19 19:54:38

Re: glibc update refusing to proceed. File ownership problem

#215 2012-07-19 20:04:05

Re: glibc update refusing to proceed. File ownership problem

#216 2012-07-19 20:06:56

Re: glibc update refusing to proceed. File ownership problem

#217 2012-07-19 20:08:31

Re: glibc update refusing to proceed. File ownership problem

#218 2012-07-19 20:10:26

Re: glibc update refusing to proceed. File ownership problem

#219 2012-07-19 20:40:12

Re: glibc update refusing to proceed. File ownership problem

#220 2012-07-19 21:21:29

Re: glibc update refusing to proceed. File ownership problem

#221 2012-07-19 21:22:20

Re: glibc update refusing to proceed. File ownership problem

#222 2012-07-19 21:22:42

Re: glibc update refusing to proceed. File ownership problem

#223 2012-07-19 21:42:38

Re: glibc update refusing to proceed. File ownership problem

#224 2012-07-19 21:51:21

Re: glibc update refusing to proceed. File ownership problem

#225 2012-07-19 23:04:46

Re: glibc update refusing to proceed. File ownership problem

Board footer