#
…

2024-03-24

00:00chadmedhmm yep looks like its trying to load zink
00:00chadmedi dont think mesa was built with VIDEO_CARDS=asahi
00:03nyaomixyz../var/db/pkg/media-libs/mesa-24.1.0_pre20240228-r1/USE lists video_cards_asahi
00:04leiothat zink stuff is usually just a red herring warning in my experience, especially in that form where it says it doesn't have zink available
00:04chadmeddo apple_dri.so and asahi_dir.so exist in /usr/lib64/dri?
00:05leioI'm guessing the xorg in there is because sddm doesn't do wayland or something?
00:05nyaomixyzasahi_dri and apple_dri are there
00:05chadmedsddm supports wayland sort-of, it needs manual config and you need to remove agetty from tty0 in inittab
00:05leioyeah, nvm, plasma looks to be in wayland
00:05nyaomixyzcorrect sddm is not yet defaulting to wayland but since i am now starting from terminal this shouldn't be an issue
00:06* leiosneaks off to bed, gl
00:06chadmedcan you try rebuild mesa and libdrm?
00:06chadmedeverything in the logs looks fine tbh
00:12nyaomixyzand yet for some reason llvmpipe remains
00:12nyaomixyznot even MESA_LOADER_DRIVER_OVERRIDE=asahi works
00:13nyaomixyzMESA_LOADER_DRIVER_OVERRIDE=apple works, but it's a slideshow
00:13nyaomixyzasahi -> llvmpipe
00:36chadmed_ has joined #asahi-alt
00:53ipatch_ has quit [Quit: WeeChat 4.2.1]
01:00nyaomixyztried to specify use flags by hand but it amounted to nothing
01:06possiblemeatball has quit [Quit: Quit]
01:12zerdox has quit [Ping timeout: 480 seconds]
01:36nyaomixyzchadmed: why the hell all the dri libs have the same md5sum
01:36psykosethey're hardlinks
01:36psykosegallium is one library
01:37nyaomixyznow it makes sense
01:37psykosei don't know why they're hardlinks
01:37psykosethey work fine as symlinks too
01:37psykoseseems like a silly decisiou
01:37psykosedecision*
01:40nyaomixyzalso because it kinda tricks your brain in thinking stuff
01:41nyaomixyzbtw, idk what the hell is wrong
01:42chadmed_yeah sorry im at a loss too... i just did a fresh install last night on a j314 and it all worked fine
01:43chadmed_im working on fixing the rust bs in the overlay rn, then ill need to do an MR for asahi-sources in the main gentoo branch
01:43chadmed_which will of course take 600 years to get merged because no one with write access has the bandwidth to review anything and no one wants to give me write access
01:43psykosewhat's the normal way to find out why mesa refused to load a specific driver
01:43psykosethat is not trying to compare strace with code :D
01:44nyaomixyzat some point it emerged the mesa gentoo driver but i masked that out, removed it from existence and then i installed mesa from asahi
01:44psykosethat would be ok
01:44nyaomixyzat this point i am wondering if something was left in there
01:44chadmed_uhh one second
01:44chadmed_yeah that is kinda fucky
01:44chadmed_you have to rebuild some other package
01:44nyaomixyzlibdrm? done
01:45chadmed_nah not libdrm theres some other one
01:45nyaomixyzvulkan-loader?
01:47chadmed_it might be libglvnd
01:47nyaomixyzit's from nvidia
01:48chadmed_zstd is from meta but its not just for accessing facebook
01:49nyaomixyzi know though it seems wacky that could be it
01:49chadmed_also try xorg-proto
01:50psykosexorgproto is just a bunch of headers so that would mean more rebuilds after
01:51tpw_ruleschadmed_: are you that guy who claims zstd is how facebook is trying to take over the world
01:52psykosethat's probably the worst part about zstd
01:52psykosenothing about itself, just all the people that refuse to touch it because 'lol facebook'
01:53psykosealways hurts when something comes out that pushes the pareto front and people turn up their nose
01:53nyaomixyztried to rebuild a bunch of other media-libs, nothing
01:56chadmed_im out of ideas then something's clearly broken because a clean install Just Works(tm)
01:57nyaomixyzthis was supposed to be a clean install but i fucked it up midway without noticing lmao
01:57tpw_rulesi've had a few users report corruption of the built mesa libraries and idk why
01:57nyaomixyzon one side i can restart, on the other it's a pain
01:57nyaomixyzit'd be easier to tear the entirety of mesa down
02:00psykoseemerge world minus a few packages and take a break :-)
02:00KxCORP5 has quit [Quit: Bye!]
02:00KxCORP5 has joined #asahi-alt
02:03tpw_rulesor reformat?
02:10chadmed_you could probably just try doing emerge @installed and letting it rip
02:10chadmed_will take a decent whack of time though :p
02:17nyaomixyz has quit [Remote host closed the connection]
02:17chadmed_ugh that rust patch is so big
03:11jeisom has quit [Ping timeout: 480 seconds]
04:22tobhe has joined #asahi-alt
04:27tobhe_ has quit [Ping timeout: 480 seconds]
06:11chadmed_ has quit [Remote host closed the connection]
06:20chadmed_ has joined #asahi-alt
08:22nyaomixyz has joined #asahi-alt
08:24nyaomixyzhello - dropping in to report, no progress yet but i found that DRI devices aren't even good. Starting to wonder that problem is not related to mesa
08:25nyaomixyz has quit [Remote host closed the connection]
08:51chadmeddid you try emerge @installed?
09:00nyaomixyz has joined #asahi-alt
09:00nyaomixyzchadmed: no I didn't yet. Doing it now
09:00nyaomixyz900 something packages
09:01nyaomixyzwhat I found is that the gpu lives at /dev/dri/card1
09:01nyaomixyzand it's THE gpu
09:01nyaomixyzhowever the screen for some reason seems connected to /dev/dri/card0
09:01chadmedits because the gpu is not the display controller
09:02nyaomixyzand that display controller
09:02chadmedthey are totally independent SIP blocks and have almost nothing to do with each other
09:02nyaomixyzcard0 shows up as framebuffer
09:02nyaomixyzdunno if it's legitimate
09:02nyaomixyzbefore rebuilding the kernel today (after your rust patch I made sure to emerge sync for safety) not even the gpu was recognized
09:03nyaomixyzso now I have a legitimate card1 and renderD128
09:03nyaomixyzyet, llvmpipe on kde
09:04nyaomixyzbtw the hdmi won't work
09:04chadmedsomething about your install is totally busted then, you should just reinstall
09:06nyaomixyzlike it spams "Failed to get dp-xbar: -517" exactly
09:07chadmedah yep i _think_ thats going to be because the distkernel uses the alarm kernel config which doesnt have that option
09:07nyaomixyzbut could that be related?
09:07chadmedcan you try with asahi-sources instead of asahi-kernel and ill upload the .config i use
09:09chadmedthis is a very very barebones kernel but everything asahi-related should work
09:10nyaomixyzwell... i'll do that after emerging the entirety of my install at this point
09:11nyaomixyzor i could also cancel
09:16nyaomixyznice, it crashes because rust
09:17chadmedergh yeah take the patch from the overlay and put it in /etc/portage/patches/sys-kernel/asahi-sources/
09:17nyaomixyzin any case, so people are not using asahi-kernel for real?
09:18chadmedi started working on the dist-kernel in preparation for bootable install media however we need a reliable way to copy down the fedora kernel config which doesnt exist for COPRs
09:18chadmedsomeone was working on it but the configs they landed on were not conformant to our "do what upstream does" policy
09:18nyaomixyzi will emerge @installed for now, because i have other stuff pending irl and well, so that i start narrowing down the thing
09:18chadmedand they were unwilling to change
09:18nyaomixyzhowever i wonder if anyone else can reproduce by just emerging asahi-kernel at this point
09:20chadmedasahi-kernel works on my mac studio
09:21chadmed has quit [Remote host closed the connection]
09:28mpschadmed: alpine asahi kernel config works long time and very stable, maybe you could look in its config (sorry for advertising)
09:36chadmed has joined #asahi-alt
09:37nyaomixyzchadmed: ok but a mac studio doesn't have a built in screen... i wonder if this can be repro'd on m1 pro macbooks at this point (if it's a platform issue we're all happy and i am just unlucky)
09:38chadmedthe builtin screen is irrelevant, the relationship between the display controller and gpu is the same in all machines
09:39janneghas the asahi-kernel config CONFIG_MUX_APPLE_DPXBAR as module / built-in? that would be the most obvious cause for "Failed to get dp-xbar: -517"
09:40chadmedno it doesnt, its just the -edge config from ALARM pkgbuilds repo
09:40chadmedi need to grab the fedora config and host that somewhere and just pull it in as a SRC_URI
09:43jannegthat breaks asahi-kernel on all m2* devices
09:44nyaomixyzwhat does ls -la /dev/dri/by-path look like in your machines?
09:47chadmedgpu-card > card1, gpu-render > renderD128, display-subsystem-card > card0
09:53nyaomixyzcard0 is framebuffer here
09:53nyaomixyzso there's a missing puzzle piece
09:54chadmed has quit [Quit: Konversation terminated!]
10:20jannegnyaomixyz: the display controller never probes because because the driver for one piece required for hdmi support (on laptops) is not enabled in the config
10:25nyaomixyzso i tried to compile asahi-sources and it would hang on boot
10:25nyaomixyzso i unmerged and remerged it for good measure
10:25nyaomixyznow rebuilding again with chad's config
10:25nyaomixyzalso following 1:1 the install.sh
10:25jannegchadmed_: see the the "
10:25nyaomixyzthis is like the first time i am installing gentoo ever but at least i got some experience in wacky linux stuff from other distros... it's fun
10:26nyaomixyzwell not fun fun as i would've loved to do stuff by this point but eh, problems
10:26jannegchadmed_: see the the "Dist Git Source" links on the copr build page
10:33nyaomixyzchadmed_: your configuration won't boot on my pc
10:34nyaomixyzerr, macbook
10:35jeisom has joined #asahi-alt
10:36nyaomixyzwell, compiling with the fedora config
10:37nyaomixyzand here goes nothing
10:46chadmed has joined #asahi-alt
10:47chadmedare you using dracut to make an initramfs?
10:49chadmeddid you pass --zstd to it?
10:49nyaomixyzi'm passing whatever is in ./install.sh so it's compress gzip
10:50chadmedah yeah thats wrong my config only uses zstd across the kernel
10:50chadmedi told you it was barebones heh :p
10:50chadmedhence why its not suitable for a dist kernel
10:50jannegI'm working on getting asahi-kernel fixed
10:50nyaomixyzhowever probably the entire asahi-gentoosupport has to be revised
10:51nyaomixyzso that it pulls asahi-meta
10:51nyaomixyzoh and also why the hell `exec $(which asahi-fwupdate)`
10:51chadmedthere was a reason but it escapes me
10:51nyaomixyzit won't ever print your "finished" lines tho
10:52chadmedthat repo is basically deprecated at this point anyway, the plan going forward is for a bootable livecd with all required ebuilds upstream or the choice of a prepackaged disk image like the vanilla asahi installer
10:52mpsahm, latest tagged kernel is still 6.6 based
10:53mpsnot sure should it be upgraded for distro (alpine in my case)
10:53nyaomixyzBTF: .tmp_vmlinux.btf: pahole (pahole) is not available
10:53nyaomixyznew dep for asahi-kernel with fedora config
10:56jannegthanks, I wouldn't have noticed the missing the pahole dependency, curse of dev machines which have dev tools installed
10:56jannegchadmed: is there a reason why asahi-kernel depends on virtual/dist-kernel?
10:57nyaomixyzasahi-sources doesn't have dtbs in /lib/modules wtf
10:57nyaomixyzis there a make subcommand for those?
10:58chadmedjanneg: gentoo-kernel does it so we do it too
10:58chadmedyeah its make dtbs_install
10:58jannegsince asahi-sources doesn't build / install anything that's to be expected
10:58sam_it's required to pull in the new version of dist-kernel in the right order
10:58chadmedupdate-m1n1 is patched to take them from /usr/src/linux though
10:58sam_(for the rebuilds)
10:59jannegbut virtual/dist-kernel depends on the upstream dist-kernel, i.e. that's pointless for us
11:00sam_you'll have to fork the virtual until you add asahi-kernel to ::gentoo
11:00chadmedi override upstream in the overlay
11:01chadmedbecause asahi-kernel depends on virtual/dist-kernel-6.6.0_p15 specifically it will never try to pull upstream
11:01nyaomixyzoh god it's taking dracut so long to compress this initrd
11:01nyaomixyzthe fedora config has to be cut
11:01chadmedno it doesnt
11:01chadmedif you want a dist kernel, you get the full dist kernel experience
11:01chadmeduse asahi-sources if you want a lighter kernel
11:02jannegah, so I should install virtual/dist-kernel::asahi instead of asahi-kernel
11:02chadmedno you shouldnt need to
11:02chadmedthe dep graph will resolve to only ever want virtual/dist-kernel::asahi
11:02chadmedsince there is no virtual/dist-kernel-6.6.0_p15 upstream
11:04chadmedargh ffs
11:04jeisom has quit [Quit: Leaving]
11:04chadmed_now_ it will only ever depend on 6.6.0_p15 :/
11:05jannegbut doesn't that break the auto update as well?
11:06jeisom has joined #asahi-alt
11:07jannegif it deepends on dist-kernel-6.6.0_p15 it will not pull in dist-kernel-6.8.0_p1 once we provide that
11:08chadmedwe just add a virtual/dist-kernel version for that
11:08chadmedthe ebuild has =virtual/dist-kernel-${PV} so it will look for a virtual/dist-kernel with a version exactly matching the actual kernel ebuild
11:09chadmedsince there are no upstream kernels called -6.8.0_pX then it wont match on anything but what we provide
11:09chadmedno upstream virtual/dist-kernels*
11:10jannegI'm not convinced that the auto-update within ::asahi will work with the fixed version
11:11nyaomixyzwell, compiling asahi-sources with fedora config makes a compressed initramfs of 200mb
11:11nyaomixyzand it won't even boot because it won't find /init
11:11nyaomixyzfor some reason
11:11nyaomixyzit hangs with errno -2
11:12nyaomixyzwhich is.. understandable? is that linked to systemd in some way?
11:13chadmedjanneg: just tested it and it worked fine
11:13jannegfedora-asahi-remix' initramfs are ~95M
11:13chadmednyaomixyz: unless the fedora config looks somewhere other than /sbin/init it shouldnt matter
11:13jannegchadmed: ok
11:13chadmedcan you try with my config again and pass --zstd to dracut
11:14chadmedall we need to do for updating to work properly is remember to also push a new version of virtual/dist-kernel that matches exactly the asahi-kernel version
11:14chadmedand portage resolves the deps properly and updates successfully
11:16jannegis it an oversight that asahi-kernel has no metadata cache?
11:16jannegmps: asahi-6.6-16 fixes HDMI issues on M2* desktop systems
11:17mpsjanneg: aha, thanks for info
11:17chadmedjanneg: not an oversight i just stopped pushing them since they pollute the commits and dont seem to be neccessary/wanted as they also screw with pkgdev
11:18chadmedtheyre not present in ::gentoo
11:19sam_is the overlay in the official repo list?
11:19sam_if it's not, if you get it added, then we mirror it w/ metadata added
11:20chadmedi think leio wanted to get some QA stuff cleaned up before endorsing it
11:20sam_there's far worse in the list ;)
11:20chadmedi dealt with a bunch of stuff pkgcheck was complaining about months ago but theres probably more
11:20sam_yeah i guess add the pkgcheck action to the gh repo first
11:21chadmeddo i just knick that from ::gentoo?
11:21sam_we have a custom setup for ::gentoo, but you can grab https://github.com/thesamesam/overlay/tree/master/.github/workflows or the one from haskell
11:22jannegasahi-kernel initramfs size with fedora config is 41M, not yet booted though
11:23chadmedits insane to me that the same people who own github also somehow managed to wrought the crime against humanity that is azure devops upon us
11:24chadmedspent over a week wrangling CI stuff on azure for work and just gave up, its deranged
11:24sam_horrible isnt it
11:26axt has joined #asahi-alt
11:26chadmedi have it running on a single repo since its the only one we have that actually needs to build deployable artefacts but if i had to do another one id probably sooner quit and look for another job
11:28nyaomixyzbtw it didn't boot because dracut couldn't copy the full initramfs to the uefi
11:28nyaomixyzit wasn't 200mb it seems
11:28nyaomixyzit was... more
11:28leiowhat are we talking about? Getting to overlays list?
11:30chadmedleio: yeah mostly
11:30leioI vaguely recall encouraging you to file the PR to api.g.o
11:30nyaomixyzAAAAAAAAND
11:30nyaomixyzit was the kernel
11:30leioand was annoyed I couldn't just give an eselect repository instruction in the project page
11:30nyaomixyzasahi-kernel has to be revised
11:30nyaomixyzyour configs booted with gpu acceleration
11:31nyaomixyzoh shit i was really thinking of emerging @installed poor me
11:31nyaomixyzcc chadmed
11:31chadmedeyyyy \o/
11:31nyaomixyzso i can install gentoo after all
11:31nyaomixyzok but now... do i leave this on github issues?
11:32chadmedyeah leave the issue open and ill close it when we fix it up
11:32chadmedsorry about all the mess, i started fixing all this stuff during the christmas break and then got inundated with life/work stuff...
11:32chadmedsomeone should pay me to do this full time i think :p
11:32possiblemeatball has joined #asahi-alt
11:33nyaomixyzand here i was doubting myself
11:33nyaomixyzi kinda don't like fedora so...
11:33nyaomixyzok but now for real what's the difference between the two configuration files? question mark
11:33chadmedas in the fedora config and mine?
11:36nyaomixyzas in alarm and yours
11:36nyaomixyzbut legitimately a kernel built with fedora configs won't fit on the 512mb efi
11:37nyaomixyzit's 1.4gb uncompressed
11:37nyaomixyzso either the modules and kernel are compressed beforehand with zstd or.. idk
11:39sam_wtf are you doing if it wont fit
11:39sam_maybe it's the page size i guess
11:39sam_but i mean the gentoo fedora config ones are like, 100MB or something
11:39nyaomixyzI literally downloaded the config from fedora and then I ran... make -j4
11:39nyaomixyzmake install and make modules_install
11:39chadmedthe alarm build is older than gilgamesh and mine is not so it has all the latest kernel options
11:39nyaomixyzdracut failed copying the initrd to /boot
11:42nyaomixyzbtw tested hdmi and it works too
11:42nyaomixyzso yeah asahi-kernel... bad move from me
11:44jannegfails the just added pkgcheck CI
11:44nyaomixyz... did you build with that?
11:45nyaomixyzoh btw asahi-audio still depends on asahi-sources
11:45nyaomixyzso if one wants to use either or, they still have to pull both
11:45chadmedjanneg: seems to be annoying dep handling due to out of sync keywords on quite a few packages. ill fix them all up this week
11:46jannegyes, and it results in a 41M initramfs, I suspect that's a hostonly initramfs though as the fedora initramfs is 95M
11:47chadmedgentoo defaults to --no-hostonly aiui
11:47chadmedfedora ironically defaults to the opposite which caused me much frustration with asahi-gentoosupport :p
11:47nyaomixyzthe hell happened with my build then
11:47stintelyou can always use package.provided
11:48stintel➜ cat /etc/portage/profile/package.provided
11:48stintelsys-kernel/asahi-sources-6.8.0
11:48janneg1.4gb uncompressed sounds like modules with debug info, which makes sense as the fedora build keeps the debug info in a separate package
11:49nyaomixyzkernel-aarch64-16k-fedora.config
11:49nyaomixyzthis is the one I downloaded
11:52janneguse asahi-kernel with asahi-kernel as that seems to remove either the debug CONFIGs or removes the debug info before install
12:37JayBeeFOSS has quit [Ping timeout: 480 seconds]
12:38JayBeeFOSS has joined #asahi-alt
13:09qdot has quit [Ping timeout: 480 seconds]
13:11paps__ has joined #asahi-alt
13:17paps__hi, I'm trying to boot a live debian in order to luks encrypt my debian asahi install, but after following the instructions from @cy8aer (https://git.g3la.de/repos/m1-debian) and making the usb key both ways (either from debian or macos) I cannot boot from it. After typing 'run bootcmd_usb0' or 'run usb_boot', U-boot says 'no usb devices available'
13:18paps__Or it says 'Device 0: unknown device'. Any idea what I might be doing wrong? Do I need to worry about boot flags on the usb thumb drive? thanks and sorry for the noob questions
13:20cy8aerLook at your live stick in "efi/debian/grub.cfg" and try other than "hd0" like "hd1", "hd2" - for me it is "hd2"
13:21cy8aerLooks like it is different for every device and usb slot (?)
13:24cy8aeroh, for me it is "hd3" (macbook pro m1pro)
13:31chadmedu-boot's usb stack is not very good and doesnt work with some usb sticks too. try a different stick
13:32paps__I think you're talking about a future problem I'm going to have :) Right now I don't get to the stage where it tries to boot from the stick. U-boot basically doesn't see my key
13:32paps__@chadmed ah interesting, ok I will try
13:36cy8aerAnd: I do not know which description you actually used for starting it up. It should be: "env set boot_efibootmgr; run bootcmd_usb0"
13:37cy8aer(just correcting at every place I documented this)
13:46cy8aerand the stick should have a subpartition, do not put vfat directly in the stick (e.g. "sda") but into e.g. "sda1"
13:56paps__I got it to boot! I had to use a different key and then change hd0 to hd3 :) Thanks a lot for the help
14:00axt has left #asahi-alt [#asahi-alt]
14:07qdot has joined #asahi-alt
14:08cy8aeryep sorry for the unconvenience 😉
14:09cy8aerpaps__: what system do you have? Probably "hd3" is the new parameter for grub...
14:17jannegwe probably want to cut the fedora config down, it installs 39M of dtbs to /boot
14:20mpsdtbs for all SoCs
14:21paps__@cy8aer it's a m1 pro 14"
14:22cy8aerok, same system. So no prove that hd3 is standard
14:48chaos_princess has quit [Quit: chaos_princess]
14:48chaos_princess has joined #asahi-alt
14:52nyaomixyzasahi-kernel with the fedora config builds and runs fine
14:52nyaomixyznow i'm supposed to go through with the installation since it's been half done since yesterday
14:58zzywysm has quit [Quit: Textual IRC Client: www.textualapp.com]
15:14zzywysm has joined #asahi-alt
16:13opticron has quit [Remote host closed the connection]
16:13opticron has joined #asahi-alt
17:35tobhe_ has joined #asahi-alt
17:39tobhe has quit [Ping timeout: 480 seconds]
18:00zzywysmjanneg: for some reason, virtually all of the folks i deal with in Linux seem to take pride in how bloated their kernel configs are
18:01zzywysmjanneg: it suggests that very few people know what return-oriented programming is
18:09qyliss has quit [Quit: bye]
18:10qyliss has joined #asahi-alt
18:10mpszzywysm: for machines I use I usually build trimmed kernels but these are not acceptable for distro users, mostly
18:18qyliss has quit [Quit: bye]
18:20qyliss has joined #asahi-alt
18:27mpszzywysm: ahm, similar with my ones
18:41jannegzzywysm: not much to do about distro kernels as you can't predict which devices users want to use
18:44ipatch has joined #asahi-alt
19:06Compassion1 has quit [Quit: lounge quit]
19:22jacksonchen666 has quit [Quit: WeeChat 4.2.1]
19:25Compassion1 has joined #asahi-alt
19:26Compassion1 has quit []
19:39Compassion1 has joined #asahi-alt
19:42zzywysmanyone have any insight into why these changes lead to memory savings? my primary goal was getting rid of build warnings, and my secondary goal was increased performance
19:51paps__ has quit [Quit: Connection closed for inactivity]
19:51tpw_ruleschadmed: wireplumber 0.5 apparently "refactors" the lua script support and asahi-audio doesn't work properly anymore. i've rolled back to 0.4 but you might wish to know
20:04mpstpw_rules: I reported this issue few days ago
20:04mpsreported here
20:04tpw_rulesah, i had missed that
20:04mpsalso I went back to 0.4
20:10ipatch has quit [Quit: WeeChat 4.2.1]
20:15ipatch has joined #asahi-alt
20:35possiblemeatball has quit [Quit: Quit]
20:49jeisom has quit [Quit: Leaving]
20:51jeisom has joined #asahi-alt
20:51jeisom has quit [Remote host closed the connection]
20:51jeisom has joined #asahi-alt
21:37jacksonchen666 has joined #asahi-alt
22:08chadmed__ has joined #asahi-alt
22:10chadmed__tpw_rules, mps: ill look into it when i have the time. wp 0.5 hasnt made it into gentoo yet so i didnt notice
22:14sam_deliberately because of the breakage
22:14sam_not been in a hurry...
22:15sam_i think the migration doc thing only got made like 2 days ago
22:15nyaomixyzis there a gentoo binhost that provides packages without systemd integration?
22:16nyaomixyzbecause I wanted to test that, but I am still compiling the most of packages
22:16sam_i think the binhost has one or two openrc builders but it doesnt rebuild everything as lots of packages do not have USE=systemd
22:16sam_it's just that the openrc one needs to gain a few packages
22:16sam_but i am very surprised by *most*
22:16sam_the notable issue one is webkit-gtk where it has USE=systemd but its for something silly and that annoys people
22:16nyaomixyzsystemd is winning.....
22:16sam_well its not about winning
22:17sam_its because the other way around is harder
22:17sam_like, on a systemd machine, you can build stuff w/ USE=-systemd
22:17nyaomixyzcompiling webkitgtk as we speak
22:17jacksonchen666 has quit [Quit: WeeChat 4.2.1]
22:17sam_but on an openrc machine, you cant just build stuff w/ USE=systemd
22:17sam_when u say most things
22:17sam_do you really mean you are sad building webkit-gtk
22:17leiowebkit-gtk feels like something that would work with elogind?
22:17sam_which is totally reasonable, but a different matter
22:18sam_i looked into it before and i don't remember the answer
22:18sam_maybe tomorrow
22:18leioit's journal usage per cmake knob; maybe if it works and we made USE=systemd depend on systemd || elogind, the binpkg would be usable if openrc doesn't use.mask systemd? (does it?)
22:18nyaomixyzi did spawn more jobs than my ram could keep and i already crashed the puter on that hill
22:19* leiowould just use systemd, and does :)
22:19* nyaomixyzwould just use openrc, it's still the default
22:19sam_"default" doesn't really mean anything in gentoo
22:19sam_anyway
22:19sam_we should add webkit-gtk to one of the openrc builders
22:19sam_back later
22:20nyaomixyzi know i was teasing
22:20nyaomixyzabout the default
22:20sam_i have heard it seriously so many times
22:20sam_everything in the book from both "sides"
22:20nyaomixyzbut like, for real, i only run openrc on my personal stuff
22:20sam_i have no sense of humour anymore about it, im like a husk
22:20nyaomixyzsystemd i run on my homelab thingy tho
22:21nyaomixyzwell i guess that you've lived enough days with people fighting each other over the init system choice
22:21nyaomixyzi only barely looked at that discourse
22:21nyaomixyzused openrc because uh alpine had it and i worked with it, then artix had it and i wanted to try it, now gentoo
22:27chadmed__urgh so everything has changed to spa-json
22:28chadmed__thats not necessarily a bad thing but virtually everything we did has to be thrown in the bin :)
22:57possiblemeatball has joined #asahi-alt
23:08kidplayer666 has joined #asahi-alt
23:14chadmed__ has quit [Remote host closed the connection]
23:27JayBeeFOSS has quit [Remote host closed the connection]
23:27JayBeeFOSS has joined #asahi-alt
23:57tobhe_ is now known as tobhe
…