Package Details: linux-next-git 20250403.r0.gf0a16f536332-1

Git Clone URL: https://aur.archlinux.org/linux-next-git.git (read-only, click to copy)
Package Base: linux-next-git
Description: The Linux NEXT kernel and modules
Upstream URL: http://www.kernel.org/
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: Nefelim4ag
Maintainer: ptr1337 (gromit)
Last Packager: ptr1337
Votes: 18
Popularity: 0.80
First Submitted: 2014-10-12 19:04 (UTC)
Last Updated: 2025-04-03 17:24 (UTC)

Dependencies (20)

Required by (8)

Sources (5)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 14 Next › Last »

<deleted-account> commented on 2020-12-06 23:36 (UTC)

Looks like upstream has done nothing yet. This error is now also present in linux v5.10-rc7

sir_lucjan commented on 2020-12-06 21:58 (UTC)

@bennebartsch

If this is not a problem, I would ask you to read the previous comments and draw the appropriate conclusion from it.

Thank you.

bennebartsch commented on 2020-12-06 21:55 (UTC)

FAILED unresolved symbol __add_to_page_cache_locked make: *** [Makefile:1168: vmlinux] Error 255 ==> ERROR: A failure occurred in build(). Aborting...

sir_lucjan commented on 2020-12-01 14:50 (UTC)

@ekollof

NOT out-of-date!

This is not a packaging error. Report it in upstream and do not mark a package as out of date.

Bednar commented on 2020-11-26 11:40 (UTC)

Hi @sir_lucjan

Thanks, I resolved the below with a clean build.

Now I am getting this:

FAILED unresolved symbol __add_to_page_cache_locked make: *** [Makefile:1168: vmlinux] Error 255 ==> ERROR: A failure occurred in build(). Aborting...

Anyone else?

sir_lucjan commented on 2020-10-15 19:13 (UTC)

I can not confirm:

$ export LANG=C
$ git cl aur:linux-next-git
Cloning into 'linux-next-git'...
remote: Enumerating objects: 616, done.
remote: Counting objects: 100% (616/616), done.
remote: Compressing objects: 100% (422/422), done.
remote: Total 616 (delta 320), reused 472 (delta 194), pack-reused 0
Receiving objects: 100% (616/616), 463.11 KiB | 1.72 MiB/s, done.
Resolving deltas: 100% (320/320), done.
$ cd linux-next-git
$ mkaurball 
==> Making package: linux-next-git 20201013.r0.gf2fb1afc5730-1 (Thu Oct 15 21:12:25 2020)
==> Retrieving sources...
  -> Downloading 0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4423    0  4423    0     0  13124      0 --:--:-- --:--:-- --:--:-- 13124
  -> Found config
==> Validating source files with sha512sums...
    linux-next ... Skipped
    0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch ... Passed
    config ... Passed
==> Entering fakeroot environment...
==> Creating source package...
  -> Adding PKGBUILD...
  -> Generating .SRCINFO file...
  -> Adding config...
  -> Compressing source package...
==> Leaving fakeroot environment.
==> Source package created: linux-next-git (Thu Oct 15 21:12:29 2020)

Bednar commented on 2020-10-15 15:31 (UTC)

the validity check is failing for the ZEN patch as of today for me

==> Validating source files with sha512sums... linux-next ... Skipped 0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch ... FAILED config ... Passed ==> ERROR: One or more files did not pass the validity check!

ArthurBorsboom commented on 2020-09-23 08:34 (UTC)

@sir_lucjan, good to know that I was wrong, twice.

After searching, I found the 'following vanilla' comment not in the PKGBUILD, but inside the ZEN patch.

"Our default behavior continues to match the vanilla kernel."

Please disregard my incorrect observation. :)

sir_lucjan commented on 2020-09-17 20:25 (UTC) (edited on 2020-09-17 20:32 (UTC) by sir_lucjan)

@ArthurBorsboom

You are wrong."The normal kernel" has it.

https://github.com/archlinux/linux/commits/v5.8.10-arch1

It is used by default.

https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/config#L195

I am trying to make this kernel as consistent as possible with the stock.

In the PKGBUILD it says to follow the vanilla build

Out of curiosity, where did you find it?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 14 Next › Last »