help-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Broken Guix Pull


From: Maxim Cournoyer
Subject: Re: Broken Guix Pull
Date: Fri, 02 Jul 2021 17:16:57 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

Hi Christopher,

Christopher Howard <christopher@librehacker.com> writes:

> Hello, I had a power outage during a guix pull a few days ago, and I haven't 
> been able to do a `guix pull` successfully since then from that computer. I 
> always get an error similar to this:
>
> ```
> building /gnu/store/yjx4pq303sj22w6476j1hql3h74z1lr4-config.scm.drv...
> building /gnu/store/60v3vy5ls2vgy47rs26r1xbz6in04hv4-module-import.drv...
> building /gnu/store/7nzi3i4031h2piwk1640yjnh9lnrwnwy-module-import.drv...
> building 
> /gnu/store/nmqi0acf82hkb1wbx9d916qb3cpjgwzk-module-import-compiled.drv...
>   4%
> [#######                                                                      
>                                                                               
>                                             
>        ]builder for 
> `/gnu/store/nmqi0acf82hkb1wbx9d916qb3cpjgwzk-module-import-compiled.drv' 
> failed with exit code 1
> build of 
> /gnu/store/nmqi0acf82hkb1wbx9d916qb3cpjgwzk-module-import-compiled.drv failed
> View build log at 
> '/var/log/guix/drvs/nm/qi0acf82hkb1wbx9d916qb3cpjgwzk-module-import-compiled.drv.bz2'.
> cannot build derivation 
> `/gnu/store/3swk97m8jdqksr3lvhiid0k3k48jvwv1-compute-guix-derivation.drv': 1 
> dependencies couldn't be built
> guix pull: error: build of 
> `/gnu/store/3swk97m8jdqksr3lvhiid0k3k48jvwv1-compute-guix-derivation.drv' 
> failed
>
> ```
>
> The log looks like this, minus the last 10,000 null characters:
>
> ```
> [ 1/78] Loading './gcrypt/hash.scm'...
> [ 2/78] Loading './git.scm'...
> [ 3/78] Loading './gnu/packages/bootstrap.scm'...
> Backtrace:
>           19 (primitive-load "./gnu/packages/bootstrap.scm")
> In ice-9/eval.scm:
>    721:20 18 (primitive-eval (define-module (gnu packages #) # (?) ?))
> In ice-9/psyntax.scm:
>   1241:36 17 (expand-top-sequence ((define-module (gnu # #) # (?) ?)) ?)
>   1233:19 16 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
>    285:10 15 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) ?)
> In ice-9/eval.scm:
>    293:34 14 (_ #<directory (guix build utils) 7ffff5994d20>)
> In ice-9/boot-9.scm:
>    3380:4 13 (define-module* _ #:filename _ #:pure _ #:version _ # _ ?)
>   2565:24 12 (call-with-deferred-observers #<procedure 7ffff5543a50 ?>)
>   3393:24 11 (_)
>    222:17 10 (map1 (((guix licenses)) ((gnu packages)) ((guix #)) # ?))
>   3297:17  9 (resolve-interface (guix licenses) #:select _ #:hide _ # ?)
> In ice-9/threads.scm:
>     390:8  8 (_ _)
> In ice-9/boot-9.scm:
>   3223:13  7 (_)
> In ice-9/threads.scm:
>     390:8  6 (_ _)
> In ice-9/boot-9.scm:
>   3507:20  5 (_)
>    2806:4  4 (save-module-excursion #<procedure 7ffff5214930 at ice-?>)
>   3527:26  3 (_)
> In unknown file:
>            2 (primitive-load-path "guix/licenses" #<procedure 7ffff5?>)
> In ice-9/eval.scm:
>    223:20  1 (proc #<module (#{ g74}#) 7ffff5255be0>)
> In unknown file:
>            0 (%resolve-variable (7 . #) #<module (#{ g74}#) 7ffff525?>)
>
> ERROR: In procedure %resolve-variable:
> Unbound variable: 
> #{\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;\x0;
> ```
>
> These are fixes that I have tried, but I always get the same failure:
>
> * sudo guix gc --verify=contents,repair
>
> Ends with an error like:
>
> ```
> error: cannot repair path 
> `/gnu/store/48bcdy815zcp007v0jpjrw9wnbs1cinh-guix-c19d29c'
> ```
>
> * doing a `guix pull --roll-back`
>
> * doing a `guix pull --commit` back to some earlier commit.
>
> * building guix myself from a local checkout, and trying to pull using that 
> guix (the above output is from that attempt)
>
> * Deleting ~/.cache/guix
>
> Could I get some guidance on what to do?

I hope others will have more helpful replies than mine, but perhaps your
file system was badly damaged.  Depending on what kind of file system
you are using, you may want to try to run a fsck tool to see if it can
recover.

HTH,

Maxim



reply via email to

[Prev in Thread] Current Thread [Next in Thread]