From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 71024@debbugs.gnu.org
Subject: [bug#71024] Update diffoscope to 267 (with xz bonus update)
Date: Fri, 17 May 2024 18:46:53 -0700 [thread overview]
Message-ID: <87r0dzriwi.fsf@wireframe> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
The upcoming patches update diffoscope to 267, which requires a newer
version of xz to pass the test suites (No, no, not the *evil* versions,
just the same version that is in core-updates, 5.4.5! (although that
version has shadows cast on it too due to involvement of a certain
infamous internet identity, caveat emptor)).
I made a versioned xz variant to avoid a world rebuild so we can update
diffoscope before updating core-updates, hopefully I did it mostly
right... :)
Uhhh... so yeah, send in the clowns... er, patches!
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2024-05-18 1:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 1:46 Vagrant Cascadian [this message]
2024-05-18 1:53 ` [bug#71024] Update diffoscope to 267 (with xz bonus update) Vagrant Cascadian
2024-05-18 1:53 ` Vagrant Cascadian
2024-05-18 2:01 ` Vagrant Cascadian
2024-05-21 2:48 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0dzriwi.fsf@wireframe \
--to=vagrant@reproducible-builds.org \
--cc=71024@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.