all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Jovany Leandro G.C" <bit4bit@riseup.net>
Cc: 33426@debbugs.gnu.org
Subject: [bug#33426] [PATCH] gnu: python-kivy-next: Fix build.
Date: Mon, 19 Nov 2018 21:12:04 +0100	[thread overview]
Message-ID: <8736rwygh7.fsf@gnu.org> (raw)
In-Reply-To: <20181119121233.41667d60@riseup.net> (Jovany Leandro G. C.'s message of "Mon, 19 Nov 2018 12:12:33 -0500")

¡Hola!

(Re-re-adding Cc:.)

"Jovany Leandro G.C" <bit4bit@riseup.net> skribis:

> El Mon, 19 Nov 2018 17:23:02 +0100
> ludo@gnu.org (Ludovic Courtès) escribió:

[...]

>> Are you saying the patch you’re interested in was never integrated in
>> the official repo?
>> 
>> Ludo’.
>
> in the master branch, for version 1.10.0.
>
>
> question: python-kivy 1.10.1 is mantanied, 1.9.1 it's old and
> unmantained, ¿why python-kivy-next, we can delete it?

‘python-kivy-next’ was added in 6eb7af2a43d94d6404a9b70c8beff1a535b50607
in 2016.  Probably the reason to add it back then no longer makes any
sense.

So yes, I think we can simply delete it.

Sounds good?

Thank you,
Ludo’.

  parent reply	other threads:[~2018-11-19 20:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19  5:43 [bug#33426] [PATCH] gnu: python-kivy-next: Fix build Jovany Leandro G.C
2018-11-19  9:00 ` Ludovic Courtès
     [not found]   ` <20181119091612.5780f5fc@riseup.net>
2018-11-19 16:23     ` Ludovic Courtès
     [not found]       ` <20181119121233.41667d60@riseup.net>
2018-11-19 20:12         ` Ludovic Courtès [this message]
2018-11-27 11:13           ` bug#33426: " 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=8736rwygh7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33426@debbugs.gnu.org \
    --cc=bit4bit@riseup.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 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.