Excerpts from Serge Hallyn's message of Wed Oct 19 18:38:35 UTC 2011: > Hi Clint, > > is it really valid to require an upstart job for package X to check that > other scripts installed by package X are in fact installed? > > If so this is trivial to add, but it seems over the top to worry about > the upstart job failing (with no further ill effects on the host, IIUC) > if the package is in a bad state. Put another way, you say the upstart > job should 'exit gracefully', but really the upstart job should fail > under this condition! >
Its required by policy. Upstart jobs are conffiles, and so are not removed until a package is *purged*.. even though the binaries are. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/875525 Title: cgroup-bin upstart job does not handle the package being removed but not purged properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/875525/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
