> Bug #933973 has been named a duplicate of this one. Not sure why but I
> will post this here as that bug is not confirmed.
It was marked a duplicate in error. Bug #933973 is unrelated to this one.
However, it's also not a bug. Packages that provide services expect to
enable them at install time; in the case of cups and bluez, they do this
using upstart jobs. If you're running Ubuntu in a chroot on Debian, you
don't have upstart running to make this possible.
If you want to avoid packages trying to start services on upgrade inside a
chroot (which is generally advisable anyway), you should configure
/usr/sbin/policy-rc.d to tell invoke-rc.d not to try to start them.
> Bug #933973 has been named a duplicate of this one. Not sure why but I
> will post this here as that bug is not confirmed.
It was marked a duplicate in error. Bug #933973 is unrelated to this one.
However, it's also not a bug. Packages that provide services expect to
enable them at install time; in the case of cups and bluez, they do this
using upstart jobs. If you're running Ubuntu in a chroot on Debian, you
don't have upstart running to make this possible.
If you want to avoid packages trying to start services on upgrade inside a policy- rc.d to tell invoke-rc.d not to try to start them.
chroot (which is generally advisable anyway), you should configure
/usr/sbin/