asimovc has quit [Remote host closed the connection]
ukky has quit [Quit: rebooting]
ukky has joined #kisslinux
vulpine has quit [Ping timeout: 246 seconds]
fitrh has joined #kisslinux
krjst has quit [Server closed connection]
krjst has joined #kisslinux
vulpine has joined #kisslinux
fitrh has quit [Ping timeout: 256 seconds]
vulpine has quit [Ping timeout: 258 seconds]
vulpine has joined #kisslinux
vulpine has quit [Ping timeout: 245 seconds]
vulpine has joined #kisslinux
phinxy has quit [Ping timeout: 246 seconds]
phinxy has joined #kisslinux
<sewn>
asimovc: uhh
<sewn>
kernel install as $esp/EFI/BOOTX64.EFI
<sewn>
embedded cmdline kernel option
<sewn>
fstab no change, keep root and es
zlg has quit [Ping timeout: 265 seconds]
fultilt has quit [Quit: WeeChat 3.7.1]
sjalv has quit [Ping timeout: 258 seconds]
ElKowar has quit [Server closed connection]
ElKowar has joined #kisslinux
<midfavila>
SkyrixFr: sounds to me like it's a difference in architecture or uarch. even if it's "generic" and both systems are nominally x86, a malformed toolchain or dramatically more modern host can still sometimes have trouble running code on older machines
<midfavila>
at least that's what i've experienced
<midfavila>
what other versions of kiss did you try?
SkyrixFr has joined #kisslinux
<SkyrixFr>
midfavila i just tried on another machine (on virtualbox, on a modern host) the latest tarball, the exact same problem, even on a debian live environement
<midfavila>
hrm
<midfavila>
that's really strange
<SkyrixFr>
and i just tried on this machine the 23.04.30 and it all works
<SkyrixFr>
so the big problem is the latest tarball
<midfavila>
in that case, maybe just install the prior version and upgrade everything
<SkyrixFr>
cuz on either machine, vm not vm, different kernel versions etc. it doesn't work
<SkyrixFr>
yeah i'll do that
<SkyrixFr>
just figured it out, took quite some time :/
<midfavila>
before you do though do a sanity check for your toolchain
<SkyrixFr>
how do i do that?
<midfavila>
just compile a hello world using gcc or something
<SkyrixFr>
okay (y)
<midfavila>
#include <stdio.h>
<SkyrixFr>
the one inside the chroot, or the live enrionement?
<SkyrixFr>
environement*
<midfavila>
int main(int *argc, char **argv){printf("hello\n");}
<midfavila>
chroot
<midfavila>
to make sure you can actually make ELFs that dont go spastic
<midfavila>
otherwise youll end up in a world of fun
<SkyrixFr>
yes! works like a charm
<SkyrixFr>
Thanks for your help!
<SkyrixFr>
and someone maybe should report to phoeb that his tarball has problem and if need be i'm always looking at the logs ;D
<SkyrixFr>
i don't have a clue how to report that kind of problem
SkyrixFr has quit [Quit: Client closed]
SkyrixFr has joined #kisslinux
SkyrixFr has quit [Changing host]
SkyrixFr has joined #kisslinux
SkyrixFr has quit [Quit: Client closed]
vulpine has quit [Quit: Connection reset by purr]
vulpine has joined #kisslinux
sjalv has joined #kisslinux
fultilt has joined #kisslinux
SkyrixFr has joined #kisslinux
SkyrixFr has quit [Client Quit]
Skyrix has joined #kisslinux
Skyrix has quit [Ping timeout: 258 seconds]
SkyrixFr has joined #kisslinux
zlg has joined #kisslinux
geekthattweaks has joined #kisslinux
<SkyrixFr>
Hey, i know it says that it should be the maintainers only that can update the packages but some of them are really getting old (some even have mild CVE's). How do i request a package to be "parked" to maybe become a maintainer? Or can i just do a pull request?
<SkyrixFr>
I mean't orphaned, not parked
<SkyrixFr>
Also why aren't baseinit sources linked to the community sources (like they go all the way to dylan's version, which is 3 years old) but the community sources have been updated recently, so why is that?
<SkyrixFr>
oh didn't say anything (branch pre-changes explains it all)
<sad_plan>
just make a pr for w/e it is you want bumped SkyrixFr
<sad_plan>
some maintainers are slow, myself included.
SkyrixFr has quit [Remote host closed the connection]
avs_origami has joined #kisslinux
avs_origami has quit [Remote host closed the connection]