From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 54440@debbugs.gnu.org
Subject: [bug#54440] Updates for genext2fs and genimage
Date: Sat, 19 Mar 2022 11:49:50 +0100 [thread overview]
Message-ID: <87cziinrn5.fsf@gnu.org> (raw)
In-Reply-To: <87sfrgt7ou.fsf@contorta> (Vagrant Cascadian's message of "Thu, 17 Mar 2022 17:39:45 -0700")
Hello Vagrant,
Vagrant Cascadian <vagrant@debian.org> skribis:
> I have updates for genext2fs and genimage!
>
> Newer versions of the genext2fs tool have support for things like
> SOURCE_DATE_EPOCH, and Guix seems keen on reproducible builds, so Guix
> may as well have the latest and greatest genext2fs!
Yup, sounds like an interesting option! I’m not sure yet it can be used
as a drop-in replacement in (gnu build images), but we’ll see.
> Updating genext2fs triggered test suite failures in genimage, which I
> also noticed was a slightly out of date... so updated that too!
>
> Will submit the patches once I get a bug number... (that's really how
> this is supposed to be done still?)
Yes. :-)
The patches LGTM, thank you!
Ludo’.
next prev parent reply other threads:[~2022-03-19 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 0:39 [bug#54440] Updates for genext2fs and genimage Vagrant Cascadian
2022-03-18 1:11 ` [bug#54440] [PATCH 1/2] gnu: genext2fs: Update to 1.5.0 Vagrant Cascadian
2022-03-18 1:12 ` [bug#54440] [PATCH 2/2] gnu: genimage: Update to 15 Vagrant Cascadian
2022-03-19 10:49 ` Ludovic Courtès [this message]
2022-04-11 22:15 ` bug#54440: Updates for genext2fs and genimage 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=87cziinrn5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54440@debbugs.gnu.org \
--cc=vagrant@debian.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).