** Branch linked: lp:~ubuntu-dev/quassel/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244036
Title:
Quasselcore should use an Upstart script instead of a sysv initscript
To manage
** Branch linked: lp:ubuntu/trusty-proposed/quassel
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to quassel in Ubuntu.
https://bugs.launchpad.net/bugs/1244036
Title:
Quasselcore should use an Upstart script instead of a sysv initscript
This bug was fixed in the package quassel - 0.9.2-0ubuntu2
---
quassel (0.9.2-0ubuntu2) trusty; urgency=low
* Add quasselcore upstart job. Thanks to Michael Marley. (LP: #1244036)
* Restart quasselcore after upgrades.
* Make quassel-data and quassel-qt4-data conflict as they
** Changed in: quassel (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244036
Title:
Quasselcore should use an Upstart script instead of a sysv
Here is a quassel-core.preinst file that will stop the quasselcore when
upgrading to an Upstart-enabled version so that Upstart may track the
process.
** Attachment added: quassel-core.preinst
I have made an updated version that uses start-stop-daemon in an attempt
to fix the problem that debfx was having with SSL certificates.
** Attachment added: quasselcore.conf
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1244036/+attachment/3901021/+files/quasselcore.conf
--
You
** Changed in: quassel (Ubuntu)
Status: Incomplete = In Progress
** Changed in: quassel (Ubuntu)
Assignee: (unassigned) = Michael Marley (thefirstm)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, here is a new version with most of the suggestions implemented. I
didn't change it to static-network-up though, because based on what I
read about static-network-up, it is only for statically-configured
network interfaces and not ones configured through network-manager.
** Attachment added:
Here is another update with the default values for PORT and LOGLEVEL
added to the Upstart script, as recommended by debfx in #kubuntu-devel.
** Attachment added: quasselcore.conf
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1244036/+attachment/3891150/+files/quasselcore.conf
--
Looks pretty good, but I got a few comments from a developer that knows
way more about upstart than me:
stgraber ScottK: looks to me like he wants start on filesystem and
static-network-up instead, but the start on condition he's using isn' wrong
either. Just because I'm picky, the respawn
10 matches
Mail list logo
