jdeb: archive entry has inconsistent/wrong leading slashes

In version 1.4 PermMapper was changed and now instead of creating a new TarArchiveEntry it uses the one provided to the map function. Before the TarArchiveEntry constructor was called with preserveLeadingSlashes true. Now the setName method is called without the second parameter meaning preserveLeadingSlashes is false. So, in version 1.3 if I use a PermMapper with prefix “/etc/default” my conffile entry looks like: /etc/default/file-name but in 1.4 it’s generated as etc/default/file-name

can you pass true as the second parameter to setName and fix this?

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 31 (22 by maintainers)

Most upvoted comments

both? nice!

@peternewman if you are able provide a patch I am happy to apply it and make a well needed release.

The pom is still listing commons-compress 1.10 - but it was fixed in 1.11. I guess it’s time for fixing this in jdeb as well now.