From: ludo@gnu.org (Ludovic Courtès)
To: mhw@netris.org
Cc: 17083-done@debbugs.gnu.org, guix-devel@gnu.org
Subject: bug#17083: ‘union-build’ does not handle collisions between a leaf and a sub-tree
Date: Wed, 02 Apr 2014 23:43:43 +0200 [thread overview]
Message-ID: <87ioqrflv4.fsf@gnu.org> (raw)
In-Reply-To: <87siq7y96h.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 24 Mar 2014 15:15:34 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> On the Loongson 3A machine, I finished building all the packages from
>> core-updates that I use in my profile, and then tried installing them.
>> I got this:
>>
>> In /gnu/store/9sqx55rgygyrcyg350cfqwy8wqb4fr69-module-import/guix/build/union.scm:
>> 226: 1 [loop # #]
>> In unknown file:
>> ?: 0 [mkdir "/gnu/store/c30bsax58scw5qwcnbma16k6z88s1lh3-profile/./include" ...]
>>
>> ERROR: In procedure mkdir:
>> ERROR: In procedure mkdir: File exists
>> builder for `/gnu/store/17w6kggffh79drmmrdnxy1yhgr6p2in5-profile.drv' failed with exit code 1
>>
>> The problem turns out to be that 'libffi' makes 'include' a symlink to
>> 'lib/libffi-3.0.13/include', and union.scm cannot cope with conflicts
>> between a directory and a symlink.
>
> Ouch, good catch.
This is fixed with the new union.scm (commit 1212999.)
> I’ve come up with a test that reproduces it:
This test was actually bogus, so I committed a correct one (commit
a53a9ae.)
Thanks!
Ludo’.
prev parent reply other threads:[~2014-04-02 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 6:07 libffi cannot be installed in user profile in core-updates Mark H Weaver
2014-03-24 9:52 ` Sree Harsha Totakura
2014-03-24 13:15 ` Mark H Weaver
2014-03-24 14:15 ` bug#17083: ‘union-build’ does not handle collisions between a leaf and a sub-tree Ludovic Courtès
2014-04-02 21:43 ` Ludovic Courtès [this message]
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=87ioqrflv4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=17083-done@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.