Ticket #63 (new defect)
Opened 7 years ago
tailor gets confused by cvs 1.12 "phantom commits"
|Reported by:||ydirson||Owned by:||lele|
Similarly to cvsps (see http://bugs.debian.org/369872), the cvs backend in tailor gets confused by empty commits with bogus timestamp added by recent cvs versions. Although the timestamp issue at least is probably a bug in cvs (see http://bugs.debian.org/369870), there are now cvs repositories in the wild which exhibit the problem, and it would be a shame to let people trapped in cvs because of this :)
What happens is that tailor uses the timestamp of the bogus commit to checkout the initial version from the branch, but since the timestamp is bogus, it checks out an empty working copy, and then correctly gets confused.
Checkout of v30-pull failed! Cannot handle empty repositories. Maybe wrong module/repository?: The working copy '/homelocal/ydirson/test/root/v30-in' of the CVS repository seems empty, don't know how to deal with that.