Stéphane writes: > Concerning #390915, I don't agree with the way the original (LP > #51468) bug was fixed. Again, plain tar behaves correctly IMHO.
Sorry that I didn't reply at the time. I found this bug again now. I still think that the fix in #390915 is correct. Unpacking source code definitely ought to respect the user's umask. Otherwise the source will not be writeable to their collaborators, as intended. That tar (often, depending on options) behaves differently is because tar is trying to be several different kinds of utility in one. I think a package build where the output file permissions depend on the user's umask is a buggy package build. (And this is not just a reproducibility issue.) This is what we have dh_fixperms for: to manage the difference between source file and intermediate build product permissions (which should respect the user's umask) and binary-package-in-preparation permissions (which need to be those intended for the output package). Does that make sense ? Thanks, Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
