[Reproducible-builds] Second build on failures

[Vagrant Cascadian]

On 2015-12-21, Holger Levsen wrote:
> On Donnerstag, 3. Dezember 2015, Vagrant Cascadian wrote:
>> Filed against libc-bin:
>>   https://bugs.debian.org/806911
>> Aurelian Jarno filed a patch upstream to support using the uname26
>> personality:
>>   https://sourceware.org/ml/libc-alpha/2015-12/msg00028.html
>
> ok, cool, thanks!
>  
>> So it might get fixed in future versions ...although we'd need to run
>> From within sid (or backport util-linux) to run on jenkins any time
>> soon...
>
> yeah :/
>  
>> For now, relying on the fact that there are different actual kernels on
>> various builds (4.x vs. 3.x) will hopefully be good enough to detect the
>> issue that using "linux64 --uname-2.6" was trying to solve.
>
> yeah. what I don't like about this is that it forces us to do that. I liked 
> the flexibility using --uname-2.6 gave us…

The impression I got was the patch implementation was rejected upstream,
but in theory a better patch could be written. Aurelian wasn't planning
on working on it.

So if it's wanted for reproducible builds purposes, probably need to
come up with a patch that would get accepted upstream...

live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20151221/6065525f/attachment.sig>