> Is my current (commited) modification, though I'm unsure if resetting the > umask to the previous value is really necessary...
Yeah... me too. Resetting the previous value of umask is just a prevention decision because through the program code a lot of files and directories are created. It is necessary to study if other files/directories depends on concrete permissions so that a custom umask value would corrupt them. For all these reasons, I think current patch is a good solution. I have to read more slowly the piuparts code to understand it better, so I'll take a look to this issue. Cheers, Cleto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
