diff options
author | David Kalnischkies <david@kalnischkies.de> | 2018-02-02 19:14:09 +0100 |
---|---|---|
committer | David Kalnischkies <david@kalnischkies.de> | 2018-02-19 15:56:09 +0100 |
commit | b3e7a16265e7c6c3b6892b9ec8a787d692ced6e6 (patch) | |
tree | 631acc6779df934c8cac78f4ffa5776ab7d75d2a /test/integration/test-bug-735967-lib32-to-i386-unavailable | |
parent | 7aaf9b2c63aa8bdd87de4c19dcf1742c686a1cc2 (diff) |
ensure correct file permissions for auxfiles
The interesting takeaway here is perhaps that 'chmod +w' is effected by
the umask – obvious in hindsight of course. The usual setup helps with
hiding that applying that recursively on all directories (and files)
isn't correct. Ensuring files will not be stored with the wrong
permissions even if in strange umask contexts is trivial in comparison.
Fixing the test also highlighted that it wasn't bulletproof as apt will
automatically fix the permissions of the directories it works with, so
for this test we actually need to introduce a shortcut in the code.
Reported-By: Ubuntu autopkgtest CI
Diffstat (limited to 'test/integration/test-bug-735967-lib32-to-i386-unavailable')
0 files changed, 0 insertions, 0 deletions