www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (INFRA-1687) Migrate JSecurity from SourceForge SVN repository to ASF Incubator SVN repository
Date Sat, 26 Jul 2008 19:06:33 GMT

    [ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617207#action_12617207
] 

lhazlewood edited comment on INFRA-1687 at 7/26/08 12:05 PM:
----------------------------------------------------------------

I'm re-enabling this issue.  Please move forward with it now.

Ultimately, as I'm not too sure how the ASF SVN repo works (revisions, etc), I thought it
better to explain what we're trying to achieve:

We'd like the SVN repo located at   

https://jsecurity.svn.sourceforge.net/svnroot/jsecurity

(with all of its trunk, tags, branches and children) to be copied over to here, including
all revision history, to be accessible here:

https://svn.apache.org/repos/asf/incubator/jsecurity

Note that the SourceForge user IDs do _not_ match our recently created ASF user ids.  I don't
know if this would cause a problem on the Infra side, but I'm assuming it won't (should just
be text ids in the SF repo details)

Given this information, I'm assuming you folks will know the best way to do this - svnsync
vs svnadmin dump/load, etc.  Please feel free to follow up with any questions.

Thanks!

      was (Author: lhazlewood):
    I'm re-enabling this issue.  Please move forward with it now.

Ultimately, as I'm not too sure how the ASF SVN repo works (revisions, etc), this is what
we're trying to achieve:

We'd like the SVN repo located here:  

https://jsecurity.svn.sourceforge.net/svnroot/jsecurity

(with all of its trunk, tags, branches and children) to be copied over to here, including
all revision history, to be accessible here:

https://svn.apache.org/repos/asf/incubator/jsecurity

Note that the SourceForge user IDs do _not_ match our recently created ASF user ids.  I don't
know if this would cause a problem on the Infra side, but I'm assuming it won't (should just
be text ids in the SF repo details)

Given this information, I'm assuming you folks will know the best way to do this - svnsync
vs svnadmin dump/load, etc.  Please feel free to follow up with any questions.

Thanks!
  
> 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.


Mime
View raw message