You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Les Hazlewood (JIRA)" <ji...@apache.org> on 2008/07/25 20:29:31 UTC
[jira] Created: (INFRA-1687) Migrate JSecurity from SourceForge SVN
repository to ASF Incubator SVN repository
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.
[jira] Updated: (INFRA-1687) Migrate JSecurity from SourceForge SVN
repository to ASF Incubator SVN repository
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood updated INFRA-1687:
---------------------------------
Priority: Blocker (was: Trivial)
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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629823#action_12629823 ]
Joe Schaefer commented on INFRA-1687:
-------------------------------------
Looks good to me.
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629815#action_12629815 ]
Les Hazlewood commented on INFRA-1687:
--------------------------------------
Hi Joe,
No, we still need to do this, but are waiting until the existing codebase's next final release is made (hopefully this week). Once that is done, we can move forward on this issue.
But I'd like to get some feedback. Is what I explained above (the 31/Jul/08 post) the correct way to prepare what you guys will need? Or is there a different way that you prefer? How has this been done for other existing projects entering the incubator?
Thanks,
Les
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643562#action_12643562 ]
Joe Schaefer commented on INFRA-1687:
-------------------------------------
Here's the load:
https://svn.apache.org/repos/test/joes/jsecurity
I loaded from Peter's dump, so please inspect it carefully
before giving the go-ahead to load it to the main repo.
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Peter Ledbrook (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642797#action_12642797 ]
Peter Ledbrook commented on INFRA-1687:
---------------------------------------
Sorry for the long delay. Two dumps available - take your pick :)
http://people.apache.org/~elecharny/jsecurity.dmp.gz
or
http://people.apache.org/~pledbrook/jsecurity-svn-dump.tar.bz2
The first one was generated by "svnsync"ing the repository and then performing an "svndump".
The second one was created by "rsync"ing the repository and then doing "svndump". The only difference seems to be that the former has a revision 0 while the latter does not.
> 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.
[jira] Closed: (INFRA-1687) Migrate JSecurity from SourceForge SVN
repository to ASF Incubator SVN repository
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer closed INFRA-1687.
-------------------------------
Resolution: Fixed
Done.
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629808#action_12629808 ]
Joe Schaefer commented on INFRA-1687:
-------------------------------------
Does this still need doing or have you decided
not to seed the repo with an svn dump?
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618690#action_12618690 ]
Les Hazlewood commented on INFRA-1687:
--------------------------------------
Ok, this is what I'll do (just outlining for clarity's sake):
1. Run 'svnadmin dump'
2. Take the resulting file and make a tarball of it
3. Attach the tarball's URL to this issue
4. You (or someone else from Infrastructure) will download the tarball and import it into the ASF repo.
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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642799#action_12642799 ]
Emmanuel Lecharny commented on INFRA-1687:
------------------------------------------
After having done a diff on both dumps, there are also other differences in the middle, but I have no idea what they are about (the diff is 3520 lines long ..., differences start at line 159 105).
I don't know, but I think that Peter's dump might be more reliable than mine.
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617808#action_12617808 ]
Les Hazlewood commented on INFRA-1687:
--------------------------------------
When you begin this process, could you please indicate that it is being worked on actively? I.e. the 'start work' link in Jira? Or even a comment would suffice since I'm watching the issue.
I've done a few incremental commits (very infrequent) since opening this issue and I just want to ensure that I won't commit when work starts on it.
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Joe Schaefer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618678#action_12618678 ]
Joe Schaefer commented on INFRA-1687:
-------------------------------------
We need a dump of the repo. The process is for us to
take the dump file from some url you provide, add the
dump to our test repo to see what it does, and then
load it to the incubator repo after everything checks out.
> 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.
[jira] Issue Comment Edited: (INFRA-1687) Migrate JSecurity from
SourceForge SVN repository to ASF Incubator SVN repository
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617014#action_12617014 ]
Alan Cabrera commented on INFRA-1687:
-------------------------------------
Just a heads up. The userids in the SourceForge repo will not match the ASF user ids.
> 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.
[jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge
SVN repository to ASF Incubator SVN repository
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643986#action_12643986 ]
Emmanuel Lecharny commented on INFRA-1687:
------------------------------------------
Hi Joe,
the import has been checked, it seems correct.
So go ahead, let's move it to the real place : Make History ;)
Many 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.
[jira] Updated: (INFRA-1687) Migrate JSecurity from SourceForge SVN
repository to ASF Incubator SVN repository
Posted by "Les Hazlewood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Les Hazlewood updated INFRA-1687:
---------------------------------
Priority: Trivial (was: Blocker)
Please don't do this yet - the IPMC is still discussing exactly how this should happen. I'll change the priority back when the discussion is finalized. 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: Trivial
>
> 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.