Archive for the ‘Subversion’ Category

Packing FSFS Repositories in Subversion 1.6

12 March 2009

After Subversion 1.5 introduced sharding to handle repositories with lots of commits more efficiently, 1.6 adds another feature: packing
Here’s an article that explains the why and how: Packing FSFS Repositories

The most important information:

In order to use FSFS packing, you simply need to ensure that target repository has been upgraded to the latest format, and then pack the repository using svnadmin.  Note that repositories do not automatically pack themselves, so for heavily used repositories, you may want to install a cron job or post commit hook to do the packing.  Users can continue to use the repository while it is being packed:

$ svnadmin upgrade repo<br />Repository lock acquired.<br />Please wait; upgrading the repository may take some time...<br /><br />Upgrade completed.<br />$ svnadmin pack repo<br />Packing shard 0...done.<br />Packing shard 1...done.<br />Packing shard 2...done.<br />Packing shard 3...done.<br />Packing shard 4...done.<br />...<br />Packing shard 36...done.<br />$ svnadmin upgrade repoRepository lock acquired.Please wait; upgrading the repository may take some time...

Upgrade completed.$ svnadmin pack repoPacking shard 0...done.Packing shard 1...done.Packing shard 2...done.Packing shard 3...done.Packing shard 4...done....Packing shard 36...done.$lt;br />

Let’s see how this works out with our repo (~ 55000 revisions).


Subversion 1.5 Clients

3 July 2008

Since this Monday, I’ve been using the new Subversion 1.5 clients on two Windows machines: Tortoise SVN, the SVN command line client and the Subclipse 1.4 Eclipse Plugin for Eclipse Ganymede.
I first thought I had encountered a problem with the Subclipse Plugin. When I tried to update a folder / file in a project, the client worked fine. But when I tried to update the project itself (or the top level foldet, so to speak), I got an error (I think I first encountered this on Tuesday.). During the last two days, the problem didn’t occur again.
This may have happened because I only updated parts of my local checked out projects, so they were only partially converted to the new format.
Anyway, I think I’m going to use the new client for other machines as well.

Subversion 1.5 release candidate 8 available

6 June 2008

RC8 has been released, there might be a RC9, but according to this post, Subversion 1.5 will be out soon.

Eclipse Ganymede JEE RC1 released

1 June 2008

The recently released Eclipse Ganymede JEE RC1 packages seem to solve my problem with using M7 and Subversion 1.5.
After installing the Subclipse plugin I had no problems using the workspace that contained subversion projects.

Living on the bleeding edge: Subversion and Eclipse Ganymede

18 May 2008
It seems as if I discovered an incompatibility between the Subversion 1.5 RC and Eclipse Ganymede JEE M7.

I’ve been using the Subversion 1.5 RC / Tortoise SVN on my laptop for over a week now. I have been accessing our company’s Subversion 1.4 repository and my local 1.5 repository with the command line client and Tortoise SVN.

Additionally, I’ve been trying out Eclipse Ganymede. While the “plain” Eclipse M7 worked (and still works) fine with my checked-out projects from our company repository, the now available Eclipse Ganymede JEE M7 crashed, when I try to open the workspace.

In the heapdump file the problem seems to be libapr from the Apache installation coming with Subversion 1.5.

This may be just a local problem on my laptop, but as developers in our company usually use both Tortoise SVN and the command line client, I better investigate this.

Subversion 1.5 coming up

14 May 2008

As the first release candidates for Subversion 1.5 & Tortoise SVN are now available, I decided to give them a try. The new features sound great: We will finally have merge tracking, sparse checkouts look interesting and synchronizing several SVN servers seems promising. And I wanted to give the new Subversion a try to get a feeling for how to best convert our repository at work.

First impressions:

  • Installation of Subversion and TortoiseSVN on my laptop went fine.
  • I’m now using the new Tortoise SVN client for accessing our regular 1.4 repository and my local 1.5 repository.
  • A very nice feature in the Subversion server installation: It already includes a pre-packaged Apache 2.2 web server.