Top-posting I have moved SVN down a level to trunk/ and updated the workspace on projects.a.o to use it. Its pubsub seems to be working.
The next set of cronjobs run from midnight to 4am (UTC) so we shall see tomorrow if anything needs to be tweaked. S. On 29 April 2018 at 07:04, sebb <seb...@gmail.com> wrote: > On 26 April 2018 at 01:02, sebb <seb...@gmail.com> wrote: >> Looks like there is a bit more to it. >> >> asf-auth template needs to be updated to give projects_role access to >> the new directory. >> This can be done by adding the new directory name and later dropping >> the old one. > > The asf-auth update has been applied, so the code will be able to > update SVN in the new location. > >> I don't yet know how to update projects-vm safely. >> >> >> On 25 April 2018 at 12:43, Hervé BOUTEMY <herve.bout...@free.fr> wrote: >>> no objection for me: what is important is to keep the machine running the >>> web >>> server synchronized with the change >>> >>> Regards, >>> >>> Hervé >>> >>> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit : >>>> It looks like we need to move the contents of >>>> >>>> https://svn.apache.org/repos/asf/comdev/projects.apache.org >>>> >>>> to >>>> >>>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk >>>> >>>> [No need to do the same for reporter, as it already uses a trunk directory] >>>> >>>> AFAICT this should not affect the projects.a.o site. >>>> The pubsub script that pulls in updates only looks for the >>>> comdev/projects.apache.org prefix. >>>> (As it does for reporter) >>>> >>>> Moving projects to the trunk directory would give it the same layout >>>> as reporter. >>>> It would also allow the use of tags/ and branches/ sibling directories. >>>> >>>> Are there objections to moving projects.a.o down a level? >>>> >>>> On 13 April 2018 at 16:59, Hervé BOUTEMY <herve.bout...@free.fr> wrote: >>>> > Jira issue created: >>>> > https://issues.apache.org/jira/browse/INFRA-16355 >>>> > >>>> > Regards, >>>> > >>>> > Hervé >>>> > >>>> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit : >>>> >> ok, I don't see any remaining objection >>>> >> >>>> >> I'll ask for svn2git read-only Git+GitHub mirrors. >>>> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git >>>> >> repo "comdev-community.apache.org" to match other "comdev-*.apache.org" >>>> >> >>>> >> This will ease people understanding that comdev's site is >>>> >> community.apache.org (and not comdev.apache.org...) >>>> >> >>>> >> Regards, >>>> >> >>>> >> Hervé >>>> >> >>>> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit : >>>> >> > What about creating a Git/GitHub svn2git mirror for >>>> >> > projects.apache.org? >>>> >> > This would be our first Git repo for community/comdev: I don't know >>>> >> > which >>>> >> > prefix we should use... >>>> >> > >>>> >> > Any objection? >>>> >> > >>>> >> > Perhaps we can do the same for the 3 other locations in svn >>>> >> > https://projects.apache.org/project.html?comdev-community_development >>>> >> > >>>> >> > Regards, >>>> >> > >>>> >> > Hervé >>>> >> > >>>> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit : >>>> >> > > Vincent Tuybens created COMDEV-288: >>>> >> > > -------------------------------------- >>>> >> > > >>>> >> > > Summary: Request "Projects Directory" migration to GIT >>>> >> > > >>>> >> > > Key: COMDEV-288 >>>> >> > > URL: >>>> >> > > https://issues.apache.org/jira/browse/COMDEV-288 >>>> >> > > >>>> >> > > Project: Community Development >>>> >> > > >>>> >> > > Issue Type: SVN->GIT Migration >>>> >> > > Components: Projects Tool >>>> >> > > >>>> >> > > Reporter: Vincent Tuybens >>>> >> > > >>>> >> > > Dear all, >>>> >> > > >>>> >> > > is it possible for you to plan SVN to GIT migration for "Projects >>>> >> > > Directory" project ? >>>> >> > > >>>> >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac >>>> >> > > he. >>>> >> > > or >>>> >> > > g/ {color}] >>>> >> > > >>>> >> > > Thank you, >>>> >> > > >>>> >> > > Regards. >>>> >> > > >>>> >> > > >>>> >> > > >>>> >> > > -- >>>> >> > > This message was sent by Atlassian JIRA >>>> >> > > (v7.6.3#76005) >>>> >> > > >>>> >> > > --------------------------------------------------------------------- >>>> >> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>>> >> > > For additional commands, e-mail: dev-h...@community.apache.org >>>> >> > >>>> >> > --------------------------------------------------------------------- >>>> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>>> >> > For additional commands, e-mail: dev-h...@community.apache.org >>>> >> >>>> >> --------------------------------------------------------------------- >>>> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>>> >> For additional commands, e-mail: dev-h...@community.apache.org >>>> > >>>> > --------------------------------------------------------------------- >>>> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>>> > For additional commands, e-mail: dev-h...@community.apache.org >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>>> For additional commands, e-mail: dev-h...@community.apache.org >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
