[PATCH] gnu: asignify: Update to 1.1-1.08af003.

  • Done
  • quality assurance status badge
Details
One participant
  • Leo Famulari
Owner
unassigned
Submitted by
Leo Famulari
Severity
normal
L
L
Leo Famulari wrote on 11 Sep 2021 19:53
(address . guix-patches@gnu.org)
8e773a091b76322f338f4f84bba22c34cf3a5f1a.1631382741.git.leo@famulari.name
I might have screwed up the versioning of this package:


I wonder what's the best way to "update" it while making sure that it is
correct and also making sure that `guix package -u asignify` works as
desired...

* gnu/packages/crypto.scm (asignify): Update to 1.1-1.08af003.
---
gnu/packages/crypto.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

Toggle diff (26 lines)
diff --git a/gnu/packages/crypto.scm b/gnu/packages/crypto.scm
index c511d0a711..2a54ead1d5 100644
--- a/gnu/packages/crypto.scm
+++ b/gnu/packages/crypto.scm
@@ -964,8 +964,8 @@ security.")
(license license:gpl2)))
(define-public asignify
- (let ((commit "f58e7977a599f040797975d649ed318e25cbd2d5")
- (revision "0"))
+ (let ((commit "08af003e1f4833713db28b871759d94f9b2b1469")
+ (revision "1"))
(package
(name "asignify")
(version (git-version "1.1" revision commit))
@@ -977,7 +977,7 @@ security.")
(file-name (git-file-name name version))
(sha256
(base32
- "1zl68qq6js6fdahxzyhvhrpyrwlv8c2zhdplycnfxyr1ckkhq8dw"))))
+ "1zacpqa8b5lg270z1g06r5ik9vnb91crb4ivyy20381dny82xvr1"))))
(build-system gnu-build-system)
(arguments
`(#:configure-flags
--
2.33.0
L
L
Leo Famulari wrote on 26 Oct 2021 18:34
(address . 50522-done@debbugs.gnu.org)
YXguJzutbJSs5FTm@jasmine.lan
Pushed as c6adc0947396daa6d85ab08837f9cbc86f4d8722
Closed
?