all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 31162@debbugs.gnu.org
Subject: bug#31162: "guix pull" broke itself
Date: Thu, 19 Apr 2018 14:22:30 +0200	[thread overview]
Message-ID: <878t9jl721.fsf@gnu.org> (raw)
In-Reply-To: <20180418233958.504dc025@scratchpost.org> (Danny Milosavljevic's message of "Wed, 18 Apr 2018 23:39:58 +0200")

Hello,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

>> You should grep in ~/.config/guix/latest as well.
>
> ~/.config/guix/latest$ grep -r util-linux-2.31 .
> ./gnu/packages/linux.scm:(define-public util-linux-2.31.1
> ./gnu/system.scm:         util-linux-2.31.1
> Binary file ./gnu/system.go matches
>
>> I can’t seem to reproduce the issue though.  Is it just running ‘guix
>> pull’ that breaks, or do ‘guix package’ or ‘guix system’ fail similarly?
>
> 'guix package' and 'guix system' fail as well, with the same message.

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)’,
run ‘guix build --log-file’ for the relevant guix-*.drv, and see if the
build logs contain hints?

Besides, to work around the issue, you can always do:

  mv ~/.config/guix/latest{,.broken}
  guix pull

Thanks,
Ludo’.

  reply	other threads:[~2018-04-19 12:23 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 [this message]
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

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878t9jl721.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=31162@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.