You are not logged in.
Pages: 1
Hello,
Today pacman is dynamically linked to a lot of libraries, so when an error occur about the update these libraries, pacman will not work any more
To illustrate, let me show you what I did.
# pacman -Suy
error: failed to commit transaction (conflicting files)
glibc: /lib exists in filesystem
# pacman -S glibc
:: valgrind: requires glibc<2.16
# pacman -S valgrind --force
error: extract: not overwriting dir with file lib
# pacman -Suy
/usr/bin/pacman: No such file or directory
# ls
/bin/ls: No such file or directory
Of course this is the worth case, because now glibc do not exist any more and the system will not reboot :-(
So I have two questions:
- What I should do to avoid this situation ?
- Is it not possible to link statically to have an independent pacman of the libraries update errors ?
Offline
...- What I should do to avoid this situation ?
Read the News and the Forums.
http://www.archlinux.org/news/the-lib-d … a-symlink/
http://www.archlinux.org/news/filesyste … equired-1/
Is it not possible to link statically to have an independent pacman of the libraries update errors ?
I think that has been discussed as well, but it really isn't your problem
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Nothing stops you from doing so. You could always have a static pacman somewhere on your hard disk. This is probably not a bad idea.
Offline
Pages: 1