[03:14] OvenWerks: lsp-plugins entering autobuillds (Already, I know!) [03:15] Some of the credit goes to trebmuh for having some of the work done already. :) [12:47] hi Eickmeyer [12:48] question: why removing all the info in d/changelog? [12:48] remark: d/copyright : the licence for "*" needs to be changed to LGPL-3 as it is the current licence [12:49] remark: you need to clean d/rules since you are currently building the package with KXstudio rules [12:51] eg: using pkg-config from /opt/kxstudio/lib/pkgconfig which doesn't sounds good to me while building the package in a Ubuntu chroot context === Ian is now known as Guest26856 [14:31] trebmuh: I had to clean the changelog rather quickly. There were too many epohs. Epochs need to be avoided at all costs. [14:31] I'll put the relevant info back, but overall, the changelog needs a lot of work. [14:32] Yes, the license file needs work. I'm far from done.. [14:33] Also, the rules file builds just fine, so I don't see any reason to clean it too much. [14:33] But, yes, I'lll get rid of the kxstudio reference. [14:33] It's all just very early stages. [14:43] trebmuh: There's nothing in the rules file for using pkg-config from /opt/kxstudio/pkgconfig, so I can't find what you're talking about. [14:45] trebmuh: Oops, was looking at the wrong repo. Disregard. [14:54] trebmuh: Pushed those fixes. Thanks! [17:58] Rosco2: Congrats on the upload rights for the package set!!!!!! [17:58] OvenWerks: ^ [17:58] sakrecoer: ^^ [18:02] \o/ [18:03] Now I have no excuse for not doing any work :-) [18:03] Haha! Well, it was two years in the making and took a lot of pushing and shoving, but you've finally "arrived." [18:04] Possibly 3 years, if you look at the history leading up to it. [18:04] I've been encouraged to apply next, but I think I want to get another package under my belt. [18:05] Thats' why https://launchpad.net/lsp-plugins is now a thing and available in our Autobuilds. [18:08] As long as I am available, there is no hurry. I can now sponsor anything you do in the package set. [18:09] This would be an entirely new package, so I'm going to have to go through the whole MOTU -> Archive Admin process like I did with Carla. [18:09] Of course NEW stuff like lsp-plugins will need a MOTU [18:09] Yes - the Debian path is blocked for a few months [18:10] Nearly done with Hexter in Debian. Can get that synced, although it will need unblocking now we are in Beta. [18:10] Then I will look at x42 [18:11] Okay, cool. Mira Mikes has gone MIA. [18:11] He's got a huge TODO backlog, including x42. [18:11] Yeah - he was prolific, but got busy [18:12] I would like to get some sort of a package tracker set up to monitor our packages [18:12] I think we can all relate. [18:12] I'm trying to think of a way to do that in Launchpad, but I don't know. [18:13] Perhaps the packageset script shows something? [18:13] cyphermox: ^ ? [18:13] You can extract the source packages from the package set in Launchpad [18:14] Then you can interogate launchpad for version in different releases and bugs [18:14] hum, sorry, what is the question? [18:14] you can also interrogate UDD for Debian info [18:14] cyphermox: We're trying to figure out what a good way to get a package tracker set up to monitor our packages. [18:15] ah [18:15] I was wondering if you had ideas. [18:15] I do [18:16] something like this? http://people.canonical.com/~platform/desktop/desktop.html [18:17] Uh, that would be perfect. Rosco2 ^ [18:17] Yes - I had tried mucking about with launchpad-lib from scratch. [18:17] Better to steal something. [18:18] * Eickmeyer figured there had to be something already done [18:18] That looks like a good start :-) [18:18] Rosco2: Eickmeyer: ask seb128 or Laney in #ubuntu-desktop where the script is for this and if you could steal it ;) [18:18] * Eickmeyer joins [18:18] they are both from Europe so they may or may not answer just yet [18:19] grats Rosco2 [18:19] didrocks is also a potential victim ;) [18:20] Rosco2: azbulutlu = eylul- [18:20] I really need to clarify that (or change my telegram name xD) [18:20] Haha [18:22] you asked in public or pm? [18:22] cyphermox: I haven't asked yet. None of those that you mentioned are in the room. [18:22] Thanks :-) [18:22] oh [18:22] And, I've been busy with other pings. They come in waves. :) [18:23] solid point! [18:23] Hehe [18:23] I have a hard time seeing if people are in or out, my part messages don't always show [18:23] (or quits for that matter) [18:23] * cyphermox stabs weechat [18:23] Well, I'm lurking in there, so we'll see what happens. [18:23] ok [18:24] sorry, I can't really help much more, I don't know what generates those [18:24] hm... I could go look though, I might have access :) [18:24] cyphermox: Pointing us in the right direction was perfect, but if you have access.... :) [18:24] Well - we need to concentrate on ISO testing & bug fixing for a bit :-) [18:24] I use Quassel with a separate core on the same server that's running studiobot, so I never really disconnect. [18:25] Rosco2: This is true. Beta is on Thursday. I plan to do a bunch of that stuff today, new computer on the way. [18:25] Not just for testing, but for mutliple uses. The timing is just right. [18:27] This is the first release for a while that I have a play computer [18:27] I have had to be careful for a while not to break my good machines [18:27] * Rosco2 going to find food - it hasn't come to me today [18:27] Eickmeyer: I have enough to tell you the code is here: [18:27] https://code.launchpad.net/~ubuntu-desktop/ubuntu-desktop-versions/trunk [18:28] cyphermox: Okay, perfect. Shouldn't be hard to fork, but then it needs to be hosted. [18:28] Excellent! Thanks cyphermox [18:28] yep [18:29] so; you might still want to ask seb or Laney or didrocks if they can host it for you [18:29] It can go on my people page until we get it working properly [18:29] and if you have changes; submit a merge proposal, I'm sure they'll be happy to review / merge [18:29] it's not only a page though, it's a script that needs to be run [18:29] I just posted in there in general. Hopefully the right people will see. [18:29] if necessary, I'll be happy to host it /after/ I finish rebuilding that server (which needs to happen this week) [18:30] If not, I could always ping them. [18:30] Eickmeyer: Rosco2: you'll still be left with how to see what packages you care about [18:30] either using team subcriptions, if you want to use that [18:30] willcooke just respoded. [18:31] or you could look at edit-acl (https://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/view/head:/edit-acl) to see how to get the list of packages in a packageset programmatically [18:32] the packageset report gets the list of packages from launchpad [18:33] Lot os options! [18:33] of [18:33] * Rosco2 really going to get food before I faint [18:35] Rosco2: the pacakgeset report? [18:35] oh, true [18:35] there's lots of scripts that can do it anyway, since IIRC it's a well-documented API call [18:36] Eickmeyer: do you know who owns ubuntustudio.org? [18:36] Canonical. [18:37] ah? [18:37] Well, I don't have access to it, except the Wordpress front-end. [18:38] Everything has to go through IS, afaik. [18:38] oh, right; the DNS is canonical [18:39] hrm [18:39] so is the hosting, it seems [18:39] I had no idea [19:28] Rosco2: congrats! now just time... [19:35] Eickmeyer: falktx made a good point at LAC. "falktx> stable release with rolling audio audio packages is the best" [19:36] I think this is what we are doing with back ports. However, I think it would be a good thing to document it as such as well. [19:38] Thanks OvenWerks, now maybe we should stop stealing your good work and sponsor your packages. Having three uploaders would be a dream :-) [19:39] That is, rather suggesting people upgrade to "intermeiate releases" have a policy that in general LTS releases (ubuntu repo LST) is the best install. Adding backports for applications to keep up to date [19:40] Rosco2: I am sure uploaders are great. I won't be going there though. I have too much on my plate already [19:41] Sure - but some of your packages got uploaded with only be changing the name. They were already in good shape. [19:42] Eickmeyer: intermediat releases would be considered Beta only. And all work on them would be prep for next LTS... ie no backdrop change or other such "fluff" [19:42] Rosco2: I am not sure what you mean really. The only two packages I think are -controls and -installer [19:43] I do try to keep them clean because they belong to Studio. [19:43] Two packages, but several version were uploaded. No problems. [19:43] cool. [19:43] No pressure :-) [19:45] I have work to do in Ardour as well. I am part way through an Ardour progect that I have left for a few months while working on those packages. [19:45] * OvenWerks finds GUI work hard [19:46] Personally I like the idea of intermediate releases. The work in testing and writing is a small proce for the generation of publicity from an announcement. [19:47] me/ finds any programming slow and hard - but fun [19:49] My personal thought is that if we have the testing "staff" that is fine but I haven't any time for testing for maybe two releases [19:51] intermediate releases are also good for people with new HW that needs kernel support. As such they should work but polish beyond the last LTS is not as important [19:58] Rosco2: I think announcement of a new package available in backports can also be used for publicity as these aften come between releases. [19:58] Eickmeyer: ^^ [20:00] OvenWerks: That's really what we're working toward, IMO. [20:01] I did some fluff this time because, well, I had the time. [20:01] But, the real highlights are the features in -controls and -installer. [20:01] which is fine too as that is work towards the next lts too [20:01] And the inclusion of Crla. [20:01] *Carla [20:02] All of the intermediate releases eventually reach a zenith at the LTS. [20:02] LSP will be in back ports too? [20:02] OvenWerks: That's the plan. [20:02] What I have is a stable release, but I want to get the packaging cleaned-up a bit. [20:03] so upstream -> backports -> release [20:03] One person said I should split-out the lv2, ladspa, and VST plugins into separate packages, but seeing as how we have the infrastructure for all 3 by default (and not all 3 are supported by every DAW), I don't see the point. [20:04] OvenWerks: Bingo. [20:04] so long as the LV1 doesn't crash things [20:04] Really, upsream -> Autobuilds -> Backports (once stable) -> release. [20:05] LV1 shouldn't in this case. We're not talking about Calf here. [20:05] having the ladspa separate still makes sense [20:06] there was another ladspa package that was problematical too: csladspa [20:07] but I think that was ladspa only [20:07] OvenWerks: That's because the version that was pulled from Debian during Bionic was known to be problematic and had a bug fix shortly after. [20:07] has it been backported? [20:07] Nope. [20:08] is it past eol? [20:08] The issue was fixed before Cosmic. [20:08] Bionic is 18.04, so no, it would just need an SRU. [20:09] BUT, I think it was fixed before release but didn't make it into the ISO, so people are filing bugs without updating their system first. I always shudder when I see bug reports for a "fresh install" because it means, typically, they didn't update it. [20:10] Honestly, I don't remember correctly. I do remember participating in a bug report on it and investigating. [20:13] Eickmeyer, Have you heard of the backportpackage tool in ubuntu-dev-tools [20:13] It is really easy to use [20:14] Assume a package makes it into Debian quickly, you don't need to package the new upstream [20:15] Just use the backportpackage tool to backport from the Ubuntu development release [20:15] Assuming Debian reacts fast is not always true though ;-) [20:19] Rosco2: That's really cool. [20:20] * Eickmeyer needs a nap. [23:14] Good afternoon, I have been using Ubuntu for 10 years. and ubuntu studio for 2 years. [23:15] I would like to help where ever I can. I am still very green in development, but maybe in testing or other areas I can help. [23:23] stormchas2000: Thanks for the offer. We're just about to hit our beta testing period, which is testing and bug-squish time for 19.04. Announcement should be Thursday on that, but you're welcome to grab the latest daily ISO and give it a shot at http://cdimage.ubuntu.com/ubuntustudio/dvd/current/ [23:24] Right now, that's the image that should become our beta image if everything goes right. [23:38] Thank you, I will look it over. and as I need help I will ask, since this will be my first time. But i feel that i should start helping out since I have benifited so much with Ubuntu. [23:40] stormchas2000: There's no reason to feel such obligation, but we appreciate the help.