Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
2014-06-26 23:19 GMT+02:00, Stuart Henderson : > On 2014/06/26 20:20, Christian Weisgerber wrote: >> As everybody noticed, there was another problem. Please update to >> cvsync-0.25.0pre0p0 for the latest bug fix. Sorry for all the >> inconvenience. > > At least the following anoncvs mirrors have this as of now: > > anon...@anoncvs.spacehopper.org:/cvs > anon...@anoncvs.usa.openbsd.org:/cvs > anon...@anoncvs.ca.openbsd.org:/cvs > anon...@anoncvs.cs.toronto.edu:/cvs > > anoncvs.eu.openbsd.org should be running pre0p0 also now. -- May the most significant bit of your life be positive.
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
On 06/26/14 17:18, Stuart Henderson wrote: > On 2014/06/26 20:20, Christian Weisgerber wrote: >> As everybody noticed, there was another problem. Please update to >> cvsync-0.25.0pre0p0 for the latest bug fix. Sorry for all the >> inconvenience. > > At least the following anoncvs mirrors have this as of now: > > anon...@anoncvs.spacehopper.org:/cvs > anon...@anoncvs.usa.openbsd.org:/cvs > anon...@anoncvs.ca.openbsd.org:/cvs > anon...@anoncvs.cs.toronto.edu:/cvs anon...@openbsd.cs.toronto.edu:/cvs is updated now, too, and looking MUCH happier. Thanks, Naddy and Stuart and Bob! Nick.
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
On 2014/06/26 20:20, Christian Weisgerber wrote: > As everybody noticed, there was another problem. Please update to > cvsync-0.25.0pre0p0 for the latest bug fix. Sorry for all the > inconvenience. At least the following anoncvs mirrors have this as of now: anon...@anoncvs.spacehopper.org:/cvs anon...@anoncvs.usa.openbsd.org:/cvs anon...@anoncvs.ca.openbsd.org:/cvs anon...@anoncvs.cs.toronto.edu:/cvs
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
As everybody noticed, there was another problem. Please update to cvsync-0.25.0pre0p0 for the latest bug fix. Sorry for all the inconvenience. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
On Thu, Jun 26, 2014 at 10:19:09AM +0100, Stuart Henderson wrote: > On 2014/06/26 11:02, Mike Belopuhov wrote: > > On 26 June 2014 08:53, patrick keshishian wrote: > > > 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 > > > Connected to 149.20.54.217 port > > > 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 > > > > > > > > > > removing offending files locally and restarting cvsync helps. > > > > I suspect this may only help until they receive another commit. I was thinking it would be bit of a pain to keep running cvsync, have it fail, remove files, run it again, repeat. I stopped after three cycles. > The server *must* be updated - though it looks like there may still be > some problems. Run with -v option per Stuart Henderson's comment. Parsing a file /etc/obsd-cvsync... Connecting to anoncvs1.usa.openbsd.org port Connected to 149.20.54.217 port Protocol: 0.25 Hash: MD5 Exchanging collection list... collection name "openbsd-src" release "rcs" umask 002 collection name "openbsd-xenocara" release "rcs" umask 002 collection name "openbsd-ports" release "rcs" umask 002 Compression: zlib Trying to establish the multiplexed channel... Running... Updating (collection openbsd-src/rcs) Updater(RCS): UPDATE(delta): error Updater(RCS): UPDATE: /cvs/anoncvs/cvs/obsd/src/lib/libcrypto/crypto/getentropy_linux.c,v Updater: RCS Error Socket Error: recv: 1691 residue 334 Receiver(DATA) Error: recv Mux(SEND) Error: not running: 1 FileScan(RCS): UPDATE /cvs/anoncvs/cvs/obsd/src/usr.sbin/installboot/i386_installboot.h,v FileScan: RCS Error Mux(SEND) Error: not running: 0 DirScan: RCS Error Failed I suspect this is because 'there still are some problems'. Is there anther way to update one's source trees for the time being? Best, --patrick
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
2014-06-25 20:52 GMT+02:00, Bob Beck : > 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. > anoncvs.eu.openbsd.org updated and cvsyncd restarted, but I don't think I get updated repos myself from the feeds I've tried. -- May the most significant bit of your life be positive.
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
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 >> >
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
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).
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
On 2014/06/26 11:02, Mike Belopuhov wrote: > On 26 June 2014 08:53, patrick keshishian wrote: > > 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 > > Connected to 149.20.54.217 port > > 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 > > > > > > removing offending files locally and restarting cvsync helps. > I suspect this may only help until they receive another commit. The server *must* be updated - though it looks like there may still be some problems.
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
On 26 June 2014 08:53, patrick keshishian wrote: > 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 > Connected to 149.20.54.217 port > 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 > > removing offending files locally and restarting cvsync helps.
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
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 Connected to 149.20.54.217 port 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 > > > > > >
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
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. 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 > > >
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
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. /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
Re: ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
openbsd.cs.toronto.edu updated (again) 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 >
ANONCVS MIRROR MAINTAINERS.. YOU NEED TO READ THIS!
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
