On Feb 15, Guillem Jover <guillem@debian.org> wrote: > > Somebody reported a similar problem about libcrypt.so.1, which moved > > from /lib/ (provided by libc) to /usr/lib/ (provided by libxcrypt). > If the problem was with the new pathname disappearing, then that's just > yet another instance of the usrmerge-via-symlinks collateral damage. No: the problem was an old libcrypt.so.1 left in /lib/. This cannot have anything to do with merged-usr: if /lib/ and /usr/lib/ on this system were actually merged then it would not be possible to have two different libraries around. > The irony in all this is that the usrmerge hack that got introduced to The irony is that in your quest to fight usrmerge, which at this point has been the default for all new installs and obviously did not cause any major troubles, you ranted at lenght about something which does not appear to be a real-life problem (people tend to report bugs which break PAM and perl...). -- ciao, Marco
Attachment:
signature.asc
Description: PGP signature