(no subject)

[Hussein Badakhchani]

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

CVS - setup reserved checkout

[Andrew]

Hello all,

Has anyone setup reserved checkout in CVS (ver 1.11.1p1) in Unix
(Solaris)? Or is there any documentation on this other than the manual
that comes with the source code?

If there is any info., please email to [EMAIL PROTECTED] 

Many thanks in advance

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

Re: CVS - setup reserved checkout

[Matthias Kranz]

On Wed, Oct 10, 2001 at 01:18:55AM -0700, Andrew wrote:
> Has anyone setup reserved checkout in CVS (ver 1.11.1p1) in Unix
> (Solaris)? Or is there any documentation on this other than the manual
> that comes with the source code?

Try http://cvsbook.red-bean.com/ for a very good book about CVS. Perhaps
it clarifies things for you. If not, try to give a more specific
description of the particular problem you have and we try to help you.

Cheers,
Matthias
-- 
Matthias Kranz [EMAIL PROTECTED]
 http://www.buug.de/~mkr
ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol

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

umask

[James Stevenson]

Hi

i am running a pserver
and i was wondering if there is anyway to get the cvs server
to use a umask for when it is creating files.
like
umask 007

thanks
James

--

 11:30am  up 35 days, 19:46, 12 users,  load average: 0.00, 0.00, 0.00



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

[kfogel@collab.net: Re: rename in cvs]

[Miklos Quartus]

Hi info-cvs,

Have you tried to rename a file and to retain the revision history? Karl
suggested to cp the ,v file from the Repository. Which one?

Any help would be appreciated. Thank you,
Miklos
- Forwarded message from [EMAIL PROTECTED] -

Envelope-to: qmi@localhost
Subject: Re: rename in cvs
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: rename in cvs
Thread-Index: AcFQ86RA2o3xmLzjEdWpXABQi2kYTQ==
From: <[EMAIL PROTECTED]>
To: "Miklos Quartus" <[EMAIL PROTECTED]>
Reply-To: <[EMAIL PROTECTED]>

You can cp the ,v file in the repository... (mail [EMAIL PROTECTED] for
more details).

Good luck,
-Karl

Miklos Quartus <[EMAIL PROTECTED]> writes:
> I feel sorry that your laptop was stolen. I hope you can recover both
> financially and mentally...:)
> 
> I have question about renaming in CVS. I understand what is written in
> the book, but if I do rm and cp oldname newname and cvs add newname, 
> than the modifications will be lost. Is there any way to preserve the
> log and revision history for a file if rename it?
> 
> I checked the 1.21 version of the manual.
> 
> Looking forward to hearing of you,
> -- 
> Miklos Quartus
> Nokia Research Center
> Mobile Networks Laboratory
> Phone: +358 50 4873093

- End forwarded message -

-- 
Miklos Quartus
Nokia Research Center
Mobile Networks Laboratory
Phone: +358 50 4873093

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

making binaries versioned

[Nils9]

Hi,
i was wondering if it could be possible by somehow running the
binary thru wrapper and encoding it on the way to the repository.
Something like uuencode but more suitable. Not that I'd like to
store octal dumps in CVS of the actual binaries, but similar...

And, speaking of CVS2.0, are there any tools now out to convert
CVS repository to SubVersioN repository? Anyone done that?

Nils Jakobson
SWHTechnology


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

Re: CVS - setup reserved checkout

[yap_noel]

The most you could hope for in CVS is to install a patch that allows
advisory locks -- reserved locks are counter to the purpose of CVS.  You
can find a version of the patch (I think against cvs-1.11.1) at SourceForge
under project RCVS.

Once the patch is installed, tell the users that they must have "cvs edit
-c" and "cvs ci -c" in their ~/.cvsrc files.  Be sure to turn on
notification as well.  The process they should follow is:
1. When intending to modify a file for checkin, "cvs edit" the file.
2. If the files are being edited by others, contact the other parties to
minimize the chances of conflicts.
3. If the chances of conflicts is minimal or the others cannot be
contacted, "cvs edit -f" the files.
4. If one receives notification about an as-yet-unknown edit, contact the
editor to help minimize the chances of conflicts.

Noel

Hello all,

Has anyone setup reserved checkout in CVS (ver 1.11.1p1) in Unix
(Solaris)? Or is there any documentation on this other than the manual
that comes with the source code?

If there is any info., please email to [EMAIL PROTECTED]

Many thanks in advance

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





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.


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

Re: making binaries versioned

[Ilya Martynov]

N> And, speaking of CVS2.0, are there any tools now out to convert
N> CVS repository to SubVersioN repository? Anyone done that?

AFAIK developers of SubVersion are going to implement such tools. But
it is not ready yet.

Anyway IMHO it is too early to migrate on SubVersion. IMHO it is not
ready for production environment yet.

-- 
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
| Ilya Martynov (http://martynov.org/)|
| GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80  E4AE BE1A 53EB 323B DEE6 |
| AGAVA Software Company (http://www.agava.com/)  |
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

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

Re: [kfogel@collab.net: Re: rename in cvs]

[Dave Storrs]

Hi Miklos,

What he means is this:  let's say that you want to rename file
"foo.c" in your working copy to "bar.c", and you want the name change to
sync up in the repository, without losing any of "foo.c"'s version
history.  You would then do the following:

- Make sure no one else is accessing the repository right now.
- 'cd' into the repository, find the file named "foo.c,v"
- 'mv foo.c,v bar.c,v'

I've done this and it works, as long as no one is doing a checkout
or update while you are renaming (if they are, results are undefined
(=="openly hostile", as K&R once remarked)).

The only downside is that you will not be able to reconstruct the
project as it did before you did this rename...because CVS will not be
able to serve up the file "foo.c" file for you.

Hope this helps.

 Dave

On Wed, 10 Oct 2001, Miklos Quartus wrote:

> Hi info-cvs,
> 
> Have you tried to rename a file and to retain the revision history? Karl
> suggested to cp the ,v file from the Repository. Which one?
> 
> Any help would be appreciated. Thank you,
> Miklos
> - Forwarded message from [EMAIL PROTECTED] -
> 
> Envelope-to: qmi@localhost
> Subject: Re: rename in cvs
> X-MS-Has-Attach: 
> X-MS-TNEF-Correlator: 
> Thread-Topic: rename in cvs
> Thread-Index: AcFQ86RA2o3xmLzjEdWpXABQi2kYTQ==
> From: <[EMAIL PROTECTED]>
> To: "Miklos Quartus" <[EMAIL PROTECTED]>
> Reply-To: <[EMAIL PROTECTED]>
> 
> You can cp the ,v file in the repository... (mail [EMAIL PROTECTED] for
> more details).
> 
> Good luck,
> -Karl
> 
> Miklos Quartus <[EMAIL PROTECTED]> writes:
> > I feel sorry that your laptop was stolen. I hope you can recover both
> > financially and mentally...:)
> > 
> > I have question about renaming in CVS. I understand what is written in
> > the book, but if I do rm and cp oldname newname and cvs add newname, 
> > than the modifications will be lost. Is there any way to preserve the
> > log and revision history for a file if rename it?
> > 
> > I checked the 1.21 version of the manual.
> > 
> > Looking forward to hearing of you,
> > -- 
> > Miklos Quartus
> > Nokia Research Center
> > Mobile Networks Laboratory
> > Phone: +358 50 4873093
> 
> - End forwarded message -
> 
> -- 
> Miklos Quartus
> Nokia Research Center
> Mobile Networks Laboratory
> Phone: +358 50 4873093
> 
> ___
> 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

file,t

[Wim Dausy]

What are and of what purpose are *,t-files?
In my case they seem to be appeared when new files where created.
I'm suffering from unresolved conflicts which I can't resolve,
update won't work (cvs update: conflict: *file* created independently by
second party)
andso cvs doesn't give me any conflicts (in the files I'm refering to)
to resolve.
It looks like I'm forced to release (delete) these files and check them
out again.
Any other suggestions?

#maybe useful:
File: *file*   Status: Unresolved Conflict
 
   Working revision:New file!
   Repository revision: 1.1.1.1 /home/***/*file*

If you like to know what I did, or what happened whit these files, same
here.
I can't remember because I've been out for a while.
Maybe someone can tell me what I did wrong or what could have happened.

Thanx.

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

Web interfaces that supports the CVSROOT/modules

[Rich Wittmer]

I have a developer that is interested in a web interfaces that supports the
CVSROOT/modules file to display the directory representation rather than the
actual set of directories. Does anyone know of a interface of this nature?

Rich


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

RE: deprecated caommand in 1.11.1.1

[Stanton, Curt (NCI/IMS)]

Well, I am planning on getting comfortable with the concurrent part
of it, but why not get comfortable with it using CVS seeing as there was
some sort of locking feature on it already.  I was simply asking if there
was something like that on the newest version or if I had to start out with
a previous version.  


>  
> [ On Tuesday, October 9, 2001 at 15:31:46 (-0400), Stanton, Curt (NCI/IMS)
> wrote: ]
> > Subject: RE: deprecated caommand in 1.11.1.1
> >
> > First of all relax.  Second of all, I like a lot of things about CVS.
> We
> > would like to try to avoid problems right away by trying this way, which
> was
> > already there in previous versions, until we are comfortable without it.
> I
> > was merely asking if there was a way to do it in the latest release, not
> > asking anyone to spend time on something that the software isn't working
> > towards
> 
> It really doesn't matter how much you like some features of CVS if you
> don't like the "concurrent" part -- CVS was designed to force its users
> into the concurrent (parallel) development model.  If you don't want to
> do that then you do not want to use CVS.
> 
> Conversely If you really really really want to use CVS then you really
> really really must get comfortable with the concurrent development
> model.
> 
> You might also want to look at other tools which allow concurrent
> development but with a more controlled two-phase commit mechanism,
> eg. Aegis.
> 
> -- 
>   Greg A. Woods
> 
> +1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
> Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>

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

moving a tag

[Arcin Bozkurt]

>From a set of files in the repository which are tagged as Dev13, I want the tag Dev13 
>to point to the latest versions of these files. (Moving the tag in CVS terminology?) 
>But i don't want to specify each file. I want a command to automatically find all the 
>files associated with a tag and move this tag for those files to the latest version 
>of those files.

Will the following command update the tag Dev13 to point to the newest versions in the 
repository?? (It should work only for the files that were tagged with this tagname 
before)


cvs rtag -F Dev13
(no module name is specified, cause i am in that projects working copy)
Or is the module name required?
 
Arcin



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

How to handle drive letters on 'Windows

[Chris Nelson]

Sorry if this is a FAQ, I've skimmed the group and the FAQ and not found
an answer.

I'm running cvs.exe on 'Windows 98.  My repository is in C:\Data
Files\Repository and I want to import files from another drive.  I've
tried:

 cvs -d "C:\Data Files\Repository" import ...

but keep getting a parsing error.  The : confuses cvs.  Is there a
command line workaround?

Chris
-- 
Never doubt that a small group of thoughtful, concerned citizens 
can change the world.  Indeed, it's the only thing that ever has. 
 --Margaret Mead
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

CVS client port and proxys

[david delbecq]

Could somebody help me.

Am trying to use the cvs tool (client part) from behind a proxy (running on a 
RedHat). The configuration of the proxy fobids me to connect (I always receive 
a connection timed out) to public cvs servers.

Does somebody know the lines to add to the proxy configuration file to allow 
the opening of this port.

I understand this is not directly a question related to cvs but you perhaps 
know the anwer (and i don't know what the cvs default port is!).

Thank you.

David Delbecq (Tchize)

David Delbecq
[EMAIL PROTECTED]


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

Re: Info-cvs digest, Vol 1 #1069 - 16 msgs

[Martin Fuzzey]

Hi,

To keep the full histories and be able to reconstruct old versions of the
project do the following :

- Make sure no one else is accessing the
repository right now.
- 'cd' into the repository, find the file named
"foo.c,v"cp foo.c,v bar.c,v

Then from your cvs client :
1) do an update (you will now have both foo.c and bar.c)
2) Do a cvs remove foo.c , followed by a commit  (the old file foo.c
will thus no longer exist for new versions)
3) Remove all the tags from bar.c   (this prevents the new file
bar.c being checked out when you give an old tag)

Hope this helps

Martin Fuzzey

Message: 16
Date: Wed, 10 Oct 2001 06:00:55 -0700 (PDT)
From: Dave Storrs <[EMAIL PROTECTED]>
To: Miklos Quartus <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]

Hi Miklos,

What he
means is this:  let's say that you want to rename file
"foo.c" in your working copy to "bar.c", and you want
the name change to
sync up in the repository, without losing any of "foo.c"'s
version
history.  You would then do the following:

- Make sure no one else is accessing the repository right now.
- 'cd' into the repository, find the file named "foo.c,v"
- 'mv foo.c,v bar.c,v'

I've done
this and it works, as long as no one is doing a checkout
or update while you are renaming (if they are, results are 
undefined
(=="openly hostile", as K&R once remarked)).

The only
downside is that you will not be able to reconstruct the
project as it did before you did this rename...because CVS will not
be
able to serve up the file "foo.c" file for you.

Hope this
helps.

 Dave

On Wed, 10 Oct 2001, Miklos Quartus wrote:

> Hi info-cvs,
> 
> Have you tried to rename a file and to retain the revision history?
Karl
> suggested to cp the ,v file from the Repository. Which one?
> 
> Any help would be appreciated. Thank you,
> Miklos
> - Forwarded message from [EMAIL PROTECTED] -
> 
> Envelope-to: qmi@localhost
> Subject: Re: rename in cvs
> X-MS-Has-Attach: 
> X-MS-TNEF-Correlator: 
> Thread-Topic: rename in cvs
> Thread-Index: AcFQ86RA2o3xmLzjEdWpXABQi2kYTQ==
> From: <[EMAIL PROTECTED]>
> To: "Miklos Quartus" 
<[EMAIL PROTECTED]>
> Reply-To: <[EMAIL PROTECTED]>
> 
> You can cp the ,v file in the repository... (mail [EMAIL PROTECTED]
for
> more details).
> 
> Good luck,
> -Karl
> 
> Miklos Quartus <[EMAIL PROTECTED]> writes:
> > I feel sorry that your laptop was stolen. I hope you can
recover both
> > financially and mentally...:)
> > 
> > I have question about renaming in CVS. I understand what is
written in
> > the book, but if I do rm and cp oldname newname and cvs add
newname, 
> > than the modifications will be lost. Is there any way to
preserve the
> > log and revision history for a file if rename it?
> > 
> > I checked the 1.21 version of the manual.
> > 
> > Looking forward to hearing of you,
> > -- 
> > Miklos Quartus
> > Nokia Research Center
> > Mobile Networks Laboratory
> > Phone: +358 50 4873093
> 
> - End forwarded message -
> 
> -- 
> Miklos Quartus
> Nokia Research Center
> Mobile Networks Laboratory
> Phone: +358 50 4873093
> 
> ___
> 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


End of Info-cvs Digest


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

(no subject)

[Tim Moreton]

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

Module directory nameing....

[Bryon Lape]

I have a project that is divided into two modules.  One contains HTML
files and the other is java and jsp code.  They each live in different
areas (one under the JSP server, the other under the HTML server).
Let's say the project is named foo, so the directories in cvs are named
as such:

foo-jsp
foo-html

When a user does cvs checkout foo-jsp, I would like the local directory
that gets created to just be called foo and not foo-jsp.  The same would
be for foo-html; that is, just foo locally.  Is this possible?  If so,
how?

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

cvs exit status

[Andrea Montefusco]

I am writing some shell script that invoke
cvs commands: some command appear to return  
always "0".

For example

[andrew]$ cvs update no-such-file.fig  ; echo $?
cvs server: nothing known about no-such-file.fig
0 

My repository is remote (pserver) and my CVS
version is 1.10.8.

There is a method to retrieve the true exit code 
or I need to parse the output messages ?

Thanx.

   *am*

 
-
Andrea Montefusco Network Manager
Kyneste S.p.A.  Roma Via Mario Bianchini, 68 
Milano Via della Posta, 3
tel: +390687402612 mob: +393356992791 fax: +390687402300
-

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

cvsup question

[Nils9]

Hi,
slight offtopic, I've encountered strange entries in cvsup logfile:
.
Applying fixups for collection Products/cvs
 Fixup Products/Desktop/Comp/ScanSupport/ANALYSIS.CPP,v
 Fixup Products/Desktop/Comp/ScanSupport/ANALYSIS.H,v
 Fixup Products/Desktop/Comp/ScanSupport/BIC.LOG,v
.

what are these fixups?!

-Nils Jakobson
SWHTechnology


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

cvs edit -c command

[Stanton, Curt (NCI/IMS)]

Does anyone know where I can find some info on this command and arguments.
I can't seem to find it
Thanks

Curt Stanton

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

Re: Module directory nameing....

[Kaz Kylheku]

In article <[EMAIL PROTECTED]>, Bryon Lape wrote:
>When a user does cvs checkout foo-jsp, I would like the local directory
>that gets created to just be called foo and not foo-jsp.

One way is the module definition

foo-jsp -d foo foo-jsp

This defines a regular module called foo-jsp which checks out the
directory foo-jsp. The -d module option causes the checkout name
to be foo rather than foo-jsp.

> The same would
>be for foo-html; that is, just foo locally.

Probably a bad idea to have two that clash this way.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

rolling back

[r w]

Hey all,
time for a newbie question i believe.  I was curious if there was a way to 
roll back to a previous version utilizing cvs AND deleting the current 
version of a file.  Everytime I try to roll back and check in a previous 
versioned file .. the changes are merged.. am i missing a flag of some sort?
please cc me

Thanks,
R.



_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


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

Re: cvs edit -c command

[yap_noel]

The patch is available at SourceForge under project RCVS.

The gist of the patch is:
1.  "cvs edit -c" will abort the edit if another is editing the files.
2.  "cvs edit -f" will force the edit.
3.  "cvs ci -c" will abort the checkin if a valid edit does not exist on
the files.

Noel

Does anyone know where I can find some info on this command and arguments.
I can't seem to find it
Thanks

Curt Stanton

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





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.


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

Re: CVS - setup reserved checkout

[David Masterson]

> Andrew  writes:

> Has anyone setup reserved checkout in CVS (ver 1.11.1p1) in Unix
> (Solaris)? Or is there any documentation on this other than the
> manual that comes with the source code?

Given the CVS model of unreserved checkouts, why do you need reserved
checkouts?  Also, are you talking about reserved checkouts of a file
or an entire product?

-- 
David Mastersondmaster AT synopsys DOT com
Sr. R&D Engineer   Synopsys, Inc.
Software Engineering   Sunnyvale, CA
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: [kfogel@collab.net: Re: rename in cvs]

[Kaz Kylheku]

In article <[EMAIL PROTECTED]>, Dave Storrs wrote:
>Hi Miklos,
>
>   What he means is this:  let's say that you want to rename file
>"foo.c" in your working copy to "bar.c", and you want the name change to
>sync up in the repository, without losing any of "foo.c"'s version
>history.  You would then do the following:
>
>- Make sure no one else is accessing the repository right now.

The way you do that is by creating a lock directory.

>- 'cd' into the repository, find the file named "foo.c,v"
>- 'mv foo.c,v bar.c,v'

Before you do anything, "mkdir #cvs.lock". If that fails, wait and
try again.

Note that Karl Fogel already provided the advice of cp'ing the
file. This is more sensible because it produces a new object without
destructively manipulating the old. So foo.c,v is still there with
its version history intact; you merely have a duplicate.

The best way is to do this from the working copy. Copy your working
foo.c to bar.c.  Then do:

cvs add bar.c
rm foo.c
cvs rm

and commit. In other words, cvs remove the old, add the new.

>   I've done this and it works, as long as no one is doing a checkout
>or update while you are renaming (if they are, results are undefined
>(=="openly hostile", as K&R once remarked)).

You could have found out on how to place a lock with a tiny amount of RTFM.

>   The only downside is that you will not be able to reconstruct the
>project as it did before you did this rename...because CVS will not be
>able to serve up the file "foo.c" file for you.

And after that downside, you think there is still an upside?
Version control has gone out the window basically. Bye bye tagged,
reproducible builds.

There are other downsides, like people's working copies having dangling
references to a nonexistent version file. People may have local
modifications to the renamed file.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: rolling back

[Kaz Kylheku]

In article <[EMAIL PROTECTED]>, r w wrote:
>Hey all,
>time for a newbie question i believe.  I was curious if there was a way to 
>roll back to a previous version utilizing cvs AND deleting the current 
>version of a file.

I should abandon thinking about version control in terms of the primitive
tool you were using previously. The very concept of rolling back is wrong.
You cannot roll anything back in a version control system, because that
is equivalent to turning time back, and discarding information.

Rather, you can create a new version of a file in which some past
changes are reversed. This is done by merging on those changes
in reverse using two -j options. For example, if version 1.5
of a file was a bad one, you can try to remove it from your
working copy using

cvs update -j 1.5 -j 1.4 

Note the reversed order of the versions; you are merging the changes
between 1.5 and 1.4 which are just the changes between 1.4 and 1.5 done
in reverse.

The merge may introduce conflicts which you have to resolve before
you commit the new version.
was done 



  Everytime I try to roll back and check in a previous 
>versioned file .. the changes are merged.. am i missing a flag of some sort?
>please cc me
>
>Thanks,
>R.
>
>
>
>_
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>


-- 
Refracturing: the technique of taking broken code, and breaking it some more.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

cvs [login aborted]: connect to 216.254.34.156:2401 failed: Connection timed out

[Matt Burba]

I am a newbie to cvs and I am having problems logging in as a client
from my work machine (WinNT).  The server I am logging into is running
Linux and I have no trouble connecting from home (using WinCVS or
Forte For Java's built in client).  I am DEFINITELY behind a firewall
at work that I have no control over.  I can telnet to the ip address
(port 23?) and connect via ftp (port 21?).

I have thoroughly investigated this problem on the web and have not
seen anyone with a good solution.  One "troubleshooting" technique
I've seen to try is to telnet to the port using "telnet ipaddress
port" which for me is "telnet 216.254.34.156 2401".  When I do this, I
get a long wait period followed by a "Connection failed!" dialog from
the Telnet program that is automatically launched by WinNT from the
command prompt.  Do this mean I'm out of luck?

Posted below are the environment variables I set with a batch file and
the error message I'm getting.  Thanks in advance for any insight
y'all can provide!

Matt Burba

D:\>java.bat
D:\>path=%path%;D:\Burba\Java\cvs;c:\jdk1.3\bin;d:\Burba\Java
D:\>set home=c:\Burba\Java
D:\>set homedrive=d:
D:\>set homepath=\Burba\Java
D:\>set cvsroot=:pserver:[EMAIL PROTECTED]:/cvs/rep
D:\>set classpath=d:\Burba\Java;d:\Burba\Java\PictureViewer;d:\Burba\Java\Pap
D:\>cd d:\Burba\Java

D:\Burba\Java>cvs login
(Logging in to [EMAIL PROTECTED])
CVS password:
cvs [login aborted]: connect to 216.254.34.156:2401 failed: Connection
timed out

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

Re: [kfogel@collab.net: Re: rename in cvs]

[Paul Sander]

Or, you could copy the ,v file to the new location and move the original
to the Attic.  (Well, that's true if the rename is on the trunk.  If it's
on a branch only, don't move to the Attic.)  That at least leaves the
original version history in its original location.  The downside that, of
course, is that checking out with old tags produces the file in two places.
But that can be countered by removing the offensive tags from the new copy.
Care must be taken with branch tags, however:  You'll want some of them to
be made "dead" in the original location.

Generally speaking, renaming stuff in CVS is royal pain.  You always lose
something.  It's up to you to decide what you're willing to give up.

>--- Forwarded mail from [EMAIL PROTECTED]

>   What he means is this:  let's say that you want to rename file
>"foo.c" in your working copy to "bar.c", and you want the name change to
>sync up in the repository, without losing any of "foo.c"'s version
>history.  You would then do the following:

>- Make sure no one else is accessing the repository right now.
>- 'cd' into the repository, find the file named "foo.c,v"
>- 'mv foo.c,v bar.c,v'

>   I've done this and it works, as long as no one is doing a checkout
>or update while you are renaming (if they are, results are undefined
>(=="openly hostile", as K&R once remarked)).

>   The only downside is that you will not be able to reconstruct the
>project as it did before you did this rename...because CVS will not be
>able to serve up the file "foo.c" file for you.

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


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

Re: cvs exit status

[Paul Sander]

Under some error conditions, the exit status gets incremented rather than
being set to a fixed value.  That means that under those error conditions,
the exit status varies and may sometimes indicate success (due to overflow)
if there are a lot of problems.

So, exit status is not a reliable way to detect problems.  You must parse
the CVS standard output and standard error streams for relevant messages.

--- Forwarded mail from [EMAIL PROTECTED]

I am writing some shell script that invoke
cvs commands: some command appear to return  
always "0".

For example

[andrew]$ cvs update no-such-file.fig  ; echo $?
cvs server: nothing known about no-such-file.fig
0 

My repository is remote (pserver) and my CVS
version is 1.10.8.

There is a method to retrieve the true exit code 
or I need to parse the output messages ?

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


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

RE: deprecated caommand in 1.11.1.1

[Greg A. Woods]

[ On Wednesday, October 10, 2001 at 09:22:50 (-0400), Stanton, Curt (NCI/IMS) wrote: ]
> Subject: RE: deprecated caommand in 1.11.1.1
>
>   Well, I am planning on getting comfortable with the concurrent part
> of it, but why not get comfortable with it using CVS seeing as there was
> some sort of locking feature on it already.  I was simply asking if there
> was something like that on the newest version or if I had to start out with
> a previous version.  

There is no traditional check-out locking support in CVS.  Whatever you
think is there is a mostly broken bad idea.  It is deprecated in
1.11.1.1 _because_ it's broken and unworkable.

Either dive right in with CVS, or don't.  If you need some time to get
comfortable with parallel development techniques then practice them with
RCS and read some of the many papers published discussing this
methodology (many tools implement it).

If this is any kind of a problem for you then CVS is probably not going
to meet your requirements and you should stop considering it.

I suspect that if your team needs more orderly interaction with the
versioning tools you use then you should look at something somewhat more
sophisticated than CVS, such as Aegis, as I've already suggested.

-- 
Greg A. Woods

+1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>

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

No $Name$ substitution

[Christian Tveen Jensen]

Hello,
I would like to use the $Name$ within my source code, but have failed
to get a substitution to work.
I've done something like
cvs co -rHot-1 module
if I do cvs status, the Sticky tag is set to Hot-1.
looking into the source code only shows $Name:
$
I've also tried cvs export -rHot-1 module, with the same result.
Hope anyone has a clue to what is missing.
Regards Christian G. Tveen.

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

Re: Why can't root check in files?

[Larry Jones]

[EMAIL PROTECTED] writes:
> 
> cvs [commit aborted]: cannot commit files as 'root'
> 
> Can someone explain this to me, please?  It's a major problem for me.
> I had a look through the FAQ and the cvs document, but could find no
> mention of it.

Here's what the current development version of the manual has to say:

When committing a permanent change, CVS makes a log entry of who
committed the change.  If you are committing the change logged
in as "root" (not under "su" or other root-priv giving program),
CVS cannot determine who is actually making the change. As such,
by default, CVS disallows changes to be committed by users
logged in as "root".  (You can disable this option by commenting
out the definition of CVS_BADROOT in 'options.h' before building
CVS.

-Larry Jones

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

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

Re: committing alias modules

[Larry Jones]

Brooke Smith writes:
> 
> It seems obvious that commit doesn't work with module alias files -
> commit must only work with files and directories in the current working
> directory.  

Exactly.  "checkout" and the various r* commands are the only CVS
commands that work on modules -- all the other commands work on checked-
out files and/or directories.

> So do I have to say:
> 
> bsmith$ cvs ci xpp tk

Yes.  Or you can change your module definition so that those directories
get created as subdirectories of a "translate" directory, which would
probably make your life easier.

-Larry Jones

...That would be pretty cool, if they weren't out to kill me. -- Calvin

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

Re: How to handle drive letters on 'Windows

[Larry Jones]

Chris Nelson writes:
> 
>  cvs -d "C:\Data Files\Repository" import ...
> 
> but keep getting a parsing error.  The : confuses cvs.  Is there a
> command line workaround?



Pay careful attention to the fourth paragraph.

-Larry Jones

I like maxims that don't encourage behavior modification. -- Calvin

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

Re: file,t

[Larry Jones]

[EMAIL PROTECTED] writes:
> 
> What are and of what purpose are *,t-files?
> In my case they seem to be appeared when new files where created.

Exactly.  The *,t file stores the message you supplied (with -m) to the
add command until you commit the file (and the message goes into the RCS
file).

> I'm suffering from unresolved conflicts which I can't resolve,
> update won't work (cvs update: conflict: *file* created independently by
> second party)

That means that there is already a file in the repository with the same
name.  What you need to do is to rename your file and then "cvs remove"
it to undo the add, do a "cvs update" to get the file checked out of the
repository, and then compare your file to the repository file and
resolve any conflicts however you like.

-Larry Jones

He piqued my curiosity. -- Calvin

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

Re: CVS client port and proxys

[Larry Jones]

david delbecq writes:
> 
> Am trying to use the cvs tool (client part) from behind a proxy (running on a 
> RedHat). The configuration of the proxy fobids me to connect (I always receive 
> a connection timed out) to public cvs servers.

Do you mean a firewall?

> Does somebody know the lines to add to the proxy configuration file to allow 
> the opening of this port.

Since you haven't told us what proxy/firewall you're running, that would
require quite a crystal ball.

> I understand this is not directly a question related to cvs but you perhaps 
> know the anwer (and i don't know what the cvs default port is!).

That depends on what connection method you're using.  If you're using
:pserver:, the default port is whatever you've defined "cvspserver" as
(typically 2401).  If you're using :ext:, it's whatever port your
external command (e.g., RSH or SSH) uses.

-Larry Jones

I take it there's no qualifying exam to be a Dad. -- Calvin

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

Re: cvs [login aborted]: connect to 216.254.34.156:2401 failed: Connection timed out

[Larry Jones]

Matt Burba writes:
> 
> I am a newbie to cvs and I am having problems logging in as a client
> from my work machine (WinNT).  The server I am logging into is running
> Linux and I have no trouble connecting from home (using WinCVS or
> Forte For Java's built in client).  I am DEFINITELY behind a firewall
> at work that I have no control over.  I can telnet to the ip address
> (port 23?) and connect via ftp (port 21?).

You need to get the firewall administrator to allow outgoing connections
to port 2401 (presuming you want to use pserver to connect).  If your
filewall already allows RSH (unlikely) or SSH (quite possibly)
connections, you can use one of them with the :ext: connection method
instead of using pserver.

-Larry Jones

He's just jealous because I accomplish so much more than he does. -- Calvin

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

Re: [kfogel@collab.net: Re: rename in cvs]

[Greg A. Woods]

[ On Wednesday, October 10, 2001 at 10:52:04 (-0700), Paul Sander wrote: ]
> Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
>
> Generally speaking, renaming stuff in CVS is royal pain.  You always lose
> something.  It's up to you to decide what you're willing to give up.

You never loose anything if you do it right.

(and assuming some bugs are fixed in some ancillary sub-commands)

-- 
Greg A. Woods

+1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>

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

CVS:short path

[Sawasy, Matthew]

Title: CVS:short path





Hello!


I'm currently in the process of installing CVS on Solaris.  One of the senior geeks wants the CVSROOT to be as simple as possible for the developers.  That being said my question is:

Do you know of a method in CVS of shortening the path from say
    
:pserver:foo@bar:/usr/local/cvs_rep 


to


:pserver:foo@bar:/cvs_rep


while keeping the repository in /usr/local/cvs_rep and not using a symbolic link?


Cheers


m!
-- 
Matthew Sawasy
System Programmer
ICBC Enterprise Computing
P: (604)443-7310
E: [EMAIL PROTECTED]

Re: How to lock CVS for check-in

[Brad L. Chisholm]

You can selectively lock branches, but only if the branch info can get
passed to your commitinfo script.  We have "enhanced" the commitinfo
interface locally to send additional parameters we find useful, including
the branch info.  I'd be happy to send the diffs (commit.c), if anyone 
is interested.

-Brad

On Wed, Oct 10, 2001 at 11:57:25AM -0600, David Everly wrote:
> Can I do a selective lock using this process, such that only certain
> branches are locked?  What would my script look for if this could be
> done?
> 
> On Wed, Oct 10, 2001 at 12:59:46PM -0400, Brad L. Chisholm wrote:
> > You could also create a commitinfo trigger which returns non-zero, and
> > optionally displays a message indicating that check-ins are currently
> > disabled.  Since read locks can occur in normal use, this also allows
> > the users to distinguish between a mandated lockdown, and just a normal
> > lock collision.
> > 
> > -Brad
> > 
> > On Tue, Oct 09, 2001 at 03:28:10PM -0400, Larry Jones wrote:
> > > [EMAIL PROTECTED] writes:
> > > > 
> > > >            I have set up a CVS as part of my project. At times I want to
> > > > lock the CVS for check-ins .But checkouts should not be locked. Is there a
> > > > way to do this in the CVS. Could any one help me to resolve the issue.
> > > 
> > > You need to create a read lock in each directory in your repository. 
> > > See the manual for technical details:
> > > 
> > > 
> > > 
> > > -Larry Jones
> > > 
> > > Even though we're both talking english, we're not speaking the same language.
> > > -- Calvin
> > > 
> > > ___
> > > Bug-cvs mailing list
> > > [EMAIL PROTECTED]
> > > http://mail.gnu.org/mailman/listinfo/bug-cvs
> > 
> > ___
> > Info-cvs mailing list
> > [EMAIL PROTECTED]
> > http://mail.gnu.org/mailman/listinfo/info-cvs
> 
> -- 
> [EMAIL PROTECTED]
> V-Net:   622-3286
> Phone: 1-719-535-3286
> Pager: 1-800-724-3624 # 140-1311

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

Re: cvs exit status

[Greg A. Woods]

[ On Wednesday, October 10, 2001 at 10:57:50 (-0700), Paul Sander wrote: ]
> Subject: Re: cvs exit status
>
> Under some error conditions, the exit status gets incremented rather than
> being set to a fixed value.  That means that under those error conditions,
> the exit status varies and may sometimes indicate success (due to overflow)
> if there are a lot of problems.
> 
> So, exit status is not a reliable way to detect problems.  You must parse
> the CVS standard output and standard error streams for relevant messages.

What's wrong with using relational tests?!?!?!?  Don't you do that
anyway just as a matter of careful robust programming?

-- 
Greg A. Woods

+1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>

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

Re: CVS:short path

[Larry Jones]

Sawasy, Matthew writes:
> 
> Do you know of a method in CVS of shortening the path from say
>   
> :pserver:foo@bar:/usr/local/cvs_rep 
> 
> to
> 
> :pserver:foo@bar:/cvs_rep
> 
> while keeping the repository in /usr/local/cvs_rep and not using a symbolic
> link?

Some systems have a loopback filesystem that can be used to mount one
directory on another.  Failing that, you can always use an NFS mount
(which is reasonably safe in this case since the client and server are
the exact same machine).

-Larry Jones

I suppose if I had two X chromosomes, I'd feel hostile too. -- Calvin

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

Re: CVS:short path

[Bob Bowen]

> "Sawasy, Matthew" wrote:
> 
> Hello!
> 
> I'm currently in the process of installing CVS on Solaris.  One of the
> senior geeks wants the CVSROOT to be as simple as possible for the
> developers.  That being said my question is:
> 
> Do you know of a method in CVS of shortening the path from say
> 
> :pserver:foo@bar:/usr/local/cvs_rep
> 
> to
> 
> :pserver:foo@bar:/cvs_rep
> 
> while keeping the repository in /usr/local/cvs_rep and not using a
> symbolic link?

On our Linux system, we mount the repository on the desired path. I
would think Solaris would be able to do it, too. All it took was a line
in /etc/mtab like this:

localhost:/u2/CVS /cvs nfs rw,addr=127.0.0.1 0 0


In this particular case /u2/CVS is in a different filesystem, but I
don't think that's necessary (though using a filesystem other than root
is generally a good idea, IMHO).

Hope this helps,

=Bob=

Bob Bowen  [EMAIL PROTECTED]  Process Engineering 
(952)876-4635

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

Re: [kfogel@collab.net: Re: rename in cvs]

[Paul Sander]

>--- Forwarded mail from [EMAIL PROTECTED]

>[ On Wednesday, October 10, 2001 at 10:52:04 (-0700), Paul Sander wrote: ]
>> Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
>>
>> Generally speaking, renaming stuff in CVS is royal pain.  You always lose
>> something.  It's up to you to decide what you're willing to give up.

>You never loose anything if you do it right.

>(and assuming some bugs are fixed in some ancillary sub-commands)

In one method, you lose the ability to get a file's entire revision history
in one place (i.e. you must track down its old location(s) and fetch
additional history from there).

In another method, you lose the ability to re-create old configurations
due to missing files.

In still another method, you lose the ability to re-create old configurations
due to extra files.

In all of these methods plus at least one other, you lose the ability to
merge between branches when the rename is done on one of them, at least,
not with the customary "cvs update -j".

I've tried them all.  None of them is 100% satisfactory.

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


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

Re: [kfogel@collab.net: Re: rename in cvs]

[Sam Steingold]

> * In message <[EMAIL PROTECTED]>
> * On the subject of "Re: [[EMAIL PROTECTED]: Re: rename in cvs]"
> * Sent on Wed, 10 Oct 2001 15:06:14 -0400 (EDT)
> * Honorable [EMAIL PROTECTED] (Greg A. Woods) writes:
>
> [ On Wednesday, October 10, 2001 at 10:52:04 (-0700), Paul Sander wrote: ]
> > Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
> >
> > Generally speaking, renaming stuff in CVS is royal pain.  You always lose
> > something.  It's up to you to decide what you're willing to give up.
> 
> You never loose anything if you do it right.
> (and assuming some bugs are fixed in some ancillary sub-commands)

if you rename FOO to BAR "the right way", i.e.,

$ mv FOO BAR
$ cvs rm FOO
$ cvs add BAR
$ cvs ci BAR

then you lose in many ways:

 * 'cvs log BAR' does not list changes in file FOO

 * there is no way to compare BAR 1.123 with FOO 1.321
   [yeah, they are separated by over a hundred revisions, so what?
there are still situations when this makes sense.]

 -->  etc - CVS does not know that FOO is the old name for BAR.

 * also, this operation cannot be undone gracefully: when I do the above
   renaming backwards, CVS moves BAR,v into the attic and there is no
   way to get the revisions of BAR into the FOO,v file
   (or is there - how do I concat two *,v files?!)

This is why I usually rename the *,v files, edit them manually to
replace file names in $Id$ and also edit history.

The problem is that I do not always have shell access - then I am stuck.

Ideally I want to be able to say
$ cvs rename -r 2.0 FOO BAR
so that BAR 2.0 is the same as the current FOO.
then BAR 1.123 will be the same as FOO 1.123.
CVS would know that FOO and BAR are the same logical file.
$ cvs co -r 1.123 BAR
and
$ cvs co -r 1.123 FOO
would create a file named FOO while
$ cvs co -r 2.0 BAR
and
$ cvs co -r 2.0 FOO
would create a file named BAR


-- 
Sam Steingold (http://www.podval.org/~sds)
Support Israel's right to defend herself! 
Read what the Arab leaders say to their people on 
Only adults have difficulty with childproof caps.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: cvs exit status

[Paul Sander]

>--- Forwarded mail from [EMAIL PROTECTED]

>[ On Wednesday, October 10, 2001 at 10:57:50 (-0700), Paul Sander wrote: ]
>> Subject: Re: cvs exit status
>>
>> Under some error conditions, the exit status gets incremented rather than
>> being set to a fixed value.  That means that under those error conditions,
>> the exit status varies and may sometimes indicate success (due to overflow)
>> if there are a lot of problems.
>> 
>> So, exit status is not a reliable way to detect problems.  You must parse
>> the CVS standard output and standard error streams for relevant messages.

>What's wrong with using relational tests?!?!?!?  Don't you do that
>anyway just as a matter of careful robust programming?

What happens on a Unix system when the exit status exceeds 127?  It overflows.
An incremented exit status can (and does) report success in the presence of
failures.

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


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

How to set-up CVS server on RedHat 7.1 to use from Netbeans?

[Neil Aggarwal]

Hello:

I have the following development environment:
Dell Laptop
Windows 2000 
JDK 1.3
Netbeans 3.2

I need to share a project with several developers that
are remotely located.

Therefore, I am thinking of setting up a CVS server on
a RedHat 7.1 machine that I have for development.  Since
it is is our colo space, it will be remotely accessible.

I started to look at the CVS web site and got horribly confused
as most of the docs talk about using a server, not how to 
set it up.

If I go to the server, it already has the CVS RPM installed,
rpm -q cvs yields cvs-1.11-3

So, all I need to do is to figure out how to set it up so
I can checking my existing source files from Netbeans on my
laptop.

Also, I have seen a lot of projects on sourceforge 
using CVS over SSH, which I think is a great idea.  
Unfortunately, this is a non open-source project so I cant
use sourceforge.

I already have sshd running on the server, but will
netbeans on my laptop recognize it?

Thanks,
Neil.

--
Neil Aggarwal
JAMM Consulting, Inc.(972) 612-6056, http://www.JAMMConsulting.com
Custom Internet DevelopmentWebsites, Ecommerce, Java, databases

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

RE: How to lock CVS for check-in

[Pyatt, Scott]

"How to lock a branch?"  This seems to be the number one question posted to
info-cvs.  I posted it myself two years ago.  Is there anyway this
enhancement can get rolled into a future release of cvs (e.g., 1.12)?  If
not, is the fear that it may break existing commitinfo scripts?

Thanks,
-Scott

-Original Message-
From: Brad L. Chisholm [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 1:15 PM
To: David Everly
Cc: Brad L. Chisholm; Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: How to lock CVS for check-in


You can selectively lock branches, but only if the branch info can get
passed to your commitinfo script.  We have "enhanced" the commitinfo
interface locally to send additional parameters we find useful, including
the branch info.  I'd be happy to send the diffs (commit.c), if anyone 
is interested.

-Brad

On Wed, Oct 10, 2001 at 11:57:25AM -0600, David Everly wrote:
> Can I do a selective lock using this process, such that only certain
> branches are locked?  What would my script look for if this could be
> done?
> 
> On Wed, Oct 10, 2001 at 12:59:46PM -0400, Brad L. Chisholm wrote:
> > You could also create a commitinfo trigger which returns non-zero, and
> > optionally displays a message indicating that check-ins are currently
> > disabled.  Since read locks can occur in normal use, this also allows
> > the users to distinguish between a mandated lockdown, and just a normal
> > lock collision.
> > 
> > -Brad
> > 
> > On Tue, Oct 09, 2001 at 03:28:10PM -0400, Larry Jones wrote:
> > > [EMAIL PROTECTED] writes:
> > > > 
> > > >            I have set up a CVS as part of my project. At times I
want to
> > > > lock the CVS for check-ins .But checkouts should not be locked. Is
there a
> > > > way to do this in the CVS. Could any one help me to resolve the
issue.
> > > 
> > > You need to create a read lock in each directory in your repository. 
> > > See the manual for technical details:
> > > 
> > > 
> > > 
> > > -Larry Jones
> > > 
> > > Even though we're both talking english, we're not speaking the same
language.
> > > -- Calvin
> > > 
> > > ___
> > > Bug-cvs mailing list
> > > [EMAIL PROTECTED]
> > > http://mail.gnu.org/mailman/listinfo/bug-cvs
> > 
> > ___
> > Info-cvs mailing list
> > [EMAIL PROTECTED]
> > http://mail.gnu.org/mailman/listinfo/info-cvs
> 
> -- 
> [EMAIL PROTECTED]
> V-Net:   622-3286
> Phone: 1-719-535-3286
> Pager: 1-800-724-3624 # 140-1311

___
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: Module directory nameing....

[Bryon Lape]

Does this mean I could do this in the modules file??

foo-jsp -d foo foo-jsp/dir
foo-html -d foo foo-html/dir

and the when a user does this:

cvs checkout foo-jsp

it will get copied to foo and so will this

cvs checkout foo-html

??

Kaz Kylheku wrote:

> In article <[EMAIL PROTECTED]>, Bryon Lape wrote:
> >When a user does cvs checkout foo-jsp, I would like the local directory
> >that gets created to just be called foo and not foo-jsp.
>
> One way is the module definition
>
> foo-jsp -d foo foo-jsp
>
> This defines a regular module called foo-jsp which checks out the
> directory foo-jsp. The -d module option causes the checkout name
> to be foo rather than foo-jsp.
>
> > The same would
> >be for foo-html; that is, just foo locally.
>
> Probably a bad idea to have two that clash this way.

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

RE: moving a tag

[Jerry Nairn]

> From: Arcin Bozkurt [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 10, 2001 6:35 AM

> Will the following command update the tag Dev13 to point to 
> the newest versions in the repository?? (It should work only 
> for the files that were tagged with this tagname before)
> 

> cvs rtag -F Dev13
> (no module name is specified, cause i am in that projects 
> working copy)
> Or is the module name required?

Yes, the module name is required with rtag.

I don't think you can do this with one command.

cvs rtag -F Dev13 modulename

would tag everything, and

cvs rtag -r Dev13 -F Dev13 modulename

would only "move" the tag to exactly the same revision.

cvs co -d foo -r Dev13 modulename
cvs tag -r HEAD -F Dev13 foo

would move the tag to the head revision of every file which already had the
tag in it.

Jerry

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

Re: CVS import branching question

[Kaz Kylheku]

In article <[EMAIL PROTECTED]>, Chalmers, Tim wrote:
>I am experiencing some weirdness that I do not understand.  I am issuing the
>following commands:
>
>cvs import -m InititalRelease GyLocation VenderTag ReleaseTag  
>cvs checkout  filename
>cvs status filename 
>
>
>The output looks like:
>
>File: gybtmfw_GyTaskController_setStatus_313.qppStatus: Up-to-date
>
>   Working revision:1.1.1.1 Thu Oct 11 00:16:34 2001
>   Repository revision: 1.1.1.1
>/export/home/gy45044/CVSROOT/GyLocation/gybtmfw_GyTaskController_setStatus_3
>13.qpp,v
>   Sticky Tag:  (none)
>   Sticky Date: (none)
>   Sticky Options:  (none)
>
>
>The question is, when I performed the checkout, why am I on the vender or
>Release branch?

You're not. The reason you have file 1.1.1.1 is because that is the 
head revision of the file. This is an internal notion within CVS that
you don't need to worry about.

Basically, if you import a file on a vendor branch, and the corresponding
file is not independently modified on the trunk, the new vendor branch 
version supersedes the trunk by becoming the new head.  If you make
a change and commit, it will go to the trunk.

E.g. in this case, the next version you commit will create version 1.2,
not 1.1.1.2.

If you were on the vendor branch, you would have a sticky tag indicating so.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: How to lock CVS for check-in

[Shubhabrata Sengupta]

Wondering why this enhancement is needed in the commitinfo interface when
you can always get the branch information out of the CVS/Entries file which
is always available to the commitinfo script.

Thanks

Shubho

-Original Message-
From: Pyatt, Scott <[EMAIL PROTECTED]>
To: 'Brad L. Chisholm' <[EMAIL PROTECTED]>; David Everly
<[EMAIL PROTECTED]>
Cc: Larry Jones <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, October 11, 2001 3:36 AM
Subject: RE: How to lock CVS for check-in


>"How to lock a branch?"  This seems to be the number one question posted to
>info-cvs.  I posted it myself two years ago.  Is there anyway this
>enhancement can get rolled into a future release of cvs (e.g., 1.12)?  If
>not, is the fear that it may break existing commitinfo scripts?
>
>Thanks,
>-Scott
>
>-Original Message-
>From: Brad L. Chisholm [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 10, 2001 1:15 PM
>To: David Everly
>Cc: Brad L. Chisholm; Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: How to lock CVS for check-in
>
>
>You can selectively lock branches, but only if the branch info can get
>passed to your commitinfo script.  We have "enhanced" the commitinfo
>interface locally to send additional parameters we find useful, including
>the branch info.  I'd be happy to send the diffs (commit.c), if anyone
>is interested.
>
>-Brad
>
>On Wed, Oct 10, 2001 at 11:57:25AM -0600, David Everly wrote:
>> Can I do a selective lock using this process, such that only certain
>> branches are locked?  What would my script look for if this could be
>> done?
>>
>> On Wed, Oct 10, 2001 at 12:59:46PM -0400, Brad L. Chisholm wrote:
>> > You could also create a commitinfo trigger which returns non-zero, and
>> > optionally displays a message indicating that check-ins are currently
>> > disabled.  Since read locks can occur in normal use, this also allows
>> > the users to distinguish between a mandated lockdown, and just a normal
>> > lock collision.
>> >
>> > -Brad
>> >
>> > On Tue, Oct 09, 2001 at 03:28:10PM -0400, Larry Jones wrote:
>> > > [EMAIL PROTECTED] writes:
>> > > >
>> > > >I have set up a CVS as part of my project. At times I
>want to
>> > > > lock the CVS for check-ins .But checkouts should not be locked. Is
>there a
>> > > > way to do this in the CVS. Could any one help me to resolve the
>issue.
>> > >
>> > > You need to create a read lock in each directory in your repository.
>> > > See the manual for technical details:
>> > >
>> > > 
>> > >
>> > > -Larry Jones
>> > >
>> > > Even though we're both talking english, we're not speaking the same
>language.
>> > > -- Calvin
>> > >
>> > > ___
>> > > Bug-cvs mailing list
>> > > [EMAIL PROTECTED]
>> > > http://mail.gnu.org/mailman/listinfo/bug-cvs
>> >
>> > ___
>> > Info-cvs mailing list
>> > [EMAIL PROTECTED]
>> > http://mail.gnu.org/mailman/listinfo/info-cvs
>>
>> --
>> [EMAIL PROTECTED]
>> V-Net:   622-3286
>> Phone: 1-719-535-3286
>> Pager: 1-800-724-3624 # 140-1311
>
>___
>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
>


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

RE: How to lock CVS for check-in

[Pyatt, Scott]

Is CVS/Entries available to the commitinfo script when the repository is on
a Unix server and the developer is working on an NT client (pserver)?  If
so, I can put something together.  

With companies like mine that have so many branches in order to support a
number of back and future releases, I really need to implement branch
locking to keep the developers from accidentally shooting themselves in the
foot (happened again today).  I'm just surprised that something as basic as
branch locking has not made its way into CVS yet.  That aside, CVS has been
a decent tool for us.

Thanks,
-Scott

-Original Message-
From: Shubhabrata Sengupta [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 7:54 PM
To: Pyatt, Scott; 'Brad L. Chisholm'; David Everly
Cc: Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: How to lock CVS for check-in


Wondering why this enhancement is needed in the commitinfo interface when
you can always get the branch information out of the CVS/Entries file which
is always available to the commitinfo script.

Thanks

Shubho

-Original Message-
From: Pyatt, Scott <[EMAIL PROTECTED]>
To: 'Brad L. Chisholm' <[EMAIL PROTECTED]>; David Everly
<[EMAIL PROTECTED]>
Cc: Larry Jones <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, October 11, 2001 3:36 AM
Subject: RE: How to lock CVS for check-in


>"How to lock a branch?"  This seems to be the number one question posted to
>info-cvs.  I posted it myself two years ago.  Is there anyway this
>enhancement can get rolled into a future release of cvs (e.g., 1.12)?  If
>not, is the fear that it may break existing commitinfo scripts?
>
>Thanks,
>-Scott
>
>-Original Message-
>From: Brad L. Chisholm [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 10, 2001 1:15 PM
>To: David Everly
>Cc: Brad L. Chisholm; Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: How to lock CVS for check-in
>
>
>You can selectively lock branches, but only if the branch info can get
>passed to your commitinfo script.  We have "enhanced" the commitinfo
>interface locally to send additional parameters we find useful, including
>the branch info.  I'd be happy to send the diffs (commit.c), if anyone
>is interested.
>
>-Brad
>
>On Wed, Oct 10, 2001 at 11:57:25AM -0600, David Everly wrote:
>> Can I do a selective lock using this process, such that only certain
>> branches are locked?  What would my script look for if this could be
>> done?
>>
>> On Wed, Oct 10, 2001 at 12:59:46PM -0400, Brad L. Chisholm wrote:
>> > You could also create a commitinfo trigger which returns non-zero, and
>> > optionally displays a message indicating that check-ins are currently
>> > disabled.  Since read locks can occur in normal use, this also allows
>> > the users to distinguish between a mandated lockdown, and just a normal
>> > lock collision.
>> >
>> > -Brad
>> >
>> > On Tue, Oct 09, 2001 at 03:28:10PM -0400, Larry Jones wrote:
>> > > [EMAIL PROTECTED] writes:
>> > > >
>> > > >I have set up a CVS as part of my project. At times I
>want to
>> > > > lock the CVS for check-ins .But checkouts should not be locked. Is
>there a
>> > > > way to do this in the CVS. Could any one help me to resolve the
>issue.
>> > >
>> > > You need to create a read lock in each directory in your repository.
>> > > See the manual for technical details:
>> > >
>> > > 
>> > >
>> > > -Larry Jones
>> > >
>> > > Even though we're both talking english, we're not speaking the same
>language.
>> > > -- Calvin
>> > >
>> > > ___
>> > > Bug-cvs mailing list
>> > > [EMAIL PROTECTED]
>> > > http://mail.gnu.org/mailman/listinfo/bug-cvs
>> >
>> > ___
>> > Info-cvs mailing list
>> > [EMAIL PROTECTED]
>> > http://mail.gnu.org/mailman/listinfo/info-cvs
>>
>> --
>> [EMAIL PROTECTED]
>> V-Net:   622-3286
>> Phone: 1-719-535-3286
>> Pager: 1-800-724-3624 # 140-1311
>
>___
>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
>

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

Re: How to lock CVS for check-in

[Shubhabrata Sengupta]

Yes it is - I use that same kind of scenario down here in my workplace. I
had posted a script to do this sometime back on this list, a Python script
 I forget the name of the author - apologies)  was also posted a couple of
weeks back which achieves the same thing - searching the archives should
unearth them.

I have the same kind of scenario - there are a whole bunch of branches (some
for support, some for experimental dev. some for the current release and so
on and so forth) and we have a geographically distributed team as well.
Branch locking is necessary for us the same reason - developers have shot
themselves in the foot a number of times inthe past.

Thanks

Shubho

-Original Message-
From: Pyatt, Scott <[EMAIL PROTECTED]>
To: 'Shubhabrata Sengupta' <[EMAIL PROTECTED]>; 'Brad L.
Chisholm' <[EMAIL PROTECTED]>; David Everly <[EMAIL PROTECTED]>
Cc: Larry Jones <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, October 11, 2001 9:07 AM
Subject: RE: How to lock CVS for check-in


>Is CVS/Entries available to the commitinfo script when the repository is on
>a Unix server and the developer is working on an NT client (pserver)?  If
>so, I can put something together.
>
>With companies like mine that have so many branches in order to support a
>number of back and future releases, I really need to implement branch
>locking to keep the developers from accidentally shooting themselves in the
>foot (happened again today).  I'm just surprised that something as basic as
>branch locking has not made its way into CVS yet.  That aside, CVS has been
>a decent tool for us.
>
>Thanks,
>-Scott
>
>-Original Message-
>From: Shubhabrata Sengupta [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, October 10, 2001 7:54 PM
>To: Pyatt, Scott; 'Brad L. Chisholm'; David Everly
>Cc: Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: How to lock CVS for check-in
>
>
>Wondering why this enhancement is needed in the commitinfo interface when
>you can always get the branch information out of the CVS/Entries file which
>is always available to the commitinfo script.
>
>Thanks
>
>Shubho
>
>-Original Message-
>From: Pyatt, Scott <[EMAIL PROTECTED]>
>To: 'Brad L. Chisholm' <[EMAIL PROTECTED]>; David Everly
><[EMAIL PROTECTED]>
>Cc: Larry Jones <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
><[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Thursday, October 11, 2001 3:36 AM
>Subject: RE: How to lock CVS for check-in
>
>
>>"How to lock a branch?"  This seems to be the number one question posted
to
>>info-cvs.  I posted it myself two years ago.  Is there anyway this
>>enhancement can get rolled into a future release of cvs (e.g., 1.12)?  If
>>not, is the fear that it may break existing commitinfo scripts?
>>
>>Thanks,
>>-Scott
>>
>>-Original Message-
>>From: Brad L. Chisholm [mailto:[EMAIL PROTECTED]]
>>Sent: Wednesday, October 10, 2001 1:15 PM
>>To: David Everly
>>Cc: Brad L. Chisholm; Larry Jones; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>>Subject: Re: How to lock CVS for check-in
>>
>>
>>You can selectively lock branches, but only if the branch info can get
>>passed to your commitinfo script.  We have "enhanced" the commitinfo
>>interface locally to send additional parameters we find useful, including
>>the branch info.  I'd be happy to send the diffs (commit.c), if anyone
>>is interested.
>>
>>-Brad
>>
>>On Wed, Oct 10, 2001 at 11:57:25AM -0600, David Everly wrote:
>>> Can I do a selective lock using this process, such that only certain
>>> branches are locked?  What would my script look for if this could be
>>> done?
>>>
>>> On Wed, Oct 10, 2001 at 12:59:46PM -0400, Brad L. Chisholm wrote:
>>> > You could also create a commitinfo trigger which returns non-zero, and
>>> > optionally displays a message indicating that check-ins are currently
>>> > disabled.  Since read locks can occur in normal use, this also allows
>>> > the users to distinguish between a mandated lockdown, and just a
normal
>>> > lock collision.
>>> >
>>> > -Brad
>>> >
>>> > On Tue, Oct 09, 2001 at 03:28:10PM -0400, Larry Jones wrote:
>>> > > [EMAIL PROTECTED] writes:
>>> > > >
>>> > > >I have set up a CVS as part of my project. At times I
>>want to
>>> > > > lock the CVS for check-ins .But checkouts should not be locked. Is
>>there a
>>> > > > way to do this in the CVS. Could any one help me to resolve the
>>issue.
>>> > >
>>> > > You need to create a read lock in each directory in your repository.
>>> > > See the manual for technical details:
>>> > >
>>> > > 
>>> > >
>>> > > -Larry Jones
>>> > >
>>> > > Even though we're both talking english, we're not speaking the same
>>language.
>>> > > -- Calvin
>>> > >
>>> > > ___
>>> > > Bug-cvs mailing list
>>> > > [EMAIL PROTECTED]
>>> > > http://mail.gnu.org/mailman/listinfo/bug-cvs
>>> >
>>> > _

Re: [kfogel@collab.net: Re: rename in cvs]

[Greg A. Woods]

[ On Wednesday, October 10, 2001 at 14:40:11 (-0700), Paul Sander wrote: ]
> Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
>
> In one method, you lose the ability to get a file's entire revision history
> in one place (i.e. you must track down its old location(s) and fetch
> additional history from there).

That's not a loss, nothing is lost -- that a stupid illogical complaint.

-- 
Greg A. Woods

+1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>

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

Re: [kfogel@collab.net: Re: rename in cvs]

[Greg A. Woods]

[ On , October 10, 2001 at 17:31:23 (-0400), Sam Steingold wrote: ]
> Subject: Re: [[EMAIL PROTECTED]: Re: rename in cvs]
>
> if you rename FOO to BAR "the right way", i.e.,
> 
> $ mv FOO BAR
> $ cvs rm FOO
> $ cvs add BAR
> $ cvs ci BAR
> 
> then you lose in many ways:

No, you lose absolutely nothing -- in fact you _gain_ the information
about the rename!

>  * 'cvs log BAR' does not list changes in file FOO

Of course not  You do not want it to!  That would be illogical.

>  * there is no way to compare BAR 1.123 with FOO 1.321
>[yeah, they are separated by over a hundred revisions, so what?
> there are still situations when this makes sense.]

Bull.  It's trivial to do.

>  -->  etc - CVS does not know that FOO is the old name for BAR.
> 
>  * also, this operation cannot be undone gracefully: when I do the above
>renaming backwards, CVS moves BAR,v into the attic and there is no
>way to get the revisions of BAR into the FOO,v file
>(or is there - how do I concat two *,v files?!)

It's trivial to "undo" too -- the same way you "undo" any commit.

> The problem is that I do not always have shell access - then I am stuck.

You don't need to have shell-level access to the repository.

-- 
Greg A. Woods

+1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>

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

Re: How to lock CVS for check-in

[Greg A. Woods]

[ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata Sengupta wrote: ]
> Subject: Re: How to lock CVS for check-in
>
> Wondering why this enhancement is needed in the commitinfo interface when
> you can always get the branch information out of the CVS/Entries file which
> is always available to the commitinfo script.

I'm not sure the CVS/Entries file is always available, and in any case
accessing it directly is a very very very bad hack.  Its contents should
be private and for CVS internal use only.  The fact that some of its
structure is documented in the manual is not permission to go mucking
about in it unless you're cleaning up some form of corruption or another.

-- 
Greg A. Woods

+1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>

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

Re: Why can't root check in files?

[luke]

On 10 Oct, Larry Jones wrote:
>  [EMAIL PROTECTED] writes:
> > 
> > cvs [commit aborted]: cannot commit files as 'root'
> > 
> > Can someone explain this to me, please?  It's a major problem for me.
> > I had a look through the FAQ and the cvs document, but could find no
> > mention of it.
>  
>  Here's what the current development version of the manual has to say:
>  
>   When committing a permanent change, CVS makes a log entry of who
>   committed the change.  If you are committing the change logged
>   in as "root" (not under "su" or other root-priv giving program),
>   CVS cannot determine who is actually making the change. As such,
>   by default, CVS disallows changes to be committed by users
>   logged in as "root".  (You can disable this option by commenting
>   out the definition of CVS_BADROOT in 'options.h' before building
>   CVS.

Thanks.  That makes sense, and I think it's right.

However, I still think that I'm onto something good here - the cvs
control of Unix config files.  Unfortunately, this sensible cvs feature
utterly prevents me from providing this useful facility.

The idea of modifying cvs to remove the restriction (as I just noticed
the comment is src/options.h suggest):

>   * As such, by default, CVS disallows changes to be committed by users
>   * logged in as "root".  You can disable this option by commenting out
>   * the lines below.

isn't a good solution either, since I want to release my script that
puts /etc under cvs control.  There would be little value in doing that
if it would require people to compile a special version of cvs.

I think the problem would be solved, though, if cvs were to have the
following commit option added:

-u USER This option means, override the apparent user when
recording the change.  This is useful if you wish
commit a change as root, or if you are sitting down at
someone else's login for some reason, and making a
change there.  Use this option responsibly.

Sometimes, I've wished I could do that.  Sometimes, the complex problem
you're resolving only shows up on certain people's machines, in their
peculiar environment, and it's just 10 times faster to fix it on the
spot.

BTW, the shell script I've written proved to be surprisingly
challenging; it's 1200 lines long.  (Hmm, 30% of that is comment - good
for me!)

I plan to test it out a bit more than just on my home Linux system
before I release it.  That is, if I can get this small change made to
cvs.  :-)

Would it make it easier if I offered to do it myself and submit a patch?

luke


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

Re: How to lock CVS for check-in

[Shubhabrata Sengupta]

At least in pserver access it is and I think it is also available in for
local repository access as well. I am not sure about :ext: access though.

I agree that its contents and its structure is entirely internal to CVS and
may change without notice from one CVS release to another. I do not write
anything into CVS/Entries at all - I use it to read the branch name of the
file that is being committed. So that way there is very little danger of
corrupting that file. Of course I make assumptions about the structure of
the file and that may change from one CVS release to another - I am ready to
change the regex I use to grep the branch name when that happens. The
advantages I get from controlling access to branches through commitinfo
script outweighs the risk in my case.

Thanks

Shubho

-Original Message-
From: Greg A. Woods <[EMAIL PROTECTED]>
To: CVS-II Discussion Mailing List <[EMAIL PROTECTED]>
Date: Thursday, October 11, 2001 10:47 AM
Subject: Re: How to lock CVS for check-in


>[ On Thursday, October 11, 2001 at 08:24:11 (+0530), Shubhabrata Sengupta
wrote: ]
>> Subject: Re: How to lock CVS for check-in
>>
>> Wondering why this enhancement is needed in the commitinfo interface when
>> you can always get the branch information out of the CVS/Entries file
which
>> is always available to the commitinfo script.
>
>I'm not sure the CVS/Entries file is always available, and in any case
>accessing it directly is a very very very bad hack.  Its contents should
>be private and for CVS internal use only.  The fact that some of its
>structure is documented in the manual is not permission to go mucking
>about in it unless you're cleaning up some form of corruption or another.
>
>--
> Greg A. Woods
>
>+1 416 218-0098  VE3TCP  <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
>Planix, Inc. <[EMAIL PROTECTED]>;   Secrets of the Weird <[EMAIL PROTECTED]>
>
>___
>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: [kfogel@collab.net: Re: rename in cvs]

[Kaz Kylheku]

In article <[EMAIL PROTECTED]>, Greg A. Woods wrote:
>>  * 'cvs log BAR' does not list changes in file FOO
>
>Of course not  You do not want it to!  That would be illogical.

That is false. Just because the tool doesn't do something doesn't mean we
don't *want* it or that it is illogical. Some version control tools can
handle renames.  The actual object being version is stored anonymously,
and a path name is just another versioned property of that object.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: Why can't root check in files?

[Mike Castle]

On Thu, Oct 11, 2001 at 03:37:47PM +1000, [EMAIL PROTECTED] wrote:
> However, I still think that I'm onto something good here - the cvs
> control of Unix config files.  Unfortunately, this sensible cvs feature
> utterly prevents me from providing this useful facility.

Use something like GNU's cfengine
(http://www.gnu.org/software/cfengine/cfengine.html) and put those
configuration files under CVS control.

Check the CVS archives.  Been discussed here several times in the past.  :->

mrc
-- 
 Mike Castle  [EMAIL PROTECTED]  www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

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