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
The implementation assumes the LinkName stored for a hard link is a path relative to the location of the link (like with a symbolic link).
However, the LinkName for a hard link is path relative to the archive extraction directory.
I've included a commit that fixes this in the PR I already had open which changes some related code: #85378.
I can move it to a separate PR if desired.
Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.
Issue Details
The implementation assumes the LinkName stored for a hard link is a path relative to the location of the link (like with a symbolic link).
However, the LinkName for a hard link is path relative to the archive extraction directory.
I've included a commit that fixes this in the PR I already had open which changes some related code: #85378.
I can move it to a separate PR if desired.
Tagging subscribers to this area: @dotnet/area-system-io-compression
See info in area-owners.md if you want to be subscribed.
Issue Details
The implementation assumes the LinkName stored for a hard link is a path relative to the location of the link (like with a symbolic link).
However, the LinkName for a hard link is path relative to the archive extraction directory.
I've included a commit that fixes this in the PR I already had open which changes some related code: #85378.
I can move it to a separate PR if desired.
The implementation assumes the
LinkName
stored for a hard link is a path relative to the location of the link (like with a symbolic link).However, the
LinkName
for a hard link is path relative to the archive extraction directory.I've included a commit that fixes this in the PR I already had open which changes some related code: #85378.
I can move it to a separate PR if desired.
cc @dotnet/area-system-io @carlossanlop @adamsitnik
The text was updated successfully, but these errors were encountered: