unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25089@debbugs.gnu.org
Subject: bug#25089: Can't build source derivations with Guix 0.11.0-4.1f41
Date: Mon, 5 Dec 2016 20:14:24 -0500	[thread overview]
Message-ID: <20161206011424.GA21206@jasmine> (raw)
In-Reply-To: <87r35n5rrn.fsf@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 1739 bytes --]

On Sun, Dec 04, 2016 at 10:05:48PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> The main difference is that downloads are performed by the daemon itself
> (via the ‘guix perform-download’ internal command), which was not the
> case before (see <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22774#13>.)

Okay, I'll investigate this change.

> > Starting download of /gnu/store/hbdalsf5lpf01x4dcknwx6xbn6n5km6k-hello-2.10.tar.gz
> > From http://ftpmirror.gnu.org/hello/hello-2.10.tar.gz...
> > following redirection to `http://mirrors.ibiblio.org/pub/mirrors/gnu/ftp/gnu/hello/hello-2.10.tar.gz'...
> > following redirection to `http://mirrors.ibiblio.org/gnu/ftp/gnu/hello/hello-2.10.tar.gz'...
> > ERROR: In procedure open-file: Permission denied: "/gnu/store/hbdalsf5lpf01x4dcknwx6xbn6n5km6k-hello-2.10.tar.gz"
> 
> It should definitely have write permission on the output file.
> 
> Could you ‘strace -f’ guix-daemon or something like that to see under
> what UID ‘guix perform-download’ executes?  It’s expected to be running
> as a build user, but not in a chroot.

It does appear to be running as a build user.

I realized that I can, in fact, build source derivations, but I can't
--check them. I use `guix build --source --check foo` to make sure a
package has the right source URL.

So my original report was misleading, sorry.

I can reproduce this on GuixSD, after reconfiguring my system based on
8243951ef1b9d (gnu: guix: Update development snapshot.).

Can you try reproducing it like this?

$ guix build hello --source && guix build hello --source --check

I've attached gzip compressed strace logs, created with `strace -f -p
PID -o FILE`.

[-- Attachment #1.2: log-bad-0.11.0-7.e11c.gz --]
[-- Type: application/x-gunzip, Size: 53023 bytes --]

[-- Attachment #1.3: log-good-0.11.0-3.7ca3.gz --]
[-- Type: application/x-gunzip, Size: 103462 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2016-12-06  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02  8:10 bug#25089: Can't build source derivations with Guix 0.11.0-4.1f41 Leo Famulari
2016-12-04 21:05 ` Ludovic Courtès
2016-12-06  1:14   ` Leo Famulari [this message]
2016-12-07  9:46     ` Ludovic Courtès
2017-01-11 16:22 ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161206011424.GA21206@jasmine \
    --to=leo@famulari.name \
    --cc=25089@debbugs.gnu.org \
    --cc=ludo@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).