[Pkg-libvirt-maintainers] libvirt + AppArmor in Stretch vs. merged-/usr

intrigeri intrigeri at debian.org
Sat Dec 17 15:17:40 UTC 2016


Hi,

two commits of mine made it into the upstream master branch, but
they're not part of 2.5.0:

  commit a73e7037e5a5f7af94216e2147c6ef675b2323f6
  Author: intrigeri <intrigeri+libvirt at boum.org>
  Date:   Mon Dec 12 10:59:32 2016 +0000
  
      AppArmor: allow QEMU to set_process_name.
      
      https://bugzilla.redhat.com/show_bug.cgi?id=1369281
      
      Acked-by: Christian Ehrhardt <christian.ehrhardt at canonical.co>
  
  commit de79efdeb8558bbdb3677dbcaaebf7c50cb3bab4
  Author: intrigeri <intrigeri at debian.org>
  Date:   Sat Dec 3 18:32:48 2016 +0000
  
      AppArmor policy: support merged-/usr.
      
      Acked-by: Christian Ehrhardt <christian.ehrhardt at canonical.co>

Will Stretch be shipped with an AppArmor newer than 2.5, or should
I prepare a branch that imports these commits in debian/patches/?

Cheers,
-- 
intrigeri



More information about the Pkg-libvirt-maintainers mailing list