From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel@gnu.org
Subject: Re: Guile-Gcrypt 0.4.0 released
Date: Sat, 03 Dec 2022 14:45:40 -0800 [thread overview]
Message-ID: <877cz8p0mj.fsf@contorta> (raw)
In-Reply-To: <87r0xjyywc.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On 2022-12-01, Ludovic Courtès wrote:
> I’m pleased to announce Guile-Gcrypt version 0.4.0:
>
> git clone https://notabug.org/cwebber/guile-gcrypt.git
> cd guile-gcrypt
> git checkout v0.4.0 # or 425554d4327eeeb60c39e3d4a1b7bc5e36b63953
> git tag -v v0.4.0
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
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?
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)?
I know the guix thing would be to package all the relevent versions, but
that is a bit trickier in Debian! :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-12-03 22:46 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 [this message]
2022-12-05 14:58 ` Ludovic Courtès
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=877cz8p0mj.fsf@contorta \
--to=vagrant@debian.org \
--cc=guix-devel@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.