From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#32183: New =?UTF-8?Q?=E2=80=98guix_?= =?UTF-8?Q?pull=E2=80=99?= /root/.config/current/bin/guix: Permission denied Date: Sun, 02 Sep 2018 22:04:32 +0200 Message-ID: <87efeb64z3.fsf@gnu.org> References: <20180717085541.g6nuycopf5kxoin7@thebird.nl> <20180723222855.osvahab6uo677nfd@thebird.nl> <87tvomxfzy.fsf@gnu.org> <871sacats5.fsf@gnu.org> <20180902142855.llzongao3kraunys@thebird.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36546) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fwYcM-00051Q-JZ for bug-guix@gnu.org; Sun, 02 Sep 2018 16:05:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fwYcL-0005WI-BH for bug-guix@gnu.org; Sun, 02 Sep 2018 16:05:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:38333) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fwYcJ-0005V3-8P for bug-guix@gnu.org; Sun, 02 Sep 2018 16:05:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fwYcJ-0007tx-2D for bug-guix@gnu.org; Sun, 02 Sep 2018 16:05:03 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <20180902142855.llzongao3kraunys@thebird.nl> (Pjotr Prins's message of "Sun, 2 Sep 2018 16:28:55 +0200") 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: Pjotr Prins Cc: 32183-done@debbugs.gnu.org Hi, Pjotr Prins skribis: > On Sun, Sep 02, 2018 at 03:55:06PM +0200, Ludovic Court=C3=A8s wrote: >> Hi Pjotr, >>=20 >> What was the outcome of this bug? >>=20 >> https://bugs.gnu.org/32183 >>=20 >> If it wasn=E2=80=99t resolved, could you answer the questions below? > > I still face this problem on one or two machines. I am running a > standard setup. Not sure what it is. > > But since no one else is reporting I think it must be because I am > running some earlier tree checkout too for deployment. Something got > messed up. OK. Do reopen it if it shows up again. Thanks, Ludo=E2=80=99.