Am 11/07/14 um 15:15 schrieb Alexander Hall: > On November 7, 2014 2:55:50 PM CET, Stefan Wollny <stefan.wol...@web.de> > wrote: >> Am 11/06/14 um 13:38 schrieb Nick Holland: >>> On 11/06/14 02:36, Stefan Wollny wrote: >>>> Hi there! >>>> >>>> This morning I fetched the latest snapshots (#537) from >>>> ftp.hostserver.de. As usual after rebooting I updated the sources >> from >>>> the same server being set in '.profile' as CVSROOT. >>>> >>>> This time I noticed a lot of warnings for s.th. needing to be a >> absolute >>>> path. At the end I saw the following: >>>> >>>> <quote> >>>> cvs update: CVSROOT "U:" must be an absolute pathname >>>> cvs [update aborted]: Bad CVSROOT >>>> </quote> >>> >>> and what IS $CVSROOT? >>> Not what you THINK it is...what is it really? >>> >>>> I did an other update-run from openbsd.cs.fau.de and noticed too the >>>> warnings about the absolute pathnames, but not the "update aborted" >> note >>>> as with ftp.hostserve.de. >>>> >>>> Is this a (known) issue server-sided or is s.th. broke on my side??? >>> >>> impossible to say with the information provided -- note you have >>> provided (some) error messages and ZERO information about what you >>> actually did, that's usually an indication of a user error. >>> >>> Putting your CVSROOT in your command line is a good way to solve a >> lot >>> of problems and troubleshoot the rest. Simply setting it as an >>> environment variable causes it to be used ONLY if there's nothing on >> the >>> command line AND nothing in the CVS tree. >>> >>> Nick. >>> >> ~ $ cat .profile | grep CVS >> >> >> #CVSROOT=anon...@openbsd.cs.fau.de:/cvs >> CVSROOT=anon...@ftp.hostserver.de:/cvs >> #CVSROOT=anon...@anoncvs.spacehopper.org:/cvs >> #CVSROOT=anon...@anoncvs.openbsd.org:/cvs >> #CVSROOT=anon...@anoncvs.bytemine.net:/cvs >> export PKG_PATH CVSROOT >> >> ~ $ print $CVSROOT >> anon...@ftp.hostserver.de:/cvs >> >> I am pretty confident that $CVSROOT has never-ever been anything other >> than one of the above. >> >> "ZERO information" about what I did??? Beside what I have been writing >> - >> what else would be of interest? >> >> Step 1: Boot OpenBSD >> Step 2: Login with an user privileged by sudo >> Step 3: Run script to fetch the snapshot-files from 'ftp.hostserver.de' >> Step 4: Reboot >> Step 5: Login again with the same user as previous >> Step 6: cd to /usr/src >> Step 7: Run 'sudo cvs -q up -Pd' > > I don't recall sudo being mentioned before. In pretty sure it will eat your > $CVSROOT unless you specifically configured it not to. > > Either way try running cvs with -d $CVSROOT. > > My guess is you have one or more borked CVS/Root in the tree. > > /Alexander > Hi Alexander,
thank you for your fast reply - I will delete /usr/src, /usr/ports and /usr/xenocara first and get a fresh checkout. I will adjust my little script according your advice and check if the messages pop up again after the next snapshots are out. Cheers, STEFAN
