[pkg-apparmor] Ubuntu/Debian apparmor package maintenance in bzr
intrigeri
intrigeri at debian.org
Thu Apr 30 09:32:52 UTC 2015
Hi Jamie & Steve!
[disclaimer: I'm a bzr newbie.]
when packaging new AppArmor userspace releases for Debian, I generally
merge Ubuntu's packaging branch in bzr, in order to keep our delta as
small as possible. I'm now looking into packaging 2.9.2. I'm happy
that 2.9.1-0ubuntu4 contains "Partial sync with debian apparmor
package" -- thanks, this will make my job easier :)
Now, there are a few things I don't quite understand and need help
with:
1. Many of the commits in your bzr packaging VCS are done by "Package
Import Robot", and I can't find where the corresponding set of
atomic commits are. Could anyone please enlighten me?
2. You've imported some of the packaging improvements we've done in
Debian, which is good. But as far as I can see, this is not
apparent at the bzr level: I can't find traces of my atomic commits
in your bzr history. Assuming I didn't miss anything: could this
workflow be changed, so that I can more easily check what you add
on top of Debian's packaging, and what Debian's packaging adds on
top of yours? (Ideally, I'd love to be able to do the equivalent of
`git log ubuntu/vivid..debian/experimental' and vice-versa.) E.g.
when I've merged Ubuntu changes up to 2.8.98-0ubuntu2, I did it
with `bzr merge', so if you look at r1526 on the
https://alioth.debian.org/scm/loggerhead/collab-maint/apparmor-experimental
branch, you'll see that this branch's history explicitly embeds
your packaging VCS' history. See what I mean?
Thanks in advance!
Cheers,
--
intrigeri
More information about the pkg-apparmor-team
mailing list