From: Roel Janssen <roel@gnu.org>
To: 26868@debbugs.gnu.org
Subject: bug#26868: [PATCH] gnu: python-pytest-runner: Update to 2.11.1.
Date: Wed, 10 May 2017 19:57:37 +0200 [thread overview]
Message-ID: <87fugcbnn2.fsf@gnu.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: 0001-gnu-python-pytest-runner-Update-to-2.11.1.patch --]
[-- Type: text/x-patch, Size: 1070 bytes --]
From 33ba51e99c62243905cb88466eb5bfea557aaf4e Mon Sep 17 00:00:00 2001
From: Roel Janssen <roel@gnu.org>
Date: Wed, 10 May 2017 19:53:45 +0200
Subject: [PATCH] gnu: python-pytest-runner: Update to 2.11.1.
* gnu/packages/python.scm (python-pytest-runner): Update to 2.11.1.
---
gnu/packages/python.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 60d3868e9..be0202de6 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -1879,14 +1879,14 @@ supports coverage of subprocesses.")
(define-public python-pytest-runner
(package
(name "python-pytest-runner")
- (version "2.6.2")
+ (version "2.11.1")
(source
(origin
(method url-fetch)
(uri (pypi-uri "pytest-runner" version))
(sha256
(base32
- "1nwcqx0l3fv52kv8526wy8ypzghbq96c96di318d98d3wh7a8xg7"))))
+ "1cw978kqqcq916b9gfns1qjqvg33c5ail5jhw9054dsynkm32flq"))))
(build-system python-build-system)
(arguments
`(#:phases
--
2.12.2
[-- Attachment #2: Type: text/plain, Size: 289 bytes --]
Dear Guix,
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.
Kind regards,
Roel Janssen
next reply other threads:[~2017-05-10 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 17:57 Roel Janssen [this message]
2017-05-10 21:15 ` bug#26868: [PATCH] gnu: python-pytest-runner: Update to 2.11.1 Marius Bakke
2017-05-11 9:11 ` julien lepiller
2017-05-11 9:24 ` Roel Janssen
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fugcbnn2.fsf@gnu.org \
--to=roel@gnu.org \
--cc=26868@debbugs.gnu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).