[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install.
From: |
Ludovic Courtès |
Subject: |
Re: [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install. |
Date: |
Sat, 06 Jul 2013 15:36:39 +0200 |
User-agent: |
Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux) |
"BlueT - Matthew Lien - 練喆明" <address@hidden> 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?
>
> address@hidden:~/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’.