We have performed a manual installation of Airtime 1.8.1. It was installed on Ubuntu 10.04.2 LTS but in a vserver environment. In order to get it working correctly, we tweaked some elements.
The two main elements we needed to customise were:
* Converting daemontools to start via init.d (since vserver will hang with the standard version of daemontools installed)
* Building liquidsoap from source in order to work correctly.
With these two changes in place, Airtime is working perfectly and is stable around 10% CPU usage encoding two streams to icecast.
The question relates to apt upgrades or manual installation upgrades - say for the newly released 1.8.2.
Will an apt upgrade or an upgrading install via the airtime installer replace our customised daemontools changes and liquidsoap binaries?
If so, how best can we revert these changes after an upgrade?
Which of the two (apt vs the manual Airtime upgrade script) would be least disruptive or would have better conflict checking regarding our necessary customisation changes?
Unfortunately upgrading to 1.8.2 via package would install a daemontools instance of liquidsoap (as it is a package dependency). Installing from the tar ball would create files in specific locations for daemontools to read, but if daemontools is not installed and running this shouldnt really affect the system. So you have that route as an option.
As for compiling your own version of liquidsoap, Im not convinced this is actually needed. I have suggested in other threads that users try this, but are you certain Airtime wouldn't run until you compiled your own binary?
In either case, saving the liquidsoap binary is simple: go to /usr/lib/airtime/pypo/bin/liquidsoap and backup the "liquidsoap" binary. After the upgrade restore this file.
BTW this is nothing official, but hopefully we would switch to init.d scripts sometime in the future. Would you be willing to share the ones you made?
In fact daemontools is installed and running correctly, however we had to tweak its initialisation in order to get it working in the vserver VPS. I'll make our init.d approach for its startup available to you.
As for compiling liquidsoap, we had a similar problem as described in other threads here concerning everything seeming to work correctly but no 'On Air' button and no audio being streamed to icecast. When we compiled our own liquidsoap binary and moved it into place, suddenly the system started working correctly.
So it seems in our case, we can preserve our own compiled liquidsoap binary and allow the upgrade to replace everything else without problems.
So it seems in our case, we can preserve our own compiled liquidsoap binary and allow the upgrade to replace everything else without problems.
Yes this appears to be the case Please report back whether the bundled liquidsoap works for you in the next release. 1.8.2-RC is available if you want to test it