--- Begin Message ---
Subject: |
[PATCH 1/5] gnu: python-daemon: Update to 2.3.0. |
Date: |
Tue, 30 Nov 2021 21:37:20 +0100 |
---
this patchset updates trezor support to current latest. it eliminates
the argv[0] patch that was introduced in https://issues.guix.gnu.org/50751
because upstream stopped using argv[0].
issue 50751 just got pushed recently, sorry for the unfortunate timing.
i was just about to send the new set of patches, but here they are.
gnu/packages/python-xyz.scm | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index ffd39860d8..2f95f272c7 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -4103,14 +4103,14 @@ (define-public python2-joblib
(define-public python-daemon
(package
(name "python-daemon")
- (version "2.2.3")
+ (version "2.3.0")
(source
(origin
(method url-fetch)
(uri (pypi-uri "python-daemon" version))
(sha256
(base32
- "09fcjdjzk9ywmpnrj62iyxqgcygzdafsz41qlrk2dknzbagcmzmg"))))
+ "1bxfn2bq56sd4w0nm9mqy8y0905m7fc8vmhnjxlrf49vcbqr7adx"))))
(build-system python-build-system)
(arguments
`(#:phases
@@ -4125,9 +4125,11 @@ (define-public python-daemon
(propagated-inputs
`(("python-lockfile" ,python-lockfile)))
(native-inputs
- `(("python-unittest2" ,python-unittest2)
+ `(("python-coverage" ,python-coverage)
+ ("python-unittest2" ,python-unittest2)
("python-testtools" ,python-testtools)
("python-testscenarios" ,python-testscenarios)
+ ("python-twine" ,python-twine)
("python-mock" ,python-mock)
("python-docutils" ,python-docutils)))
(home-page "https://pagure.io/python-daemon/")
--
2.33.0
--- End Message ---
--- Begin Message ---
Subject: |
Re: [bug#52207] [PATCH 1/2] gnu: python-daemon: Update to 2.3.0. |
Date: |
Wed, 01 Dec 2021 18:40:25 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) |
Hello,
Attila Lendvai <attila@lendvai.name> writes:
> as requested, resending the patchset in only two commits (rationale:
> the packages are inter-dependent, and splitting the commit means that
> the commits would leave the repo in a broken state; thinking of
> git bisect, etc).
I applied the patches, thank you.
I tweaked the last one because it was based on a previous patch, not the
current state of the repository. I also fixed commit messages. You may
want to look at them.
Regards,
--
Nicolas Goaziou
--- End Message ---