Description:

Package version was bumped to 2.13.1[0] but it still building from 2.13.0 source.

It happened because when apparmor-2.13.tar.gz is already present in the SRCDEST (cached from previous build) it will match "${pkgname}-${pkgver%.[0-9]}.tar.gz" from PKGBUILD source [1].

If apparmor-2.13.tar.gz is not present in SRCDEST then building package will fail with:

curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading https://launchpad.net/apparmor/2.13/2.13.1/+download/apparmor-2.13.tar.gz

You can also notice that sha512sums didn't change in repo commit.

This is quite important as at the same time 'binmerge' compatibility oatch was dropped from PKGBUILD which means apparmor profiles won't be compatible with Arch anymore.

[0] https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/apparmor&id=90787e655bac3f7f005f283b86adca040c281e53
[1] https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/apparmor#n23


Couple other things regarding package update:

Missing executable bit on apparmor.systemd script was supposedly fixed thus https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/apparmor#n45 can be dropped

Empty RPATH was fixed thus https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/apparmor#n103 (and chrpath dependency) can be dropped too.