From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: bug#24670: Unexpected EOF reading a line (from guix pull) [forward] Date: Thu, 13 Oct 2016 08:09:42 +0000 Message-ID: <87y41s8ybd.fsf@we.make.ritual.n0.is> References: <20161011223407.GA31313@khaalida> <8760oycwno.fsf@we.make.ritual.n0.is> <20161012070258.GA12645@khaalida> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46506) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bub6Y-0003cL-98 for bug-guix@gnu.org; Thu, 13 Oct 2016 04:11:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bub6T-000154-VK for bug-guix@gnu.org; Thu, 13 Oct 2016 04:11:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:47507) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bub6T-00014v-Rb for bug-guix@gnu.org; Thu, 13 Oct 2016 04:11:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bub6T-00035O-Kz for bug-guix@gnu.org; Thu, 13 Oct 2016 04:11:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20161012070258.GA12645@khaalida> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: dian_cecht@zoho.com, 24670@debbugs.gnu.org The following message has been forwarded to this bug again. There are some details removed which will not be useful to anyone but me - I don't think many people are running Gentoo here so I was told to remove the output of "emerge --info" as this is only useful to recreate a somewhat similar system. To reply to your bug (as I wrote before), just reply to the initial info message or.. If this doesn't get sorted out use $bugid@debbugs.gnu.org. More on this can be found here: https://debbugs.gnu.org/Developer.html which took me long enough myself. The debbugs team of gnu should really document this more visible. 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. I've > even tried to track down where a profile might exist within /gnu/store, but > "ls /gnu/store/*profile*" responds with: > > ls -1 /gnu/store/*profile* > 4.0K /gnu/store/ba2bkragdwyb1yhlsqq8idvz7ps4bnqk-profile-builder > 4.0K /gnu/store/ccbgqxinaimvy0nxi7b9gy1000z533yg-profile-builder > 4.0K /gnu/store/giplwz9pldknh5v1zmjjxmqcxy2qscai-profile.drv > 4.0K /gnu/store/h2l6kjwdbdfv4k47ibmgc270p9mbf9d8-profile.drv > 8.0K /gnu/store/lzmyqhnccl8rppjwiih08xh2wamqg9x3-profiles.scm > 4.0K /gnu/store/mrj87096jj84x5asicyqmkicfbx0zxwm-profile.drv > 4.0K /gnu/store/xavk99lizyl83qwqnpirjr9ck68b2wnf-profile-builder > > and when I look at what I get from the binary tarball from the website, the > profile symlinks seem to do as follows (note I extracted this as a normal user > into $HOME, so dirs might not be exactly the same): > > var/guix/profiles/per-user/root/guix-profile -> /var/guix/profiles/per-user/root/guix-profile-1-link > var/guix/profiles/per-user/root/guix-profile-1-link -> /gnu/store/6wz49d3pxf1dqc0rzmigsp6yr9abbz1x-profile > > Note the lack of any suffix on the last line; this simply isn't created via guix > pull nor by the ebuild, and if guix is simply sourcing these files, this /might/ > explain why this error keeps coming up. It also means that Guix is slightly > broken because it doesn't handle this file missing in any reasonable manner (I'd > consider "sane" to be spitting out an error message or, preferably, generating a > reasonable symlink and related file tree, explaining that it did so and why, > then proceeding (or giving the user the option to proceed).