[darcs-devel] [issue595] get to remote repo fails when upstream directory permisions are restrictive

system bugs at darcs.net
Sat Jan 19 01:44:12 UTC 2008


New submission from system <mark at stosberg.com>:

I'll be 'sending' a test to bugs directory shortly which illustrates the
following weakness of darcs: 

darcs "get" may fail with a permissions error even when the current directory
has sufficient permissions, and the remote directory has sufficient permissions,
as well, but a parent directory of the current repo has restrictive permissions. 

This is the case on some web-server setups where "/home" has restrictive
permissions, but people may run darcs from "/home/user/www". 

By using "strace", I can see that the failure point is when "chdir" is called
with the full path of the current directory. An example failure message looks
like this:

darcs: /home/mark/Haskell/darcs-unstable-hashed/bugs/tmp_restrictive/liberal:
setCurrentDirectory: permission denied (Permission denied)

It seems the fix would have to involve avoiding the "chdir" call to the full
path of the current repo. 

The bug is triggered in darcs 1.0.9 and a current build of Darcs2.

----------
messages: 2565
nosy: beschmi, droundy, kowey, system, tommy
priority: bug
status: unread
title: get to remote repo fails when upstream directory permisions are restrictive
topic: Darcs2

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue595>
__________________________________


More information about the darcs-devel mailing list