Re: ANONCVS MIRROR MAINTAINERS PLEASE READ!
On 2014/06/07 01:02, Alexander Hall wrote: If you use a scanfile, it should be removed and re-created when updating. If I update my package before my upstream does, do I have to keep removing the scanfile (or disable it) until the upstream mirror has been fully fixed too? Sorry I have no idea about this..
Re: ANONCVS MIRROR MAINTAINERS PLEASE READ!
An additional note: this doesn't just apply to mirror maintainers. If you are using cvsync to update a local repository, you need the updated version of cvsync too.
ANONCVS MIRROR MAINTAINERS PLEASE READ!
If you or someone you love runs an anoncvs server, they need to see this. We recently added commitid support to our cvs repo. all works fine with cvs and this. However, we ran into a problem with cvsync in ports. Most mirror maintianers use cvsync to fetch the repository from anoncvs.ca - it had a bug where it would not get commits to branches that contained a commitid. anoncvs.ca (the fanout machine) has been fixed. If your cvsync binary is up to date with what has been committed, it should fix itself. So what you need to do is update to the latest -current cvsync port - either build it from sources or install a recently built snapshot port. 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 gnu/usr.sbin/sendmail/sendm\ ail/conf.c | less and see if it has r 1.38 Thanks, and sorry for the disruption, -Bob
Re: ANONCVS MIRROR MAINTAINERS PLEASE READ!
On 2014/06/06 11:17, Bob Beck wrote: If you or someone you love runs an anoncvs server, they need to see this. We recently added commitid support to our cvs repo. all works fine with cvs and this. However, we ran into a problem with cvsync in ports. Most mirror maintianers use cvsync to fetch the repository from anoncvs.ca - it had a bug where it would not get commits to branches that contained a commitid. anoncvs.ca (the fanout machine) has been fixed. If your cvsync binary is up to date with what has been committed, it should fix itself. So what you need to do is update to the latest -current cvsync port - either build it from sources or install a recently built snapshot port. 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 gnu/usr.sbin/sendmail/sendm\ ail/conf.c | less and see if it has r 1.38 Updated information on this, check that r 1.37 has branches: 1.37.4 Thanks, and sorry for the disruption, If you use a scanfile, it should be removed and re-created when updating.
Re: ANONCVS MIRROR MAINTAINERS PLEASE READ!
On 06/06/14 19:29, Stuart Henderson wrote: On 2014/06/06 11:17, Bob Beck wrote: If you or someone you love runs an anoncvs server, they need to see this. We recently added commitid support to our cvs repo. all works fine with cvs and this. However, we ran into a problem with cvsync in ports. Most mirror maintianers use cvsync to fetch the repository from anoncvs.ca - it had a bug where it would not get commits to branches that contained a commitid. anoncvs.ca (the fanout machine) has been fixed. If your cvsync binary is up to date with what has been committed, it should fix itself. So what you need to do is update to the latest -current cvsync port - either build it from sources or install a recently built snapshot port. Care to mention the fixed package version, so one knows when it's available at the favourite mirror? cvsync-0.24.19p3, yes? /Alexander 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 gnu/usr.sbin/sendmail/sendm\ ail/conf.c | less and see if it has r 1.38 Updated information on this, check that r 1.37 has branches: 1.37.4 Thanks, and sorry for the disruption, If you use a scanfile, it should be removed and re-created when updating.
Re: ANONCVS MIRROR MAINTAINERS PLEASE READ!
On 2014/06/07 00:04, Alexander Hall wrote: Care to mention the fixed package version, so one knows when it's available at the favourite mirror? cvsync-0.24.19p3, yes? That is correct. There is a -current snapshot package for i386 at http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/cvsync-0.24.19p3.tgz and probably some mirrors; amd64 should follow shortly. For 5.4/i386 there is a package at http://ftp.obsd.si/pub/OpenBSD-unofficial/5.4-stable/i386/cvsync-0.24.19p3.tgz For 5.5/amd64, http://spacehopper.org/mirrors/cvsync-0.24.19p3.tgz There is a tar of the port directory at http://spacehopper.org/mirrors/cvsync-port.tgz which should be able to replace an existing port directory on a 5.4 or 5.5 system.
Re: ANONCVS MIRROR MAINTAINERS PLEASE READ!
On 06/06/14 19:29, Stuart Henderson wrote: On 2014/06/06 11:17, Bob Beck wrote: If you or someone you love runs an anoncvs server, they need to see this. We recently added commitid support to our cvs repo. all works fine with cvs and this. However, we ran into a problem with cvsync in ports. Most mirror maintianers use cvsync to fetch the repository from anoncvs.ca - it had a bug where it would not get commits to branches that contained a commitid. anoncvs.ca (the fanout machine) has been fixed. If your cvsync binary is up to date with what has been committed, it should fix itself. So what you need to do is update to the latest -current cvsync port - either build it from sources or install a recently built snapshot port. 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 gnu/usr.sbin/sendmail/sendm\ ail/conf.c | less and see if it has r 1.38 Updated information on this, check that r 1.37 has branches: 1.37.4 Thanks, and sorry for the disruption, If you use a scanfile, it should be removed and re-created when updating. If I update my package before my upstream does, do I have to keep removing the scanfile (or disable it) until the upstream mirror has been fully fixed too? /Alexander
Re: ANONCVS MIRROR MAINTAINERS PLEASE READ!
On 06/06/14 18:20, Stuart Henderson wrote: On 2014/06/07 00:04, Alexander Hall wrote: Care to mention the fixed package version, so one knows when it's available at the favourite mirror? cvsync-0.24.19p3, yes? That is correct. There is a -current snapshot package for i386 at http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/cvsync-0.24.19p3.tgz and probably some mirrors; amd64 should follow shortly. For 5.4/i386 there is a package at http://ftp.obsd.si/pub/OpenBSD-unofficial/5.4-stable/i386/cvsync-0.24.19p3.tgz For 5.5/amd64, http://spacehopper.org/mirrors/cvsync-0.24.19p3.tgz There is a tar of the port directory at http://spacehopper.org/mirrors/cvsync-port.tgz which should be able to replace an existing port directory on a 5.4 or 5.5 system. openbsd.cs.toronto.edu should be fixed (using Stuart's packages) Let me know if there are any issues seen there. Nick.
