Renato.Pinheiro 25 de jun. de 2008
Bom, achei a solução que, apesar de tosca, é a única disponível por enquanto (parece que o pessoal do SVN vai criar um comando para apagar arquivos e diretórios, inclusive tirando o histórico)
Backup your repository.
O backup é feito com o rsync (http://alexandria.wiki.sourceforge.net/Subversion+-+Version+Control+for+Source+Code#backup ), e é necessário porque os comandos não funcionam no work directory
Create a SVN dump file (using svnadmin dump) if you haven’t already done so. Filter anything out of the dump file that isn’t to be imported.
[i][b]Para criar o dump file é simple, dentro do diretório criado no backup citado no item 1, execute o comando svnadmin dump ./
Quanto ao svndumpfilte (http://svnbook.red-bean.com/en/1.4/svn.ref.svnadmin.c.dump.html ), seguem alguns exemplos:
Para filtrar deixando apenas o diretório calc
Para filtrar excluindo o diretório calendas
Compress the dump file, if possible, to save space. We support zip, bzip2 and gzip compression.
Name the file using only alphanumeric characters and a period (Example: svndump.gz – good; projectname-svndump.gz – bad).
Upload the dump file into the root of your project group directory on the shell server (i.e. scp filename.gz [email removido] :/home/groups/P/PR/PROJECTNAME/filename.gz).
Login to the SourceForge.net website.
Go to the project summary page (https://www.sf.net/projects/PROJECTNAME ).
Click on the ‘Admin’ link.
Click on the ‘Subversion’ admin page link.
Click on the ‘migrate’ link on the ‘Migration Instructions’ section of the page.
Key in the filename of the archive into the ‘Source path’ field, noting that it must comply with the filename restrictions previously described.
Check the ‘Replace’ check box in the same column, if you wish to replace the existing content with the new content to be added.
Enter the value you want passed to the --parent-dir argument of the “svnadmin load” command into the ‘Destination’ field. For most users, this would be left blank. Note that the destionation directory must be created but empty for this to work.
Click on the ‘Submit’ button.
The migration will be finished within 24 hours. It could be finished in as soon as an hour or two, depending on the size of your CVS repository and the number of projects queued for migration in front of yours. Returning to the page will display whether it completed, failed or is still in queue.
