Update: Confirmed that this process works on svn 1.7.3 and 1.7.4, Works well on Debian Lenny (5.0) so if you have problems and your running Etch (4.0) or older please try and upgrade
At the time of writing Subversion 1.7.x wasn’t in the Debian Apt tree, and as i wanted to use the new HTTPv2 access method i decided to try my hand at building it from source.
I started with a bare bones Debian 6.0.3 box, the only non standard package i installed was ssh.
First off lets let apt-get do all the hard work when it comes to solving the dependencies for building SVN 1.7, we also may as well install Apache2 at this point. I have also added vim as its my text editor of choice for CLI
If you don’t get any errors, Chances everything is installed and configured correctly, you can always use the –version switch on svn or svnadmin to confrim
So its installed, but lets setup a quick and dirty test repo to confrim that apache is working
Config for /etc/apache2/conf.d/svn_test
Restart Apache then you should be good to go
Now browse to http://your_server/svn and you should see a screen similar to the one below
From here you have the worlds most basic SVN server setup, no restrictions or limitations but if your just installing something on your local pc/network this may be enough for you, I plan to follow this up with a post about how i migrated 200gb 300,000+ revision corporate repo from my old 1.6.x server to my new 1.7.1 server
So running my first Citrix XenDesktop 5.5 Deployment, Did the pilot and the design on 5.0 SP1 but when 5.5 came out the first day i saw no reason not to jump straight to 5.5. As i work for a software development company the requirements for developer are quite high so we took some careful consideration when designing the environment as one must when every user us utalising their own Oracle or MS SQL Database plus some JBoss and Eclipse thrown in for good measure.
Long story short we split up the system to a C: and a D: drive for OS and installs respectively, All well and good, nothing in any of the citrix design guides i read saying this wasent possable? XenDesktop just links into VMware and esentially clones the VM right? Wrong! think its best summed up by the one line i got from Citrix support
The Machine Creation Service will always recognise only the first drive, if you require desktops with multiple drives you would work around the MCS by using PVS to stream disks, use partitioning, or manually add disks after MCS has deployed the VM’s.
For all those who use Atlassian Products such as Jira or Confluence, you may or may not be familiar with Crowd now for anyone using Jira and Confluence it can allow you to use your existing user DB for multiple other systems, Personally i use it as a client access database to keep external users out of my AD database wherever possible while allowing internal users to still access these systems with their AD accounts.
With the right plug-in’s you can hook the system into pretty much everything, the most flexible one is the Apache 2 module, personalty i use it mostly as i had endless troubles getting recursive sub group lockups working with the free Apache modules floating around.
If you need to use a proxy, set it now
For Debian just copy and past the commands below, for other Distrobutions you will need to install the equivalent packages
apt-get-yinstall libapache2-mod-perl2 libsoap-lite-perl libdigest-sha1-perl liberror-perl libcache-cache-perl unzip make
Then to download, install and build the required modules the commands below should work.
My Previous post Subversion 1.6 on Debian Lenny has been quite popular! So i thought i should post this next snippet for people, Its the process i used for upgrading my 1.6.1 setup as detailed in the previous post to 1.6.3.
The previous post pulled packages from the experimental branch, This one pulls from the Sid (unstable) branch as it is more up to date then experimental.
Below are the commands i used for a 64bit OS, dont have any 32bit SVN servers lying around anymore so i don’t have a system to work out the require 32bit packages but in theory it should be as simple as changing “amd64” to “i386” in all the URL’s below
Currently the Version of Subversion in Debian Lenny is 1.5.1, there are a few bugs in this that could be show stoppers if you are using a write through proxy setup for your SVN Repo’s as i have. There are two bugs that keep cropping up, one that is solved in 1.5.5, the other in 1.6, however if you want to use debian packages the easiest way i have found to install them is as follows
Update 1: Few people are having problems, this guide assumes your running lenny with the default svn packages already installed, to do this try running the command below to install the latest version from apt (1.5.x as i write this) including the required Apache modules
Update 3:This post was originally just some notes for me on highly critical production servers that all had to be running exactly the same versions and i had to have a very controled upgrade, However google sends a few hundred people here a month! So i thought id include the better general way that has been in the comments for awhile