Merge lp:~jdstrand/click-apparmor/click-apparmor.lstat into lp:click-apparmor
Status: | Superseded |
---|---|
Proposed branch: | lp:~jdstrand/click-apparmor/click-apparmor.lstat |
Merge into: | lp:click-apparmor |
Diff against target: |
101 lines (+60/-2) 4 files modified
apparmor/click.py (+9/-2) debian/changelog (+9/-0) debian/control (+3/-0) test-clicktool.py (+39/-0) |
To merge this branch: | bzr merge lp:~jdstrand/click-apparmor/click-apparmor.lstat |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Steve Beattie | Pending | ||
Review via email: mp+210725@code.launchpad.net |
This proposal supersedes a proposal from 2014-03-12.
This proposal has been superseded by a proposal from 2014-03-13.
Commit message
regenerate policy if hook symlink is newer than the profile (LP: #1291549)
debian/control: update for CI Train
- Set X-Auto-Uploader to no-rewrite-version
- Set Vcs-Bzr to the new target branch
Description of the change
High priority fix for bug #1291549. In essence, apps that were installed via the store had policy generated using CLICK_DIR=
Checklist:
* Is your branch in sync with latest trunk (e.g. bzr pull lp:click-apparmor -> no changes): yes
* Did you build your software in a clean sbuild/pbuilder chroot or ppa? yes
* Did you build your software in a clean sbuild/pbuilder chroot or ppa on armhf? yes
* Does the package's autopkgtests pass with exit status '0'? yes
* Has your component TestPlan been executed successfully on emulator/supported device? yes
* Has a 5 minute exploratory testing run been executed on emulator/supported device? yes
* If you changed the packaging (debian), did you subscribe a core-dev to this MP? n/a
* What components might get impacted by your changes? none
* Have you requested review by the teams of these owning components? n/a
This change looks correct. Thanks!