[07:45] <zequence> DalekSec: Interesting thread
[07:45] <DalekSec> Thought you'd read it..
[07:46] <zequence> I didn't know about ardour changing their development method as far as branches go
[07:46] <zequence> Also, Adrian is pointing out the problem with how the development model of ardour doesn't work with how debian does packaging
[07:47] <zequence> Jessie just came out, with ardour3, when ardour3 is already EOL
[07:47] <zequence> The answer could be backporting though
[07:47] <zequence> ..all though I'm sure las and other would prefer people used their builds
[07:48] <zequence> Or even doing SRU, since ardour3 is not supported at all anymore
[07:48] <zequence> But you can't SRU ardour3 with ardour4. That becomes weird
[07:52] <DalekSec> Well, it makes sense to not include the major version number in the package name, IMO.
[07:53] <DalekSec> Just like any other software.
[07:53] <DalekSec> Ah, in the past they had issues with backwards compatibility... I see.
[07:58] <zequence> Doesn't seem like anyone has reported a bug on the potential file loss caused by the trusty ardour3 version
[07:59] <zequence> I'm filing one, all though there doesn't seem to be any hard proof of a fix - the ardour people are saying they never found out how it happened, but found some stuff in the code that could potentially cause file loss
[08:00] <zequence> I'm going to file a bug and start a SRU process for ardour3
[08:00] <DalekSec> Niiiiiice.  Good luck.
[08:06] <zequence> Does anyone know how to make a bug only point to certain releases?
[08:11] <DalekSec> Some people can nominate it.
[08:12] <zequence> Ok
[08:40] <zequence> If someone wants to confirm. bug 1450992
[10:49] <zequence> Packages built for testing. Should not be very different from the original https://launchpad.net/~zequence/+archive/ubuntu/sru-testing
[13:11] <OvenWerks> zequence: the ardour3 in 15.04 is the right one (well, latest one)
[13:13] <zequence> OvenWerks: Yep. I'm going to request it to be synced to Trusty and Utopic
[13:13] <zequence> Just need to try a build to make sure it works, but should be fine
[13:14] <OvenWerks> I will go confirm the bug.
[13:14] <OvenWerks> done
[13:16] <OvenWerks> This is a problem with the LTS model in audio. Two years is a long time and the audio SW changes a lot in that time (well some of it)
[13:17] <zequence> Depens on how you see it
[13:17] <zequence> Firefox is updated continuously
[13:17] <zequence> We could set up a similar thing for ardour
[13:18] <OvenWerks> Then it would have to be just ardour, not *3 *4 or whatever
[13:18] <zequence> I've had problems when using updated version of plugins for an ardour project
[13:18] <zequence> OvenWerks: It will be, from now on
[13:18] <zequence> ardour3 will be removed, as will ardour2 and ardour4 will become ardour
[13:19] <OvenWerks> the calf plugins have problems.
[13:19] <zequence> So, I wouldn't want to update anything in the middle of a project anyway
[13:19] <OvenWerks> They look good in their own GUI, but can not be automated properly
[13:20] <OvenWerks> I have tried both ours and DL the latest and built. 
[13:27] <OvenWerks> qmidiroute has a bug too, but it needs to be fixed at the dev level :) One of the config values does not reload properly.
[13:27] <OvenWerks>  I have sent email but not received a response
[13:30] <zequence> Tried the latest ardour3 on trusty, and it seems to work fine. Will setup bzr branches for utopic and trusty and request merges
[13:31] <zequence> OvenWerks: Would you be able to spot the bug in the code?
[13:31] <zequence> Doesn't sound too hard to debug
[13:32] <zequence> We could do a patch, and then send it upstream
[13:32] <OvenWerks> I will look... c++ is not one of my strengths :)
[13:35] <OvenWerks> It was last updated in 2009, which should tell you how often the parameter I tried to use gets used by others...
[13:41] <zequence> ah
[13:42] <OvenWerks> Just going through the change log and it looks like a complete rewrite in 2009.
[14:28] <zequence> I've made merge requests, but the trusty branch has some merge conflicts
[14:29] <zequence> I'll see what the response is before I do anything else