Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tracer: for bin -> usr/bin symlink on debian systems we might to track both paths #591

Open
yarikoptic opened this issue Jan 18, 2023 · 0 comments
Labels

Comments

@yarikoptic
Copy link
Member

somewhat more info on VIDA-NYU/reprozip#390 but the overall issue is:

❯ 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 .

yarikoptic added a commit to yarikoptic/ReproNim that referenced this issue Jan 18, 2023
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant