all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 74888@debbugs.gnu.org
Subject: [bug#74888] [PATCH 0/3] Fixes to the 'security-updates' and 'ungraft' manifests
Date: Wed, 18 Dec 2024 20:45:35 +0900	[thread overview]
Message-ID: <87y10dnrj4.fsf@gmail.com> (raw)
In-Reply-To: <cover.1734279715.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Sun, 15 Dec 2024 17:24:14 +0100")

Hi Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi!
>
> This fixes mistakes I made in these two manifests and that led them
> to compute derivations that differ from what you’d get by changing
> the code manually.
>
> There’s still one discrepancy, which is due to the use of
> ‘computed-origin-method’:
>
>   https://lists.gnu.org/archive/html/guix-devel/2024-12/msg00113.html
>
> Hopefully this will be addressed soon.
>
> Thanks,
> Ludo’.
>
> Ludovic Courtès (3):
>   packages: Add #:recursive? to ‘package-input-rewriting’.
>   etc: upgrade: Really compute joint upgrades.
>   etc: ungraft: Use ‘package-mapping’ directly.

I've proof-read carefully everything, but haven't tried it.

Reviewed-by: Maxim Cournoyer <maxim.cournoyer@gmail>

--
Thanks,
Maxim




  parent reply	other threads:[~2024-12-18 11:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15 16:24 [bug#74888] [PATCH 0/3] Fixes to the 'security-updates' and 'ungraft' manifests Ludovic Courtès
2024-12-15 16:25 ` [bug#74888] [PATCH 1/3] packages: Add #:recursive? to ‘package-input-rewriting’ Ludovic Courtès
2024-12-15 16:25 ` [bug#74888] [PATCH 2/3] etc: upgrade: Really compute joint upgrades Ludovic Courtès
2024-12-15 16:25 ` [bug#74888] [PATCH 3/3] etc: ungraft: Use ‘package-mapping’ directly Ludovic Courtès
2024-12-18 11:45 ` Maxim Cournoyer [this message]
2024-12-18 17:36   ` bug#74888: [PATCH 0/3] Fixes to the 'security-updates' and 'ungraft' manifests 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=87y10dnrj4.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=74888@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 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.