Date: Wed, 2 Jan 2013 15:30:36 -0800 (PST) From: "Chris H" <chris#@1command.com> To: "Peter Wemm" <peter@wemm.org> Cc: Eitan Adler <lists@eitanadler.com>, FreeBSD <freebsd-stable@freebsd.org>, Chris Rees <utisoft@gmail.com> Subject: Re: Does / Is anyone maintaining CVS for FreeBSD? Message-ID: <718d7f7cb15cabfe2894a85f0c262aff.authenticated@ultimatedns.net> In-Reply-To: <CAGE5yCqTfbsW4QBBBifk8T-accT%2BP3YLEfxUES2nMyk8UAT4ng@mail.gmail.com> References: <50E1D012.1040004@missouri.edu> <20121231175808.GA1399@glenbarber.us> <6817fb4c15659b194cc658b1dfa58a31.authenticated@ultimatedns.net> <CADLo83-RtuRE58HORn8ocqRVtcF3ZANJoHh1D8TO=aucwywbQw@mail.gmail.com> <f7a783bba9425aeaf67d94056b49f272.authenticated@ultimatedns.net> <CAF6rxgmFU-gnNqzbfpzBrAkKSrizigtsZ_3Q5KORZfL8=pv3PA@mail.gmail.com> <76a7aa4b1baf918bf02734d3336e2b7f.authenticated@ultimatedns.net> <CAGE5yCqTfbsW4QBBBifk8T-accT%2BP3YLEfxUES2nMyk8UAT4ng@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greetings Peter, and thank you _very_ much for the thoughtful, and very informative reply -- _greatly_ appreciated. > On Mon, Dec 31, 2012 at 2:39 PM, Chris H <chris#@1command.com> wrote: >>> On 31 December 2012 15:40, Chris H <chris#@1command.com> wrote: >>>> Are there _any_ CVS servers/trunks/tree's left? If so, how _current_ are >>>> they? >>> >>> Ports and Source currently have CVS trees. >>> Ports has an explicit EoL on February 28th (2 months from today) >>> Source does not have an explicit EoL though it *is* considered deprecated. >> >> Thank you for providing this information, and my apologies, for not having >> better researched it myself. I'll make an effort to provide a permanent CVS >> repo for both src && ports. > > At the risk of a late reply stirring things up. > > doc and www were converted from cvs -> svn in May 2012. There was > *never* a svn->cvs exporter for the doc/www trees - it was a clean > break and switch over, and the cvs tree was closed. However, a stale > orphaned copy of the doc/www files were in the cvsup network. If you > were using those, you were using stale, out of date files. > > I've been rebuilding *.freebsd.org machines over the last 3-4 months > and came across these stale files on a machine that was being > decommissioned. When I was building the replacement I didn't include > them. > > The cvs exporter was running on a machine that was broken into. The > entire machine, code, exporters and cvs repository were considered > tainted. As the exported src cvs tree has been deprecated for years, > we should have just turned it off, Instead we salvaged and reviewed > what we could, threw together a really quick and dirty exporter > replacement and made it run for a little longer. It really is on its > last legs. Note that there is no practical way to audit a cvs tree > after an incident like that, especially a deprecated tree at that. > > cvs for /usr/src was deprecated in October 2008. The original plan > for running the exporter for 2-3 months as a transition aide ran a > little longer than planned. > > The branch support timeline is listed here: http://www.freebsd.org/security/ > > As things stand right now, this is the exporter's run schedule: > * RELENG_6: Updates once a day, probably turning off on Feb 28th. > * RELENG_7: Updates hourly, probably turning off on Feb 28th at EOL > * RELENG_7_4: Updates hourly, probably turning off on Feb 28th at EOL > * RELENG_8: Updates hourly > * RELENG_8_3: Updates hourly > * RELENG_9: Updates hourly > * RELENG_9_0: Updates hourly > * src-HEAD: Updates daily, probably turning off on Feb 28th. > * ports-HEAD: Updates hourly, definitely turning off on Feb 28th. > > That's about what the limit of what the machine can handle. When > folks go on a commit spree, the poor thing runs its disks white-hot > for a few hours to catch up. > > > No new branches will ever make it into cvs. eg: no RELENG_9_2. > You'll have to get them from svn, just like getting updates to the > older branches. > > Its also worth noting that all of the RELENG_9 series were released > from the subversion tree - cvs was never involved. If there's an 8.4, > it'll have to be built from svn as well. > > We have some significant problems with both ezm3 and cvsup itself > (which is written in Modula-3). It basically is an inverse > compatability binary.. The runtime code uses the oldest available > versions of syscalls that it can, mostly the FreeBSD-4 versions. > Emulation for some of the more exotic functionality - particularly > signals - has become ... problematic .. lately. It has memory > corruption problems. The cvsup/cvsupd servers break regularly when > they corrupt their checkouts files and fetch the same data over and > over and over again, crashing each time. > > And worse.. cvsup/cvsupd doesn't understand the version of cvs we have > in the freebsd tree. *Every* *single* *commit* causes a checksum > error and re-fetch. For the cvs/rcs ,v files, it degenerates into the > old sup(1) mode - not even rsync. > > It is more efficient to transport the src cvs repository with rsync + > rsyncd these days than cvsup/cvsupd. > > I'm sorry, but it is time to move on. Understood. --Chris > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV > bitcoin:188ZjyYLFJiEheQZw4UtU27e2FMLmuRBUE > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?718d7f7cb15cabfe2894a85f0c262aff.authenticated>