vcswatch reports that
this package seems to have a new changelog entry (version
2.13-9, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 69be44e5ef31905eb27be0c04c1346061b0cbc78
Author: intrigeri <intrigeri@boum.org>
Date: Sun Aug 5 05:33:32 2018 +0000
Update debian/changelog.
Gbp-Dch: Ignore
commit 6a94ca691addbf2b43162eef301d1ada58c8f052
Author: intrigeri <intrigeri@boum.org>
Date: Sat Aug 4 15:42:04 2018 +0000
GitLab CI: disable reprotest job.
It fails for some reason I don't understand:
https://salsa.debian.org/apparmor-team/apparmor/-/jobs/36377
And it is not super useful anyway:
- so far, since we've fixed all known reproducibility issues,
no new ones have been introduced yet;
- reproducibility is tested (after uploading though) on
https://tests.reproducible-builds.org/.
commit 18a71b467bf8778754f56b27824d1d752231a7fd
Author: intrigeri <intrigeri@boum.org>
Date: Sat Aug 4 13:33:47 2018 +0000
GitLab CI: enable reprotest and piuparts jobs.
It turns out that on Salsa, one simply has to "enable for this project"
one of the existing privileged runners.
commit fdc31053c4d44a4c8710b3b99bd770eea4090dc2
Author: intrigeri <intrigeri@boum.org>
Date: Fri Aug 3 08:35:33 2018 +0000
Update debian/changelog.
Gbp-Dch: Ignore
commit 0c226bfc7f7d13c9b0ef3fb23e82cc8ecf1b47f4
Author: intrigeri <intrigeri@boum.org>
Date: Fri Aug 3 04:39:22 2018 +0000
Add .gitlab-ci.yml, copied from Salsa CI Team's example.
This will build the package and run autopkgtest and Lintian on it. I've not
included the jobs that need a privileged runner (piuparts, reprotest) because
I don't know how to run them on Salsa.
Origin: https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/salsa-ci.yml
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/apparmor.png){kind=link}