From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: 60003@debbugs.gnu.org
Subject: [bug#60003] [PATCH 0/3] gnu: Add pass-import.
Date: Fri, 3 Feb 2023 18:25:23 +0100 [thread overview]
Message-ID: <c0c4a768-0110-44da-2906-63382050df96@web.de> (raw)
In-Reply-To: <cover.1670844319.git.tobias.kortkamp@gmail.com>
I see this test failure(s) as well. Additionaly I required this diff to
get it start building:
diff --git a/gnu/packages/password-utils.scm
b/gnu/packages/password-utils.scm
index 0fdfccaa5b..f8a0b6a40c 100644
--- a/gnu/packages/password-utils.scm
+++ b/gnu/packages/password-utils.scm
@@ -1535,7 +1535,7 @@ (define-public pass-import
(source (origin
(method url-fetch)
(uri (string-append
"https://github.com/roddhjav/pass-import"
- "/releases/download/" version
"/pass-import-"
+ "/releases/download/v" version
"/pass-import-"
version ".tar.gz"))
(sha256
(base32
"18vh97h3bmspwqhb9xjkapk3p8hy4rxhazrcc06f6pdz8rb6rxxp"))))
I further recommend to use the `git-fetch` method in this case...
next prev parent reply other threads:[~2023-02-03 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:46 [bug#60003] [PATCH 0/3] gnu: Add pass-import Tobias Kortkamp
2022-12-12 11:49 ` [bug#60003] [PATCH 1/3] gnu: python-construct: Update to 2.10.68 Tobias Kortkamp
2022-12-12 11:49 ` [bug#60003] [PATCH 2/3] gnu: python-pykeepass: Update to 4.0.3 Tobias Kortkamp
2022-12-12 11:49 ` [bug#60003] [PATCH 3/3] gnu: Add pass-import Tobias Kortkamp
2023-01-05 15:21 ` Jelle Licht
2023-01-11 11:55 ` Tobias Kortkamp
2023-02-02 13:13 ` Jelle Licht
2023-02-03 17:25 ` Jonathan Brielmaier [this message]
2023-05-22 9:48 ` [bug#60003] [PATCH 0/3] " Tobias Kortkamp
2023-05-22 9:45 ` [bug#60003] [PATCH v2 1/2] gnu: python-pykeepass: Update to 4.0.4 Tobias Kortkamp
2023-05-22 9:45 ` [bug#60003] [PATCH v2 2/2] gnu: Add pass-import Tobias Kortkamp
2024-04-18 18:52 ` [bug#60003] Built docs using pandoc Abhishek Cherath
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=c0c4a768-0110-44da-2906-63382050df96@web.de \
--to=jonathan.brielmaier@web.de \
--cc=60003@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).