#158: restarting the darcs source backend skips failed changesets
------------------------+---------------------------------------------------
Reporter: wfranzini | Owner: lele
Type: defect | Status: reopened
Priority: major | Milestone: VersionOne
Component: darcs | Version: 0.9
Resolution: | Keywords:
------------------------+---------------------------------------------------
Old description:
> Using the darcs source backend I've observed the following behavior:
>
> * the target (aegis) back-end fails[[BR]]
> * the state file seems (to me) to correctly register the last
> successfully applied change-set[[BR]]
>
> however starting tailor again with the very same conditions skips the
> failed change-set, while I was expecting the same failure.
>
> I think the darcs source back-end should obliterate a failed change-set
> before quitting.
New description:
Using the darcs source backend I've observed the following behavior:
* the target (aegis) back-end fails
* the state file seems (to me) to correctly register the last
successfully applied change-set
however starting tailor again with the very same conditions skips the
failed change-set, while I was expecting the same failure.
I think the darcs source back-end should obliterate a failed change-set
before quitting.
--
Comment(by lele):
Rethinking the issue, it may be related to the StateFile machinery. I
broke it recently and it's been so for a few weeks. Given that Miklos
experienced the problem well before that, I can only assume it had some
glitch even before then :)
Anyway, if that's the case, it should be fixed, now. I just pushed [1594]
that should prevent it happens again.
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/158#comment:5>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
