From: Michael Ford <fanquake@gmail.com>
To: Janneke Nieuwenhuizen <janneke@gnu.org>
Cc: 65179@debbugs.gnu.org
Subject: [bug#65179] [PATCH] gnu: mingw: Update reproducibility patch
Date: Mon, 21 Aug 2023 09:54:16 +0100 [thread overview]
Message-ID: <CAFyhPjUwmJMZJ-thmDSHw+mcP=ChudyfqaK7Y7FGgx+1t_3A_g@mail.gmail.com> (raw)
In-Reply-To: <87350flbdi.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]
> Would you like to look into that?
Sure, I'll see if I can track down the issue.
On Sat, 19 Aug 2023 at 08:50, Janneke Nieuwenhuizen <janneke@gnu.org> wrote:
> Michael Ford writes:
>
> Hi!
>
> > From c8e8b7dacfe86147226a687acd495e59826368d7 Mon Sep 17 00:00:00 2001
> > From: fanquake <fanquake@gmail.com>
> > Date: Wed, 9 Aug 2023 14:42:38 +0200
> > Subject: [PATCH] gnu: mingw: Update reproducibility patch.
> > * gnu/packages/patches/mingw-w64-reproducible-gendef.patch: Update from
> > upstream.
> > ---
> > .../patches/mingw-w64-reproducible-gendef.patch | 16 +++++++++++++---
> > 1 file changed, 13 insertions(+), 3 deletions(-)
>
> Applied, thanks!
>
> However...even with this patch MinGW does not build reproducibly, e.g.
>
> --8<---------------cut here---------------start------------->8---
> diffoscope
> /gnu/store/ra40ckd09sapzlh7mib2qmwkbjamgcxb-mingw-w64-x86_64-11.0.1/lib/libntoc.a
> /tmp/ra40ckd09sapzlh7mib2qmwkbjamgcxb-mingw-w64-x86_64-11.0.1/lib/libntoc.a
> ---
> /gnu/store/ra40ckd09sapzlh7mib2qmwkbjamgcxb-mingw-w64-x86_64-11.0.1/lib/libntoc.a
> +++
> /tmp/ra40ckd09sapzlh7mib2qmwkbjamgcxb-mingw-w64-x86_64-11.0.1/lib/libntoc.a
> ├── file list
> │ @@ -1,4 +1,4 @@
> │ ----------- 0 0 0 100 2023-08-18 13:26:59.000000 /
> │ --rw-r--r-- 0 999 30000 586 2023-08-18 13:26:59.000000
> libntoct.o
> │ --rw-r--r-- 0 999 30000 648 2023-08-18 13:26:59.000000
> libntoch.o
> │ --rw-r--r-- 0 999 30000 624 2023-08-18 13:26:59.000000
> libntocs00000.o
> │ +---------- 0 0 0 100 2023-08-19 06:04:15.000000 /
> │ +-rw-r--r-- 0 999 30000 586 2023-08-19 06:04:15.000000
> libntoct.o
> │ +-rw-r--r-- 0 999 30000 648 2023-08-19 06:04:15.000000
> libntoch.o
> │ +-rw-r--r-- 0 999 30000 624 2023-08-19 06:04:15.000000
> libntocs00000.o
> --8<---------------cut here---------------end--------------->8---
>
> Would you like to look into that?
>
> Greetings,
> Janneke
>
> --
> Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond
> https://LilyPond.org
> Freelance IT https://www.JoyOfSource.com | Avatar®
> https://AvatarAcademy.com
>
[-- Attachment #2: Type: text/html, Size: 3105 bytes --]
next prev parent reply other threads:[~2023-08-21 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:09 [bug#65179] [PATCH] gnu: mingw: Update reproducibility patch Michael Ford
2023-08-19 7:50 ` Janneke Nieuwenhuizen
2023-08-21 8:54 ` Michael Ford [this message]
2023-10-30 13:08 ` bug#65179: " Christopher Baines
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='CAFyhPjUwmJMZJ-thmDSHw+mcP=ChudyfqaK7Y7FGgx+1t_3A_g@mail.gmail.com' \
--to=fanquake@gmail.com \
--cc=65179@debbugs.gnu.org \
--cc=janneke@gnu.org \
/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).