touch-packages team mailing list archive

[Ricardo Salveti <rsalveti@xxxxxxxxxxxx>]

Public bug reported:

Currently we're still handling device specific apparmor rules in lxc-
android-config, and the main reason is that we need such rules when
generating the cache for apparmor (which happens when generating the
rootfs).

Moving the rules into the device tarball can cause timestamp issues if
the cache is newer, as apparmor will never update the cache files with
the device specific rules.

** Affects: android (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: lxc-android-config (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Also affects: android (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: lxc-android-config (Ubuntu)
       Status: New => Confirmed

** Changed in: lxc-android-config (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Find a way to move device specific apparmor rules into android/device
  tarball without breaking cache

Status in “android” package in Ubuntu:
  New
Status in “lxc-android-config” package in Ubuntu:
  Confirmed

Bug description:
  Currently we're still handling device specific apparmor rules in lxc-
  android-config, and the main reason is that we need such rules when
  generating the cache for apparmor (which happens when generating the
  rootfs).

  Moving the rules into the device tarball can cause timestamp issues if
  the cache is newer, as apparmor will never update the cache files with
  the device specific rules.

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