[darcs-users] another 0.9.17 convert-repo bug?

[David Roundy]

On Mon, Feb 23, 2004 at 11:03:51AM +0100, Shae Matijs Erisson wrote:
> Here's the output:
> <paste>
> # sudo -u wikiwiki convert-repo
> Already have 20040220165452-e350a-1f9c2d541ebceb9970e168e6f10f6b913d9f8d73.gz
> Already have 20040222195831-03db8-a668c1aa67c4b528aeb73837fd32573a68784444.gz
> Already have 20040119235239-03db8-bbc894d110c47837c611c33d2e02819ac71ec941.gz
> Already have 20040119233002-03db8-39a7f40c9e119cf9ee0509c38ae3444a0932decf.gz
> different file lengths for /var/lib/darcs/repos/wikiwiki/repo/_darcs/current/README and /tmp/_darcs/newcurrent/README
> Fixing current...
>  
> Fail: /var/lib/darcs/repos/wikiwiki/repo/_darcs/current_old: removeFile: does not exist (No such file or directory)
> </paste>

It looks like the problem is with the repair command (which is called by
convert-repo).  Just to make sure, can you try running darcs repair on the
repo?

I think I've found and fixed the problem, which was from a change in where
temporary directories are created that confused repair.

I'm wondering why you called convert-repo... was this a repository that
hadn't been modified since darcs 0.9.14? convert-repo should no longer be
needed, since the repository transitions it was created for are complete.
If you were concerned about the permissions bug, convert-repo doesn't do
anything about that, but a simple "chmod -R a+r ." should fix those, unless
you had some executable permissions set, in which case those will have to
be restored by hand.

Thanks for the report! And do run repair (once you get a working version),
because there does seem to be a problem that needs fixing with your
repository.  I can't see the problem myself, since when I "get" your repo,
I get my own clean copy of _darcs/current, where the problem is.

(and I'd definitely like to hear what happens...)
-- 
David Roundy
http://www.abridgegame.org