I had this same exact problem while either upgrading or installing a package(s) and I simply removed it (which I was almost sure would break something anyway) and reran pacman and it seemed to work fine. Although I probably wouldnt recommend doing it because it could possibly affect one package differently from another. On Wed, 2008-05-07 at 20:28 +0200, RedShift wrote: > Xavier wrote: > > Lukáš Jirkovský wrote: > >> Hi > >> I don't know if it's bug or feature, but it makes me crazy. It begun > >> probably after some pacman upgrade. > >> I'm using blowfish passwords with my archlinux, so my > >> /lib/libcrypt.so.1 points to libxcrypt.so.1 instead of libcrypt-2.7.so > >> from glibc. In my pacman.conf I have NoExtract = lib/libcrypt.so.1. > >> But even though I've made this arrangements everytime when I run > >> pacman -S some_interesting_package (it doesn't have to be glibc, eg > >> libpng is enough) the link gets changed. > >> Any suggestions? > >> > > > > From what I can tell, it's ldconfig who does this (try running it, it > > should overwrite your symlink). > > And pacman runs ldconfig when installing packages. > > Maybe someone can clarify further why ldconfig does this and if it's > > possible to prevent it. > > > > ldconfig makes sure you are using the most recent version of a certain library and provides a cache for the runtime linker. See man 8 ldconfig. > > Glenn >
