touch-packages team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

In thinking about this a little, it seems that if optimization flags can
be set in parser.conf to change the defaults, then use of '-O' shouldn't
force skipping reading of the cache. Perhaps it would make sense to
apply this patch but also to adjust the man page to state something long
the lines of "if specifying '-O' on the command line, it probably makes
sense to also specify '--skip-read-cache'".

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