#158: restarting the darcs source backend skips failed changesets
------------------------+---------------------------------------------------
Reporter: wfranzini | Owner: lele
Type: defect | Status: new
Priority: major | Milestone: VersionOne
Component: darcs | Version: 0.9
Resolution: | Keywords:
------------------------+---------------------------------------------------
Comment(by lele):
Yes, that's expected!
Consider this:
{{{
>>> from vcpx.statefile import StateFile
>>> sf = StateFile('project.state', None)
>>> print sf.lastAppliedChangeset()
Revision: Use a common ancestor to recognize tailor exceptions
Date: 2006-06-24 23:11:57+00:00
Author: [EMAIL PROTECTED]
Entries: tailor(UPD), vcpx/__init__.py(UPD), vcpx/config.py(UPD),
vcpx/cvsps.py(UPD), vcpx/project.py(UPD), vcpx/source.py(UPD),
vcpx/tailor.py(UPD), vcpx/target.py(UPD)
Log:
}}}
The `lastAppliedChangeset()` is the changeset that tailor has been able to
fetch and apply (from the source) ''and'' to replay and commit (on the
target).
Your case shows that the source backend has been able to do it's work, ie
pulling and applying the next patch, but an error occurred while replaying
it on the target, and thus it's still "pending" there.
At next run, tailor will retry to commit that patch on the target, before
going on.
Maybe the source backend could ''unpull'' (in darcs parlance) the applied-
but-not-replayed-and-committed patch, but I do not see an obvious
advantage of doing that. Do you?
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/158#comment:2>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
Tailor@lists.zooko.com
http://lists.zooko.com/mailman/listinfo/tailor
