unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jelle Licht <jlicht@fsfe.org>
To: Arun Isaac <arunisaac@systemreboot.net>, 38715@debbugs.gnu.org
Subject: bug#38715: Issue with guile-email: unbound variable
Date: Mon, 23 Dec 2019 14:48:52 +0100	[thread overview]
Message-ID: <87a77jp2yj.fsf@jlicht.xyz> (raw)
In-Reply-To: <cu77e2nk28m.fsf@systemreboot.net>

Arun Isaac <arunisaac@systemreboot.net> writes:

>> My best guess is that this has something to do with a circular
>> reference between guile modules, but I am not certain on how to easily
>> debug (and fix) this.
>
> I updated the guile-email package two days ago. I hope that is not what
> introduced this problem, and I don't see how it could have. Even `guix
> build guile-email` on the terminal fails with a guile-email unbound
> variable error.

I do not think it was that commit, as I found the offending commit:
c7b2b539802eaa3f969e212c98eb671a1a75e9f3

This is the commit that adds mumimu to gnu/packages/mail.scm, as well as
to the inputs of mumi. Reverting this commit (at least) solves the issue
I had in the first mail.

Could it be that the reference to guile-email in the version field of
mumimu created this issue?
--8<---------------cut here---------------start------------->8---
(version (git-version (package-version guile-email) revision commit))
--8<---------------cut here---------------end--------------->8---

- Jelle

  reply	other threads:[~2019-12-23 13:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23  3:20 bug#38715: Issue with guile-email: unbound variable Jelle Licht
2019-12-23  5:56 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-12-23  6:03 ` Arun Isaac
2019-12-23 13:48   ` Jelle Licht [this message]
2019-12-26 10:41     ` Christopher Baines
2019-12-26 18:18       ` Ludovic Courtès
2019-12-26 20:03       ` Ricardo Wurmus
2020-12-06 12:27         ` Ricardo Wurmus

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=87a77jp2yj.fsf@jlicht.xyz \
    --to=jlicht@fsfe.org \
    --cc=38715@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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).