New Upstart script to deal with CUPS problem (race condition?)

CUPS wasn't *started* by the time karoshi-update ran, resulting in printer
configurations failing to be set. This separates the printing part into two
stages - karoshi-update copies in a list of printers along with their PPDs,
then karoshi-cups runs when CUPS is really started and configures them.
Merge branch 'master' into develop
Remove unneeded copying of Upstart scripts
Logrotate old logs, closes #43
Use post-session workaround for silly PAM
Remove auto-generation of firewall rules
Remove trailing whitespace
Add package to remove-list and prevent unattended upgrades
Fix grep error for retrieving printers
Thunderbird alert change to not show subject
Fix syntax error in Thunderbird configuration, remove unneeded files
Change karoshi-update to run full-time, fix CUPS issue

karoshi-update is now a proper job that runs all the time the system is up.
It also only runs when the system has updated successfully, allowing other
jobs to use the stanza 'started karoshi-update' to detect if the system is
online and connected to the network, and has updated.

Included in this update is a fix for the persistent CUPS issue where CUPS
karoshi-cups will not run if CUPS doesn't start on time/starts too quickly.
That was caused by Upstart being silly - now the dependencies are much
simpler, with karoshi-cups starting when cups and karoshi-update are both
started.
Fuck Upstart for CUPS.

Right, I'm just using a SysV script to start CUPS now. Fuck Upstart and all of
its problems. Enough is enough. Come back when it actually works
Merge branch 'master'

This is the state of Karoshi Client for the Karoshi Server patch 131017-1237