Package Base Details: linux-ck

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 446
Popularity: 3.17
First Submitted: 2011-07-22 14:51
Last Updated: 2021-04-17 10:20

Packages (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

bryanjhv commented on 2021-01-09 02:30

@graysky thanks for the update but... I think it's missing a $ ($pkgbase instead of just pkgbase).

graysky commented on 2021-01-09 02:07

@Distorted - It is undone in the PKGBUILD. Maintaining is easier if I take the Arch config as-is. See https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=linux-ck#n133 and else where in the PKGBUILD other Arch specific calls are commented out.

graysky commented on 2021-01-09 02:03

@bryanjhv - sure, 5.10.5-2

Distorted commented on 2021-01-09 00:32

Why is CONFIG_DEBUG_INFO=y set? It causes builds to use over 10GB in disk space.

bryanjhv commented on 2021-01-08 22:13

@graysky, is there possibility to change _package-headers' depends array using "$pkgbase" instead of fixed 'linux-ck'? I was building for silvermont (changing $pkgbase to linux-ck-silvermont the way some repositories provide it), and didn't notice it until installing linux-ck-silvermont-headers asked me to also install linux-ck instead of linux-ck-silvermont.

bryanjhv commented on 2021-01-08 22:05

Ignoring the error would make things unpredictable. Just remove "-N" option so patch will try to reverse-apply and re-apply.

Kr1ss commented on 2021-01-03 11:14

@LucidComplex That would make it pass though also in situations where the patch itself fails for a different reason. Not sure if that's what you want to achieve.

LucidComplex commented on 2021-01-03 10:47

prepare() fails when patches have already been applied. I suppose you can append a || true to the end of patch commands in prepare() to address this.

Kr1ss commented on 2021-01-02 21:24

@graysky The checksum for config doesn't match in the recent release.

EDIT/ Thank you fixing this so quickly ! :)

graysky commented on 2021-01-02 20:36

My bad... git push didn't respond for some reason.