[Reproducible-builds] Remaining reprotest variations

[Ceridwen]

On Wed, 2016-07-27 at 13:48 -0700, Vagrant Cascadian wrote:
> On 2016-07-27, Ceridwen wrote:
> > 
> > For most of the variations I've done so far, I've been either
> > depending on external utilities or had POSIX-compliant ways to
> > execute
> > them.  The rest of the variations pose more problems.
> ...
> > 
> > 5. kernel: While `uname` is in the POSIX standard, mechanisms for
> > altering its output aren't.  `setarch`, what prebuilder uses and
> > what
> > reprotest uses at the moment, is Linux-specific.
> >     - What methods of changing `uname` will work on other OSes?
> Using "setarch uname26" on non-x86 architectures may cause issues
> with
> recent versions of glibc, too:
> 
>   https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-
> of-Mon-20151130/004040.html
>   https://bugs.debian.org/806911
>   https://sourceware.org/ml/libc-alpha/2015-12/msg00028.html
> 
> So it certainly should be optional, at best.
> 

All the variations can be disabled at the command line or with a config
file, so anyone using reprotest can disable `kernel` to work around
this kind of bug.

Ceridwen