www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-5079) SVN Migration from SourceForge to Incubator/ctakes
Date Thu, 13 Sep 2012 08:51:08 GMT

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

#asfinfra IRC Bot commented on INFRA-5079:

<danielsh> I don't know the committer id's were changed -- if it was a sed it might
have modified or corrupted file contents.  (I have some suggestions as to how to verify that
wasn't the case - ping me later if interested)

> SVN Migration from SourceForge to Incubator/ctakes
> --------------------------------------------------
>                 Key: INFRA-5079
>                 URL: https://issues.apache.org/jira/browse/INFRA-5079
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Pei Chen
>            Assignee: Gavin
>            Priority: Minor
> As part of cTAKES entry into the ASF Incubator process, we need to migrate our existing
code over from SourceForge. But we would like to preserve the commit/revision history in the
> Could we perform an svmadmin load of the current dump file located on:
> people.apache.org:/home/chenpei/ohnlp_svndump_20120724_17_50_00.dump.gz (8GB compressed/14GB
> into: https://svn.apache.org/repos/asf/incubator/ctakes/
> - If possible, could we backup/restore the current site directory used by Apache CMS.
> - Otherwise, It is okay to overwrite the current https://svn.apache.org/repos/asf/incubator/ctakes/
repo from the dump file as we have just started the migration.
> - The userids will be different between SourceForge and Apache Id's.  Hopefully, this
won't pose any issues.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message