Hello,

Here is a trace of a darcs pull. Darcs failed to pull pathed leading to
conflicts and said me to email to this list.

The version used is "1.0.9 (release)" (from Debian Sid).

The repository contains some file that were sharply deleted and
recreated because I have forgotten there was a darcs repository in my
/home. I have no idea if it is a real bug or only a bad use from me,
sorry if it is the case.

Don't hesitate to ask more precisions.

Thanks,

Olivier

Olivier,

Could you test again with the pre-release binaries available from here? 

http://wiki.darcs.net/DarcsWiki/DarcsTwo

I suspect you'll find the bug is fixed. You may need to first run "darcs
convert" on the upstream repo before trying the pull again. 

You can also search this bug tracker for similar reports and results:

http://bugs.darcs.net/

  Mark

This issue is "presumed-dead" in the unstable branch, but can't be confirmed
without further testing from the reporter, who hasn't responded in the last week. 

Olivier: please re-open this issue if you find the problem persists with a darcs
2 binary.

Sorry for the long delay, I didn't have time to answer.

I didn't anymore have the original buggy repository, but only a fresh copy made
with 'darcs get'.

With darcs 1.0.9-1 from debian, I have a new error:
"bug in darcs! in function reconcile_unwindings"
followed by a sequence of hunks (I join a copy of the trace).

After converting the source and target repositories, I have the error:
"darcs: bug in get_extra commuting patch:"
followed by the name of the patch.

Olivier

Attachments

• log.darcs

oschwand, 

Thanks for your help with this. The "reconcile_unwindings"  issue is fixed in
the unstable branch. (You can search for reconcile_unwindings in the bug tracker
to confirm this). 

Regarding the error you got with Darcs 2, "convert" is not meant to be run on
more than repository in a group of related repositories. It appears you did
that, and errors are expected in that case. If there's a way to make the docs
for "convert" more clear about this, please let us know. 

   Mark