From: Maxime Devos <maximedevos@telenet.be>
To: "(" <paren@disroot.org>, 56722@debbugs.gnu.org
Subject: bug#56722: guix pull fails -- unbound variable in gnu/home/services/symlink-manager.scm
Date: Sat, 23 Jul 2022 12:26:47 +0200 [thread overview]
Message-ID: <ec512883-c254-b08e-7a96-25fc3164d252@telenet.be> (raw)
In-Reply-To: <CLMXM00R1D8L.2KCVYXJAIMUW0@guix-aspire>
[-- Attachment #1.1.1: Type: text/plain, Size: 605 bytes --]
On 23-07-2022 11:35, paren--- via Bug reports for GNU Guix wrote:
> Log here:
> <https://paste.sr.ht/~unmatched-paren/201220d944b25ae9074d94c29b88852de70730cb>
>
> What's weird is that the culprit, gnu/home/services/symlink-manager.scm,
> *does* have access to `service-type`, because it imports (gnu home
> services), which re-exports it!
Such weirdness can be caused by cycles in the module structure, maybe
see if you can locate a cycle between (gnu home services
symlink-manager), (gnu home services) and the modules from that
ba2256... commit and break it?
Greetings,
Maxime
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-23 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 9:35 bug#56722: guix pull fails -- unbound variable in gnu/home/services/symlink-manager.scm paren--- via Bug reports for GNU Guix
2022-07-23 10:08 ` paren--- via Bug reports for GNU Guix
2022-07-31 22:08 ` Ludovic Courtès
2022-07-31 22:18 ` paren--- via Bug reports for GNU Guix
2022-07-23 10:26 ` Maxime Devos [this message]
2022-07-23 10:32 ` Maxime Devos
2022-07-24 10:39 ` paren--- via Bug reports for GNU Guix
2022-07-24 10:52 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-07-31 20:49 ` Ludovic Courtès
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=ec512883-c254-b08e-7a96-25fc3164d252@telenet.be \
--to=maximedevos@telenet.be \
--cc=56722@debbugs.gnu.org \
--cc=paren@disroot.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).