You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@logging.apache.org by Henri Yandell <ba...@apache.org> on 2005/10/09 19:29:20 UTC
Migration Complete Was: CVS -> SVN Migration Status
Okay, all done:
---------
http://svn.apache.org/repos/asf/logging/
svn co https://svn.apache.org/repos/asf/logging/chainsaw/trunk logging-chainsaw
svn co https://svn.apache.org/repos/asf/logging/log4cxx/trunk logging-log4cxx
svn co https://svn.apache.org/repos/asf/logging/log4j/trunk logging-log4j
svn co https://svn.apache.org/repos/asf/logging/log4net/trunk logging-log4net
svn co https://svn.apache.org/repos/asf/logging/log4php/trunk logging-log4php
svn co https://svn.apache.org/repos/asf/logging/sandbox/log4j/trunk logging-log4j-sandbox
svn co https://svn.apache.org/repos/asf/logging/site/trunk logging-site
---------
Authorization-wise, I've matched the CVS permissions, setting up 5 groups:
logging-pmc=ceki,mwomack,hoju,psmith,sdeboy,yoavs,nicko,niall,mcatan,marco,carnold,cdevienne
logging-log4j=ceki,mwomack,hoju,psmith,sdeboy,yoavs,carnold
logging-log4net=nicko,niall,ceki,psmith,yoavs,drieseng,rgrabowski
logging-log4php=ceki,marco
logging-log4cxx=ceki,mcatan,carnold,cdevienne
And then setting up the various directory permissions:
[/logging]
@logging-pmc = rw
[/logging/log4j]
@logging-log4j = rw
[/logging/sandbox/log4j]
@logging-log4j = rw
[/logging/chainsaw]
@logging-log4j = rw
[/logging/log4net]
@logging-log4net = rw
[/logging/log4php]
@logging-log4php = rw
[/logging/log4cxx]
@logging-log4cxx = rw
----
/logging/site isn't mentioned because the /logging permission encompasses
it. I think the hierarchical nature of things means that the PMC have rw
access to all subprojects now, which also means that most of the
subproject groupings can be smaller/removed due to the overlap with the
PMC group.
Mark, give me an email if this is bad and/or you have questions about
modifying it. All chairs have access to it, though it is a point of
failure for the system in that if you check it in with problems, it can
break subversion (same held for CVSROOT/avail I guess).
It's in:
https://svn.apache.org/repos/asf/infrastructure/trunk/subversion/authorization
Commit notifications should goto the same email addresses, let me know if
there are any problems with that, it always feels a bit like magic trying
to pull the bits together on that :)
Anyway, I'm done now, have at it :)
Hen
Re: Migration Complete Was: CVS -> SVN Migration Status
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 10 Oct 2005, Curt Arnold <ca...@apache.org> wrote:
> Committed changes to the Gump descriptors for LS on revision 312773
> and crossing my fingers that don't take down almost all of the Gump
> build.
Changing the repository unfortunately requires one of the people with
shell accounts on the Gump boxes to lend a hand (which I just did ;-).
If Gump finds a working copy it will do an "svn up" instead of "svn
co" and it doesn't recognize that the working copy comes from a
different repo. I've purged logging* so the next full build should
check out fresh copies.
So please keep your fingesr crossed for a little longer.
Stefan
Re: Migration Complete Was: CVS -> SVN Migration Status
Posted by Curt Arnold <ca...@apache.org>.
On Oct 10, 2005, at 6:50 PM, Curt Arnold wrote:
>
> On Oct 10, 2005, at 6:24 PM, Mark Womack wrote:
>
>
>
>> Is there anything special we need to do for projects like Gump now
>> that we have switched repositories from CVS to SVN? Anyone know
>> the answer?
>>
>> -Mark
>>
>>
>>
>
> The Gump descriptors will need to be changed (likely the repository
> element). I'll take a stab, but might be tomorrow.
Committed changes to the Gump descriptors for LS on revision 312773
and crossing my fingers that don't take down almost all of the Gump
build.
$ svn diff http://svn.apache.org/repos/asf/gump/metadata -r
312772:312773
Index: repository/logging.xml
===================================================================
--- repository/logging.xml (revision 312772)
+++ repository/logging.xml (revision 312773)
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
- Copyright 2004 The Apache Software Foundation
+ Copyright 2004-2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -15,17 +15,10 @@
limitations under the License.
-->
-<repository name="logging" type="cvs">
+<repository name="logging" type="svn">
<title>Logging</title>
<home-page>http://logging.apache.org/</home-page>
- <cvsweb>http://cvs.apache.org/viewcvs/</cvsweb>
+ <cvsweb>http://cvs.apache.org/viewcvs.cgi/logging/?root=Apache-SVN/
</cvsweb>
+ <url>http://svn.apache.org/repos/asf/logging</url>
<redistributable/>
-
- <root>
- <method>pserver</method>
- <user>anoncvs</user>
- <password>anoncvs</password>
- <hostname>cvs.apache.org</hostname>
- <path>/home/cvspublic</path>
- </root>
</repository>
Index: project/logging-log4j-12.xml
===================================================================
--- project/logging-log4j-12.xml (revision 312772)
+++ project/logging-log4j-12.xml (revision 312773)
@@ -21,7 +21,7 @@
Fast and flexible logging package for Java
</description>
- <cvs repository="logging" module="logging-log4j"/>
+ <svn repository="logging" module="log4j/branches/v1_2-branch"/>
<project name="logging-log4j-12">
<package>org.apache.log4j</package>
Index: project/logging-log4cxx.xml
===================================================================
--- project/logging-log4cxx.xml (revision 312772)
+++ project/logging-log4cxx.xml (revision 312773)
@@ -22,7 +22,7 @@
Apache log4cxx
</description>
- <cvs repository="logging"/>
+ <svn repository="logging" dir="log4cxx/trunk"/>
<!--
Index: project/logging-chainsaw.xml
===================================================================
--- project/logging-chainsaw.xml (revision 312772)
+++ project/logging-chainsaw.xml (revision 312773)
@@ -21,7 +21,7 @@
Chainsaw log viewer
</description>
- <cvs repository="logging"/>
+ <svn repository="logging" dir="chainsaw/trunk"/>
<project name="logging-log4j-chainsaw">
<package>org.apache.log4j.chainsaw</package>
Index: project/logging-log4j.xml
===================================================================
--- project/logging-log4j.xml (revision 312772)
+++ project/logging-log4j.xml (revision 312773)
@@ -21,7 +21,7 @@
Reliable, fast and flexible logging package for Java
</description>
- <cvs repository="logging"/>
+ <svn repository="logging" dir="log4j/trunk"/>
<project name="jakarta-log4j">
<depend project="logging-log4j" inherit="jars"/>
Re: Migration Complete Was: CVS -> SVN Migration Status
Posted by Curt Arnold <ca...@apache.org>.
On Oct 10, 2005, at 6:24 PM, Mark Womack wrote:
> Is there anything special we need to do for projects like Gump now
> that we have switched repositories from CVS to SVN? Anyone know
> the answer?
>
> -Mark
>
>
The Gump descriptors will need to be changed (likely the repository
element). I'll take a stab, but might be tomorrow.
Re: Migration Complete Was: CVS -> SVN Migration Status
Posted by Mark Womack <mw...@apache.org>.
Is there anything special we need to do for projects like Gump now that we
have switched repositories from CVS to SVN? Anyone know the answer?
-Mark
On 10/9/05, Mark Womack <mw...@apache.org> wrote:
>
> Henri,
>
> Thanks! I will be updating the web site today to mention the svn repos
> instead of the the cvs ones. And I will look into being able to
> view/change
> the permissions.
>
> And no worries about last night. I figured you were busy with other stuff
> when I did not see any emails. And it is not like we have been the fastest
> moving group on this task. Hope the home improvement is moving along!
>
> OK, everyone should try out the new repos. Report any problems or issues.
>
> Thanks!
> -Mark
>
> ----- Original Message -----
> From: "Henri Yandell" <ba...@apache.org>
> To: <ge...@logging.apache.org>
> Cc: "Mark Womack" <mw...@apache.org>
> Sent: Sunday, October 09, 2005 10:29 AM
> Subject: Migration Complete Was: CVS -> SVN Migration Status
>
>
> >
> > Okay, all done:
> >
> > ---------
> > http://svn.apache.org/repos/asf/logging/
> >
> > svn co https://svn.apache.org/repos/asf/logging/chainsaw/trunk
> > logging-chainsaw
> >
> > svn co https://svn.apache.org/repos/asf/logging/log4cxx/trunk
> > logging-log4cxx
> >
> > svn co https://svn.apache.org/repos/asf/logging/log4j/trunklogging-log4j
> >
> > svn co https://svn.apache.org/repos/asf/logging/log4net/trunk
> > logging-log4net
> >
> > svn co https://svn.apache.org/repos/asf/logging/log4php/trunk
> > logging-log4php
> >
> > svn co https://svn.apache.org/repos/asf/logging/sandbox/log4j/trunk
> > logging-log4j-sandbox
> >
> > svn co https://svn.apache.org/repos/asf/logging/site/trunk logging-site
> > ---------
> >
> > Authorization-wise, I've matched the CVS permissions, setting up 5
> groups:
> >
> >
> logging-pmc=ceki,mwomack,hoju,psmith,sdeboy,yoavs,nicko,niall,mcatan,marco,carnold,cdevienne
> > logging-log4j=ceki,mwomack,hoju,psmith,sdeboy,yoavs,carnold
> > logging-log4net=nicko,niall,ceki,psmith,yoavs,drieseng,rgrabowski
> > logging-log4php=ceki,marco
> > logging-log4cxx=ceki,mcatan,carnold,cdevienne
> >
> > And then setting up the various directory permissions:
> >
> > [/logging]
> > @logging-pmc = rw
> >
> > [/logging/log4j]
> > @logging-log4j = rw
> >
> > [/logging/sandbox/log4j]
> > @logging-log4j = rw
> >
> > [/logging/chainsaw]
> > @logging-log4j = rw
> >
> > [/logging/log4net]
> > @logging-log4net = rw
> >
> > [/logging/log4php]
> > @logging-log4php = rw
> >
> > [/logging/log4cxx]
> > @logging-log4cxx = rw
> >
> > ----
> >
> > /logging/site isn't mentioned because the /logging permission
> encompasses
> > it. I think the hierarchical nature of things means that the PMC have rw
> > access to all subprojects now, which also means that most of the
> > subproject groupings can be smaller/removed due to the overlap with the
> > PMC group.
> >
> > Mark, give me an email if this is bad and/or you have questions about
> > modifying it. All chairs have access to it, though it is a point of
> > failure for the system in that if you check it in with problems, it can
> > break subversion (same held for CVSROOT/avail I guess).
> >
> > It's in:
> >
> >
> https://svn.apache.org/repos/asf/infrastructure/trunk/subversion/authorization
> >
> > Commit notifications should goto the same email addresses, let me know
> if
> > there are any problems with that, it always feels a bit like magic
> trying
> > to pull the bits together on that :)
> >
> > Anyway, I'm done now, have at it :)
> >
> > Hen
> >
>
>
>
>
Re: Migration Complete Was: CVS -> SVN Migration Status
Posted by Mark Womack <mw...@apache.org>.
Henri,
Thanks! I will be updating the web site today to mention the svn repos
instead of the the cvs ones. And I will look into being able to view/change
the permissions.
And no worries about last night. I figured you were busy with other stuff
when I did not see any emails. And it is not like we have been the fastest
moving group on this task. Hope the home improvement is moving along!
OK, everyone should try out the new repos. Report any problems or issues.
Thanks!
-Mark
----- Original Message -----
From: "Henri Yandell" <ba...@apache.org>
To: <ge...@logging.apache.org>
Cc: "Mark Womack" <mw...@apache.org>
Sent: Sunday, October 09, 2005 10:29 AM
Subject: Migration Complete Was: CVS -> SVN Migration Status
>
> Okay, all done:
>
> ---------
> http://svn.apache.org/repos/asf/logging/
>
> svn co https://svn.apache.org/repos/asf/logging/chainsaw/trunk
> logging-chainsaw
>
> svn co https://svn.apache.org/repos/asf/logging/log4cxx/trunk
> logging-log4cxx
>
> svn co https://svn.apache.org/repos/asf/logging/log4j/trunk logging-log4j
>
> svn co https://svn.apache.org/repos/asf/logging/log4net/trunk
> logging-log4net
>
> svn co https://svn.apache.org/repos/asf/logging/log4php/trunk
> logging-log4php
>
> svn co https://svn.apache.org/repos/asf/logging/sandbox/log4j/trunk
> logging-log4j-sandbox
>
> svn co https://svn.apache.org/repos/asf/logging/site/trunk logging-site
> ---------
>
> Authorization-wise, I've matched the CVS permissions, setting up 5 groups:
>
> logging-pmc=ceki,mwomack,hoju,psmith,sdeboy,yoavs,nicko,niall,mcatan,marco,carnold,cdevienne
> logging-log4j=ceki,mwomack,hoju,psmith,sdeboy,yoavs,carnold
> logging-log4net=nicko,niall,ceki,psmith,yoavs,drieseng,rgrabowski
> logging-log4php=ceki,marco
> logging-log4cxx=ceki,mcatan,carnold,cdevienne
>
> And then setting up the various directory permissions:
>
> [/logging]
> @logging-pmc = rw
>
> [/logging/log4j]
> @logging-log4j = rw
>
> [/logging/sandbox/log4j]
> @logging-log4j = rw
>
> [/logging/chainsaw]
> @logging-log4j = rw
>
> [/logging/log4net]
> @logging-log4net = rw
>
> [/logging/log4php]
> @logging-log4php = rw
>
> [/logging/log4cxx]
> @logging-log4cxx = rw
>
> ----
>
> /logging/site isn't mentioned because the /logging permission encompasses
> it. I think the hierarchical nature of things means that the PMC have rw
> access to all subprojects now, which also means that most of the
> subproject groupings can be smaller/removed due to the overlap with the
> PMC group.
>
> Mark, give me an email if this is bad and/or you have questions about
> modifying it. All chairs have access to it, though it is a point of
> failure for the system in that if you check it in with problems, it can
> break subversion (same held for CVSROOT/avail I guess).
>
> It's in:
>
> https://svn.apache.org/repos/asf/infrastructure/trunk/subversion/authorization
>
> Commit notifications should goto the same email addresses, let me know if
> there are any problems with that, it always feels a bit like magic trying
> to pull the bits together on that :)
>
> Anyway, I'm done now, have at it :)
>
> Hen
>