[01:51] <OvenWerks> Eickmeyer: I am not at a place where I can test on 20.10 right now. Being broken on 20.04 is fine if it works on 20.10 (where it was made to).
[01:52] <Eickmeyer[m]> Honestly, I haven't tested it yet.
[01:52] <OvenWerks> I need to set those flags on my set up and see if that affects my build I guess. I can add them one at a time.
[01:52] <OvenWerks> At least one person has built and is using it though (aside from me)
[01:54] <OvenWerks> I guess it could be jack... but the api shouldn't have changed that much. My use of it is pretty slim.
[01:54]  * OvenWerks knowledge has expanded some too though.... 
[01:55] <Eickmeyer[m]> We can override the build flags if you can figure out which one is problematic.
[01:55] <OvenWerks> I do have one fix I want done in Ardour, then I can try some things.
[01:56] <OvenWerks> Eickmeyer: while it would be nice to get it into G it is not top importance.
[01:57] <OvenWerks> means "I will see what I can do"
[01:57] <Eickmeyer[m]> OvenWerks: Yeah, no worries. At least we have most of the packaging done.
[01:58]  * OvenWerks has spent half the day setting a stage up for Sunday.... tomorrow too. The room has been turned 90 degrees... 
[01:59] <OvenWerks> At least the stage now has built in power
[01:59] <Eickmeyer[m]> Oh wow.
[01:59] <OvenWerks> The signals to stage have to go through isolators because there are two power entrances to the building
[02:00] <OvenWerks> The grounds are not close to each other.
[02:00] <Eickmeyer[m]> Oh yeah. I've dealt with that. Hum central.
[02:01] <OvenWerks> The FOH speaker/amps have no power transformer (class D) and if the signal is off DC wise one part of the amp works harder than the other. We lost one that way when we first installed. (warranties are great :)
[02:02] <OvenWerks> we have gone a few years with isolators in line with no troubles
[02:03] <OvenWerks> It just means when things get redone someone who knows what those boxen are for has to be there
[02:04] <Eickmeyer[m]> Yeah, or someone who can figure it out.
[02:05] <OvenWerks> ;)
[02:06] <OvenWerks> so I will be there tomorrow too... we be running mics, monitors and guitar directs under the stage
[02:06] <Eickmeyer[m]> So much fun. :)
[02:06] <OvenWerks> so much less stage clutter.
[02:07] <OvenWerks> Got to find out how much stuff got moved to Paul's house for video feed the last few months.
[03:24] <studiobot> <teward001> Alright who do i have to smack
[03:24] <studiobot> <teward001> *smacks Eickmeyer*
[14:54] <OvenWerks> Eickmeyer[m]: booted to groovy. doing update and it says it is updating "Ardour5" (5.12 -> 6.0) does the package name change?
[14:59] <OvenWerks> Is the new package actually called "Ardour6" has the .desktop file been changed?
[15:00]  * OvenWerks guesses he will find out.... almost soon after 542 updates are done
[15:33]  * OvenWerks needs glasses... arm64 looks too much like amd64
[15:35] <OvenWerks> Eickmeyer[m]: the jack not running dialog works :)
[15:36] <OvenWerks> I have the real time warning? wow
[15:43] <OvenWerks> ardour 6 startup shows: LADSPA: cannot load module "/usr/lib/ladspa/autotalent.so" (/usr/lib/ladspa/autotalent.so: undefined symbol: __exp_finite)
[15:45] <OvenWerks> Eickmeyer[m]: mcpdisp fails the same way in groovy
[15:47] <OvenWerks> if I had to guess which cflag causes this I would expect it to be: -fstack-protector-strong
[15:48] <OvenWerks> which goes well with: buffer overflow detected
[15:52] <OvenWerks> Eickmeyer[m]: I don't know how much c++ you know... but I think local local variables (as in local scope) would be on the stack
[15:54] <OvenWerks> It may be I need to allocate some memory for some things before it starts
[16:20] <OvenWerks> reboot
[18:25] <Eickmeyer[m]> OvenWerks: So, Ardour's package name doesn't change, but the executable name and the desktop file do change.
[21:32] <Eickmeyer[m]> Scratch that, the desktop filename did not change.