echo “deb http://YOUR_CLOSEST_MIRROR/debian/ wheezy main” > /etc/apt/sources.list.d/testing.list

Put

Package: *
Pin: release a=stable
Pin-priority: 900

Package: *
Pin: release a=testing
Pin-priority: 200

into /etc/apt/preferences

Update

apt-get update

Now install

apt-get install -t testing mono-complete

• Easy to upgrade
• Auto start on boot

Before you start

You may need to tweak commands for the correct versions of Fisheye you have. Mine were as follows…

• Current version of fisheye was 2.5.2.
• Upgrading to 2.5.5
• Moving to separate the application / data directory [by using FISHEYE_INST]

How to

1. Backup fisheye using built-in backup feature

2. Shutdown fisheye

./fecru-2.5.2/bin/stop.sh

3. Create new directories

mkdir -p /opt/fisheye/data

3. Create a user for fisheye

groupadd -g 5000 fisheye
useradd -g fisheye -u 5000 fisheye -d /opt/fisheye -m

4. Move your fisheye installation

mv fecru-2.5.2 /opt/fisheye/

5. Separate out data files

cd /opt/fisheye
cp fecru-2.5.2/config.xml data/
cp -r fecru-2.5.2/var data/
cp -r fecru-2.5.2/cache data/

6. Download latest version

wget http://www.atlassian.com/software/fisheye/downloads/binary/fisheye-2.5.5.zip
unzip fisheye-2.5.5.zip
ln -s fecru-2.5.5 current

The ln command is used so the init.d script doesn’t need to be changed after an upgrade.

7. Install init script

wget http://patrick.qmtech.net/downloads/fisheye
mv fisheye /etc/init.d/
chmod +x /etc/init.d/fisheye
update-rc.d fisheye defaults

8. Make sure file permissions are right

chown -R fisheye:fisheye .

9. Start it up [and watch the log to check for errors]

/etc/init.d/fisheye start
tail -f current/var/log/fisheye.out

Crtl+C to break out of tail

Roundup

So now the following should apply…

• Data in /opt/fisheye/data
• Application in /opt/fisheye/fecru-2.5.5 [symbolic linked to current dir for easy upgrading]
• init script for auto start on boot

https://github.com/firegrass/mono-installer-script

Usage: mono_build.sh [-v version] [-p prefix] [-m gitmodules] [-i] [-s] [-t]

Command line options

  -v   specify version of mono

  -p   specify prefix to install

  -m   specify git modules to build [ libgdiplus llvm mono gtk-sharp xsp mod_mono mono-basic
       mono-addins gtkmozembed-sharp webkit-sharp gluezilla gnome-sharp gnome-desktop-sharp
       mono-tools debugger monodevelop]

  -i   Interactive mode, pause between each modules make and make install. Allows skipping of modules

  -u   Do not update source code, just build

  -b   Do not build, just update source code

  -c   Clean git before building

Example

  mono_build.sh -v 2.6 -p ~/mono -m libgdiplus mono gtk-sharp mono-tools

• Installs Ubuntu dependencies
• Supports 2.6 and trunk builds
• Gets mono from github

Download here http://github.com/firegrass/mono-installer-script/raw/master/mono_parallel.sh

And run…

chmod +x mono_parallel.sh
./mono_parallel.sh 2.6
./mono_parallel.sh trunk

Free feel to fork and improve at github…

http://github.com/firegrass/mono-installer-script

Things I’d like it to do

• Configuration at start (like monodevelop –select) for which modules to build/install
• Manage git branch/checkouts better
• Install MonoDevelop

I have released an updated version which supports mono 2.10 (and previous versions) updated post version

Old article…

UPDATE: I have released an updated version which uses new git repos here

This is a simple work in progress to make the process a bit easier. There are many good reasons not to follow various scripts on the internet that install mono over the top of your packaged distribution install. The fact the Mono 2.6 isn’t released yet is an overriding one because any application depending on mono might stop working, Banshee, Tomboy, F-Spot, etc

At the moment this scripts only supports Mono 2.6 branch + Ubuntu 9.10, see the TODOs! It will install mono into /opt/mono-2.6 and checkout & build in ~/mono-src/mono-2.6. Run it again to update your working copy and rebuild/install.

Please let me know if you like/hate/improve the script

Download script here http://patrick.qmtech.net/downloads/mono_parallel.sh

You will need these packages installed: build-essential automake libtool gettext mono-devel mono-1.0-devel subversion libpng-dev libtiff-dev libgif-dev libjpeg-dev libexif-dev autoconf automake bison flex libcairo2-dev libpango1.0-dev

If you’re looking for more than a DIY script my company QMTech offers commercial support for mono, please contact info@qmtech.net / +44 (0) 161 660 2690 for details.

UPDATE (Thanks Ben): If you’re doing this on a server (no Firefox) you will also need to install: libxul-dev

UPDATE (7/FEB/10): Updated the package requirements

UPDATE (4/MAR/10): Updated the package requirements (added mono-1.0-devel, libcairo2-dev)

UPDATE (20/MAR/10): reworded to reference 2.6 branch not specific 2.6.1

Many of you might be wondering, where are we with Mono and Castle?

These days Mono and Castle work fine together, I use Castle and Mono web stacks in production environments. While there are some issues to be aware of they’re steadily getting ironed out and it’s nothing you can’t live with. Just ask on the Castle mailing lists.

What are we doing?

With the help of the Linux/Mono TeamCity agent, great efforts are being made to get all Castle tests passing on Mono. Failing tests range from simple mismatching line endings to real complex problems, so it’s gonna take some time.

Where are we going?

To increase Castle usage in the Linux world we need to package Castle for various Linux distros.  I am only experienced in packaging for Debian/Ubuntu so I’ll only talk about that. Some of you may or may not know that all Debian packages are built from source and no binaries can be included in a source package. Therefore all dependencies must be packaged first before we can get anywhere near doing Castle. With the recent changes to release schedules and project separation this has been made a lot easier, as we can start with something easier like DP.

I am currently finishing off the debian Nant package upgrade to 0.86-beta, here’s a preview nant_0.86-beta1+dfsg_all.deb. This is needed as 0.85 won’t build Castle because it doesn’t have a mono-3.5 target.

If anyone wants to help just get in touch! That’s it for now!