I have managed to accidentally reverse the context order in makeBundle,
which results in completely bogus bundles. The testsuite did not detect
that. (I.e. instead of writing the context in RL order, I wrote it in FL
order.) Witnesses do not apply here, either.
Gah. I just got confused, it was not makeBundle that was busted, but
savetoBundle in Darcs.Commands.Unrecord. Nevertheless, the problem boils
down to makeBundle taking a [PatchInfo] which can be easily reversed by
mistake. I will submit a patch to fix this.
The following patch updated issue issue1892 with status=resolved;resolvedin=2.6.0 HEAD
* Resolve issue1892: Improve safety of makeBundle* and fix a couple of related bugs.
Ignore-this: 9eaa26edfdda09ac444f124130b9e74b
The following patch updated issue issue1892 with status=resolved;resolvedin=2.5.0 CURRENT
* Resolve issue1892: Improve safety of makeBundle* and fix a couple of related bugs.
Ignore-this: 9eaa26edfdda09ac444f124130b9e74b
History
Date
User
Action
Args
2010-07-15 01:54:33
mornfall
create
2010-07-15 09:32:48
mornfall
set
assignedto: mornfall messages:
+ msg11749 title: Testsuite does not cover bundle creation very well. -> darcs unpull -o creates a busted bundle (reversed context)