[darcs-devel] Fwd: [issue573] corrupted repository -- indelible "conflicting local changes"

[Nathan]

I'm sorry, I didn't realize this tarball is over 15 MB until I tried
sending email.  Is there another delivery method I could use?
(Perhaps I can post this tarball to the allmydata.org site somewhere?)

Nathan



---------- Forwarded message ----------
From: Nathan <nejucomo at gmail.com>
Date: Jan 12, 2008 1:31 PM
Subject: Re: [issue573] corrupted repository -- indelible "conflicting
local changes"
To: zooko <zooko at zooko.com>
Cc: Darcs bug tracker <bugs at darcs.net>, beschmi at cloaked.de,
darcs-devel at darcs.net, droundy at darcs.net, eric.kow at gmail.com,
mark at summersault.com, ptp at lysator.liu.se


Here's the process leading to the bug:

Directory A had an old checkout, and I wanted to test a new checkout
on my system.

Inside a new directory, B, I ran "darcs get /path/to/A".

Then inside B/C (where lived B/C/_darcs), I ran "darcs pull
http://url-to-tahoe".

The attached tarball is of directory A.  I have not tried to recreate the error.

Thanks for looking into this!






On Jan 12, 2008 8:18 AM, zooko <zooko at zooko.com> wrote:
> >
> > I've got the tarball, but I'm not clear how to use it to reproduce
> > the bug.
> > I don't see any problems there (e.g. no unrecorded changes), but I
> > only
> > looked with the latest darcs-unstable and the darcs 1.0.9rc1 that
> > is in
> > etch, so it may be that the bug appeared and disappeared between those
> > versions.
> >
> > What should I see?
>
> I haven't tried to reproduce it yet, but if I did I guess I would
> obliterate the patch that Rob wrote on his Mac and then repull that
> patch.  Also, Nejucomo has a tarball from before he experienced the
> issue, so if you can get that tarball from him, then pull all patches
> into it from the Tahoe trunk, that might reproduce the bug.
>
> More later!  (I'm on my way to the airport.)
>
> --Z
>