From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: Guile-Gcrypt 0.4.0 released
Date: Mon, 05 Dec 2022 15:58:17 +0100 [thread overview]
Message-ID: <87359trj7a.fsf@gnu.org> (raw)
In-Reply-To: <877cz8p0mj.fsf@contorta> (Vagrant Cascadian's message of "Sat, 03 Dec 2022 14:45:40 -0800")
Hi,
Vagrant Cascadian <vagrant@debian.org> skribis:
> FWIW, I updated guile-gcrypt to 0.4.0 in Debian experimental and updated
> to guix 1.4.0rc1 in Debian experimental using guile-gcrypt 0.4.0, and it
> seemed to go fine so far...
>
> https://buildd.debian.org/status/package.php?p=guile-gcrypt&suite=experimental
> https://buildd.debian.org/status/package.php?p=guix&suite=experimental
Yay, thanks!
> I'm guessing guile-gcrypt 0.4.0 will not land in the soon-to-be-released
> guix 1.4.0 once it is released, though?
No, but it doesn’t matter much because there are very few differences.
> Looking at the longer term, makes me wonder if I should build guix with
> guile-gcrypt 0.3.0 currently in Debian unstable & testing ... or if
> 0.4.0 is a small enough difference that it will probably be fine to
> build guix 1.4.0* against it (and eventually migrate it to debian
> unstable and eventually testing)?
Either way is fine.
> I know the guix thing would be to package all the relevent versions, but
> that is a bit trickier in Debian! :)
Heheh. :-)
Ludo’.
next prev parent reply other threads:[~2022-12-05 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 14:36 Guile-Gcrypt 0.4.0 released Ludovic Courtès
2022-12-03 22:45 ` Vagrant Cascadian
2022-12-05 14:58 ` Ludovic Courtès [this message]
2022-12-06 20:21 ` Jonathan Brielmaier
2022-12-08 16:05 ` 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=87359trj7a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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.