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: Marius Bakke
Subject: bug#26868: [PATCH] gnu: python-pytest-runner: Update to 2.11.1.
Date: Wed, 10 May 2017 23:15:22 +0200
User-agent: Notmuch/0.24.1 (https://notmuchmail.org) Emacs/25.2.1 (x86_64-unknown-linux-gnu)

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.

Attachment: signature.asc
Description: PGP signature


reply via email to

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