Date: Mon, 16 Dec 1996 13:56:43 -0800 From: "Dima Ruban" <dima@burka.rdy.com> To: John Polstra <jdp@polstra.com>, ernie@spooky.eis.net.au Cc: freebsd-current@freebsd.org, peter@freebsd.org Subject: Re: SUP of current weird Message-ID: <961216135643.ZM22781@burka.rdy.com> In-Reply-To: John Polstra <jdp@polstra.com> "Re: SUP of current weird" (Dec 15, 1:04pm) References: <199612142219.IAA10425@spooky.eis.net.au> <199612152104.NAA28986@austin.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 15, 1:04pm, John Polstra wrote: > Subject: Re: SUP of current weird > In article <199612142219.IAA10425@spooky.eis.net.au> you write: > > I noticed over the last few days that there have been a few minor bugs that > > stop a make world in -current so I simply run sup again to get the latest > > fixed the next day. However every time I run sup it seems to want to > > retreive most of the contrib directory again which is wastefull. > > > > Has there been major patches every day of the last week to the contrib dir > > that forces sup to download it again? Or is there something odd going on? > > There have been very few commits to contrib lately. There is something > odd going on. > > > It only seems to be the contrib dir the other just update changed files as > > normal. > > > > Any suggestions? > > Your supfile line looks fine. I looked around a bit on sup.freebsd.org. > The problem appears to be a bug in cvs-1.6.3, which is the version used > there. > > Periodically (every day, I suppose) the source tree there is updated > with "cvs update -APd". For some reason, this is causing the > modtimes of the contrib files to be updated, even though the files > haven't changed. (2554 files under contrib on sup.freebsd.org have > been touched in the past 24 hours.) > > I tried some experiments on two machines here, one running cvs-1.6.3, > and the other running cvs-1.8.1. Both times, I did this: > > cvs checkout contrib_libpcap > cd contrib_libpcap > ls -lt > cvs update -APd > ls -lt > > On the -1.6.3 machine, zillions of files got "updated", and their > modtimes were touched. On the -1.8.1 machine, the "cvs update" did > nothing. > > Peter: Is this a known bug? > > Dima: Could you update your cvs to the version from -current? Ugh ... actually I can, but I'm running -stable here, and every time I'm recompiling system - I'll have to recompile cvs stuff after that. The question is - how about to bring these changes from -current to -stable? (I know, -stable is almost dead, but this is a bug fix, so it should be realy usefull) > > Ernie: If you were using CVSup, this wouldn't be happening to you. > (Sorry, I couldn't resist. :-) > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth >-- End of excerpt from John Polstra -- dima
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?961216135643.ZM22781>