Monthly Archives: February 2011

Additional Steps Installing Ubuntu 10.10 Maverick

Here are some additional things either installing custom software or specific configuration options used in setting up my new system.

A few settings I set with Compiz setup.

  1. I use shutter for a screenshot utility and this will allow it to replace the default gnome-screenshot tool allowing more flexibility and control. I especially like the section and web screenshot options where I can take a shot of the entire contents of a window without any of the controls or of an entire web page without having to stitch them together.Open up the Settings Manager and in Gnome Compatibility on the Commands tab I replace ‘gnome-screenshot’ with ‘shutter –full’ and ‘gnome-screenshot –window’ with ‘shutter –section’ in the first two entries.

    Edit: be sure to have synapse 0.87 installed

    sudo add-apt-repository ppa:shutter/ppa
    sudo apt-get update && sudo apt-get install shutter

I chose to install synapse over gnome-do my usual default launcher, Synapse just seemed like a little more fun this time around.

sudo add-apt-repository ppa:synapse-core/ppa
sudo apt-get update && sudo apt-get install synapse

Some other software I installed as I realized it.

wget http://download.virtualbox.org/virtualbox/4.0.2/virtualbox-4.0_4.0.2-69518~Ubuntu~maverick_i386.de
sudo apt-get install libqt4-network libqt4-opengl
sudo dpkg -i virtualbox-4.0_4.0.2-69518~Ubuntu~maverick_i386.deb

sudo apt-get install apache2 mysql-client mysql-server php5 libapache2-mod-php5
sudo apt-get install banshee
sudo apt-get install subversion
sudo apt-get install sshfs

Subversion file removal

I performed one of my no-no’s today by accidentally adding my wp-config.php file to a svn repo full of database password goodness. That’s not good. Anyways, it’s a simple enough procedure to revert the issue and continue on with your complete repository as it was just without that file and it’s contents.

cd /var/svn
svnadmin dump repository-name > ~/repository-name.dump
svndumpfilter exclude trunk/wp-config.php < ~/repository-name.dump > ~/repository-name.dump-new
mv repository-name repository-name.bak
svnadmin create repository-name
svnadmin load repository-name < ~/repository-name.dump-new

A quick line by line explanation:

I start off by dumping the repository into a dump file (great, we now have a backup, but you were already keeping backups anyways). Then with the svndumpfilter
we exclude the nasty file that you don't want and put that into a new dump file. Remeber that it's relative to the root of the repository so if you put stuff into trunk you need to prepend your file with trunk, also it does not search out that file name recursively, it's directly getting that specific file. Now that I have my new clean dump file I will backup my repository directory just in case I make a mistake and then create a new repository and finally I load that new repository from the new dump file. That's it!

A final note, I did have to checkout my local working copy again after this as it was still under the impression that the wp-config.php file was still versioned. Probably because it wrote that to the local .svn folders and it doesn't check that again in the repo, I'm sure there would be several ways to correct that but this was simple enough to do.