You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Geoffrey Young <ge...@modperlcookbook.org> on 2004/11/14 21:42:48 UTC
Re: [NOTICE] Subversion conversion
> It's just that someone needs to simultaneously move modperl-2.0 to
> subversion too. And modperl-docs too, since they are checked out into
> modperl-2.0 check out. As long as this is all done at once there should
> be no problem. None of these projects had any branching so it shouldn't
> be a problem. But I've next to zero experience with subversion, so I'm
> not volunteering to do that.
gozer and I can take care of this while we're here. I was waiting on you to
agree with the move before we went forward, though. and it looks like your +1.
ok, so we're giving sander and justin the ok to lock down cvs until the svn
conversion is complete, which may be a day or two. after that, everyone
will need to use svn to access mod_perl cvs (with instructions to follow).
so, rock on svn.
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>>When the spamassassin group made the switch, they added a file to the
>>CVS at the top level, telling everyone still checking it out that it was
>>obsolete and to use svn instead. I hope that happens with mod_perl's
>>tree, too. I think a file named THIS_CODE_IS_OBSOLETE.txt would be
>>pretty clear. :-)
>
>
> maybe, maybe not - someone would need to actually ls the directory to find
> the file :)
>
> a better solution would be to remove anonymous cvs access entirely (while
> keeping committer-level access, of course). gozer and I should ask about
> this, but I suspect that since httpd is also doing this conversion that they
> have thought about the issue a bit.
Yeah, I like Geoff's idea better.
Also Geoff and Philippe, please don't forget the cvs snapshots at:
http://cvs.apache.org/snapshots/modperl-2.0/
http://cvs.apache.org/snapshots/modperl-docs/
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Joe Orton <jo...@redhat.com>.
On Mon, Nov 15, 2004 at 12:33:18PM -0800, Geoffrey Young wrote:
> > When the spamassassin group made the switch, they added a file to the
> > CVS at the top level, telling everyone still checking it out that it was
> > obsolete and to use svn instead. I hope that happens with mod_perl's
> > tree, too. I think a file named THIS_CODE_IS_OBSOLETE.txt would be
> > pretty clear. :-)
>
> maybe, maybe not - someone would need to actually ls the directory to find
> the file :)
>
> a better solution would be to remove anonymous cvs access entirely (while
> keeping committer-level access, of course). gozer and I should ask about
> this, but I suspect that since httpd is also doing this conversion that they
> have thought about the issue a bit.
Do check with the infrastructure guys about this... the way that
committer CVS access-over-ssh is denied now for apr/apr-util, you can't
even "cvs up" an existing checkout to see what files you have changed:
cvs server: failed to create lock directory for `/home/cvs/apr'
(/home/cvs/apr/#cvs.lock): Permission denied
so a good workaround for this is to switch the checkout to an anoncvs
checkout (I use "scvs" for this, recursive perl foo works too), and then
you *can* cvs up again to work out what needs to be rescued from that
working copy...
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
> When the spamassassin group made the switch, they added a file to the
> CVS at the top level, telling everyone still checking it out that it was
> obsolete and to use svn instead. I hope that happens with mod_perl's
> tree, too. I think a file named THIS_CODE_IS_OBSOLETE.txt would be
> pretty clear. :-)
maybe, maybe not - someone would need to actually ls the directory to find
the file :)
a better solution would be to remove anonymous cvs access entirely (while
keeping committer-level access, of course). gozer and I should ask about
this, but I suspect that since httpd is also doing this conversion that they
have thought about the issue a bit.
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Vivek Khera <kh...@kcilink.com>.
On Nov 14, 2004, at 7:52 PM, Philippe M. Chiasson wrote:
>> Don't forget about preserving the frozen cvs though. I have lots of
>> modified files all over.
>
> Yah, the CVS repository will remain for a long time read-only. (don't
> exactly know what *long* means)
>
When the spamassassin group made the switch, they added a file to the
CVS at the top level, telling everyone still checking it out that it
was obsolete and to use svn instead. I hope that happens with
mod_perl's tree, too. I think a file named THIS_CODE_IS_OBSOLETE.txt
would be pretty clear. :-)
Vivek Khera, Ph.D.
+1-301-869-4449 x806
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Gerald Richter <ri...@ecos.de>.
Am Dienstag, 16. November 2004 17:40 schrieb Philippe M. Chiasson:
> Gerald Richter wrote:
> >Hi,
> >
> >>It would most likely reside in
> >> http://svn.apache.org/repos/asf/perl/embperl/
> >>With the standard trunk/ tags/ branches/ under there
> >
> >ok
>
> Allright, in that case I'll get infrastructure to move it over, most
> likely today. I'll let everyone know
> once it has been moved successfully. Gerald, would you like to QA the
> import at least once before
> they go ahead with the _real_ conversion ? Or do you just trust cvs2svn ?
I trust cvs2svn. In all cases it had worked for me before and in case it
really goes wrong I still have all the commit mails in my archive (and some
checked out working copies of course)
So go ahead and do the _real_ conversion.
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Gerald Richter wrote:
>Hi,
>
>
>
>>It would most likely reside in
>> http://svn.apache.org/repos/asf/perl/embperl/
>>With the standard trunk/ tags/ branches/ under there
>>
>>
>>
>
>ok
>
>
Allright, in that case I'll get infrastructure to move it over, most
likely today. I'll let everyone know
once it has been moved successfully. Gerald, would you like to QA the
import at least once before
they go ahead with the _real_ conversion ? Or do you just trust cvs2svn ?
RE: [NOTICE] Subversion conversion
Posted by Gerald Richter <ri...@ecos.de>.
>
> Oops, sorry. So you can just use rsync, right?
>
Yes, I can use rsync
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Stas Bekman <st...@stason.org>.
Gerald Richter wrote:
>>Gerald Richter wrote:
>>[...]
>>
>>>I don't need the version history of the website. I never
>>
>>have used it.
>>
>>>The website is anyway auto generated out of the normal Embperl
>>>distribution, so the history is in the embperl repository anyway.
>>
>>So why do you need a repository at all? Just upload your
>>files to where you used to check them out and that's it. Do I
>>miss something?
>>
>
>
> The only thing you missed, is that this is what I suggested in my mail from
> yesterday.
Oops, sorry. So you can just use rsync, right?
> So yes, I need no repository for the website at all. (Of course I need one
> for the embperl code)
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
RE: [NOTICE] Subversion conversion
Posted by Gerald Richter <ri...@ecos.de>.
>
> Gerald Richter wrote:
> [...]
> > I don't need the version history of the website. I never
> have used it.
> > The website is anyway auto generated out of the normal Embperl
> > distribution, so the history is in the embperl repository anyway.
>
> So why do you need a repository at all? Just upload your
> files to where you used to check them out and that's it. Do I
> miss something?
>
The only thing you missed, is that this is what I suggested in my mail from
yesterday.
So yes, I need no repository for the website at all. (Of course I need one
for the embperl code)
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Stas Bekman <st...@stason.org>.
Gerald Richter wrote:
[...]
> I don't need the version history of the website. I never have used it. The
> website is anyway auto generated out of the normal Embperl distribution, so
> the history is in the embperl repository anyway.
So why do you need a repository at all? Just upload your files to where
you used to check them out and that's it. Do I miss something?
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Gerald Richter <ri...@ecos.de>.
Hi,
>
> It would most likely reside in
> http://svn.apache.org/repos/asf/perl/embperl/
> With the standard trunk/ tags/ branches/ under there
>
ok
> >Embperl repository contains two branches (ep1 for Embperl 1 and main
> > branch for Embperl 2). It would be good to preserve them. There are some
> > other old branches, which could/should be deleted during the conversion.
> >
> >Also my time is limited this week, I can help with the conversion (also
> > the mod_perl part) if desired.
>
> I'll take care of the conversion (well infrastructure will do it) unless
> you want it to happen at a later time.
> This will mean the CVS repository will be locked in read-only mode from
> then on. Okay with that ?
>
That's ok. Just do it. I just wanted to offer my help in case it is needed.
> >Since I only use the modperl-site repositotry as transport for the Embperl
> >website, I can change to use scp to copy the content over. I just have to
> >check that I have the correct access rights.
>
> But you don't want to lose version history of all that stuff, don't you?
> If you feel like it, it could
> simply be imported under
> http://svn.apache.org/repos/asf/perl/embperl/site for instance.
>
I don't need the version history of the website. I never have used it. The
website is anyway auto generated out of the normal Embperl distribution, so
the history is in the embperl repository anyway.
From my side you can just delete modperl-site repository.
Regards
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Gerald Richter wrote:
>Hi,
>
>
>
>>>Also worth noting, we should be pigning Gerald to plan
>>>
>>>
>>moving embperl
>>
>>
>>>over to the perl svn repos as well.
>>>
>>>
>
>That would be great. I am using svn all over the place for a long time and
>Embperl is one of the last things where I need to deal with CVS, so I am
>happy to move the Embperl repository to svn.
>
>
It would most likely reside in
http://svn.apache.org/repos/asf/perl/embperl/
With the standard trunk/ tags/ branches/ under there
>Embperl repository contains two branches (ep1 for Embperl 1 and main branch
>for Embperl 2). It would be good to preserve them. There are some other old
>branches, which could/should be deleted during the conversion.
>
>Also my time is limited this week, I can help with the conversion (also the
>mod_perl part) if desired.
>
>
I'll take care of the conversion (well infrastructure will do it) unless
you want it to happen at a later time.
This will mean the CVS repository will be locked in read-only mode from
then on. Okay with that ?
>>in fact the modperl-site repository should not be ported to
>>svn, but instead die. Gerald should move the embperl stuff
>>elsewhere. Gerald, feel free to suggest what you want to do
>>with it. Thanks.
>>
>>
>
>Since I only use the modperl-site repositotry as transport for the Embperl
>website, I can change to use scp to copy the content over. I just have to
>check that I have the correct access rights.
>
>
But you don't want to lose version history of all that stuff, don't you?
If you feel like it, it could
simply be imported under
http://svn.apache.org/repos/asf/perl/embperl/site for instance.
>Gerald
>
>
RE: [NOTICE] Subversion conversion
Posted by Gerald Richter <ri...@ecos.de>.
Hi,
>
> > Also worth noting, we should be pigning Gerald to plan
> moving embperl
> > over to the perl svn repos as well.
>
That would be great. I am using svn all over the place for a long time and
Embperl is one of the last things where I need to deal with CVS, so I am
happy to move the Embperl repository to svn.
Embperl repository contains two branches (ep1 for Embperl 1 and main branch
for Embperl 2). It would be good to preserve them. There are some other old
branches, which could/should be deleted during the conversion.
Also my time is limited this week, I can help with the conversion (also the
mod_perl part) if desired.
> in fact the modperl-site repository should not be ported to
> svn, but instead die. Gerald should move the embperl stuff
> elsewhere. Gerald, feel free to suggest what you want to do
> with it. Thanks.
Since I only use the modperl-site repositotry as transport for the Embperl
website, I can change to use scp to copy the content over. I just have to
check that I have the correct access rights.
Gerald
P.S. Embperl is on the Apache site for a long time (must be about 7 years),
but it has never become a official Apache project. I had some mail exchange
with Doug about this topic (of course this was some time ago) where he said
that it would be possible to make Embperl an official Apache project. We
wanted to talk about this in detail on the ApacheCon two years ago, but he
didn't make it to the conference, so the thread got lost.
I don't know if there were discussions about having Perl subprojects in the
past, maybe it would be worth thinking about it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Stas Bekman <st...@stason.org>.
[adjusting the CC list]
Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>> Geoffrey Young wrote:
>>
>>> [...]
>>>
>>> so, rock on svn.
>>
>>
>> yes, yes, I'm +1. Thanks for taking care of it.
>>
>> Don't forget about preserving the frozen cvs though. I have lots of
>> modified files all over.
>
>
> Yah, the CVS repository will remain for a long time read-only. (don't
> exactly know what *long* means)
>
>> Also we will need to modify some of the sw to work with svn instead of
>> cvs (Makefile(s) and RELEASE notes)
>
>
> Yes, I am here too, so I volountereed to take care of all the work
> required to move us over painlessley. It will include:
>
> Fix external svn linkage for Apache-Test/ and docs/
> Makefile & Release notes.
> Developer documentation
> perl.apache.org cronned building.
gozer++
> Also worth noting, we should be pigning Gerald to plan moving embperl
> over to the perl svn repos as well.
in fact the modperl-site repository should not be ported to svn, but
instead die. Gerald should move the embperl stuff elsewhere. Gerald, feel
free to suggest what you want to do with it. Thanks.
> Oh, and one last thing, the infrastructure people suggested we move the
> content of the perl-core repos to
> commiters/pmc/perl ? Any objections to that as well?
+1
it'd be nice to have a summary of the changes posted as well - in order to
reinitialize the reps, etc.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Geoffrey Young wrote:
>
>> [...]
>>
>> so, rock on svn.
>
> yes, yes, I'm +1. Thanks for taking care of it.
>
> Don't forget about preserving the frozen cvs though. I have lots of
> modified files all over.
Yah, the CVS repository will remain for a long time read-only. (don't
exactly know what *long* means)
> Also we will need to modify some of the sw to work with svn instead of
> cvs (Makefile(s) and RELEASE notes)
Yes, I am here too, so I volountereed to take care of all the work
required to move us over painlessley. It will include:
Fix external svn linkage for Apache-Test/ and docs/
Makefile & Release notes.
Developer documentation
perl.apache.org cronned building.
Also worth noting, we should be pigning Gerald to plan moving embperl
over to the perl svn repos as well.
Oh, and one last thing, the infrastructure people suggested we move the
content of the perl-core repos to
commiters/pmc/perl ? Any objections to that as well?
Re: [NOTICE] Subversion conversion
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Geoffrey Young wrote:
>
>> [...]
>>
>> so, rock on svn.
>
> yes, yes, I'm +1. Thanks for taking care of it.
>
> Don't forget about preserving the frozen cvs though. I have lots of
> modified files all over.
Yah, the CVS repository will remain for a long time read-only. (don't
exactly know what *long* means)
> Also we will need to modify some of the sw to work with svn instead of
> cvs (Makefile(s) and RELEASE notes)
Yes, I am here too, so I volountereed to take care of all the work
required to move us over painlessley. It will include:
Fix external svn linkage for Apache-Test/ and docs/
Makefile & Release notes.
Developer documentation
perl.apache.org cronned building.
Also worth noting, we should be pigning Gerald to plan moving embperl
over to the perl svn repos as well.
Oh, and one last thing, the infrastructure people suggested we move the
content of the perl-core repos to
commiters/pmc/perl ? Any objections to that as well?
Re: [NOTICE] Subversion conversion
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Geoffrey Young wrote:
>
>> [...]
>>
>> so, rock on svn.
>
> yes, yes, I'm +1. Thanks for taking care of it.
>
> Don't forget about preserving the frozen cvs though. I have lots of
> modified files all over.
Yah, the CVS repository will remain for a long time read-only. (don't
exactly know what *long* means)
> Also we will need to modify some of the sw to work with svn instead of
> cvs (Makefile(s) and RELEASE notes)
Yes, I am here too, so I volountereed to take care of all the work
required to move us over painlessley. It will include:
Fix external svn linkage for Apache-Test/ and docs/
Makefile & Release notes.
Developer documentation
perl.apache.org cronned building.
Also worth noting, we should be pigning Gerald to plan moving embperl
over to the perl svn repos as well.
Oh, and one last thing, the infrastructure people suggested we move the
content of the perl-core repos to
commiters/pmc/perl ? Any objections to that as well?
Re: [NOTICE] Subversion conversion
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>>It's just that someone needs to simultaneously move modperl-2.0 to
>>subversion too. And modperl-docs too, since they are checked out into
>>modperl-2.0 check out. As long as this is all done at once there should
>>be no problem. None of these projects had any branching so it shouldn't
>>be a problem. But I've next to zero experience with subversion, so I'm
>>not volunteering to do that.
>
>
> gozer and I can take care of this while we're here. I was waiting on you to
> agree with the move before we went forward, though. and it looks like your +1.
>
> ok, so we're giving sander and justin the ok to lock down cvs until the svn
> conversion is complete, which may be a day or two. after that, everyone
> will need to use svn to access mod_perl cvs (with instructions to follow).
>
> so, rock on svn.
yes, yes, I'm +1. Thanks for taking care of it.
Don't forget about preserving the frozen cvs though. I have lots of
modified files all over.
Also we will need to modify some of the sw to work with svn instead of cvs
(Makefile(s) and RELEASE notes)
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [NOTICE] Subversion conversion
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>>It's just that someone needs to simultaneously move modperl-2.0 to
>>subversion too. And modperl-docs too, since they are checked out into
>>modperl-2.0 check out. As long as this is all done at once there should
>>be no problem. None of these projects had any branching so it shouldn't
>>be a problem. But I've next to zero experience with subversion, so I'm
>>not volunteering to do that.
>
>
> gozer and I can take care of this while we're here. I was waiting on you to
> agree with the move before we went forward, though. and it looks like your +1.
>
> ok, so we're giving sander and justin the ok to lock down cvs until the svn
> conversion is complete, which may be a day or two. after that, everyone
> will need to use svn to access mod_perl cvs (with instructions to follow).
>
> so, rock on svn.
yes, yes, I'm +1. Thanks for taking care of it.
Don't forget about preserving the frozen cvs though. I have lots of
modified files all over.
Also we will need to modify some of the sw to work with svn instead of cvs
(Makefile(s) and RELEASE notes)
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: [NOTICE] Subversion conversion
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>>It's just that someone needs to simultaneously move modperl-2.0 to
>>subversion too. And modperl-docs too, since they are checked out into
>>modperl-2.0 check out. As long as this is all done at once there should
>>be no problem. None of these projects had any branching so it shouldn't
>>be a problem. But I've next to zero experience with subversion, so I'm
>>not volunteering to do that.
>
>
> gozer and I can take care of this while we're here. I was waiting on you to
> agree with the move before we went forward, though. and it looks like your +1.
>
> ok, so we're giving sander and justin the ok to lock down cvs until the svn
> conversion is complete, which may be a day or two. after that, everyone
> will need to use svn to access mod_perl cvs (with instructions to follow).
>
> so, rock on svn.
yes, yes, I'm +1. Thanks for taking care of it.
Don't forget about preserving the frozen cvs though. I have lots of
modified files all over.
Also we will need to modify some of the sw to work with svn instead of cvs
(Makefile(s) and RELEASE notes)
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com