[13:09] <BluesKaj> Hi all
[16:04] <RikMills> ping
 pong
 \o/ here too!
[21:37] <Eickmeyer> https://twitter.com/KubuntuF/status/1405277762479263750?s=20
[21:38] <Eickmeyer> Everyone, check out the video in that. It's for the Kubuntu Focus computer. :)
[21:45] <clivejo> did the dev team ever get free laptops out of that deal?
[21:46] <Eickmeyer> clivejo: The Council gets a percentage of each sale.
[21:47] <clivejo> oh are you the guy behind it?
[21:47] <Eickmeyer> I work for the company.
[21:47] <clivejo> I see
[21:48] <Eickmeyer> I'm really the Ubuntu Studio lead and on the Ubuntu Community Council, but they hired me for packaging/UX.
[21:48] <clivejo> ah right
[23:47] <valorie> lovely little video, Eickmeyer
[23:52] <Eickmeyer> valorie: Thanks! Just trying to drum-up a little community interest in what we're doing. The community interest has felt lacklustre at best.


[00:00] <sbtech> full error here http://pastebin.com/MbbQUzrc
[00:12] <sbtech> and this is the debug message just below http://pastebin.com/Jcx46rjr
[07:57] <UnderTheDome> hello
[07:58] <UnderTheDome> Can someone explain to me how to create a Windows Image to submit to MAAS, in order to be deployed on physical machines ?
[10:36] <UnderTheDome> Can someone explain to me how to create a Windows Image to submit to MAAS, in order to be deployed on physical machines ?


[00:39] <tiwake> Ardonel: poke
[00:57] <Ardonel> ouch
[00:57] <Ardonel> why?
[01:12] <tiwake> why not :3
[01:13] <Ardonel> why knot?
[02:27] <tiwake> heh
[02:27] <tiwake> Ardonel: what are you up to?
[10:52] <Ardonel> sorry about that, had evening guests till late, then crashed...
[15:09] <tiwake> Ardonel: enh, just small talk


[21:05] <plasmasolutions> Hi guys, I got a really big problem here, maybe you got an idea - my latin has come to an end...
[21:05] <plasmasolutions> https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1270655
[21:07] <plasmasolutions> I don't know where to look, so any ideas are helpful
[21:09] <tjaalton> so you filed a bug against an encoder?
[21:10] <tjaalton> the nvidia driver is a better bet
[21:15] <plasmasolutions> tjaalton: Hi Timo! I just added you to the bug - ubuntu-gnome was telling me to do that..
[21:15] <plasmasolutions> Great to see you "personal" here ;)
[21:15] <plasmasolutions> tjaalton: So you mean I should try to get the bleeding edge nvidia?
[21:18] <plasmasolutions> tjaalton: Atm I'm not using the nvidia cards (got all cards removed) and am on the internal chip...but still freezing - do you still think that could be the nvidia driver?
[21:18] <plasmasolutions> Didn't purge it
[21:18] <tjaalton> and I removed myself :)
[21:18] <tjaalton> dunno then
[21:19] <tjaalton> if it freezes with intel too
[21:19] <tjaalton> wait, blender just crashes?
[21:19] <plasmasolutions> Yes, it just crashes
[21:19] <tjaalton> so blame blender then
[21:19] <plasmasolutions> But "crashes" in the meaning of freezing the whole system
[21:20] <tjaalton> ok
[21:20] <plasmasolutions> It's exactly the same issue as with the thumbnailer
[21:20] <plasmasolutions> And as I am a blender developer I would never blame me :D
[21:22] <plasmasolutions> tjaalton: no, I think the problem lies deeper on the ground: As that are all h264 vids and the cpu got decoder units for that I assume that the mobo and the cpu are not talking nicely to each other... (corrupting memory)
[21:24] <plasmasolutions> tjaalton: Maybe you know who could take a look at the bug? I really like to help investigate it
[21:26] <tjaalton> the cpu doesn't, but the gpu
[21:26] <tjaalton> check your ram
[21:26] <tjaalton> try newer kernels
[21:26] <tjaalton> or older
[21:26] <plasmasolutions> tjaalton: Did a one day check...no issues
[21:26] <plasmasolutions> and tried the 3.13 kernel, no problem
[21:26] <plasmasolutions> ups same problem
[21:27] <plasmasolutions> didn't try older ones though
[22:27] <plasmasolutions> am off now, tjaalton thanks for your help!


[05:49] <Nothing_Much> what's going on in europe?
[06:38] <mhall119> Nothing_Much: lots of hacking, arguing and drinking
[06:43] <Nothing_Much> oh my


[15:59] <paride> holmanb, fwiw responses==0.17.0 is the versions that fixes the issue that affects your ec2-dualstack branch
[15:59] <paride> but I can't spot an obvious change between 0.16.0 and 0.17.0 that could make the difference *and* can be backported to 0.5.1
[22:24] <akutz> I will be filing an issue with LP, but it looks like there's a bug in the SystemD renderer -- https://github.com/canonical/cloud-init/blob/main/cloudinit/net/networkd.py. Can someone confirm that only the Photon distro uses this renderer and other distros that use systemd use the netplan renderer?
[22:25] <akutz> FWIW, the bug is with generate_match_section -- https://github.com/canonical/cloud-init/blob/bb93952cb90e07e9a9c2e4e6bdab94a1582ffeeb/cloudinit/net/networkd.py#L83-L98. This always adds the name to the match section, regardless of whether the scalar in the cloud-init network config matches the name of the device. I'm going to propose if the MAC address is known then the name should be omitted from the match section.
[22:25] <akutz> I was wondering why I did not hit this when testing with Ubuntu (since RHEL uses sysconfig), and I realized it's because Ubuntu uses netplan, not the direct systemd renderer that was ported from the old Photon distro source.
[22:26] <akutz> I also realized the reason this never tripped anyone up in CAPV is because set-name was always used there, so the devices always ended up renamed to the intended name anyway.
[22:26] <akutz> But for a distro that uses the networkd renderer that does not use set-name, unless the network config ethernets scalar matches the name of the device on the guest, the match section, even if the MAC address is provided, will never match.
[22:27] <akutz> Because as per the docs, at https://www.freedesktop.org/software/systemd/man/systemd.network.html -- "A network file is said to match a network interface if all matches specified by the [Match] section are satisfied."


[04:54] <vinsci> hi all
[04:54] <vinsci> I'm considering the possibility of using and extending Malone as a base for another application.
[04:55] <vinsci> I haven't been able to find the source code though, who should I talk to about getting that?
[04:56] <Kinnison> Malone's source code is not public currently as far as I understand it
[04:57] <vinsci> Hence the question, who to talk to?
[04:58] <Kinnison> Mark Shuttleworth I guess
[04:59] <SteveA> vinsci: what's your application?
[05:00] <vinsci> hi stevea, thought you might be at the top of the list :)
[05:01] <vinsci> We're hoping to build a workflow/agenda system for public administrations (local governments)
[05:02] <SteveA> why do you think the malone sourcecode would help with that?
[05:02] <SteveA> hi vinsci.  did we meet at europython?
[05:03] <vinsci> as a fairly zope x3 app, it ought to provide a good example
[05:03] <vinsci> yes, we met in Gothenburg
[05:06] <SteveA> are you planning to use zodb or to use a relational database?
[05:06] <vinsci> officially undecided, but I don't want to spend the rest off my life writing obj/rel mappers
[05:07] <SteveA> does that mean, probably zodb?
[05:07] <vinsci> the flow of issues/agendas in a public administration is actually not all that far from bug tracking. The initial use would be to use it as a base for prototyping purposes and as a demo base for the financers (we're seeking public financing)
[05:07] <vinsci> yes, but through zodb, we can of course use an sql storage if we like
[05:09] <SteveA> i'll tell you a bit about launchpad.  i can't speak to what kind of access to the source code is available for people outside of canonical.  you'd need to talk to mark about that.  there is an intention to make the launchpad code open source at some point in the future, but exactly when or what the circumstances would be for that is totally undecided at the moment.
[05:09] <SteveA> launchpad stores most of its data in a relational database.  we use sqlobject as an OR tool.  we're not particularly using the zodb.
[05:10] <SteveA> also, malone is far more complex than it would be if it were just a bug tracker
[05:12] <SteveA> it is meant to deal with the complexities of different packaged versions of software, and how the bugs in such things are interrelated
[05:13] <SteveA> if your main task at the moment is making a mock-up application to demonstrate the ideas and get funding, i'd suggest putting something together using zope3's schemas and autogenerated forms, as a regular zope3 application
[05:56] <vinsci> thanks, SteveA
[05:58] <SteveA> maybe look at hiring stephan richter to work with you on building the prototype.  he's good at quickly building proofs-of-concept
[05:58] <vinsci> been playing with sqlobject from a standalone py app and as far as mappers go, it seemed quite usable
[06:02] <vinsci> adding him to the list ;)


[11:58] <Kilos> helloooo africa
[13:49] <superfly> Kilos: http://ubuntu-africa.info/
[13:49] <Kilos> ok
[13:50] <Kilos> i see cgi-bin/
[13:50] <superfly> Kilos: before you ask: yes, there's nothing there.
[13:50] <Kilos> lol
[13:50] <Kilos> oh you mean its live
[13:52] <inetpro> great!
[13:53]  * Kilos bows to superfly
[16:33] <cyrilb> https://twitter.com/cyb_bo/status/586929926424506369
[16:34] <Kilos> nice work cyrilb
[16:35] <cyrilb> thanks
[17:26] <inetpro> cyrilb: looks interesting
[17:33] <cyrilb> thanks
[17:52] <inetpro> cyrilb: I guess you stay in Mauritius?
[17:52] <inetpro> or did you fly in from somehwere else?
[18:03] <cyrilb> I'm French but I live in Mauritius
[18:03] <cyrilb> just moves there
[18:03] <Kilos> too many pretty holiday makers there to leave
[18:03] <inetpro> lol
[18:04] <inetpro> Kilos: one day you will hopefully take us for a tour to meet all your new friends across the globe
[18:05] <Kilos> whew we gonna have to travel
[18:05] <Kilos> from berlin to the west of the states
[18:06] <Kilos> others in asia and korea
[18:06] <inetpro> Kilos: and down under?
[18:07] <Kilos> i havent spoken to them yet except for when tara needed help with buntu
[18:07] <inetpro> oh I forgot you even have family there :-)
[18:09] <Kilos> they werent very helpful
[18:09] <inetpro> who?
[18:10] <Kilos> thats when i brought her to za
[18:10] <Kilos> the aus guys
[18:10] <inetpro> aha
[18:10] <Kilos> they didnt try help online just said bring your pc in
[18:11] <Kilos> now she knows enough to help herself with ubuntu
[18:11] <Kilos> oh and the odd question for the old man of course
[18:12] <Kilos> in pidgin
[18:12] <inetpro> cool
[18:13] <Kilos> and i dare not miss a za ruby match without have her commenting
[18:13] <Kilos> lol
[18:13] <Kilos> they just went to bed now
[18:14] <Kilos> 5am


[00:04] -queuebot:#ubuntu-release- Unapproved: accepted lyx [source] (bionic-proposed) [2.2.4-0ubuntu<IP_ADDRESS>]
[03:57] -queuebot:#ubuntu-release- Unapproved: rejected gnupg2 [source] (bionic-proposed) [2.2.4-1ubuntu1.3]
[03:58] -queuebot:#ubuntu-release- Unapproved: rejected gnupg2 [source] (cosmic-proposed) [2.2.8-3ubuntu1.2]
[04:00] -queuebot:#ubuntu-release- Unapproved: rejected gnupg2 [source] (xenial-proposed) [2.1.11-6ubuntu2.2]
[05:44] -queuebot:#ubuntu-release- Unapproved: accepted ruby2.5 [sync] (bionic-proposed) [2.5.1-1ubuntu1.4]
[05:54] -queuebot:#ubuntu-release- Unapproved: rejected geocode-glib [source] (bionic-proposed) [<IP_ADDRESS>-4ubuntu18.04.1]
[05:54] -queuebot:#ubuntu-release- Unapproved: geocode-glib (bionic-proposed/main) [<IP_ADDRESS>-4 => <IP_ADDRESS>-4ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[06:38] -queuebot:#ubuntu-release- Unapproved: accepted geocode-glib [source] (bionic-proposed) [<IP_ADDRESS>-4ubuntu<IP_ADDRESS>]


[07:40] <Rellis> Hi
[08:57] <cjwatson> mdz: urgh, sorry, I completely missed this last night (same virtual sprint as stgraber, and so for once I finished work more or less on time)
[15:57] <jamespage> o/
[15:57] <arosales> Hello
[15:57] <smoser> o/
[15:59] <m_3> hola
[15:59] <rbasak> \o
[16:00] <arosales> Its top of the hour so lets get started. I am going to give chairing the meeting a whack. So please bear with me and correct me where needed :-)
[16:00] <arosales> #startmeeting ubuntu-server-team
[16:00] <meetingology> Meeting started Tue Jun 12 16:00:52 2012 UTC.  The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:01] <arosales> #topic Review ACTION points from previous meeting
[16:01] <arosales> rbasak: how is the migration to ubuntuserver.org going?
[16:02] <rbasak> I had assumed that was a joke action. I have no knowledge of ubuntuserver.org or anything surrounding it whatsoever.
[16:02] <arosales> I think that was in reference to our server team blog, correct
[16:02] <smoser> hm.. funny. it probably was a joke action and then got carried over too.
[16:03] <smoser> nice. for shame on whoever chaired last week.
[16:03] <arosales> If so, are there any objections about where the blog current lives?
[16:03] <rbasak> I would just like to see the typo fixed, which is how I ended up with the joke action
[16:03] <m_3> rbasak: I think you were dissing the site and got volunteered by the meeting chair :)
[16:03] <arosales> rbasak: where is that typo again?
[16:03] <rbasak> In the headline
[16:03] <rbasak> peices
[16:04] <arosales> ah ok, here https://ubuntuserver.wordpress.com/
[16:04] <arosales> rbasak:  did you want to follow up with jamespage and see who has access and get that corrected?
[16:05] <arosales> rbask, if not I can.
[16:05] <jamespage> arosales, rbasak: I think I might have access
[16:05] <rbasak> I don't think it's worth me being involved. I know nothing about it, and am not sure what I can add
[16:05] <rbasak> (apart from another cook for the broth)
[16:05] <arosales> ok, I will follow up
[16:05] <SpamapS> o/
[16:06] <arosales> #action arosales to correct "pieces" on ubuntu server blog
[16:06] <meetingology> ACTION: arosales to correct "pieces" on ubuntu server blog
[16:06] <arosales> smoser:  did you have a chance to follow up with rbasak on bug 972077
[16:07] <smoser> rbasak, ping, re 972077
[16:07] <smoser> (no, i didn't. but i will)
[16:07] <arosales> ok thanks smoser
[16:07] <arosales> #topic Precise Development
[16:07] <arosales> bugs
[16:07] <arosales> http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:07] <arosales> bug https://launchpad.net/bugs/974584
[16:08] <arosales> hallyn: were you taking a look at this one ^
[16:08] <arosales> bug 920197
[16:09] <arosales> zul: and jamespage this one queued up correctly for SRU in 12.04.1?
[16:09] <jamespage> yep
[16:09] <zul> yep
[16:09] <arosales> cool thanks zul and jamespage
[16:09] <arosales> bug 1001846
[16:09] <hallyn> hm, yeah, i dropped the fix for bug 974584 both in debian and ubuntu bugs, i don't have upload rights...
[16:10] <arosales> smoser: I think you were looking for more info on this one did airtonix give what was needed?
[16:10] <hallyn> think the debian maintainer got sick of me
[16:10] <arosales> hallyn: thanks for the update on 974584
[16:10]  * smoser re-looks
[16:10] <arosales> hallyn: let us know if you don't get a response soon
[16:10] <arosales> smoser: thanks
[16:11] <arosales> bug https://launchpad.net/bugs/1009294
[16:11] <smoser> hm... roaksoax is not around. i think there is enough info in that bug to move forward.
[16:11] <arosales> smoser: looks like you had the todo here to get the fix commited. Is that now in the ubuntu cloud images?
[16:12] <arosales> well catch roaksoax later on the cobbler bug
[16:12] <arosales> bug 880339
[16:12] <smoser> someone should verify images are fixed for that cloud image bug
[16:12] <smoser> and we need to refresh the 12.04 images.
[16:13] <utlemming> smoser: I can do that...
[16:13] <SpamapS> arosales: that one is a dupe of one that I'm working on
[16:13] <arosales> jamespage:  I think you were tracking bug 880339, is that now fixed?
[16:13] <utlemming> smoser: and I plan on re-spinning precise ASAP
[16:13] <SpamapS> arosales: I think we can drop it from the list, having been incomplete without a response for so long
[16:13] <arosales> utlemming: could you help with verifying the fix smoser commited?
[16:13] <utlemming> arosales: yup
[16:13] <arosales> utlemming: thanks
[16:13] <hallyn> arosales: i've got a note in my tickler to bug ubuntu-devel on thu if no action from maintainer
[16:14] <jamespage> arosales, yes - SpamapS please could you ensure the bug that you are working on has a task for precise and is targetted to 12.04.1
[16:14] <arosales> #action drop 880339 from bug list — no response
[16:14] <meetingology> ACTION: drop 880339 from bug list — no response
[16:14] <SpamapS> arosales: no action needed
[16:14] <arosales> thanks SpamapS
[16:14] <arosales> ah, ok :-)
[16:14] <SpamapS> arosales: its already closed as Invalid actually
[16:14] <SpamapS> there was a recent response.. that the user had screwed it up themselves
[16:15] <arosales> I'll make sure to remove the subscription of ubuntu server team too
[16:15] <Daviey> (sorry for speaking out of turn.. but the ubuntuserver.org blog transition wasn't a joke action.. it needs to happen, and rbask wanted to see it improved.)
[16:15] <arosales> bug 993291
[16:16] <arosales> jamespage: looks like 993291 is tracking ok, correct?
[16:16] <jamespage> arosales, yeah - I just picked that up
[16:16] <arosales> jamespage: ok, thanks
[16:16] <arosales> bug 1009553
[16:17]  * jamespage is unsurprised
[16:17] <arosales> jamespage:  is this one a result of just droping -virtual kernel?
[16:17] <arosales> any fix needed?
[16:17] <jamespage> well its always close to the line - but yes that does seem to be the problem this release
[16:17] <Daviey> Well, we should dive for extra opportunities to reduce it's size
[16:18] <Daviey> but growth is expected.
[16:18] <jamespage> I'm not sure TBH - I though the -virtual piece was going to be managed with additional module packages
[16:18] <jamespage> which is the bulk of the oversize ATM
[16:18] <jamespage> ~60MB I think
[16:18] <jamespage> smb`, any opinion on ^^
[16:18]  * smb` tries to catch up
[16:19] <utlemming> jamespage: -virtual did indeed get dropped...and the kernel bloat in the AMI's is ~200M as a result
[16:19] <jamespage> utlemming, sounds about right :-)
[16:19] <arosales> in parallel for bug 920197, zul is that progressing as expected?
[16:20] <zul> arosales: no it needs some work still which im doing this afternoon
[16:20] <smb`> utlemming, Why there would be a virtual meta which only consists of the smaller part
[16:20] <utlemming> smb: is there a -virtual meta then?
[16:21] <arosales> zul: ok thanks. Make sure to ping smoser or jamespage both on the 12.04.1 team if any assistance is needed.
[16:21] <smb`> utlemming, linux-generic-meta -> linxu-image-generic + linux-image-extra-generic   vs. linux-virtual-meta -> linux-image-generic
[16:21] <zul> arosales: ack
[16:21] <jamespage> smb`, utlemming: sounds like we are bloating out to much
[16:21] <jamespage> arosales, please action smb, utlemming and I to discuss offline
[16:21] <jamespage> well online but not in this meeting :-)
[16:22] <utlemming> +1, we'll discuss this right after
[16:22] <smb`> jamespage, At least that is the theory, we need to reality check but, yes put up an action
[16:22] <arosales> #action jamespage and utlemming to discuss dropping -virtual kernel; re bug 1009553
[16:22] <meetingology> ACTION: jamespage and utlemming to discuss dropping -virtual kernel; re bug 1009553
[16:22] <arosales> utlemming: jamespage and smb thanks
[16:22] <jamespage> ta
[16:22] <arosales> bug 1008537
[16:22] <arosales> failed to build
[16:23] <arosales> may be similar to bug https://bugs.launchpad.net/bugs/968308
[16:23] <arosales> anyone interested in taking a look ?
[16:24] <arosales> webkit and sphinx
[16:24] <arosales> any interested folks?
[16:25] <Daviey> i'll investigate it.
[16:25] <arosales> Daviey: thanks
[16:25] <arosales> moving onto blueprints http://status.ubuntu.com/ubuntu-quantal/ubuntu-server.html
[16:25] <arosales> so we got some good work items documented, and dependencies liked to topics.
[16:26] <arosales> please take a look if the dependency linkage looks correct for your blueprint
[16:26] <arosales> also be sure to be implementing the blueprint spec into blueprints, jamespage do you have a link handy?
[16:27] <jamespage> https://wiki.ubuntu.com/BlueprintSpec
[16:27] <arosales> jamespage: thanks
[16:27] <jamespage> I do - thanks skaet!
[16:27] <arosales> Any other items on blueprints?
[16:28]  * arosales forgot the two topics under quantal dev
[16:28] <hallyn> hm, in https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-server-iso-tests-review, i hope someone will explain to me what that action item assigned to me is
[16:29] <arosales> jamespage:  can you assist hallyn with work items on the ISO tesing?
[16:29] <jamespage> hallyn, arosales: yep
[16:29] <arosales> #action jamespage to follow up with hallyn on servercloud-q-server-iso-tests-review
[16:29] <meetingology> ACTION: jamespage to follow up with hallyn on servercloud-q-server-iso-tests-review
[16:29] <arosales> jamespage: thanks
[16:29] <hallyn> thx
[16:29] <arosales> #topic Ubuntu Server Team Events
[16:29] <arosales> jim is at  http://static.usenix.org/events/config10/index.html
[16:30] <arosales> this week
[16:30] <arosales> Velocity coming up in a couple of weeks.
[16:30] <arosales> any other events?
[16:30] <jamespage> I pretending to be hazmat at EuroPycon at the start of July
[16:30] <arosales> cool, should be fun pretending to be hazmat :-)
[16:30] <SpamapS> jamespage: I can't wait to see your beard :)
[16:31] <arosales> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:31] <arosales> hggdh: Any updates from QA?
[16:31] <jamespage> SpamapS, I'm working on that :-)
[16:32] <jamespage> hggdh, whats the current status on UTAH?
[16:32] <arosales> perhaps hggdh isn't around at the moment. hggdh please feel free to comment if you return.
[16:32] <arosales> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:32] <arosales> smb`:  how is the kernel looking?
[16:33] <smb`> Mostly harmless...
[16:33] <arosales> any questions for smb` ?
[16:33] <arosales> thanks smb`
[16:34] <arosales> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:34] <rbasak> Calxeda's Highbank machine is now enabled in Quantal! We're planning a more detailed announcement on this soon, including installation instructions. MAAS support for this machine is now the next step.
[16:34] <rbasak> Any questions for me?
[16:34] <arosales> woot :-)
[16:35] <arosales> no other questions for rbasak
[16:35] <arosales> #topic Open Discussion
[16:35] <utlemming> rbasak: so we need to get together
[16:35] <utlemming> and get the armhf images using the Highbank then
[16:36] <arosales> Daviey: I'll follow up with rbasak on seeing how we can get our server team blog moved to the correct home. I have an action items to correct the spelling so I'll investigate the move with rbask.
[16:36]  * rbasak just wanted the typo fixed!
[16:36] <rbasak> That'll be <5 minutes for someone with access, right?
[16:37] <Daviey> rbasak: we need to move it regardless
[16:37] <Daviey> rbasak: You volunteered AIUI.
[16:37] <rbasak> Where should it go?
[16:37] <arosales> #action utlemming to follow up with rbasak on getting armhf images using highbank.
[16:37] <meetingology> ACTION: utlemming to follow up with rbasak on getting armhf images using highbank.
[16:37]  * rbasak didn't volunteer. He just asked for the typo to be fixed.
[16:37] <Daviey> rbasak: canonical hosted.. under that domain (owned by canonical)
[16:37] <m_3> prob a good idea to talk to jcastro about it
[16:38] <Daviey> rbasak: just need to raise an RT and get IS to setup wordpress under that domain.
[16:38] <Daviey> and migrate content... can you take that?
[16:38] <rbasak> Who has access to the current wordpress?
[16:38] <rbasak> To migrate content I'll want access
[16:38] <Daviey> rbasak: it's wordpress.org.. so all of us.
[16:38] <Daviey> err, .com
[16:38] <rbasak> Credentials?
[16:38] <Daviey> rbasak: anyone on the team can have an account
[16:38] <rbasak> Who has admin access?
[16:39] <Daviey> rbasak: If you don't have one, i can add you.
[16:39] <rbasak> Please
[16:39] <Daviey> rbasak: lets take this offline.
[16:39] <arosales> ok, thanks Daviey
[16:39] <arosales> Any other topics to discuss?
[16:40] <arosales> ok, thanks for everyone's time
[16:40] <arosales> #topic Announce next meeting date and time
[16:40] <jamespage> o/
[16:40] <jamespage> I had one actually
[16:40] <arosales> Tuesday 2012-06-19 at 1600 UTC
[16:40] <arosales> jamespage:  go
[16:40] <jamespage> OK - so smoser and I and representing the server team for the 12.04.1 release
[16:41] <Daviey> so don't mess it up.
[16:41] <jamespage> we have a regular catchup with all of the other 12.04.1 folk every 2 weeks
[16:41] <jamespage> I spent some time updating zul's reports - http://people.canonical.com/~jamespage/server-sru/precise-sru.html
[16:42] <jamespage> it you come across any bugs that should be SRU'ed please raise tasks for precise and target them to 12.04.1 - that way they will appear in the report
[16:42] <jamespage> assigning someone or an upload being accepted into -proposed results in them moving to 'inflight'
[16:43] <jamespage> I'd also like to have a regular slot in the meeting as well
[16:43] <jamespage> not to review the entire report but to focus on any problematic bugs...
[16:43] <jamespage> oh - http://people.canonical.com/~jamespage/server-sru/ contains series based reports for all supported releases as well
[16:43] <arosales> perhaps after the quantal development section
[16:43] <jamespage> that would make sense to me
[16:44] <arosales> #action arosales to add 12.04.1 Development section
[16:44] <meetingology> ACTION: arosales to add 12.04.1 Development section
[16:44] <arosales> jamespage: and smoser 	thanks for rep'ing server in the 12.04.01 team
[16:45] <arosales> any other items to discuss
[16:45] <arosales> Next meeting is Tuesday 2012-06-19 at 1600 UTC. Thanks for attending, and bearing with me ;-)
[16:45] <arosales> #endmeeting
[16:45] <meetingology> Meeting ended Tue Jun 12 16:45:55 2012 UTC.
[16:45] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-12-16.00.moin.txt
[16:45] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-12-16.00.html
[16:46] <jamespage> thanks arosales - great first chair!
[16:54] <hggdh> for the record -- UTAH is getting ready to have some tests ported
[16:59] <arosales> thanks hggdh
[17:00] <meetingology> Meeting started Tue Jun 12 17:00:05 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <ppisati> o/
[17:00] <herton> o/
[17:00] <sforshee> o/
[17:00] <bjf> -\o/-
[17:00] <henrix> o/
[17:00] <cking> \o
[17:00] <kamal> o/
[17:00] <BenC> o/
[17:00] <sconklin_> o/
[17:00] <arges> o/
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:00] <ppisati> Q/omap4: no new code was committed since last week, kept working on the configuration (delta reduction against master).
[17:00] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:01] <ogasawara> yeek, just a sec
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team-quantal-alpha-2.html
[17:02] <ogasawara> || apw         || hardware-q-kernel-config-review || 4 work item   ||
[17:02] <ogasawara> ||             || hardware-q-kernel-delta-review  || 3 work items  ||
[17:02] <ogasawara> ||             || hardware-q-kernel-versions-and-flavors || 1 work item ||
[17:02] <ogasawara> || cking       || hardware-q-kernel-delta-review  || 2 work items  ||
[17:02] <ogasawara> || cooloney    || hardware-q-kernel-config-review || 1 work item   ||
[17:02] <ogasawara> || jjohansen   || hardware-q-kernel-config-review || 1 work item   ||
[17:02] <ogasawara> || jk-         || hardware-q-kernel-config-review || 2 work items  ||
[17:02] <ogasawara> || ogasawara   || hardware-q-kernel-config-review || 2 work items  ||
[17:02] <ogasawara> || cyphermox   || hardware-q-kernel-delta-review  || 1 work item   ||
[17:02] <ogasawara> || ppisati     || hardware-q-kernel-config-review || 1 work item   ||
[17:02] <ogasawara> || sforshee    || hardware-q-kernel-delta-review  || 1 work item   ||
[17:02] <ogasawara> || smb         || hardware-q-kernel-delta-review  || 1 work item   ||
[17:02] <ogasawara> ||             || hardware-q-kernel-versions-and-flavors || 1 work item   ||
[17:02] <ogasawara> || tgardner    || hardware-q-kernel-config-review || 2 work items  ||
[17:02] <ogasawara> ||             || hardware-q-kernel-delta-review  || 2 work items  ||
[17:02] <ogasawara> || tlei        || hardware-q-kernel-delta-review  || 2 work items  ||
[17:02] <ogasawara> || kernel-team || hardware-q-kernel-config-review || 3 work items ||
[17:02] <ogasawara> ||             || hardware-q-kernel-versions-and-flavors || 2 work items ||
[17:02] <ogasawara> If your name is in the above table, please review your Alpha-2 work
[17:02] <ogasawara> items.
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Quantal Development Kernel (ogasawara)
[17:03] <ogasawara> We have recently rebased the Quantal kernel to the latest v3.5-rc2
[17:03] <ogasawara> upstream kernel.  I'd like to see a little more smoke testing before
[17:03] <ogasawara> uploading.
[17:03] <ogasawara> We've also began providing the 12.10 kernel for 12.04.  We welcome any
[17:03] <ogasawara> early adopters to please install, test, and let us know your feedback.
[17:03] <ogasawara> It is available from the following PPA:
[17:03] <ogasawara> https://launchpad.net/~ubuntu-x-swat/+archive/q-lts-backport
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara>  * Thurs Jun 28 - Alpha 2 (~2 weeks)
[17:03] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Precise/Oneiric/Natty/Lucid/Hardy (bjf/herton/henrix)
[17:03] <bjf> Here is the status for the main kernels, until today (June  05):
[17:03] <bjf>
[17:03] <bjf>  * Hardy    - 2.6.24-31.102 - Being prepared; 2 CVEs
[17:03] <bjf>  * Lucid    - 2.6.32-41.91  - Being prepared; 2 CVEs
[17:03] <bjf>  * Natty    - 2.6.38-15.61  - Being prepared; 3 CVEs
[17:03] <bjf>  * Oneiric  - 3.0.0-22.36   - Being prepared; 1 upstream stable release (approx. 60 commits), 1 CVE
[17:03] <bjf>  * Precise  - 3.2.0-26.41   - Being prepared; 1 upstream stable release (approx. 137 commits)
[17:03] <bjf>
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf>
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf>
[17:03] <bjf> Future stable cadence cycles:
[17:03] <bjf>  * https://wiki.ubuntu.com/QuantalQuetzal/ReleaseInterlock
[17:03] <bjf>
[17:03] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's (sconklin)
[17:03] <sconklin_> == 2012-06-12 (weekly) ==
[17:03] <sconklin_> Currently we have 89 CVEs on our radar, with 0 new CVEs added this week.
[17:03] <sconklin_> See the CVE matrix for the current list:
[17:03] <sconklin_> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <sconklin_> There is no change in the backlog this week:
[17:03] <sconklin_> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:03] <sconklin_> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:04] <sconklin_> ..
[17:04] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <kamal> o/
[17:04] <jsalisbury> kamal, go
[17:04] <BenC> o/
[17:04] <kamal> I've recently been working with the upstream Bufferbloat group: http://www.bufferbloat.net ...
[17:04] <kamal> They have implemented new network scheduler algorithms designed to address the performance drag induced by large unmanaged network buffers.  The new stuff ("fq_codel" and "codel") just landed in linux 3.5.
[17:04] <kamal> A good article about the bufferbloat problem and the new scheduling algo's is here: http://queue.acm.org/detail.cfm?id=2209336
[17:04] <kamal> The result is *very* impressive:  I see a 30X reduction in ping latency on a fully saturated 10Mbps network, just by switching on the new fq_codel scheduler.
[17:04] <kamal> For an interactive ssh session over that same saturated 10Mbps network, fq_codel totally eliminates the laggy keyboard response -- it feels like there's no other network traffic at all!
[17:04] <kamal> I have produced a Bufferbloat PPA to allow us to experiment with this stuff now in Precise and Quantal:
[17:04] <kamal> https://launchpad.net/~kamalmostafa/+archive/bufferbloat
[17:04] <kamal> The PPA includes a "quantal-3.4-plus-bufferbloat" kernel for precise and quantal.  (The new schedulers won't work on pre-3.3 kernels).  The PPA page links to a quick how-to-smoke-test-it guide and more info.
[17:05] <kamal> The Bufferbloat group is eager for testing and feedback and general eyeball time from the Ubuntu kernel team and the Ubuntu community.  Their channel is #bufferbloat on freenode.
[17:05] <kamal> Please give my PPA a whirl, and get a taste of the new cutting-edge network goodness.  Any questions about it -- I'll at least know who to direct you to, so feel free to ask me.
[17:05] <kamal> ..
[17:05] <jsalisbury> BenC, go
[17:05] <BenC> I had this on the meeting agenda, but don't see it above.
[17:05] <BenC> Trying to get some feedback for the patches I sent to kernel-team@, hoping to get it merged for next kernel upload
[17:05] <BenC> Re: PowerPC e500mc
[17:06] <BenC> ..
[17:07] <apw> BenC, i think that are being reviewed at the moment arn't they ?
[17:07] <BenC> If so, I'm unaware :)
[17:08] <BenC> Also, if there are any suggestions on changes to my workflow for getting powerpc stuff merged, let me know
[17:08] <bjf> we are looking at them and seeing if they scare us or not
[17:09] <BenC> bjf: The only scary one(s) are the mdio phy changes, but I have tested them extensively on non-ppc
[17:09] <tgardner> BenC: just got back after 5 days off. they are on my todo list.
[17:09] <BenC> Everything else is either nop or segmented on non-ppc
[17:09] <BenC> tgardner: thanks
[17:09] <bjf> a lot of the patches are sauce, are those also heading upstream ?
[17:10] <BenC> All of them have been pushed upstream
[17:10] <BenC> 2 have been accepted
[17:10] <tgardner> BenC: I should have some comments by tomorrow. got a huge pile of email to deal with...
[17:10] <BenC> Oh wait, not the SAUCE, not yet
[17:10] <BenC> freescale had 360+ patches last year, so they've done a lot to get this merged upstream
[17:10] <BenC> These are the last few, and are being dealt with in the coming months
[17:11] <BenC> tgardner: ok, please email, ping me if any questions come up…
[17:11] <tgardner> will do
[17:11] <tgardner> ..
[17:11] <BenC> ..
[17:12] <jsalisbury> Anything else for open discussion?
[17:12] <jsalisbury> Thanks everyone
[17:12] <jsalisbury> #endmeeting
[17:12] <meetingology> Meeting ended Tue Jun 12 17:12:39 2012 UTC.
[17:12] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-12-17.00.moin.txt
[17:12] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-12-17.00.html
[17:12] <kamal> thanks jsalisbury


[00:10] <Ursinha> OOPS-1362EA10197
[16:00] <matsubara> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is matsubara.
[16:00] <matsubara> Welcome to this week's Launchpad Production Meeting. For the next 45 minutes or so, we'll be coordinating the resolution of specific Launchpad bugs and issues.
[16:00] <matsubara> [TOPIC] Roll Call
[16:00] <MootBot> New Topic:  Roll Call
[16:00] <bigjools> me
[16:00] <matsubara> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us!
[16:00] <rockstar> ni!
[16:00] <bac> me
[16:00] <stub> me
[16:00] <gary_poster> me
[16:00] <EdwinGrubbs> me, sitting in for sinzui
[16:01] <matsubara> Ursinha, Chex: hi
[16:01] <Ursinha> me
[16:01]  * Chex is here
[16:01] <matsubara> danilos, are you joining us?
[16:01] <Ursinha> matsubara, flaky internet
[16:01] <matsubara> allenap, hi
[16:01] <danilos> me
[16:01] <danilos> matsubara: yes
[16:01] <allenap> me
[16:02] <matsubara> danilos, shall I make you the default translations person for the LP prod meeting?
[16:02] <mbarnett> me?
[16:02] <gary_poster> you!
[16:02] <matsubara> hi mbarnett
[16:02] <matsubara> welcome :-)
[16:02] <mbarnett>  :)
[16:02] <matsubara> ok, everyone is here
[16:02] <matsubara> [TOPIC] Agenda
[16:02] <MootBot> New Topic:  Agenda
[16:02] <matsubara>  * Actions from last meeting
[16:02] <matsubara>  * Oops report & Critical Bugs & Broken scripts
[16:02] <matsubara>  * Operations report (mthaddon/Chex/spm/mbarnett)
[16:02] <matsubara>  * DBA report (stub)
[16:02] <matsubara>  * Proposed items
[16:02] <matsubara> [TOPIC] * Actions from last meeting
[16:02] <MootBot> New Topic:  * Actions from last meeting
[16:03] <matsubara>     * barry to continue debug on bug 403606 after finishing 3.0 UI stuff
[16:03] <matsubara>     * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it
[16:03] <danilos> matsubara: yes
[16:03] <matsubara> I still suck, haven't done that one.
[16:03] <matsubara> [action]  * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it
[16:03] <MootBot> ACTION received:   * matsubara to trawl logs related to high load on edge yesterday and ping Chex about it
[16:04] <matsubara> EdwinGrubbs, I'll keep the action item for barry in the list since 3.0 crazyness is not over yet :-)
[16:04] <matsubara> [action] * barry to continue debug on bug 403606 after finishing 3.0 UI stuff
[16:04] <MootBot> ACTION received:  * barry to continue debug on bug 403606 after finishing 3.0 UI stuff
[16:04] <matsubara> [action] matsubara to update translations qa contact on meeting agenda page
[16:04] <MootBot> ACTION received:  matsubara to update translations qa contact on meeting agenda page
[16:05] <matsubara> [TOPIC] * Oops report & Critical Bugs & Broken scripts
[16:05] <MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
[16:05] <matsubara> Ursinha, go ahead
[16:06] <matsubara> hmm Ursinha was having connectivity problems before the meeting
[16:07] <danilos> ok, so, let me take over for what I can
[16:08] <danilos> bac is doing a great job with managing release of 3.0 and any critical bugs
[16:08] <danilos> what we've seen is already listed on https://dev.launchpad.net/CurrentRolloutBlockers
[16:08] <bac> thanks.  getting lots of good help.
[16:08] <danilos> we have noticed increased timeouts on production DBs, due to postgres restart
[16:09] <danilos> for more details, Ursinha will have to fill us in
[16:09] <matsubara> we had a bunch of disconnection errors as well
[16:09] <danilos> matsubara: around the time of rollout or? (because that'd be expected if so)
[16:09] <matsubara> danilos, not sure, Ursinha just sms'ed me and asked me to bring it up
[16:10] <matsubara> but I take the increase on those are due to the rollout, yes
[16:11] <matsubara> so, Ursinha and I will keep looking for the new oopses that happened since the rollout
[16:11] <danilos> matsubara: I suggest we get more detailed input from Ursula when she shows up back online, but go on with the meeting for now; for what we know, all critical issues are being taken care of, and we are hoping for a re-rollout tonight
[16:11] <matsubara> and let each affected team about them and add them to the CRB page
[16:11] <danilos> matsubara: thanks matsubara, that'd be great
[16:11] <matsubara> we had some script failures as well related to the rollout
[16:11] <matsubara> and another one unrelated which bigjools already replied to
[16:12] <matsubara> (which is the packagediffs thing)
[16:12] <matsubara> we have 6 critical bugs
[16:12] <bigjools> fixed in the rollout
[16:13] <matsubara> 2 fix committed, 3 in progress and one triaged
[16:13] <matsubara> danilos, the one triaged is in rosetta. what's up? are you expecting to land code for that one for the second rollout?
[16:13] <matsubara> bac, do you have a time for the second rollout?
[16:14] <danilos> matsubara: it's in progress
[16:14] <matsubara> thanks bigjools
[16:14] <matsubara> danilos, I mean bug 435891
[16:14] <danilos> matsubara: it's in progress
[16:14] <bac> matsubara: we anticipate a second roll out.  perhaps later today, though no decision has been made yet.
[16:14] <matsubara> danilos, it's not what LP says :-)
[16:15] <danilos> matsubara: it's what I say :)
[16:15] <danilos> bug 435891 is in progress :)
[16:15] <matsubara> danilos, I trust you to beat LP and make it behave :-)
[16:15] <matsubara> thanks danilos
[16:15] <danilos> the other in-progress one is almost landed (in pqm)
[16:15] <flacoste> matsubara: Disconnection errors
[16:15] <flacoste> about them
[16:16] <flacoste> do you know if they happened before or after the roll-out?
[16:16] <flacoste> if they happened before/during the roll-out they are expected
[16:16] <flacoste> we had a bug, now fixed, that logged DisconnectionError as regular OOPS
[16:16] <bac> are you in the production meeting?
[16:16] <flacoste> where it should be logged as a soft oops
[16:16] <danilos> bac: yes, this is the production meeting
[16:16] <bac> sorry, wrong window
[16:16] <flacoste> so DisconnectionError logged after the roll-out are a problem
[16:16] <matsubara> flacoste, after the meeting I'll generate a new summary to find that out.
[16:17] <flacoste> ones before or during it (when running with unfixed code) is not a problem
[16:17] <matsubara> [action] matsubara to generate new oops summary including oopses only for after the rollout
[16:17] <MootBot> ACTION received:  matsubara to generate new oops summary including oopses only for after the rollout
[16:17] <flacoste> matsubara, bac: we can determine the second roll-out time after we have that report
[16:18] <bac> matsubara: i was just made aware of bug 435628 that the bugs team is working on for a re-roll
[16:18] <matsubara> I'll defer the answer to bac
[16:18] <stub> barry was going to look at annotating those oopses so we can tell if they where DisconnectionErrors returned to users, or just part of the normal reconnection workflow.
[16:19] <bac> matsubara: i agree with flacoste that we can make a decision after getting your report
[16:19] <matsubara> all right
[16:19] <stub> erm... gary... not barry
[16:19] <gary_poster> :-)
[16:19] <matsubara> heh
[16:19] <matsubara> ok, I think that's all for this section
[16:19] <matsubara> let's move on
[16:20] <matsubara> thanks everyone!
[16:20] <matsubara> [TOPIC] * Operations report (mthaddon/Chex/spm/mbarnett)
[16:20] <MootBot> New Topic:  * Operations report (mthaddon/Chex/spm/mbarnett)
[16:20] <Chex> HI everyone, brief LOSA report this week.
[16:20] <Chex> - LP 3.0 rollout: The rollout dominated Launchpad work this week. Briefly, things went fairly well, we
[16:20] <Chex> observed a number of items in the rollout process that are being addressed.  We have emailed out the
[16:20] <Chex> full report today.
[16:21] <Chex> And that it for us, unless anyone has questions?
[16:22] <gary_poster> three cheers for losas. :-)
[16:22] <matsubara> thanks Chex
[16:22] <mthaddon> gary_poster: I think you mean three *beers* for each losa...
[16:22] <gary_poster> lol, yeah, probably more appreciated
[16:22] <mthaddon> :)
[16:22]  * stub raises a glass and says 'cheers'
[16:23]  * Chex drinks to that
[16:23] <danilos> so, drunken DB report comes next? :)
[16:23] <matsubara> let's go to the bar, err, move on
[16:23] <matsubara> [TOPIC] * DBA report (stub)
[16:23] <MootBot> New Topic:  * DBA report (stub)
[16:24] <drunken_master> Database update seems to have gone smoothly apart from Bug #435674 being discovered. This will have caused a short hang of the SSO servers, but it was probably quick and hopefully nobody noticed.
[16:24] <danilos> :)
[16:24] <drunken_master> After the update, I needed to do some data migration.  All done now and load is back to normal. This will have contributed to timeouts, so you may wants to attribute timeouts before 1200 UTC to this.
[16:24] <drunken_master> The appservers where observed in the wild basing their decision to use the slave database on how lagged that particular slave is, not how lagged the cluster is as a whole. This means that building new slave databases will no longer stop the appservers going into master-only mode.
[16:24] <rockstar> :)
[16:24] <drunken_master> oot.
[16:24] <gary_poster> lol
[16:24] <mbarnett> heh
[16:25] <danilos> thanks for the update drunken_master, always appreciated
[16:25] <matsubara> thanks stub
[16:26] <matsubara> [TOPIC] * Proposed items
[16:26] <MootBot> New Topic:  * Proposed items
[16:26] <matsubara> no proposed items
[16:26] <matsubara> anything else before I close?
[16:26] <matsubara> hi Ursinha
[16:26] <matsubara> just in time :-)
[16:26] <Ursinha> I just want to say sorry
[16:27] <Ursinha> and congrats to all lp team because LP 3.0 rocks
[16:27] <Ursinha> :)
[16:27] <matsubara> indeed!
[16:27] <matsubara> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
[16:27] <matsubara> #endmeeting
[16:27] <MootBot> Meeting finished at 10:27.
[16:27] <gary_poster> thank you!


 So guys, vmware called and told me they are preparing my offer
 Ohhhhh snap
 I'm freaking out. Scared about the move. Excited
 It's big but it will be awesome dude
 vmware...
 I applied for a job at vmware
 I'll be living near Aaron
 \o/
 very nice
 That's Awesome congrats @govatent
 Everyone is moving on up
 The problem will be my mom.
 Once I sign the offer I'll tell her
 She's gonna be so upset
 Yea that's tough
 I hope you don't expect us to plan another going away party
 Lol
 Oh BTW
 XD
 Next week I'm talking at a vmware user group on behalf of my vendor tintri
 It's at um.
 5 pm follow by free food on drinks on tintri
 I'll send you the link to register if anyone wants to go.
 It'd be cool for some additional support
 When? I will have to see
 I'm talking about how their product improved our network
 I'll get you the deets
 https://community.vmug.com/events/event-description?CalendarEventKey=c130209d-92ae-459c-b366-3e6aaee95e15&CommunityKey=61865ca2-538e-4ade-bfd7-3568b00c1766&Home=%2fcommunities%2flocalcommunityhome
 That's the link to the event. If you are able to make it out, try and register cause they want a head count
 Hank the keynote speaker is my sales engineer for my account. He's really nice and cool. I'm talking during his speech on behalf of my company
 Ya think there's enough open iot thermostats?
 You should hack them for your "perfect" temperature.
 IoT, overwhelming complexity in overwhelming combinations


[02:09] <bud32> Hi :) what means "intelfb: cannot reserve FB region" ? This message appears on system boot. I have a custom config for this kernel. I saw the code... drivers/video/intelfb/intelfbdrv.c:568, does cleanup() then return means that the intelfb is not actually used / completely initialized? I tried without the driver, but I couldn't use tty's.
[03:23] <atrus> at some point I used to be able to put a script into /etc/acpi/resume.d (in particular 99-xrandr.sh), and have it run when I resume from suspend, but now that doesn't seem to happen. Has that behavior changed, or am I doing something wrong?
[03:23] <J-Unit> atrus: yeah it's now /etc/pm.d/suspend.d or somethig of that sort
[03:24] <atrus> J-Unit: hmm. /etc/pm.d has nothing but 3 empty subdirectories.
[03:25] <J-Unit> atrus: yeah.... I wish I remember the correct format off the top of my head
[03:25] <J-Unit> but currently I'm on a RHEL box and can't check
[03:25] <J-Unit> ubuntu land is suffering a power outage ;-)
[03:25] <atrus> heh. well, it gives me something else to google for anyways :)
[03:26] <J-Unit> it's the standard pm-utils script format
[03:26] <J-Unit> list the contents of pm-utils
[03:26] <J-Unit> and in /usr/share you should see similar formatted scripts
[03:26] <J-Unit>  the /etc/ location is simply a supplement to those
[07:26] <TheInfinity> blaxun1st
[08:14] <bain> Good morning.
[08:17] <bain> Is there currently any plans for an integrated user desktop backup application ?
[08:19] <persia_ume>  What would it backup up?  To what media?  On what conditions?  There are several tools to facilitate this, with different answers to those questions available.
[08:22] <bain> persia_ume: I'm talking about an easy way to backup your desktop to usb to migrate a desktop to another machine ? medium would likely be usb since it's portable. I'm really thinking of something aimed at a newby ubuntu user
[08:41] <persia_ume> bain: Hmmm...  I suspect you're looking for something based on sbackup or hubackup, but I'm not sure.
[08:49] <jscinoz_> Is it planned to migrate to Grub2 at some point?
[08:49] <jscinoz_> as the default bootloader
[09:33]  * pitti takes a stab at the xargs b0rkage in intrepid
[10:03] <stgraber> pitti: where are you ? :) I don't see you at the 3rd floor (or you are behind me)
[10:03] <pitti> stgraber: I'm in my room; is there wifi still?
[10:03] <stgraber> yep
[10:04] <stgraber> I guess we are like 20 here using the fosscamp wifi, it's still really fast and working just fine
[10:06] <pitti> coming down then
[10:44] <pitti> StevenK: I shouldn't have said it so loud ... http://launchpadlibrarian.net/14584191/buildlog_ubuntu-intrepid-i386.findutils_4.4.0-2ubuntu2_CHROOTWAIT.txt.gz
[10:45] <pitti> infinity: so, my new upload of findutils to fix the xargs b0rkage doesn't build, because it fails with that very xargs crash; that requires some manual building, I figure?
[10:48] <pitti> lamont: ^
[11:01] <kahrytan> What is being done to prevent what happened with SSH keys  in debian/ubuntu to never happen again?
[11:02] <jdavies> !libsslbug > kahrytan
[11:02] <pitti> kahrytan: that's one of the bad things in the world, you can only defend against catastrophes that already happened; but there are infinitely many more ways to break something
[11:03] <pitti> kahrytan: but this certainly helped to raise awareness and caution a lot
[11:03] <kahrytan> Was that package only managed by 1 person?
[11:05] <pitti> two at the moment
[11:05] <kahrytan> At the time of issue?
[11:06] <RAOF> tjaalton: You were the person interested in putting nouveau into experimental, right?  I'm currently playing around with module-assistant-ing the drm modules, which may make that easier/possible.
[11:06] <kahrytan> This just proves that two or more people needs to over see code before it comes mainstream.
[11:06] <tjaalton> RAOF: right, it was discussed recently on debian-x@
[11:07] <RAOF> tjaalton: Ah.  I'm obviously not subscribed to that; is there a one line summary?
[11:07] <tjaalton> RAOF: "hard" :)
[11:08] <tjaalton> to maintain, at least
[11:08] <RAOF> Right.  Because you sometimes need new snapshots of libdrm for new snapshots of nouveau.
[11:08] <tjaalton> yep..
[11:08] <RAOF> And you want to keep reasonably current with nouveau, so...
[11:09] <RAOF> Well, after I've tested this, it'll be possible to point debian people at my source packages, at least.
[11:09] <tjaalton> there really ought to be a new libdrm release soon, since X 7.4 basically can't release without it
[11:09] <RAOF> Oh, DRI2.
[11:09] <tjaalton> right
[11:10] <tjaalton> unless they demote it as experimental
[11:10] <kahrytan> pitti,  The funny thing about this.. this was one my parents worest fears about linux. What is stopping coders from putting backdoors/security holes in code?
[11:10] <pitti> kahrytan: that's not a linux specific problem
[11:10] <RAOF> tjaalton: By 'they', you mean Debian-X?  Or upstream?
[11:11] <kahrytan> pitti,  but it's easier to do for a hacker in oss.
[11:11] <soren> kahrytan: Err? Why?
[11:11] <pitti> kahrytan: there was one such case in Debian that I faintly remember, and it was discovered pretty fast and the code got a big audit
[11:11] <ivoks> kahrytan: how? other hackers could check source
[11:11] <kahrytan> pitti,  Yet, ths ssh one didnt get discovered for awhile
[11:11] <ivoks> kahrytan: that's much easier to do in closed source; no one but you could check the source
[11:11] <tjaalton> RAOF: upstream
[11:11] <pitti> kahrytan: no, you can't "just do" it, you need to earn credibility and permissions first
[11:12] <soren> kahrytan: If there's a backdoor in a closed source product, noone will discover it. In free software, eventually someone will discover it.
[11:12] <ivoks> kahrytan: do you know how many of those are in closed source world? :)
[11:12] <RAOF> tjaalton: That would suck.  DRI2 brings world peace.  It'd be nice to have in Intrepid :)
[11:12] <kahrytan> ivoks,  How many people work for close source developer?
[11:12] <ivoks> kahrytan: a lot less than on open source
[11:13] <virtuald> were the other vulns in that dsa from debian or wideopenbsd?
[11:13] <kahrytan> I just know if this happens again, it will hurt OSS more then anyone realizes.
[11:13] <tjaalton> RAOF: yeah..
[11:14] <ivoks> kahrytan: it might seem like that, yes... but you have to wonder... are you sure this kind of thing never happend anywhere else?
[11:14] <pitti> kahrytan: I'm undecided on that; on the one hand it proves transparency, on the other hand you always lose a big chunk of trust on those
[11:14] <ivoks> we aren't silent about our problems, closed source vendor are
[11:14] <kahrytan> ivoks,  On the one hand,  It didnt take long to fix it.  M$ would have waited til patch Tues.
[11:14] <ivoks> kahrytan: MS wouldn't patch that at all
[11:15] <pitti> closed source devs aren't invincible against making stupid errors either, we are all just humans
[11:15] <ivoks> at least, not the way we did
[11:15] <kahrytan> They would patch it but not tell anyone
[11:15] <virtuald> how do you define aren't silent?
[11:15] <pitti> under that assumption, the OS/CS quality wrt. to those incidents doesn't make much of a difference
[11:15] <virtuald> In addition to this critical change, two other vulnerabilities have been fixed in the openssl package which were originally scheduled for release with the next etch point release: OpenSSL's DTLS (Datagram TLS, basically "SSL over UDP") implementation did not actually implement the DTLS specification, but a potentially much weaker protocol, and contained a vulnerability permitting arbitrary code execution (CVE-2007-4995).  Now does Ubuntu installer do it automatically?
[11:21] <ivoks> this, of course, isn't support channel
[11:22] <pitti>  kahrytan: we also have this "migration assistant" in the installer which keeps some settings (or the partitioner keeping your /home dir)
[11:22] <kahrytan> ivoks,  just showing some feature seeds. :-P
[11:22] <ivoks> pitti: right, it can even import your windows settings :)
[11:22] <kahrytan> pitti,  You mean the migration assistant for windows prefs?
[11:23] <kahrytan> The same assistant that failed to work in Ubuntu 8.04?
[11:23] <ivoks> kahrytan: file a bug
[11:23] <pitti> kahrytan: it also imports Firefox/Pidgin from Linux installs
[11:23] <pitti> but I haven't used it much, I just keep my /home forever
[11:24] <kahrytan> It's supposed to do that import from prev installs?
[11:24] <pitti> you can tell it to
[11:24] <kahrytan> Wouldnt know how to.
[11:25] <kahrytan> I just thought no one tried to add it since either of install screens asked about it.
[11:40] <evand> It's not shown if it cannot do anything, such as when you're overwriting the partition in question.
[11:41] <evand> err, the partition that you would be importing from.
[12:57] <Samsemilia> ,seen mvo
[12:58] <Samsemilia> !seen mvo
[12:59] <Hobbsee>  /msg seenserv seen mvo...
[13:03] <Keybuk> Preparing to replace debconf 1.5.20 (using .../debconf_1.5.21_all.deb) ...
[13:03] <Keybuk> xargs: xargs.c:443: main: Assertion `bc_ctl.arg_max <=<PHONE_NUMBER>)' failed.
[13:03] <Keybuk> EPIC.
[13:03] <Keybuk> FAIL.
[13:04] <TheMuso> eh
[15:33] <lamont> pitti: that or an upload that builds without needing xargs...
[16:40] <pitti> lamont: that's hard, since debconf is already in the chroot, and it fails to upgrade; there's no way how to fix it with dropping build deps
[16:41] <pitti> lamont: I guess one would need to download the chroot, hit debconf over the head to install properly, save it, and upload it back?
[17:00] <lamont> pitti: ew
[17:29] <amitk> Keybuk: https://edge.launchpad.net/~kernel-ppa/+archive
[17:32] <Keybuk> amitk: ah, thanks
[17:32]  * Keybuk kills the heater
[17:56] <infinity> pitti: Probably, yeah.
[18:43] <dondelelcaro> hey; is there a UDS specific channel?
[18:49] <KristianL> yeah, #ubuntu-devel-summit
[18:52] <dondelelcaro> ah, thanks
[20:04] <emgent`UDS> heya
[20:25] <pitti> hey emgent
[20:28] <emgent> hey pitti :)
[20:28] <emgent> fosscamp AP r0cks!


[08:00] <Saviq> Moaning.
[08:21] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2766](https://github.com/MirServer/mir/pull/2766): spread: improve local experience
[08:21] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq edited [pull request #2765](https://github.com/MirServer/mir/pull/2765): spread/sbuild: Don't purge the schroot session, more for local runs
[08:32] <Saviq> Hmm. This is the first time I've seen this in the lab:
[08:32] <Saviq> > Mir fatal error: surface observer should have been deleted, but was not (use count 2)
[08:32] <Saviq> Which is suspect, because we actually had a fix for that…
[09:08] <Saviq> A re-run worked, something I'll keep an eye on
[09:15] <alan_g[m]> There might be another cause?
[09:16] <Saviq> Sure could
[09:57] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned  to [pull request #2769](https://github.com/MirServer/mir/pull/2769): all: drop Canonical copyright year
[10:16] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned AlanGriffiths to [issue #2632](https://github.com/MirServer/mir/issues/2632): Miriway frequently crashes to GDM after exiting powersave
[10:24] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [pull request #2771](https://github.com/MirServer/mir/pull/2771): ci: better LP creds location
[10:53] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [issue #2772](https://github.com/MirServer/mir/issues/2772): wlcs.PrimarySelection tests failing on PowerPC... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/7a9e31c311685edf56158585d45f8c99de4b6c2e>)
[10:54] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq edited [issue #2772](https://github.com/MirServer/mir/issues/2772): wlcs.PrimarySelection tests failing on PowerPC
[10:55] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq added bug to [issue #2772](https://github.com/MirServer/mir/issues/2772): wlcs.PrimarySelection tests failing on PowerPC
[10:57] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [issue #2773](https://github.com/MirServer/mir/issues/2773): BadBufferTest.client_lies_about_buffer_size dies on PowerPC... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/c225883ef77dd5d13043a0656624257a61df6fd6>)
[10:59] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [issue #2774](https://github.com/MirServer/mir/issues/2774): A couple ShmBacking.* tests failing on PowerPC... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/ca04dfd996c6a22ff787a1dde38c4c83466b2dba>)
[10:59] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq added bug to [issue #2774](https://github.com/MirServer/mir/issues/2774): A couple ShmBacking.* tests failing on PowerPC
[11:45] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq merged [pull request #2771](https://github.com/MirServer/mir/pull/2771): ci: better LP creds location
[13:43] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq merged [pull request #2765](https://github.com/MirServer/mir/pull/2765): spread/sbuild: Don't purge the schroot session, more for local runs
[14:05] <Saviq> FWIW I couldn't reproduce any of the powerpc64 failures under qemu, so I can organize access to HW.
[14:08] <alan_g[m]> Ack. I suspect it is differences in detecting access faults and not something we can do much about.
[15:33] <alan_g[m]> Mir2 is in for Debian: https://tracker.debian.org/pkg/mir
[15:37] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [pull request #2775](https://github.com/MirServer/mir/pull/2775): bors: skip snapping
[15:37] -GitHub[m]:#mir-server-
[15:37] -GitHub[m]:#mir-server- > This was just a waste, never uploaded anywhere and not looked at by bors.
[15:37] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [pull request #2776](https://github.com/MirServer/mir/pull/2776): debian: use newer -dev packages
[15:37] -GitHub[m]:#mir-server-
[15:37] -GitHub[m]:#mir-server- > Those were highlighted by Debian's linter.
[16:48] <Saviq> I'm out for today o/
[16:54] -GitHub[m]:#mir-server- **[MirServer/mir]** dobey opened [issue #2777](https://github.com/MirServer/mir/issues/2777): Support for input-method-unstable-v1... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/49fbd5a2b71239f74027e99052afa95081a3cb5b>)
[17:25] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths unassigned AlanGriffiths from [issue #2632](https://github.com/MirServer/mir/issues/2632): Miriway frequently crashes to GDM after exiting powersave
[18:08] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [issue #2778](https://github.com/MirServer/mir/issues/2778): Time to refresh xdg-shell implementation... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/d6a12625a58ee6ba50955d1165861e263d9122bd>)
[19:02] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2775](https://github.com/MirServer/mir/pull/2775): bors: skip snapping


[09:58] <gary4gar>  how to make deb files?
[10:57] <ubotu> New bug: #178064 in ubuntu-docs (main) "Documentation Error: IP Masquerading" [Undecided,New] https://launchpad.net/bugs/178064