[apparmor] Moving Debian/Ubuntu packaging to Git

[intrigeri]

Hi,

intrigeri:
> I'll try hard to prepare by the end of the year a realistic PoC
> Vcs-Git (with upstream/2.11.x, upstream/2.12.x, debian/stretch,
> debian/master and possibly ubuntu/$something branches). I won't bother
> rewriting history to pretend we've been using this model forever: I'll
> instead focus on setting up the framework I have in mind for our
> _future_ work.

Today I've migrated the Debian packaging history to Debian's shiny new
GitLab instance:

   https://salsa.debian.org/apparmor-team/apparmor

I've imported Ubuntu's "citrain" bzr branch in there at the same time,
so the merging history between our branches were preserved.
Additionally I've imported into the new Git branch (ubuntu/master) the
last two Ubuntu uploads of src:apparmor, that were not pushed to the
citrain branch.

This new Git repository mostly follows DEP-14 namespacing conventions
(http://dep.debian.net/deps/dep14/) so there's room in there for
Debian and derivatives to share one single repository. I'd like us to
do that. If you maintain the AppArmor packaging in a Debian
derivative, I'm happy to give you whatever access you'll need to work
in that repo:

 1. If you're not a Debian developer yet, create an account:
    https://signup.salsa.debian.org/
 2. Request access to the apparmor-team group:
    https://salsa.debian.org/apparmor-team

And if needed:

 - doc: https://wiki.debian.org/Salsa/Doc
 - FAQ: https://wiki.debian.org/Salsa/FAQ
 - ask here

I've then imported the new 2.12 upstream release both in bzr and Git,
built both and confirmed they produce identical packages modulo a few
file timestamps ⇒ uploaded. Yay!

And finally I've added debian/gbp.conf on the ubuntu/master branch,
suitably configured to help get you started :)

Cheers,
-- 
intrigeri