You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leo Simons <le...@apache.org> on 2003/02/05 11:03:56 UTC
request cvs renaming (was: Re: cvs repository symlink)
Hi Brian,
I guess this slipped through your busy schedule. Could you find some
time or someone to do this:
a) renaming /home/cvs/jakarta-avalon[-$foo] to /home/cvs/avalon[-$foo]
b) putting something temporary in the cvs/modules file that when someone
goes to update or commit under the old name, tells them to go to the
new one.
c) chgrp'ing /home/cvs/avalon-* to group "avalon", which all of you are
in.
d) for now, making sure that commits to the avalon modules goes to the
"right place" at the avalon-*-cvs@jakarta lists, but eventually moving
that to *-cvs@avalon.apache.org.
thanks!
- Leo
Brian Behlendorf wrote:
>On Wed, 22 Jan 2003, Leo Simons wrote:
>
>
>>Brian Behlendorf wrote:
>>
>>
>>>Symlinks are always dangerous, and I especially worry about them in a CVS
>>>repository.
>>>
>>>
>>didn't know that...hmm. We do have a few, don't we?
>>
>>
>
>Um, yeah, too many. Let's not create more. I'll address removing the
>remaining ones in a separate email to infrastructure@.
>
>I mainly worry about whether an action like that corrupts the repository
>in some subtle way. Imagine if someone checks out both the part of
>the repos that appears under the symlink, and the original name for that
>link itself, changes each copy separately, then (without thinking) checks
>both in at the same time. I don't know what'll happen, so I'm not trying
>to spread FUD, I'm just trying to completely eliminate the possibility of
>something going wrong.
>
>
>
>>>Can we just rename them, and then modify the modules file to
>>>tell people who try and check out or update jakarta-avalon[-site] about
>>>the new module name?
>>>
>>>
>>sounds good to me, but maybe I'm missing something....avalon
>>people...objections anyone?
>>
>>
>
>So, to be clear: what we're doing is
>
>a) renaming /home/cvs/jakarta-avalon[-$foo] to /home/cvs/avalon[-$foo]
>b) putting something temporary in the cvs/modules file that when someone
> goes to update or commit under the old name, tells them to go to the
> new one.
>c) chgrp'ing /home/cvs/avalon-* to group "avalon", which all of you are
> in.
>d) for now, making sure that commits to the avalon modules goes to the
> "right place" at the avalon-*-cvs@jakarta lists, but eventually moving
> that to *-cvs@avalon.apache.org.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: request cvs renaming (was: Re: cvs repository symlink)
Posted by Sam Ruby <ru...@apache.org>.
Leo Simons wrote:
> One more thing to do...
>
> e) update the ViewCVS configuration so it knows about the changes.
> Currently, it shows the following errors:
> -----------
> jakarta-avalon - this entry is unreadable
> jakarta-avalon-apps - this entry is unreadable
> jakarta-avalon-cornerstone - this entry is unreadable
> jakarta-avalon-excalibur - this entry is unreadable
> jakarta-avalon-logkit - this entry is unreadable
> jakarta-avalon-phoenix - this entry is unreadable
> jakarta-avalon-site - this entry is unreadable
> jakarta-avalon-testlet - this entry is unreadable
> jakarta-ojb - this entry is unreadable
> jakarta-turbine-torque - this entry is unreadable
>
> NOTE: One or more files were unreadable. The files in the CVS repository
> should be readable by the web server process. Please report this
> condition to the administrator of this CVS repository.
> -----------
> and it doesn't show the renamed modules.
Fixed.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: request cvs renaming (was: Re: cvs repository symlink)
Posted by Leo Simons <le...@apache.org>.
One more thing to do...
e) update the ViewCVS configuration so it knows about the changes.
Currently, it shows the following errors:
-----------
jakarta-avalon - this entry is unreadable
jakarta-avalon-apps - this entry is unreadable
jakarta-avalon-cornerstone - this entry is unreadable
jakarta-avalon-excalibur - this entry is unreadable
jakarta-avalon-logkit - this entry is unreadable
jakarta-avalon-phoenix - this entry is unreadable
jakarta-avalon-site - this entry is unreadable
jakarta-avalon-testlet - this entry is unreadable
jakarta-ojb - this entry is unreadable
jakarta-turbine-torque - this entry is unreadable
NOTE: One or more files were unreadable. The files in the CVS repository
should be readable by the web server process. Please report this
condition to the administrator of this CVS repository.
-----------
and it doesn't show the renamed modules.
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: request cvs renaming (was: Re: cvs repository symlink)
Posted by Leo Simons <le...@apache.org>.
Commit messages from new module
-------------------------------
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<av...@apache.org>:
Sorry, no mailbox here by that name. (#5.1.1)
--- Below this line is a copy of the message.
Return-Path: <le...@apache.org>
Received: (qmail 34700 invoked from network); 5 Feb 2003 22:44:29 -0000
Received: from icarus.apache.org (208.185.179.13)
by daedalus.apache.org with SMTP; 5 Feb 2003 22:44:29 -0000
Received: (qmail 55169 invoked by uid 1291); 5 Feb 2003 22:44:28 -0000
Date: 5 Feb 2003 22:44:28 -0000
Message-ID: <20...@icarus.apache.org>
From: leosimons@apache.org
To: avalon-cvs@apache.org
Subject: cvs commit: avalon README.txt
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
leosimons 2003/02/05 14:44:28
Modified: . README.txt
Log:
testing cvs repository move....
<snip/>
---
This doesn't work properly. The address is supposed to be
avalon-cvs@jakarta.apache.org. My guess is you made a typo renaming some
.qmail files?
Checkout of old module name
---------------------------
[lsimons@LSD cvs]$ cvs -d leosimons@cvs.apache.org:/home/cvs co
jakarta-avalon
cvs server: cannot find module
`avalon_repositories_have_moved_-_try_avalon-*' - ignored
cvs [checkout aborted]: cannot expand modules
[lsimons@LSD cvs]$
---
is ok with me :D
Checkout of new module
----------------------
[lsimons@LSD cvs]$ cvs -d leosimons@cvs.apache.org:/home/cvs co avalon
---
works fine.
Committing to old module
------------------------
In C:\gump\cvs\jakarta-avalon: cvs -q commit -m "testing cvs repository
move...." README.txt
CVSROOT=leosimons@cvs.apache.org:/home/cvs
cvs server: failed to create lock directory for
`/home/cvs/jakarta-avalon' (/home/cvs/jakarta-avalon/#cvs.lock): No such
file or directory
cvs server: lock failed - giving up
cvs [server aborted]: lock failed - giving up
Error, CVS operation failed
---
the error message is a little obscure, but I think everyone is informed
of the change so it should be ok.
Committing to new module
------------------------
In C:\gump\cvs\avalon: cvs -q commit -m "testing cvs repository
move...." README.txt
CVSROOT=leosimons@cvs.apache.org:/home/cvs
Checking in README.txt;
/home/cvs/avalon/README.txt,v <-- README.txt
new revision: 1.3; previous revision: 1.2
done
Mailing the commit message...
Success, CVS operation completed
---
works fine.
cheers!
- Leo
Brian Behlendorf wrote:
> On Wed, 5 Feb 2003, Leo Simons wrote:
>
>>I guess this slipped through your busy schedule. Could you find some
>>time or someone to do this:
>>
>>a) renaming /home/cvs/jakarta-avalon[-$foo] to /home/cvs/avalon[-$foo]
>
> Done. Note that there's a repos now called "/home/cvs/avalon" - not a
> problem, just be aware. The "avail" file has been updated with the new
> location too.
>
>>b) putting something temporary in the cvs/modules file that when someone
>> goes to update or commit under the old name, tells them to go to the
>> new one.
>
> Let me know if what I put there makes sense.
>
>>c) chgrp'ing /home/cvs/avalon-* to group "avalon", which all of you are
>> in.
>
> Done.
>
>>d) for now, making sure that commits to the avalon modules goes to the
>> "right place" at the avalon-*-cvs@jakarta lists, but eventually moving
>> that to *-cvs@avalon.apache.org.
>
> Done, I think. This just involved renaming the corresponding .qmail
> files. give it a try, let me know if it doesn't work.
>
> Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org
Re: request cvs renaming (was: Re: cvs repository symlink)
Posted by Brian Behlendorf <br...@collab.net>.
On Wed, 5 Feb 2003, Leo Simons wrote:
> I guess this slipped through your busy schedule. Could you find some
> time or someone to do this:
>
> a) renaming /home/cvs/jakarta-avalon[-$foo] to /home/cvs/avalon[-$foo]
Done. Note that there's a repos now called "/home/cvs/avalon" - not a
problem, just be aware. The "avail" file has been updated with the new
location too.
> b) putting something temporary in the cvs/modules file that when someone
> goes to update or commit under the old name, tells them to go to the
> new one.
Let me know if what I put there makes sense.
> c) chgrp'ing /home/cvs/avalon-* to group "avalon", which all of you are
> in.
Done.
> d) for now, making sure that commits to the avalon modules goes to the
> "right place" at the avalon-*-cvs@jakarta lists, but eventually moving
> that to *-cvs@avalon.apache.org.
Done, I think. This just involved renaming the corresponding .qmail
files. give it a try, let me know if it doesn't work.
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-dev-help@jakarta.apache.org