[00:00] <OvenWerks> I may start switching my day to day over to 20.04 this week.
[00:02] <Eickmeyer> I'm going to throw it up to critical.
[00:05] <Eickmeyer> OvenWerks: So, for clarification: Do we need that patch or no? Should I just grab the plugins from that directory?
[00:13] <OvenWerks> robin thinks it should just work so long as it is built on the same lib as we run
[00:13] <Eickmeyer> So, are we talking a simple rebuild or should I patch the plugins?
[00:13] <OvenWerks> we can't just grab binary files
[00:14] <OvenWerks> they have to be source
[00:14] <Eickmeyer> Well, yes. That's not an issue.
[00:14] <Eickmeyer> I'm talking grabbing the a* plugins from the git tree and creating a patch with them.
[00:14] <OvenWerks> if I can get a rebuild to test I can tell.
[00:14] <Eickmeyer> Ok, I'll just do a simple rebuild then.
[00:14] <Eickmeyer> Standby...
[00:16] <Eickmeyer> https://code.launchpad.net/~ubuntustudio-dev/+recipe/ardour-daily
[00:16] <Eickmeyer> That should at least emulate what we're trying to do.
[00:16] <Eickmeyer> I have a patch ready though.
[00:20] <OvenWerks> it says 40 mins to go
[00:22] <Eickmeyer> Yeah, it would be that way whether or not it was a PPA upload.
[01:05] <Eickmeyer> OvenWerks: Build done, waiting for publish
[01:05] <Eickmeyer> You could probably grab it now from https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild/+build/19157297
[01:15] <OvenWerks> so I have to install all three packages?
[01:15] <OvenWerks> guess so.
[01:19] <Eickmeyer> Sadly, yes.
[01:19] <Eickmeyer> No clue why someone decided to split it into three packages since all three depend on each other.
[01:22] <OvenWerks> it did not install correctly
[01:23] <OvenWerks> the main package says it has dependency problems
[01:23] <OvenWerks> even efter installing the other two packages first
[01:24] <Eickmeyer> Oh, that's easy to fix. Just download all three to your ~/Downloads directory, then in that directory, "sudo apt install ./ardour*"
[01:24] <OvenWerks> when I try apt -f install it wants to reinstall the original packages agian
[01:24] <Eickmeyer> The command I just gave you is for installing the local files.
[01:27] <OvenWerks> that didn't help
[01:27] <OvenWerks> trying to remove them first
[01:27] <OvenWerks> do we install the video timeline by default?
[01:27] <Eickmeyer> Yes.
[01:28] <OvenWerks> The following packages have unmet dependencies:
[01:28] <OvenWerks>  ardour-data : Breaks: ardour (<= 1:4.2~dfsg-1) but 5.12.0-0~202003241547~ubuntu20.04.1 is to be installed
[01:34] <Eickmeyer> I'll have to give it a whirl.
[01:40] <Eickmeyer> OvenWerks: I might have to rebuild with a trick in the recipe.
[01:42] <OvenWerks> waht I was able to do still did not install the a-plugins
[01:43] <Eickmeyer> I'm rebuilding the package now.
[01:47] <Eickmeyer> OvenWerks: So, the whole reason it didn't install was because the ~ in the version number makes it less than the actual version number as far as apt is concerned.
[01:48] <OvenWerks> ja, that makes sense
[01:56] <Eickmeyer> Biggest reason: I forgot the epoch (the 1 in front of the colon).
[01:58] <OvenWerks> Looks like it is still not right
[01:58] <OvenWerks> it still says newer version available
[01:58] <Eickmeyer> Yeah, I just started another build.
[01:59] <Eickmeyer> this time WITH the epoch.
[02:10] <Eickmeyer> OvenWerks: Looks like this one will actually install. No "Newer version available" tag.
[02:43] <Eickmeyer> OvenWerks: give it a whirl from this build: https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild/+build/19157446
[02:48] <Eickmeyer> OvenWerks: Same problem exists. Could not be loaded.
[02:48] <Eickmeyer> Might actually need the patch.
[02:48] <OvenWerks> could be. Odd though did the delay line work?
[02:49] <OvenWerks> (a-delay)
[02:49] <Eickmeyer> I didn't try. I tried loading a-compressor.
[02:49] <Eickmeyer> Same issue with a-delay.
[02:49] <OvenWerks> it looks to me that the patch doesn't touch a-delay
[02:50] <OvenWerks> why do they wait till an lts to try new libs?
[02:50] <Eickmeyer> The patch I made does. It grabs the entire libs/.plugins/* from the working tree.
[02:50] <Eickmeyer> I'll try it next.
[02:50] <OvenWerks> and it works?
[02:50] <Eickmeyer> I need to build it first. :P
[02:53] <Eickmeyer> Building now.
[02:57] <Eickmeyer> Well, that completely failed.
[02:57] <Eickmeyer> I'm going to have to figure this out.
[02:57]  * OvenWerks wonders how long that has been broken for
[02:58] <Eickmeyer> Since the no-change rebuild.
[02:58] <Eickmeyer> I'd bet on it.
[02:58] <OvenWerks> I wonder is there is a build flag we can use to make it c++11
[02:59] <OvenWerks> Its probably c++19 or some thing
[02:59] <Eickmeyer> I'm going to continue working on this, then I'm going to yell at people for not notifying any of us of these no-change rebuilds.
[02:59] <Eickmeyer> The failure is due to my patch not applying correctly, meaning it's a bad patch.
[03:00] <Eickmeyer> I basically have to apply the patches one by one, then create another patch.
[03:10] <OvenWerks> it would be interesting to see if ardour 60 builds on this and works
[03:24] <Eickmeyer> Ok, new build in progress.
[03:29] <OvenWerks> how come python doesn't point to anything?
[03:32] <OvenWerks> hmm, python2.7 still exists
[03:33] <OvenWerks> and is not one of the things autoremove wants to take out
[03:33] <Eickmeyer> They want the python version explicitly called-out.
[03:34] <OvenWerks> ok so all the scripts people have been using forever are then broken? seems prtty dumb
[03:34] <Eickmeyer> And, complete FTBFS with my patch. Turns out, the newer plugins don't like the version of waf I have & patched.
[03:35] <Eickmeyer> This might have to be an SRU.
[03:35] <Eickmeyer> I can work on this tomorrow with Robin to show him the issue.
[03:35] <OvenWerks> these are things that should have happened at 19.10... at the latest
[03:36] <OvenWerks> 18.10 would have been better
[03:36] <Eickmeyer> Agreed. I'm going to have a nasty email to the release team about this. This is unacceptable.
[03:36] <Eickmeyer> Upgraded gcc a month before release. Not cool.
[03:45] <Eickmeyer> Aha. Missing autowaf. I can fix that.
[03:58] <Eickmeyer> Rather, the plugins weren't pointing to the custom autowaf. Just patched.
[03:58] <OvenWerks> I wish there was a way to just always install the -dev package for all packages I use
[03:59] <Eickmeyer> If you install the -dev package, it pulls in its base package usually.
[04:00] <OvenWerks> ya, but I want all the dev packages to just install if I have the libs anyway
[04:01] <Eickmeyer> 37 minutes to a build.
[04:02] <OvenWerks> most of that waiting for availablility
[04:03] <Eickmeyer> Nope. It's seriously how long it takes to build the thing: https://launchpad.net/builders
[04:04] <OvenWerks> I guess that makes sense, it takes 12 min here for a straight build without setting up a whole build environment first
[04:06] <OvenWerks> right now I am importing the dev requirements for ardour 6
[04:11] <Eickmeyer> Not gonna lie, I'm excited for Ardour 6. Though, I'm also a bit excited for mixbus 6 which dropped today.
[04:12] <OvenWerks> it appears there is a newer liblv2 than we have too
[04:12] <OvenWerks> 1.17.2
[04:12] <OvenWerks> maybe that is for a different os?
[04:13] <Eickmeyer> Not sure, I'd have to look.
[04:14] <Eickmeyer> Fedora has lv2 1.16.0
[04:14] <Eickmeyer> Ubuntu also has lv2 1.16.0
[04:14] <OvenWerks> ardour looks for 3 different groups of versions and uses which ever one it finds
[04:15] <Eickmeyer> Cool!
[04:19] <Eickmeyer> lv2 github onlyl has a 1.16.0 tag. Strange you found that 1.17.2
[04:39] <Eickmeyer> OvenWerks: Build is ready if you want to grab it: https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild/+build/19157649
[04:41] <Eickmeyer> OvenWerks: Fix works.
[04:46] <OvenWerks> my build of 60 works too.
 @teward001 When you come back to us, critical fix for Ardour at https://code.launchpad.net/~ubuntustudio-dev/+git/ardour, fixes bug 1872555
 I'd upload, but ERR:NoPackageSetYet
[04:49] <Eickmeyer> With that, I'm heading to bed. That was a bit of a rollercoaster.
[05:54] <OvenWerks> Eickmeyer: good night confirm your fix works
[13:39] <teward> Eickmeyer: do you need me to upload something for you?
[13:39] <Eickmeyer> Wow, I just happened to be looking at this when you pinged.
[13:39] <Eickmeyer> https://code.launchpad.net/~ubuntustudio-dev/+git/ardour
[13:40] <Eickmeyer> Fixes bug 1872555
[13:40] <Eickmeyer> teward: ^
[14:18] <teward> cloning fresh since i purged my VCS directories
[14:19] <Eickmeyer> Ok, probably a good idea.
[14:19] <teward> patch fuzz
[14:19] <teward> *finger wags*
[14:19] <Eickmeyer> Wait... what?
[14:19] <teward> dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
[14:19] <teward> dpkg-source: info: if patch '0200-fix-for-a-plugin-failure.patch' is correctly applied by quilt, use 'quilt refresh' to update it
[14:19] <teward> dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/0200-fix-for-a-plugin-failure.patch/ --reject-file=- < ardour.orig.vwGGlI/debian/patches/0200-fix-for-a-plugin-failure.patch subprocess returned exit status 1
[14:19] <teward> dpkg-buildpackage: error: dpkg-source -b ardour subprocess returned exit status 2
[14:19] <teward> oops
[14:19] <teward> 1 moment
[14:21] <teward> ah hang on
[14:22] <teward> yeah this won't debuild
[14:22] <teward> dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
[14:22] <teward> dpkg-source: info: if patch '0200-fix-for-a-plugin-failure.patch' is correctly applied by quilt, use 'quilt refresh' to update it
[14:22] <teward> so either the patch is malformed or it has fuzz
[14:22] <teward> can't figure that one out
[14:22] <Eickmeyer> That's not possible. Something is wrong on your end. I did an autobuild on it which went cleanly.
[14:23] <teward> ah wait interesting
[14:23] <teward> The next patch would create the file libs/plugins/reasonablesynth.lv2/MSVCreasonablesynth/reasonablesynth.vcproj,
[14:23] <teward> which already exists!  Skipping patch.  <--
[14:23] <teward> that's interesting
[14:23] <Eickmeyer> https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild/+build/19157649
[14:23] <teward> that's probably why let me dig
[14:23] <Eickmeyer> The patches have to be applied in order, otherwise you'll get that error.
[14:23] <teward> i know this lol
[14:24] <teward> but it IS applied in the order of `quilt series`
[14:24] <teward> https://paste.ubuntu.com/p/9GPd5fPHfR/ <-- is this the proper patch order?
[14:25] <Eickmeyer> Yes, that's correct. Don't know why it's not building right on your system, it worked in that build I just pointed out.
[14:27] <teward> deploying a 20.04 dev env as well
[14:27] <teward> with my PGP key that I probably shouldn't be cloning off my smartcard
[14:29] <Eickmeyer> I just got the same issue. Dunno why. Might have to remake the patch. >.<
[14:29] <teward> yeah you may have to
[14:32] <Eickmeyer> Strange that it will build cleanly in Launchpad but then has issues locally.
[15:21] <Eickmeyer> teward: This is totally weird. I can run dh_quilt_patch and it runs cleanly. If I run debuild, it fails.
[15:22] <Eickmeyer> I might have to throw an override in the rules file.
[15:25] <Eickmeyer> That's right, it doesn't use debhelper.
[15:26] <teward> Well it needs to run via debuild in order to build proper for debian pckaging so :P
[15:26] <teward> Either way you may have to override
[15:27] <Eickmeyer> Right, but we're using that "classic" way.
[16:12] <Eickmeyer> teward: The problem here is CDBS applies the patches differently.
[16:12] <Eickmeyer> I'm banging my head against the wall here.
[16:13] <teward> sounds like we need ubuntu-devel help xD
[17:11] <Eickmeyer> Carla has now been accepted. We just need the bugfix for Ardour to get accepted, then as long as nothing completely falls apart on us, we're good to go.
[19:30] <Eickmeyer> Ardour uploaded, waiting for acceptance.