From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: Questions about packaging Date: Mon, 21 Oct 2019 11:34:44 +0200 Message-ID: References: <20191009095633.qlhnq2yvtp7dbrrf@rafflesia> <20191010024127.1da7c86d@scratchpost.org> <20191011074200.azkyt4mufjazbuj6@rafflesia> <20191012124116.6f842667@scratchpost.org> <20191014075154.glbillit5hu7p6vb@rafflesia> <87y2xix9cc.fsf@devup.no> <20191021092320.rirojs26u6vshivn@rafflesia> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000008cdfbd0595686519" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36227) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMU5c-00085v-15 for guix-devel@gnu.org; Mon, 21 Oct 2019 05:35:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMU5a-0006e8-QP for guix-devel@gnu.org; Mon, 21 Oct 2019 05:34:59 -0400 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]:42470) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iMU5a-0006dy-Jk for guix-devel@gnu.org; Mon, 21 Oct 2019 05:34:58 -0400 Received: by mail-ed1-x535.google.com with SMTP id s20so3478414edq.9 for ; Mon, 21 Oct 2019 02:34:57 -0700 (PDT) In-Reply-To: <20191021092320.rirojs26u6vshivn@rafflesia> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Tanguy Le Carrour Cc: Guix-devel --0000000000008cdfbd0595686519 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, Tanguy Le Carrour ezt =C3=ADrta (id=C5=91pont: 2019.= okt. 21., H=C3=A9t 11:24): > Hi Marius, > > > Le 10/18, Marius Bakke a =C3=A9crit : > > Tanguy Le Carrour writes: > > > In Guix, we have Pytest 4.4.2, but the latest release is 5.2.1. > > > In that case, would it make sense to define a new "versionned" public > > > variable for python-pytest? Would I create python-pytest5? Or would I > > > rename python-pytest to python-pytest4 and add python-pytest for Pyte= st > > > 5? In this later case, would I have to "fix" all the packages that we= re > > > using python-pytest?! > > > > Pytest has 4457 dependent packages and can thus only be changed on the > > 'core-updates' branch. So the recommended way is indeed to define a ne= w > > public 'python-pytest-5' variable, and add that as an input for the > > packages that require 5.x. > > OK=E2=80=A6 sounds like something I can do! > > > > On the next 'core-updates' cycle, Pytest 5 will then become the default= , > > and we will have to fix all packages that does not work with that > > version :-) > > I guess those broken packages will show up as "red" in Cuirass!? > Would they have to be fixed, or just told to use python-pytest-4? > > Is there a way to build those packages on my machine? What a > script to find and build all the packages dependent on pytest would look > like? > I mean, using LISP/Scheme/Guile, as I think I could come up with a > "manual" solution with `guix graph --type=3Dreverse-package`. > guix refresh -l should give you the minimum number of packages that ensures every dependent is rebuilt. > > > Regards, > > -- > Tanguy > > --0000000000008cdfbd0595686519 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

Tanguy Le Carrour <tanguy@bioneland.org> ezt =C3=ADrta (id=C5=91pont: 201= 9. okt. 21., H=C3=A9t 11:24):
Hi Ma= rius,


Le 10/18, Marius Bakke a =C3=A9crit :
> Tanguy Le Carrour <tanguy@bioneland.org> writes:
> > In Guix, we have Pytest 4.4.2, but the latest release is 5.2.1. > > In that case, would it make sense to define a new "versionne= d" public
> > variable for python-pytest? Would I=C2=A0create python-pytest5? O= r would I
> > rename python-pytest to python-pytest4 and add python-pytest for = Pytest
> > 5? In this later case, would I have to "fix" all the pa= ckages that were
> > using python-pytest?!
>
> Pytest has 4457 dependent packages and can thus only be changed on the=
> 'core-updates' branch.=C2=A0 So the recommended way is indeed = to define a new
> public 'python-pytest-5' variable, and add that as an input fo= r the
> packages that require 5.x.

OK=E2=80=A6 sounds like something I can do!


> On the next 'core-updates' cycle, Pytest 5 will then become th= e default,
> and we will have to fix all packages that does not work with that
> version :-)

I guess those broken packages will show up as "red" in Cuirass!?<= br> Would they have to be fixed, or just told to use python-pytest-4?

Is there a way to build those packages on my machine? What a
script to find and build all the packages dependent on pytest would look li= ke?
I mean, using LISP/Scheme/Guile, as I think I could come up with a
"manual" solution with `guix graph --type=3Dreverse-package`.
=
guix refresh -l should give you = the minimum number of packages that ensures every dependent is rebuilt.


Regards,

--
Tanguy

--0000000000008cdfbd0595686519--