[darcs-users] Leading / stripped from local repository

[Matthias Kilian]

I just ran into a strange bug in darcs-HEAD, which is a regression
wrt darcs-2.0.2. Here's a typescripted shell session:

$ 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))
$ darcs pull --debug-verbose
Beginning identifying repository .
Done identifying repository .
Identified darcs-1 repo: /tmp/foo
Beginning identifying repository var/tmp/foo
Done identifying repository var/tmp/foo

darcs failed:  Not a repository: var/tmp/foo (var/tmp/foo/_darcs/inventory: openBinaryFile: does not exist (No such file or directory))


This seems to happen whenever the *first* component in the paths
of the two local repositories differ, i.e. pulling from /var/tmp/foo
into /tmp/foo  (or vice versa) or pulling from /home/kili/src/ghc-head
into /var/tmp/ghc.

Is this a known bug? If not, I'll open a ticket for it (I didn't
find a match in the bug database).

Ciao,
	Kili

-- 
Infinite compression is easy, if you use a sufficiently lossy
compression algorithm.  Ask anybody who's talked to a journalist
for an hour, and ends up as a one-sentence misquote...
		-- Valdis.Kletnieks at vt.edu