On Fri, Jan 27, 2012 at 9:10 PM, Dave Anderson <d...@daveanderson.com> wrote: > I've run into this problem perhaps a dozen times over the past several > months while running amd64-current, most recently at 15:53 2012/1/26 EST > while running a system built from source updated at about 14:30 > 2012/1/21 EST: when trying to update the xenocara source tree there is a > very long (perhaps infinite) delay between issuing the 'cvs ...' command > and the start of any visible activity. B In this most recent case the > delay was about 9 hours. B Updating the src and ports source trees at > about the same time and using the same CVSROOT has always worked OK; > there's some delay but not a really long one. B And sometimes the > xenocara update has worked without any problem. B When it doesn't, 'rm > -rf /usr/xenocara' followed by reloading from the 5.0-release CD has > always allowed a subsequent cvs update to work. > > The command I'm using is > B # cd /usr/xenocara && cvs -d$CVSROOT -q up -Pd > (except for the working directory, exactly the same as the command for > updating the src or ports tree).
How about: # cd /usr ; cvs -d$CVSROOT -q up -Pd xenocara > > This has happened with several different values for CVSROOT, currently > B # echo $CVSROOT > B anon...@anoncvs1.usa.openbsd.org:/cvs > > I am very confused by this. B Any clues would be greatly appreciated. > > B B B B Dave > > -- > Dave Anderson > <d...@daveanderson.com>
