Produce relative paths #336
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Relates to #264
|
Thanks for the PR! |
|
Thanks for merging :) |
|
I'm wondering if this did not cause #364. |
|
See #364 (comment). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When upgrading the jdeb dependency in the gradle-debian-plugin, I stumbled upon failing tests. The tests related to paths which had been relative (no leading
/or having a./instead), but got a leading/with jdeb 1.7 and jdeb 1.8.This change reverts the behaviour back to jdeb 1.6 with two combined changes:
Utils#joinUnixPathnow doesn't prepend a/anymore (so, it only joins now)PermMapper#mapremoves any leading/, just like Apache commons-compress did in versions up to 1.10.Relates to #264