18:02 <Guest53> Hey! Is kiss linux compatible with any of the latest lts kernels?

18:05 <sewn> Guest53: try it and see

18:05 <sewn> kiss doesn't care about your kernel, that's your job to do

18:07 <Guest53> okay thx

18:09 <Guest53> also is it really up to date (security wise i mean), last commit was 3 years ago so i just wondered.

18:10 <sad_plan> kiss doesnt require any specific linux version. so use w/e floats your boat. regarding commits. use codeberg.org/kiss-community

18:10 <sad_plan> dylan araps is on a hiatus, so no updates. the community picked up the slack instead

18:11 <sad_plan> which is what codeberg.org/kiss-community is

18:14 <Guest53> okay, thanks also other question (i'm quite new to building your own system sorry...), this is the main repo : https://github.com/kisslinux/repo and in this repository with all the basic tools like baseinit etc. And in this repo there's the tarball, but where's the source to that? thx in advance

18:15 <Guest53> by the tarball i mean the file u extract in the root of your disk

18:26 <sad_plan> use codeberg.org/kiss-community/repo instead. the one you linked is not active. as I stated. but initially, theyre the same yes

18:27 <sad_plan> you can find a tarball at codeberg repo aswell. which is up to date. more or less anyway. not sure when the latest tarball was released, as I havent checked

18:27 <sad_plan> the source to the tarball, is the repo itself. its built using that repo

18:34 <Guest53> oh yeah mybad wrong link i did check the community, i'm gonna all start from scratch with it. Thanks!

18:49 <sad_plan> np. if youre having trouble figuring out the install, its on kisslinux.org/install

18:49 <sad_plan> unless youd already found that one :p

18:57 <Guest53> yeah found that one 😝

19:01 <Guest53> But now i'm facing a new problem while building menuconfig with kernel 6.76 and 6.6.18 LTS https://imgur.com/a/WZdDXPJ

19:01 <Guest53> any idea why that would happen bc the error output is just nonsense to me

19:01 <sad_plan> please post logs at 0x0.st or similar sites

19:05 <Guest53> there : https://0x0.st/H5ty.png

19:07 <sad_plan> hm. thats not the kiss-chroot is it? try using building it from inside the chroot instead

19:07 <sad_plan> run /mnt/bin/kiss-chroot /mnt

19:07 <sad_plan> this will chroot into the tarball youve extracted. assuming youve already did that

19:11 <sad_plan> oh, wait, its in the chroot. says so on the top. didnt notice that.

19:13 <Guest53> yeah i'm in the kiss-chroot inside the /mnt

19:13 <ukky> old thread on Gentoo forum related to the same error: https://forums.gentoo.org/viewtopic-t-972530-start-0.html

19:13 <Guest53> like the install wiki said

19:15 <Guest53> could it be because i'm in a vm ?

19:16 <sad_plan> hm. its related to ncurses anyhow. could try to rebuild ncurses. sometimes that fixes the issue

19:17 <sad_plan> no, vm or not, shouldnt matter

19:20 <Guest53> could it be because ncurses is built with -O2?

19:22 <Guest53> got this : https://0x0.st/H5tI.png do conflicts affect in any way?

19:22 <Guest53> btw still getting the same error after rebuilding

19:24 <sad_plan> -O2 is just the optimization level for the compiler. it dont matter. its also the recommended one, appart from using -Os instead for size.

19:25 <sad_plan> no, busybox has those iirc

19:25 <sad_plan> clear and reset I mean

19:25 <sad_plan> this is the alternative system in use actualy

19:25 <sad_plan> its a neat system. lets you swap out components of the system

19:25 <sad_plan> as oppposed to just overwrite them

19:26 <Guest53> i should reset everything?

19:28 <sad_plan> no need for that

19:28 <sad_plan> i refered to clear and reset as /usr/bin/reset and /usr/bin/clear, as you shown in the screenshot

19:29 <sad_plan> atm, its provided by busybox, but you can use the alternative system and switch to ncurses as provider instead if you want. its some documentation about it on the kisslinux site

19:33 <Guest53> okay thx i'll try

19:38 <sad_plan> np