AUR (en) - 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:	461
Popularity:	1.01
First Submitted:	2011-07-22 14:51 (UTC)
Last Updated:	2024-03-16 18:02 (UTC)

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 305 Next › Last »

graysky commented on 2020-08-21 13:15 (UTC)

5.7.17 introduces some changes that break the ck1 patch. If someone wants to take a look at that and share a solution, that would be good. I am busy at the moment.

enihcam commented on 2020-08-20 23:19 (UTC)

https://ck-hack.blogspot.com/2020/08/more-delays-and-motivation-issues.html

graysky commented on 2020-08-20 17:27 (UTC) (edited on 2020-08-20 17:27 (UTC) by graysky)

Yes, I fucked it up, should be fixed with https://aur.archlinux.org/cgit/aur.git/commit/?h=linux-ck&id=473e18c7ccdec2e641eab76ffcf93e87ff6140a1

You don't need to rebuild unless you have [testing] enabled or have it enabled in a clean build root btw.

Kr1ss commented on 2020-08-20 17:11 (UTC) (edited on 2020-08-20 17:16 (UTC) by Kr1ss)

The recent pkgrel bump broke the validity of the config checksum, @graysky. Could you update that pls ?

Thank you !

air-g4p commented on 2020-08-09 15:18 (UTC) (edited on 2020-08-09 15:25 (UTC) by air-g4p)

@graysky - 5.7.14-1-ck compiled and installed without issue. Good work, done here!

Kr1ss commented on 2020-08-07 13:02 (UTC)

@graysky I'm running 5.7.14-1-ck right now, built w/ localmodconfig.

Looks fine so far, thx.

graysky commented on 2020-08-07 12:39 (UTC)

I cannot reboot now so can someone verify that 5.7.14-ck1 is working properly for me? A small adjustment to ck1 was required.

mrkline commented on 2020-07-31 01:06 (UTC) (edited on 2020-07-31 01:07 (UTC) by mrkline)

Inexplicably, this I ran into the SHA256 issue on one of my machines but not the other. I diffed the two versions of unfuck-ck1.patch - check it out:

--- unfuck-ck1.patch.works  2020-07-30 18:00:17.955122911 -0700
+++ unfuck-ck1.patch.borked 2020-07-30 18:01:49.000000000 -0700
@@ -8,7 +8,7 @@
  1 file changed, 11 insertions(+)

 diff --git a/kernel/sched/MuQSS.c b/kernel/sched/MuQSS.c
-index 18a9b4a23e44e..c55c158e8b8e4 100644
+index 18a9b4a23e44ea..c55c158e8b8e42 100644
 --- a/kernel/sched/MuQSS.c
 +++ b/kernel/sched/MuQSS.c
 @@ -3246,6 +3246,17 @@ static inline u64 do_task_delta_exec(struct task_struct *p, struct rq *rq)

It seems like https://github.com/ckolivas/linux/commit/0b69e633d6b0b08ae8547dc4099c8c0985019553.patch is inconsistent in how many digits of the Git SHAs it sends.

vltr commented on 2020-07-27 15:27 (UTC)

I think it's just a wild guess (or just my guts), but I think this might be some caching problem when downloading that particular file. Sometimes you might get it from a different server with a different content (even though this is odd, yes), but might explain why sometimes (and how inconsistently) this happens ...

air-g4p commented on 2020-07-27 05:15 (UTC) (edited on 2020-07-27 05:17 (UTC) by air-g4p)

@graysky and @artafinde: Thanks for trying to reproduce on your respective ends.

Inexplicably, the build completed without any PKGBUILD SHA256 modifications on my other laptop, and again running makepkg -sric. I suppose this success is consistent with @artafinde's '50% of the time' finding when running makepkg -sric.

Cheers guys...