Hello,
There appears to be a regression since 2.4.4 which is experienced like this:
The right kind of "bad patch" is introduced into the tree, and after
that, trying to unpull *any* patch from the repo will fail. Very bad.
There is a test repo available that illustrates the issue, and with it
we've confirmed that 2.4.4 does not have the bug, but 2.5, 2.5.1 and
2.5.2, and "2.7.3 (+ 300 patches)" *do* have the bug.
I was thinking that perhaps with the test case available, this might be
enough information for a developer to set up a test case to use with
"darcs trackdown" which could find the problematic patch in automated way?
>From --debug--verbose, we can see that the hang is happening after this
printed to the screen:
I'm doing copyFileUsingCache on
patches/0000003769-e379a42f9ae1ab3f5c3e689a8fb154922276e99093ae5547e4f358775190df49
Perhaps that rings some bells?
Thanks for your help with this.
I hope I can soon work towards installing a new darcs that fixes this,
rather than working on installing darcs 2.4.4 again.
Mark
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
