From: "Ludovic Courtès" <ludo@gnu.org>
To: 75137@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Christopher Baines" <guix@cbaines.net>,
"Josselin Poiret" <dev@jpoiret.xyz>,
"Ludovic Courtès" <ludo@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>,
"Simon Tournier" <zimon.toutoune@gmail.com>,
"Tobias Geerinckx-Rice" <me@tobias.gr>
Subject: [bug#75137] [PATCH 0/4] 'package-with-upstream-version' can preserve archive type
Date: Fri, 27 Dec 2024 11:55:23 +0100 [thread overview]
Message-ID: <cover.1735296761.git.ludo@gnu.org> (raw)
Hello,
This fixes a discrepancy observed in:
https://ci.guix.gnu.org/jobset/security-updates
For ‘xorg-server’, ‘package-with-upstream-version’ would pick the
tar.gz file, whereas running ‘guix refresh -u xorg-server’ would
pick the tar.xz file since the package definition already uses
a tar.xz file.
Ludo’.
Ludovic Courtès (4):
upstream: Switch to SRFI-71.
upstream: Extract ‘preferred-upstream-source-url’.
upstream: Define ‘preferred-upstream-source’.
transformations: ‘package-with-upstream-version’ can preserve archive
type.
guix/transformations.scm | 44 ++++++++++++++++++--------------
guix/upstream.scm | 55 +++++++++++++++++++++++++---------------
tests/upstream.scm | 21 ++++++++++++++-
3 files changed, 80 insertions(+), 40 deletions(-)
base-commit: e4bdd464ebb49f4e698e5105f70b29688fff9475
--
2.46.0
next reply other threads:[~2024-12-27 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 10:55 Ludovic Courtès [this message]
2024-12-27 10:56 ` [bug#75137] [PATCH 1/4] upstream: Switch to SRFI-71 Ludovic Courtès
2024-12-27 10:56 ` [bug#75137] [PATCH 2/4] upstream: Extract ‘preferred-upstream-source-url’ Ludovic Courtès
2024-12-27 10:56 ` [bug#75137] [PATCH 3/4] upstream: Define ‘preferred-upstream-source’ Ludovic Courtès
2024-12-27 10:56 ` [bug#75137] [PATCH 4/4] transformations: ‘package-with-upstream-version’ can preserve archive type Ludovic Courtès
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=cover.1735296761.git.ludo@gnu.org \
--to=ludo@gnu.org \
--cc=75137@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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.