From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Langlois <pierre.langlois@gmx.com>
Cc: 36906-done@debbugs.gnu.org
Subject: bug#36906: [PATCH 0/2] gnu: Add emacs-mu4e-jump-to-list and emacs-mu4e-patch.
Date: Thu, 22 Aug 2019 17:57:32 +0200 [thread overview]
Message-ID: <878srlp503.fsf@gnu.org> (raw)
In-Reply-To: <87imreibui.fsf@gmx.com> (Pierre Langlois's message of "Sat, 03 Aug 2019 15:04:53 +0100")
Hello Pierre,
Pierre Langlois <pierre.langlois@gmx.com> skribis:
> Here are a couple of new packages that extend mu4e, notably, mu4e-patch
> makes emails with patches look nice :-).
Neat, applied both!
> As a side-note, I wasn't able to run `guix lint`:
>
> ~~~
> $ ./pre-inst-env guix lint emacs-mu4e-patch
> Backtrace:macs-mu4e-patch@0.1.0-1.522da46 [refresh]...
> 9 (apply-smob/1 #<catch-closure 1cab900>)
> 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) 1d36140>)))
> In guix/ui.scm:
> 1692:12 6 (run-guix-command _ . _)
> In srfi/srfi-1.scm:
> 640:9 5 (for-each #<procedure 21938a0 at guix/scripts/lint.scm…> …)
> In guix/scripts/lint.scm:
> 57:4 4 (run-checkers _ _)
> In srfi/srfi-1.scm:
> 640:9 3 (for-each #<procedure 4003e60 at guix/scripts/lint.scm…> …)
> In guix/scripts/lint.scm:
> 64:17 2 (_ _)
> In guix/lint.scm:
> 1010:2 1 (check-for-updates #<package emacs-mu4e-patch@0.1.0-1.5…>)
> In ice-9/boot-9.scm:
> 829:9 0 (catch srfi-34 #<procedure 6c89570 at guix/lint.scm:93…> …)
>
> ice-9/boot-9.scm:829:9: In procedure catch:
> Wrong type (expecting array): ()
> ~~~
>
> Does this ring any bells?
Yes: you’re running guile-json@1 whereas Guix now requires guile-json@3.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-08-22 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 14:04 [bug#36906] [PATCH 0/2] gnu: Add emacs-mu4e-jump-to-list and emacs-mu4e-patch Pierre Langlois
2019-08-22 15:57 ` Ludovic Courtès [this message]
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=878srlp503.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36906-done@debbugs.gnu.org \
--cc=pierre.langlois@gmx.com \
/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).