From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: 24670@debbugs.gnu.org, dian_cecht@zoho.com
Subject: bug#24670: Unexpected EOF reading a line (from guix pull) [forward]
Date: Thu, 13 Oct 2016 13:25:34 +0200 [thread overview]
Message-ID: <idjbmyoxzgx.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87y41s8ybd.fsf@we.make.ritual.n0.is>
> dian_cecht@zoho.com writes:
>
>> I'm just sending this to you since I think I might have figured out what is
>> happening, and I don't know how to respond to bugs via the mailing list.
>> Instruction on replying to bugs via the mailing list would be quite a help.
>>
>> Basically, /var/lib/guix/profiles/per-user/$USER/guix-profile doesn't exist. For
>> example, on the root account on my machine (I've run guix pull multiple times as
>> root, and even tried to install icecat as a normal user, plus running guix pull
>> several times as a normal user) $HOME/.guix-profile points to a nonexistent
>> file/directory, and where it points to
>> (/var/lib/guix/profiles/per-user/root/guix-profile) simply doesn't
>> exist.
The profile is created automatically the first time “guix package -i” is
run. This happens reliably for me on Fedora, CentOS, and on GuixSD. If
this doesn’t happen Gentoo I suspect the Gentoo package to be defective
(e.g. setting invalid permissions on certain directories).
>> I've
>> even tried to track down where a profile might exist within /gnu/store, but
>> "ls /gnu/store/*profile*" responds with:
This is not important. Anything Guix creates will be in the store.
This includes all profile generations.
I suggest installing Guix using the official binary package. See this
page for the tarballs and the install instructions:
https://www.gnu.org/software/guix/download/
~~ Ricardo
next prev parent reply other threads:[~2016-10-13 11:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 22:34 bug#24670: Unexpected EOF reading a line (from guix pull) dian_cecht
2016-10-11 23:07 ` ng0
[not found] ` <20161012070258.GA12645@khaalida>
2016-10-13 8:09 ` bug#24670: Unexpected EOF reading a line (from guix pull) [forward] ng0
2016-10-13 11:25 ` Ricardo Wurmus [this message]
2016-10-13 12:44 ` ng0
2016-10-14 0:10 ` ng0
2016-10-14 10:08 ` Ricardo Wurmus
2016-10-14 11:22 ` ng0
2016-10-14 11:53 ` Ricardo Wurmus
2016-10-14 12:21 ` ng0
2016-10-14 13:17 ` Ricardo Wurmus
2016-10-14 14:21 ` ng0
2016-10-14 14:33 ` ng0
2016-10-14 14:37 ` Ricardo Wurmus
2016-10-14 0:21 ` bug#24670: bug #24670: Unexpected EOF reading a line (from guix pull) dian_cecht
2016-10-14 10:06 ` Ricardo Wurmus
2016-10-16 4:57 ` dian_cecht
2016-10-16 10:23 ` Ricardo Wurmus
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=idjbmyoxzgx.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=24670@debbugs.gnu.org \
--cc=dian_cecht@zoho.com \
--cc=ng0@we.make.ritual.n0.is \
/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).