On 23 Jan 2001, Didier Verna gibbered:
>| cvs update: move away bits/bbdb-filters/COPYING.LIB; it is in the way

This is a client issue, not a server-side one. (Rare, really; most of
the annoyances I get with CVS crop up on the server, where mortals
cannot fix them. I've never had any problems with the BBDB repository,
though.)

The CVS sources say:

,----[ src/client.c ]
|         /* This error might be confusing; it isn't really clear to
|             the user what to do about it.  Keep in mind that it has
|             several causes: (1) something/someone creates the file
|             during the time that CVS is running, (2) the repository
|             has two files whose names clash for the client because
|             of case-insensitivity or similar causes, (3) a special
|             case of this is that a file gets renamed for example
|             from a.c to A.C.  A "cvs update" on a case-insensitive
|             client will get this error.  Repeating the update takes
|             care of the problem, but is it clear to the user what
|             is going on and what to do about it?, (4) the client
|             has a file which the server doesn't know about (e.g. "?
|             foo" file), and that name clashes with a file the
|             server does know about, (5) classify.c will print the same
|             message for other reasons.
| 
|             I hope the above paragraph makes it clear that making this
|             clearer is not a one-line fix.  */
`----

and src/classify.c displays it if there is a user file (not mentioned in
CVS/Entries) which is not the same as the file being checked out.

(Has something happened to your CVS/ directories in your BBDB tree?)

-- 
`Anyhow, that pipe dream doesn't say anything about the question you
 asked.  (I am planning for a career in politics.)' --- Mark Mitchell
                                                      on the GCC list

_______________________________________________
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/bbdb-info

Reply via email to