00:27 <cruxbot> [contrib/3.7]: python3-maturin: updated to version 1.8.3

00:27 <cruxbot> [contrib/3.8]: Merge branch '3.7' into 3.8

00:27 <cruxbot> [contrib/3.8]: python3-maturin: updated to version 1.8.3

04:50 <cruxbot> [core/3.8]: meson: 1.7.2 -> 1.8.0

10:25 <ppetrov^> r0ni, you there?

16:17 <fire_varan> jaeger^ [3:0:0:0] cd/dvd NECVMWar VMware SATA CD01 1.00 /dev/sr0

16:17 <fire_varan> [32:0:0:0] disk VMware, VMware Virtual S 1.0 /dev/sda

16:18 <fire_varan> that's what lsscsci gives me

16:58 <frinnst> now to figure out what broke my wayland screen setup.. TV somehow ended up the right end with shit resolution, compared to 4k on the left yesterday

16:58 <frinnst> i love random stuff

18:57 <cruxbridge> <tim> frinnst: any specific error you're getting?

19:01 <frinnst> no errors, screen just moved

19:02 <frinnst> profile static { output HDMI-A-1 enable position 0,0 <- 0,0 is apparantly more than 5120 nwo

19:02 <frinnst> now

19:02 <frinnst> using kanshi

19:04 <cruxbridge> <tim> Odd

19:05 <frinnst> how do you get the current layout with wlroot composers? I guess I should start with that

19:05 <cruxbridge> <tim> I just wanted to say: there is a command with sway using swaymsg

19:06 <frinnst> ahh thats the one

19:06 <frinnst> and this one is a bit surprising i guess? 00:00:00.006 [swaymsg/main.c:497] Unable to retrieve socket path

19:07 <frinnst> this all feels very familiar from a year or so ago - havent really touched it since and of course, i've forgotten 99% of it

19:10 <cruxbridge> <tim> Which socket though?

19:15 <frinnst> fucking reboot solved it - not just restarting labwc

19:15 <frinnst> its like windows \o/

19:16 <frinnst> now to try and find a way to control my 7600xt's fan.. its on or off, like a superbike reving it's engine. not annoying at all

19:16 <frinnst> once it hits 60C - 100%

19:23 <cruxbridge> <tim> Mine does not do that

19:24 <frinnst> it was quiet during the winter.. but with an additional extra ambient degrees, its gone fairly mad

19:24 <frinnst> what vendor? mine was powercolor something

19:35 <zorz_> jaeger lvm2 works fine with /etc/rc

19:36 <SiFuh_> zorz_: noted!

19:37 <zorz_> with pencil or pen? :p

19:38 <SiFuh_> Nah, just memory.

19:41 <zorz_> logging 20y bitch.

19:41 <zorz_> heh

19:41 <farkuhar> As I understand it, the lvm2 breakage was reported on a 3.8 rc4 installation, which zorz_ later updated using the 3.8 release ISO. I'm curious whether zorz_ changed anything in pkgadd.conf, or otherwise prevented the upgrade from overwriting the old scripts from 3.8 rc4.

20:21 <cruxbridge> <tim> frinnst: Asus

20:27 <farkuhar> The timeline for zorz_'s lvm2 issue is hard to reconcile with the dates when 3.8rc4 and 3.8final were released. Even by the date of 3.8rc4, the ports tree for building the ISO should have contained this commit. https://git.crux.nu/ports/core/commit/5a54055e9f639e773b8e4ef83da777cda6bd7be5

20:32 <farkuhar> zorz_ mentioned doing a prtwash in a previous attempt to reproduce the error, as if the rc scripts were still being distributed via the ports tree, not via a tarball downloaded from Gitea. Somehow the ports tree distribution method was still in effect at the time of zorz_'s rc4 install?

20:36 <zorz_> look now i am checking the https://crux.nu/ports/crux-3.7/core/rc/Pkgfile it says source=(inittab rc rc.modules rc.single rc.multi rc.local rc.fix rc.shutdown rc.conf)

20:37 <zorz_> why 3.7, why source are the files?