This page explains how to update an AppArmor profile shipped in apparmor-profiles-extra with a newer upstream version.
In short: get the latest version from upstream, test, prepare a Debian patch against apparmor-profiles-extra, submit patch to the BTS or push a Git branch to collab-maint.
Find out more about upstream repositories.
Merge a profile from upstream
Merging a profile update from upstream into the apparmor-profiles-extra Debian package is fairly easy: it only requires basic Git usage skills.
If you want to get write access to the apparmor-profiles-extra package in Debian, you first need to request access to the Collaborative Maintenance Alioth project, 'collab-maint' in short. This also requires setting up an account on Alioth.
Once all is set up, one can export the apparmor-profiles-extra Git repository. If you simply want to submit a patch, it's sufficient to clone this repository anonymously. Otherwise, you need to pass the --auth parameter to debcheckout. The debcheckout command is part of the devscripts package:
debcheckout --auth apparmor-profiles-extra
Go into the apparmor-profiles-extra folder and create a new working branch:
git checkout -b workingtitle
Get the latest version of profiles from upstream. Profiles live in the profiles sub-directory. Some helper scripts in debian/scripts/ can be helpful.
Test the updated profile.
Update the information about the profile you are updating, in debian/README.Debian.
Then, one could either push the branch to collab-maint:
git commit -a git push origin workingtitle
or simply submit a patch to the Debian Bug Tracking System against the apparmor-profiles-extra package.
The Debian AppArmor packaging team mailing list will receive a notification of this commit. This way, commits can be peer-reviewed and then merged by the team.
Inform the team
When creating a new profile, we encourage you to report a bug with the usertag merge-from-upstream to the Debian BTS in order to inform the Debian AppArmor Packaging Team.
Equally, do not hesitate to provide a patch for the bug. You should then also tag the bug with the tag patch.
Find out more about usertags on the AppArmor/Reportbug page.