Date: Fri, 04 Apr 1997 09:45:53 -0800 From: John Polstra <jdp@polstra.com> To: current@freebsd.org Cc: nate@mt.sri.com Subject: Re: Oops Message-ID: <199704041745.JAA24277@austin.polstra.com> In-Reply-To: <199704040539.WAA26546@rocky.mt.sri.com> References: <19970403182654.29991@Jupiter.Mcs.Net> <199704040143.RAA19367@austin.polstra.com> <19970403194951.58431@Jupiter.Mcs.Net> <199704040539.WAA26546@rocky.mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199704040539.WAA26546@rocky.mt.sri.com>,
Nate Williams <nate@mt.sri.com> wrote:
> > > > ***
> > > > *** runtime error:
> > > > *** Exception "RCSError.E" not in RAISES list
> > > > ***
> > >
> > > What version of CVSup are you running? Run "cvsup -v" to find out. I
> > > didn't see the problem here.
> >
> > I reloaded the entire tree and the problme went away.
>
> I had this problem, but it turned out I was running V13.5.
In private e-mail to me, Karl reported that he was running 13.5 as
well. The potential for this kind of problem is much reduced in
14.1.1, the current released version.
There is an unreleased version, 14.1.4, which I believe solves the
whole problem. In that version, I did some extensive restructuring
of the code that does file updates. Now there is a unified framework
that handles all the different kinds of updates (RCS, append, touch,
rsync, etc.). It greatly simplified and reduced the code. As a
side-effect, it makes it much easier to be sure that unexpected
situations like the one above are handled properly.
These kinds of errors only happen when something forbidden has
been done to the repository. What you are watching is an evolution
of my notions about what CVSup should reasonably be expected to deal
with in a CVS repository, either on the server or the client. It's
progressed something like this:
Only things done via legitimate "cvs" commands =>
Manual hacking around in the repository by well-meaning troublemakers =>
Complete trashing of repository files by well-meaning troublemakers =>
Anything except kernel errors =>
Anything except hardware errors =>
Anything except RAM errors =>
Any damn thing whatsoever. :-(
If anybody wants to use 14.1.4, it's in the "BETA" subdirectory of
the usual distribution points:
ftp://freefall.freebsd.org/pub/CVSup/ (California)
ftp://ftp.cs.tu-berlin.de/pub/FreeBSD/CVSup/ (Germany)
ftp://ftp.polstra.com/pub/FreeBSD/CVSup/ (slow; avoid if possible)
Freefall, the US mirrors, and some of the other mirrors have all
been running it for weeks without problems. It's only a "beta"
because I wanted to add a few more features before making another
official release. There's no port or package for it, but the
sources and static executables are available as usual.
By the way, I'd like to publicly thank the folks at Pluto Technologies
for supporting much of the work that went into 14.1.4, as well as
other enhancements that are underway. Check out their web page
some time: <http://www.plutotech.com/>. They're doing some pretty
cool things!
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704041745.JAA24277>