Re: Please review the draft for week 166's blog post

2018-07-02 Thread Chris Lamb
Chris Lamb wrote: > Please review the draft for week 166's blog post [..] This has now been published; many thanks to all who contributed! Please share the following URL: https://reproducible-builds.org/blog/posts/166/ Alternatively, if you are into that kind of thing, please consider retwee

Bug#902709: diffoscope: test failures everywhere

2018-07-02 Thread Mattia Rizzolo
On Mon, Jul 02, 2018 at 08:43:04PM +0100, Chris Lamb wrote: > > This particular error is fixed by d6f1d04 (and I did include the bug > > number in the commit). > > Are we talking about the right commit? I only ask because I do not see > the bug number in the commit... :) > >https://salsa.debi

Bug#902709: diffoscope: test failures everywhere

2018-07-02 Thread Mattia Rizzolo
Control: owner -1 ! Control: tag -1 pending On Mon, Jul 02, 2018 at 06:52:15PM +0100, Chris Lamb wrote: > Are we still seeing this on current master? (As-of writing, that is > a6b4effc). I ask because, as mentioned previously, I cannot reproduce > this. :) This particular error is fixed by d6f1d

Processed: Re: Bug#902709: diffoscope: test failures everywhere

2018-07-02 Thread Debian Bug Tracking System
Processing control commands: > owner -1 ! Bug #902709 [diffoscope] diffoscope: FTBFS: /usr/lib/python3.6/tempfile.py:509: FileNotFoundError Owner recorded as Mattia Rizzolo . > tag -1 pending Bug #902709 [diffoscope] diffoscope: FTBFS: /usr/lib/python3.6/tempfile.py:509: FileNotFoundError Added

Bug#902709: diffoscope: test failures everywhere

2018-07-02 Thread Chris Lamb
Hi Mattia, > This particular error is fixed by d6f1d04 (and I did include the bug > number in the commit). Are we talking about the right commit? I only ask because I do not see the bug number in the commit... :) https://salsa.debian.org/reproducible-builds/diffoscope/commit/ d6f1d04b3dbc3f3

Bug#902709: diffoscope: test failures everywhere

2018-07-02 Thread Chris Lamb
Hi Mattia, > So, autopkgtest is failing […] > The ubuntu build also failed with a very similar error […] > And also the reproducible builds build FTBFS with the same errors. Are we still seeing this on current master? (As-of writing, that is a6b4effc). I ask because, as mentioned previously, I c