bug in compute-guix-derivation

  • Done
  • quality assurance status badge
Details
2 participants
  • Marco van Hulten
  • Andreas Enge
Owner
unassigned
Submitted by
Marco van Hulten
Severity
normal
M
M
Marco van Hulten wrote on 25 Feb 2019 14:32
(address . bug-guix@gnu.org)
20190225143258.0f64f7c7@gfi063209.klientdrift.uib.no
Hello,

I could not 'guix pull' on my recently installed Guix (on Ubuntu 18.04).

Pull log attached.

—Marco
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
Building from this channel:
Computing Guix derivation for 'x86_64-linux'... Backtrace:
In ice-9/boot-9.scm:
2887:24 19 (_)
222:29 18 (map1 (((guix i18n)) ((guix gexp)) ((guix sets)) ((?)) ?))
222:29 17 (map1 (((guix gexp)) ((guix sets)) ((guix utils)) (#) ?))
222:29 16 (map1 (((guix sets)) ((guix utils)) ((guix store)) (#) ?))
222:29 15 (map1 (((guix utils)) ((guix store)) ((guix config)) # ?))
222:29 14 (map1 (((guix store)) ((guix config)) ((guix #)) ((?)) ?))
222:29 13 (map1 (((guix config)) ((guix packages)) ((guix #)) # ?))
222:29 12 (map1 (((guix packages)) ((guix profiles)) ((guix #)) ?))
222:17 11 (map1 (((guix profiles)) ((guix derivations)) ((# #)) ?))
2800:17 10 (resolve-interface (guix profiles) #:select _ #:hide _ # ?)
In ice-9/threads.scm:
390:8 9 (_ _)
In ice-9/boot-9.scm:
2726:13 8 (_)
In ice-9/threads.scm:
390:8 7 (_ _)
In ice-9/boot-9.scm:
2994:20 6 (_)
2312:4 5 (save-module-excursion #<procedure 1c4e180 at ice-9/boo?>)
3014:26 4 (_)
In unknown file:
3 (primitive-load-path "guix/profiles" #<procedure 1c9524?>)
In ./guix/profiles.scm:
1773:23 2 (_)
In ./guix/utils.scm:
661:47 1 (xdg-directory _ "/.config" #:ensure? _)
In unknown file:
0 (getpw 96252)

ERROR: In procedure getpw:
In procedure getpw: entry not found
guix pull: error: You found a bug: the program '/gnu/store/i49yy9zlv7h1bsds96ld7fhgni9ycvr6-compute-guix-derivation'
failed to compute the derivation for Guix (version: "5c06a185038ec7e114b71bafdbcab42cca9abcfb"; system: "x86_64-linux";
host version: "9d391ccd107e3d7f3759bc2596e5f4e5670a8683"; pull-version: 1).
Please report it by email to <bug-guix@gnu.org>.
M
M
Marco van Hulten wrote on 25 Feb 2019 17:17
fixed
(address . 34649@debbugs.gnu.org)
20190225171714.2e678ef0@gfi063209.klientdrift.uib.no
The problem disappeared. Either user error or bug was fixed since
reporting.

—Marco
M
M
Marco van Hulten wrote on 25 Feb 2019 17:19
close 34649
(address . 34649@debbugs.gnu.org)
20190225171916.2c181a47@gfi063209.klientdrift.uib.no
close 34649
A
A
Andreas Enge wrote on 25 Feb 2019 18:55
(name . Marco van Hulten)(address . Marco.Hulten@uib.no)(address . 34649-done@debbugs.gnu.org)
20190225175516.GB25374@jurong
Control messages should be sent to the debbugs server, not to a specific
bug addess.

Closing a bug is simpler, just send a message to xyz-done@debbugs.gnu.org.

Andreas
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 34649@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 34649
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch