latest apparmor utilities for feisty

[Mathias Gug]

Binary package hint: apparmor

The latest version of apparmor (2.0.1+510.dfsg-0ubuntu6) cannot be installed on feisty, because it requires libc6 (>= 2.5-5). Could it be possible to provide the latest apparmor package for feisty too, in order to increase testing ?

[Kees Cook (kees)]

For doing a stable release update, please follow the process here:
  https://wiki.ubuntu.com/StableReleaseUpdates

If you want to just test locally, you can rebuild under feisty using the following series of commands:

 cd /tmp
 apt-get source apparmor
 sudo apt-get build-dep apparmor
 sudo apt-get install build-essential fakeroot devscripts

 wget http://librarian.launchpad.net/7690794/apparmor_2.0.1%2B510.dfsg-0ubuntu6.dsc
 wget http://librarian.launchpad.net/7690793/apparmor_2.0.1%2B510.dfsg-0ubuntu6.diff.gz

 rm -rf apparmor-*/
 dpkg-source -x apparmor*ubuntu6.dsc
 cd apparmor-*
 debuild -uc -us

The resulting .debs will then be available in /tmp

[Daniel Holbach (dholbach)]

I don't think this is a bug. You might try to ask for a sync to -backports though. Kees: what do you think?

[Mathias Gug (mathiaz)]

On Fri, May 25, 2007 at 08:32:17AM -0000, Daniel Holbach wrote:
> You might try to ask for a sync to -backports though.

The idea behind this bug is how to increase the usage of AppArmor. For now
only people running gutsy can install the latest version of AppArmor. I'd
like to make it simple for people running feisty to test AppArmor.

One strategy could be to provide deb packages for apparmor utilities from a
third party repository (from people.u.c for example). Could -backports be
used to achieved that ?
Also what about providing apparmor-modules-kernel_version for feisty kernels,
so that people don't have to compile the modules themselves ?

[Kees Cook (kees)]

I think -backports is likely the best place to see this done. feisty is already out the door, so testing new AppArmor stuff should be done either with gutsy (where the feedback will have a direct bearing on the next release) or have releases done via -backports, so it doesn't get in the way of regular people's updates. Additionally, keeping a repository on people.u.c for backported-to-feisty packages would work too, since the audience may be relatively small initially.

[Kees Cook (kees)]

Backports of AA utilities into Feisty aren't going to happen. :)