From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 54440-done@debbugs.gnu.org
Subject: bug#54440: Updates for genext2fs and genimage
Date: Mon, 11 Apr 2022 15:15:04 -0700 [thread overview]
Message-ID: <87v8vfp8rb.fsf@contorta> (raw)
In-Reply-To: <87cziinrn5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On 2022-03-19, Ludovic Courtès wrote:
> 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.
I have seen instructions for adding features using tune2fs after the
fact to make it ext3 or ext4 ... or other arbitrary features (though not
all can be) and who knows how that will affect the reproducibility of
the image!
>> Updating genext2fs triggered test suite failures in genimage, which I
>> also noticed was a slightly out of date... so updated that too!
...
> The patches LGTM, thank you!
Pushed as:
ba1ce250c8d2d0d3c215e06d722f8d561cbe095f gnu: genimage: Update to 15.
8aae96b44c2e84f31574200aa71c6ee4979b1620 gnu: genext2fs: Update to 1.5.0.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2022-04-11 22:17 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 ` [bug#54440] Updates for genext2fs and genimage Ludovic Courtès
2022-04-11 22:15 ` Vagrant Cascadian [this message]
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=87v8vfp8rb.fsf@contorta \
--to=vagrant@debian.org \
--cc=54440-done@debbugs.gnu.org \
--cc=ludo@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).