From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Efraim Flashner" <efraim@flashner.co.il>
Cc: 45299@debbugs.gnu.org
Subject: [bug#45299] [PATCH] maint: Require Guile >= 2.2.6.
Date: Fri, 18 Dec 2020 13:06:46 -0800 [thread overview]
Message-ID: <87im8y6cyh.fsf@yucca> (raw)
In-Reply-To: <87wnxfb210.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On 2020-12-18, Ludovic Courtès wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
>> Debian 10 (the current release) has guile-2.2.4
> Hmm OK. Should it hold us back, though?
Debian 10 doesn't have many of the guile-* build dependencies, so I
would not recommend the current Debian stable release block bumping the
minimum guile 2.2 version for guix...
> 2.2.6 was released in June 2019.
Debian bullseye (the testing branch) currently has guile-2.2 at 2.2.7:
https://tracker.debian.org/pkg/guile-2.2
Debian bullseye is likely to become Debian stable mid-2021, starting to
freeze in early 2021.
It should have all the dependencies for building guix against guile-2.2,
and *almost* all for building guix against guile-3.0...
> Also, I expect most users to either use Vagrant’s brand new ‘guix’
> package or to use our binary tarball.
The guix package may not make it out of Debian experimental any time
soon... unless I switch it to use guile-2.2 (and track down the
corresponding test suite failures) or the guile-gnutls test suite issues
with guile-3.0 get fixed.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-12-18 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:33 [bug#45299] [PATCH] maint: Require Guile >= 2.2.6 Ludovic Courtès
2020-12-17 20:16 ` Efraim Flashner
2020-12-18 14:51 ` Ludovic Courtès
2020-12-18 21:06 ` Vagrant Cascadian [this message]
2020-12-19 23:04 ` bug#45299: " 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=87im8y6cyh.fsf@yucca \
--to=vagrant@debian.org \
--cc=45299@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--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.