all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Truby <David.Truby@arm.com>
To: 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: Sun, 13 Oct 2019 15:54:47 +0000	[thread overview]
Message-ID: <AM6PR08MB37013DFED4D104499A3D58CFF3910@AM6PR08MB3701.eurprd08.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

Hi Guix,

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!)

Thanks
David Truby
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 2883 bytes --]

             reply	other threads:[~2019-10-13 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13 15:54 David Truby [this message]
2020-12-21 13:13 ` bug#37737: Documentation should mention that source checkout must be readable by the guixbuild group if guix-daemon is run from there zimoun
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=AM6PR08MB37013DFED4D104499A3D58CFF3910@AM6PR08MB3701.eurprd08.prod.outlook.com \
    --to=david.truby@arm.com \
    --cc=37737@debbugs.gnu.org \
    /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.