cvs freebios locked? [PMX:#]
John Usher (Maptek)
John.Usher at perth.maptek.com.au
Tue Jun 15 20:30:01 CEST 2004
It all sorted itself out overnight for me.
From: Greg Watson [mailto:gwatson at lanl.gov]
Sent: Tuesday, 15 June 2004 10:19 PM
To: John Usher (Maptek)
Cc: Gregg C Levine; linuxbios at clustermatic.org
Subject: Re: cvs freebios locked? [PMX:#]
Strange. I just tried to co both freebios and freebios2 using
pserver:anonymous and they both worked fine. Try removing the entire
tree and start from scratch.
On Jun 14, 2004, at 10:34 PM, John Usher (Maptek) wrote:
>> Hello from Gregg C Levine
>> Check your CVS command string. SF updated to a newer release of BIND,
>> and it has a problem with the way the domains were arranged from the
>> earlier versions. So it becomes like this:
>> "#cvs -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios
>> login" and then:
> Yeah. I discovered that cvs.freebios.sourceforge.net does nothing but
> time out for me.
>> "#cvs -z3 -d:pserver:anonymous at cvs.sourceforge.net:/cvsroot/freebios
>> co modulename". (With out the quotes or pound marks. And the line
>> included by my mailer.)
> The 'co' is working fine until it gets to that sis directory, so I've
> got all the mainboard stuff etc down...
> My command is equivalent to the above though I have CVSROOT set rather
> than using the -d flag. However, I would expect it to not work at all
> wrong, not get half of it then complain about a lock on the
> Its obviously only meant to be a temporary lock as well, because cvs
> retries every thirty seconds.
> There is a specific user with the lock on the .../northsouthbridge/sis
> directory, I just don't want to post it on here.
> Linuxbios mailing list
> Linuxbios at clustermatic.org
More information about the coreboot