Will this be fixed for lucid too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/603934
Title:
upstart-job returns SysV-incompatible value for 'start' when job is
already running
--
ubuntu-bugs
As far as I can tell Lucid is not affected by this bug see the following
comment that indicates this was a result of a change in debhelper.
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/707971/comments/5
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- package nfs-common 1:1.2.0-2ubuntu8 failed to install/upgrade: start: Job is
already running: idmapd
+ upstart-job returns SysV-incompatible value for 'start' when job is already
running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: upstart (Ubuntu)
Importance: Low = Critical
** Also affects: upstart (Ubuntu Natty)
Importance: Critical
Status: Triaged
** Changed in: upstart (Ubuntu Natty)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: upstart (Ubuntu Natty)
Milestone:
This bug has become much more urgent due to fixes to the debhelper-
provided maintainer script snippets; now any job which has no associated
pid when in a 'started' state (and there are a few that legitimately
work this way) will fail to upgrade. So we'll be fixing this for natty
alpha-2.
--
** Branch linked: lp:ubuntu/upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/603934
Title:
upstart-job returns SysV-incompatible value for 'start' when job is
already running
--
This bug was fixed in the package upstart - 0.6.7-5
---
upstart (0.6.7-5) natty; urgency=low
* debian/upstart-job: properly handle jobs that are in state 'start/running'
with no PID, by checking only if the goal is 'start'. LP: #603934,
#707971.
-- Steve Langasek
