From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 42601@debbugs.gnu.org
Subject: bug#42601: Guix install bug: error: Unbound variable: ~S
Date: Wed, 29 Jul 2020 18:33:31 -0400 [thread overview]
Message-ID: <20200729223331.GA10794@jasmine.lan> (raw)
In-Reply-To: <87pn8ege77.fsf@elephly.net>
On Thu, Jul 30, 2020 at 12:15:56AM +0200, Ricardo Wurmus wrote:
> “Unbound variable: ~S” looks like a format string with a placeholder
> that didn’t get replaced with an actual value. It would be marginally
> better if it said “Unbound variable: avr-toolchain”.
The reason I suggested an interface change being responsible for
"Unbound variable: ~S" is that I noticed it a couple days ago after
changes to (guix ui), and it was fixed by `make clean-go`:
http://logs.guix.gnu.org/guix/2020-07-27.log#015055
I think that error message is an example of what can go wrong when using
a development environment without rebuilding everything first.
next prev parent reply other threads:[~2020-07-29 22:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 16:09 bug#42601: Guix install bug: error: Unbound variable: ~S Jan Wielkiewicz
2020-07-29 16:16 ` Jan Wielkiewicz
2020-07-29 17:00 ` Leo Famulari
2020-07-29 17:18 ` Jan Wielkiewicz
2020-07-29 17:57 ` Ricardo Wurmus
2020-07-29 19:36 ` Jan Wielkiewicz
2020-07-29 19:44 ` Jan Wielkiewicz
2020-07-29 20:17 ` Ricardo Wurmus
2020-07-29 22:12 ` Jan Wielkiewicz
2020-07-29 22:15 ` Ricardo Wurmus
2020-07-29 22:33 ` Leo Famulari [this message]
2020-07-31 8:04 ` Bengt Richter
2020-08-03 18:39 ` maxim.cournoyer
2020-08-05 20:33 ` Ludovic Courtès
2020-08-05 23:53 ` Jan Wielkiewicz
2020-08-23 16:24 ` Ludovic Courtès
2020-08-09 22:25 ` Jan Wielkiewicz
2022-06-11 21:27 ` bug#42601: Sharlatan Hellseher
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=20200729223331.GA10794@jasmine.lan \
--to=leo@famulari.name \
--cc=42601@debbugs.gnu.org \
--cc=rekado@elephly.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).