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.

<[EMAIL PROTECTED]>:
Sorry, no mailbox here by that name. (#5.1.1)

--- Below this line is a copy of the message.

Return-Path: <[EMAIL PROTECTED]>
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: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] My guess is you made a typo renaming some .qmail files?

Checkout of old module name
---------------------------
[lsimons@LSD cvs]$ cvs -d [EMAIL PROTECTED]:/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 [EMAIL PROTECTED]:/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
[EMAIL PROTECTED]:/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
[EMAIL PROTECTED]:/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 *[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to