Hi there, SmartSVN 7.6 will automatically update to SmartSVN 8 once it's released, but it won't automatically upgrade your working copy. SmartSVN 8 will be compatible with Subversion 1.7 and 1.8, so it will be up to you to make the switch once you're ready to do so.
I upgraded to smartsvn 8 and it refuses to work without upgrading the working copy format to 1.8. Since I have svn integration in other software which I cannot upgrade yet, this means I now have to spend the time to downgrade smartsvn. I am not amused.
Hi there, Sorry to hear that, if you don't mind us asking what is it in the build environment that's not compatible? Just asking so we can replicate this for you and see what's going on. You'll be fine committing a 1.8 working copy to a 1.7 server, though from what you've said that's not the problem :/ Cheers, Matt
Incidentally, I've tried several times to download an older version of smartsvn from the website to downgrade back to a version that is compatible with a 1.7 working copy, and have not succeeded (the mail with the download link never arrives for older versions, but it does for the latest version). I am also not able to create a support account to book a ticket, as the validation mail never arrives (my email address is [email]firstname.lastname@example.org[/email]). So, I've basically given up on smartsvn at this point and gone back to tortoise.
Hi, We've had a look and can't see any form records with that email address, though we've tested it with the same address (so if you've received emails that's why) and they've gone through fine. I'll drop you a PM with some links to the older version (7.6.3), not sure which OS it is you're using so we'll send all three, hope that helps. Cheers, Matt
I haven't received any mails, so they must be getting intercepted somewhere. Thanks for the links.
Hi, Your analysis is correct in that you can't use SmartSVN 8, though from what you've said that's not because you're standardised on using Subversion 1.7 (you'll be fine committing a 1.8 working copy to a server running 1.7 or 1.6, which is why the download page continues to state what it does) - it looks like it's the commands in the build scripts you mention that are the incompatibility in this case. Nontheless I'm sorry that the latest version isn't working for you. Cheers, Matt