Date: Mon, 19 May 2008 18:12:00 -0700 From: "Peter Wemm" <peter@wemm.org> To: "Garrett Cooper" <yanefbsd@gmail.com> Cc: Max Laier <max@love2party.net>, Ian FREISLICH <ianf@clue.co.za>, freebsd-current@freebsd.org Subject: Re: Anyone else seeing this (cvs wierdness)? Message-ID: <e7db6d980805191812q1e162d0bgd7e42c87685512be@mail.gmail.com> In-Reply-To: <0FBE942C-4EE3-47A1-B1D5-A62ED0F06C3F@gmail.com> References: <E1JxoXB-0001Ij-TZ@clue.co.za> <0FBE942C-4EE3-47A1-B1D5-A62ED0F06C3F@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 18, 2008 at 5:36 PM, Garrett Cooper <yanefbsd@gmail.com> wrote: > On May 18, 2008, at 12:27 PM, Ian FREISLICH wrote: > >> Max Laier wrote: >>> >>> On Friday 16 May 2008 16:12:39 Ian FREISLICH wrote: >>>> >>>> Recently - I guess in the last month or two - successive cvs updates >>>> always "updates" files in the follwing directories, this with no >>>> update to the CVS repo: >>>> >>>> cddl/contrib/opensolaris >>>> contrib/ntp >>>> contrib/ipfilter >>>> contrib/expat >>>> contrib/tcsh >>>> >>>> I sync a local CVS repo using cvsup and I update my source using >>>> 'cvs -q update -PdA' >>>> >>>> I've tried removing the offending parts of my source tree and the >>>> repo and re-updating or syncing them but to no avail. Is it just >>>> me or are others seeing this? Has there been repo "surgery" in >>>> these areas that's causing this? >>> >>> Is this with the updated cvs 1.11 (recently imported to current)? There >>> has been some reports of fallout of this on cvs-all@ already. >> >> It's with: >> >> Concurrent Versions System (CVS) 1.11.22.1-20080310-FreeBSD >> (client/server) >> >> Glad to hear the madness probably isn't with me. >> >> Ian >> >> -- >> Ian Freislich > > I'm not sure about cvs, but I've been seeing some weirdness with csup lately > syncing from HEAD and the fact that it doesn't match cvs... that's most > likely some entirely different issue though. > -Garrett David broke cvs with his last few imports. The two problems that I know of are all related to 'cvs update'. - cvs update -C doesn't work right. It might not restore the modified files to clean status. - cvs update -A checks out over and over again if the -ko flag is set on the files. I've fixed the -ko issue in the repository by removing it from there, so at least the -A bug won't be so annoying. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e7db6d980805191812q1e162d0bgd7e42c87685512be>