As posted on darcs-users@, there's a regression since darcs-2.0.2 when pulling 
from a local (filesystem) repository where the first component of the source 
repository's path differs from the first component of the the target 
repository's path, i.e.:

$ mkdir /var/tmp/foo
$ cd /var/tmp/foo
$ darcs init
$ cd /tmp
$ darcs get /var/tmp/foo
Finished getting.
$ cd foo
$ darcs pull
darcs failed:  Not a repository: var/tmp/foo (var/tmp/foo/_darcs/inventory:
+openBinaryFile: does not exist (No such file or directory))


I didn't yet find the code to blame, but it might be in the vicinity of 
FileName.lhs or any module that's using it (which is pretty much anything).

Hi Dmitry,  May I interest you in this one?  I think it may be related to the
issue950 fixes or the subsequent cleanups.  Sorry about this!  Definitely a
documentation or lack-of-tests problem on my part.

I believe this is now fixed.  Thanks for the report!

David

I take that back.  I fixed it before lunch, but now I see that I didn't record
before pushing... the fix will arrive soon!  :)

David

David, did you forget to record and push this? It still doesn't work here.

Attached is a little shell script that does the same stuff with repodirs /a 
and /b (must be run as root, and it removes /a and /b after the test, so be 
careful).

Attachments

• ms.sh

I can confirm that Matthias's test fails with
darcs failed:  Not a repository: a (a/_darcs/inventory: openBinaryFile: does not
exist (No such file or directory))

Dmitry or David, comments?

P.S. I tried to make this more general by prepending PWD, but then the test
passed :-/

I am not working on this one. At least until David comments.

Regards,
  Dmitry

On Sun, Sep 07, 2008 at 09:52:19PM -0000, dmitry.kurochkin wrote:
> I am not working on this one. At least until David comments.

I'm not sure what's causing this, and don't have the time to look at
it any time soon.

David

Ok, I need a volunteer to look into this.  Note the test case.   You'd probably
want to poke at the repopath module.  I'm promoting this to urgent just because
the potential 2.0.3 release is blocking on it.

Works for me with the latest darcs unstable. Looks like this was fixed by recent
patches from David.

Regards,
  Dmitry

Resolving in unstable then.  Thanks!

On Wed, Sep 10, 2008 at 11:19:29AM -0000, dmitry.kurochkin wrote:
> Works for me with the latest darcs unstable. Looks like this was
> fixed by recent patches from David.

Yep, I can confirm that. Thanks.