touch-packages team mailing list archive

[John Johansen <john.johansen@xxxxxxxxxxxxx>]

Sticking it the parser.conf also counts as overriding because the set of
flags used during compile are currently not stored (basically anything
different than the default binary behavior is treated as different).

The proper long term fix is to store this information off so that the
parser can detect compile option changes.

-- 
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/1385947

Title:
  specifying -O to parser causes the parser to not consider cache files

Status in AppArmor Linux application security framework:
  Confirmed
Status in “apparmor” package in Ubuntu:
  Confirmed
Status in “apparmor” package in Ubuntu RTM:
  Confirmed

Bug description:
  If the cache files are up to date and I specify:
  /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -- profile1 profile2 ...

  then the cache files in /var/cache/apparmor are used (good).

  However, if the cache files are up to date and I specify:
  /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -O no-expr-simplify -- profile1 profile2 ...

  then the cache files in /var/cache/apparmor are all regenerated (not
  good).  This needs to be fixed in order to use '-O no-expr-simplify'
  to fix bug #1383858.

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