all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Guix <guix-devel@gnu.org>
Subject: Re: Questions about packaging
Date: Wed, 23 Oct 2019 20:10:42 +0200	[thread overview]
Message-ID: <878spbwcwt.fsf@devup.no> (raw)
In-Reply-To: <20191021092320.rirojs26u6vshivn@rafflesia>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

Tanguy Le Carrour <tanguy@bioneland.org> writes:

> Le 10/18, Marius Bakke a écrit :
>> 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?

The answer to that is "it depends" :-)

If the fix is easy or obvious, we do that; but it's OK to use Pytest 4
if a proper fix turns out to be difficult.

> 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=reverse-package`.

Try `guix refresh -l python{,2}-pytest`.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      parent reply	other threads:[~2019-10-23 18:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09  9:56 Questions about packaging Tanguy Le Carrour
2019-10-10  0:41 ` Danny Milosavljevic
2019-10-11  7:42   ` Tanguy Le Carrour
2019-10-12 10:41     ` Danny Milosavljevic
2019-10-12 10:49       ` Danny Milosavljevic
2019-10-14  7:53         ` Tanguy Le Carrour
2019-10-14  7:51       ` Tanguy Le Carrour
2019-10-18 17:16         ` Marius Bakke
2019-10-21  9:23           ` Tanguy Le Carrour
2019-10-21  9:34             ` Gábor Boskovits
2019-10-23 18:10             ` Marius Bakke [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

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

  git send-email \
    --in-reply-to=878spbwcwt.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=tanguy@bioneland.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.