Re: Moving CVS repository
Greg A. Woods writes: > > [ On Friday, May 3, 2002 at 13:30:04 (-0400), Larry Jones wrote: ] > > Subject: Re: Moving CVS repository > > > > The way CVS handles a directory tree with multiple CVSROOTs is by > > running the command once for each root with just the directories that > > have that root. As far as I can tell, the *info files work just like > > you'd expect in that scenario. Can you provide an explicit example? > > One word: policy. Each set of working directories that belong to a single repository follow that repository's policy. I don't see the problem -Larry Jones That gives me a FABULOUS idea. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
On Fri, May 03, 2002 at 16:14:14 -0400, Greg A. Woods sent 0.8K bytes: > [ On Friday, May 3, 2002 at 13:30:04 (-0400), Larry Jones wrote: ] > > Subject: Re: Moving CVS repository > > > > Greg A. Woods writes: > > > > > > there are zillions of basically unsolvable issues which arise if there's > > > any use of *info files. > > > > The way CVS handles a directory tree with multiple CVSROOTs is by > > running the command once for each root with just the directories that > > have that root. As far as I can tell, the *info files work just like > > you'd expect in that scenario. Can you provide an explicit example? > > One word: policy. One word: clarification? Scott -- Simon's Law: Everything put together falls apart sooner or later. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
[ On Friday, May 3, 2002 at 13:30:04 (-0400), Larry Jones wrote: ] > Subject: Re: Moving CVS repository > > Greg A. Woods writes: > > > > there are zillions of basically unsolvable issues which arise if there's > > any use of *info files. > > The way CVS handles a directory tree with multiple CVSROOTs is by > running the command once for each root with just the directories that > have that root. As far as I can tell, the *info files work just like > you'd expect in that scenario. Can you provide an explicit example? One word: policy. -- Greg A. Woods +1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
Greg A. Woods writes: > > there are zillions of basically unsolvable issues which arise if there's > any use of *info files. The way CVS handles a directory tree with multiple CVSROOTs is by running the command once for each root with just the directories that have that root. As far as I can tell, the *info files work just like you'd expect in that scenario. Can you provide an explicit example? -Larry Jones These findings suggest a logical course of action. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
[ On Thursday, May 2, 2002 at 18:01:03 (-0400), Larry Jones wrote: ] > Subject: Re: Moving CVS repository > > Greg A. Woods writes: > > > > It's irrelevant how they get that way. If all the files in given > > working directory hierarchy are not from the same repository then the > > user loses. > > In what sense? CVS has handled that just fine for quite some time now. only in its most basic form there are zillions of basically unsolvable issues which arise if there's any use of *info files. I seem to remember a discussion on this issue back in the dark ages about this issue and the resolution would be that such "accidents" would be officially unsupported. -- Greg A. Woods +1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
Greg A. Woods writes: > > It's irrelevant how they get that way. If all the files in given > working directory hierarchy are not from the same repository then the > user loses. In what sense? CVS has handled that just fine for quite some time now. -Larry Jones There's a connection here, I just know it. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
[ On Thursday, May 2, 2002 at 15:38:27 (-0500), Joi Ellis wrote: ] > Subject: Re: Moving CVS repository > > On Thu, 2 May 2002, Greg A. Woods wrote: > > > > If I'm not mistaken the CVS/Root file _MUST_ be identical throughout an > > entire module's working directory, regardless of whether module aliases > > are used or not. A given working directory _MUST_ always come from the > > same repository. > > > > (Of course idiot users could maybe manually check out one module from > > another repository into the same working directory, but they lose and > > that's just too bad for them, IMNSHO! :-) > > Yes, that is true. > > However, this isn't what I said. I said users often nest modules. It's irrelevant how they get that way. If all the files in given working directory hierarchy are not from the same repository then the user loses. It matters not whether they were checked out with a module alias (which automatically "nests modules"), or by hand, or whatever. What you've described doesn't seem to indicate any deviation from this rule. -- Greg A. Woods +1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
On Thu, 2 May 2002, Greg A. Woods wrote: > [ On Thursday, May 2, 2002 at 13:39:06 (-0400), Eric Siegerman wrote: ] > > Subject: Re: Moving CVS repository > > > > On Wed, May 01, 2002 at 01:42:44PM -0500, Joi Ellis wrote: > > > find . -type f -name 'Root' | \ > > > xargs perl -pi.bak -e 's/localhost/some.hostname/' > > > [...] > > > I prefer using perl rather than a 'cp' because some of our modules > > > are nested and I don't trust the Root file to be identical all > > > through the tree. Maybe they are, maybe they aren't. > > > > Agreed. > > If I'm not mistaken the CVS/Root file _MUST_ be identical throughout an > entire module's working directory, regardless of whether module aliases > are used or not. A given working directory _MUST_ always come from the > same repository. > > (Of course idiot users could maybe manually check out one module from > another repository into the same working directory, but they lose and > that's just too bad for them, IMNSHO! :-) Yes, that is true. However, this isn't what I said. I said users often nest modules. This is particularly common in Java applications. There is at least one IDE that leads its users into building such bastard workspaces. I see this come up a lot on the JBuilder newsgroups because JBuilder doesn't support nested modules well (if at all) but users are trying to coerce JBuilder into adjusting itself to an existing nested workspace. Module A: dirA1 dirA2 Module B: dirB1 dirB2 Workspace: dirA1 dirA2 dir B1 dir B2 In this sort of nested workspace, one can't simply cp a Root file from the top of the workspace into all of the subdirectories because B's Root is different. -- Joi EllisSoftware Engineer Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED] No matter what we think of Linux versus FreeBSD, etc., the one thing I really like about Linux is that it has Microsoft worried. Anything that kicks a monopoly in the pants has got to be good for something. - Chris Johnson ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
[ On Thursday, May 2, 2002 at 13:39:06 (-0400), Eric Siegerman wrote: ] > Subject: Re: Moving CVS repository > > On Wed, May 01, 2002 at 01:42:44PM -0500, Joi Ellis wrote: > > find . -type f -name 'Root' | \ > > xargs perl -pi.bak -e 's/localhost/some.hostname/' > > [...] > > I prefer using perl rather than a 'cp' because some of our modules > > are nested and I don't trust the Root file to be identical all > > through the tree. Maybe they are, maybe they aren't. > > Agreed. If I'm not mistaken the CVS/Root file _MUST_ be identical throughout an entire module's working directory, regardless of whether module aliases are used or not. A given working directory _MUST_ always come from the same repository. (Of course idiot users could maybe manually check out one module from another repository into the same working directory, but they lose and that's just too bad for them, IMNSHO! :-) -- Greg A. Woods +1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
Eric Siegerman wrote: >On Wed, May 01, 2002 at 01:42:44PM -0500, Joi Ellis wrote: > >> find . -type f -name 'Root' | \ >> xargs perl -pi.bak -e 's/localhost/some.hostname/' >>[...] >>I prefer using perl rather than a 'cp' because some of our modules >>are nested and I don't trust the Root file to be identical all >>through the tree. Maybe they are, maybe they aren't. >> we have a rule in our base Makefile that fiddles with the file - and this works only on CVS Root files. .PHONY: fix_root fix_root: CVS/Root if [ X`cat $<` = X$(OLD_ROOT) ]; then echo $(NEW_ROOT) > $<; fi It's policy to have a Makefile that includes our base make file in every directory. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
On Wed, May 01, 2002 at 01:42:44PM -0500, Joi Ellis wrote: > find . -type f -name 'Root' | \ > xargs perl -pi.bak -e 's/localhost/some.hostname/' > [...] > I prefer using perl rather than a 'cp' because some of our modules > are nested and I don't trust the Root file to be identical all > through the tree. Maybe they are, maybe they aren't. Agreed. > It also makes it easier to repair damage should some foolish programmer > have a file named 'Root' with other content. The way to guard against that is to be more careful with the first, "selection", part of the pipeline, rather than the last, "action" part: find . -type f -print | grep '/CVS/Root$' | xargs [whatever] The "whatever" can be perl, cp, or anything else that makes sense (though I typically use perl, as shown above). -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / Anyone who swims with the current will reach the big music steamship; whoever swims against the current will perhaps reach the source. - Paul Schneider-Esleben ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
On Wed, 1 May 2002 [EMAIL PROTECTED] wrote:
> > I have made a mistake in accessing the host: I used
> >
> > :pserver:cvs@localhost:/home/cvs/repository
> >
> > and wanted to use
> >
> > :pserver:[EMAIL PROTECTED]:/home/cvs/repository
> >
> > Is it dangerous to do this? I do not have other files called Root.
> > I do not want to redownload everything from remote (the problem is: I
> > used this tree locally and burned it to a CDR).
> >
> > find -type f -name 'Root' \
> > -exec perl -pi -e 's/localhost/some.hostname/g' {} \;
I use a variant:
find . -type f -name 'Root' | \
xargs perl -pi.bak -e 's/localhost/some.hostname/'
This tends to launch perl only once or twice, depending upon the
size of the tree, thanks to xargs.
I prefer using perl rather than a 'cp' because some of our modules
are nested and I don't trust the Root file to be identical all
through the tree. Maybe they are, maybe they aren't.
It also makes it easier to repair damage should some foolish programmer
have a file named 'Root' with other content.
--
Joi EllisSoftware Engineer
Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED]
No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried. Anything
that kicks a monopoly in the pants has got to be good for something.
- Chris Johnson
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS repository
> I have made a mistake in accessing the host: I used
>
> :pserver:cvs@localhost:/home/cvs/repository
>
> and wanted to use
>
> :pserver:[EMAIL PROTECTED]:/home/cvs/repository
>
> Is it dangerous to do this? I do not have other files called Root.
> I do not want to redownload everything from remote (the problem is: I
> used this tree locally and burned it to a CDR).
>
> find -type f -name 'Root' \
> -exec perl -pi -e 's/localhost/some.hostname/g' {} \;
The last time I had to do a similar thing I had people create a file
called CVSRoot in their home directories and run
find -type -f -name 'Root' \
-exec cp /home/whoever/CVSRoot {} \;
Perl just looks like overkill here.
I had no problems.
David H. Thornley| If you want my opinion, ask.
[EMAIL PROTECTED] | If you don't, flee.
http://www.thornley.net/~thornley/david/ | O-
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Moving CVS repository
No problem.
If your new CVSROOT is otherwise correct changing should not pose any
problems.
Regards,
anders
-Original Message-
From: Rudolf Polzer [mailto:[EMAIL PROTECTED]]
Sent: 30. april 2002 06:57
To: [EMAIL PROTECTED]
Subject: Moving CVS repository
I have made a mistake in accessing the host: I used
:pserver:cvs@localhost:/home/cvs/repository
and wanted to use
:pserver:[EMAIL PROTECTED]:/home/cvs/repository
Is it dangerous to do this? I do not have other files called Root.
I do not want to redownload everything from remote (the problem is: I
used this tree locally and burned it to a CDR).
find -type f -name 'Root' \
-exec perl -pi -e 's/localhost/some.hostname/g' {} \;
___
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: moving cvs repository from one machine to another
This may be too late to be of use, but here goes... On Thu, Sep 27, 2001 at 07:09:56PM +0100, PRUDHVIDHAR lingala wrote: > Once you setup the CVS server on new system > > 1) Just copy the entire CVS repository from old > server and put it on new system > 2) do following on the new cvs server > cvs -d init > 3) check whether you are able to access the new > server's repository > 4) Cut off the access to the cvs repository on old > system Do (4) first! If you do the steps in the order shown here, there's a race condition: a user could commit new revisions to the old repo, too late for them to be copied to the new repo. (For a large repo, step (1) could take a long time, so this isn't a purely theoretical concern.) It'd be much safer to take the repo offline during this process -- scheduled downtime is almost certainly cheaper than lost revisions! -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The world has been attacked. The world must respond ... [but] we must be guided by a commitment to do what works in the long run, not by what makes us feel better in the short run. - Jean Chrétien, Prime Minister of Canada ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Moving CVS Repository
Title: RE: Moving CVS Repository What we are planning to do is to keep the same hostname and the path to the repository. Hence it will be transparent to the users when it comes up. Thanks joe -Original Message- From: David Taylor [mailto:[EMAIL PROTECTED]] Sent: Monday, September 17, 2001 1:37 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Moving CVS Repository Kaz Kylheku wrote: > In article <[EMAIL PROTECTED]>, Cornellious Mann wrote: > >If I want to move my CVS repository (let's say from NT > >to Unix), can I simply copy everything under CVSROOT > >into my new CVSROOT? Thanks. > > You can, however the existing users will be left stranded, pointing > to the old repository. > If the old repository was accessed via a DNS alias - rather than actual host name (or IP address) - and the path of the new repository is the same, then pointing that alias to the the host of the new repository points all checked out directories to the new repository. dtayl ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: moving cvs repository from one machine to another
Once you setup the CVS server on new system 1) Just copy the entire CVS repository from old server and put it on new system 2) do following on the new cvs server cvs -d init 3) check whether you are able to access the new server's repository 4) Cut off the access to the cvs repository on old system --- Joseph Natar <[EMAIL PROTECTED]> wrote: > Hi: > > We merged with another company recently and we took > over there cvs server. > The server was very unstable due to OS and Hardware > issues. We are planning > to move to another machine. I read thru most of the > manual and found that > after installing, initializing, unix permissions and > setting up pserver, we > plan to migrate the old repository filesystem to > the new one. If anyone has > done this before and has any advice, please let me > know. > > Thanks > > > Joe Natar > Quality Tools Engineering > Ventro Corporation > 650-903-5535 > [EMAIL PROTECTED] > > > > > Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS Repository
Kaz Kylheku wrote: > In article <[EMAIL PROTECTED]>, Cornellious Mann wrote: > >If I want to move my CVS repository (let's say from NT > >to Unix), can I simply copy everything under CVSROOT > >into my new CVSROOT? Thanks. > > You can, however the existing users will be left stranded, pointing > to the old repository. > If the old repository was accessed via a DNS alias - rather than actual host name (or IP address) - and the path of the new repository is the same, then pointing that alias to the the host of the new repository points all checked out directories to the new repository. dtayl ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Moving CVS Repository
In article <[EMAIL PROTECTED]>, Cornellious Mann wrote: >If I want to move my CVS repository (let's say from NT >to Unix), can I simply copy everything under CVSROOT >into my new CVSROOT? Thanks. You can, however the existing users will be left stranded, pointing to the old repository. It's best to coordinate this action with the users so that they can synchronize with it. This means that they commit any outstanding work, (or else throw away anything they don't intend to commit). When everyone has commited their work, you can move the repository. The users can then check out working copies from the new place. There are shortcuts possible. For example, one can write a script which edits the metadata stored in the CVS subdirectories of the working copy in order to ``rehome'' the working copy to a new location. Whatever you do, you want to avoid the situation where some users continue commiting changes to the old repository, after others have begun committing to the new! ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
