You are not logged in.
I managed to completely wreck my system during the /lib symlink upgrade. So I booted into a live image, mounted my partitions, and am trying to recover the system through various applications of
pacman -r newroot ...
There's all kinds of weird stuff going on now (I've modified the following console output to ignore the fact that I'm doing this in a different root)
# pacman -Su
targets (1): glibc-2.16.0-5
...
glibc: /lib exists in filesystem
glibc: /usr/lib/ld-2.16.so exists in filesystem
(a whole bunch of similar errors)
glibc: /usr/lib/libutil.so.1 exists in filesystem
This is weird because there are conflicts with /lib and /usr/lib.
# 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
(a whole bunch of similar lines)
/var/lib/pacman/local/glibc-2.16.0-1/files:lib64
so nothing else owns lib.
Since I'm in a live environment, and the only thing left to install is glibc, would it be okay to use --force in this situation?
Last edited by silverhammermba (2012-11-04 19:03:55)
Offline
see first post.
Last edited by silverhammermba (2012-11-04 19:00:25)
Offline
see first post.
Last edited by silverhammermba (2012-11-04 19:02:49)
Offline
https://www.archlinux.org/news/the-lib- … a-symlink/
Never use --force during this update.
maybe this helps
http://allanmcrae.com/2012/07/updating- … e-install/
Offline
I already tried those steps. I get the same error.
Offline