Debian Package Tracker

general

source: apparmor (main)
version: 2.13.1-3
maintainer: Debian AppArmor Team (archive) [DMD]
uploaders: intrigeri [DMD]
arch: all any
std-ver: 4.2.1
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.7.103-4
oldstable: 2.9.0-3
old-bpo: 2.10.95-4~bpo8+2
stable: 2.11.0-3+deb9u2
testing: 2.13.1-3
unstable: 2.13.1-3

versioned links

2.7.103-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.9.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.10.95-4~bpo8+2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.11.0-3+deb9u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.12-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.13.1-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

apparmor
apparmor-easyprof
apparmor-notify
apparmor-profiles
apparmor-utils
dh-apparmor
libapache2-mod-apparmor
libapparmor-dev
libapparmor-perl
libapparmor1
libpam-apparmor
python3-apparmor
python3-libapparmor

action needed

Multiarch hinter reports 1 issue(s) high

There are issues with the multiarch metadata for this package.

libapparmor-dev conflicts on 10 files starting with /usr/share/man/man on mips64el, mipsel <-> amd64, arm64, armel, and 5 more

Created: 2018-11-03 Last update: 2018-11-19 20:47

1 bug tagged help in the BTS normal

The BTS contains 1 bug tagged help, please consider helping the maintainer in dealing with it.

Created: 2017-08-29 Last update: 2018-11-19 21:05

1 bug tagged patch in the BTS normal

The BTS contains patches fixing 1 bug, consider including or untagging them.

Created: 2018-10-01 Last update: 2018-11-19 21:05

Depends on packages which need a new maintainer normal

The packages that apparmor depends on which need a new maintainer are:

apache2 (#910917)
- Build-Depends: apache2-dev
- Depends: apache2-bin

Created: 2018-10-13 Last update: 2018-11-19 19:00

5 new commits since last upload, time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 2.13.1-4~2.gbp93c6f8, 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 dcd115fda96355cf062094b113b5d1ef797c43b9
Author: intrigeri <intrigeri@boum.org>
Date:   Sun Nov 11 20:21:13 2018 +0000

    Update debian/changelog.
    
    Gbp-Dch: Ignore

commit 93c6f89107329a844dc30c5b60df99a046779ea9
Author: intrigeri <intrigeri@boum.org>
Date:   Sun Nov 11 20:15:42 2018 +0000

    Replace home-made GitLab CI with the standard Salsa pipeline (Closes: #912722).
    
    i.e. https://salsa.debian.org/salsa-ci-team/pipeline/

commit 36ea9960a69fcbed070eecd6a5941e72a5ba49c4
Author: intrigeri <intrigeri@boum.org>
Date:   Sun Nov 4 12:12:18 2018 +0000

    Update debian/changelog.
    
    Gbp-Dch: Ignore

commit 91b966614d656127098b8e21a7b9391612a3f21d
Author: intrigeri <intrigeri@boum.org>
Date:   Sun Nov 4 12:09:45 2018 +0000

    Adjust name of patch that was merged upstream.

commit dfe0036a020f25fa1629aa7540254ca51b02e735
Author: intrigeri <intrigeri@boum.org>
Date:   Tue Oct 30 19:42:41 2018 +0000

    autopkgtest: add dummy test so that changes to linux-image-amd64 trigger our other tests on ci.debian.net

Created: 2018-11-04 Last update: 2018-11-19 14:01

lintian reports 4 warnings normal

Lintian reports 4 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2018-11-06 Last update: 2018-11-06 08:30

1 ignored security issue in jessie low

There is 1 open security issue in jessie.

1 issue skipped by the security teams:

CVE-2017-6507: An issue was discovered in AppArmor before 2.12. Incorrect handling of unknown AppArmor profiles in AppArmor init scripts, upstart jobs, and/or systemd unit files allows an attacker to possibly have increased attack surfaces of processes that were intended to be confined by AppArmor. This is due to the common logic to handle 'restart' operations removing AppArmor profiles that aren't found in the typical filesystem locations, such as /etc/apparmor.d/. Userspace projects that manage their own AppArmor profiles in atypical directories, such as what's done by LXD and Docker, are affected by this flaw in the AppArmor init script logic.

Please fix it.

Created: 2017-03-24 Last update: 2018-11-04 02:15

Build log checks report 1 warning low

Build log checks report 1 warning

Created: 2018-10-21 Last update: 2018-10-21 17:41

news

[rss feed]

[2018-11-04] apparmor 2.13.1-3 MIGRATED to testing (Debian testing watch)
[2018-10-30] Accepted apparmor 2.13.1-3 (source) into unstable (intrigeri)
[2018-10-26] Accepted apparmor 2.13.1-2 (source) into unstable (intrigeri)
[2018-10-23] apparmor 2.13.1-1 MIGRATED to testing (Debian testing watch)
[2018-10-21] Accepted apparmor 2.13.1-1 (source) into unstable (intrigeri)
[2018-08-04] apparmor 2.13-8 MIGRATED to testing (Debian testing watch)
[2018-08-04] apparmor 2.13-8 MIGRATED to testing (Debian testing watch)
[2018-08-02] Accepted apparmor 2.13-8 (source) into unstable (intrigeri)
[2018-08-02] Accepted apparmor 2.13-7 (source) into unstable (intrigeri)
[2018-08-01] apparmor 2.13-6 MIGRATED to testing (Debian testing watch)
[2018-07-30] Accepted apparmor 2.13-6 (source) into unstable (intrigeri)
[2018-07-30] Accepted apparmor 2.13-5 (source) into unstable (intrigeri)
[2018-07-27] Accepted apparmor 2.13-4 (source) into unstable (intrigeri)
[2018-07-26] Accepted apparmor 2.13-3 (source) into unstable (intrigeri)
[2018-07-10] apparmor 2.12-5 MIGRATED to testing (Debian testing watch)
[2018-07-07] Accepted apparmor 2.13-2 (source) into experimental (intrigeri)
[2018-07-07] Accepted apparmor 2.12-5 (source) into unstable (intrigeri)
[2018-06-13] Accepted apparmor 2.13-1 (source) into experimental (intrigeri)
[2018-03-24] apparmor 2.12-4 MIGRATED to testing (Debian testing watch)
[2018-03-18] Accepted apparmor 2.12-4 (source) into unstable (intrigeri)
[2018-03-03] apparmor 2.12-3 MIGRATED to testing (Debian testing watch)
[2018-03-02] Accepted apparmor 2.11.0-3+deb9u2 (source amd64 all) into proposed-updates->stable-new, proposed-updates (intrigeri)
[2018-02-25] Accepted apparmor 2.12-3 (source) into unstable (intrigeri)
[2018-01-29] apparmor 2.12-2 MIGRATED to testing (Debian testing watch)
[2018-01-29] apparmor 2.12-2 MIGRATED to testing (Debian testing watch)
[2018-01-24] Accepted apparmor 2.12-2 (source) into unstable (intrigeri)
[2018-01-20] apparmor 2.12-1 MIGRATED to testing (Debian testing watch)
[2018-01-14] Accepted apparmor 2.12-1 (source) into unstable (intrigeri)
[2017-12-13] apparmor 2.11.1-4 MIGRATED to testing (Debian testing watch)
[2017-12-07] Accepted apparmor 2.11.1-4 (source) into unstable (intrigeri)

bugs [bug history graph]

all: 23
RC: 0
I&N: 5
M&W: 17
F&P: 1
patch: 1
help: 1

links

homepage
lintian (0, 4)
buildd: logs, checks, clang, reproducibility
popcon
debci
browse source code
edit tags
security tracker
screenshots

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.12-4ubuntu10
168 bugs (5 patches)
patches for 2.12-4ubuntu10