From: Ricardo Wurmus <rekado@fhain.coderdojo.berlin>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 31162-done@debbugs.gnu.org
Subject: bug#31162: "guix pull" broke itself
Date: Mon, 04 Feb 2019 11:01:59 +0100 [thread overview]
Message-ID: <87sgx3hnxk.fsf@fhain.coderdojo.berlin> (raw)
In-Reply-To: <20180521105703.0e9865bf@scratchpost.org> (Danny Milosavljevic's message of "Mon, 21 May 2018 10:57:03 +0200")
Hi,
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi Ludo,
>
> I've checked guix-packages now and I see:
>
> $ bzless $(guix build --log-file /gnu/store/q0s172fgb213c4jk7hvgkzsw0i1bq6j0-guix-packages.drv)
>
> ...
> 31.4% of 407 files^Mcompiling... 31.7% of 407 files^Mcompiling... 31.9% of 407 files^Mcompiling... 32.2% of 407 files^Mcompiling... 32.4% of 407 files^Mcompiling... 32.7% of 407 files^Mcompiling... 32.9% of 407 files^Mcompiling... 33.2% of 407 files^Mcompiling... 33.4% of 407 files^Mcompiling... 33.7% of 407 files^Mcompiling... 33.9% of 407 files^Mcompiling... 34.2% of 407 files^Mcompiling... 34.4% of 407 files^Mcompiling... 34.6% of 407 files^Mcompiling... 34.9% of 407 files^Mcompiling... 35.1% of 407 files^Mcompiling... 35.4% of 407 files^Mcompiling... 35.6% of 407 files^Mcompiling... 35.9% of 407 files^Mcompiling... 36.1% of 407 files^Mcompiling... 36.4% of 407 files^Mcompiling... 36.6% of 407 files^Mcompiling... 36.9% of 407 files^Mcompiling... 37.1% of 407 files^Mcompiling...
> 37.3% of 407 files^Mcompiling... 37.6% of 407 files^Mcompiling... 37.8% of 407 files^Mcompiling... 38.1% of 407 files^Mcompiling... 38.3% of 407 filesIn thread:
> unexpected syntax
> In thread:
> no code for module (guix licenses)
> ^Mcompiling... 38.6% of 407 filesIn thread:
> no code for module (guix licenses)
> ^Mcompiling... 38.8% of 407 filesIn thread:
> no code for module (guix licenses)
> ^Mcompiling... 100.0% of 407 files
>
> (Deleting ~/.cache/guile and ~/.cache/guix didn't help)
I believe that this can no longer happen since the new “guix pull”
(aside from the infamous miscompilation bug #27476).
I’m closing this, but feel free to reopen if this can be reproduced with
the new “guix pull” implementation.
~~ Ricardo
prev parent reply other threads:[~2019-02-04 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 10:59 bug#31162: "guix pull" broke itself Danny Milosavljevic
2018-04-18 21:19 ` Ludovic Courtès
2018-04-18 21:39 ` Danny Milosavljevic
2018-04-19 12:22 ` Ludovic Courtès
2018-04-19 12:37 ` Danny Milosavljevic
2018-04-23 15:14 ` Ludovic Courtès
2018-04-24 20:57 ` Danny Milosavljevic
2018-04-24 22:20 ` Adonay Felipe Nogueira
2018-04-25 12:42 ` Ludovic Courtès
2018-05-21 8:57 ` Danny Milosavljevic
2019-02-04 10:01 ` Ricardo Wurmus [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=87sgx3hnxk.fsf@fhain.coderdojo.berlin \
--to=rekado@fhain.coderdojo.berlin \
--cc=31162-done@debbugs.gnu.org \
--cc=dannym@scratchpost.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).