Re: Any plan for file level CVS ACL in near feature?

[Peter Connolly]

Afaik, there is no way to restrict checkouts.


On 02 Mar 2005 12:41:48 +0530, Tushar <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-03-01 at 23:44, Peter Connolly wrote:
> > The 'cvs_acls' script in the 'contrib' directory:
> >
> > https://ccvs.cvshome.org/source/browse/ccvs/contrib/
> >
> > already supports file-level as well as directory-level access control.
> >  Since this is one of the 'commitinfo' scripts triggered at commit
> > time, it works for restricting the ability to commit files.
> >
> > pc
> Thanks for your answer. I have source of 1.12.11 downloaded from
> cvshomes.org. I was actually confused bet the CVS ACL from
> sourceforge.net which requires patching to source and this ACL. I think
> now I should be able to do it for commit. BTW , is there any way to have
> read restriction (i.e checkout) for files and dirs?
> 
> 
> >
> > On 01 Mar 2005 19:33:53 +0530, Tushar <[EMAIL PROTECTED]> wrote:
> > > Hi all,
> > > I want to known if there is any method to have file level access control
> > > using CVS. Also is it expected in near feature as a standard feature?
> > > Regards,
> > > Tushar
> > > 
> > > Visit us at CeBit Hannover, Germany, Hall No. 6, Stand No. H02 from 10th 
> > > to 16th March 2005.
> > > For Appointments write to us or visit our website http://www.mwti.net
> > >
> > > ___
> > > Info-cvs mailing list
> > > Info-cvs@gnu.org
> > > http://lists.gnu.org/mailman/listinfo/info-cvs
> > >
> >
> 
>


___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs

Re: Any plan for file level CVS ACL in near feature?

[Peter Connolly]

The 'cvs_acls' script in the 'contrib' directory:

https://ccvs.cvshome.org/source/browse/ccvs/contrib/

already supports file-level as well as directory-level access control.
 Since this is one of the 'commitinfo' scripts triggered at commit
time, it works for restricting the ability to commit files.

pc

On 01 Mar 2005 19:33:53 +0530, Tushar <[EMAIL PROTECTED]> wrote:
> Hi all,
> I want to known if there is any method to have file level access control
> using CVS. Also is it expected in near feature as a standard feature?
> Regards,
> Tushar
> 
> Visit us at CeBit Hannover, Germany, Hall No. 6, Stand No. H02 from 10th to 
> 16th March 2005.
> For Appointments write to us or visit our website http://www.mwti.net
> 
> ___
> Info-cvs mailing list
> Info-cvs@gnu.org
> http://lists.gnu.org/mailman/listinfo/info-cvs
>


___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: ACL status

[Peter Connolly]

There's a newer version of the 'cvs_acls' script in the CVS CVS
repository (I meant to say that;-)

https://ccvs.cvshome.org/source/browse/ccvs/contrib/

that has more documentation (check the 'cvs_acls.html' POD file), a bit
more fine-grained control and some extra features (such as logging
support and optional site-specific messaging).

It hasn't found its way into the general releases yet.

pc 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Matt Doar
> Sent: Thursday, January 13, 2005 11:28 AM
> To: Rafael Sanz; info-cvs@gnu.org
> Subject: RE: ACL status
> 
> 
> Take a look at the cvs_acls script in the conrtib subdirectory in the
> CVS source from cvshome.org. It's pretty easy to use and restricts
> access by user, directory and branch.
> 
> ~Matt
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] 
> > [mailto:[EMAIL PROTECTED] 
> > On Behalf Of Rafael Sanz
> > Sent: Thursday, January 13, 2005 7:31 AM
> > To: info-cvs@gnu.org
> > Subject: ACL status
> > 
> > Hello, I need to extend my cvs server with fine grain of 
> > Access Control
> > Level (beyond writers or readers files natives in CVS standar).
> > 
> > I'm found some references to patches at C code
> > (http://www.unixgods.org/~tilo/CVS_ACL/), but any is standard...
> > 
> > What is the develop status of ACL in cvs server for UNIX?? Is 
> > in progress?
> > Nothing about?
> > 
> > Whatever, some link better to ACL solutions that deal with 
> > read restriction
> > for files or directories?
> > 
> > Thanks in advanced.
> > 
> > 
> > 
> > 
> > ___
> > Info-cvs mailing list
> > Info-cvs@gnu.org
> > http://lists.gnu.org/mailman/listinfo/info-cvs
> > 
> 
> 
> ___
> Info-cvs mailing list
> Info-cvs@gnu.org
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: CVS Feature Version 1.12.11 Released!

[Peter Connolly]

Sorry, I guess my question was not clear.  I would like to have a list
of the features that have been added to the 1.12 "feature release."  

Except for the recent versions that highlight "NEW FEATURES," the 1.12
NEWS file contains bug fixes, security issues and new features all
lumped together.

The diff remark was a joke.  The diff would be between the NEWS file for
1.11.x and 1.12.x as a desperate attempt to gleen the new features out
of the 1.12 NEWS file.  But even if that yielded some results, wouldn't
it make sense to have a separate file/page/whatever that highlights the
new features rather than making everyone try to figure it out?

pc

> -Original Message-
> From: Derek Robert Price [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, December 14, 2004 10:36 AM
> To: Peter Connolly
> Cc: [EMAIL PROTECTED]
> Subject: Re: CVS Feature Version 1.12.11 Released!
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Peter Connolly wrote:
> 
> > RE: CVS Feature Version 1.12.11 Released!
> >
> > Short of each of us diff'ing the two NEWS files, is there a digest
> of the new features on the 1.12 branch?
> 
> I'm sorry?  Why would you need to diff which two NEWS files?
> 
> Derek
> - --
> *8^)
> 
> Email: [EMAIL PROTECTED]
> 
> Get CVS support at <http://ximbiot.com>!
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFBvzKGLD1OTBfyMaQRAs63AJ93oGS1/oSforW7aM3Wg1Ibq2s4iwCfeMC2
> hXAeDJixktF4k5rZYck9/ik=
> =QJSr
> -END PGP SIGNATURE-
> 
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: CVS Feature Version 1.12.11 Released!

[Peter Connolly]

Title: RE:  CVS Feature Version 1.12.11 Released!






Short of each of us diff'ing the two NEWS files, is there a digest of the new features on the 1.12 branch?

pc

-Original Message-
From: Derek Robert Price [mailto:[EMAIL PROTECTED]]
Sent: Mon 12/13/2004 12:34 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject:  CVS Feature Version 1.12.11 Released!

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Feature CVS 1.12.11 has been released.  Feature releases contain new
features as well as all the bug fixes from the stable releases.  This
version fixes a few minor bugs in both the CVS client and server
executables, as well as extending the write proxy functionality slightly.

We recommend this upgrade for all CVS clients and servers already
running the feature release and for those who simply like to stay on
the cutting edge!

Take a look at the NEWS file

from the source distribution for a more exhaustive list of changes or
go directly to the downloads page
.

My PGP public key, ID# 0x17F231A4, is available from pgp.mit.edu and
its associated key servers, for verifying signatures on released files.

Cheers,

Derek

- --
    *8^)

Email: [EMAIL PROTECTED]

Get CVS support at !
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBvfzILD1OTBfyMaQRAtfrAKC4UJKgNIChkGzlTjWTTuY/pc2OCwCeIu0Z
7hcmLdgo9fpa+8aZ8tfCrOc=
=l8lv
-END PGP SIGNATURE-


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]









___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: disabling branch commit

[Peter Connolly]

Thanks for the reference Mark!

The latest script (March 24) is located in the enhancement bug:

https://ccvs.cvshome.org/issues/show_bug.cgi?id=170

pc 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Mark D. Baushke
> Sent: Friday, September 10, 2004 3:13 PM
> To: Fernando Silveira
> Cc: [EMAIL PROTECTED]
> Subject: Re: disabling branch commit 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Fernando Silveira <[EMAIL PROTECTED]> writes:
> 
> > Dear list,
> > 
> >I work for a software development company and we use CVS 
> to control
> > our source code. Right now I am trying to make my CVS 
> server to disable
> > commits to a specific BRANCH (or TAG) of a module.
> > 
> >I've studied and tryied it a lot of times using "commitinfo",
> > "loginfo" and other configuration files but I had no 
> success. It seems
> > that I cannot have the information of which revision, tag or branch
> > before committing to block it, but I'm not sure. I wonder 
> if you could
> > help me with this problem, have any tips, docs or anything 
> that helps or
> > tells if it is possible or not.
> > 
> > Thanks in advance.
> 
> The list has talked about branch locking and access control 
> on multiple
> occasions.
> 
> The following link points to a reasonable cvs_acls2 script:
> 
>   http://lists.gnu.org/archive/html/cvs-utils/2004-02/msg00047.html
> 
> that allows you the control you wish.
> 
>   -- Mark
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3 (FreeBSD)
> 
> iD8DBQFBQib03x41pRYZE/gRAoHnAJ9/NnL1/QoOp0BKAk4EKQ8vgYZ1vACghD4m
> ZrebyJyihK5QCAvauXxp67c=
> =0rrA
> -END PGP SIGNATURE-
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

Any 'contrib' scripts have access to pre-commit source?

[Peter Connolly]

I would like to restrict certain types of changes to specific files in
the repository.  I'm using pserver access.  In order to do this I need
access to the source that is going to be committed.

So, I was planning to write a script that would:

1) examine the pre-commit source
2) return a non-zero return code that would prohibit the commit

commit_prep seems to be the ideal place to trigger such a script, but
there doesn't appear to be any parameters in the commitinfo file that
would forward the pre-commit source to the script.

Any help would be appreciated.

Thanks,
pc


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: cvs command not available

[Peter Connolly]

I don't think CVS is installed by default.  You might want to check the
'devel' tree in the Cygwin setup to make sure that CVS is checked before
starting the download/install.


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Jacky Luk
> Sent: Monday, July 19, 2004 1:32 PM
> To: [EMAIL PROTECTED]
> Subject: cvs command not available
> 
> 
> I am using cygwin 1.5.10.1
> However, when I was using the bash shell, typing "cvs. 
> login" it said
> command not found? Could anyone help? Do I need to seperately 
> check out that
> file somewhere?
> Thanks
> Jack
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: Ristricting access to CVSROOT....

[Peter Connolly]

I enhanced the original contrib/cvs_acl:

https://ccvs.cvshome.org/issues/show_bug.cgi?id=170

Although it's not yet part of the regular distribution, you may want to
take a look.

pc

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Mark D. Baushke
> Sent: Thursday, July 15, 2004 4:39 PM
> To: Hamid Ghassemi
> Cc: [EMAIL PROTECTED]
> Subject: Re: Ristricting access to CVSROOT 
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hamid Ghassemi <[EMAIL PROTECTED]> writes:
> 
> > This may have been asked before; however, I cannot find the answer
> > anywhere.
> 
> See https://www.cvshome.org/docs/manual/cvs-1.11.17/cvs_18.html#SEC169
> https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in
> https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.i
n?rev=HEAD

> We are trying to restrict access to CVSROOT directory such that only a
few
> can make changes to it and all other can checkout only to read.  How
can
> this be done?
 
Have the commitinfo script have an entry for CVSROOT which runs a
script. The script returns a zero exit code when $USER is in the allowed
list and a non-zero code when $USER is not in the list.

Look at contrib/cvs_acls in a tree where you built cvs 1.11.17 for ideas
or
https://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in?rev=HEAD

-- Mark


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFA9xWw3x41pRYZE/gRAn/pAJ9KEaJZw3xoKcrLfEDe9nwyNPMiggCfYLeU
Duoi9VpHwMOa4kiu7XW1jtc=
=zRva
-END PGP SIGNATURE-


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: Assert error checking out tagged files with -p option

[Peter Connolly]

I think that the problem is that the 'val-tags' admin file is being checked
for an entry and new tags do not have an entry created in that file until a
checkout or update (without the -p option) has been performed.  Here is one
bug in the CVS queue related this problem:

"checkout (or update) with -p fails because val-tags doesn't have new tag
yet"  
https://ccvs.cvshome.org/issues/show_bug.cgi?id=186

And here is a related one (I think):

"`cvs co -rTAG -f' fails if TAG isn't in val-tags"
https://ccvs.cvshome.org/issues/show_bug.cgi?id=31

In the meantime, the workaround is to checkout with that tag before using
the -p option.


> -Original Message-
> From: [EMAIL PROTECTED] [mailto:info-cvs-
> [EMAIL PROTECTED] On Behalf Of Abhinandan Jain
> Sent: Wednesday, June 16, 2004 6:37 PM
> To: [EMAIL PROTECTED]
> Subject: Assert error checking out tagged files with -p option
> 
> I am using cvs 1.11.17 and am getting assert errors when using the "-pr"
> tagged checkout option for a freshly tagged file. That is, if I
> 
>  1) tag a file A with tag B
>  2) right away checkout the file using "-pr B", I get an assert error of
> the form
> 
> Assertion failed: repository != NULL, file ../../src/recurse.c, line
> 641
> cvs [checkout aborted]: received abort signal
> 
>  3) If however I checkout the file without the -p option, i.e. using
> simply  "-r B", things work, and strangely enough, after this the
> "-pr B" option also starts working.
> 
> Unforutnately, if I now use a new tag "C", I get exactly the same
> problem going from step 1-3 with this new tag. So it appears that this
> version of CVS requires at least one checkout to the file system using a
> new tag before the tag can be used with the "-p" option.
> 
> This beharior is causing quite a few problems in our environment.
> 
> I have included a short test case below which reproduces the problem:
> 
> # create a new repository
> cvs -d /home/jain/tempRepo init
> 
> # import a single file "tmpfile" into the repository
> mkdir tmpdir
> touch tmpdir/tmpfile
> cd tmpdir
> cvs -d /home/jain/tempRepo import -m "" tmpmod ddd ggg
> 
> # checkout "tmpfile" and tag it with the "tmptag" tag
> cvs -d /home/jain/tempRepo co tmpmod
> cvs -d /home/jain/tempRepo tag tmptag tmpmod/tmpfile
> 
> # try to checkout tmpfile with the -p -r tmptag options
> cvs -d /home/jain/tempRepo co -P -p -r tmptag tmpmod/tmpfile
> 
> This results in the error message:
> 
>   Assertion failed: repository != NULL, file ../../src/recurse.c, line 641
>   cvs [checkout aborted]: received abort signal
> 
> # try to checkout tmpfile with the "-r tmptag" option (no -p option)
> cvs -d /home/jain/tempRepo co -P -r tmptag tmpmod/tmpfile
> 
> WORKS! Checks out tmpfile to the file system.
> 
> # try the -p -r tmptag option again
> cvs -d /home/jain/tempRepo co -P -p -r tmptag tmpmod/tmpfile
> 
> WORKS!! No more problems using -pr option with the tmptag tag.
> 
> Thanks in advance for any help.
> 
> Abhi
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://lists.gnu.org/mailman/listinfo/info-cvs




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: Remote CVS access via SSH

[Peter Connolly]

ssh-keygen

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of [EMAIL PROTECTED]
> Sent: Monday, June 14, 2004 1:47 PM
> To: [EMAIL PROTECTED]
> Subject: Remote CVS access via SSH
> 
> 
> Sorry if this does NOT belong to this group. I'm only hoping
> someone has done this before...
> 
> Ok, I finally got this working. Understandly so, whenever I enter
> a CVS command, I'm prompted for a password so I can tunnel through.
> As you folks know, this is a LOT of passwords to enter per session.
> My "Essential CVS" book says,
> 
> "...generate an SSH key for the client, using the key- generation 
> program. You may want to add the key to the user's home directory 
> on the server, as explained in the documentation for your SSH 
> program. 
> If you do so, the user won't need to provide a password when 
> connecting 
> with SSH."
> 
> We use RH Fedora, which has OpenSSH. Where is this "key-generation"
> prgram?
> 
> --
> Chris T Fouts
> Infineon Technologies Corp
> 3000 CentreGreen Way
> Cary, NC 27513
> Phone: (919)677-3016
> Fax: (919)678-1929
> Email: [EMAIL PROTECTED]
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: cvs with mysql

[Peter Connolly]

Reposting without all the Outlook formatting garbage...  As well as that
proprietary garbage at the end...

pc

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Peter Connolly
Sent: Monday, June 07, 2004 9:30 AM
To: Ramanuj Singh; [EMAIL PROTECTED]
Subject: RE: cvs with mysql


Take a look at Bonsai:

http://www.mozilla.org/projects/bonsai/

or XCVS (if you're Windows only):

http://xcvs.sourceforge.net/

pc
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Ramanuj Singh
Sent: Monday, June 07, 2004 4:11 AM
To: '[EMAIL PROTECTED]'
Subject: cvs with mysql


How can we store the cvs operations in RDBMS-MySQL. For eg- whenever a
tag or rtag command is executed the user name, name of tag ,module name,
and the date gets stored in MySQL.
We need to do it for each cvs operations. Is there any tool or we have
to write a script in perl for it
Thanks in advance
 



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: reports

[Peter Connolly]

Take a look at Bonsai:

http://www.mozilla.org/projects/bonsai/

or XCVS (if you're Windows only):

http://xcvs.sourceforge.net/

pc

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Ramanuj Singh
Sent: Saturday, June 05, 2004 7:33 AM
To: '[EMAIL PROTECTED]'
Subject: reports


How cvsgraph/cvsweb extract tags and branches from repository. I have
gone through their codes but I m harldly able to get some information
about the extraction of tags and branches. Or give me a script which
gives information about all the tags and branches along with the date of
creation  and name of author. This is really urgent as I m new in CVS
and working as cvs administrator. Don't tell me about the history
command as it generates reports only for the tags created with rtag
command.
Even CVSWeb also gives the graphical view of branch and tag. If u can
help me in this scenario , I will be grateful to u. Have to generate
this kind of report on urgent basis. 
I need the kind of report as history command generates for all tags. As
I have mentioned earlier the history command is not of great help as
generates report about the tags or branches created by rtag command. So
the tags created by simple tag command are not mentioned in this repor
 
I need to generate report from cvs reporsitory for a project which
displays the fields as I mentioned before. Don't need to just look up in
wincvs and get information. I have to generate report from cvs
repository. Not have to manually see those information and pen it down.
May be a script can do. There are many projects in our repository and
for each project looking at the graphical view and penning down the
information is not the stuff we have to do. I have to submit the reports
about the tags and branches on Monday. I m cvs newbee. So its really
urgent. 
The format for the report which will do is as follows, 
DateName of tag or branch Name of the author 
Right now have to generate report for the project of duration of three
months from march to may, on weekly basis 
So may be now u get the thing wat I want. 
 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: cvs with mysql

[Peter Connolly]

Title: Message



Take a look at Bonsai:
 
http://www.mozilla.org/projects/bonsai/
 
or XCVS (if you're Windows 
only):
 
http://xcvs.sourceforge.net/
 
pc

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Ramanuj SinghSent: Monday, June 07, 2004 4:11 AMTo: 
  '[EMAIL PROTECTED]'Subject: cvs with mysql
  
  How can we store the cvs 
  operations in RDBMS-MySQL. For eg- whenever a tag or rtag command is executed 
  the user name, name of tag ,module name, and the date gets stored in 
  MySQL.
  We need to do it for each cvs 
  operations. Is there any tool or we have to write a script in perl for 
  it
  Thanks in 
  advance
   
  The information transmitted is intended only for 
  the person or entity to whom it is addressed and may contain confidential and 
  / or privileged Material. Any review, re-transmission, dissemination or other 
  use of or taking of any action in reliance upon, this information by persons 
  or entities other than the intended recipient is prohibited. If you received 
  this in error, please contact the sender and delete the material from your 
  computer. Thank you for your understanding & co-operation. 
  
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: CVS corrupts binary files ...

[Peter Connolly]

> You may wish to choose a tool that is better for
> your particular needs. cvs is not at that friendly
> at controlling and merging binary files.

Actually, if there are a lot of binary files in your repository, you might
want to consider switching to Subversion (http://subversion.tigris.org/)
since it mimics many of the CVS commands; has better support for binary
files; and there is a conversion script (http://cvs2svn.tigris.org/).

pc




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: CVS corrupts binary files ...

[Peter Connolly]

> Too dificult to set up, I think
> Shouldn't cvs have a list of binary file types
> preinstalled in the cvswrappers ?

I agree, it should.




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: CVS corrupts binary files ...

[Peter Connolly]

> You may wish to choose a tool that is better for
> your particular needs. cvs is not at that friendly
> at controlling and merging binary files.

Actually, if there are a lot of binary files in your repository, you might
want to consider switching to Subversion (http://subversion.tigris.org/)
since it mimics many of the CVS commands; has better support for binary
files; and there is a conversion script (http://cvs2svn.tigris.org/).

pc




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: CVS corrupts binary files ...

[Peter Connolly]

> Too dificult to set up, I think
> Shouldn't cvs have a list of binary file types
> preinstalled in the cvswrappers ?

I agree, it should.




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: CVS corrupts binary files ...

[Peter Connolly]

And to make the -kb automatic with binary file types, modify your
cvswrappers file...

https://www.cvshome.org/docs/manual/cvs-1.11.16/cvs_18.html#SEC166



> -Original Message-
> From: [EMAIL PROTECTED] [mailto:info-cvs-
> [EMAIL PROTECTED] On Behalf Of Mark D. Baushke
> Sent: Friday, June 04, 2004 11:45 PM
> To: Adrian Constantin
> Cc: [EMAIL PROTECTED]
> Subject: Re: CVS corrupts binary files ...
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Adrian Constantin <[EMAIL PROTECTED]> writes:
> 
> > I've created a simple repository on a Linux server
> > with one module wich is a web site. My working
> > directory is on a Windows machine and I have to use
> > ssh to connect to the server. I've tried several ssh
> > clients and with all of them the checkout command
> > creates corrupted image files in my working directory.
> > The module has been imported on the Linux server, from
> > the server, and the checkout is done from the Windows
> > machine.
> >
> > If I just copy the images with WinSCP they are ok.
> > If I import them (on Linux) and then check them out
> > (on Windows) the images get corrupted
> >
> > Also text files do not transfer properly; there's a
> > strange square at the end of the lines after checkout.
> > Again copying with WinSPC is ok...
> >
> > I thought maybe the ssh client does LF<->CR/LF
> > mapping, but I've tried several, including OpenSSH,
> > and thingd didn't change.
> >
> > Must I tell explicitly to cvs that I transfer
> > text/binary files between different systems ?
> 
> Yes, for binary files. See the -kb switch.
> 
> > Or maybe I can't have sources on Windows and Linux in
> > the same time and cvs to function correctly ?
> 
> No. Sources which are text files will handle the line
> endings properly for the client. You are describing a
> problem with binary files.
> 
>   -- Mark
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3 (FreeBSD)
> 
> iD8DBQFAwWvW3x41pRYZE/gRApLPAKDX0WGqqbk/IXrayPtNyBFQ1Oiu5QCgka7J
> fj85gJI5pf+bjpcLRTHMIog=
> =wrTy
> -END PGP SIGNATURE-
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://lists.gnu.org/mailman/listinfo/info-cvs




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs

RE: Updated cvs_acls2 Access Control List script

[Peter Connolly]

Noted.

> -Original Message-
> From: Ville Skyttä [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, April 08, 2004 12:33 PM
> To: Derek Robert Price
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Aaron Voisine
> Subject: Re: Updated cvs_acls2 Access Control List script
> 
> 
> On Thu, 2004-04-01 at 03:39, Derek Robert Price wrote:
> 
> > I don't actually use this script.  Would someone who does 
> mind reviewing
> > Peter's changes?  Should I really check this in as a 
> separate script or
> > can I just update the old version and assume anyone who 
> needs something
> > older either already has it or can find the version in the 
> repository?
> > Ville?  Aaron?  Anybody?
> 
> I don't have time or a good place to test this thoroughly, sorry.
> My .02€: include it as a separate script, do not nuke the old cvs_acls
> just yet (or at all, since AFAICS the old one cannot be 
> upgraded to this
> one).
> 
> But if it was my call, before including this I'd require it 
> to run with
> warnings and taint checks on (ie. -wT in the shebang line), and add a
> "use strict;" near the top of the file.
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Tag and Branch with Same Name

[Peter Connolly]

Title: Message



Is there 
a script out there that can run through a repository and see if there are tags 
and branches with the same name?
 
Thanks,
pc
 
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: cvs (pserver) and LDAP ?

[Peter Connolly]

Before you consider that, you should read:

http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_2.html#SEC32

2.9.3.3 Security considerations with password authentication 

The passwords are stored on the client side in a trivial encoding of the
cleartext, and transmitted in the same encoding. The encoding is done
only to prevent inadvertent password compromises (i.e., a system
administrator accidentally looking at the file), and will not prevent
even a naive attacker from gaining the password. 


> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:info-cvs-
> [EMAIL PROTECTED] On Behalf Of Dorin Ciobanu
> Sent: Tuesday, March 30, 2004 4:29 AM
> To: [EMAIL PROTECTED]
> Subject: cvs (pserver) and LDAP ?
> 
> Hi !
> 
> Does anyone knows how to configure a pserver CVS repository and to use
> pam_ldap for athentication ?
> 
> Maybe a tutorial available ?
> 
> Thx !
> 
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: folder level access in cvs

[Peter Connolly]

There's another approach to controlling access to directory *and files*
that is in the 'contrib' subdirectory.  It's a script called cvs_acls
that provides access control lists for your repository.  It avoids the
increasing nastiness (IMO) of having to juggle an ever-expanding list of
*nix groups to match the different access requirements to your
repository.  That is the inevitable end-game of the approach described
in .

Having said that, I ran into some problems using the original script.
There were some bugs and some not-so-nice features.  As a result, I
rewrote the script last month.  The new script's name is cvs_acls2.  I
submitted it to the ccvs project this month for regular inclusion in its
distribution.  I think you may find it useful.  I've added the script
and its documentation into the issues log on the ccvs project
Issuezilla:



pc

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Sandhya
> Sent: Thursday, March 25, 2004 1:32 AM
> To: [EMAIL PROTECTED]
> Subject: folder level access in cvs
> 
> 
> Hi all,
> 
> Joining new to the team of mails... 
> Have started to be the admin of cvs for for the past 1 month. 
> Just wanted to know how to give read-
> write access on a folder level in cvs.
> I have tried readers and writers. but that works only for 
> repository level and not for modules or 
> directory level. If anyone can help me out how this can be 
> achieved, it wud be of great help to me.
> 
> Thanx in advance
> Sandhya.S
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Updated cvs_acls2 Access Control List script

[Peter Connolly]

Thanks to the feedback on the first release of this script.  

In particular, I'd like to thank Karl-Konig Konigsson for sending me debug trace with 
his emails.

Thanks to Derek Robert Price and Mark D. Baushke for the help on how to submit this 
script to 'contrib'.  (Do these guys ever sleep?)

I've posted the updated script as issue #170 on the ccvs Issuezilla.  Since the last 
drop on Feb. 26 we've fixed some errors in "global" restrictions; refactored some 
duplicate code; fixed the date/time stamp in the restricted_log file output; 
reformatted the code comments into pod format; and many others.

I also posted the script comments in pod2html format. It lists the updated 
installation, configuration, program logic and licensing information.

As usual, any input, feedback, corrections or suggestions you have are welcome.

Thanks,
pc



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Submitting a contrib script?

[Peter Connolly]

Title: Message



What is 
the normal way to submit a 'contrib' script to the CVS 
project?
 
Thanks,
pc
 
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: cvs_acl and cvsd

[Peter Connolly]

I posted a new version of cvs_acls to this mail group later in the day.
It is called cvs_acls2.  It addresses the problem you mention by
(optionally) allowing you to specify the client-side userId in the
commitinfo file so that access is controlled by the client-side userId,
not the pserver server-side userId.

Hope that helps.
pc

> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:info-cvs-
> [EMAIL PROTECTED] On Behalf Of Mohamed Eldesoky
> Sent: Thursday, February 26, 2004 1:38 AM
> To: CVS
> Subject: cvs_acl and cvsd
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi all,
> 
> I am preparing a CVS server for my organization, and I am using cvsd
and
> at
> the same time I want to use cvs_acl to determine who has access to
what.
> 
> Alas, it doesn't work, because it treats all users as if they are
(cvsd)
> user !!
> 
> Anyone succeeded to overcome this ??
> 
> I know this is not the place to ask this question, but I searched alot
in
> google, and I hope someone here has solved this before.
> 
> Regards
> Mohamed Eldesoky
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFAPb5r2FHsOWMJBKMRAkTkAKDBPusumJOk6WCzKTkuW0CoKXRWzwCgm5jS
> 4ZKb69cWCr2GYwcfW0uJGQM=
> =kBmo
> -END PGP SIGNATURE-
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Access Control for CVS

[Peter Connolly]

Check out cvs_acls in the contrib directory.


>-- Original Message --
>To: [EMAIL PROTECTED]
>From: "George Abraham" <[EMAIL PROTECTED]>
>Date: Fri, 27 Feb 2004 09:52:24 +0530
>Subject: Access Control for CVS
>
>
>Can we add Access Control Support into CVS ? Which would be the best
>plugin tool to add Access Control Support into CVS?.
>
>Regards,
>George Abraham
>
>
>
>___
>Info-cvs mailing list
>[EMAIL PROTECTED]
>http://mail.gnu.org/mailman/listinfo/info-cvs




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

New, Improved cvs_acls contrib for Access Control

[Peter Connolly]

The original 'cvs_acls' script in 'contrib' wasn't doing what I 
needed and the directory permissions approach:

http://www.cvshome.org/docs/manual/cvs-1.11.13/cvs_2.html#SEC13 

involves too much administration as well as not handling individual 
file restrictions.  

I rewrote the 'cvs_acls' script to do what I needed and called it 
'cvs_acls2'. Please see attached. 

I'd like to submit it to 'contrib' but do not know what the proper 
procedure is.  Could someone explain the process?



Here's a list of the problems I encountered when I tried to use the
original ('cvs_acls' from v1.11.13):

 0) Multiple entries on an 'avail' line will be matched 
individually, instead of requiring that all @ARGV entries match 
all 'avail' entries.
  (IMO, this basically made the original script unuseable for us 
  since any arbitrary combination of committed files could avoid 
  matching the 'avail's entries.)
 1) Correctly handle specific filename restrictions
 2) Correctly handle multiple, specific filename restrictions
 3) Prohibit mix of dirs and files on a single 'avail' line
 4) Correctly handle a mixture of branch restrictions within one 
work directory
 5) Do some sanity checking on the 'avail' file
 6) Accurately report restricted entries and their matching patterns
 7) $CVSROOT existence is checked too late
 8) Expanded overly complex PERL REGEXPs for readability and 
maintainability
 9) Correctly handle the CVSROOT=:local:/... option 
(useful for testing)
10) Skip the rest of processing if a mismatch on portion of the 
'avail' line
11) Get rid of opaque "karma" messages in favor of user-friendly 
messages that explain what the permission restrictions were
12) Add optional 'restrict_msg' file for additional restriction 
messages.
13) Take a "-u" parameter for $USER from commit_prep so that the 
script can do restrictions based on the client-side userId 
rather than the server-side userId (usually 'cvs').
14) Added a lot more debug trace 
15) Tested these restrictions with concurrent use of pserver and SSH
access to model our transition from pserver to ext access.
16) Added logging of restricted commit attempts.
Restricted commits can be sent to a default file:
$CVSROOT/CVSROOT/restrict_log or to one passed to the script
via the -f command parameter.
17) Added commit-error message include for site-specific contact
information. Default file is: $CVSROOT/CVSROOT/restrict_msg

Things still left to do: 

 1) Need to deal with pserver/SSH migration that may have conflicting 
umasks?
 2) Refactor checkDirectoryMatch and checkFileMatch together.
(Can pass in match expression?)
 3) Use some CPAN module to handle command parameters.
 4) use some CPAN module to clone data structures.

 Version information

I'm not offering this as a fix to the original 'cvs_acls' script since 
it differs substantially in goals and methods from its original and 
there are probably a significant number of people out there that still 
require the original version's functionality.

Please note that there has been very limited cross-platform testing of 
this script!!! (We did not have the time or resources to do exhaustive
cross-platform testing.)

It was developed and tested under Red Hat Linux 9.0 using PERL 5.8.0.
Additionally, it was tested under Red Hat Linux 7.3 using PERL 5.6.1.
It is now running on our main development repositories under Red Hat
Linux 7.3 using PERL 5.6.1.

pc

Peter Connolly, CNET Networks, Inc.
[EMAIL PROTECTED]



cvs_acls2
Description: Binary data
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Pserver command

[Peter Connolly]

Make sure their userId|password(encrypted)|cvsUserId is in the $CVSROOT/CVSROOT/passwd 
file on the pserver machine. Assuming that they have set up their CVSROOT env 
variable, then they 'cvs login' and they should then be able to proceed.

> -Original Message-
> From: RAJAGOPAL, AARTI (SBCSI) [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 04, 2004 10:03 AM
> To: Peter Connolly; '[EMAIL PROTECTED]'
> Subject: RE: Pserver command
> 
> 
> I already have it set up and working through inetd. What I'm 
> trying to get
> to work is if a client wants to access the CVS repository 
> remotely from
> another UNIX development box on which they are set up, how 
> will they get
> authenticated through pserver to the CVS repository from 
> their box, so that
> they can execute CVS commands from their dev system? They 
> will have CVS
> installed on their dev box as well. Thx.
> 
> 
> 
> -Original Message-
> From: Peter Connolly [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, February 04, 2004 11:53 AM
> To: RAJAGOPAL, AARTI (SBCSI); '[EMAIL PROTECTED]'
> Subject: RE: Pserver command
> 
> 
> It isn't meant for command line execution. Try the inetd 
> setup described in
> the Cederqvist manual:
> 
http://www.cvshome.org/docs/manual/cvs-1.11.10/cvs_2.html#SEC30

pc

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of RAJAGOPAL, AARTI (SBCSI)
> Sent: Wednesday, February 04, 2004 9:34 AM
> To: [EMAIL PROTECTED]
> Subject: Pserver command
> 
> 
> Does anyone know the correct syntax for using pserver command 
> directly from
> a UNIX shell prompt. I tried the following, they don't work
> 
>  :pserver:[EMAIL PROTECTED]:repository path
>  cvs pserver:[EMAIL PROTECTED]:repository path
> 
> Thanks...
> 
> 
> 
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Pserver command

[Peter Connolly]

It isn't meant for command line execution. Try the inetd setup described in the 
Cederqvist manual:

http://www.cvshome.org/docs/manual/cvs-1.11.10/cvs_2.html#SEC30

pc

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of RAJAGOPAL, AARTI (SBCSI)
> Sent: Wednesday, February 04, 2004 9:34 AM
> To: [EMAIL PROTECTED]
> Subject: Pserver command
> 
> 
> Does anyone know the correct syntax for using pserver command 
> directly from
> a UNIX shell prompt. I tried the following, they don't work
> 
>  :pserver:[EMAIL PROTECTED]:repository path
>  cvs pserver:[EMAIL PROTECTED]:repository path
> 
> Thanks...
> 
> 
> 
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: CVS pserver login problem

[Peter Connolly]

Check this out:
http://www.cvshome.org/docs/manual/cvs-1.11.10/cvs_21.html#SEC184


>-- Original Message --
>Date: Fri, 30 Jan 2004 16:05:03 -0500
>From: "Adam Vainder" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: CVS pserver login problem
>
>
>Hi,
>
>I hope this is the right place to send this. If not, please let me know

>where to send/post it.
>
>I've been trying to figure this out on my own for about a month, and just
>
>cant take it anymore. Hopefully one of you has seen this before and knows
>
>the answer.
>
>I set up a pserver on a Red Hat 9 machine with CVS installed. From that

>machine, i have no problem using the pserver info to access the cvs server.
>
>But from a remote machine, I only get an "end of file" message if i try
to
>
>log in. It happens whether password is correct or not. Any ideas what might
>
>be causing this?
>
>Thanks,
>Adam
>
>The following is info about related files and the error message, let me
know
>
>if you need more (and please be as specific as possible, especially  with
>
>typical locations of files) :
>
>from /etc/services :
>cvspserver  2401/tcp# CVS client/server
>operations
>cvspserver  2401/udp# CVS client/server
>operations
>
>from /etc/xinetd.conf :
>defaults
>{
>instances   = 60
>log_type= SYSLOG authpriv
>log_on_success  = HOST PID
>log_on_failure  = HOST
>cps = 25 30
>}
>includedir /etc/xinetd.d
>
>from /etc/xinetd.d/cvspserver :
>service cvspserver
>{
>socket_type = stream
>protocol= tcp
>wait= no
>user= root
>passenv =
>server  = /usr/bin/cvs
>server_args = --allow-root=/var/cvs/cvsstuff pserver
>}
>
>Error message from my remote machine (happens whether password is correct
>or
>incorrect):
>[login and machine name taken out]
>C:\>cvs -d :pserver:@:/var/cvs/cvsstuff login
>Logging in to :pserver:@:2401/var/cvs/cvsstuff
>CVS password:
>cvs [login aborted]: end of file from server (consult above messages if
>any)
>cvs repo is in /var/cvs/cvsstuff
>password file is in /var/cvs/cvsstuff/CVSROOT
>
>
>
>
>___
>Info-cvs mailing list
>[EMAIL PROTECTED]
>http://mail.gnu.org/mailman/listinfo/info-cvs




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: (no subject)

[Peter Connolly]

Then use RCS, not CVS.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jhon William Parra
Sent: Wednesday, January 28, 2004 8:55 AM
To: [EMAIL PROTECTED]
Subject: (no subject)


Hi,
i have problems:

CVS client win nt.
CVS server win nt.

I am locking a file and  show the next message :

" 
cvs [admin aborted]: 'admin -l' is a depreciated option. Use 'edit -c' instead."

I want to LOCK THE FILES.

thank you.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

http://www.cvshome.org/ has bad links today...

[Peter Connolly]

Title: Message



Not only 
is the site horribly slow, links to "CVS", "CVS Communications", and "CVS 
Downloads" do not work.
 
Who/how 
do we notify about the problem?
 
Peter 
Connolly, CNET Networks, Inc.
(415) 
344-2840
[EMAIL PROTECTED]
 
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Loophole in cvs_acls script allows restricted files to be com mitted

[Peter Connolly]

> 2. Change the way you write your acls. Your behavior will be more in
> line with what you expect if you write your unavail 
> directives based on
> directories rather than files. So to achieve what you want:
> unavail CVSROOT
> avail|cvsadmin|CVSROOT/avail
> avail|wimpy|CVSROOT/loginfo
> << 
> I'd recommend option 2 here, or better yet, just using filesystem
> permissions if you can.
> 
> Hope this helps,
> 
> Geoff
>

Thanks Geoff. Indeed a rejiggering of my avail file solves my problem.

We'll probably use the filesystem permissions approach later, after we've refactored 
some of our restricted classes into separate directories... 

Btw, as you noted, I confirmed that the use of the null commit message command option 
-m"" does seem to trigger the directory-wide commits instead of the requested 
file-specific commit.  Vey interesting.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Loophole in cvs_acls script allows restricted files to be committed

[Peter Connolly]

There appears to be a loophole in the cvs_acls script that allows 
someone to bypass an 'unavail' on a specific file and commit changes to 
that file.

It seems that all one needs to do is update another file in that same
directory. Then a commit of that unrestricted file will include the
restricted file, which commits successfully.

The avail file would look something like this:

unavail||CVSROOT/avail
avail|cvsadmin|CVSROOT/avail

So that only 'cvsadmin' should be able to update the 'avail' file.

But if a non-cvsadmin user updates **any other file** in the CVSROOT
directory (e.g., loginfo) and commits that file, the commit includes the
'avail' file and successfully commits it.

Here is some sample output when done under :ext: (ssh):

   [EMAIL PROTECTED] ssh]$ vi CVSROOT/avail
   [EMAIL PROTECTED] ssh]$ cvs ci -m"" CVSROOT/avail
   cvs commit: Examining CVSROOT
   [EMAIL PROTECTED]'s password:
    Access denied: Insufficient permission for this dir/file
(wimp|CVSROOT|)
   cvs commit: Pre-commit check failed
   cvs [commit aborted]: correct above errors first!
   [EMAIL PROTECTED] ssh]$ vi CVSROOT/loginfo
   [EMAIL PROTECTED] ssh]$ cvs ci -m"" CVSROOT/loginfo
   cvs commit: Examining CVSROOT
   [EMAIL PROTECTED]'s password:
   Checking in CVSROOT/avail;
   /usr/cvsroot/CVSROOT/avail,v  <--  avail
   new revision: 1.7; previous revision: 1.6
   done
   Checking in CVSROOT/loginfo;
   /usr/cvsroot/CVSROOT/loginfo,v  <--  loginfo
   new revision: 1.139; previous revision: 1.138
   done
   cvs commit: Rebuilding administrative file database


This exposure occurs under both pserver and ext access modes. Client and
server were using CVS 1.11.10 under Redhat Linux 9.0.

Any help would be appreciated...
pc



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: How to give certain users check in, everyone one else checkou t for certain modules?

[Peter Connolly]

> > What is the best method people have found to let only certain users
> > check in and everyone else check out?
> 
> An example may be found in the contrib directory in the check_acls.in
> script.
> 
> http://ccvs.cvshome.org/source/browse/ccvs/contrib/cvs_acls.in

The cvs_acls script says:

# 1. Put one line, as the *only* non-comment line, in your commitinfo file:

If we're already using commitinfo, commit_prep and log_accum to log and send email 
notifications, can this script co-exist? 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: what to use to see merged files?

[Peter Connolly]

CVS does not implicitly maintain this information. That is why it's important to 
follow an *explicit* tagging discipline when merging.  See:

http://mail.gnu.org/archive/html/info-cvs/2002-12/msg00037.html

and 

http://mail.python.org/pipermail/spambayes-dev/2003-November/001597.html

for more.  

For example, you might tag all your merge sources as MERGESOURCE_,
or MERGESOURCE__ or whatever.  
Say...MERGESOURCE_PROJECT_ABC_BRANCH_20031217.
Tag your targets with something similar so that it's easy to match source and target.
Say...MERGETARGET_PROJECT_ABC_BRANCH_20031217.

In any case, it's important for your organization to have a set of branch and merge 
tagging standards so that this information can be tracked.  CVS won't do it for you.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Phil Labonte
> Sent: Wednesday, December 17, 2003 12:15 PM
> To: [EMAIL PROTECTED]
> Subject: what to use to see merged files?
> 
> 
> I want to know if there is a windows app that will let me see 
> visually 
> which files have been merged together...
> 
> I have tried Tortoise, smartcvs, lincvs and wincvs all of them have a 
> revision graph but they do not show in the graph which to files have 
> been merged.
> 
> For instance... I have a file called filt.txt and I make 2 
> revisions so 
> main is revision 1.3, from the 1.3 revision I branch of to 
> 1.3.1.1. then 
> I make two revisions off the brached version and say I am now 
> at 1.3.1.3.
> 
> Now that I am done and I merge the 1.3.1.3 version back into the main 
> brach 1.3 to end up with 1.4. If  I do the revision graph I 
> do not see a 
> link from 1.3 to 1.3.1.1. Is there a way to see it?
> 
> Thanks
> 
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Stopping a modified file from being checked in

[Peter Connolly]

>Peter Connolly <[EMAIL PROTECTED]> writes:

>>>I would like to make some changes to a file in my working copy, but
>>>definitely not check them in.
>> 
>>If you don't want to accidently effect HEAD, why don't you do your
>>changes on a branch?

>I want to affect HEAD, just not for this one file.  Making a branch
>would be a bit silly if I will never commit anything on that branch.

Not at all.  Isolating your work from that of your peers is what
branches are all about.

>--- End of forwarded message from [EMAIL PROTECTED]

Agreed. That's exactly what branches are for. Word to the wise...
Anytime you find yourself standing on your head to do something like
this, you're probably not using the tool the way that it was intended to
be used.  ;-) 'Nuff said.





___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Stopping a modified file from being checked in

[Peter Connolly]

> What I'd like is some error when I try to commit this one file.

Well...probably the simplest (although it doesn't generate an error message) is to 
delete the file's entry from the CVS/Entries file in that file's current directory.  
CVS won't identify it as an updated file; it will think it's a new file requiring a 
'cvs add...' and will leave it alone when you do commits.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Stopping a modified file from being checked in

[Peter Connolly]

> I would like to make some changes to a file in my working copy, but
> definitely not check them in.  

If you don't want to accidently effect HEAD, why don't you do your changes on a branch?


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: users file and notification

[Peter Connolly]

> Can anybody tell me if there is a way to tell cvs to let the 
> file users map
> cvs users to email adresses? Or if there's another way to 
> configure cvs
> to send mail to the cvs users instead of system users?

If you want users notified when commits are made to specific CVS modules, this is done 
by using the following 'contrib' scripts and control files:

log_accum.pl: is a PERL script that is run after commit processing 

loginfo: This is the control file used by log_accum. Each line contains a pattern of 
the module you are tracking; the email addresses that require notification; and the 
current $USER.

commit_prep: is a PERL script that will facilitates getting all the commit log 
messages (and diffs if requested) into a single log_accum email.

commitinfo: has a line for each module to track and the current $USER.

Once you've installed CVS, look in the .../cvs/share/cvs/contrib directory for the 
scripts.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Format for 1.11.10's contrib's loginfo, used by log_accum com mit

[Peter Connolly]

> Perl isn't that hard to read.

Larry, Larry, Larry,...  Trust me. If you've never encountered constructs like @_, my, 
local($wd, @files); scalars, arrays... (and btw, 'local' is not local, 'my' is 
local...how cute), reading it is doable but tediously slow.  I'm reminded of a 
friend's admonition in college.  He said: "Physics is easy, once you know it."

> I believe you want something like:
> 
> commitinfo:
>   DEFAULT commit_prep -u ${USER}
> 
> loginfo:
>   DEFAULT log_accum -u ${USER} %s

I've tried that and when I commit, I get the following messages:

   Processing log script arguments...
   Mailing the commit message to (from [EMAIL PROTECTED])
   No recipient addresses found in header

which I guess means that $mail_to and its progenitor $addr_list in the 
 subroutine are not being set properlybut no hints as to how to 
format those email addresses into loginfo...

General question: Is it really expected that EVERYONE that wants to set up and use 
these contrib scripts have to read them, understand them and retro-engineer the inputs?


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Format for 1.11.10's contrib's loginfo, used by log_accum commit script?

[Peter Connolly]

I asked this question before and got pointed to the Cederqvist manual, which does 
*not* help at all.  Please don't tell me to RTFM, the answer is not there.

We are on CVS 1.11.5, moving to 1.11.10. We are using a really old version (1.11.1p) 
of the log_accum.pl and loginfo files.  I would like to upgrade to the commit_prep and 
log_accum scripts that are included in the $CVS/share/cvs/contrib directories of 
1.11.10.  However, I can't find any documentation or examples of what this variant of 
the 'loginfo' file should look like.  When I run with the old formatted version of the 
loginfo file, I get a "Too many arguments" error coming out of .

Now, I could spend a week learning PERL and figure out the format that is required...

BUT, I'd really rather not.

Does anyone out there know the file format required for the 'loginfo' file that is 
included in the 'contrib' directory of 1.11.10 CVS???  Presumably someone out there 
wrote this thing and knows what inputs it takes???

Thanks,
pc

Peter Connolly, CNET Networks, Inc.
(415) 344-2840
[EMAIL PROTECTED]


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

FW: best windows client?

[Peter Connolly]

-Original Message-
From: Peter Connolly 
Sent: Tuesday, December 09, 2003 11:24 AM
To: 'Rod Macpherson'; Peter Connolly
Subject: RE: best windows client?


> Tried Tortoise but did not like the idea that the whole file 
> system would be exposed to CVS for all the users of CVS at 
> our company. Wanted a more project-oriented approach. 

There are two strategies that we use to filter the repository for our users:

1) Define modules in the 'modules' file so that they can easily check out portions of 
the tree that pertain to them

2) Use LockDir and directory permissions to limit who can check in changes to certain, 
protected portions of the tree.

There is also the optional 'readers' and 'writers' admin files that can define who can 
read or write to the repository.

If that isn't enough and more separation is required, then consider splitting up the 
repository into separate repositories.


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: best windows client?

[Peter Connolly]

I tried to get used to WinCVS.  Try TortoiseCVS instead:

http://www.tortoisecvs.org/

pc

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Phil Labonte
> Sent: Tuesday, December 09, 2003 6:57 AM
> To: [EMAIL PROTECTED]
> Subject: best windows client?
> 
> 
> I have CVS setup on a Linux server. I have several Windows 
> clients that 
> are using WinCVS... 
> 
> I have done some searching and nothing else really comes up 
> for Windows
> 
> Is that the best client to use?
> 
> Specifically what I am looking for would be a client that would let a 
> user pick individual files from the repository and then be 
> able to check 
> out those files...?
> 
> Is there anything like that available for CVS?
> 
> 
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: best windows client?

[Peter Connolly]

> Specifically what I am looking for would be a client that would let a 
> user pick individual files from the repository and then be 
> able to check out those files...?

To view all the hideous detail of a repository without checking it all out, try either:

CVSWeb: http://people.freebsd.org/~fenner/cvsweb/

or 

ViewCVS: http://viewcvs.sourceforge.net/




___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

RE: Checkout files from multiple porjects at that same time

[Peter Connolly]

Take a look at the use of modules to do this:

http://www.cvshome.org/docs/manual/cvs-1.11.10/cvs_18.html#SEC157

pc

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On 
> Behalf Of Phil Labonte
> Sent: Monday, December 08, 2003 10:25 AM
> To: [EMAIL PROTECTED]
> Subject: Checkout files from multiple porjects at that same time
> 
> 
> Is this possible?
> 
> Or can I create a new project that contains files from a 
> combination of 
> other projects?
> 
> Thanks.
> 
> 
> 
> ___
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Format for the 'loginfo' file for log_accum.pl & commit_prep?

[Peter Connolly]

I can't find any reference to the loginfo file format or to a sample of
that file in the contrib directories.  I need to know because when I use
our company's old format (circa 1.11.1p) for the loginfo file, the new
log_accum.pl script complains that there are too many input parameters: 

[EMAIL PROTECTED] dir1]$ cvs ci -m"Hi" file1
Checking in file1;
/usr/cvsroot/dir1/file1,v  <--  file1
new revision: 1.6; previous revision: 1.5
done
Too many arguments!
Processing log script arguments...
[wimpey...

We're currently using 1.11.5 and I am testing the new version: 1.11.10.
We haven't upgraded our log_accum and commit_prep scripts since about
1.11.1p.

Thanks,
pc



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

How to Connect WinCVS 1.3b10 to New CVS 1.11.5 pserver?

[Peter Connolly]

We're testing out the new version of CVS 1.11.5 on a new pserver 
(Solaris 5.8) using port 2402.  All of our cross-platform access 
(i.e., Solaris, Linux & Win2K) to this new port and version 
check out okay **except** for WinCVS.  We're using WinCVS 1.3b10.  
There are two problems:

1) Switching to the new client in the Admin, Preferences, WinCVS 
   dialog box ("Alternate cvs executable (NOTE...")
   
   Doing any command (e.g., status on a CVS file) yields the following:
   
   C:\cygwin\bin\cvs.exe: invalid option -- c
   Usage: cvs.exe [cvs-options] command [command-options-and-arguments]
 where cvs-options are -q, -n, etc.
   (specify --help-options for a list of options)
 where command is add, admin, etc.
   (specify --help-commands for a list of commands
or --help-synonyms for a list of command synonyms)
 where command-options-and-arguments depend on the specific command
   (specify -H followed by a command name for command-specific help)
 Specify --help to receive this message
   
   The Concurrent Versions System (CVS) is a tool for version control.
   For CVS updates and additional information, see
   the CVS home page at http://www.cvshome.org/ or
   Pascal Molli's CVS site at http://www.loria.fr/~molli/cvs-index.html
   
   And WinCVS hangs, even after pressing the "Stop" button.  
   It has to be killed from the Win2K Task Manager.
   
2) Using the embedded client, but pointing WinCVS at the new CVS port (2402)
   
   This time there is no override for the client, but we add the new 
   port number '2402' to the Admin, Preferences, WinCVS dialog box
   ("General" tab, adding 2402 to the front of the 'path' entry so that
   the resulting CVSROOT line reads something like:
   
   [EMAIL PROTECTED]:2402/cvs/path/here
   
   An update to any directory shows that the old server is being accessed:
   
   cvs update -P -d (in directory C:\cygwin\home\Administrator\cvs\java\)
   cvs-1.10.7 server: Updating .
   cvs-1.10.7 server: Updating core
   cvs-1.10.7 server: Updating view
   
   * CVS exited normally with code 0 *

It appears that there are two obstacles to upgrading WinCVS to the
new version of CVS.  

1) Some modifications to CVS are needed in order to be able to
   talk successfully to WinCVS.  Any idea how/where to make these
   mods???

2) WinCVS doesn't appear to handle alternate pserver ports.
   I know there is a sub-dialog box under Admin, Preferences,
   General, Settings, but that generates a CVSROOT entry that
   looks totally bogus (i.e., [EMAIL PROTECTED]:2402:/cvs/path)
   and doesn't work either.  What's the trick to getting WinCVS
   to use alternate port numbers?

Thanks,
pc


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs