Thursday, June 21, 2012

SVN: Upgrade Interupted

I finally got my computer upgrade today. Nothing spectacular, a 64Bit Win7 Dell. But it doubled my ram, which was becoming a necessity. Oh the pains of a new system. I spent my entire time before lunch just downloading, installing, configuring. Feels like such a waste. But at the end of the day, I'm back in business and I even got to exchange 2 4x3 monitors in my setup for a new 16x9.

In the process of configuring everything I ended up downloading the latest version of syntevo's SmartSVN client. This is a pretty baller SVN client. Everything is nice and visual, information always at a glance. I couldn't work without it. However it forces the working copy upgrade from 1.6 to 1.7. I'm sure this has it's advantages, but just means more time waiting for me. And then the I made the embarrassing mistake of kicking the button on my power strip. If you've ever interrupted an SVN process, you know I'm in for a world of hurt. I get booted back up, and fire up SmartSVN again. I'm again prompted that I have to upgrade, but now the process errors out.

svn:E200030: Table "REPOSITORY" exists already

As somewhat of a newbie to SVN I have no idea what to do here. So I go where any intrepid developer goes, and post a question on Stack Overflow. Before I even get a response I decided to give slikSVN a crack at doing the upgrade. Slik is happily chewing away at upgrading my working copy. So either a failure in one client will not block other clients, or, as I'm sure the command-line purists will claim, slikSVN is a better client. 

In my opinion, for our rather large repo, I don't see a command-line client working out. SmartSVN does background status pulls and gives me visuals on when things change. That is well worth any possible issues with a GUI system. But It's nice to have a command-line as a back up.

After the fact, I get a response on Stack Overflow that I just need to delete anything in my .svn/tmp folder and SmartSVN should be able to then do the upgrade. I almost wish slik hadn't fixed the issue so I could test out if that works or not.

No comments:

Post a Comment