Re: [viewvc-users] cvsdbadmin does not parse commits

"C. Michael Pilato" <[email protected]>
Newsgroups gmane.comp.version-control.cvs.viewcvs.user
Organization CollabNet, Inc.
Message-ID <[email protected]>
>> This is certainly unexpected.  cvsdbadmin works as expected on my Ubuntu
>> 10.10 system, which has the distribution's RCS 5.7 installed.  Now, in
>> fairness, my CVS repositories (which only exist so that I can test ViewVC)
>> were probably generated with older versions of CVS.  Maybe your repositories
>> were created by more recent CVS versions which don't write the RCS ,v
>> backing files the same way that ViewVC expects?  I dunno.
>>
> 
> Thanks for the response. I figured out the problem. It was a
> misconfiguration of the viewvc.conf. I had enabled the *cvsnt* option
> and had it pointing to */usr/bin/cvs*. Now, the server had GNU CVS
> installed and not cvsnt. After disabling this option, viewvc
> successfully used RCS to parse the log information.

Cool.  Glad you figured that out!

>> If you have a ,v file that contains innocuous, non-private information in
>> it, I'd be more than happy to try to reproduce the problem you are seeing on
>> my machine here and debug it.
>>
> 
> Right now, rlog parses most ,v files correctly. However, ",v" files that
> have the *filename* directive with an underscore value do not get
> parsed. For example:
> 
> 1.3
> date    2010.04.22.18.51.57;    author amit;    state Exp;
> branches;
> next    1.2;
> deltatype       text;
> kopt    kv;
> permissions     666;
> commitid        1de44bd09aa755be;
> filename        APP_MAIN.C;
> 
> Removing the line that contains filename allows RCS to parse this file.
> It seems as if the *filename* is a CVSNT specific syntax and is not
> valid RCS.

The "filename" token is a CVSNT addition, yes.  RCS is a relatively flexible
format, though, built for expansion and customization.  Interesting that you
only see problems on files with underscores in their names...  my
understanding of the RCS file format does *not* lead me to believe that the
underscore character is specifically disallowed.  *shrug*   At least it
seems you have a workaround that's doing the trick for you.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2709331

To unsubscribe from this discussion, e-mail: [[email protected]].
signature.asc (application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk1vt5UACgkQokEGqRcG/W5oygCgnxKEVkpg3QOSJrZlrMa0w0BX
gE0AnAo0hcoKTVABJteiQ+Iyzyry/0Xq
=RT9P
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.