From: Eric Bavier <ericbavier@centurylink.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30469@debbugs.gnu.org
Subject: [bug#30469] [PATCH 0/1] Require Guile >= 2.0.14
Date: Sat, 24 Feb 2018 08:30:32 -0600 [thread overview]
Message-ID: <20180224083032.4f5f1e36@centurylink.net> (raw)
In-Reply-To: <20180215152627.4695-1-ludo@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On Thu, 15 Feb 2018 16:26:27 +0100
Ludovic Courtès <ludo@gnu.org> wrote:
> Hello Guix,
>
> This patch is to require Guile >= 2.0.14, released one year ago, instead
> of 2.0.9, released in 2013.
>
> For the record, here’s the distro status:
>
> • Debian unstable has 2.2:
> <https://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=guile-2.2>.
>
> • Older Debian versions have 2.0.13 (not .14):
> <https://packages.debian.org/search?keywords=guile-2.0>.
How much of this patch would change if it were to instead support
2.0.13? Is cutting off users of Debian stable a good idea?
>
> • Parabola, Gentoo, Homebrew, openSUSE, Fedora 26+ have 2.0.14 and/or
> 2.2: <https://repology.org/metapackage/guile/versions>.
>
> I’d like to have this change in place for the next Guix release, 0.14.1
> I presume.
>
> I’d also like it to be the last release that support Guile 2.0.
Same question.
`~Eric
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-24 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 15:26 [bug#30469] [PATCH 0/1] Require Guile >= 2.0.14 Ludovic Courtès
2018-02-15 15:29 ` [bug#30469] [PATCH 1/1] build: " Ludovic Courtès
2018-02-24 14:30 ` Eric Bavier [this message]
2018-02-24 22:41 ` [bug#30469] [PATCH 0/1] " Ludovic Courtès
2018-02-25 11:53 ` Jonathan Brielmaier
2018-02-27 17:23 ` Ludovic Courtès
2018-02-26 0:59 ` Eric Bavier
2018-02-26 18:49 ` bug#30469: " 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=20180224083032.4f5f1e36@centurylink.net \
--to=ericbavier@centurylink.net \
--cc=30469@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.