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
{{ message }}
Repository navigation
Paths from slice dependency are not preserved (symlink vs directory) #3
[NOTE: I'm telling chisel to create /lib symlink because base-files contains it not as a symlink but as a directory and dotnet package needs that to be a symlink because the dotnet executable links to /lib/x86_64-linux-gnu/libstdc++.so.6 but libstdc++6 package installs it in /usr/lib/x86_64-linux-gnu/libstdc++.so.6. On Ubuntu usrmerge package does the job in postinst but we don't have that so that's why I'm creating the symlink manually. (To make dotnet work.)]
When a slice lists a path entry as a symlink to directory and some other slice depends on it and installs its files into symlink, the symlink is not preserved but instead a directory is created at that path. Example:
In this snippet you can see that /lib is created as symlink when no other slice installing files at that path is being installed. But afterwards it fails to install because of the symlink:
Activity