On 2014/06/26 06:37, Alexander Hall wrote: > On 06/25/14 20:52, Bob Beck wrote: > >If you or someone you love runs an anoncvs server, they need to see this. > > > >As you know we recently added commitid support to cvs, and we had > >you update your cvsync binary. > > > >Unfortunately, the fix wasn't quite right. We ran into problems > >with the synching of commitid files. naddy managed to cook > >a correct fix for us. > > > >anoncvs.ca (the fanout machine) has been fixed - again. What you > >need to do is to update your cvsync to the latest one that was > >just committed into ports (cvsync-0.25.0pre0 or later). Remove your > >scanfile (if any). > > > >Once you do that, re-run cvsync and you should be back in business. > > Is it known whether this requires a fixed upstream cvsync first, or if it is > ok to apply the fix and your repo will become fine whenever the upstream is > fixed?
If you run the client with "cvsync -v", it will show you whether the server is updated (Protocol: 0.25) or not (Protocol: 0.24).
