infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <>
Subject [jira] Commented: (INFRA-1687) Migrate JSecurity from SourceForge SVN repository to ASF Incubator SVN repository
Date Wed, 10 Sep 2008 14:36:44 GMT


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?



> Migrate JSecurity from SourceForge SVN repository to ASF Incubator SVN repository
> ---------------------------------------------------------------------------------
>                 Key: INFRA-1687
>                 URL:
>             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
 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:
> 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>
> $ svnadmin create jsecurity
> $ svnsync init --username <your_username>
> Copied properties for revision 0.
> $ svnsync sync --username <your_username>
> 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:
> Please feel free to contact me at 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.

View raw message