Issue 3640 - anon cvs giving error on check out
Summary: anon cvs giving error on check out
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL: anon cvs
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-23 23:40 UTC by foskey
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description foskey 2002-03-23 23:40:26 UTC 
I am getting an error on checking out of anon cvs.   Raising issue to ensure
there is not a server component to the error I am receiving.  Partial error follows:

? freetype/unxlngi3.pro
? nas/unxlngi3.pro
cvs: lock.c:177: lock_name: Assertion `(__extension__ (__builtin_constant_p (
strlen (CVSroot_directory))

I have seen a similar message previously on Open Office cvs,  it may be a bad
server message.

Also when there are too many people on the server the message appears that the
server is not found.  Is there a way to make this a 'come back later' type message?
Comment 1 lsuarezpotts 2002-05-05 08:59:53 UTC 
reassigning to support
louis
Comment 2 foskey 2002-05-05 10:41:39 UTC 
It appears that I was using an incorrect tag.  When I changed the tag
to OO_STABLE_1 it started working again.  I think that the error is
coming from you server because it is consistent despite upgrades of
client cvs on my side.
Comment 3 Unknown 2002-05-07 00:40:06 UTC 
Thanks for the update.  We do actually have a known issue open
internally reflecting the fact that checking out non-existant
tags/branches causes a crash (which is targeted for our upcoming
Truckee release).  I'll mark this issue to reflect that.
Comment 4 foskey 2002-07-15 14:35:20 UTC 
This apears to be solved.  Has the release gone in?
Comment 5 Unknown 2002-08-21 22:03:12 UTC 
closing with status resolved/later as it is resolved in the Truckee
release
Comment 6 foskey 2003-03-17 00:35:26 UTC 
This was a tag issue verified closed.
Comment 7 foskey 2003-03-17 00:36:35 UTC 
closing issue.
Comment 8 foskey 2003-03-17 00:37:18 UTC 
closing issue.
Comment 9 foskey 2003-06-18 13:11:42 UTC 
Closed.