#28144 - info-dir ERROR: no code for module (guix build utils) - GNU bug report logs
GNU bug report logs -
#28144
info-dir ERROR: no code for module (guix build utils)
Previous
Next
Package:
guile
Reported by:
Christopher Baines
Date: Sat, 19 Aug 2017 00:21:01 UTC
Severity:
serious
Tags: unreproducible
Merged with
27476
27652
31294
31367
31740
32385
34112
34319
Done:
Ludovic Courtès
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first
unarchive
it, by sending
a message to control AT debbugs.gnu.org, with
unarchive 28144
in the body.
You can then email your comments to 28144 AT debbugs.gnu.org in the normal way.
Toggle
the display of automated, internal messages from the tracker.
View this report as an
mbox folder
status mbox
maintainer mbox
Report forwarded
to
bug-guix
bug#28144
; Package
guix
(Sat, 19 Aug 2017 00:21:01 GMT)
Full text
and
rfc822 format
available.
Acknowledgement sent
to
Christopher Baines
New bug report received and forwarded. Copy sent to
bug-guix
(Sat, 19 Aug 2017 00:21:01 GMT)
Full text
and
rfc822 format
available.
Message #5
received at submit
full text
mbox
):
From:
Christopher Baines
To:
bug-guix
Subject:
info-dir ERROR: no code for module (guix build utils)
Date:
Sat, 19 Aug 2017 01:20:22 +0100
Message part 1
(text/plain, inline)]
I've had the following issue a few times now, it seems that somehow,
the info-dir builder can be incorrectly generated, without the usual
module import stuff.
The most recent time this occurred, I worked around this by finding the
guix package in the store which I thought was being used at the time,
and explicitly garbage collected it (guix gc -d ...). I then rebuilt
it, and this seemed to work around the problem. I was using the same
guix package, pinned to an revision in a git repository.
The builder starts with:
(begin (use-modules (guix build utils)
This is the error which you get:
The following derivations will be built:
/gnu/store/8qi10kwz4ghabdj5p7s252z11snvhhgf-profile.drv
/gnu/store/0jxiph2hvmvakcj6gkz9d00a8ncma903-info-dir.drv
Backtrace:
In ice-9/boot-9.scm:
160: 18 [catch #t #
In unknown file:
?: 17 [apply-smob/1 #
In ice-9/boot-9.scm:
66: 16 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
432: 15 [eval # #]
In ice-9/boot-9.scm:
2412: 14 [save-module-excursion #
4089: 13 [#
1734: 12 [%start-stack load-stack #
1739: 11 [#
In unknown file:
?: 10 [primitive-load "/gnu/store/9ywpf5jc12svv04gvbx96j5z1kpllwn4-info-dir-builder"]
In ice-9/eval.scm:
505: 9 [#
In ice-9/psyntax.scm:
1107: 8 [expand-top-sequence ((begin # # # ...)) () ((top)) ...]
990: 7 [scan ((begin (use-modules # # ...) (define # #) ...)) () ...]
990: 6 [scan ((use-modules # # ...) (define # #) (define # #) ...) () ...]
279: 5 [scan ((# #) #(syntax-object *unspecified* # #)) () (()) ...]
In ice-9/boot-9.scm:
3622: 4 [process-use-modules ((#) (#) (#) (#))]
712: 3 [map #
3623: 2 [#
2903: 1 [resolve-interface (guix build utils) #:select ...]
In unknown file:
?: 0 [scm-error misc-error #f ...]
ERROR: In procedure scm-error:
ERROR: no code for module (guix build utils)
builder for `/gnu/store/0jxiph2hvmvakcj6gkz9d00a8ncma903-info-dir.drv' failed with exit code 1
Message part 2
(application/pgp-signature, inline)]
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Tue, 22 Aug 2017 08:43:01 GMT)
Full text
and
rfc822 format
available.
Message #8
received at 28144
full text
mbox
):
From:
ludo
To:
Christopher Baines
Cc:
28144
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Tue, 22 Aug 2017 10:41:55 +0200
Heya,
Christopher Baines
> I've had the following issue a few times now, it seems that somehow,
> the info-dir builder can be incorrectly generated, without the usual
> module import stuff.
> The most recent time this occurred, I worked around this by finding the
> guix package in the store which I thought was being used at the time,
> and explicitly garbage collected it (guix gc -d ...). I then rebuilt
> it, and this seemed to work around the problem. I was using the same
> guix package, pinned to an revision in a git repository.
> The builder starts with:
> (begin (use-modules (guix build utils)
> This is the error which you get:
> The following derivations will be built:
> /gnu/store/8qi10kwz4ghabdj5p7s252z11snvhhgf-profile.drv
> /gnu/store/0jxiph2hvmvakcj6gkz9d00a8ncma903-info-dir.drv
Could you check if the .drv has the right -L and -C flags for guile?
What commit was this on?
Looking at (guix profiles), what you describe Cannot Happen™ because
there’s a correct ‘with-imported-modules’ form there.
Thanks,
Ludo’.
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Tue, 22 Aug 2017 10:01:02 GMT)
Full text
and
rfc822 format
available.
Message #11
received at 28144
full text
mbox
):
From:
Christopher Baines
To:
ludo
Cc:
28144
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Tue, 22 Aug 2017 10:59:58 +0100
Message part 1
(text/plain, inline)]
On Tue, 22 Aug 2017 10:41:55 +0200
ludo
> Heya,
> Christopher Baines
> > I've had the following issue a few times now, it seems that somehow,
> > the info-dir builder can be incorrectly generated, without the usual
> > module import stuff.
> >
> > The most recent time this occurred, I worked around this by finding
> > the guix package in the store which I thought was being used at the
> > time, and explicitly garbage collected it (guix gc -d ...). I then
> > rebuilt it, and this seemed to work around the problem. I was using
> > the same guix package, pinned to an revision in a git repository.
> >
> >
> > The builder starts with:
> >
> > (begin (use-modules (guix build utils)
> >
> >
> > This is the error which you get:
> >
> > The following derivations will be built:
> > /gnu/store/8qi10kwz4ghabdj5p7s252z11snvhhgf-profile.drv
> > /gnu/store/0jxiph2hvmvakcj6gkz9d00a8ncma903-info-dir.drv
> Could you check if the .drv has the right -L and -C flags for guile?
> What commit was this on?
> Looking at (guix profiles), what you describe Cannot Happen™ because
> there’s a correct ‘with-imported-modules’ form there.
I've included the derivation contents below, I can't see the -L and -C
flags, so I'm guessing that they are missing.
As for what commit this is on, this particular occurance took place
when I was using my odd guix-pre-inst-env [1] script that
attempts to create an environment containing a particular version of
Guix, without letting anything from the surrounding environment creep
in, so I'm not really sure what code was in use at the time.
1:
Derive([("out","/gnu/store/fnfm2vv9khyxpsnr7ybn8h7ir2l3685y-info-dir","","")],[("/gnu/store/0l3zxcx0n31xal7jf1d981j377wh3nir-zlib-1.2.11.drv",["out"]),("/gnu/store/0ppzqkwl7ma4s3bz1wvc0s9crd0wbir7-guile-2.2.2.drv",["out"]),("/gnu/store/1wq563kgbhv26f99hq1d2ay7gw8qy3cq-libgc-7.6.0.drv",["out"]),("/gnu/store/2ryhk3mp55dshlgyj53a16x08ifqqlvw-bash-4.4.12.drv",["out"]),("/gnu/store/4rjl58s30zwiahl6ji7bbjxq30yyl9vl-texinfo-6.3.drv",["out"]),("/gnu/store/69b611ifkq1942zvf79d5sszpp8n9w38-libunistring-0.9.7.drv",["out"]),("/gnu/store/94hkgqjvsk689zzhdv9382kh2pkn7mrz-libltdl-2.4.6.drv",["out"]),("/gnu/store/c8zl2wq0jmahcjb2zdf5w5z1i2iangma-guix-gds-release_8.drv",["out"]),("/gnu/store/g2a46givk3s9jlchmq4m1fmnc25qh1c0-git-2.13.1.drv",["out"]),("/gnu/store/hdd0rz201djb0wis4jwrlnjp3kq1f9xq-nss-certs-3.31.drv",["out"]),("/gnu/store/lvkjr70rf8j355igip04z8iglxnl3mkk-guile-ssh-0.11.0.drv",["out"]),("/gnu/store/lw5qrzgh2yxpd58b722ph6f466sn51xm-gmp-6.1.2.drv",["out"]),("/gnu/store/m71zs1cgl0qiyrl5mzrjh60dsg757nvx-guile-2.0.14.drv",["out"]),("/gnu/store/rwgybvpsmrkh6rbz502ac6p6vkfr1jgm-gzip-1.8.drv",["out"]),("/gnu/store/vd7py9zp3s81mg3h0ppm5bkbdcgpn17w-libidn2-0.16.drv",["out"]),("/gnu/store/vk8fhc7x7kc4y6h6gy42idnawxabj8dv-guile2.2-gnutls-3.5.9.drv",["out"]),("/gnu/store/vl1vcbzgplncw4i3sfiglyy1n2ycnwwn-guile-json-0.6.0.drv",["out"]),("/gnu/store/whz1jbvs9ipgkslim63lqw7wdljxlmzg-nettle-3.3.drv",["out"]),("/gnu/store/xdbnmw3kizlx157l76cdb1w6y2kz7yhi-coreutils-8.27.drv",["out"]),("/gnu/store/xs8z1ycvdpmip7rx4xqs8qj56fdblgbk-less-487.drv",["out"]),("/gnu/store/xz2zfvzy2g55wgna0vpwd6zjwfmxn1ms-libtasn1-4.10.drv",["out"])],["/gnu/store/9ywpf5jc12svv04gvbx96j5z1kpllwn4-info-dir-builder"],"x86_64-linux","/gnu/store/3lsfrwlp1qa345x71yw5w49i2mpp0vxm-guile-2.0.14/bin/guile",["--no-auto-compile","/gnu/store/9ywpf5jc12svv04gvbx96j5z1kpllwn4-info-dir-builder"],[("allowSubstitutes","0"),("out","/gnu/store/fnfm2vv9khyxpsnr7ybn8h7ir2l3685y-info-dir"),("preferLocalBuild","1")])
Message part 2
(application/pgp-signature, inline)]
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Tue, 22 Aug 2017 10:42:01 GMT)
Full text
and
rfc822 format
available.
Message #14
received at 28144
full text
mbox
):
From:
ludo
To:
Christopher Baines
Cc:
28144
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Tue, 22 Aug 2017 12:41:26 +0200
Christopher Baines
> bin/guile",["--no-auto-compile","/gnu/store/9ywpf5jc12svv04gvbx96j5z1kpllwn4-info-dir-builder"]
Something is indeed wrong here. I have:
--8<---------------cut here---------------start------------->8---
$ cat /gnu/store/0gn0dxgg68w3yc4ywxp586z98h9l00j3-info-dir.drv
[...] bin/guile",["--no-auto-compile","-L","/gnu/store/l4jxniixlkqpy5aaxhgfp4xywsimd6p2-module-import","-C","/gnu/store/gj3ks9vi1ys3hgr1jzywjx2rq3dsmsbd-module-import-compiled","/gnu/store/m4kyr2isfskss2vkc7hvnbw786kd52v9-info-dir-builder"] [...]
--8<---------------cut here---------------end--------------->8---
Is it reproducible? Does “make clean-go && make” help? Is it Guile 2.2
or 2.0?
Thanks,
Ludo’.
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Tue, 22 Aug 2017 11:03:02 GMT)
Full text
and
rfc822 format
available.
Message #17
received at 28144
full text
mbox
):
From:
Christopher Baines
To:
ludo
Cc:
28144
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Tue, 22 Aug 2017 12:02:03 +0100
Message part 1
(text/plain, inline)]
On Tue, 22 Aug 2017 12:41:26 +0200
ludo
> Christopher Baines
> > bin/guile",["--no-auto-compile","/gnu/store/9ywpf5jc12svv04gvbx96j5z1kpllwn4-info-dir-builder"]
> Something is indeed wrong here. I have:
> --8<---------------cut here---------------start------------->8---
> $ cat /gnu/store/0gn0dxgg68w3yc4ywxp586z98h9l00j3-info-dir.drv
> [...]
> bin/guile",["--no-auto-compile","-L","/gnu/store/l4jxniixlkqpy5aaxhgfp4xywsimd6p2-module-import","-C","/gnu/store/gj3ks9vi1ys3hgr1jzywjx2rq3dsmsbd-module-import-compiled","/gnu/store/m4kyr2isfskss2vkc7hvnbw786kd52v9-info-dir-builder"]
> [...] --8<---------------cut
> here---------------end--------------->8---
> Is it reproducible? Does “make clean-go && make” help? Is it Guile
> 2.2 or 2.0?
Unfortunately, I've only run in to this when trying to get other stuff
done, and my approach for working around the problem has been to delete
the guix packages from the store to force them to be rebuilt.
I'd previously guessed that the ...-info-dir-builder was wrong, but
knowing that the command in the derivation is wrong is useful. If I
come across this again, I'll try to investigate further, but I don't
have a way of reproducing this at the moment.
Message part 2
(application/pgp-signature, inline)]
Added tag(s) unreproducible.
Request was from
ludo
to
control
(Tue, 22 Aug 2017 13:39:02 GMT)
Full text
and
rfc822 format
available.
bug closed, send any further explanations to
28144
Request was from
ludo
to
control
(Tue, 22 Aug 2017 13:39:02 GMT)
Full text
and
rfc822 format
available.
bug archived.
Request was from
Debbugs Internal Request
to
internal_control
(Wed, 20 Sep 2017 11:24:04 GMT)
Full text
and
rfc822 format
available.
Did not alter fixed versions and reopened.
Request was from
Debbugs Internal Request
to
internal_control
(Mon, 13 Nov 2017 09:44:02 GMT)
Full text
and
rfc822 format
available.
bug unarchived.
Request was from
ludo
to
control
(Mon, 13 Nov 2017 09:48:01 GMT)
Full text
and
rfc822 format
available.
Did not alter fixed versions and reopened.
Request was from
Debbugs Internal Request
to
internal_control
(Mon, 13 Nov 2017 09:48:01 GMT)
Full text
and
rfc822 format
available.
Severity set to 'important' from 'normal'
Request was from
ludo
to
control
(Mon, 13 Nov 2017 10:00:02 GMT)
Full text
and
rfc822 format
available.
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Mon, 13 Nov 2017 10:04:01 GMT)
Full text
and
rfc822 format
available.
Message #34
received at 28144
full text
mbox
):
From:
ludo
To:
Christopher Baines
Cc:
28144
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Mon, 13 Nov 2017 11:03:15 +0100
Hello,
Christopher Baines
> The following derivations will be built:
> /gnu/store/8qi10kwz4ghabdj5p7s252z11snvhhgf-profile.drv
> /gnu/store/0jxiph2hvmvakcj6gkz9d00a8ncma903-info-dir.drv
> Backtrace:
> In ice-9/boot-9.scm:
> 160: 18 [catch #t #
> In unknown file:
> ?: 17 [apply-smob/1 #
> In ice-9/boot-9.scm:
> 66: 16 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
> 432: 15 [eval # #]
> In ice-9/boot-9.scm:
> 2412: 14 [save-module-excursion #
> 4089: 13 [#
> 1734: 12 [%start-stack load-stack #
> 1739: 11 [#
> In unknown file:
> ?: 10 [primitive-load "/gnu/store/9ywpf5jc12svv04gvbx96j5z1kpllwn4-info-dir-builder"]
> In ice-9/eval.scm:
> 505: 9 [#
> In ice-9/psyntax.scm:
> 1107: 8 [expand-top-sequence ((begin # # # ...)) () ((top)) ...]
> 990: 7 [scan ((begin (use-modules # # ...) (define # #) ...)) () ...]
> 990: 6 [scan ((use-modules # # ...) (define # #) (define # #) ...) () ...]
> 279: 5 [scan ((# #) #(syntax-object *unspecified* # #)) () (()) ...]
> In ice-9/boot-9.scm:
> 3622: 4 [process-use-modules ((#) (#) (#) (#))]
> 712: 3 [map #
> 3623: 2 [#
> 2903: 1 [resolve-interface (guix build utils) #:select ...]
> In unknown file:
> ?: 0 [scm-error misc-error #f ...]
> ERROR: In procedure scm-error:
> ERROR: no code for module (guix build utils)
> builder for `/gnu/store/0jxiph2hvmvakcj6gkz9d00a8ncma903-info-dir.drv' failed with exit code 1
I’ve just experienced it!
As in your case, info-dir.drv contained no references to
module-import.drv or anything like that, and the ‘guile’ command line
lacked ‘-L …-module-import’.
Then I recompiled guix/profiles.go, and the problem went away.
My guess is that Guile 2.2.2 sometimes mishandles syntax parameters. In
this case, the syntax param used by ‘with-imported-modules’ was seen as
'() during macro expansion whereas it should have been '((guix build
utils)).
This is very similar to what we see in <
>.
Ludo’.
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Sun, 29 Apr 2018 16:05:01 GMT)
Full text
and
rfc822 format
available.
Message #37
received at 28144
full text
mbox
):
From:
ludo
To:
Fis Trivial
Cc:
28144
Subject:
Re: bug#31294: Failed building dependencies for guix.
Date:
Sun, 29 Apr 2018 18:04:28 +0200
Hi,
Fis Trivial
> Use following steps to reproduce:
> $ env -i bash --norc --noprofile --login
> $ guix environment guix
> Error message:
> The following derivations will be built:
> /gnu/store/c53mj37x2dnrgmrpagpv9l5c2ghly2hy-profile.drv
> /gnu/store/vpvx01j2qs31lfix131n1akwdjwf5s4z-xdg-desktop-database.drv
> /gnu/store/hr8xa2inki6lfbn8v9jfgmygbxygszs2-xdg-mime-database.drv
> /gnu/store/5y6mkv079xq5hnfajxfwky0kfc6ffy3p-info-dir.drv
> /gnu/store/95glrzk2y6p6b3z7hlmdignzzvxjvi2r-manual-database.drv
> Backtrace:
> 10 (primitive-load "/gnu/store/mpy5w5gprs1ymrl3kwhqwr2jvnk?")
> In ice-9/eval.scm:
> 721:20 9 (primitive-eval (begin (use-modules (guix build #) ?) ?))
> In ice-9/psyntax.scm:
> 1235:36 8 (expand-top-sequence ((begin (use-modules (# # ?) ?) ?)) ?)
> 1182:24 7 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
> 1182:24 6 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
> 285:10 5 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) ?)
> In ice-9/boot-9.scm:
> 3365:20 4 (process-use-modules _)
> 222:17 3 (map1 (((guix build utils)) ((srfi srfi-1)) ((srfi ?)) ?))
> 3366:31 2 (_ ((guix build utils)))
> 2791:6 1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ ?)
> In unknown file:
> 0 (scm-error misc-error #f "~A ~S" ("no code for modu?" ?) ?)
> ERROR: In procedure scm-error:
> no code for module (guix build utils)
> builder for `/gnu/store/5y6mkv079xq5hnfajxfwky0kfc6ffy3p-info-dir.drv' failed with exit code 1
This looks like <
>, which we don’t understand
yet.
(Most likely changing the Bash environment just led you to ignore
~/.config/guix/latest (or vice versa), thereby leading you to use a
different set of Guix compiled modules.)
Could you paste /gnu/store/5y6mkv079xq5hnfajxfwky0kfc6ffy3p-info-dir.drv ?
Also, could you post ~/.config/guix/latest/guix/profiles.go and
/run/current-system/profile/lib/guile/2.2/site-ccache/guix/profiles.go ?
(Perhaps you’ll need to gzip them to be sure.)
Thanks in advance,
Ludo’.
Merged
28144
31294
Request was from
ludo
to
control
(Sun, 29 Apr 2018 19:35:02 GMT)
Full text
and
rfc822 format
available.
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Tue, 01 May 2018 13:36:01 GMT)
Full text
and
rfc822 format
available.
Message #42
received at 28144
full text
mbox
):
From:
ludo
To:
Fis Trivial
Cc:
28144
Subject:
Re: bug#31294: Failed building dependencies for guix.
Date:
Tue, 01 May 2018 15:35:21 +0200
ludo
> It confirms that the bad code creates a
> list as its ‘modules’ field instead of '((guix build utils)).
> That’s clearly a Guile bug.
This miscompilation issue involves “syntax parameters” (because
‘with-imported-modules’ uses a syntax parameter), and it very likely has
to do with the thread-safety issue I describe here:
>.
Ludo’.
Merged
28144
31294
31367
Request was from
ludo
to
control
(Sun, 06 May 2018 15:24:01 GMT)
Full text
and
rfc822 format
available.
Merged
28144
31294
31367
32385
Request was from
Chris Marusich
to
control
(Fri, 10 Aug 2018 06:48:02 GMT)
Full text
and
rfc822 format
available.
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Thu, 03 Jan 2019 22:03:01 GMT)
Full text
and
rfc822 format
available.
Message #49
received at 28144
full text
mbox
):
From:
Ricardo Wurmus
To:
Ludovic Courtès
Cc:
28144
Fis Trivial
Subject:
Re: bug#31294: Failed building dependencies for guix.
Date:
Thu, 03 Jan 2019 23:01:41 +0100
Ludovic Courtès
> ludo
>> It confirms that the bad code creates a
>> list as its ‘modules’ field instead of '((guix build utils)).
>>
>> That’s clearly a Guile bug.
> This miscompilation issue involves “syntax parameters” (because
> ‘with-imported-modules’ uses a syntax parameter), and it very likely has
> to do with the thread-safety issue I describe here:
> <
>.
I just got this on my Fedora workstation in the office, where I use Guix
from a git checkout. I worked around this by moving “guix/profiles.go”
out of the way.
(Some people seem to be getting this with just “guix pull” now.)
--
Ricardo
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Mon, 28 Jan 2019 16:10:01 GMT)
Full text
and
rfc822 format
available.
Message #52
received at 28144
full text
mbox
):
From:
"Brant Gardner"
To:
28144
Subject:
info-dir ERROR: no code for module (guix build utils)
Date:
Mon, 28 Jan 2019 08:00:42 -0500
Message part 1
(text/plain, inline)]
I get this very reproducibly with 'guix pull', starting last week. This is on a pretty simple installation of GuixSD, no extra parameters or unusual environment. Is there anything I gather that would help?
Note: This only seems to happen for the non-root user executing 'guix pull' - so far it has not show for root.
--
Brant Gardner
Key: E9F7 AC51 99A7 C8DF 355D A751 7064 3C93 00C0 FBCE
Message part 2
(text/html, inline)]
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Mon, 28 Jan 2019 19:14:02 GMT)
Full text
and
rfc822 format
available.
Message #55
received at 28144
full text
mbox
):
From:
Ricardo Wurmus
To:
Brant Gardner
Cc:
28144
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Mon, 28 Jan 2019 19:57:45 +0100
Brant Gardner
> I get this very reproducibly with 'guix pull', starting last
> week. This is on a pretty simple installation of GuixSD, no extra
> parameters or unusual environment. Is there anything I gather that
> would help?
> Note: This only seems to happen for the non-root user executing 'guix
> pull' - so far it has not show for root.
That’s because every user has their own version of Guix. The root
user’s copy of Guix differs from that of your other user account.
Could you please tell us what “guix describe” and/or “guix --version”
say? This would help us figure out if we can do something to prevent
this.
You can get out of this problem by using a different variant of Guix to
run “guix pull”, e.g. ~/.config/guix/current-1-link/bin/guix pull.
--
Ricardo
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Mon, 28 Jan 2019 22:08:01 GMT)
Full text
and
rfc822 format
available.
Message #58
received at 28144
full text
mbox
):
From:
"Brant Gardner"
To:
"Ricardo Wurmus"
Cc:
28144
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Mon, 28 Jan 2019 17:04:43 -0500
As normal user:
~ % guix describe
guix describe: error: failed to determine origin
~ % guix --version
guix (GNU Guix) 0.16.0-8.7ba2b27
Copyright (C) 2018 the Guix authors
License GPLv3+: GNU GPL version 3 or later <
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
-----
Root gets very different answers, as you already pointed out I should expect:
root
Generation 3 Jan 27 2019 07:33:28 (current)
guix 4f8be6d
repository URL:
branch: master
commit: 4f8be6d905de0ca53275907cce37742287b51111
root
guix (GNU Guix) 4f8be6d905de0ca53275907cce37742287b51111
Copyright (C) 2019 the Guix authors
License GPLv3+: GNU GPL version 3 or later <
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
The path you indicated doesn't exist for me, can I use root's path to the guix executable to perform the pull and fix the normal user?
Thank you,
--
Brant Gardner
Key: E9F7 AC51 99A7 C8DF 355D A751 7064 3C93 00C0 FBCE
On Mon, Jan 28, 2019, at 12:57, Ricardo Wurmus wrote:
> Brant Gardner
> > I get this very reproducibly with 'guix pull', starting last
> > week. This is on a pretty simple installation of GuixSD, no extra
> > parameters or unusual environment. Is there anything I gather that
> > would help?
> >
> > Note: This only seems to happen for the non-root user executing 'guix
> > pull' - so far it has not show for root.
> That’s because every user has their own version of Guix. The root
> user’s copy of Guix differs from that of your other user account.
> Could you please tell us what “guix describe” and/or “guix --version”
> say? This would help us figure out if we can do something to prevent
> this.
> You can get out of this problem by using a different variant of Guix to
> run “guix pull”, e.g. ~/.config/guix/current-1-link/bin/guix pull.
> --
> Ricardo
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Tue, 29 Jan 2019 21:16:03 GMT)
Full text
and
rfc822 format
available.
Message #61
received at submit
full text
mbox
):
From:
swedebugia
To:
bug-guix
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Tue, 29 Jan 2019 22:14:58 +0100
Hi Brant
I moved your reply below. Please avoid top posting.
On 2019-01-28 23:04, Brant Gardner wrote:
> On Mon, Jan 28, 2019, at 12:57, Ricardo Wurmus wrote:
>>
snip
>> Could you please tell us what “guix describe” and/or “guix --version”
>> say? This would help us figure out if we can do something to prevent
>> this.
>>
>> You can get out of this problem by using a different variant of Guix to
>> run “guix pull”, e.g. ~/.config/guix/current-1-link/bin/guix pull.
> As normal user:
> ~ % guix describe
> guix describe: error: failed to determine origin
> ~ % guix --version
> guix (GNU Guix) 0.16.0-8.7ba2b27
> Copyright (C) 2018 the Guix authors
> License GPLv3+: GNU GPL version 3 or later <
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> -----
> Root gets very different answers, as you already pointed out I should expect:
> root
> Generation 3 Jan 27 2019 07:33:28 (current)
> guix 4f8be6d
> repository URL:
> branch: master
> commit: 4f8be6d905de0ca53275907cce37742287b51111
> root
> guix (GNU Guix) 4f8be6d905de0ca53275907cce37742287b51111
> Copyright (C) 2019 the Guix authors
> License GPLv3+: GNU GPL version 3 or later <
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> The path you indicated doesn't exist for me, can I use root's path to the guix executable to perform the pull and fix the normal user?
Yes if you make sure it and all directories above it is readable by the
normal user.
--
Cheers
Swedebugia
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Tue, 29 Jan 2019 21:19:01 GMT)
Full text
and
rfc822 format
available.
Message #64
received at submit
full text
mbox
):
From:
swedebugia
To:
bug-guix
Subject:
Re: bug#28144: info-dir ERROR: no code for module (guix build utils)
Date:
Tue, 29 Jan 2019 22:17:47 +0100
On 2019-01-29 22:14, swedebugia wrote:
> Hi Brant
> I moved your reply below. Please avoid top posting.
> On 2019-01-28 23:04, Brant Gardner wrote:
>> On Mon, Jan 28, 2019, at 12:57, Ricardo Wurmus wrote:
>>>
> snip
>>> Could you please tell us what “guix describe” and/or “guix --version”
>>> say? This would help us figure out if we can do something to prevent
>>> this.
>>>
>>> You can get out of this problem by using a different variant of Guix to
>>> run “guix pull”, e.g. ~/.config/guix/current-1-link/bin/guix pull.
>> As normal user:
>>
>> ~ % guix describe
>> guix describe: error: failed to determine origin
>>
>> ~ % guix --version
>> guix (GNU Guix) 0.16.0-8.7ba2b27
>> Copyright (C) 2018 the Guix authors
>> License GPLv3+: GNU GPL version 3 or later
>> <
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>>
>> -----
>>
>> Root gets very different answers, as you already pointed out I should
>> expect:
>>
>> root
>> Generation 3 Jan 27 2019 07:33:28 (current)
>> guix 4f8be6d
>> repository URL:
>> branch: master
>> commit: 4f8be6d905de0ca53275907cce37742287b51111
>>
>> root
>> guix (GNU Guix) 4f8be6d905de0ca53275907cce37742287b51111
>> Copyright (C) 2019 the Guix authors
>> License GPLv3+: GNU GPL version 3 or later
>> <
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>>
>>
>> The path you indicated doesn't exist for me, can I use root's path to
>> the guix executable to perform the pull and fix the normal user?
> Yes if you make sure it and all directories above it is readable by the
> normal user.
Also see this by fredrick in guix-help:
"I didn't have ~/.config/guix/current-1-link/bin/guix, so I ran
/var/guix/profiles/system-1-link/profile/bin/guix pull. That solved the
issue and I can now run "guix pull" and "guix environment guix"
again. Haven't tried "guix package -u" but I would assume that works as
well."
HTH
--
Cheers
Swedebugia
Information forwarded
to
bug-guix
bug#28144
; Package
guix
(Fri, 01 Feb 2019 20:00:02 GMT)
Full text
and
rfc822 format
available.
Message #67
received at 28144
full text
mbox
):
From:
Brant Gardner
To:
28144
Subject:
info-dir ERROR: no code for module (guix build utils)
Date:
Fri, 1 Feb 2019 13:59:43 -0600
Message part 1
(text/plain, inline)]
(Sorry for the top post from before, I've sorted that out now.)
Just wanted to report that using root's path for 'guix-command' worked immediately and my user
profile works fine now.
Thank you!
--
Brant Gardner
signature.asc
(application/pgp-signature, inline)]
Severity set to 'serious' from 'important'
Request was from
Ludovic Courtès
to
control
(Wed, 06 Feb 2019 20:58:02 GMT)
Full text
and
rfc822 format
available.
Merged
27476
27652
28144
31294
31367
31740
32385
34112
34319
Request was from
Ludovic Courtès
to
control
(Wed, 06 Feb 2019 20:58:03 GMT)
Full text
and
rfc822 format
available.
bug reassigned from package '
guix
' to '
guile
'.
Request was from
Ludovic Courtès
to
control
(Sat, 09 Feb 2019 22:12:01 GMT)
Full text
and
rfc822 format
available.
bug archived.
Request was from
Debbugs Internal Request
to
internal_control
(Fri, 15 Jan 2021 12:24:04 GMT)
Full text
and
rfc822 format
available.
This bug report was last modified 5 years and 100 days ago.
Previous
Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.