From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#39194: help for non-root users to start using Date: Sun, 19 Jan 2020 23:12:43 +0100 Message-ID: <87blqzqen8.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:49494) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itIoZ-0001aY-MA for bug-guix@gnu.org; Sun, 19 Jan 2020 17:13:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1itIoY-00061j-Fv for bug-guix@gnu.org; Sun, 19 Jan 2020 17:13:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:38046) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1itIoY-00061Z-Cl for bug-guix@gnu.org; Sun, 19 Jan 2020 17:13:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1itIoY-0005k2-9C for bug-guix@gnu.org; Sun, 19 Jan 2020 17:13:02 -0500 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: (Matt Wette's message of "Sun, 19 Jan 2020 09:48:02 -0800") 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-mx.org@gnu.org Sender: "bug-Guix" To: Matt Wette Cc: 39194-done@debbugs.gnu.org Hi Matt, Matt Wette skribis: > This guix-1.0.1 on x86_64 Fedora 30. > > After installing as root, it's not clear from the manual how users > should start. > I found out "guix pull" is the right thing. > Maybe add that to the manual? (Or add a "guix init" command.) =E2=80=9Cguix pull=E2=80=9D brings you an up-to-date Guix, which is a good = thing, but you don=E2=80=99t _have_ to run it to get started. > Here is the error that I get w/o "guix pull": > > [mwette@localhost ~]$ guix install hello > Backtrace: > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 8 (primitive= -load "/usr/local/bin/guix") > In guix/ui.scm: > =C2=A0 1813:12=C2=A0 7 (run-guix-command _ . _) > In ice-9/boot-9.scm: > =C2=A0=C2=A0=C2=A0 829:9=C2=A0 6 (catch _ _ # ?) > =C2=A0=C2=A0=C2=A0 829:9=C2=A0 5 (catch _ _ # ?) > In guix/scripts/package.scm: > =C2=A0=C2=A0 948:10=C2=A0 4 (_) > In guix/status.scm: > =C2=A0=C2=A0=C2=A0 768:4=C2=A0 3 (call-with-status-report _ _) > In guix/scripts/package.scm: > =C2=A0=C2=A0 956:14=C2=A0 2 (_) > In guix/build/syscalls.scm: > =C2=A0 1127:14=C2=A0 1 (call-with-file-lock/no-wait _ # ?) > In ice-9/boot-9.scm: > =C2=A0=C2=A0=C2=A0 777:6=C2=A0 0 (throw "open-file" "~A: ~S" ("No such fi= le or direc?" ?) ?) > > ice-9/boot-9.scm:777:6: In procedure throw: > In procedure throw: Wrong type argument in position 1: open-file I believe this is fixed by commit 7842ddcbc118cbc2799e22651732b7cdc06b93ee. Here=E2=80=99s my understanding of what happened: 1. You=E2=80=99re running guix-daemon 1.0.1, which lacks the fix for (aka. CVE-2019-18192). 2. As =E2=80=9Cmwette=E2=80=9D, you ran =E2=80=98guix pull=E2=80=99 and o= btained a new =E2=80=98guix=E2=80=99, which you then used in =E2=80=98guix install hello=E2=80=99 above. 3. That new Guix contains the new profile locking mechanism that threw the exception we see above. That exception is because it failed to create the lock file (=E2=80=9CNo such file or directory=E2=80=9D), an= d that in turn is because /var/guix/profiles/per-user/mwette didn=E2=80=99t exist yet. /=E2=80=A6/per-user/mwette didn=E2=80=99t exist because it was the fir= st time you ran =E2=80=98guix install=E2=80=99 as =E2=80=9Cmwette=E2=80=9D, and be= cause guix-daemon lacks the fix mentioned above that would create upon first connection. QED =E2=96=A0 :-) Thanks for your report! Ludo=E2=80=99.