Package Details: linux-next-git 20220808.r0.gca688bff68bc-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: GPL2
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: Nefelim4ag
Maintainer: sir_lucjan
Last Packager: sir_lucjan
Votes: 16
Popularity: 0.013259
First Submitted: 2014-10-12 19:04 (UTC)
Last Updated: 2022-08-08 10:35 (UTC)

Latest Comments

sir_lucjan commented on 2022-01-23 22:03 (UTC)

There is only one patch and it is the Arch Linux patch, from the stock kernel. There is no other patch.

l_archlinux commented on 2022-01-08 22:25 (UTC)

thanks a lot!

sir_lucjan commented on 2022-01-08 19:55 (UTC)

You don't have to change anything. You will always build the latest possible version.

l_archlinux commented on 2022-01-08 19:35 (UTC)

hi, i'm a little inexperienced in this and i was wondering: can i update the kernel to the latest commits just by reinstalling it? or does it need some changes in the PKGBUILD? thanks in advance

sir_lucjan commented on 2021-10-18 08:15 (UTC)

I can not confirm.

lucjan@archlinux $ export LANG=C
lucjan@archlinux $ git cl aur:linux-next-git
Cloning into 'linux-next-git'...
remote: Enumerating objects: 885, done.
remote: Counting objects: 100% (885/885), done.
remote: Compressing objects: 100% (614/614), done.
remote: Total 885 (delta 463), reused 675 (delta 271), pack-reused 0
Receiving objects: 100% (885/885), 689.68 KiB | 2.71 MiB/s, done.
Resolving deltas: 100% (463/463), done.
lucjan@archlinux cd linux-next-git
lucjan@archlinux $ mkaurball 
==> Making package: linux-next-git 20211013.r0.g8006b911c90a-1 (Mon Oct 18 10:13:50 2021)
==> 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  4425  100  4425    0     0  11092      0 --:--:-- --:--:-- --:--:-- 11118
  -> 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 (Mon Oct 18 10:13:54 2021)

CyrIng commented on 2021-10-17 03:17 (UTC) (edited on 2021-10-17 03:17 (UTC) by CyrIng)

==> 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!

sir_lucjan commented on 2021-10-09 17:36 (UTC)

Done, thanks.

gamezelda commented on 2021-10-09 11:20 (UTC)

I'm not entirely sure if requiring resolve_btfids for building external modules was intentional, but yeah, it doesn't hurt to change the PKGBUILD to install the tool to get external modules / DKMS working again.

(BTW, the commit introducing the requirement is the one named "bpf: Enable TCP congestion control kfunc from modules" in case anyone wants to look deeper.)

sir_lucjan commented on 2021-10-08 20:32 (UTC) (edited on 2021-10-08 20:33 (UTC) by sir_lucjan)

@gamezelda

Did I understand correctly that you want me to add this to PKGBUILD?

gamezelda commented on 2021-10-08 20:25 (UTC)

Since recently I've had to add the resolve_btfids tool in order to build external (DKMS) modules:

   # add objtool for external module building and enabled VALIDATION_STACK option
   install -Dt "$builddir/tools/objtool" tools/objtool/objtool
+  install -Dt "$builddir/tools/bpf/resolve_btfids" tools/bpf/resolve_btfids/resolve_btfids

   # add xfs and shmem for aufs building

catman commented on 2021-08-23 04:02 (UTC)

@sir_lucjan

works now. thanks.

sir_lucjan commented on 2021-08-21 18:15 (UTC)

@catman

Could you try now? I've disabled html docs.

catman commented on 2021-08-21 00:58 (UTC)

Sphinx parallel build error: docutils.utils.SystemMessage: /home/catman/linux-next-git/src/linux-next/Documentation/powerpc/associativity.rst:1: (SEVERE/4) Title overline & underline mismatch.

mikoxyz commented on 2021-06-10 07:36 (UTC)

Note: nvidia-dkms fails to build on 210609

Ttz_ztT commented on 2021-01-12 16:45 (UTC) (edited on 2021-01-15 07:14 (UTC) by Ttz_ztT)

@habys : same here. builds fine, doesn't want to boot. with an almost identical entry for /boot (nvme0n1p1 instead) on booting kernel.

dmesg gives lots of "BPF:No data" and "failed to validate module [crc*] BTF: -22" ?

The only difference I see in dmesg is that -next finds a numa node on my ryzen 3xxx now...

Edit: 210115 works.

habys commented on 2021-01-09 16:39 (UTC)

This is building for me. Anyone else having their system die as I can't manage to mount /boot? (wrong fs type, bad option, bad superblock).

From my working kernel I see: /dev/nvme1n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

eggz commented on 2020-12-07 01:46 (UTC)

confirmed for my part (rc7). revert that commit and the (upstream) kernels wil build. Lets hope upstream will wake up to this soon.

sir_lucjan commented on 2020-12-06 23:41 (UTC)

I suspect that this is the culprit.

https://github.com/torvalds/linux/commit/3351b16af4946fff0d46481d155fb91adb28b1

eggz 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?

ArthurBorsboom commented on 2020-09-17 20:20 (UTC)

I'm wondering if the ZEN patch is (still?) needed in this package.

In the PKGBUILD it says to follow the vanilla build. However, neither the regular Arch [linux] kernel has it, nor linux-git.

https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/PKGBUILD https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-git

Might it be outdated?

sir_lucjan commented on 2020-09-12 17:32 (UTC)

Fixed.

gamezelda commented on 2020-09-12 17:20 (UTC)

The sphinx-workaround.patch patch does no longer apply. It looks like it is no longer necessary:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/Documentation/conf.py?id=afde706afde2fea8a1dff84acaedac4f8dfe84b9

sir_lucjan commented on 2020-05-01 11:40 (UTC)

@blacktea

The git package is never out of date. You will always build the latest possible version.

peeweep commented on 2020-01-04 23:38 (UTC) (edited on 2020-01-04 23:45 (UTC) by peeweep)

A patch for nvidia-dkms

https://github.com/peeweep/nvidia-dkms-fix-drm-drmph-not-found

Ref: https://devtalk.nvidia.com/default/topic/1068332

Ref: https://gitlab.com/snippets/1923197

Aaron1011 commented on 2020-01-01 07:58 (UTC)

in1t3r: I'm getting the same DKMS error with the linux-mainline kernel. Looking at the kernel repository, it looks like this error is legitmate: include/drm/drmP.h no longer exists in the latest kernel.

eliminator commented on 2019-12-09 08:38 (UTC) (edited on 2019-12-09 08:39 (UTC) by eliminator)

nvidia-dkms fails to install module on the linux-next-git kernel dkms install nvidia/440.36 -k 5.4.0-next-20191208-1-next-git The error in terminal is: Error! Bad return status for module build on kernel: 5.4.0-next-20191208-1-next-git (x86_64)

And the error inside of the log file is:

/var/lib/dkms/nvidia/440.36/build/nvidia-drm/nvidia-drm-utils.h:30:10: fatal error: drm/drmP.h: No such file or directory
   30 | #include <drm/drmP.h>

I hope it helps if someone confirms the error. Also do I need to use some other nvidia dkms package to be able to build with git version of the linux? Or is it the error that is made during writing the PKGBUILD. To mention I haven't changed a single option in PKBUILD left them default.

nekonoor commented on 2019-10-04 12:29 (UTC) (edited on 2019-10-04 12:30 (UTC) by nekonoor)

running make htmldocs seperately from make bzImage modules in the PKGBUILD solves the issue. I couldn't find the bugzilla for linux-next and I'm not sure where I should report it.

sir_lucjan commented on 2019-10-04 12:07 (UTC)

This error is unlikely to be related to PKGBUILD. Report the bug on bugzilla and if necessary I will disable htmldocs.

nekonoor commented on 2019-10-04 12:02 (UTC)

20191003 and 20191004 both fail to build for me when i have anything other than -j1 set in /etc/makepkg.conf, 20190930 built just fine using -j16

log with -j2: https://clbin.com/32ZNK

if i run make without htmldocs it builds just fine

sir_lucjan commented on 2018-12-24 12:56 (UTC)

Please try with another commit.

pagdot commented on 2018-12-24 08:42 (UTC) (edited on 2018-12-24 08:43 (UTC) by pagdot)

I get linker errors when trying to compile it on my machine:

ld: drivers/nvdimm/security.o: in function `nvdimm_request_key':
security.c:(.text+0x46): undefined reference to `key_type_encrypted'
ld: drivers/nvdimm/security.o: in function `nvdimm_lookup_user_key.isra.2':
security.c:(.text+0x134): undefined reference to `key_type_encrypted'
make: *** [Makefile:1038: vmlinux] Error 1

sir_lucjan commented on 2018-06-11 20:39 (UTC)

@Raansu

I've updated :)

Raansu commented on 2018-06-05 10:56 (UTC)

@sir_lucjan I put in a request for this package to be orphaned. If someone gets around to processing my request please take over maintaining this package.

sir_lucjan commented on 2018-05-29 17:40 (UTC)

Done.

https://github.com/sirlucjan/workbench/tree/master/linux-next

  1. Files: https://github.com/sirlucjan/workbench/tree/master/linux-next/linux-next-git

  2. Log #1 (build): https://github.com/sirlucjan/workbench/blob/master/linux-next/LOG%231

  3. Log #2 (install): https://github.com/sirlucjan/workbench/blob/master/linux-next/LOG%232

  4. Log #3 (remove): https://github.com/sirlucjan/workbench/blob/master/linux-next/LOG%233

sir_lucjan commented on 2018-05-29 13:47 (UTC)

I've updated PKGBUILD. I'm going to build and if everything will ok, I'll share my PKGBUILD.

sir_lucjan commented on 2018-05-29 11:10 (UTC)

I can adpot.

Raansu commented on 2018-05-29 09:24 (UTC)

Will this package be updated to include the below fixes?

jwhickman commented on 2017-10-28 21:49 (UTC)

The 'makedepends' for 'xmlto' 'docbook-xsl' can be removed. I modified the dvb config (since I disabled that subsystem) to add an if statement: ---------------- msg "Checking for DVB config to add to kernel headers" if [ -d include/config/dvb/ ]; then msg "DVB config found, adding to kernel headers" mkdir -p "${pkgdir}/usr/lib/modules/${_kernver}/build/include/config/dvb/" cp include/config/dvb/*.h "${pkgdir}/usr/lib/modules/${_kernver}/build/include/config/dvb/" fi

sevkard commented on 2017-09-06 05:24 (UTC) (edited on 2017-09-06 05:27 (UTC) by sevkard)

Previous comments have been helpful in building this package successfully. In case anyone needs a how-to: a)Open the PKGBUILD in your preferred editor. b)Remove change-default-console-loglevel.patch from "source=" and its corresponding "md5sum=" entry. This patch is redundant as you now get to specify a loglevel during config. c)Comment out the "add docbook makefile" part (lines 230-231), otherwise the build will fail at the end because the file is no longer in the tree. I hope this helps you save time and avoid frustration.

parkerlreed commented on 2017-01-20 19:43 (UTC)

It prints a lot of errors because of the redefined DEFAULT_CONSOLE_LOGLEVEL (They actually fixed it upstream it seems) # set DEFAULT_CONSOLE_LOGLEVEL to 4 (same value as the 'quiet' kernel param) # remove this when a Kconfig knob is made available by upstream /* * Default used to be hard-coded at 7, we're now allowing it to be set from * kernel config. */ #define CONSOLE_LOGLEVEL_DEFAULT CONFIG_CONSOLE_LOGLEVEL_DEFAULT extern int console_printk[]; #define console_loglevel (console_printk[0]) #define default_message_loglevel (console_printk[1]) #define minimum_console_loglevel (console_printk[2]) #define default_console_loglevel (console_printk[3]) So the K config exists and this patch is no longer needed.

dequis commented on 2017-01-19 19:25 (UTC)

==> Starting prepare()... patching file include/linux/printk.h patch: **** malformed patch at line 10: Looks like the last revision of this package removed one line from the patch file without updating the @@ part.

Nefelim4ag commented on 2016-12-01 20:37 (UTC) (edited on 2016-12-01 20:37 (UTC) by Nefelim4ag)

@fpqc, i add you maintainer rights to the package %) And i did try modify patch by your suggestion.

fpqc commented on 2016-11-30 05:58 (UTC) (edited on 2016-11-30 05:59 (UTC) by fpqc)

diff --git a/include/linux/printk.h b/include/linux/printk.h index 3472cc6..4b4986e 100644 --- a/include/linux/printk.h +++ b/include/linux/printk.h @@ -50,6 +50,7 @@ static inline const char *printk_skip_headers(const char *buffer) #define CONSOLE_LOGLEVEL_SILENT 0 /* Mum's the word */ #define CONSOLE_LOGLEVEL_MIN 1 /* Minimum loglevel we let people use */ #define CONSOLE_LOGLEVEL_QUIET 4 /* Shhh ..., when booted with "quiet" */ +#define CONSOLE_LOGLEVEL_DEFAULT 4 /* Arch modified loglevel */ #define CONSOLE_LOGLEVEL_DEBUG 10 /* issue debug messages */ #define CONSOLE_LOGLEVEL_MOTORMOUTH 15 /* You can't shut this one up */ That's my modified change-default-console-loglevel. It builds with this but spits out tons of error messages you have to edit the patch to move it somewhere else.

fpqc commented on 2016-11-30 05:41 (UTC)

@nefelim4ag you also need to fix the change-default-console-loglevel patch. It doesn't work right now.

Nefelim4ag commented on 2016-11-29 11:35 (UTC)

@fpqc, you right, i forget to add file to source array.

fpqc commented on 2016-11-28 00:59 (UTC) (edited on 2016-11-28 01:08 (UTC) by fpqc)

@Nefelim4ag It looks like you forgot to include 99-linux.hook as a sourcefile. Also, the patch of printk.h is failing.

Nefelim4ag commented on 2016-11-27 14:07 (UTC)

@fpqc, done

fpqc commented on 2016-11-27 04:53 (UTC)

Hiya, you need to add the new libalpm hook for this kernel.

desaparecido commented on 2016-05-17 10:56 (UTC)

hi, after a successfully build when I install it I have this issue when kernel image is created: $ sudo mkinitcpio -p linux-next-git ==> Building image from preset: /etc/mkinitcpio.d/linux-next-git.preset: 'default' -> -k /boot/vmlinuz-linux-next-git -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-next-git.img ==> Starting build: 4.6.0-next-20160517-1136-ARCH -> Running build hook: [consolefont] -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [filesystems] -> Running build hook: [keyboard] -> Running build hook: [fsck] ==> WARNING: No modules were added to the image. This is probably not what you want. ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-next-git.img ==> Image generation successful the important line is this: "==> WARNING: No modules were added to the image. This is probably not what you want." I have this problem only with this package, when I install linux, o another kernel from repos all works fine, so is not mkinitcpio, filesystem or kmod packaged than are corrupted or missed (in some arch forum usually the solution was to reinstall that packages, but in my case is not that problem) so I don't know if is a problem in the PKGBUILD or in my system, thanks for any tips ;-)

Nefelim4ag commented on 2016-05-09 01:08 (UTC)

@mnovick1988, i use virtualbox-host-dkms without issues

EndlessEden commented on 2016-02-19 06:27 (UTC)

anyone else having issues with no modules being built?

youvegotmoxie commented on 2015-09-21 21:12 (UTC)

Have at it.

Nefelim4ag commented on 2015-09-21 20:16 (UTC)

Hey, i can take ownership of this package =)

youvegotmoxie commented on 2015-09-21 15:21 (UTC)

Anyone interested in taking ownership of this package? I'm not currently using Arch so I can't test this anymore. I'm going to increment pkgver for the next week and then orphan the package if no one is interested.

Nefelim4ag commented on 2015-07-31 00:10 (UTC)

^_^ my favorite package

sir_lucjan commented on 2015-06-10 17:25 (UTC)

Pushed and orphaned.

Nefelim4ag commented on 2014-10-12 19:07 (UTC)

https://aur.archlinux.org/packages/linux-next-git/ Created temporarily, this is a linux-git code with your env var and its cloning into yaourt-build

Nefelim4ag commented on 2014-10-11 23:47 (UTC)

@denspirit, may be you know why yaourt feature DEVELSRCDIR="/var/tmp/yaourt-build" Working for other git packages like linux-git and zsh-git But not work for linux-next package?

denspirit commented on 2014-10-11 19:03 (UTC)

config.* files (as well as PKGBUILD) were mindlessly stolen from linux-git package, and I apologize for that.

Nefelim4ag commented on 2014-10-11 18:40 (UTC)

using env var for config is awesome, thanks. Just a big thanks.

brenton commented on 2014-05-09 00:50 (UTC)

a suggestion to make the PKGBUILD a bit better: pkgver=next.$(date -u +%Y%m%d)

denspirit commented on 2013-11-18 00:40 (UTC)

Linux-next is an experimental kernel branch, so shipping some default configs is slightly impractical, in my humble opinion. Old PKGBUILD did not use any default configs and relied on user. I stole/inherited a PKGBUILD and default kernel configs from linux-git by xduugu, correcting package names where necessary. X.509 crypto-module could not build,possibly due to a code error, so I disabled it in config.x86-64 and config.i686. While I am posting this PKGBUILD, modules are still building, so I will be sure it works only at morning. If something goes wrong, I will update PKGBUILD again.

enunes commented on 2013-11-17 22:18 (UTC)

I agree. There's also linux-git in the AUR which at least is already updated to the newer git PKGBUILD format.

denspirit commented on 2013-11-17 22:17 (UTC)

True. Relying on makepkg new VCS capability is not suitable for large projects due to the deletion of 'src' every time to update. Will be uploaded soon. Sorry for inconvenience.

paraxor commented on 2013-11-17 22:15 (UTC)

Perhaps it would be prudent to redo this package based on core/linux.

enunes commented on 2013-11-17 22:05 (UTC)

This package isn't building with the uploaded PKGBUILD: -> Skipping tree update... sed: can't read scripts/depmod.sh: No such file or directory ==> ERROR: A failure occurred in build(). Aborting... Why isn't the PKGBUILD posted two comments ago uploaded? While at it, using the PKGBUILD from pastebin, may I give a few improvement suggestions: - Why does this package request user interaction? My build stopped at "Press ENTER if you want to build the kernel or CTRL+C to abort". I don't think that question adds any value to the build process. Also this requires me to sit in front of my PC when building this (one can't build it automatically or just run makepkg and go grab coffee). - This PKGBUILD could be updated to meet the VCS PKGBUILD Guidelines, there's a template for git packages at: https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines#A_sample_Git_PKGBUILD the prepare() PKGBUILD function could be used to do the rest of stuff in fetch_sources. - This is more questionable but couldn't it just try to borrow the -ARCH config and do oldconfig or zcat /proc/config.gz > .config as fallback instead of failing if I don't provide a .config in the PKGBUILD directory? - In my opinion, mentioning yaourt in the package description is poor practice, that whole second sentence doesn't seem necessary. - namcap throws some warnings: PKGBUILD (linux-next) E: Split PKGBUILD needs additional makedepends ['kmod', 'linux-firmware', 'mkinitcpio'] to work properly PKGBUILD (linux-next) E: File referenced in $startdir PKGBUILD (linux-next) I: Missing Contributor tag PKGBUILD (linux-next) W: Description should not contain the package name.

paraxor commented on 2013-09-12 00:01 (UTC)

@denspirit: Would you like to adopt this package?

denspirit commented on 2013-09-11 22:05 (UTC)

Made this PKGBUILD work in half of a day. Essential variables $_builddir and $_sourcedir contain empty values, because of inexistense of $srcdir and $pkgdir before build() starts. I am posting my edited version of PKGBUILD, but it contains lots of dirty hacks to get everything working by now, and .install and .preset files are unmodified. http://pastebin.com/quHA607j

cpatrick08 commented on 2012-10-11 06:55 (UTC)

in linux-next/src/linux-next/scripts/depmod.sh

ilikenwf commented on 2012-10-11 01:47 (UTC)

Erm...can you look in the source directory and tell me where depmod.sh is, please? The full path relative to $(SRCDIR)

cpatrick08 commented on 2012-10-10 17:18 (UTC)

cant install kernel get following error message -> Skipping tree update... sed: can't read scripts/depmod.sh: No such file or directory

ilikenwf commented on 2012-09-14 08:05 (UTC)

Pretty sure that one was owned, but not updated when I created this one. If a TU wants to delete the other one and rename this one, that's fine.

techlive commented on 2012-08-29 19:24 (UTC)

@ilikenwf This is acctually a git package, thus it should be named as linux-next-git which has already existed in the [aur](https://aur.archlinux.org/packages.php?ID=49614) and been orphaned, why not just pick up and maintain it rather than creating a package which does not follow the Arch Package Naming conventions?

ilikenwf commented on 2012-07-15 02:47 (UTC)

Updated for new layout.

ilikenwf commented on 2012-01-27 00:30 (UTC)

Fixed - now uses kmod.

ilikenwf commented on 2012-01-12 01:22 (UTC)

Bugfix.

ilikenwf commented on 2012-01-10 06:40 (UTC)

And how is it out of date?

ilikenwf commented on 2012-01-07 06:40 (UTC)

This package now supports extramodules and grub2 detection.