On Wed, Jun 25, 2014 at 10:01:06PM -0700, patrick keshishian wrote:
> On Thu, Jun 26, 2014 at 06:37:00AM +0200, 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?
> > 
> > Anyone with insight, please feel free to chime in.
> 
> 
> The commit message suggests, at least, the server must be
> updated:
> 
>     | Add full support for commitid and bump protocol version
>     | Old clients will receive updates with commitid stripped out.


It seems, running updated cvsync against an "un-updated"
cvsyncd (I assume) results in failure:

Connecting to anoncvs1.usa.openbsd.org port 7777
Connected to 149.20.54.217 port 7777
Running...
Updating (collection openbsd-src/rcs)
Updater(RCS): UPDATE(delta): error
Updater(RCS): UPDATE: 
/cvs/anoncvs/cvs/obsd/src/lib/libc/string/timingsafe_bcmp.3,v
Updater: RCS Error
Socket Error: recv: 2 residue 2
Receiver Error: recv
Mux(SEND) Error: not running: 0
DirScan: RCS Error
Mux(SEND) Error: not running: 1
FileScan(RCS): UPDATE /cvs/anoncvs/cvs/obsd/src/sbin/pfctl/parse.y,v
FileScan: RCS Error
Failed


ouch :-)

--patrick


> HTH,
> --patrick
> 
> 
> > /Alexander
> > 
> > >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