<elisoli>
is there any body using librewolf? how did you compile it?
<dery>
me elisoli
<dery>
using flatpak :P
<dery>
I don't see why it should be much different from building firefox tho
elisoli has quit [Remote host closed the connection]
sjalv has joined #kisslinux
<dery>
uh, I think I found a bug in the mdev-like-a-boss config we're using
<dery>
`cpu([0-9]+)` matches to nothing on my machine, it's basically ignored
<dery>
busybox mdev (at least) straight up detects and makes `cpu/$ID/cpuid`
<dery>
I wonder if the kernel changed or something
elisoli has joined #kisslinux
<elisoli>
i am not an expert tbh, although i know a lot about programming (im a dev xd) tho i can't understand nothing in that firefox build script
<elisoli>
librewolf when compilng have me weird errors with python packages failing inside rust compilation processes O_o
sjalv has quit [Ping timeout: 240 seconds]
sjalv has joined #kisslinux
<dery>
perhaps they added some other dependency
raph_ael has quit [Ping timeout: 246 seconds]
raph_ael has joined #kisslinux
<midfavila>
got my noctua coolers in
<midfavila>
libreboot claimed am3 coolers would work with the socket c32 mount
<midfavila>
noctua cooler supports am3 officially
<midfavila>
noctua cooler does not mount to the c32 bracket
<midfavila>
noctua *used* to make a secufirm2 kit to allow mounting to c32
<midfavila>
but they no longer make it and i can't find any in the wild
<midfavila>
shoot me
sjalv has quit [Ping timeout: 240 seconds]
sjalv has joined #kisslinux
<kris_>
midfavila: are you using libreboot
<midfavila>
going to be, yes
<kris_>
at some point i really need to look at how their build system works so i can do it myself
<kris_>
not exactly a hot take but i'm not a leah fanatic
<midfavila>
it's whatever
<midfavila>
gonna be returning these coolers i think
<midfavila>
they don't seem compatible in any way shape or form with socket c32
<midfavila>
very disappointed
<dery>
aight news flash
<dery>
busybox mdev is actually very dumb
<kris_>
The Isopod
<dery>
I think it scans devices straight up wrong, according to the kernel docs
<dery>
like, when it does its first scan, a "coldplug" it straight up misses a LOT of devices
<dery>
and it's not like it does not like them, it reports their events fine
<dery>
case in point, backlight stuff
<dery>
mdevd works correctly
<dery>
so uh, I might *need* to switch to it if I want something "correct". Either that, or I need to resort to hacks like I always did to achieve what I want (user writable backlight devices and such)
sjalv has quit [Read error: Connection reset by peer]
<kris_>
dery: you're more pure than me
<kris_>
i use udev
<dery>
that's perfectly fair tbh
<dery>
like, the apis are dirty down there fr
<kris_>
really i use it because i'm too lazy to not
<dery>
I find it really satisfying to bang my head at this stuff tho
<kris_>
its kinda baked into one of voids core services, i could fix this pretty easily but im lazy
<dery>
yea it's really no biggie
<dery>
especially as then certain software won't work without libudev-zero
<dery>
and even then it's got some stubs so stuff *will* break
sjalv has joined #kisslinux
<sewn>
miau
<kris_>
indubitably
sjalv has quit [Ping timeout: 264 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 264 seconds]
sjalv has joined #kisslinux
<sad_plan>
dery: I dont belive you actually need mdev for that. you just need to fix the permissions yourself C:
sjalv has quit [Ping timeout: 244 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 265 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 264 seconds]
sjalv has joined #kisslinux
fultilt has quit [Quit: Leaving]
sjalv has quit [Ping timeout: 240 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 264 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 246 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 246 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 264 seconds]
sjalv has joined #kisslinux
clemens3 has joined #kisslinux
<dery>
sad_plan: I did
<dery>
but I was looking into why I could not manipulate backlight stuff from mdev, which I should, I think
<dery>
you can from udev
<sad_plan>
dery: I see.
<dery>
also apparently mdev-like-a-boss is built for... mdevd? there's a bunch of `cpu` regexes which I can't get to trigger on busybox mdev but do on mdevd
<dery>
I'm genuinely starting to think that perhaps a kernel update changed the /sys/ directory structure and something broke along the way
<sad_plan>
perhaps. cant you just script the correct permissions with a cronjob instead?
<dery>
again, I did in a `.boot` script previously
<dery>
that works 100%
<dery>
I was simply playing around and found those (undocumented?) limitations of busybox mdev
<sad_plan>
right. i mustve missed that
<dery>
I think it looks ever so slightly cleaner (and correct) to do it on device addition instead of bootup but on my laptop it's 100% irrelevant as both the drm adapter and the cpus aren't going anywhere :P
<dery>
no worries sad_plan
<sad_plan>
im in favor of choosing w/e solution works, while also being the simplest one. so use w/e works basically :p
sjalv has quit [Ping timeout: 246 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 240 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 264 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 264 seconds]
sjalv has joined #kisslinux
fultilt has joined #kisslinux
sjalv has quit [Ping timeout: 260 seconds]
sjalv has joined #kisslinux
sjalv has quit [Ping timeout: 246 seconds]
sjalv has joined #kisslinux
vouivre has joined #kisslinux
<vouivre>
phoebos: any idea how to contact hovercats ? I need an update for nettle in community for gnutls
<vouivre>
but I expect he isnt' active anymore
DetourNetworkUK has quit [Read error: Connection reset by peer]
DetourNe- has joined #kisslinux
DetourNe- is now known as DetourNetworkUK
<midfavila>
the package might need to be orphaned if they *are* inactive. maybe for now just bump the version on a local fork?
<vouivre>
what do you mean by "local fork" ?
<midfavila>
like make a copy of the package you need updated, make the changes yourself *to* that copy, and then you can use that until upstream is updated
<midfavila>
usually all you need to do to update a package is point the source file at the new upstream source, bump the version file to reflect that new source, and regenerat the built package's checksums
<midfavila>
regenerate, even
<vouivre>
ok, I get it. I want to update gnutls on community, because I'm the maintainer of gnutls. I can wait. But at some time it needs to be updated.
<vouivre>
and to orphan nettle, sincerly I have no idea how to contact the maintainer. He has an email ending with "@noreply.codeberg.org". I assume it's not usable.
<vouivre>
I could open an issue on community. Maybe it's the best.
<midfavila>
yeah
<vouivre>
thank you!
<midfavila>
np
<midfavila>
ngl thinking i'm gonna quit the bike job... kinda got what i wanted out of it. vancouver is looking really nice right now too