Hi!

I've problems with darcs-2 (darcs compiled on Mar 12 2008, at 14:36:06).

Attempt to do darcs put gives:

darcs: failed to read patch:
Sun Mar 30 22:06:02 CEST 2008  dev@atmarama.org
  tagged primary-1
Couldn't parse file
/home/gour/prj/rebt/_darcs/patches/3047d82af81969cccece45dad69f76ae0867a5f3
which is patch
Sun Mar 30 22:06:02 CEST 2008  dev@atmarama.org
  tagged primary-1

darcs check on the same repo gives:

gour@nitai ~/p/rebt> darcs check --debug-verbose
Beginning identifying repository .
Done identifying repository .
I'm about to check for uniqueness of patches.
Checking that patch names are unique...
I'm doing copyFileUsingCache on inventories/4f53cec555e012c5c3ba04664f68061f9090109c
I'm doing copyFileUsingCache on inventories/7539b888c283c27680adf5ba54b810196218fbec
Checking patches...
I'm doing copyFileUsingCache on inventories/4f53cec555e012c5c3ba04664f68061f9090109c
I'm doing copyFileUsingCache on inventories/7539b888c283c27680adf5ba54b810196218fbec
Beginning checking patch
Reading patch file: Wed Mar 12 11:07:56 CET 2008  dev@atmarama.org
  * 1st assignment template for Primary Certificate, module #1
I'm doing copyFileUsingCache on patches/44c1b1ccd5cea8476afcdb644d790c8ac194b5f2
Reading patch file: Fri Mar 14 20:52:56 CET 2008  dev@atmarama.org
  * space for letter-1 in Answer-1
I'm doing copyFileUsingCache on patches/fa5e0564d286bfe2065e6eda2a92cb7d2d10b8ba
Unapplicable patch:
Fri Mar 14 20:52:56 CET 2008  dev@atmarama.org
  * space for letter-1 in Answer-1
darcs: ./primary/assignment-1.muse: openBinaryFile: does not exist (No such file
or directory)

which is quite strange considering that assignment-1.muse is utf-8 text file :-/

In the attachment I provide unapplicable patch.

Sincerely,
Gour

Attachments

• fa5e0564d286bfe2065e6eda2a92cb7d2d10b8ba

You've got a corrupt repository.  Can you make the repository available?

And can you also give a brief history of this repository? It looks like
it's a pretty young repository that you perhaps created with the same
version of darcs that shows this problem?

What's the format of the repository? (e.g. cat _darcs/format)

Thanks for the bug report!

David

Hi David!

You got me idea to solve the problem.

I changed format to darcs-2 (from darcs-2-experimental), but didn't installed
(after building it) latest darcs :-/

Excuse me for creating (extra) noise :-(

Still, the error msgs. are scary ;)

Sincerely,
Gour

Then this is a bug in the format-checking.  If darcs didn't recognize the
format, it should give you a message to that effect!

Would you by any chance be willing to send in a sequence of shell commands that
reproduce this error?

David

Plain:

darcs put repo gave:

darcs: failed to read patch:
Sun Mar 30 22:06:02 CEST 2008  dev@atmarama.org
  tagged primary-1
Couldn't parse file
/home/gour/prj/rebt/_darcs/patches/3047d82af81969cccece45dad69f76ae0867a5f3
which is patch
Sun Mar 30 22:06:02 CEST 2008  dev@atmarama.org
  tagged primary-1


while issuing:

darcs check --debug-verbose

produced the error from http://bugs.darcs.net/msg4180


Sincerely,
Gour

Ooops.  It turns out that square brackets in the subject confuse the roundup
email gateway.  :(

Sorry, I wasn't clear.  I meant to ask if you would be willing to figure
out a script that could reproduce this error starting from darcs init
creating a new repository.

OK.

I put a script which shows inconsistent repo, but I'm not sure if it is appropriate.


Sincerely,
Gour

Attachments

• format_test.sh

Alas, when I run the test script you uploaded (format_test.sh) I don't get an error!

David

>>>>> "David" == David Roundy <bugs@darcs.net> writes:

David> Alas, when I run the test script you uploaded (format_test.sh) I
David> don't get an error!

Hmm...I get the error with:

gour@nitai ~/r/d/c2hs> darcs --exact-version
darcs compiled on Mar 12 2008, at 14:36:06

i.e. not the latest code.

Sincerely,
Gour

-- 

Gour  | Zagreb, Croatia  | GPG key: C6E7162D
----------------------------------------------------------------

Hi!

I built latest darcs-2.0.0rc1 and, indeed, format_tesh.sh fails, i.e. there is
no error - repo is consistent :-)

Sincerely,
Gour