Am 07.05.2016 um 14:09 schrieb Andreas Radke:

Am Sat, 7 May 2016 09:15:13 +0000 schrieb Abderrahman Najjar :

...

​The kernel package (linux) is constantly out of date, both in Testing & Core.

Whenever a version is pushed in kernel.org, the previous stable will be still in testing. And then the (old) stable version gets pushed to core, and the next one in testing will be already old (because it's the latest stable). Such as the case right now (Core=4.5.1, testing=4.5.2. Stable on kernel.org=4.5.3)

Is there a reason for such delay? Simply because our main kernel pkg maintainer is busy with real life and so somewhat late with packaging the releases.

-Andy Thanks Andy, yes this is correct. Sorry folks sometimes real life catches you and that's more important. I'm sure all understand this.

greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org

[2016-05-07 20:00:35 +0000] Abderrahman Najjar:

On Sat, May 7, 2016 at 6:24 PM, Tobias Powalowski via arch-general < arch-general@archlinux.org> wrote:

...

Thanks Andy, yes this is correct. Sorry folks sometimes real life catches you and that's more important. I'm sure all understand this.

I appreciate that. But there are two maintainers listed on the package​

It takes time to carefully configure, build and test a quality package. I, for one, am perfectly happy with Tobias taking all the time he needs to make sure we can all depend on this critical piece of software. You are of course free to try and maintain a kernel package yourself, there are numerous options in the AUR too. -- Gaetan

On Sun, 8 May 2016 13:01:31 +0000, Abderrahman Najjar wrote:

​May I ask what are the patches applied? i.e. what's the difference between the package in the repo, and a vanilla source compiled kernel?

[rocketmouse@archlinux ~]$ ls -hAl /var/abs/core/linux total 396K -rw-r--r-- 1 root root 674 May 8 00:06 change-default-console-loglevel.patch -rw-r--r-- 1 root root 181K May 8 00:06 config -rw-r--r-- 1 root root 175K May 8 00:06 config.x86_64 -rw-r--r-- 1 root root 1.2K May 8 00:06 linux.install -rw-r--r-- 1 root root 376 May 8 00:06 linux.preset -rw-r--r-- 1 root root 13K May 8 00:06 PKGBUILD [rocketmouse@archlinux ~]$ grep -i patch /var/abs/core/linux/PKGBUILD "https://www.kernel.org/pub/linux/kernel/v4.x/patch-${pkgver}.xz" "https://www.kernel.org/pub/linux/kernel/v4.x/patch-${pkgver}.sign" 'change-default-console-loglevel.patch') # add upstream patch patch -p1 -i "${srcdir}/patch-${pkgver}" # (relevant patch sent upstream: https://lkml.org/lkml/2011/7/26/227) patch -p1 -i "${srcdir}/change-default-console-loglevel.patch"

On Sun, 8 May 2016 15:18:08 +0200, Bruno Pagani wrote:

It’s about the config flags

One patch is applied. However, for those building their own kernels make localmodconfig might be something that reduces the time needed to build the kernel much and apart from this, it reduces the risk of possible issues. I build kernels myself, but don't use 'make localmodconfig'. [rocketmouse@archlinux ~]$ grep 'Configure the kernel' -A5 /var/abs/core/linux/PKGBUILD # Configure the kernel. Replace the line below with one of your choice. #make menuconfig # CLI menu for configuration #make nconfig # new CLI menu for configuration #make xconfig # X-based configuration #make oldconfig # using old config from previous kernel version # ... or manually edit .config Regards, Ralf