<Guest94>
Does River support x86? I'm trying to compile and I get the error "type 'isize' cannot represent integer value '4294967295'"
yongxiang has quit [Server closed connection]
yongxiang has joined #river
Guest81 has joined #river
Guest94 has quit [Ping timeout: 250 seconds]
Guest81 has quit [Ping timeout: 250 seconds]
ecocode___ has quit [Quit: Connection closed for inactivity]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar12 has joined #river
Ireozar12 has quit [Client Quit]
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
vimproved has quit [Ping timeout: 252 seconds]
vimproved has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
ecocode___ has joined #river
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Ireozar has quit [Remote host closed the connection]
Ireozar has joined #river
Keeto has joined #river
<ifreund>
In theory river could support 32-bit systems, but we don't have CI testing it and I'm not too surprised that it doesn't compile
<ifreund>
patches welcome
<ifreund>
We would need 32-bit CI to prevent it regressing again though
<ifreund>
jpnt: in case you check the logs, that assertion failure is theoretically fixed by the upcoming wlroots 0.19.1 release
<ifreund>
or maybe not, it looks like someone on that sway thread reports the fix I mentioned not being sufficient if creating textures/uploading buffers fails
<ifreund>
anyhow, I don't think there's anything river can do about it, it's a wlroots bug
ecocode___ has quit [Quit: Connection closed for inactivity]
daurnimator has quit [Server closed connection]
daurnimator has joined #river
palanix has quit [Ping timeout: 248 seconds]
palanix has joined #river
Guest43 has joined #river
Guest43 has quit [Client Quit]
nemoto has quit [Remote host closed the connection]
<ifreund>
will tag river 0.3.12 with Zig 0.15 compat in a day or two after I've run it for a while without crashing
<ifreund>
need to set up the river-classic repo first too, this release will get tagged there as well
jpnt has joined #river
csfore has quit [Server closed connection]
csfore has joined #river
apoorv569 has joined #river
<pkap>
Will river classic compile to a river-classic binary?
<pkap>
Or stay as is
<ifreund>
pkap: the binary will be river, the point is to break as little as possible :)
<pkap>
Curious how packagers will handle this
<pkap>
Is it even possible without breakage? At some point distros need to replace river classic with the new river
<ifreund>
pkap: it should be pretty straightforward. river-clasic replaces river 0.3.x, river-classic conflicst with river
<ifreund>
as long as the distros switch to river-classic before upgrading to river 0.4.0, there should be no breakage for end-users
<pkap>
Ah true this should work.
<pkap>
For pacman at least
<ifreund>
if a distro is using a package manager that doesn't have a mechanism for package replacement I don't think it's worth supporting
<pkap>
Yes agreed. I assume all common package managers support this case.
<pkap>
It's good to have river classic separated already. People get confused with the 0.3 branch and the deprecated master
<pkap>
People not following the development closely
<pkap>
Will the non-window manager relatet configuration (river control) stay as it is currently?
<jpnt>
is it just me or has been wlroots development super unstable recently. I come from dwl and its not the first time I come across problems since wlroots 0.19
<ifreund>
jpnt: I haven't noticed any change in the number of wlroots regressions recently
<ifreund>
the fact that regressions are often somewhat hardware-specific can make it feel rough when your hardware is affected
<ifreund>
while you might not notice regressions that don't affect your hardware at all
<jpnt>
maybe i need to test further about the problem i mention yesterday. I tested now and with scale 1.0 it doesnt crash but with scale 1.5 it does. the problem seemed to be a wlroots assertion error but im still not 100% sure
<jpnt>
yeah and the fact that im in a hybrid gpu system doesnt really help xd