[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31162: "guix pull" broke itself
From: |
Ludovic Courtès |
Subject: |
bug#31162: "guix pull" broke itself |
Date: |
Thu, 19 Apr 2018 14:22:30 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) |
Hello,
Danny Milosavljevic <address@hidden> 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’.
- bug#31162: "guix pull" broke itself, Danny Milosavljevic, 2018/04/15
- bug#31162: "guix pull" broke itself, Ludovic Courtès, 2018/04/18
- bug#31162: "guix pull" broke itself, Danny Milosavljevic, 2018/04/18
- bug#31162: "guix pull" broke itself,
Ludovic Courtès <=
- bug#31162: "guix pull" broke itself, Danny Milosavljevic, 2018/04/19
- bug#31162: "guix pull" broke itself, Ludovic Courtès, 2018/04/23
- bug#31162: "guix pull" broke itself, Danny Milosavljevic, 2018/04/24
- bug#31162: "guix pull" broke itself, Adonay Felipe Nogueira, 2018/04/24
- bug#31162: "guix pull" broke itself, Ludovic Courtès, 2018/04/25