unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Eric Bavier <ericbavier@centurylink.net>
Cc: 30469-done@debbugs.gnu.org
Subject: bug#30469: [PATCH 0/1] Require Guile >= 2.0.14
Date: Mon, 26 Feb 2018 19:49:38 +0100	[thread overview]
Message-ID: <87fu5ntwl9.fsf@gnu.org> (raw)
In-Reply-To: <20180225151831.1b413f51@centurylink.net> (Eric Bavier's message of "Sun, 25 Feb 2018 18:59:24 -0600")

Eric Bavier <ericbavier@centurylink.net> skribis:

> On Sat, 24 Feb 2018 23:41:24 +0100
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Hello,
>> 
>> Eric Bavier <ericbavier@centurylink.net> skribis:
>> 
>> > 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&section=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?  
>> 
>> I’ll double-check but I think the patch remains valid if we require
>> 2.0.13.
>> 
>> If it works I’ll commit that next week.
>
> Cool.

Pushed as 1d84d7bf6052c0c80bd212d4524876576e9817d4.

Thanks for your feedback!

Ludo’.

      reply	other threads:[~2018-02-26 18:50 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 ` [bug#30469] [PATCH 0/1] " Eric Bavier
2018-02-24 22:41   ` 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       ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fu5ntwl9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30469-done@debbugs.gnu.org \
    --cc=ericbavier@centurylink.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).