On Sat, Feb 18, 2017 at 06:12:44PM +0100, Christian Seiler wrote:
> Ah, now I understand the output. I initially thought rbuild
> was just the first build, and didn't give it too much thought
> since I didn't expect diffoscope to be called there.
rbuild is the first build + some output from the
On 02/18/2017 05:54 PM, Mattia Rizzolo wrote:
> On Sat, Feb 18, 2017 at 05:50:25PM +0100, Christian Seiler wrote:
>> Can I find that piece of information somewhere on that page?
>
> Yes, at the bottom of the rbuild log.
Ah, now I understand the output. I initially thought rbuild
was just the
On Sat, Feb 18, 2017 at 05:50:25PM +0100, Christian Seiler wrote:
> On 02/18/2017 05:42 PM, Mattia Rizzolo wrote:
> > On Sat, Feb 18, 2017 at 04:55:27PM +0100, Christian Seiler wrote:
> >> but where did the link to the diffoscope output go on the
> >> website?
> > Where it is always been.
>
> And
On 02/18/2017 05:42 PM, Mattia Rizzolo wrote:
> On Sat, Feb 18, 2017 at 04:55:27PM +0100, Christian Seiler wrote:
>> but where did the link to the diffoscope output go on the
>> website?
> Where it is always been.
And I assume that because diffoscope failed there's no link there
and that's why I
On Sat, Feb 18, 2017 at 04:55:27PM +0100, Christian Seiler wrote:
> maybe this is a case of me overlooking the obvious, but where did
> the link to the diffoscope output go on the website?
Where it is always been.
> targetcli-fb is unreproducible in testing right now (I just
> noticed), and I
Dear reproducible-builds team,
maybe this is a case of me overlooking the obvious, but where did
the link to the diffoscope output go on the website?
targetcli-fb is unreproducible in testing right now (I just
noticed), and I can find the build logs + the diff of the build
logs, but I can't seem
