guix-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#26868: [PATCH] gnu: python-pytest-runner: Update to 2.11.1.


From: julien lepiller
Subject: bug#26868: [PATCH] gnu: python-pytest-runner: Update to 2.11.1.
Date: Thu, 11 May 2017 11:11:57 +0200
User-agent: Roundcube Webmail/1.2.5

Le 2017-05-10 23:15, Marius Bakke a écrit :
Roel Janssen <address@hidden> writes:

From 33ba51e99c62243905cb88466eb5bfea557aaf4e Mon Sep 17 00:00:00 2001
From: Roel Janssen <address@hidden>
Date: Wed, 10 May 2017 19:53:45 +0200
Subject: [PATCH] gnu: python-pytest-runner: Update to 2.11.1.

[...]

When attempting to add another package (python-maildir-deduplicate),
I needed to upgrade this one.  Since I'm not sure about the impact of
this update, I'd like to have an opinion on whether this can go in
as-is, or that more care should be taken.

The impact of a package change can be determined with `guix refresh`:

$ guix refresh -l python{,2}-pytest-runner
Building the following 38 packages would ensure 113 dependent packages
are rebuilt: [...]

Since there are "only" 138 rebuilds it should be good for 'master'. It's
good to try and build some/most of the dependent packages to check for
any obvious breakage before such version jumps; but this seems fairly
safe to me.

Actually, I was about to push that this evening as part of my pootle patch series [1]. I've already tested rebuilding all dependent packages of the python- and python2 variants, and there is no new failure. The only difference being that your commit comment does not reference python2-pytest-runner, I think you can push your patch before mine if you want, or wait for me to push my patch series.

[1]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26613





reply via email to

[Prev in Thread] Current Thread [Next in Thread]