From: Leo Famulari <leo@famulari.name>
To: 50522@debbugs.gnu.org
Subject: [bug#50522] [PATCH] gnu: asignify: Update to 1.1-1.08af003.
Date: Sat, 11 Sep 2021 13:53:12 -0400 [thread overview]
Message-ID: <8e773a091b76322f338f4f84bba22c34cf3a5f1a.1631382741.git.leo@famulari.name> (raw)
I might have screwed up the versioning of this package:
https://github.com/vstakhov/asignify/issues/17
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(-)
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
next reply other threads:[~2021-09-11 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 17:53 Leo Famulari [this message]
2021-10-26 16:34 ` bug#50522: [PATCH] gnu: asignify: Update to 1.1-1.08af003 Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e773a091b76322f338f4f84bba22c34cf3a5f1a.1631382741.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=50522@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.