info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Assert Failure: cvs: lock.c:173: lock_name: Assertion `strncm p (r


From: Nesbitt, Steve
Subject: RE: Assert Failure: cvs: lock.c:173: lock_name: Assertion `strncm p (r
Date: Thu, 7 Jun 2001 13:14:19 -0700

All:

Thanks - I suspected it was something like this, but wasn't sure.

-steve
Steve Nesbitt
Configuration Manager
The Cobalt Group, Inc.
2200 First Avenue South
Seattle, WA 98134
address@hidden
www.cobaltgroup.com
If it's automotive and it's Internet, it's Cobalt.



-----Original Message-----
From: address@hidden [mailto:address@hidden]
Sent: Wednesday, June 06, 2001 11:40 AM
To: Nesbitt, Steve
Cc: address@hidden
Subject: Re: Assert Failure: cvs: lock.c:173: lock_name: Assertion
`strncmp (r


Nesbitt, Steve writes:
>
> cvs: lock.c:173: lock_name: Assertion `strncmp (repository,
> CVSroot_directory, strlen (CVSroot_directory)) == 0' failed.
> Terminated with fatal signal 6
[...]
> This command was working last week. The only known change is that the
> repository was copied to another disk yesterday because of disk space
> problems.

And that's the cause of the problem.  CVS doesn't like it when CVSROOT
is a symlink rather than a real directory.  You may be able to use some
kind of "loopback" mount rather than a symlink.  If not, you'll have to
change everyone's CVSROOT or live with the things that don't work.

-Larry Jones

See, it all makes sense.  See?  See??  They never see. -- Calvin


reply via email to

[Prev in Thread] Current Thread [Next in Thread]