GNU bug report logs - #30097
[core-updates] nspr 4.17 not reproducible

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#30097: closed ([core-updates] nspr 4.17 not reproducible)
Date: Tue, 16 Jan 2018 16:21:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 16 Jan 2018 17:20:35 +0100
with message-id <87inc1ai7g.fsf <at> fastmail.com>
and subject line Re: bug#30097: [core-updates] nspr 4.17 not reproducible
has caused the debbugs.gnu.org bug report #30097,
regarding [core-updates] nspr 4.17 not reproducible
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
30097: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30097
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Gábor Boskovits <boskovits <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: [core-updates] nspr 4.17 not reproducible
Date: Sat, 13 Jan 2018 17:23:29 +0100

[Message part 3 (text/plain, inline)]

nspr 4.17 is not reproducible.
Diffoscope output attached.

[Message part 4 (text/html, inline)]

[nspr-diffoscope (application/octet-stream, attachment)]

[Message part 6 (message/rfc822, inline)]

From: Marius Bakke <mbakke <at> fastmail.com>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 30097-done <at> debbugs.gnu.org
Subject: Re: bug#30097: [core-updates] nspr 4.17 not reproducible
Date: Tue, 16 Jan 2018 17:20:35 +0100

[Message part 7 (text/plain, inline)]

Gábor Boskovits <boskovits <at> gmail.com> writes:

> 2018-01-14 20:51 GMT+01:00 Marius Bakke <mbakke <at> fastmail.com>:
>
>> Gábor Boskovits <boskovits <at> gmail.com> writes:
>>
>> > 2018-01-14 19:28 GMT+01:00 Marius Bakke <mbakke <at> fastmail.com>:
>> >
>> >> Gábor Boskovits <boskovits <at> gmail.com> writes:
>> >>
>> >> > nspr 4.17 is not reproducible.
>> >> > Diffoscope output attached.
>> >>
>> >> Thanks for the report!
>> >>
>> >> The attached patch should solve it.  Since there are quite a few
>> >> dependent packages, I'd like to push this to a new 'staging' branch that
>> >> will be started shortly after the core-updates merge.  WDYT?
>> >>
>> >> Yes, it should go to a branch.
>> >
>> > I also don't know if this fixes the difference also, where an additional
>> ;
>> > is present...
>> > Could you check this, or should I run a test with the patch?
>> > It seems like a 2 byte difference.
>>
>> It passes `guix build --rounds=2`, so I'm not sure what was up with that
>> ";".
>>
>
> Most probably it is some kind of checksum which includes the timestamp.
> If it passes "guix build --rounds=2" it should be fine.
> Thanks for the clarification.

I pushed this to a new 'staging' branch based off core-updates.

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.