unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 23475@debbugs.gnu.org
Subject: bug#23475: no code for module (guix ui)
Date: Tue, 02 Aug 2016 11:17:03 +0200	[thread overview]
Message-ID: <87twf3zg1c.fsf@gnu.org> (raw)
In-Reply-To: <20160802013047.GA3302@jasmine> (Leo Famulari's message of "Mon, 1 Aug 2016 21:30:47 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Sun, Jul 31, 2016 at 06:40:00PM +0200, Ludovic Courtès wrote:
>> Any updates?  :-)
>
> I've noticed that it happens if I do this:
>
> $ guix gc && ./pre-inst-env guix build foo
>
> If I then do the following, it works again:
>
> $ guix environment guix
> $ exit
> $ ./pre-inst-env guix build foo 
>
> I don't have all of the Guix dependencies in my profile or my Debian
> environment (I see this on my Debian machine), so I guess that something
> important is garbage collected, but I haven't figured out what yet.
>
> So, I think it's not much of a bug, since I am deliberately invoking the
> garbage collector. WDYT?

Possibly.  If you use ./configure -C, the ‘config.cache’ file also gets
stale after GC.  But even if you don’t, (guix config) might be referring
to things that have been collected, so you have to:

  rm -f config.cache && ./configure

I’m closing this bug, but do reopen it if you think something’s really
broken.  :-)

Thanks!

Ludo’.

      reply	other threads:[~2016-08-02  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07  2:59 bug#23475: no code for module (guix ui) Leo Famulari
2016-05-08 16:10 ` Ludovic Courtès
2016-05-22 21:36   ` Ludovic Courtès
2016-05-23  3:22     ` Leo Famulari
2016-07-31 16:40       ` Ludovic Courtès
2016-08-02  1:30         ` Leo Famulari
2016-08-02  9:17           ` 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=87twf3zg1c.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=23475@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).