all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: fis trivial <ybbs.daans@hotmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: "32439@debbugs.gnu.org" <32439@debbugs.gnu.org>
Subject: bug#32439: guix pull as root generates too many errors.
Date: Tue, 14 Aug 2018 21:07:04 +0000	[thread overview]
Message-ID: <BLUPR16MB050021DA0A74FC7A4BC14C7492380@BLUPR16MB0500.namprd16.prod.outlook.com> (raw)
In-Reply-To: <20180814203608.GA16340@jasmine.lan>


Leo Famulari writes:

> On Tue, Aug 14, 2018 at 07:41:14PM +0000, fis trivial wrote:
>> Running guix pull -l as root user generates many warnings and errors. I
>> attached the first 1000 lines of stderr logging in this mail.
>>
>
>> ;;; WARNING: loading compiled file /root/.config/guix/current-17-link/lib/guile/2.2/site-ccache/guix/ui.go failed:
>> ;;; ERROR: In procedure make_objcode_from_file: bad header on object file: "\x7fELF\x02\x01\x01??\x00\x00\x00\x00\x00\x00\x00\x00"
>
> I'm not an expert on Guile or the new `guix pull`. However, I think that
> `guix pull` takes its Guile from the environment, because `guix pull -l`
> doesn't work for me when there is no Guile in PATH.
>
> Those errors look like a mismatch between Guile versions 2.0 and 2.2.
> Which Guile do you have available in the environment where you see that
> error?

As root user, it's guile@2.0.14. Indeed, installing guile@2.2.4 from Guix fixes
the problem. Thanks for your insight. :)

I thought Guix is self-contained, so are you implying that Guix itself is not
reproducible?  Is it reasonable to request making Guix self-contained?

Thanks.

--
Jiaming

  reply	other threads:[~2018-08-14 21:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 19:41 bug#32439: guix pull as root generates too many errors fis trivial
2018-08-14 20:36 ` Leo Famulari
2018-08-14 21:07   ` fis trivial [this message]
2018-08-16 21:06     ` Leo Famulari
2018-08-20  9:45     ` Ludovic Courtès
2018-08-20 19:29       ` fis trivial
2018-08-21  9:49         ` Ludovic Courtès

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=BLUPR16MB050021DA0A74FC7A4BC14C7492380@BLUPR16MB0500.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=32439@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.