intrigeri 6ab19ea82f Install pam_apparmor.so with write permission for its owner. ... I could not find the reason why the upstream Makefile has been installing it with permissions 555: this predates the migration from SVN. Regardless, at least on Debian and derivatives, dh_fixperms has been changing these permissions to 755 forever so it was causing problems, likely we would know about it by now. The initial motivation for this change is supporting rootless builds on Debian and derivatives, also known as "Rules-Requires-Root: no": - /usr/share/doc/dpkg-dev/rootless-builds.txt* on a Debian system with a sufficiently recent dpkg-dev installed - https://nthykier.wordpress.com/2017/10/29/building-packages-without-fakeroot/ - https://lists.debian.org/debian-devel/2017/10/msg00520.html With this change applied upstream, Debian-based downstreams don't need to adjust their debian/rules to make this work with "Rules-Requires-Root: no": chrpath -d $(CURDIR)/debian/tmp/lib/security/pam_apparmor.so		2018-01-19 08:22:35 +00:00
..
mod_apparmor	all: Use the MAKE variable	2017-11-01 23:22:53 +00:00
pam_apparmor	Install pam_apparmor.so with write permission for its owner.	2018-01-19 08:22:35 +00:00
tomcat_apparmor	Entire tree: makefile cruft removal	2015-01-23 15:52:09 -08:00