[PATCH] Updated the package from 0.6.0 to 0.9.0

  • Done
  • quality assurance status badge
Details
2 participants
  • nafkhamdc
  • Ricardo Wurmus
Owner
unassigned
Submitted by
nafkhamdc
Severity
normal

Debbugs page

N
N
nafkhamdc wrote on 28 Mar 05:29 -0700
(address . guix-patches@gnu.org)(name . nafkhamdc)(address . navid.afkhami@mdc-berlin.de)
2e19eb23917df2ebefe9826f549e3e7ce5fd3e79.1711628998.git.navid.afkhami@mdc-berlin.de
Change-Id: I68bcd6840577a12594e491e9fd5e114f9261f6c7
---
gnu/packages/python-science.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (28 lines)
diff --git a/gnu/packages/python-science.scm b/gnu/packages/python-science.scm
index b6a116f16b..55868e300d 100644
--- a/gnu/packages/python-science.scm
+++ b/gnu/packages/python-science.scm
@@ -1435,14 +1435,14 @@ (define-public python-unyt
(define-public python-upsetplot
(package
(name "python-upsetplot")
- (version "0.6.0")
+ (version "0.9.0")
(source
(origin
(method url-fetch)
(uri (pypi-uri "UpSetPlot" version))
(sha256
(base32
- "11zrykwnb00w5spx4mnsnm0f9gwrphdczainpmwkyyi50vipaa2l"))
+ "14l5gcj88cclkj1mf74bcy1pxq1hgsiy27fa3vxrsk32ik1nmdwm"))
(modules '((guix build utils)))
(snippet
;; Patch for compatibility with newer setuptools:

base-commit: 0e8f7ee3a95011dd9ebdc99e0f3b754160524b5d
prerequisite-patch-id: d26b189d1487d0d6a234a8197c5892f1e179e5f5
prerequisite-patch-id: 3cb34404c868aab6f273aa4342ac7266fc82457f
prerequisite-patch-id: 26c6975580ae7feb5100f84e6c123d908a303fca
--
2.34.1
R
R
Ricardo Wurmus wrote on 28 Mar 05:39 -0700
(address . 70052-done@debbugs.gnu.org)
87sf0aa5rw.fsf@elephly.net
Thanks for the patch. I noticed that the snippet should also have been
removed, because the changes have been applied upstream.

I also took the liberty of replacing the build system to remove the
custom check phase. I also replaced the commit message to our usual
format.

--
Ricardo
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 70052@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70052
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch