From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54176)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gOmLD-00039e-Am
	for guix-patches@gnu.org; Mon, 19 Nov 2018 11:24:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gOmLC-0004QO-EK
	for guix-patches@gnu.org; Mon, 19 Nov 2018 11:24:03 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:56859)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gOmLC-0004QE-B1
	for guix-patches@gnu.org; Mon, 19 Nov 2018 11:24:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gOmLC-0007ky-1w
	for guix-patches@gnu.org; Mon, 19 Nov 2018 11:24:02 -0500
Subject: [bug#33426] [PATCH] gnu: python-kivy-next: Fix build.
Resent-Message-ID: <handler.33426.B33426.154264459229758@debbugs.gnu.org>
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
References: <20181119004303.3fd5e3f4@riseup.net> <87muq51lx5.fsf@gnu.org>
	<20181119091612.5780f5fc@riseup.net>
Date: Mon, 19 Nov 2018 17:23:02 +0100
In-Reply-To: <20181119091612.5780f5fc@riseup.net> (Jovany Leandro G. C.'s
	message of "Mon, 19 Nov 2018 09:16:12 -0500")
Message-ID: <87in0tyr2x.fsf@gnu.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-patches/>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
	<mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: "Jovany Leandro G.C" <bit4bit@riseup.net>
Cc: 33426@debbugs.gnu.org

Hello,

(Re-adding Cc:.)

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

> El Mon, 19 Nov 2018 10:00:54 +0100
> ludo@gnu.org (Ludovic Court=C3=A8s) escribi=C3=B3:

[...]

>> However, since =E2=80=98python-kivy-next=E2=80=99 is a Git snapshot anyw=
ay, what about
>> updating the commit that is used instead of applying a patch?
>>=20
>> Thanks,
>> Ludo=E2=80=99.
>
> Hello,
>
> i not found a commit tagged in version 1.9.1,
>
> this pull https://github.com/kivy/kivy/pull/5459,
> was in 2017 between version >1.9.1 and <1.10.0 and tag 1.9.1 was 2016,
> which is the best route?

Are you saying the patch you=E2=80=99re interested in was never integrated =
in
the official repo?

Ludo=E2=80=99.