#3991 Issues with the old repo existing checkouts

self-service
nobody
None
2013-05-13
2013-05-10
No

Hello,

After the project was upgraded, the old repository is read-only and developers have to use the new repo for read-write access.

Still, the fact that whoever had old checkouts has to MANUALLY relocate the SVN is very troublesome, especially for a big project who has lots of users, because it is hard to reach out to all the users of such a project.

Is there any way to have the old repo still be read-only, but in the same time keeping it to be automatically in sync with the new repo ? Or perhaps there is some magic that SF can do so that old checkouts automatically move to the new repo, without manual intervention ?

Best Regards,
Vlad

Discussion

  • Rich Bowen

    Rich Bowen - 2013-05-13
    • status: unread --> self-service
     
  • Rich Bowen

    Rich Bowen - 2013-05-13

    Alas, no, developers will need to 'svn relocate' their working copy to continue working. Sometimes, however, depending on the size of the repo, getting a fresh checkout can be faster/easier.

     
  • Vladut-Stefan Paiu

    Hello,

    I'm not talking about the developers, since they will manage by themselves.

    I'm talking about the end users. Imagine a user who has a checkout from the old URL, and that weekly updates his repo so that he makes sure he runs the latest release with the latest bugfixes. He will go do 'svn update' and will get no error message or anything, it'll just say he's at the latest revision, thus he will think that all is ok when in fact it is NOT.

    I don't understand how can Sourceforge do this - change the SVN URLs - and then dump the responsability of telling the users to relocate the SVN to the project admins. Couldn't you - at the very least - trigger an error message from the server when the user tries to update it's old repo, telling him that he needs to relocate ?

    Best Regards,
    Vlad

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks