On Tue, Oct 26, 2010 at 8:56 AM, Thijs Koerselman <[email protected]> wrote: > On Sat, Oct 23, 2010 at 6:34 PM, Thijs Koerselman > <[email protected]> wrote: >> >> Hi, >> I'm using a script to install some rocks in a sandbox environment. >> Whenever I run the script a second time some of the rocks get in trouble. To >> me it looks like they extract their tmp files to the same directory in >> /private/tmp. I get asked whether I want to overwrite the rockspec and then >> regardless of my answer, the error below occurs. This doesn't seem to happen >> for all rocks, but in my case only luadoc and lualogging. I'm installing >> these rocks without sudo /root privileges. > > I have a better idea of where the problem is now. For example with > lualogging. During install it creates a directory like: > /private/tmp/luarocks_luarocks-manifest-http___luarocks.org_repositories_rocks-695/ > The second time around there is a conflict with this.
This is weird, because the directory should be deleted when luarocks finishes. *And* the directory has the numeric process id in its name specifically to avoid those conflicts... I'll investigate this further when I get the time. Thanks for the reports, -- Hisham _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
