On Aug 11, Marco d'Itri <[email protected]> wrote: > I will try to reproduce this and figure out how to fix the order of > things. I have not been able to reproduce the issue, but I think that I have committed a fix for this case.
I want to stress that convert-usrmerge is supposed to be interrupted at any time without causing troubles, so this behaviour is definitely a bug no matter what the initial conditions were. FYI, this was my test setup: mount -t tmpfs tmpfs /tmp/test/ rsync -a .../fresh/buster/chroot/ /tmp/test/ systemd-nspawn --setenv=LANG=C.UTF-8 \ --tmpfs=/tmp/:mode=1777 \ --bind=/usr/src/ \ --register=no \ --directory=/tmp/test/ # this is not the right broken link to trigger the bug #ln -s /lib/x86_64-linux-gnu/libpcre.so.3 /usr/lib/x86_64-linux-gnu/libpcre.so.3 # and neither is this one: ln -s /bin/true /usr/lib/x86_64-linux-gnu/true ln -s /bin/false /lib/x86_64-linux-gnu/true /usr/src/usrmerge/usrmerge-17/convert-usrmerge -- ciao, Marco
signature.asc
Description: PGP signature
