Re: portsnap and the imminent demise of svn-cvs ports tree export
Date: Mon, 21 Jan 2013 12:01:05 +1100 How do you work that out? None of the headers you've included show any problem. John sent his mail at 010105UT on 21st, and your headers say you received it at 095334UT on 21st - nearly 9 hours later. The X-Apparently-To header is 010132UT on the 21st (about 3s after FreeBSD forwarded it to me, se quite realistic). -- Peter Jeremy I think I might have misread something mentally transferring 3 at the end of 2013 to make Jan 21 into Jan 23: maybe the wrong time of day, too late going to bed. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portsnap and the imminent demise of svn-cvs ports tree export
On 2013-Jan-22 22:45:24 -0500, Thomas Mueller mueller6...@bellsouth.net wrote: Your date is ahead of what the headers of your message say: From owner-freebsd-po...@freebsd.org Mon Jan 21 09:53:34 2013 Received: from pop.att.yahoo.com (pop2.sbc.mail.vip.ne1.yahoo.com [98.138.197.207]) by mueller6722.bellsouth.net (mpop-1.0.23) with POP3 for arlene; Mon, 21 Jan 2013 09:53:34 + X-Apparently-To: mueller6...@bellsouth.net via 98.139.172.126; Sun, 20 Jan 2013 17:01:32 -0800 ... Date: Mon, 21 Jan 2013 12:01:05 +1100 How do you work that out? None of the headers you've included show any problem. John sent his mail at 010105UT on 21st, and your headers say you received it at 095334UT on 21st - nearly 9 hours later. The X-Apparently-To header is 010132UT on the 21st (about 3s after FreeBSD forwarded it to me, se quite realistic). -- Peter Jeremy pgpQhDRnUR4Hv.pgp Description: PGP signature
Re: portsnap and the imminent demise of svn-cvs ports tree export
On 21 January 2013 01:01, John Marshall john.marsh...@riverwillow.com.au wrote: We are on notice that the current ports tree will be soon no longer available via CVSup and friends. General consumers of the FreeBSD ports tree are being encouraged to switch to portsnap. http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-January/49.html The presence of the file LASTCOMMIT.txt, and the content of the $FreeBSD$ lines, in a portsnap-generated ports tree indicate that portsnap sources its data from a CVS export of the tree. Are there That is correct. plans to migrate the portsnap source to the subversion tree before the end of February? Colin is working right now at migrating it. As it is a somewhat larger task (it also includes some cleanup of the portsnap codebase) it hasn't been done yet. I can guarantee that we will not make portsnap stop working by killing svn2cvs for ports before portsnap is migrated, but I don't think it should be a problem. While portsnap hasn't run as reliably as we want over the last two month due to high churn of changes on the FreeBSD.org sites (as we have basically been redoing all infrastructure for scratch) it is fully supported by clusteradm/security-officer. (Lack of monitoring after the security incident has also really hurt us, but that's coming back these days). PS. I consider it a very fair question. PPS. portsnap build recently moved to a new server which decreased the portsnap build time so changes should now show up even faster in portsnap. -- Simon L. B. Nielsen Hat: FreeBSD.org clusteradm and FreeBSD Security Officer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portsnap and the imminent demise of svn-cvs ports tree export
(current time: Wed 23 Jan 2013 02:43:43 AM UTC) --] [-- End of PGP output --] [-- The following data is signed --] We are on notice that the current ports tree will be soon no longer available via CVSup and friends. General consumers of the FreeBSD ports tree are being encouraged to switch to portsnap. http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-January/49.html The presence of the file LASTCOMMIT.txt, and the content of the $FreeBSD$ lines, in a portsnap-generated ports tree indicate that portsnap sources its data from a CVS export of the tree. Are there plans to migrate the portsnap source to the subversion tree before the end of February? # cd /usr/ports # make update -- Running portsnap -- Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from your-org.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Sun Jan 20 16:00:15 PST 2013 to Sun Jan 20 16:05:39 PST 2013. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 5 patches... done. Applying patches... done. Fetching 1 new ports or files... done. Removing old files and directories... done. Extracting new files: /usr/ports/LASTCOMMIT.txt /usr/ports/lang/basic256/ /usr/ports/sysutils/less/ /usr/ports/textproc/mifluz/ /usr/ports/www/Makefile /usr/ports/www/p5-LWP-Protocol-PSGI/ Building new INDEX files... done. # ident /usr/ports/www/Makefile /usr/ports/www/Makefile: $FreeBSD: ports/www/Makefile,v 1.3300 2013/01/20 23:49:48 svnexp Exp $ Thank you. -- John Marshall [-- End of signed data --] Your date is ahead of what the headers of your message say: From owner-freebsd-po...@freebsd.org Mon Jan 21 09:53:34 2013 Received: from pop.att.yahoo.com (pop2.sbc.mail.vip.ne1.yahoo.com [98.138.197.207]) by mueller6722.bellsouth.net (mpop-1.0.23) with POP3 for arlene; Mon, 21 Jan 2013 09:53:34 + X-Apparently-To: mueller6...@bellsouth.net via 98.139.172.126; Sun, 20 Jan 2013 17:01:32 -0800 ... Date: Mon, 21 Jan 2013 12:01:05 +1100 Anyway, my latest LASTCOMMIT.txt shows ## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/310745 ## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated ## SVN ## ## SVN ## r310745 | araujo | 2013-01-21 03:39:17 + (Mon, 21 Jan 2013) | 8 lines ## SVN ## Changed paths: ## SVN ##M /head/sysutils/syslinux/Makefile ## SVN ##M /head/sysutils/syslinux/distinfo ## SVN ##M /head/sysutils/syslinux/files/patch-Makefile ## SVN ##M /head/sysutils/syslinux/files/patch-libinstaller-syslxopt.c ## SVN ##M /head/sysutils/syslinux/pkg-descr ## SVN ##M /head/sysutils/syslinux/pkg-plist ## SVN ## ## SVN ## - Update to 5.00. ## SVN ## - Update MASTER_SITES. ## SVN ## - Add MAKE_JOBS_SAFE. ## SVN ## - Trim header. ## SVN ## ## SVN ## PR: ports/174180 ## SVN ## Submitted by: KATO Tsuguru tkato...@yahoo.com ## SVN ## ## SVN ## Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
portsnap and the imminent demise of svn-cvs ports tree export
We are on notice that the current ports tree will be soon no longer available via CVSup and friends. General consumers of the FreeBSD ports tree are being encouraged to switch to portsnap. http://lists.freebsd.org/pipermail/freebsd-ports-announce/2013-January/49.html The presence of the file LASTCOMMIT.txt, and the content of the $FreeBSD$ lines, in a portsnap-generated ports tree indicate that portsnap sources its data from a CVS export of the tree. Are there plans to migrate the portsnap source to the subversion tree before the end of February? # cd /usr/ports # make update -- Running portsnap -- Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from your-org.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Sun Jan 20 16:00:15 PST 2013 to Sun Jan 20 16:05:39 PST 2013. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 5 patches... done. Applying patches... done. Fetching 1 new ports or files... done. Removing old files and directories... done. Extracting new files: /usr/ports/LASTCOMMIT.txt /usr/ports/lang/basic256/ /usr/ports/sysutils/less/ /usr/ports/textproc/mifluz/ /usr/ports/www/Makefile /usr/ports/www/p5-LWP-Protocol-PSGI/ Building new INDEX files... done. # ident /usr/ports/www/Makefile /usr/ports/www/Makefile: $FreeBSD: ports/www/Makefile,v 1.3300 2013/01/20 23:49:48 svnexp Exp $ Thank you. -- John Marshall pgpGj9clpbuzo.pgp Description: PGP signature
