Hello Tyler, or anyone else affected,

Accepted apparmor into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apparmor (Ubuntu Xenial)
       Status: New => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1628295

Title:
  Change in kernel stacking behavior causes regression tests to fail

Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * Two regression tests fail due to a behavior change in recent Xenial
  and Yakkety kernels

   * Adjusting the regression tests appropriately allows the kernel and
  security teams to use QRT's test-apparmor.py to test kernel and
  userspace AppArmor changes with confidence

  [Test Case]

  $ apt-get source apparmor
  $ cd tests/regression/apparmor
  $ make USE_SYSTEM=1
  $ sudo bash stackonexec.sh
  Error: transition failed. Test 'STACKONEXEC (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'
  Error: transition passed. Test 'STACKONEXEC (stacked with unconfined - bad 
mode)' was expected to 'fail'
  $ sudo bash stackprofile.sh
  Error: transition failed. Test 'STACKPROFILE (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'

  The two previous commands should result in no output and return value of 0 
once
  the regression test is properly updated.

  [Regression Potential]

   * This is an extremely low risk change since it only touches
  regression testing code that is not user-facing.

  [Other Info]

   * This bug has already been fixed upstream:

     https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3505

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628295/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to