I have conflicting pending patches.  'darcs repair' and 'darcs check' 
don't report anything wrong, though.

Do you want to add a long comment? [yn]y
darcs: bug in darcs!
There was an attempt to write an invalid pending!
If possible, please send the contents of _darcs/patches/pending_buggy
along with a bug report.
Please report this to bugs@darcs.net
If possible include the output of 'darcs --exact-version'.

$ darcs --exact-version
darcs compiled on Nov 20 2006, at 14:33:22
# configured Mon Oct  9 15:12:44 EDT 2006
./configure --no-create --no-recursion

Context:

[TAG 1.0.9rc1
Tommy Pettersson <ptp@lysator.liu.se>**20061008175207]

Attachments

• pending_buggy

Here seems to be the interesting part:

> move ./tmpls/locations.TMPL ./templates/locations.TMPL

... some intervening stuff on other files...

> rmfile ./tmpls/locations.TMPL

Note that here, it should be rmfile ./templates/locations.TMPL

Jason: any idea what sequence of steps led to this situation?

Thanks,

Not really - the sequence, if I could redo it would be pretty long.  I 
ended up moving the repo aside, re-getting it and then folding my 
changes back.  I don't remember doing a 'darcs mv' for that 
locations.TMPL file -- maybe I did?

There were a LOT of changes, so my guess is that something got corrupted 
a while ago.

Thanks!

Jason

Eric Y. Kow wrote:
> Here seems to be the interesting part:
> 
>> move ./tmpls/locations.TMPL ./templates/locations.TMPL
> 
> ... some intervening stuff on other files...
> 
>> rmfile ./tmpls/locations.TMPL
> 
> Note that here, it should be rmfile ./templates/locations.TMPL
> 
> Jason: any idea what sequence of steps led to this situation?
> 
> Thanks,
> 
>

> Not really - the sequence, if I could redo it would be pretty long.

Ok. Thanks anyway.

> I ended up moving the repo aside, re-getting it and then folding my 
> changes back.

Glad to hear that you found a workaround.  I was going to suggest
editing the pending by hand.

> I don't remember doing a 'darcs mv' for that locations.TMPL file --
> maybe I did?

> There were a LOT of changes, so my guess is that something got corrupted 
> a while ago.

If you could make your repository available, it might be helpful (it may
let us ferret out the corruption), but I understand if that's not
possible.

Otherwise, without a reproducible example, I'm not sure we can do
anything with this.

Darcs: maybe a battery of quickcheck tests for pending?  Somehow
generate a sequence of moves, adds, removes, and trivial hunk changes to
make sure that the pending patch is always valid?

On Sat, Aug 11, 2007 at 06:49:45AM -0000, Eric Kow wrote:
> Darcs: maybe a battery of quickcheck tests for pending?  Somehow
> generate a sequence of moves, adds, removes, and trivial hunk changes to
> make sure that the pending patch is always valid?

It's hard to say, without being able to reproduce this.  More tests in the
test suite are always a plus, but it's hard to figure out an efficient way
to generate test cases that are likely to reveal bugs!  :(
-- 
David Roundy
Department of Physics
Oregon State University

Yeah, I'm not sure about making the repository available - it's my 
company's code and there are passwords sprinkled throughout, if I'm 
understanding what you're asking for.

Thanks!

Jason

Eric Kow wrote:
> Eric Kow <eric.kow@gmail.com> added the comment:
> 
>> Not really - the sequence, if I could redo it would be pretty long.
> 
> Ok. Thanks anyway.
> 
>> I ended up moving the repo aside, re-getting it and then folding my 
>> changes back.
> 
> Glad to hear that you found a workaround.  I was going to suggest
> editing the pending by hand.
> 
>> I don't remember doing a 'darcs mv' for that locations.TMPL file --
>> maybe I did?
> 
>> There were a LOT of changes, so my guess is that something got corrupted 
>> a while ago.
> 
> If you could make your repository available, it might be helpful (it may
> let us ferret out the corruption), but I understand if that's not
> possible.
> 
> Otherwise, without a reproducible example, I'm not sure we can do
> anything with this.
> 
> Darcs: maybe a battery of quickcheck tests for pending?  Somehow
> generate a sequence of moves, adds, removes, and trivial hunk changes to
> make sure that the pending patch is always valid?
> 
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue510>
> __________________________________

I'm marking this resolved in unstable, mostly because we can't reproduce it, and
partly because of the recent issue494 fix.  Feel free to reopen if anyone has
ideas, especially Jason if you find a way to reproduce it.

I'm somewhat doubtful that the two are related (issue494 involves applying a
patch), but there are some interesting similarities (move b -> a, weird stuff in
pending).

Cheers,

Eric

P.S.  If only we had some kind of magical obfuscater that could make it easy for
people to send us repos for forensics without revealing company secrets.