apparmor python3.5 support regressed in 2.10-0ubuntu1

[Steve Langasek]

The apparmor 2.10-0ubuntu1 package that has been uploaded to wily-proposed build-depends on python3-all-dev. However, unlike version 2.9.2-0ubuntu2 in wily, this new version fails to provide a python3-libapparmor package that's built against both available versions of python3 currently supported in wily.

I don't know if python3-libapparmor needs to support multiple versions of python3, or if it only needs to support the current version. If it does need to support multiple versions, please fix this. If it doesn't, please build-depend on python3-dev instead of python3-all-dev.

Found via the python3 transition tracker: http://people.canonical.com/~ubuntu-archive/transitions/html/python3.3-5.html

[Steve Beattie (sbeattie)]

python3-libapparmor does need to support multiple versions of python3. The reason the 2.10-0ubuntu1 package didn't get python 3.5 support is that it was built in the ubuntu-security-proposed ppa (https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa) and binary copied over to wily-proposed. The ubuntu-security-proposed ppa does not have the -proposed (or -update) pockets enabled because we build packages for supported releases in that ppa as well that go into the -security pockets of released versions. The version of python3-all-dev that includes the dependency on python3.5-dev has not moved out of wily-proposed, which is why the apparmor build did not pick it up.

The apparmor 2.10-0ubuntu2 package currently in the ubuntu-security-proposed ppa which address the regression that prevented the 2.10-0ubuntu1 from migrating from proposed is also missing python3.5 support for the same reason. However, not doing a binary pocket copy and instead letting it rebuild in wily-proposed should fix that.

[Steve Beattie (sbeattie)]

This was fixed with apparmor 2.10-0ubuntu2 in wily, closing.