On 06/25/14 21:16, Nick Holland wrote:
> openbsd.cs.toronto.edu updated (again)

and cvsyncd restarted.  Unfortunately, this was long after the above
note.  *blush*

But yes, there are still issues.

Nick.

> On 06/25/14 14:51, 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.
>> 
>> to check a server do:
>> cvs -d anon...@yourserver.org:/cvs log /usr/src/libexec/ld.so/malloc.c
>> |  less  and see if it has r 1.3
>> 
>> Thanks, and sorry for the disruption,
>> 
>> -Bob
>> 
> 

Reply via email to