I just reproduced this bug with darcs-2.5.2. I also think I showed that
this bug was triggered by running "darcs optimize" on the server.
I ran a command to "darcs get" (with darcs-2.5.2) a series of closely
related repos over HTTP, and they all succeeded with two warning
messages. I didn't notice the warning messages at the time and only
found them when I reviewed my logs later while writing this bug report.
Those two warnings were:
Hash failure in
/home/source/.darcs/cache/patches/0000011594-d4086ca5795e193c8b7af6bb78970649352d7194270ceeea1933f8b085dd6647
Hash failure in
/home/source/.darcs/cache/patches/0000007091-271f31fa95af13520c6693e24d2fc06ac85ef35f2f10f1028fc35e7f805de5cb
Then I went onto the server and ran this command on all of them,
including on /home/source/darcs/tahoe-lafs/trunk itself:
darcs optimize --reorder-patches
--sibling=/home/source/darcs/tahoe-lafs/trunk --relink --pristine
--compress
(That's darcs-2.5.0 on the server.)
The command succeeded on each one with no warnings.
Then I went back to the client, did "/bin/rm -rf ~/.darcs" and ran the
exact same series of "darcs gets". This time I got a ton of these
warning messages! Here is a small sample:
Hash failure in
/home/source/.darcs/cache/patches/0000007737-1dce57015e8f61a5bb71c51481fb8ef2b0fe1c0907007453038749fe9447fbaa
Hash failure in
http://old.tahoe-lafs.org/source/tahoe-lafs/sftp/_darcs/patches/0000007737-1dce57015e8f61a5bb71c51481fb8ef2b0fe1c0907007453038749fe9447fbaa
darcs failed: Couldn't fetch
`0000007737-1dce57015e8f61a5bb71c51481fb8ef2b0fe1c0907007453038749fe9447fbaa'
in subdir patches from sources:
thisrepo:/home/source/darcs/tahoe-lafs/incoming-second-try/sftp
cache:/home/source/.darcs/cache
repo:http://old.tahoe-lafs.org/source/tahoe-lafs/sftp
darcs:
/home/source/.darcs/cache/patches/0000003216-f9fe7c2cbc084e594f176ffbb8829c11b21b58b6072eb7ea1fe3a47fe001d29f-new_ca4808abb334647c865edc1cbd3f31e3:
getSymbolicLinkStatus: does not exist (No such file or directory)
Hash failure in
/home/source/.darcs/cache/patches/0000000436-9e1046d7a4c9d75c981de19258187dedb1044c4a0d7b220b1f68ad9265c737a5
Having seen these scary warnings (and by the way I'm in the process of
moving our canonical darcs repos for the Tahoe-LAFS project to a new
server, so these warnings are quite a concern), I went back and ran
"darcs check --complete" on all the repos on the server. They all
reported that the repository was consistent. I ran darcs checks on the
client on all of the repositories that I had fetched in the first pass
(the pass that included only two warning messages) -- all consistent.
Then I ran darcs checks on the client on all of the repositories that I
had fetched in the second pass (the pass that included zillions of
warning messages) -- all consistent.
So what should I do now ?
|
