Package: disorderfs
Version: 0.4.2-1
Severity: normal
User: reproducible-builds@lists.alioth.debian.org
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
Source: diffoscope
Version: 54
Severity: minor
User: reproducible-builds@lists.alioth.debian.org
Dear Maintainer,
The --help text for diffoscope gives no indication that it operates on
directories as well as files:
usage: diffoscope [-h] [--version] [--list-tools [LIST_TOOLS]] [--debug]
o other build environments, this will
> > require double-dispatch, because the code that needs to be executed
> > will depend on both the variation to be tested and the environment
> > being built on.
"Double-dispatch" in this case just means that there are two parameters
#x27;, following the prebuilder script in
this. (Neither prebuilder nor reprotest guarantee that those
directories don't exist.) As Lunar said, one possible alternate fix
for that specific bug is to create two different temporary directories
and set $HOME to those directories instead. Is th
root privileges, but should it be tested without
virtualization?
* Are there any other variations which shouldn't be tested in some of
the execution environments without full reversion capabilities?
Ceridwen
___
Reproducible-builds mailing list
Repr
ether reprotest has root on the given testbed, and what the
testbed's OS is. I haven't written documentation for it yet, but it's
straightforward-ish to write a new Python context manager for a
specific case.
I'm going to go ahead and implement the time variation and a flag for
the
