From: "Gábor Boskovits" <boskovits@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 30097@debbugs.gnu.org
Subject: bug#30097: [core-updates] nspr 4.17 not reproducible
Date: Sun, 14 Jan 2018 21:24:17 +0100 [thread overview]
Message-ID: <CAE4v=ph17uRRtC-SmQsqTOb-VXJf6XLARnJk+wPXU-KB3p8LpQ@mail.gmail.com> (raw)
In-Reply-To: <87a7xgdxs9.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
2018-01-14 20:51 GMT+01:00 Marius Bakke <mbakke@fastmail.com>:
> Gábor Boskovits <boskovits@gmail.com> writes:
>
> > 2018-01-14 19:28 GMT+01:00 Marius Bakke <mbakke@fastmail.com>:
> >
> >> Gábor Boskovits <boskovits@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.
[-- Attachment #2: Type: text/html, Size: 1843 bytes --]
next prev parent reply other threads:[~2018-01-14 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 16:23 bug#30097: [core-updates] nspr 4.17 not reproducible Gábor Boskovits
2018-01-13 21:07 ` Ludovic Courtès
2018-01-14 18:28 ` Marius Bakke
2018-01-14 19:35 ` Gábor Boskovits
2018-01-14 19:51 ` Marius Bakke
2018-01-14 20:24 ` Gábor Boskovits [this message]
2018-01-16 16:20 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=ph17uRRtC-SmQsqTOb-VXJf6XLARnJk+wPXU-KB3p8LpQ@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=30097@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).