Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

Sprut1 · 2012-07-28 11:42:46

Hi,

im sorry if this has been asked before, I did find one thread that didn't answer my question completely.

I'm trying to update my system and have problems with both the filesystem update "filesystem upgrade - manual intervention required" (2012-06-07):
http://www.archlinux.org/news/filesyste … equired-1/
and the "The /lib directory becomes a symlink" (2012-07-14) upgrade:
http://www.archlinux.org/news/the-lib-d … a-symlink/

when trying

pacman -Syu --ignore filesystem && pacman -S filesystem --force

i get the following error:

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

since it's been a while since my last upgrade i followed the guide and did this:

pacman -U http://pkgbuild.com/~allan/glibc-2.16.0-1-x86_64.pkg.tar.xz

then when trying to upgrading ignoring glibc as mentioned in the guide i get this error:

pacman -Syu --ignore glibc

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

running --force when trying to upgrade while ignoring glibc could ruin the system, so I'm going to do that, but where do I go from here?

Edit: I read that some users moved the /lib/modules directory to another location while trying to upgrade, is this safe?

Last edited by Sprut1 (2012-07-28 11:47:07)

Gcool · 2012-07-28 12:06:37

Try the following and if succesfull, continue with the normal glibc upgrade procedure afterwards.

# pacman -Syu --ignore filesystem && rm -rf /var/run /var/lock && pacman -S filesystem

Sprut1 · 2012-07-28 18:27:10

# pacman -Syu --ignore filesystem && rm -rf /var/run /var/lock && pacman -S filesystem

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

As you see I get the exact same error, can I do an system upgrade with both ignore filesystem and ignore glibc?

Gcool · 2012-07-28 18:38:22

My bad, you need to exclude glibc as well obviously. You can specify multiple packages by separating them with a comma. So that would become something among the lines of:

# pacman -Syu --ignore filesystem,glibc && rm -rf /var/run /var/lock && pacman -S filesystem

Sprut1 · 2012-07-29 09:32:39

Gcool wrote:

My bad, you need to exclude glibc as well obviously. You can specify multiple packages by separating them with a comma. So that would become something among the lines of:
# pacman -Syu --ignore filesystem,glibc && rm -rf /var/run /var/lock && pacman -S filesystem

Thank you, I now have updated all my packages except filesystem and glibc. So how do I update filesystem and glibc? As no of them can be updated combined or separate.

fsckd · 2012-07-29 15:03:27

pacman -S filesystem

should have updated filesystem so you are in the clear there. Now just do

pacman -Su

as listed in https://wiki.archlinux.org/index.php/De … iki:usrlib.
This problem has been covered many times. Search the forums for how other people solved updating glibc and filesystem.

Sprut1 · 2012-07-29 19:07:53

fsckd wrote:

pacman -S filesystem
should have updated filesystem so you are in the clear there. Now just do
pacman -Su
as listed in https://wiki.archlinux.org/index.php/De … iki:usrlib.
This problem has been covered many times. Search the forums for how other people solved updating glibc and filesystem.

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

I still have the exact same problem as before, only difference now is that my other packages has been updated. I still can't update filesystem or glibc and the wiki doesn't cover this case.

mariusmeyer · 2012-07-29 20:14:55

Read the old news about filesystem and glibs and do these ugrades SEPARATELY. And yes, your situation has in fact been covered lots of times on the forums, on Allan's blog etc etc.

decimal · 2012-07-29 23:56:42

I regretfully tried to upgrade without reading about it and I used -f . Now I'm getting a kernel panic at boot time. Any ideas for a fix?

Trilby · 2012-07-30 01:14:18

Sprut1 wrote:

running --force when trying to upgrade while ignoring glibc could ruin the system, so I'm going to do that,

This (suspected) typo of leaving out the "not" gave me a good laugh, mostly because for so many it would not have been a typo.

On the less unproductive side of this post, decimal, you'll probably want to look at the long thread where several dozen other people made the same mistake and found solutions.

jasonwryan · 2012-07-30 01:22:37

Indeed - this has been extensively covered and the wiki has captured all of the different variations of fixes.

Closing.

Arch Linux

#1 2012-07-28 11:42:46

Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#2 2012-07-28 12:06:37

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#3 2012-07-28 18:27:10

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#4 2012-07-28 18:38:22

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#5 2012-07-29 09:32:39

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#6 2012-07-29 15:03:27

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#7 2012-07-29 19:07:53

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#8 2012-07-29 20:14:55

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#9 2012-07-29 23:56:42

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#10 2012-07-30 01:14:18

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

#11 2012-07-30 01:22:37

Re: Filesystem update (2012-06-07) & /lib to /usr/lib symlink (2012-07-14)

Board footer