Package Details: linux-apparmor 4.20.12.arch1-1

Git Clone URL: https://aur.archlinux.org/linux-apparmor.git (read-only)
Package Base: linux-apparmor
Description: The Linux-apparmor kernel and modules
Upstream URL: https://git.archlinux.org/linux.git/log/?h=v4.20.12-arch1
Licenses: GPL2
Submitter: alzeih
Maintainer: alzeih
Last Packager: alzeih
Votes: 7
Popularity: 0.035038
First Submitted: 2017-12-04 08:02
Last Updated: 2019-02-27 00:23

Latest Comments

1 2 Next › Last »

alzeih commented on 2019-01-19 10:06

@cyrinux good news, CONFIG_PKCS8_PRIVATE_KEY_PARSER=m is set with core/linux's 4.20.arch1-1. linux-apparmor is now at 4.20.3.arch1-1, so it also has this set in the config now too.

cyrinux commented on 2019-01-18 10:47

Hi, @alzeih, Please add CONFIG_PKCS8_PRIVATE_KEY_PARSER=m in config.fragment with update to last 4.20.x

alzeih commented on 2019-01-18 04:03

It seems that no one uses this anymore, as no one has flagged this out of date for a while.

If anyone still wants an update for this kernel, then just click "Flag package out-of-date" and then I might update it.

alzeih commented on 2018-09-20 00:19

@egrupled: Thanks!

I'll keep maintaining this package for those who are using it, as linux-apparmor also sets:

CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 CONFIG_DEFAULT_SECURITY_APPARMOR=y

which core/linux currently does not (people who want selinux would probably not be happy with that).

I encourage everyone who doesn't need this to switch to core/linux and configure your boot loader appropriately, unless you still want to compile your own kernel of course.

egrupled commented on 2018-09-17 18:45

FYI: AppArmor is enabled in Archlinux kernels now: https://wiki.archlinux.org/index.php/AppArmor#Kernel

alzeih commented on 2018-07-14 09:01

@rasmusowl : See https://wiki.archlinux.org/index.php/makepkg#Signature_checking for an explanation.

You could run (as the current user):

gpg --recv-keys ABAF11C65A2970B130ABE3C479BE3E4300411886 647F28654894E3BD457199BE38DBBDC86092693E

More tips at https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key.

rasmusowl commented on 2018-07-14 08:03

Verifying source file signatures with gpg... linux-4.17.tar ... FAILED (unknown public key 79BE3E4300411886) patch-4.17.4 ... FAILED (unknown public key 38DBBDC86092693E) ==> ERROR: One or more PGP signatures could not be verified!

Can some one help me why I'm getting this error

alzeih commented on 2018-06-19 22:25

@renyuneyun A custom repo sounds like a good idea for those who want it. You don’t mention what you are using for automation, but could you parse the .SRCINFO for AUR packages instead of the PKGBUILD? I think this is how the AUR itself handles this problem.

renyuneyun commented on 2018-06-19 09:24

@alzeih Thanks for the clarification. It makes sense. I didn't really carefully read the content of core/linux/PKGBUILD previously (when I manually build kernel for apparmor on my machine).

The reason that I gave this modification is that I'm packaging this package in an automated process (of a custom arch repo), which can leverage the default split package behaviour of makepkg. The automated process doesn't support non-standard split package handling (yet?), so a "correct" PKGBUILD is needed.

Anyway, since this behaviour is inherited from official PKGBUILD and I think it's constant/static, I'll write a script to automatically change the content for the repo.

alzeih commented on 2018-06-13 11:06

@renyuneyun Thanks for the patch! It makes sense given this PKGBUILD, however there are some other considerations.

This PKGBUILD is based upon core/linux's PKGBUILD. It's kept closely based so it's easy for someone to directly compare the two and be satisfied there is nothing unexpected.

The core/linux PKGBUILD allows for the pkgbase to be altered so it's easier for a custom kernel to be installed alongside the stock archlinux kernel. This seems to be why the original PKGBUILD doesn't use the automatic processes in makepkg.

If the split packages were not being generated then this would need fixing. As the split packages are being generated there's no need to fix it at the moment.

I will add back this line to the PKGBUILD:

#pkgbase=linux-custom       # Build kernel with a different name

which should make it clearer why the PKGBUILD is written as it is, and also make it easier to build the split packages with a different pkgbase.