touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #29296
[Bug 1385947] [NEW] specifying -O to parser causes the parser to not consider cache files
Public bug reported:
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.
** Affects: apparmor
Importance: Medium
Status: Confirmed
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: apparmor (Ubuntu RTM)
Importance: Critical
Status: Confirmed
** Also affects: apparmor (Ubuntu RTM)
Importance: Undecided
Status: New
** Also affects: apparmor
Importance: Undecided
Status: New
** Changed in: apparmor
Status: New => Confirmed
** Changed in: apparmor
Importance: Undecided => Medium
** Changed in: apparmor (Ubuntu RTM)
Status: New => Confirmed
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
** Changed in: apparmor (Ubuntu RTM)
Importance: Undecided => Critical
--
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
Follow ups
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Launchpad Bug Tracker, 2014-10-30
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Launchpad Bug Tracker, 2014-10-29
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Jamie Strandboge, 2014-10-29
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Launchpad Bug Tracker, 2014-10-29
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Jamie Strandboge, 2014-10-28
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: John Johansen, 2014-10-27
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Jamie Strandboge, 2014-10-27
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Jamie Strandboge, 2014-10-27
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: Ubuntu Foundations Team Bug Bot, 2014-10-27
-
[Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
From: John Johansen, 2014-10-26
-
[Bug 1385947] [NEW] specifying -O to parser causes the parser to not consider cache files
From: Jamie Strandboge, 2014-10-26
References