svn migration issue

[alextxm]

Hi,

as part of our switch to Plastic, we are migrating our existing svn repo.

Btw, there is something we really can't get through and so we need Codice's help on it.

Suppose you have the following in the svn repo:

from rev.0 to rev.N you have /repo/products/name then the prj got moved in rev.N+1 to /repo/dismissed/name.

We want to import the structure from rev.0 to rev.N in Plastic.

We tried doing so both with the guimporter and the climporter but both of them failed to work as expected:

gui: import /repo/dismissed/name --> only imports from rev.N+1 to HEAD

cli: import /repo/dismissed/name --> only imports from rev.N+1 to HEAD

gui: import /repo/products/name --> "Error: can't connect to repository"

cli: import /repo/products/name --> "Error: can't connect to repository"

we also tried with

cli: import /repo/products/name --startcs=1 --endcs=rev.N

but we always get "Error: can't connect to repository".

As a workaround we are exporting the repo "slice" (0-N) with svnadmin then load it into a new one and import it in Plastic but since we have some more cases as the one described above, is there a more simple way to accomplish such task?

Thank you,

Alessandro

[manu]

Hi alextxm,

the repository location must exist in order to success the check connection.

So, your workaround will fix the problem and we will discuss this behavior for

following releases.

Regards,

Manuel Lucio Dallo.

[alextxm]

Manuel,

the location indeed EXISTS, but not in the rev.1 (in only appears in rev.x where 1<x<N).

IMHO, the importer should resolve the requested path at the specific revision specified by the --startcs=revN argument, making it work as a request to /path/to/repo/folder@revN (i.e.: try a svn list file:///path/to/repo/folder/subfolder@revN with the svn client); it would be really nice to have it implemented in future versions of the Plastic importer.

Btw I understand this problem is caused both by mistakes on our side and by poor design on SVN side :-/

Thanks for your help,

Alessandro

Hi alextxm' date='

the repository location must exist in order to success the check connection.

So, your workaround will fix the problem and we will discuss this behavior for

following releases.

Regards,

Manuel Lucio Dallo.[/quote']

[manu]

Hi alextxm,

i agree with you and we will have to code the @revN change at the repository checks,

then the svn importer will support fully your case.

Regards,

Manuel Lucio Dallo.