trunk/bin/atk
trunk/bin
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 May 27 2006, at 00:32:26
# configured Sat May 27 00:03:13 PDT 2006
./configure

Context:

[TAG 1.0.7
Tommy Pettersson <ptp@lysator.liu.se>**20060513171438]

Attachments

• pending_buggy
• unnamed

This on my solaris box:

$uname -a
SunOS hercules 5.9 Generic_118558-22 sun4u sparc SUNW,Sun-Fire-V890
$

I took a look at the pending.  There are double entries for many files.
Note that the filenames are very similar, but there only seems to be
one duplicate for each file affected.  Attaching a list of duplicates.
(generated by sort, uniq, diff)

Ideas?

Attachments

• duplicates

Hmmm... I do not see any duplicated _paths_ on that list...
In my project  many files share the same name however they are in different
directories.
It is the full path that identifies a file not the basename...

-Chris

note: Think .bashrc  every user can have one in own dir but names are all
shared.

On 10/1/06, Eric Kow <bugs@darcs.net> wrote:
>
>
> Eric Kow <eric.kow@gmail.com> added the comment:
>
> I took a look at the pending.  There are double entries for many files.
> Note that the filenames are very similar, but there only seems to be
> one duplicate for each file affected.  Attaching a list of duplicates.
> (generated by sort, uniq, diff)
>
> Ideas?
>
> ----------
> title: BUG REPORT: There was an attempt to write an invalid pending! ->
> attempt to write invalid pending (1.0.7)
>
> ____________________________________
> Darcs issue tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue272>
> ____________________________________
>
>

Attachments

• unnamed

On Sun, Oct 01, 2006 at 22:00:46 +0000, Chris Lesner wrote:
> Hmmm... I do not see any duplicated _paths_ on that list...
> In my project  many files share the same name however they are in different
> directories.
> It is the full path that identifies a file not the basename...

Yep; I was initially confused by that (hence the warning that files have
very similar names - I meant paths), but if you do
   sort pending_buggy | uniq -c | grep 2
you'll notice some double entries

No triple entries or above, though

I'm guessing that this is fixed by the latest bugfixes in darcs-unstable, but
it's hard to say, since I don't see what triggered this bug.  Chris, can you
reproduce this bug, or give us intstructions how to do so? If you can't, I
recommend closing this report, since there's very little we can do to determine
it's fixed, and odds are good that it has been fixed recently anyhow.

David

Closing this bug because it looks like the resolved issue365.  Please repoen if
you can reproduce the bug in 1.0.9.