Package Base Details: linux-ck

Git Clone URL: (read-only, click to copy)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 441
Popularity: 2.65
First Submitted: 2011-07-22 14:51
Last Updated: 2020-12-02 18:29

Packages (2)

Latest Comments

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

air-g4p commented on 2020-07-25 07:26

@graysky - I will be the third person to confirm there is a SHA256 error with the unfuck-ck1-fix-suspend-to-ram.patch in PKGBUILD. `makepkg -sric` fails almost immediately due to this SHA256 validation error. In fact, if I comment out the currently existing value that ends in xxx3558 and use: 9ad11f720d4dd83ddb8876b453f4526ad35f1ff72465213764fb1d206fea0379 instead, as vltr originally noted, the build works fine. BTW, that substituted sha256 value I used matches the sha256sum of the unfuck-ck1-fix-suspend-to-ram.patch downloaded by PKGBUILD, which is why the build succeeds.

9ad11f720d4dd83ddb8876b453f4526ad35f1ff72465213764fb1d206fea0379 unfuck-ck1-fix-suspend-to-ram.patch


oldsadsongs commented on 2020-07-23 17:24

@graysky I was able to reproduce @vltr's report by typing 'makepkg -si' instead of 'makepkg' on a fresh git clone.

vltr commented on 2020-07-23 14:54

@graysky that's ODD. I always build after cleaning up the git repository (git clean -dfx) ... and the file had that signature I mentioned (hence my build failed). I cleaned (again), ran makepkg and everything went smoothly this time (with unfuck-ck1-fix-suspend-to-ram.patch signature being, indeed, 961ed94b8d905f1e901cacb08d253c4170af0a25828111b7558d9c874e923558). that's really weird ... sorry about the confusion, whatever it happened.

graysky commented on 2020-07-23 13:22

@vltr - You sure?

% sha256sum unfuck-ck1-fix-suspend-to-ram.patch
961ed94b8d905f1e901cacb08d253c4170af0a25828111b7558d9c874e923558  unfuck-ck1-fix-suspend-to-ram.patch

vltr commented on 2020-07-23 12:53

hi there, @graysky! just one problem with 5.7.10: the unfuck-ck1-fix-suspend-to-ram.patch has a sha256sum of value 961ed94b8d905f1e901cacb08d253c4170af0a25828111b7558d9c874e923558 in the PKGBUILD, which would not pass the validity check since the correct sha256sum should be 9ad11f720d4dd83ddb8876b453f4526ad35f1ff72465213764fb1d206fea0379. apart from that, everything works fine. thanks!

nTia89 commented on 2020-06-12 16:05

Above all, thanks @graysky for the change! Anyway, /tmp defaults to tmpfs with size=50% but not everybody has so much RAM. By my own, this is the biggest mistake behind that choice...

dimosd commented on 2020-06-12 15:23

I suggest that you disable CONFIG_DEBUG_INFO, as it was before 5.7.2. That's what I am doing in my own builds anyway to build with a 4GB /tmp.

artafinde commented on 2020-06-12 12:23

graysky: Got my answer:

artafinde commented on 2020-06-12 10:14

Kr1ss: I think devs would probably reply don't build in tmpfs (and require ~15G of space instead of ~3.5G) but that's a discussion for forums possibly :D - Thanks graysky.

Kr1ss commented on 2020-06-12 09:54

Thx @graysky ! I was only able to build 5.7.2-1 after blowing up /tmp to 20GiB, that's kind of ridiculous. If a user needs debug symbols they can enable them; I think most users wouldn't need'em anyways.

Cheers !