You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
❯ ls -ld /bin
lrwxrwxrwx 1 root root 7 Nov 5 2019 /bin -> usr/bin/
❯ dpkg -S /{,usr/}bin/ls
coreutils: /bin/ls
dpkg-query: no path found matching pattern /usr/bin/ls
❯ dpkg -S /{,usr/}bin/whoami
dpkg-query: no path found matching pattern /bin/whoami
coreutils: /usr/bin/whoami
so for some binaries package would know about /usr/bin path and for other, /bin paths. In both cases users might run one or another and reprozip might dereference symlink (VIDA-NYU/reprozip#390) so we could end up with /usr/bin paths. I think we can "hard code" logic that iff issymlink('/bin'): trace both paths .
The text was updated successfully, but these errors were encountered:
quick summary of the problem: on debian there is bin -> usr/bin symlink,
but then /bin/ls is the one known to the package. reprozip resolves path
to /usr/bin/ls and we end up without package information.
More info on VIDA-NYU/reprozip#390
and reproman specific issue ReproNim#591
somewhat more info on VIDA-NYU/reprozip#390 but the overall issue is:
so for some binaries package would know about /usr/bin path and for other, /bin paths. In both cases users might run one or another and reprozip might dereference symlink (VIDA-NYU/reprozip#390) so we could end up with /usr/bin paths. I think we can "hard code" logic that
iff issymlink('/bin'): trace both paths
.The text was updated successfully, but these errors were encountered: