[00:00] <kc2bez[m]> Quickget, which is part of quickemu uses zsync for isos that support it.
[00:01] <arraybolt3[m]> And this begins the battle of the hypervisors.
[00:01] <arraybolt3[m]> s/this/thus
[00:01] <kc2bez[m]> Hahaha
[00:01] <kc2bez[m]> I like vim too ;)
[00:01] <arraybolt3[m]> 🤯
[00:02] <arraybolt3[m]> I tried that once, it was... well, a bit too much to learn at the time.
[00:02] <arraybolt3[m]> I'm still on Nano, Kate, and GEdit.
[00:02] <arraybolt3[m]> (And VSCode.)
[00:02] <kc2bez[m]> I honestly very pragmatic. Use what works for you.
[00:03] <arraybolt3[m]> I would love to love Vim, and maybe one day I'll try it again. It was fun to learn.
 "You can literally give it an ISO..." <- If it's a file:/// URL does that work?
[00:04] <kc2bez[m]> It takes some solid time in seat to get comfortable with anything.
[00:04] <arraybolt3[m]> True. My transition from hunt-and-peck typing to touch typing made me slow down dramatically, but now it's way faster.
[00:05] <tsimonq2> arraybolt3[m]: Yeah that too
[00:06] <arraybolt3[m]> **Really?**   If you're 20 and graduated from college then you'll probably use Cockpit."
[00:08] <tsimonq2> LMAO
[00:14] <arraybolt3[m]> OK this is pretty cool so far.
[00:14] <arraybolt3[m]> (Using Cockpit to test the new Calamares on Ubuntu Studio.)
[00:17] <arraybolt3[m]> Simon Quigley (Developer): Well, once again, you've earned a convert to your software setup.
[00:17]  * arraybolt3[m] uninstalls GNOME Boxes
[00:17] <arraybolt3[m]> First Matrix and now Cockpit.
[00:20] <kc2bez[m]> > <@tsimonq2:linuxdelta.com> My boss (Noah of asknoahshow.com and Linux Action Show) once described it like this in an IRL meeting...
[00:20] <kc2bez[m]> >
[00:21] <kc2bez[m]> > "People who look like you, have a beard, and write your code in Vim, probably use virt-manager or virsh. If you're 20 and graduated from college then you'll probably use Cockpit."
[00:21] <kc2bez[m]> I guess that is fairly true. I've used my share of virsh too.
[00:29] <arraybolt3[m]> Simon Quigley (Developer): Hey, how close are we to looking over the Calamares SRU? (I hate to be in a hurry, but I won't be available after about 8:15, so if there's anything else that needs done to it, I'll need to know before then.)
[00:31] <guiverc> railer77gg
[00:31] <arraybolt3[m]> guiverc: ?
[00:32]  * guiverc busy changing something
[00:33] <arraybolt3[m]> Well, sadly, I'm back on GNOME Boxes. Cockpit kept pausing my VM mid-installation while I was fiddling with it, and the graphics were so bad (which sounds like not a big deal, but when the whole UI freezes while you're trying to install an OS in a hurry, it's a big deal). Sure looked cool, though, and I'll keep it around. Maybe it's just not for my particular computer.
[00:45] <arraybolt3[m]> Ubuntu Studio also installed and worked with Calamares 3.2.60.
[00:52] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Ready for roast time?
[00:52] <arraybolt3[m]> OK.
[00:52] <tsimonq2> Why delete this debian/calamares.1
[00:52] <tsimonq2> And this debian/calamares.manpages
[00:53] <tsimonq2> Just getting you warmed up...
[00:53] <arraybolt3[m]> Because Calamares upstream provides a manpage already.
[00:53] <arraybolt3[m]> Having two manpages for the same app in different spots could confuse the end user.
[00:54] <tsimonq2> Standard formatting of bug mentioning is (LP: #123456)
[00:54] <tsimonq2> Surround with parentheses
[00:54] <arraybolt3[m]> Ah, didn't realize that. Fixing.
[00:54] <tsimonq2> You didn't create the signing key yourself, where did you get it from?
[00:55] <arraybolt3[m]> OK, so first I downloaded the asc file from upstream's GitHub. Then I used GPG to get the key ID, and pulled it from the keyserver, then exported it with "gpg --export --armour".
[00:55] <arraybolt3[m]> s/armour/armor/
[00:56] <arraybolt3[m]> I verified that it works using "uscan --download-current-version".
[00:57] <tsimonq2> Yes, so summarize that in the changelog please
[00:57] <arraybolt3[m]> OK.
[00:57] <tsimonq2> What's up with the weird differences between tabs and spaces in the copyright file?
[00:58] <arraybolt3[m]> Eh? Didn't notice those, I'll look at it.
[00:58] <tsimonq2> Oh your watch file flat out doesn't work
[00:58] <arraybolt3[m]> (I copypasted copyright data from within Calamares itself, so that may be the problem.)
[00:58] <arraybolt3[m]> tsimonq2: Not possible, it works on my end.
[00:59] <arraybolt3[m]> (uscan --download-current-version works.)
[00:59] <tsimonq2> End of line 3 of your changelog
[00:59] <tsimonq2> s/changelog/copyright/
[01:00] <arraybolt3[m]> Hold on, looking at it, I'm not even seeing a tab.
[01:01] <arraybolt3[m]> Simon Quigley (Developer): Where is the tab? End of line 3 on the copyright, I'm not seeing anything weird in particular.
 https://matterbridge.lubuntu.me/d0347436/file_5637.jpg
[01:02] <arraybolt3[m]> Argh, just figured out how to get Nano to show them. My copypasting of copyright data for maximum accuracy backfired. Sorry, fixing...
[01:03] <tsimonq2> Also you are not consistent with comma vs not in the entries you add
[01:03] <arraybolt3[m]> That was a leftover from the previous copyright file, repair it?
[01:04] <tsimonq2> Instead of "fixed a flaw" in the changelog it should be a short summary of the flaw you fixed
[01:04] <arraybolt3[m]> Even though the summary is immediately underneath it?
[01:04] <tsimonq2> arraybolt3[m]: Yes, ONLY the ones you add though
[01:05] <tsimonq2> arraybolt3[m]: Same rationale for package descriptions in control
[01:05] <arraybolt3[m]> Hold on, going too fast, gimme a sec...
[01:05] <tsimonq2> One line summary then a couple lines below expanding
[01:05] <tsimonq2> All good
[01:09] <arraybolt3[m]> OK, back.
[01:11] <arraybolt3[m]> Simon Quigley (Developer): OK, I fixed everything you mentioned and pushed to Git.
[01:11]  * tsimonq2 takes out Elon Musk's flamethrower
[01:12] <tsimonq2> We're not done here yet :P
[01:12] <arraybolt3[m]> Of course, but everything behind us is fixed.
[01:12] <arraybolt3[m]> Or burnt, depending on how you want to look at it :-P
[01:13] <tsimonq2> Should be `SRU (LP: #929292).` with the period *after* :P and the period before your sub-bullet should be a colon.
[01:13] <arraybolt3[m]> Sub-bullet?
[01:13] <arraybolt3[m]> Like "- Reasoning:"?
[01:13] <arraybolt3[m]> Rather than "- Reasoning -"?
[01:13] <tsimonq2> If you use `Reasoning -` instead of a colon it may confuse some automation
[01:13] <tsimonq2> arraybolt3[m]: Yes
[01:14] <tsimonq2> But I mean at the end of the main bullet point line before your last sub-bullet
[01:16] <arraybolt3[m]> OK, ready for flamethrower.
[01:16] <arraybolt3[m]> Simon Quigley (Developer): ^
[01:16] <tsimonq2> Explain every part of the version to me and why you chose it
[01:16] <arraybolt3[m]> OK, hold on, pulling up docs so my reasoning makes sense...
[01:17] <arraybolt3[m]> According to the StableReleaseUpdates wiki page, "The version number does not conflict with any later and future version in other Ubuntu releases (the security policy document has a well-working scheme which can be used for SRUs.)" So I followed the link to the security policy document, and it said...
[01:18] <arraybolt3[m]> In the rare case of a new upstream release being pushed to all stable releases (substitute for 12.04 in the version string):
[01:18] <arraybolt3[m]> NOTE: This is for an upstream only update, not a backport of the development release package
[01:18] <arraybolt3[m]> [01:18] <arraybolt3[m]> (Wow that's one ugly table.)
[01:19] <arraybolt3[m]> So I used that format. Upstream release is 3.2.60, and it is a new upstream release to 22.04, so it's now 3.2.60-0ubuntu<IP_ADDRESS>.
[01:19] <arraybolt3[m]> (I am noticing a potential problem...)
[01:19] <arraybolt3[m]> Simon Quigley (Developer): ^
[01:20] <arraybolt3[m]> That was the only example the document provided for a new upstream release, and since it was an upstream-only update and not a backport of the development release package, that's what I used.
[01:21] <tsimonq2> arraybolt3[m]: What's the problem? I don't see one
[01:22] <arraybolt3[m]> It was "all stable release", this is going into Jammy only.
[01:22] <arraybolt3[m]> (I mean, the formatting is for an update into all stable releases.)
[01:22] <arraybolt3[m]> So I'm wondering if maybe there's some different formatting for when it's only going into one stable release... or is it going into all stable releases?
[01:23] <tsimonq2> There is one other correct potential version
[01:24] <arraybolt3[m]> Which is? (Sorry, I'm not figuring it out from the security updates doc.) Simon Quigley (Developer)
[01:25] <tsimonq2> > <@arraybolt3:matrix.org> [01:25] <arraybolt3[m]> Ah, leaving off the .60. OK.
[01:25] <arraybolt3[m]> But we've included the minor version number before, so I think it should stay.
[01:26] <arraybolt3[m]> (Indeed, we've never left the minor version number off that I can see.)
[01:26] <arraybolt3[m]> Simon Quigley (Developer): ^
[01:27] <tsimonq2> Nope
[01:27] <tsimonq2> Don't modify the upstream part at all
[01:27] <tsimonq2> You're simply removing the release version number
[01:27] <arraybolt3[m]> Oh wait, I noticed the wrong part of your example.
[01:28] <arraybolt3[m]> So I should do that?
[01:28] <arraybolt3[m]> (Removing the release version number?)
[01:28] <arraybolt3[m]> (And now I finally see the spot in the document that shows where I can do that. OK, that satisfies all the rules I can see.)
[01:29] <arraybolt3[m]> 2.0                           2.0ubuntu0.1
[01:30] <arraybolt3[m]> (Which looks like a typo in the document possibly? Now I'm really confused. I'm just going to do what you said and go with it.)
[01:33] <arraybolt3[m]> Simon Quigley (Developer): OK, pushed to Git again and awaiting the next needed fix.
[01:35] <tsimonq2> LGTM. Did you get to the SRU paperwork yet?
[01:35] <arraybolt3[m]> Simon Quigley (Developer): Not yet, and sadly, due to extenuating circunstances, I don't actually have the time to do that (I have to leave in about 5 minutes). It is awful if I leave that for you?
[01:37] <tsimonq2> arraybolt3[m]: We can shoot for Monday to get you practice
[01:37] <arraybolt3[m]> OK, sounds good. Sorry to run out of time just at the very end.
[01:37] <tsimonq2> All good
[01:38] <arraybolt3[m]> Whew, that was a lot! Thank you for teaching me all that, that was awesome. \o/
[01:46] <tsimonq2> Of course :)
 I don't know I ever quite groked how translations worked
 the translations platform we wanted to set up a long while ago couldnt be set up due to infra restrictions at DO and then because CI ate everything it exhausted my resources too
 so we never really set up a translations platform that worked
 then Simon went awol and it went into the depths so :P
 sup folks...i installed the daily and enabled non-released updates....so if you need someone to test some thing on intel based hardware, lemme know


[01:58] <ovnicraft> hello there is any clue in your roadmap about comments in blueprints ?
[01:58] <ovnicraft> or now how i can do it ?
[01:58] <lifeless> later this year we plan to fold blueprints and bugs together into a single issue tracker
[01:59] <lifeless> that will give you a place to have discussions about specification
[01:59] <ovnicraft> i see the whiteboard but is too stupid, users can delete texts added by others
[01:59] <ovnicraft> that sounds good
[02:00] <ovnicraft> so i think that concept now is imposible in lp
[02:00] <ovnicraft> developers cant have their space
[02:00] <ovnicraft> there is any specification where i can read ?
[02:01] <lifeless> dev.launchpad.net/IssueTracker I think
[07:41] <lag> Any skilled LP people with admin rights available to help me out?
[07:42] <lag> I've given a project to the wrong person and I need it changed pronto
[07:48] <wgrant> lag: There probably won't be any admins around for another hour or so.
[07:48] <wgrant> lag: Could you ask at https://answers.launchpad.net/launchpad/+addquestion?
[07:49] <lag> wgrant: I'm fairly sure I'm going to need an admin to correct my fopar
[07:49] <wgrant> lag: Or the person you gave it to, yes.
[07:49] <wgrant> lag: Ask a question at the URL I gave, and I'll poke an admin to deal with it when they awake.
[07:53] <lag> wgrant: https://answers.launchpad.net/launchpad/+question/146667
[07:57] <wgrant> lag: I've assigned it to the LOSAs.
[07:58] <lag> wgrant: Great, thanks
[08:01] <mok0> Hm, I am suddenly in doubt... can the Vcs-Brz: field in debian/control list the url as lp:~mok0/.... ?
[08:01] <wgrant> mok0: It should ideally list the official packaging branch.
[08:01] <wgrant> But that has nothing to do with Launchpad (yet?)
[08:01] <wgrant> We don't interpret the field at all.
[08:02] <mok0> wgrant: I know
[08:02] <mok0> wgrant: I don't maintain my packages in the main ubuntu branch
[08:04] <mok0> wgrant: what I meant, do I need to expand the "lp:" to a URL?
[08:05] <wgrant> mok0: It is already a URL. It's one that's only recognised by Bazaar, but it is still a URL.
[08:05] <wgrant> You should not have to expand it.
[08:05] <wgrant> I don't know what uses it.
[08:05] <mok0> wgrant, thanks.
[08:06] <mok0> wgrant: Isn't it used in LP to cross-reference?
[08:07] <wgrant> mok0: Not yet.
[08:07] <wgrant> It may be once we are building from branches natively.
[08:07] <mok0> wgrant: ah, ok
[08:07] <wgrant> But that is a while off.
[08:09] <mok0> wgrant: are you formally involved in LP development now?
[08:09] <wgrant> mok0: Yup, I started full-time in December.
[08:09] <mok0> wgrant: congrats!!
[08:10] <wgrant> Thanks!
[08:11] <mok0> wgrant: what kind of work do you do?
[08:12] <lifeless> the shadow knows
[08:13] <wgrant> mok0: I was initially working on Soyuz, but a month ago the team was restructured.
[08:13] <wgrant> So what lifeless says holds, basically.
[08:13] <mok0> Life in the shadow... complete freedom
[08:13] <mok0> :-)
[08:32] <gnomefreak> i was adding info to a bug report using apport-collect and answered all its question than after giving Lp access to update/change my bug report it is stuck on the "Almost Finished" page its been a few minutes now and it has not added info to the bug yet. should i start the process over again? it seems its LP not apport to me
[08:42] <wgrant> gnomefreak: Is apport not asking you to click a button to say you've done that?
[08:45] <gnomefreak> wgrant: after i allow acess i get nothing. i refreshed the web page that said almost done and it gave me an OOPS
[08:46] <gnomefreak> im going to try one last time, and ill let you know if it worked
[08:47] <wgrant> gnomefreak: It's not on a web page.
[08:47] <wgrant> gnomefreak: It's somewhere in apport.
[08:48] <gnomefreak> oh. well this time it didnt even bring up the webpage, so i guess it makes sense
[08:48] <gnomefreak> i guess ill add apport to my list of bugs to report. thanks wgrant
[09:10] <gnomefreak> wgrant: thanks it does seem that apport is crashing, i filed the bug on it.
[09:33]  * smokex is busy probably writing code: Gone away for now
[11:44] <hannie> jtv, my problem with the LoCo Directory is still not fixed. Any idea what's wrong?
[11:50] <jtv> hannie: last I heard, it was still a mystery!  The error that we found only seemed to affect one or two users.  jcsackett may know more.
[11:51] <hannie> ok
[11:51] <wgrant> What's the issue?
[11:51] <wgrant> Your team memberships and username aren't showing up in the LoCo directory?
[11:52] <jtv> wgrant: no, some "can't connect to LP server" errors (no oopses) when submitting translations.
[11:52] <wgrant> Ah.
[11:52] <jtv> The crazy thing is, that shouldn't depend at all on what exactly you happen to be doing afaict
[11:52] <jtv> It's normally a systemic problem.
[11:53] <jtv> hannie: the best guess we had last night was that RawChid and you might be behind the same proxy, but that seemed unlikely… any chance that it's the same provider though, and they might be doing something weird?
[11:54] <hannie> today is a new day ;)
[11:56] <hannie> jtv, we both log in at Launchpad. I do not see a connection with our providers
[11:56] <jtv> grr
[11:57] <hannie> It is a problem, because if today it still is not working, then well will it work?
[11:57] <jtv> Yes.  :(
[11:58] <hannie> Should I contact Danilos or David Planella about this?
[11:58] <jtv> Well that's the annoying thing: this isn't even translations-specific AFAICT.  Did you try submitting other forms, e.g. searches?
[11:58] <hannie> btw this suggestion is not a lack of confidence in you
[11:58] <jtv> No worries.
[11:59] <hannie> I have nog problem at all with other packages in LP
[11:59] <jtv> So even translating worked!?
[11:59] <jtv> For other packages?
[11:59]  * smokex is busy probably writing code: Gone away for now
[11:59] <hannie> Translating works, but if I can't save it, it is a waste of time
[12:00] <jtv> Of course.  But you were able to submit your translations to another package without the same problem?
[12:00] <hannie> jtv, yes, I worked in gcalctool simultaneously and saving there was no problem
[12:01] <jtv> That's… interesting.  And what package didn't work?
[12:01] <hannie> LoCo Directory
[12:01] <hannie> https://translations.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/
[12:02] <hannie> ...doesn't or not didn't ):
[12:02] <hannie> #not
[12:03] <jtv> Okay, I'll see if I can find anything weird about that then.  (It'd have to be very weird!)
[12:05] <jtv> hannie: do you get the same problem on our staging server?  https://translations.staging.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/
[12:05] <hannie> jtv, I found something!!!!!
[12:05] <jtv> ?
[12:05] <hannie> just a sec
[12:06] <hannie> I had filtered on the word "mondiale" because it should be substituted by "wereldwijde"
[12:07] <hannie> I have removed the filter, then translated another untranslated string and guess what...
[12:07] <hannie> it is saved!!!
[12:08] <hannie> So now I am going to try and save a string with the word "mondiale" in it.
[12:09] <hannie> With filter I mean of course the Search box
[12:10] <jtv> hannie: it's know that the search filter doesn't interact well with the translated/untranslated/… filter, but this is unexpected.
[12:11] <jtv> s/know/known/
[12:12] <hannie> ok, so that may have been the problem. I am now trying a string with "Mondiale"
[12:13] <hannie> Right, as soon as I use the word "mondiale" in the search box I get the error message
[12:13] <hannie> Finally I am going to try and change the same string, but without "mondiale" in the search box
[12:16]  * smokex is busy probably writing code: Gone away for now
[12:16] <hannie> jtv, it is still not working when I change a string with the word "mondiale" in it, even
[12:16] <hannie> when I empty the Search box and show all items
[12:17] <maxb> smokex: Automatic away messages on public channels are a bit intrusive
[12:17] <jtv> hannie: so the search filter wasn't related after all?
[12:17] <hannie> No it seems to be the word "mondiale"
[12:18] <hannie> I did hear Rawchid mention something about a script that did not word in LP, so
[12:18] <hannie> I wil contact him about this this afternoon. thanks for your help so far
[12:19] <hannie> #work
[12:19] <jtv> Thanks for helping figure this out.  Do try the same thing on the staging server, to see if it breaks there.  I'll see if I can figure out anything weird about the data.
[12:19] <hannie> jtv, what is a staging server?
[12:19] <jtv> It's a copy of Launchpad for experimenting in.
[12:20] <jtv> Its equivalent of the problem page is https://translations.staging.launchpad.net/loco-directory/trunk/+pots/loco-directory/nl/
[12:20] <jtv> (note the "staging")
[12:20] <hannie> ok, I'll have a look
[12:20] <jtv> I have to go take care of something urgent now.
[12:21] <hannie> bye
[15:38] <jtv> hannie: the good news is, I may have found the errors that have been hitting you.  The bad news is, it may be complicated and I still don't understand why it didn't give you an oops id.
[15:40] <hannie> jtv, I am playing in staging server now
[15:40] <jtv> Any different?
[15:40] <hannie> yes, I am investigating
[15:40] <jtv> (By the way, bear in mind that the data on that server is disposable—don't do "real" work there)
[15:41] <jtv> (Sorry if I keep repeating that, just want to be really really sure not to waste your work :)
[15:41] <hannie> #24 could not be altered in LP, but in 24 I see the word "mondiale" has been replaced by "wereldwijde
[15:42] <hannie> jtv, I understand. I only use it for experiments
[15:42] <jtv> OK
[15:43] <jtv> It's probably not the word "mondiale" as such; none of the interesting code cares about what exactly is in the strings.  But something unusual may have happened to those strings.
[15:44] <hannie> jtv, feedback: I can save in staging.lp.net
[15:44] <jtv> whoa
[15:44] <jtv> that's interesting
[15:44] <hannie> ah, tell me
[15:44] <jtv> but maybe the old, bad translations aren't in staging yet
[15:44] <jtv> (staging runs on slightly older copies of the database)
[15:45] <hannie> I think the string I just changed in staging was new
[15:45] <jtv> So no translation for it yet, in staging?
[15:45] <hannie> Only a suggestion
[15:46] <hannie> The 'old' suggestion (mondiale) is not present in staging, but it is in LP
[15:46] <jtv> That matches what I'm seeing…
[15:47] <hannie> And in LP I cannot change mondiale to wereldwijd because I get the error message there
[15:47] <jtv> The errors I found say that probably, the code tried to make a new message the current one without disabling the old one first.
[15:47] <jtv> If there is no old one, that would probably not happen.
[15:48] <hannie> In LP: Current Dutch = Gerelateerde mondiale activiteit
[15:48] <jtv> What I think is happening is that the code does disable the old message, but the activation of the new one gets flushed out of the ORM cache before the deactivation of the old one does.
[15:48] <jtv> (By the way yes, "wereldwijd" is much better :)
[15:48] <hannie> In staging: Gerelateerde wereldwijde activiteit, I just changed it to Current Dutch
[15:49] <hannie> Troubleshooting is fun, as long as you find the answer in the end ;)
[15:49] <jtv> heh
[15:49] <jtv> it can get a bit frustrating, too :)
[15:49] <hannie> yep, like now
[15:50] <hannie> But I do appreciate your help very much
[15:51] <jtv> hannie: and vice versa…  I just confirmed: we're just not telling the ORM "when you write our changes to the database, please write this one first or there'll be trouble."
[15:51] <jtv> So I'll go and fix that, and hopefully we can have the fix in production tomorrow.
[15:51] <hannie> right
[15:52] <hannie> What is ORM?
[15:52] <jtv> hannie: Object-Relational Manager.
[15:52] <hannie> ok
[15:52] <jtv> It's a software layer that lets you do object-oriented programming with what's actually relational database items underneath.
[15:53] <hannie> I'll check again tomorrow. thanks for your time and help so far
[15:53] <jtv> Turns out this was a known problem that we never got to the bottom of!  Bug 708385
[15:55] <jtv> I'll be attaching my fix (or "branch" really) to that bug ticket.
[16:19] <jploz> Hello. Hopefully, I'm in the right channel for my question.
[16:20] <jploz> It is about how to handle bugs and fixes in different Ubuntu versions.
[16:24] <jploz> Consider following szenario: a bug was reported against a package in universe. The bug also affects the upstream project, so it was added as also affected. Then a upstream release which fixes this issue was published and uploaded to Natty.
[16:25] <micahg> jploz: #ubuntu-motu would be better for this
[16:27] <jploz> micahg: Ok, I'll try there. Many thanks and bye.
[16:33] <JFo> wgrant, lifeless any update on my oops? It is hampering my ability to approve nominations for several CVE bugs.
[16:34] <JFo> Error ID: OOPS-1880K1665
[17:02] <jtv> RawChid: fix for that translation problem you were hitting (I hope!) is in review.  See bug 708385.
[17:11] <jcsackett> JFo, that OOPS appears to be tied to bug 723999, if you want to follow along on progress there.
[17:12] <JFo> ah, thanks jcsackett :)
[17:32] <dpm> hi launchpadders. I've just pushed a +junk branch and I got some weird output: http://paste.ubuntu.com/571820/ - is the "/~sathishmanohar/junk/main at lp-85632016" message to be expected?
[17:32] <dpm> I just found it a bit confusing...
[17:33] <james_w`> dpm, that's very odd
[17:33] <dpm> that was my thought :)
[17:35] <james_w`> dpm, jcsackett should be able to tell you if you should file a bug or not
[17:35] <james_w`> dpm, but I would suggest it
[17:35] <dpm> ok, thanks james_w`
[17:36] <jcsackett> dpm: i can't think of any valid reason you're junk branch should be stacked on another junk branch.
[17:36] <jcsackett> i'm checking to see if it does that for me as well.
[17:38] <dpm> jcsackett, ok, just let me know if you need me to file a bug
[17:39] <CarlFK> Package has already been uploaded to CarlFK-ppa on ppa.launchpad.net; Nothing more to do for dvswitch_0.9~alpha-0.5ubuntu1_source.changes
[17:39] <CarlFK> but it got rejected, guessing because I capped my username: CarlFK, when it should be carlfk
[17:40] <bigjools> dput -f
[17:40] <CarlFK> bingo.  thanks
[17:40] <RawChid> jtv, great to hear that. IS there more info on what the problem was? (I'm just curious)
[17:40] <jtv> sure
[17:40] <CarlFK> "Successfully uploaded packages."  - I figured there was something like that.
[17:40] <jcsackett> dpm: just notice, you pushed a branch for the junk project, not your junk (junk, not +junk).
[17:41] <leonardr> tumbleweed, bdrung, i've now contacted all the developers i could find. i'm going to send out an email to the tech list, and then i can do some work on upgrading u-d-t
[17:41] <dpm> jcsackett, ah, yeah, I've just seen I missed the '+'
[17:41] <jcsackett> dpm: looks like you are not alone in that.
[17:41] <jtv> RawChid: each translation, including suggestions, is recorded in the database as a "translationmessage" (or TM for short).  In a given translation, for a given msgid, zero or one TMs can be "current," which means they're the current, official, actual translation.
[17:42] <jtv> RawChid: When you change an existing translation, the code does two very sensible things:
[17:42] <dpm> jcsackett, ok, I'll just delete the branch. Thanks!
[17:42] <jcsackett> dpm: you're welcome.
[17:42] <jtv> RawChid: first, it removes the flag from the old message, so that it's no longer current.  Then, it sets the flag on the new message.
[17:42] <jtv> RawChid: and it has to happen in this order, because only one message at a time can be current.
[17:42] <bdrung> leonardr: tumbeweed began some work in lp:~stefanor/ubuntu-dev-tools/launchpadlib-1.9
[17:42] <jtv> RawChid: _however_ we weren't telling the ORM that those changes had to be sent to the database in that exact order.
[17:43] <jtv> RawChid: —and so sometimes, it would start with making the new message current and then make the old message not-current later.  Which isn't allowed, because in the meantime there are 2 current messages.
[17:43] <leonardr> ok, i'll take a look once i write the mail
[17:44] <jtv> RawChid: …so I added some hints to the ORM to say that the changes need to go out to the database in the right order.  If you're interested in the actual code changes, find the part with my branch and click on the Approved link.
[17:44] <jtv> RawChid: ahem.  I mean: go to the bug, and _there_ find the part with my branch etc.
[17:49] <RawChid> Thanks for the info! Sounds interesting. I'll take a look at the code now
[17:53] <timrc> When I attempt to change a PPA from public to private, I almost always get a 402 when I call lp_save() and the one time lp_save() did succeed, the change was not reflected on the web... http://pastebin.com/DGQHzHQt -- any obvious things that I'm doing wrong?
[17:54] <bigjools> you can't change privacy
[17:54]  * timrc slaps Cody
[17:54] <timrc> (if he were here :))
[17:55] <bigjools> well, you can't change it unless a) you're an admin, and b) there are no packages in the PPA
[17:55] <timrc> bigjools: ah ok, I'm an admin, so that's not the reason, but it requires packages... that's odd that that's not a requirement for making a PPA private through the web
[17:56] <timrc> web interface^
[17:56] <bigjools> it is, actually
[17:56] <bigjools> the checks are done at a low level
[17:57] <timrc> bigjools: I've created PPAs on a private project and set them to "private" before there were any packages in them, though...
[17:57] <bigjools> yes, you're not allowed to have packages :)
[17:58] <timrc> oh misread, the ppa has to be empty to set it private and I have to be admin
[18:05] <timrc> bigjools: so what of the 502's and 503's I get pretty much every time I call lp_save()? Bad Gateway and Service Unavailable do not seem like appropriate responses if I'm failing due to permissions problems
[18:07] <timrc> it doesn't seem to matter if I'm using 'edge' or 'production'
[18:08] <bigjools> sorry I have to go now, if you think it's wrong please file a bug and someone from the maintenance teams will triage it
[18:10] <lifeless> timrc: you should not be using edge anymore
[18:11] <sinzui> timrc: projects do not have ppas. You do though
[18:12] <dpm> jcsackett, I've got another issue with lp and bzr if you've got a minute: I'm trying to check out a branch on the canonical people server, and I'm getting this: http://paste.ubuntu.com/571831/ - I had the same problem a couple of weeks ago, but after several retries it ended up working. Any ideas what could be happening here?
[18:16] <jcsackett> dpm: sadly, i have no better explanation than sometimes codehosting gets heavy load. :-/
[18:16] <dpm> jcsackett, ok, no worries, thanks anyway
[18:17] <timrc> lifeless: okay, I think it's an artifact of looking at examples on the web which use it
[18:17] <timrc> sinzui: If I try to create a PPA on myself and then set it to private and lp_save(), I get a 502/503
[18:18] <timrc> sinzui: oh but yeah, thanks for the correction... I create a ppa on behalf of a 'team' for a project :)
[18:18] <lifeless> timrc: if those examples are on a wiki; change em ;)
[18:19] <sinzui> dpm: it works for me. can you do that from another machine? is port 22 really open on that machine
[18:20] <sinzui> timrc: I believe the only people who can set a ppa private is an admin or a commercial admin. So I think you should get a 403 when calling save for a the privacy bit
[18:22] <sinzui> This may be difficult because the you do have permission to use lp_save(). The someing, maybe in lp's API infrastructure needs to identify that the property is the issue
[18:22] <lifeless> sinzui: we should allow folk with commercial entitlements to do it themselves
[18:22] <timrc> I'm a commercial subscription admin
[18:22] <sinzui> lifeless: was say that a lot. Someone just has to pay for that to happen
[18:22] <lifeless> sinzui: well, we can start small :)
[18:23] <lifeless> sinzui: is there a bug for this?
[18:23] <sinzui> lifeless: timrc does not have a commercial entitlement by the way. we only provide that for projects with proprietary licenses. So there is another chunk of work someone must pay for before we fix the other part
[18:24] <lifeless> sinzui: timrc isn't the case I thought it was then :) - but anyone in canonical could be granted commercial entitlement from ~canonical, if we wanted to.
[18:24] <lifeless> that would be fairly cheap to do, no?
[18:28] <sinzui> lifeless:  there is no bug for this feature. I think one of my emails I sent in the privacy/disclosure email would form that basis of the issue and what we could do
[18:29] <dpm> sinzui, it worked well yesterd
[18:29] <dpm> sorry, pressed return too quick
[18:30] <sinzui> lifeless: timrc one option was to allow ~canonical members entitlement by default. I gave them power to create project and teams that start with 'canonical-' last month by the way
[18:30] <dpm> sinzui, the same bzr branch command worked well yesterday from this same machine, so I'm assuming that the port did not just get closed
[18:31] <jcsackett> dpm: you were invoking this on people.canonical.com, right?
[18:31] <timrc> sinzui, lifeless: I work in oem, we're trying to automate our project creation process and one component of that is programatically creating the private ppa for the project
[18:31] <dpm> jcsackett, yeah
[18:31] <jcsackett> i was able to do it from there a moment ago, dpm, sinzui.
[18:31] <sinzui> timrc: a noble effort. I wish we could connect that ppa to the project so it was easy to find.
[18:32] <sinzui> dpm: can you pastebin your script? I want to play a fragment to reproduce the bug
[18:33] <dpm> sinzui, it's not a script, I was just invoking http://paste.ubuntu.com/571831/ on the command line
[18:33] <timrc> sinzui: yeah, as it is all ppas live with ~oem-archive
[18:34] <sinzui> oops. too many users: timrc can you pastebin your script? I want to play a fragment to reproduce the bug
[18:34] <timrc> sinzui: http://pastebin.com/DGQHzHQt
[18:39] <sinzui> wow this scripte takes some time to run. It feels like the packets are being routed though Cleaveland
[18:39] <timrc> sinzui: my script?
[18:39] <sinzui> timrc: yes. I just code the error
[18:39] <timrc> sinzui: lp_save() alwas returns 502 or 503 ror me :(
[18:39] <timrc> for^
[18:40] <sinzui> timrc: I think this may be a timeout given the time it took to get the error
[18:40] <sinzui> timrc: I am going to toggle the ppa's privacy through the UI to see the difference
[18:41] <timrc> sinzui: if I comment out the ppa.private = True and call lp_save() it's instantaneous
[18:41] <sinzui> the UI is wicked fast
[18:41] <timrc> sinzui: doing ppa.private = True makes LP scratch its head :)
[18:42]  * sinzui looks at the impl
[18:42] <timrc> I can set ppa's private via the web ui, so I can't reconcile the difference
[18:48] <sinzui> timrc: I recall cases where field validation is not performed correctly over the API. I have seen name and date validation fail, so the bad value continues until something throws a wobbly. I wonder if this is the case here
[18:48]  * smokex_ is busy probably writing code: Gone away for now
[18:48]  * smokex_ is busy probably writing code: Gone away for now
[18:49] <sinzui> timrc: I see the field is guarded by  validator, and I wonder if the act off assignment is wrong
[18:49] <timrc> sinzui: ah, you mean, ppa.private = True would be an illegal assignment?
[18:50] <timrc> e.g. it's read-only?
[18:50] <sinzui> timrc: no we can assign, and we know from using the UI that the value is correct, but that does not mean the publisher is converting the values and doing the assignment correct
[18:57] <sinzui> timrc: I think I may need to wait for oops reports to arrive since I am not seeing an id at the moment. I am reporting a bug now
[18:57] <timrc> sinzui: excellent
[18:59] <timrc> sinzui: thanks for looking into this for me - it's greatly appreciated
[19:02] <sinzui> timrc: this issue may be bug 380504 or bug 702134. Since neither of us have seen it work. I cannot say the issue in intermittent.
[19:04] <timrc> sinzui: I went through that first bug
[19:05] <timrc> sinzui: and I believe the fix was to add a retry to the _connection() call in restfulclient
[19:05] <timrc> sinzui: that gives n=6 attempts with 2^n seconds between tries
[19:07] <timrc> er _request() I guess (looking at /usr/lib/python2.6/dist-packages/lazr/restfulclient/_browser.py)
[19:08] <timrc> (python-lazr.restfulclient 0.9.20-0ubuntu1)
[19:35] <timrc> sinzui: thanks
[20:10] <CarlFK> https://launchpad.net/~carlfk/+archive/ppa/+buildjob/2284936   "Start in 3 hours" - really?
[20:15] <spetrunia> Hello
[20:15] <spetrunia> is it just me, or all launchpad websites work extremely slow now?
[20:16] <spetrunia> for instance, it takes minutes to report a bug
[20:18] <genii-around> Hello. How to change the email address my launchpad account is in? The place it was at stopped their email services, etc. Can't find a setting for it though.
[20:20] <genii-around> Ah, found the area to set it. Not overly intuitive. Thanks.
[21:17] <jcsackett> lifeless: r=me.
[21:18] <jcsackett> crap. wrong channel, but you still get the msg.
[21:30] <aroman> hey -- what is canonical doing about Apple's copyright infringement on the trademark "Launchpad"?
[21:33] <lifeless> its with legal
[21:34] <aroman> and have they said anything?
[21:34] <lifeless> I haven't heard anything
[22:40] <Delemas> I deleted a pending build because it was going to 7 hours to build. The buildjob did not get aborted. Is there some what I can force buildjob 2285139, for a now deleted job, to abort?
[22:41] <lifeless> not at the moment
[22:41] <lifeless> once its on a machine, its on a machine
[22:41] <Delemas> Can someone there do it?
[22:41] <lifeless> not at the moment, the sysadmins are all asleep
[22:41] <Delemas> lol oh well... Thanks anyways...
[22:46] <wgrant> Delemas: It's not on the builder yet. It will be cancelled once it reaches the head of the queue.
[22:49] <Delemas> ya unfortunately that will take 6-7 hours to clue in. That package is a dependancy for my build and I was going to just copy the binaries from another PPA so I could proceed with my build...
[22:49] <Delemas> I get an error when trying to do that, because it's in the build queue...
[22:50]  * smokex_ is busy probably writing code: Gone away for now
[22:50]  * smokex_ is back.
[22:50] <lifeless> smokex_: please disable emote-on-away
[22:50] <lifeless> smokex_: its very annoying because it shows up in every channel you are in.
[22:52] <smokex_> done
[22:56] <lifeless> thanks
[23:02] <Delemas> Anyone know how to get pbuilder to pull a dependant package from a PPA?
[23:08] <sinzui> delemas, your building something locally and want to specify an archive to pull deps from?
[23:08] <lifeless> Delemas: add it to sources.list in the chroot; you can do that at runtime with an option that I have forgotten
[23:10] <Delemas> Yes I have a local package I want to build locally which needs a dependancy from a PPA. So I need a way to tell it to grab it from the PPA...
[23:12] <Delemas> I'm trying to build freeipmi 0.8.12 packages which needs autotools-dev (>= 20100122.1~)...
[23:19] <sinzui> Delemas: I think you want to look at http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html#usingspecialaptsources Launchpad ppas are archives like deb http://ppa.launchpad.net/team-of-user/ppa/ubuntu natty main
[23:35] <Delemas> Thanks


[01:30] <ripps> Does anybody know why it's been so long since chromium-browser in the dev ppa has been updated?
[01:39] <micahg> ripps: no one maintaining it ATM, we hope to get it back online the middle of next month
[01:39] <micahg> getting stable updated is my first priority
[12:52] <chrisccoulson> hmm, really must go and enjoy the sunshine
[12:54] <mdeslaur> chrisccoulson: by walking to the pub?
[12:54] <chrisccoulson> mdeslaur, no, i'm going to wash the car
[12:55] <chrisccoulson> although, i'd prefer to go to the pub
[12:55] <mdeslaur> hehe
[12:55] <chrisccoulson> the pub is probably not an appropriate place to take my daughter though ;)
[13:05] <bhearsum> chrisccoulson: sorry i didn't get back to you last night
[13:06] <bhearsum> we have defininetly successfully built aurora since the merge
[13:18] <cousin_luigi> hello
[13:18] <cousin_luigi> is ff7 coming to natty anytime soon?
[16:23] <micahg> cousin_luigi: there's a possible issue with the update, so I've not pushed it out yet
[16:29] <cousin_luigi> micahg: oh, like what?
[16:31] <micahg> cousin_luigi: mozilla Bug 680802
[16:31] <ubot2> Mozilla bug 680802 in Add-ons Manager "Upgrade Firefox when there is an add-on update waiting to be installed uninstalls the add-on" [Major,Assigned: ] http://bugzilla.mozilla.org/show_bug.cgi?id=680802
[16:35] <cousin_luigi> oh, thanks
[18:01] <gnomefreak> how do i change the theme in chrome? i downloaded 3 of them but i cant choose 2 of the ones i need. prefferences->personal stuff it lets me choose either default or gtk themes but doesnt list the thmes for me to choose
[18:03] <gnomefreak> this is the one im trying to set https://chrome.google.com/webstore/detail/ndoefmbhphkmgdgdeancfdlhkdcgpcah?hl=en&hc=search&hcp=main
[18:15] <gnomefreak> thats odd
[18:21] <chrisccoulson> hi bhearsum
[18:21] <bhearsum> hey chrisccoulson
[18:21] <chrisccoulson> sorry, been out for most of the day ;)
[18:21] <chrisccoulson> i'll try rebuilding aurora again
[18:21] <bhearsum> np
[18:37] <chrisccoulson> micahg, you'll probably need me around to give you 7.0.1 tarballs btw. the get-orig-source target won't give you a working tarball anymore on the release builds
[18:38] <chrisccoulson> (you'll get broken translations)
[18:39] <chrisccoulson> i picked the wrong week to be on vacation
[18:39] <chrisccoulson> i should ensure i schedule my personal life around firefox releases in future ;)
[18:41] <micahg> chrisccoulson: you picked the wrong week to break stuff
[18:42] <chrisccoulson> heh
[18:42] <micahg> chrisccoulson: sorry, that didn't come out right (I'm running on 3 hours of sleep)
[18:42] <micahg> chrisccoulson: the natty branch won't make a proper tarball either?
[18:43] <micahg> chrisccoulson: I'm off in 4 hours, jdstrand will be handling the update for tomorrow
[18:43] <micahg> chrisccoulson: I'm planning on pushing the updates to oneiric Sat night
[18:44]  * micahg wants to take a vacation around the next firefox release...
[18:44] <chrisccoulson> micahg, yeah, i need to run the new script manually to create the tarball (just for the stable builds. it works fine on beta, aurora and nightly)
[18:45] <micahg> chrisccoulson: are you planning on updating the PPAs?
[18:45] <chrisccoulson> i stopped mirroring the translations, so running the old get-orig-source target will not pull in new translations
[18:45] <chrisccoulson> micahg, i was hoping not too ;)
[18:45] <chrisccoulson> but i will do if i need to
[18:45] <micahg> chrisccoulson: ok, if you can leave me tarballs, I'll do it over the weekend
[18:46] <micahg> actually, firefox 7.0.1 will be in the archive already, I"ll just need thunderbird (or for you to fix th script :))
[19:28] <cousin_luigi> bbl
[20:49] <micahg> chrisccoulson: firefox 7.0.1 has been tagged, if you can get me a tarball in the next hour, I can upload before I sign off for the day
[20:54] <chrisccoulson> micahg, yeah, just creating it now
[20:59] <micahg> chrisccoulson: thanks
[20:59] <chrisccoulson> micahg, it takes a little while because of all the l10n repo's ;)
[21:00] <chrisccoulson> obvioulsy, i had to do that before too as an extra manual step though
[21:13] <chrisccoulson> bhearsum, oh, it seems that mongolian and swahili are back in shipped-locales for 7.0.1 ;)
[21:14] <chrisccoulson> (in case you didn't know already)
[21:38] <chrisccoulson> micahg, you'll need to pull my latest commits to bzr btw, so that mongolian and swahili are blacklisted
[21:38] <micahg> ok, will do, thanks
[21:38] <micahg> chrisccoulson: natty branch?
[21:38] <chrisccoulson> micahg, yeah, i pushed the same change to all branches
[21:39] <micahg> chrisccoulson: thanks
[21:39] <chrisccoulson> it won't build otherwise, as those 2 locales are omitted entirely from the source tarball (no release tag)
[21:39] <micahg> I hope you find some time to relax this vacation :)
[21:39] <chrisccoulson> heh
[21:39] <chrisccoulson> i will do by friday, as my vacation actually starts then
[21:39] <chrisccoulson> i'm driving to cornwall on friday morning, and staying in a cottage on a farm for a week
[21:40] <chrisccoulson> so, no internets ;)
[21:40] <micahg> chrisccoulson: awesome, I have no internet/phone for the next 3 days myself :)
[21:41] <chrisccoulson> cool :)
[22:09] <bhearsum> chrisccoulson: ffs
[22:09] <bhearsum> fml
[22:10] <chrisccoulson> hi bhearsum :)
[22:56] <micahg> bhearsum: if there are any major happenings WRT chemspills over the next 2 days, can you let jdstrand know?


[15:23] <Emerling>  /msg NickServ VERIFY REGISTER Emerling jqmywahqolgm
[15:23] <tsimonq2> 0.0
[15:23]  * Emerling sorry
[15:36] <pcimagen> Hola
[15:37] <pcimagen> somebody here?
[15:37] <Emerling> Hi, team ubuntu-ve ready . thanks members
[15:37] <pcimagen> o/ Emerling
[15:38] <naudy> Emerling: o/
[15:39] <naudy> Abr1l: o/
[15:39] <Abr1l> naudy, ;)
[15:42] <naudy> Lord_System:  o/
[15:42] <Lord_System> naudy o/
[15:47] <AndChat|683156> Hi
[15:47] <AndChat|683156> Test from android
[15:47] <AndChat|683156> Abr1l: hola
[15:50] <Abr1l> AndChat|683156, /nick ;)
[15:51] <AndChat|683156> Soy pcimagen
[15:53] <Abr1l> AndChat|683156, so /nick pcimagen ;)
[15:59] <naudy> k15h4: o/
[16:00] <k15h4> .o/
[16:00] <jgrimm> hi there.
[16:00] <jgrimm> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Nov 24 16:00:39 2015 UTC.  The chair is jgrimm. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: action commands idea info link nick
[16:00] <kickinz1> o/
[16:00] <matsubara> o/
[16:00] <caribou> o/
[16:01] <jgrimm> might be a light turnout today.. a good number of server team are out on vacation
[16:01] <thedac> o/
[16:01] <jgrimm> hi folks!
[16:01] <arges> o/
[16:01] <jgrimm> #topic Review ACTION points from previous meeting
[16:01] <jgrimm> So all 3 of the action items were for rbasak who is on vacation this week
[16:02] <jgrimm> rbasak look at https://code.launchpad.net/~psivaa/ubuntu-test-cases/lvm-grub-preseed-fix/+merge/258620 and https://code.launchpad.net/~om26er/ubuntu-test-cases/fix_minimal_image_size_test/+merge/235298
[16:02] <jgrimm> that one looks done..
[16:02] <matsubara> jgrimm, I believe rbasak replied to the list addressing his action points
[16:02] <jgrimm> matsubara, oh...good to know. i missed that
[16:02] <jgrimm> will go quickly then
[16:03] <jgrimm> rbasak to create blueprint for Xenial feature work
[16:03] <jgrimm> that too is done.
[16:03] <jgrimm> #link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core
[16:03] <jgrimm> See that link for various package assignments
[16:04] <matsubara> jgrimm, https://lists.ubuntu.com/archives/ubuntu-server/2015-November/007141.html
[16:04] <jgrimm> thanks matsubara!
[16:04] <matsubara> np
[16:05] <jgrimm> moving along, looks like final one still in process, so will continue action for that one
[16:06] <jgrimm> #action rbasak to find kickinz1 a merge to do. In progress, suggesting exim4.
[16:06] <meetingology> ACTION: rbasak to find kickinz1 a merge to do. In progress, suggesting exim4.
[16:06] <jgrimm> on we go..
[16:06] <kickinz1> Ok
[16:06] <jgrimm> #topic Xenial Development
[16:07] <jgrimm> Still in merge/sync mode...
[16:07] <jgrimm> anyone have anything they want to discuss here?
[16:08] <jgrimm> rbasak is still looking for volunteers for some merges.  Documented in blueprint.
[16:08] <kickinz1> working on the docker.io one currently.
[16:08] <jgrimm> kickinz1, always a fun one. eek
[16:10] <jgrimm> #topic Server & Cloud Bugs (caribou)
[16:10] <caribou> jgrimm: I'll have a look at the list to see if I can h elp
[16:10] <jgrimm> thanks caribou!!
[16:10] <jgrimm> Anything on bugs?
[16:10] <caribou> just uploaded makedumpfile/kdump-tools to Debian
[16:10] <caribou> the upcoming version will default to enabled and use of smaller initrd.img
[16:11] <caribou> that's all I have
[16:11] <jgrimm> k. thanks caribou
[16:11] <jgrimm> #topic Weekly Updates & Questions for the QA Team (matsubara)
[16:11] <matsubara> jgrimm, no news for this week.
[16:11] <jgrimm> ok thanks matsubara
[16:11] <jgrimm> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:11] <smb> I cannot think of anything to report. Are there requests or questions?
[16:12] <jgrimm> going once
[16:13] <jgrimm> and gone. thanks smb.
[16:13] <jgrimm> #topic Upcoming Call For Papers
[16:14] <jgrimm> Only thing I saw was OSCON CFP deadline today
[16:14] <jgrimm> http://conferences.oreilly.com/oscon/open-source/public/cfp/423
[16:14] <jgrimm> #link http://conferences.oreilly.com/oscon/open-source/public/cfp/423
[16:15] <jgrimm> Anything else?
[16:15] <kickinz1> pycon?
[16:15]  * jgrimm checks quick
[16:16] <kickinz1> Sorry from the canonical-tech, but seems not relevant (namibia)
[16:17] <kickinz1> http://na.pycon.org/
[16:17] <cpaelzer> jgrimm, when are we going to adress systemz conference CFPs ?
[16:18] <jgrimm> cpaelzer, :)
[16:18] <jgrimm> kickinz1, finally found the CFP date
[16:19] <jgrimm> The call for proposals expires on the 15th December 2015.
[16:19] <jgrimm> ok, moving on
[16:19] <jgrimm> #topic Open Discussion
[16:20] <jgrimm> anyone have anything for open discussion time??
[16:21] <jgrimm> ok, time to wrap things up then.   assumed it would be quick one with smoser and rbasak out this week.
[16:21] <jgrimm> #topic Announce next meeting date, time and chair
[16:21] <jgrimm> The next meeting will be Tue Dec 01 16:00 UTC 2015. kickinz1 will chair.
[16:22] <jgrimm> Thanks folks!
[16:22] <kickinz1> Thanks!
[16:22] <caribou> thanks!
[16:22] <jgrimm> #endmeeting
[16:22] <meetingology> Meeting ended Tue Nov 24 16:22:18 2015 UTC.
[16:22] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-11-24-16.00.moin.txt
[17:00] <pitti> o/
[17:00] <stgraber> pitti: we're in #ubuntu-meeting-2
[17:00] <pitti> argh