From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31162@debbugs.gnu.org
Subject: bug#31162: "guix pull" broke itself
Date: Thu, 19 Apr 2018 14:37:23 +0200 [thread overview]
Message-ID: <20180419143723.49836d5f@scratchpost.org> (raw)
In-Reply-To: <878t9jl721.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
Hi Ludo,
> OK, so it sounds like it’s the *previous* ‘guix pull’ that left you with
> miscompiled or otherwise broken modules.
>
> Could you: ‘guix gc -R $(readlink -f ~/.config/guix/latest)’,
$ guix gc -R $(readlink -f ~/.config/guix/latest) |grep guix
/gnu/store/yafigkxkq1fxfq0vwq4sndl1fjhh9aki-guix-packages-source
/gnu/store/q6sg0n5rxcgh95vzh7y623vwk8ksa33f-guix-register-0.14.0-10.486de73
/gnu/store/0drxkvvxm76vz0hb5mdpvdl071ha3if3-guix-system-source
/gnu/store/5jiyj90d2wk8jcz34n8zh59gnxdkj8v6-guix-f02d254ac
$ grep -l 5jiyj90d2wk8jcz34n8zh59gnxdkj8v6-guix-f02d254ac *guix*drv
pxm17xn6p9ndy3sjkzpdjwglfjizl7s1-guix-f02d254ac.drv
$ guix build --log-file /gnu/store/pxm17xn6p9ndy3sjkzpdjwglfjizl7s1-guix-f02d254ac.drv
/var/log/guix/drvs/px/m17xn6p9ndy3sjkzpdjwglfjizl7s1-guix-f02d254ac.drv.bz2
$ bunzip2 -cd /var/log/guix/drvs/px/m17xn6p9ndy3sjkzpdjwglfjizl7s1-guix-f02d254ac.drv.bz2 |od -tx1
0000000
> Besides, to work around the issue, you can always do:
>
> mv ~/.config/guix/latest{,.broken}
> guix pull
Sure, as soon as we've exhausted the debugging possibilities I'll do that.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-19 12:38 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 [this message]
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
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=20180419143723.49836d5f@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=31162@debbugs.gnu.org \
--cc=ludo@gnu.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).