From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: 71024@debbugs.gnu.org
Subject: [bug#71024] Update diffoscope to 267 (with xz bonus update)
Date: Mon, 20 May 2024 22:48:45 -0400 [thread overview]
Message-ID: <87y183ubg2.fsf_-_@gmail.com> (raw)
In-Reply-To: <87le47rikz.fsf@wireframe> (Vagrant Cascadian's message of "Fri, 17 May 2024 18:53:48 -0700")
Hi,
Vagrant Cascadian <vagrant@reproducible-builds.org> writes:
> From a889aaf43ee1d3cc9669bcc80888450bbd3d9ca1 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagrant@reproducible-builds.org>
> Date: Fri, 17 May 2024 17:18:39 -0700
> Subject: [PATCH 2/2] gnu: diffoscope: Update to 267.
>
> * gnu/packages/diffoscope.scm (diffoscope): Update to 267.
> [native-inputs]: Use xz-5.4.
Reviewed-by: Maxim Cournoyer <maxim.cournoyer@gmail>
LGTM, but I think it's safe to use xz 5.6.1 *from git*, unless I've
missed recent development on the xz backdoor story.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-05-21 2:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 1:46 [bug#71024] Update diffoscope to 267 (with xz bonus update) Vagrant Cascadian
2024-05-18 1:53 ` Vagrant Cascadian
2024-05-18 1:53 ` Vagrant Cascadian
2024-05-18 2:01 ` Vagrant Cascadian
2024-05-21 2:48 ` Maxim Cournoyer [this message]
2024-05-18 3:50 ` [bug#71024] [PATCH 1/2] gnu: Add xz-5.4 variant vagrant
2024-05-18 3:50 ` [bug#71024] [PATCH 2/2] gnu: diffoscope: Update to 267 vagrant
2024-05-21 2:46 ` [bug#71024] Update diffoscope to 267 (with xz bonus update) Maxim Cournoyer
2024-05-21 6:01 ` Vagrant Cascadian
2024-05-21 19:20 ` Vagrant Cascadian
2024-05-22 0:06 ` Maxim Cournoyer
2024-05-24 14:41 ` [bug#71024] Update diffoscope to 268 Vagrant Cascadian
2024-05-26 3:05 ` Maxim Cournoyer
2024-05-28 22:33 ` Vagrant Cascadian
2024-05-30 1:02 ` Maxim Cournoyer
2024-05-31 17:30 ` bug#71024: " 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=87y183ubg2.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=71024@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).