Package: disorderfs
Version: 0.4.2-1
Severity: normal

Dear Maintainer,

While working on a tool to test build reproducibility with disorderfs,
I noticed that setting the umask in a subprocess doesn't seem to
affect the permissions of a file created on a disorderfs mount.  The
command that my tool executes is:

umask 0002; linux64 --uname-2.6 python umask creates a file using the standard library
module pathlib.Path.touch(), which depends on the Python process's umask.

When this is not operating on a disorderfs mount, the permissions
of the created file are altered by the umask call:


When operating on a disorderfs mount, the umask doesn't seem to
affect them:


-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-36-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages disorderfs depends on:
ii  fuse        2.9.4-1ubuntu1
ii  libc6       2.21-0ubuntu4.3
ii  libfuse2    2.9.4-1ubuntu1
ii  libgcc1     1:5.2.1-22ubuntu2
ii  libstdc++6  5.2.1-22ubuntu2

disorderfs recommends no packages.

disorderfs suggests no packages.

-- no debconf information

Reproducible-builds mailing list

Reply via email to