You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2008/11/04 00:46:44 UTC
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644853#action_12644853 ]
Emmanuel Lecharny commented on INFRA-1687:
------------------------------------------
Thanks Joe !
> Migrate JSecurity from SourceForge SVN repository to ASF Incubator SVN repository
> ---------------------------------------------------------------------------------
>
> Key: INFRA-1687
> URL: https://issues.apache.org/jira/browse/INFRA-1687
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Subversion
> Reporter: Les Hazlewood
> Priority: Blocker
>
> Hello,
> As part of our entry into the ASF Incubator process, we need to migrate our existing code over from SourceForge. But it is extremely important to retain the previous 4 years worth of commit/revision history in the process.
> After doing some googling, it appears the correct way to do this is to use the 'svnsync' command, which requires some modifications on the ASF side:
> 1. The existing repository mapped to https://svn.apache.org/repos/asf/incubator/jsecurity needs to be blown away entirely and recreated with zero revision history - that is, after 'svnadmin create', don't create the usual trunk, branches and tags directories - see the steps in #2 below.
> Here is the email thread that verifies we've agreed to do this:
> http://jsecurity.markmail.org/search/?q=list:org.apache.incubator.jsecurity-dev#query:list%3Aorg.apache.incubator.jsecurity-dev+page:1+mid:53yhu357qfkuc3fs+state:results
> There is only a trivial amount in our current incubator repository - not a problem for us to recreate what little is there after the migration is complete.
> 2. From what I've seen after researching with google, the following needs to be run:
> $ cd <wherever 'svnadmin create' will be run - should map to https://svn.apache.org/repos/asf/incubator/jsecurity>
> $ svnadmin create jsecurity
> $ svnsync init --username <your_username> https://svn.apache.org/repos/asf/incubator/jsecurity https://jsecurity.svn.sourceforge.net/svnroot/jsecurity
> Copied properties for revision 0.
> $ svnsync sync --username <your_username> https://svn.apache.org/repos/asf/incubator/jsecurity
> Committed revision 1.
> Copied properties for revision 1.
> Committed revision 2.
> Copied properties for revision 2.
> [...]
> I have currently disabled all commit access to our SF SVN server, so there is no fear of inconsistent data, so the above can be run at any time (hopefully sooner than later since our dev team can't do anything until this is complete - hence the 'Blocker' status ;) ).
> Here are the resources I referenced while putting this request together:
> http://groups.google.com/group/google-code-hosting/browse_thread/thread/0efbf53955bedee5/f5c7f47a7687fad2
> http://code.google.com/support/bin/answer.py?answer=56673&topic=10386
> http://journal.paul.querna.org/articles/2006/09/14/using-svnsync/
> Please feel free to contact me at lhazlewood@apache.org with any questions.
> Thanks so much!!!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.