There is not a way to 'ignore it if the capability doesn't exist on the
system'. We might be able to adjust the parser, but that might not be
desirable for a number of reasons.
I don't understand how this is happening-- this capability rule should
only exist in 12.10's profile, yet 12.10 kernels have this capability.
Can you describe the test environment?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1058356
Title:
fails to install when kernel does not provide block_suspend capability
Status in “cups” package in Ubuntu:
Incomplete
Bug description:
On our Jenkins builds we're getting a failure to install the cups
package. This seems to be because the apparmor profile looks for
suspend capability but the virtualized builders do not have it. Here
seems to be the relevant log:
AppArmor parser error for /etc/apparmor.d/usr.sbin.cupsd in
/etc/apparmor.d/usr.sbin.cupsd at line 24: Invalid capability block_suspend.
start: Job failed to start
invoke-rc.d: initscript cups, action "start" failed.
dpkg: error processing cups (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
cups
E: Sub-process /usr/bin/dpkg returned an error code (1)
Full log: https://jenkins.qa.ubuntu.com/job/indicator-session-
ci/label=quantal/16/console
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1058356/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
