From: zimoun <zimon.toutoune@gmail.com>
To: David Truby <David.Truby@arm.com>
Cc: 37737@debbugs.gnu.org
Subject: bug#37737: Documentation should mention that source checkout must be readable by the guixbuild group if guix-daemon is run from there
Date: Mon, 21 Dec 2020 14:13:53 +0100 [thread overview]
Message-ID: <86r1nj9u9a.fsf@gmail.com> (raw)
In-Reply-To: <AM6PR08MB37013DFED4D104499A3D58CFF3910@AM6PR08MB3701.eurprd08.prod.outlook.com> (David Truby's message of "Sun, 13 Oct 2019 15:54:47 +0000")
Hi,
Sorry for the long delay.
On Sun, 13 Oct 2019 at 15:54, David Truby <David.Truby@arm.com> wrote:
> When following the Contributing section of the manual in my home
> directory, I was unable to use the built guix to do anything as I hit
> upon a message saying "error: failed to run download program
> '/home/truby/src/guix/scripts/guix': Permission denied"
>
> After some debugging I realised this was because my home directory was
> not world readable. I think to avoid other people having this problem
> it might be worth mentioning in the manual that the source directory
> needs to be readable by the guixbuild group for the users in that
> group to be able to actually build anything. (In hindsight, this seems
> obvious to me. But it wasn't when I first ran through that section of
> the manual!)
Since it appears to me obvious, I am not sure to see how to improve.
Because you ran into the problem, do you want to give a try in rewording
somewhere in the manual?
All the best,
simon
next prev parent reply other threads:[~2020-12-21 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 15:54 bug#37737: Documentation should mention that source checkout must be readable by the guixbuild group if guix-daemon is run from there David Truby
2020-12-21 13:13 ` zimoun [this message]
2021-01-11 13:31 ` zimoun
2021-03-24 21:47 ` zimoun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r1nj9u9a.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=37737@debbugs.gnu.org \
--cc=David.Truby@arm.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.