From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: 57304@debbugs.gnu.org
Subject: [bug#57304] Fix mm-common reproduciblility issues
Date: Tue, 30 Aug 2022 22:34:33 +0200 [thread overview]
Message-ID: <87czcheahy.fsf@gnu.org> (raw)
In-Reply-To: <874jy7k4p2.fsf@contorta> (Vagrant Cascadian's message of "Fri, 19 Aug 2022 19:51:37 -0700")
Hi,
Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
> The userid used during the build is embedded in a shipped tarball in the
> mm-common package. Some abbreviated diffoscope output from guix
> challenge against builds from ci.guix.gnu.org and bordeax.guix.gnu.org:
Good catch.
> The attached patch fixes this by setting the user, group, uid and gid
> consistently.
>
> $ guix refresh --list-dependent mm-common
> Building the following 1138 packages would ensure 2236 dependent
> packages are rebuilt: ...
>
> Looks like it will have to wait for core-updates at least...
Yeah, let’s apply it on ‘core-updates’.
> From 4b359c9bbc918e6dcf1cab1141a9651d6d7bf271 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagrant@reproducible-builds.org>
> Date: Fri, 19 Aug 2022 19:32:08 -0700
> Subject: [PATCH] gnu: mm-common: Build reproducibly.
>
> * gnu/packages/patches/mm-common-consistent-user-and-group-in-tarball.patch:
> New file.
> * gnu/local.mk (dist_patch_DATA): Add patch.
> * gnu/packages/gnome.scm (mm-common)[source]: Add patch.
[...]
> + %D%/packages/patches/mm-common-consistent-user-and-group-in-tarball.patch \
I’d suggest a shorter name to appease ‘tar’, say
‘mm-common-reproducible-tarball.patch’.
Otherwise LGTM, thanks!
Ludo’.
next prev parent reply other threads:[~2022-08-30 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 2:51 [bug#57304] Fix mm-common reproduciblility issues Vagrant Cascadian
2022-08-30 20:34 ` Ludovic Courtès [this message]
2022-08-31 0:46 ` bug#57304: " Vagrant Cascadian
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=87czcheahy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57304@debbugs.gnu.org \
--cc=vagrant@reproducible-builds.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).