unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "BlueT - Matthew Lien - 練喆明" <bluet@bluet.org>
Cc: bug-guix@gnu.org
Subject: Re: [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install.
Date: Sat, 06 Jul 2013 15:36:39 +0200	[thread overview]
Message-ID: <878v1jstco.fsf@gnu.org> (raw)
In-Reply-To: <51D768DE.90403@BlueT.org> ("BlueT - Matthew Lien - \=\?utf-8\?B\?57e05ZaG5piOIidz\?\= message of "Sat, 06 Jul 2013 08:46:22 +0800")

"BlueT - Matthew Lien - 練喆明" <bluet@bluet.org> skribis:

> On 2013年07月06日 04:29, Ludovic Courtès wrote:
>> Yeah, the latest and greatest Autotools are needed for development.
>> (This will no longer be a problem once you have Guix installed because
>> that’s what the distro has: the latest and greatest.  :-))
>
> I understand that >=1.12 might be better than 1.11, but is there
> something we can do to make it support both?

Not easily.  I have no interest in supporting old versions of Automake,
given that Automake is only needed for developers (you don’t need it
when building from a tarball), and developers can figure out how to
install the right version.  :-)

>> The test log has a lot of these:
>>
>>> suspicious ownership or permission on `/home/bluet/guix-0.2/test-tmp/store/fcj4d6x41bmsp235cwm8zhzpc782xbw4-module-import'; rejecting this build output
>>> @ build-failed /home/bluet/guix-0.2/test-tmp/store/15ifzzvqq54r7n891s47q5rai5l1pfhc-module-import.drv - 1 suspicious ownership or permission on `/home/bluet/guix-0.2/test-tmp/store/fcj4d6x41bmsp235cwm8zhzpc782xbw4-module-import'; rejecting this build output
>>
>> The code that leads to this error is this:
>>
>>     /* Check that the output is not group or world writable,
>>        as that means that someone else can have interfered
>>        with the build.  Also, the output should be owned by
>>        the build user. */
>>     if ((!S_ISLNK(st.st_mode) && (st.st_mode & (S_IWGRP | S_IWOTH))) ||
>>         (buildUser.enabled() && st.st_uid != buildUser.getUID()))
>>         throw BuildError(format("suspicious ownership or permission on `%1%'; rejecting this build output") % path);
>>
>> Could you check the permissions on these files?
>
> Those files are not exist anymore after the `make check`, as they're
> created in test-tmp/ for the test only.
>
> After some tries, I can see
> -r--r--r-- 1 bluet bluet 899 Jan  1  1970
> /home/bluet/guix-0.2/test-tmp/store/15ifzzvqq54r7n891s47q5rai5l1pfhc-module-import.drv

Hmm that looks good.

> but didn't catch the
> /home/bluet/guix-0.2/test-tmp/store/fcj4d6x41bmsp235cwm8zhzpc782xbw4-module-import
>
>> What does the ‘umask’ command show?
>
> bluet@GuixOnUbuntu64:~/guix-0.2$ umask
> 0002

Could you run this from the build directory:

  rm -rf test-tmp && umask 0022 && make check

With umask == 0002, the daemon can end up creating group-writable files,
which then triggers the above error.

TIA,
Ludo’.

  parent reply	other threads:[~2013-07-06 13:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 18:31 [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install BlueT - Matthew Lien - 練喆明
2013-07-05 20:29 ` Ludovic Courtès
2013-07-06  0:46   ` BlueT - Matthew Lien - 練喆明
2013-07-06  5:11     ` alirioeyng
2013-07-07 23:10       ` BlueT - Matthew Lien - 練喆明
2013-07-06 13:36     ` Ludovic Courtès [this message]
2013-07-07 23:25       ` BlueT - Matthew Lien - 練喆明
2013-07-08 11:55         ` 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=878v1jstco.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bluet@bluet.org \
    --cc=bug-guix@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).