Date: Mon, 09 Dec 1996 19:59:59 -0800 From: John Polstra <jdp@polstra.com> To: freebsd-hackers@freebsd.org Subject: Attention CVSup users! Message-ID: <199612100400.UAA29391@austin.polstra.com>
next in thread | raw e-mail | index | archive | help
If you have started to get messages like these when you do your CVSup
updates:
Unknown release "current" for "src-eBones"
Unknown release "current" for "src-secure"
Unknown release "stable" for "src-eBones"
Unknown release "stable" for "src-secure"
it's because your cvsupfile isn't correct. To get the "current"
release, you should have this in your supfile:
release=cvs tag=.
To get the "stable" release, you should have this:
release=cvs tag=RELENG_2_1_0
I am only seeing this in the logs for the src-eBones and src-secure
collections, and I think I know why. You probably started with a sample
supfile that had those two releases commented out. Then you ran supconv
on it. Then, later, you uncommented the lines for the above
collections. Since supconv doesn't touch comments, those lines never
got converted properly.
It used to accidentally work if you had "release=current" or
"release=stable", but it didn't work efficiently. Now it doesn't work
at all, so you'll have to fix your cvsupfiles.
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?199612100400.UAA29391>