This is not a duplicate of upstart issues.
The issue here is that publication.upstart jobs are installed --noscripts, which prevents them from starting up right after package install.
I'd agree that bug 513722, which is about what the publication job should do, could be solved in a common way with bug 503180. But this one is just an installer failure, not an upstart issue.
This is not a duplicate of upstart issues.
The issue here is that publication.upstart jobs are installed --noscripts, which prevents them from starting up right after package install.
I'd agree that bug 513722, which is about what the publication job should do, could be solved in a common way with bug 503180. But this one is just an installer failure, not an upstart issue.