From: Leo Famulari <leo@famulari.name>
To: fis trivial <ybbs.daans@hotmail.com>
Cc: "32439@debbugs.gnu.org" <32439-done@debbugs.gnu.org>
Subject: bug#32439: guix pull as root generates too many errors.
Date: Thu, 16 Aug 2018 17:06:22 -0400 [thread overview]
Message-ID: <20180816210622.GB29448@jasmine.lan> (raw)
In-Reply-To: <BLUPR16MB050021DA0A74FC7A4BC14C7492380@BLUPR16MB0500.namprd16.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On Tue, Aug 14, 2018 at 09:07:04PM +0000, fis trivial wrote:
> As root user, it's guile@2.0.14. Indeed, installing guile@2.2.4 from Guix fixes
> the problem. Thanks for your insight. :)
Great!
By the way, Guix *does* work with Guile 2.0. The messages you saw should
not prevent using Guix. Guix was using Guile 2.0, which was finding some
pre-compiled Guile 2.2 objects. Guile 2.0 printed those messages to say
that it did not recognize the precompiled objects and had to recompile
them.
> 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?
Guix is not self-contained. Its dependencies are listed in the manual:
https://www.gnu.org/software/guix/manual/en/html_node/Requirements.html
As for whether or not it could or should be self-contained, answering
that is outside of my expertise.
I think there is no bug to fix here, right? Please re-open the bug if I
am wrong.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-16 21:07 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
2018-08-16 21:06 ` Leo Famulari [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180816210622.GB29448@jasmine.lan \
--to=leo@famulari.name \
--cc=32439-done@debbugs.gnu.org \
--cc=ybbs.daans@hotmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).