On 2017-09-18, Vagrant Cascadian wrote:
> On 2017-09-18, Russ Allbery wrote:
>> Daniel Kahn Gillmor writes:
>>> On Sun 2017-09-17 16:26:25 -0700, Russ Allbery wrote:
>>> Does everything in policy need to be rigorously testable? or is it ok
>>> to have Policy state the
Daniel Kahn Gillmor writes:
> On Sun 2017-09-17 16:26:25 -0700, Russ Allbery wrote:
>> I personally lean towards 2, which is consistent with what's in Policy
>> right now, but I can see definite merits in 3. I believe the
>> reproducible builds project is currently sort
Package: libfile-stripnondeterminism-perl
Version: 0.038-1
Severity: wishlist
Since 0.030 strip-nd prints a log when fixing a file, like
| dh_strip_nondeterminism
|Using 1505769410 as canonical time
|Normalizing debian/libtse3-dev/usr/lib/x86_64-linux-gnu/libtse3.a
I'd find it handy
Hi all,
This week's blog post draft is now available for review:
https://reproducible.alioth.debian.org/blog/drafts/125/
Feel free to commit fixes directly to drafts/125.mdwn in
https://anonscm.debian.org/git/reproducible/blog.git/
I'll wait at least 24 hours from the time of this email for
On 2017-09-18, Axel Beckert wrote:
> Control: retitle -1 zsh: FTBFS with noatime mounts (e.g. on reproducible
> builds armhf nodes)
...
> We still see this issue with reproducible builds on armhf in unstable as
> well as stretch:
>