09:12 <ifreund> NickH: If that is very important to you it could be done. I've been questioning the cost/benefit ratio of doing so in this case though. Zig 0.11 came out over a month ago and the LLVM version required for it came out like 6 months ago.

09:13 <ifreund> plus, bugfix releases after 0.3 will require zig 0.11, and I'd rather not have old released versions with many fixed bugs hanging around

09:14 <ifreund> add in the fact that I've already done the 0.11 upgrade in a branch which is slowly growing more conflicts and the fact that river 0.3.0 is probably about a month out still and it doesn't seem like the best use of my limited time at the moment

09:15 <NickH> Understood. I guess I'll just have to stick with whatever the last commit is that still builds with 0.10 even if it's not an actual release.

09:21 <ifreund> you mean due to the new bootstraping approach of 0.11?

09:22 <ifreund> that problem isn't going to just magically disappear anytime soon unfortunately and river will keep gaining new features and bugfixes that require newer zig versions

09:25 <ifreund> My humble recommendation would be to accept the wasm blob bootstrapping as the most practical option for your personal package repo and let the debian higher ups deal with packaging zig once they too eventually want to have software written in it available in the mainline distro

14:45 <adamcstephens> I'd vote for 0.3 requiring zig 0.11 so we could bump the zig version building river in nixpkgs. :)

14:47 <i9j8k7> hi, there is a bug with qemu and virtio gpu, the mouse cursor apparent position is below its real position, it's also upside down

15:00 <i9j8k7> sway and labwc have the same issue, weston is fine instead

15:47 <i9j8k7> I use emacs (pure gtk version) and there is the classic useless gtk window bar at the top. csd-filter-add/remove do not seem to be having any effect.

19:14 <novakane> how is that everytime I open github the UI is worse

21:28 <ifreund> novakane: yeah, I think I'll move river's issue tracker to codeberg at some point this year

21:53 <NickH> ifreund: yes is the binary that ships with the 0.11 source that is the problem. Really bootstrapping without that in a deb source package is difficult.

21:54 <NickH> I probably will just end up using as is for my private repo, but was hoping that it wouldn't be necssary for river 0.3.0.

21:56 <ifreund> I totally see where you're coming from. The core reason I don't think it's worth it to do an 0.10 release and then update right after is that the bugfix relaeses will require 0.11

21:56 <ifreund> so you end up with users stuck on 0.3.0 while many bugs would be fixed if they could update to 0.3.2 or whatever

21:57 <ifreund> In the past the timing has been a bit different around zig updates that made this a bit less of a problem, but it's always been there to some extent

22:08 <novakane> ifreund: that would be cool, I only have river and related projects that keep me using it honestly

22:09 <ifreund> you can already submit patches over codeberg if you like :)

22:11 <novakane> yeah I saw the PRs going on on codeberg, I get the emails here too, that's nice of you to allow both

22:13 <novakane> now when I open github I just feel like I'm on a social network instead of a forge, not really my thing