From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37160@debbugs.gnu.org
Subject: bug#37160: guix lint --checkers=refresh fails
Date: Wed, 28 Aug 2019 11:36:28 +0200 [thread overview]
Message-ID: <f00bcb84-2d46-eeb6-e69a-2ed651c37fcd@web.de> (raw)
In-Reply-To: <87pnkqkzlu.fsf@gnu.org>
On 28.08.19 00:33, Ludovic Courtès wrote:
> Hi,
>
> Jonathan Brielmaier <jonathan.brielmaier@web.de> skribis:
>
>> guix lint --checkers=refresh hello
>> Backtrace:ello@2.10 [refresh]...
>> 9 (apply-smob/1 #<catch-closure 7fcdabc0a560>)
>> In ice-9/boot-9.scm:
>> 705:2 8 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
>> In ice-9/eval.scm:
>> 619:8 7 (_ #(#(#<directory (guile-user) 7fcdabcb9140>)))
>> In guix/ui.scm:
>> 1692:12 6 (run-guix-command _ . _)
>> In srfi/srfi-1.scm:
>> 640:9 5 (for-each #<procedure 7fcdaa7e9500 at guix/scripts/lin…> …)
>> In guix/scripts/lint.scm:
>> 57:4 4 (run-checkers #<package hello@2.10 gnu/packages/base.s…> …)
>> In srfi/srfi-1.scm:
>> 640:9 3 (for-each #<procedure 7fcd9e787ba0 at guix/scripts/lin…> …)
>> In guix/scripts/lint.scm:
>> 64:17 2 (_ _)
>> In guix/lint.scm:
>> 1010:2 1 (check-for-updates #<package hello@2.10 gnu/packages/ba…>)
>> In ice-9/boot-9.scm:
>> 829:9 0 (catch srfi-34 #<procedure 7fcd9f2c0390 at guix/lint.s…> …)
>>
>> ice-9/boot-9.scm:829:9: In procedure catch:
>> Wrong type to apply: #f
>
> I think commit 58d5f280a36e1cfddfa999d320c285726d8a8bc1 fixes it,
> doesn’t it? :-)
My package is now on2f57fa10f4, so includes your commit. But the error
still looks very similar:
$ guix lint --checkers=refresh hello
Backtrace:ello@2.10 [refresh]...
9 (apply-smob/1 #<catch-closure 7fcbddeb4800>)
In ice-9/boot-9.scm:
705:2 8 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
In ice-9/eval.scm:
619:8 7 (_ #(#(#<directory (guile-user) 7fcbddf82140>)))
In guix/ui.scm:
1692:12 6 (run-guix-command _ . _)
In srfi/srfi-1.scm:
640:9 5 (for-each #<procedure 7fcbdbe8b0a0 at guix/scripts/lin…> …)
In guix/scripts/lint.scm:
57:4 4 (run-checkers #<package hello@2.10 gnu/packages/base.s…> …)
In srfi/srfi-1.scm:
640:9 3 (for-each #<procedure 7fcbd3b8ca80 at guix/scripts/lin…> …)
In guix/scripts/lint.scm:
64:17 2 (_ _)
In guix/lint.scm:
1010:2 1 (check-for-updates #<package hello@2.10 gnu/packages/ba…>)
In ice-9/boot-9.scm:
829:9 0 (catch srfi-34 #<procedure 7fcbd3943e10 at guix/lint.s…> …)
ice-9/boot-9.scm:829:9: In procedure catch:
Wrong type to apply: #f
next prev parent reply other threads:[~2019-08-28 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 14:45 bug#37160: guix lint --checkers=refresh fails Jonathan Brielmaier
2019-08-27 9:44 ` Ludovic Courtès
2019-08-27 10:27 ` Jonathan Brielmaier
2019-08-27 22:33 ` Ludovic Courtès
2019-08-28 9:36 ` Jonathan Brielmaier [this message]
2019-08-27 10:29 ` quiliro
2019-08-27 12:51 ` Jonathan Brielmaier
2019-08-27 12:59 ` quiliro
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=f00bcb84-2d46-eeb6-e69a-2ed651c37fcd@web.de \
--to=jonathan.brielmaier@web.de \
--cc=37160@debbugs.gnu.org \
--cc=ludo@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).