[05:02] Huh, I just figgured out that a package can be both in bzr and in git. [05:02] * OvenWerks has uploaded his first git to launchpad... [05:11] Lets see if it will build [05:32] https://launchpad.net/~len-ovenwerks/+archive/ubuntu/ppa [05:34] shows a -controls package built from a new git package. I am trying to decide if I want this version in the wild or if I should do a bit more work first. I am in the middle of making more than one usb device work. [05:35] this version does already include the fix to work with ondemand moved to systemd instead of init.d [05:36] As such, the git version will only be set to build for 18.04 and up. [05:40] I think I will move things one more step before I move it to -devel [05:42] ErichEickmeyer: do you know if we have to get rid of the bzr branch right away, or if it is ok to leave it around for a bit. I am guessing the PPA packages will sit as they were last built. [05:43] also I am not sure if the name of the git branch will show as newer than the bzr branch. if not, I will bump the version number with no release ;) [05:52] We'll go with something that starts with "{debupstream}+git" anyway then, which sorts higher than "{debupstream}+bzr" naturally, so it will be fine. [05:53] Just not quite clear on anything that follows it yet. >_> [05:54] just time... the commit numbers in git are rather long and not in order. [05:55] Yes, but we also already use time at the end, in case of history rewrites - which then would make the version string rather long. [05:57] todays was: ubuntustudio-controls_1.5-0~201805121430~ubuntu18.04.1_all.deb which sorts ahead (or lower) than ubuntustudio-controls_1.5+bzr146+201804061516~ubuntu16.04.1_all.deb [05:57] that is in my ppa, so when I move it to -devel I will add +git [05:59] Btw, the proper namespace for your current repo would be this: lp:~len-ovenwerks/ubuntustudio-controls/+git/ubuntustudio-controls [06:00] Thats what it is. [06:00] Nope, look closer. [06:01] Oh ok... it won't stay long though [06:02] Yeah, but for the main one then. [06:03] Then it'll show up here under Git: https://code.launchpad.net/ubuntustudio-controls - before we switch the project's default VCS, of course. [06:03] right now it is: lp:ubuntustudio-controls which is: https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-controls/trunk [06:03] our git page is https://code.launchpad.net/~ubuntustudio-dev/+git [06:04] That of the dev team, yes. [06:04] I guess I will ask when I get there [06:08] krytarik: this page says the name is right: https://help.launchpad.net/Code/Git [06:08] see in pushing code. [06:08] I could have omitted the /+git/ [06:08] Well, it depends on the scope really - in this case it's not. [06:10] You could change both the owner and set a project here: https://code.launchpad.net/~len-ovenwerks/+git/ubuntustudio-controls/+edit [06:11] For comparison, look at this: https://code.launchpad.net/ubuntu-bots/+git [06:14] * both change [14:48] OvenWerks: To answer your question, looks like it should happen as soon as possible. https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004455.html [14:58] ErichEickmeyer: I am not sure what that message says... [14:59] This is talking about seeds in particular, not other packages [14:59] I think that's all they want migrated at this point. [14:59] ¯\_(ツ)_/¯ [15:00] it seems to say they should all be done may8... last week. [15:00] It says no work is required of the teams [15:00] That would make me expect that someone else was doing the transition. [15:01] Then, I guess we're good, unless we wanna be hipster and migrate before everyone else. That said, I think we should minimize the workload and that it's not a priority. [15:02] I can try to get some clarification if you'd like. [15:04] I don't think we have done our own meta since 16.10ish [15:05] So I don't know the "tooling" they are talking about. [15:06] So anyway from the wiki page they mention, it seems that all the old seed branches are supposed to end up in one git repo [15:06] Well, I just asked tsimonq2 in #ubuntu-flavors what he meant. If you want, I'd join that channel and talk to him directly, he seems to be the one coordinating this. [15:07] Basically, if I were you, I'd join that channel and talk to him directly. [15:07] OK, I certainly have no problem with dealing with seeds in a git format [15:08] ErichEickmeyer: I only have so much time. I will probably not be going through everything we use converting them to git. [15:08] new packages like a desktop-plasma will just gets started as git. [15:09] OvenWerks: I'd do whatever it takes to minimize the impact on your time. [15:09] And, that's not a bad idea. Migrate if you have time, but don't push yourself. [15:09] I'd hardly consider it a high priority. [15:12] the making of meta packages... and iso files is very much some dark art using spells and incantations mere mortals were never meant to understand. [15:19] Just heard back from tsimonq2. Basically, we're waiting on Adam Conrad (infinity) to make the final decision. Until then, we're in limbo with that project, so don't worry about that. [15:20] OvenWerks: ^ [15:26] cool, that was sort of my reading of things. [15:26] git would make managing seeds easier I think. [15:27] I think so too. I know git way better than I know bzr, personally. [15:27] in the long run being able to work with only one revision control toolkit would be nice too. [15:29] I'm off to take the truck into the shop to have the clutch looked at. [15:29] well, I could "look" at it... fix, maybe not [15:31] OvenWerks: Haha! I don't think I could take it across the border. Canada hasn't liked me for about 14 years now. I must've pissed-off a border patrol agent. [15:32] it would be a lot of work for me to say "yep, that there is a clutch all right" [15:34] * OvenWerks needs to rebuild a clutch too, but the weight of the transmition and transfer case is more than I can deal with... and no lift to use either [18:49] http://ubuntustudio.org/2018/05/ubuntu-studio-development-news-may-14-2018 [19:27] ErichEickmeyer: posted to the subreddit [19:27] I'll post it on the mastodon account - just need to know which email address eylul used to create it, as they don't use the username for logins. (didn't think to ask that they other day, lol_ [19:31] slidinghorn: it is eylul@ubuntustudio.org but that is temporary but I forgot to bring this up at the meeting, we should probably have a ubuntustudio.org email that everyone responsible for social media gets the forwards from. Not sure if we have such an account at the moment or not. Devel mailing list is not a good place for it, as this account will also be used for password resets etc. [21:18] SlidingHorn: did you get that desktop file I left yesterday? [21:19] my laptop (on which I run my IRC) froze up last night. I'll pull it from the log tonight [23:02] SlidingHorn: Thanks! [23:04] SlidingHorn: Though, including the link would've been good. :) [23:08] SlidingHorn: Also, I don't know if either of those mods are even active. Might be time for /r/ubuntustudio-official. [23:34] I meant to - somehow forgot :/ [23:34] It's edited w/ the link now [23:35] are the mods part of the old dev crew? We could just see if they'll hand it over [23:49] Well, those accounts haven't been active in months if not years. If they hand it over, sure. Otherwise, we'd have to start a new subreddit.