[02:52] Eickmeyer: so 17 worked before building 19... (did for me for sure) is there any history that can be used to find out when 17 was last built before 19 came out? [02:53] OvenWerks: Looks like January: https://launchpad.net/ubuntu/+source/jackd2/1.9.17~dfsg-1/+build/20917001 [02:56] I'm glad we're finding this out now because even if I hadn't updated it to 19, 17 still would've been rebuild after Feature Freeze. [02:58] Eickmeyer: I would say that if you fix one the other will work too [02:59] OvenWerks: What's happening is that falktx is developing against libraries in 20.04 with no mind to later libraries, so now that habit is hurting us. [03:15] Eickmeyer: so am I, it is a lot of work setting up a new version for dev work. 20.04 _is_ the latest LTS after all. [03:15] but still not helpful [03:16] I used to run latest release all the time. Then I started writing software... [03:26] Yeah. The problem is that if you're writing for an OS component (like jack), you have to write against the latest components. Problem with the LTS is it's frozen in time. [03:28] in the case of falktx, he is used to writing for kxstudio which was always lts [03:28] Right, but Jack is ubiquitous in that just about every distro carries it. [03:29] maintaining jack is something new for him though. I am sure he will get it [03:29] Right. But that doesn't help us now. [03:29] no. [03:29] Meantime we have a blocking bug. [03:30] I had to go through the same learning curve though, so I understand. [03:30] I had a perfectly working sw package till it got used in 21.04 ish... [03:32] Arch is even worse [03:32] Yeah, Arch is a moving target. [03:33] I will say, a number of my pr seem to have come from there [03:34] there should be a list of changes of the depends though. [03:34] It does mean going through them though. [03:35] It is possible it is a bug in the dep too. [03:35] That's true. The issue is figuring out which one, and that's way above my knowledge. I can get package versions, but that's about where my expertise ends.