[03:10] <arraybolt3[m]> I can't get Arch Linux or even openSUSE Tumbleweed to let me install PipeWire JACK and jackd side by side - only Ubuntu Studio lets it work. If someone can get the latest PipeWire in a PPA for me to test, I'll gladly try to get the JACK device working again, and if it fails there too, then it's bug report time.
[03:12] <Eickmeyer[m]> arraybolt3 (@arraybolt3:libera.chat) : We're going to be going with whatever's in the Ubuntu repositories, not the "latest release."
[03:12] <Eickmeyer[m]> !latest
[03:12] <arraybolt3[m]> Eickmeyer: I know that, but I need the latest version in order to know whether to send a bug report or not. Otherwise upstream will be angry with me.
[03:13] <arraybolt3[m]> If I can get a bug report in the latest version, we can backport the bugfix to the Ubuntu repositories and have everything working. Or someone upstream can slap me into shape with a good config file and everything will just work.
[03:16] <arraybolt3[m]> (I'm sorta being lazy to ask for someone else to make the PPA, I know how to do it. I should just do it and then be able to help make things work.)
[03:18] <Eickmeyer[m]> arraybolt3 (@arraybolt3:libera.chat): This just in: Latest stable release of PipeWire is 0.3.52. https://gitlab.freedesktop.org/pipewire/pipewire/-/releases
[03:18] <Eickmeyer[m]> Latest in Kinetic: 0.3.52. https://launchpad.net/ubuntu/+source/pipewire
[03:18] <arraybolt3[m]> Yay and crud at the same time.
[03:19] <Eickmeyer[m]> HAHAHAHAH
[03:19]  * arraybolt3[m] proceeds directly to bug report page
[03:22] <arraybolt3[m]> Hmm. They have a thing right at the very top of their bug report page stating "If you are filing this issue with a regular release please try master as it might already be fixed." I guess I should try that first. So now crud and crud at the same time. 😦
[03:23]  * arraybolt3[m] wishes upstream wasn't so bent on "latest version" - it takes someone ten seconds to tell me it's already fixed, and takes me a couple hours to build something to see if it's fixed or not...
[13:49] <ThomasWard[m]> arraybolt3: welcome to 'upstream developers who don't care about supporting older releases because they're just annoying that way'  :P
 "arraybolt3: welcome to 'upstream..." <- I mean, I get it, and if compiling and installing stuff was as easy as an apt comment or something, I'd be fine with it, but it's not. (Maybe that's why people love Gentoo?)
[17:21] <OvenWerks> supporting? An older release is supported by a newer release that fixes bugs in the older release... Of course the newer release may also add new features or update required libs
[17:36] <OvenWerks> as an "upstream dev", I first create SW for my own use. Then for others (still important it works for others). As with most open source developers, my sw is a part time/ hobby persuit. supporting old sw is one of those "I have no time for that, feel free to fix this open sw on your own kinds of things"
[17:38] <arraybolt3[m]> OvenWerks: Me too. I fully understand the "why" of what's happening. Maybe we just need some tool that lets someone figure out if something's already been fixed, since bug report searches seem to be SO BAD at what they do. (I filed a feature request in KDE the other day, I made sure to check before submitting to see if it was a duplicate, it wasn't, I filed it, got closed the next day as a duplicate for some request that I
[17:38] <arraybolt3[m]> had no idea was related.)
[17:39]  * arraybolt3[m] wants AI-powered bug searches
[17:44] <OvenWerks> I think by the time an AI could co-relate some of the bugs I have seen that are related, That AI could probably also point out exactly where the bug was and fix it while it was at it.
[17:44] <arraybolt3[m]> LOL Github Copilot Search?
[17:45] <OvenWerks> GH extra stuff they have added in the past year have mostly just got in my way