[10:41] <jpatrick> Gary: heh, Hobbsee threw you out by accident
[10:41] <Gary> misfire!
 gah, forgot the colon.
[23:45] <kris> hi can i have a hostname cloak ?


[08:07] <fabbione> BenC: ok, i did rename and added more stuff :) go ahead to pull anytime..
[11:31] <Tode> Hi there
[11:31] <Tode> at last I arrived in the good place
[11:31] <Tode> (I hope)
[11:31] <Tode> I'm working for a company which doing IWB (interzctive White Board)
[11:32] <Tode> Of course, the stuff works on Window$, OS X... but not on Linux
[11:32] <Tode> I'm product manager for France
[11:32] <Tode> I'd like to develop a driver for Linux
[11:32] <Tode> GPL of course
[11:33] <Tode> I don't have yet the right to give specs
[11:33] <Tode> but I'm working on it
[11:33] <Tode> as the HQ thinks Linux is not a priority, I think they'll be glad not to have to develop this themselves...
[11:33] <Tode> (I hope...)
[02:37] <zul> heylo
[02:38] <fabbione> hey zu
[02:38] <fabbione> l
[02:41] <zul> did you get my msg yesterday?
[02:45] <fabbione> zul: yes, it's fine by me
[02:45] <fabbione> the only issue i have is that i still don't know if my mobile phone will work there
[02:46] <fabbione> so we need to find a way to meet up
[02:55] <zul> well i could call your room
[02:58] <fabbione> i think we should talk later with jbailey
[02:59] <fabbione> we will probably be around playng turists ;)
[03:00] <zul> heh...i been to montreal a couple of times for the summer, my grandmother lived there for a while before she moved away
[03:03] <fabbione> i have never been there
[03:03] <fabbione> i still need to figure what to visit :)
[03:21] <jbailey> fabbione: Montral is well known for its bagels, the fact that it allowed 18 years olds to drink, and the strip clubs in the middle of the office district. =)
[03:21] <jbailey> fabbione: I need to spend some time on the wiki today posting StuffAboutMontral
[03:21] <fabbione> jbailey: hahah
[03:22] <Mithrandir> is it particular for places in .ca that 18 year olds are allowed to drink?
[03:22] <jbailey> Mithrandir: Yes.  Only Qubec and Alberta allow it.
[03:22] <jbailey> Everyone else requires one to be 19.
[03:22] <mjg59> jbailey: What character set are you sending?
[03:22] <Mithrandir> jbailey: utf8, I think
[03:23] <jbailey> What's funny is that a kid in the youthgroup/sexed class that I used to teach is coming to visit us in Feb for her 18th birthday.   So why can't I see any of your accented characters.
[03:23] <mjg59> Bloody screen.
[03:24] <jbailey> mjg59: I'm in screen too, so if could be confused.
[03:25] <mjg59>
[03:25] <Mithrandir> jbailey: it looks good to me, and I know utf8 works for me.
[03:25] <mjg59> Ought to be accented e
[03:26] <Mithrandir> mjg59: that's double-encoded.
[03:26] <mjg59> Fuckit.
[03:26] <Mithrandir> mjg59: does  come out right for you?
[03:26] <jbailey> I think it's wrapped in latin-1 from the output.
[03:26] <mjg59> No
[03:26] <mjg59> Right. Now, where is this going wrong?
[03:26] <jbailey> Mithrandir: I see tahat as ae o/ a^o
[03:26] <Mithrandir> jbailey: that's correct.
[03:26] <Mithrandir> jbailey: our three scandinavian letters.
[03:26] <mjg59> Weird. If I tell screen to do 8859-1, then everything seems to work
[03:27] <Mithrandir> mjg59: screen probably thinks the window is latin1, then.
[03:27] <mjg59> Except that I'm limited to 8859 characters
[03:27] <fabbione> BenC: please git pull ssh://people.ubuntu.com/home/fabbione/public_html/archives/ubuntu-2.6
[03:27] <Mithrandir> 8859 characters should be enough for everyone!
[03:27] <fabbione> BenC: RH Cluster updates and OCFS2
[03:28] <mjg59> Ok, that works now
[03:28] <mjg59> Looks like I forgot -U
[03:31] <Mithrandir> mjg59: that shouldn't be needed if you have an UTF8 locale
[03:33] <mjg59> Well, I needed to toggle utf8
[03:39] <BenC> fabbione: doing it now
[03:39] <fabbione> BenC: cool
[03:39] <fabbione> dpkg-deb: building package `linux-image-2.6.14-1-amd64-generic' in `../linux-image-2.6.14-1-amd64-generic_2.6.14-1.1_amd64.deb'.
[03:39] <fabbione> BenC: we can get there :)
[03:40] <fabbione> now we need to configs :)
[03:40] <BenC> fabbione: I'm getting the debian config stuff in today
[03:40] <fabbione> we also need to decide how we want to release
[03:40] <fabbione> because we can't create .udebs yet
[03:40] <fabbione> or better we can
[03:40] <fabbione> but we need to fix the debian version mistmatch
[03:41] <fabbione> i am also getting a few tons of unresolved symbols on ndiswrapper for x86_64
[03:41] <BenC> odd, I'll look into those
[03:41] <mjg59> We should pull in a newer ndiswrapper anyway
[03:41] <fabbione> and 2 for zd1211em8300
[03:41] <fabbione> and 2 for zd1211 em8300
[03:41] <mjg59> And newer zd1211
[03:42] <BenC> I got the newest of everything
[03:42] <mjg59> Ok
[03:42] <BenC> what were the ones for zd1211 and em8300?
[03:42] <BenC> guessing they were ieee80211 related
[03:43] <fabbione> BenC: there was a file called external-modules in debian/
[03:43] <fabbione> we lost that one in .14
[03:43] <fabbione> it was really useful in combination of uscan-extmod
[03:43] <mjg59> em8300 is a dvd decoder
[03:43] <fabbione> to track all external modules
[03:43] <BenC> fabbione: I am writing a script to pull the external-modules stuff from git log
[03:43] <mjg59> So probably not ieee80211
[03:44] <fabbione> BenC: ah ok...
[03:44] <BenC> fabbione: that's why I wanted the external modules git log setup as it was
[03:44] <BenC> less prone to user error, not updating the file and such
[03:44] <fabbione> BenC: meh
[03:44] <fabbione> i am not sure i did the commit right than
[03:44] <fabbione> i used the external-module template to update RedHat Cluster
[03:45] <fabbione> but from CVS tehre is no Mask or reference
[03:45] <fabbione> and it' not even a pure CVS because there are patches from different branches in CVS
[03:45] <BenC> well, then there's no way for it to be in external-modules file either, so no problem
[03:46] <fabbione> exactly
[03:46] <fabbione> it was there just as reference
[03:47] <BenC> Pulling from people.ubuntu.com
[03:47] <BenC>   Pulling master from fabbione
[03:47] <BenC> error: Could not read 72bed2a7edef353db682cd052776761967a3eadf
[03:47] <BenC> fatal: bad tree object 72bed2a7edef353db682cd052776761967a3eadf
[03:47] <BenC> that's odd
[03:47] <fabbione> weird
[03:48] <fabbione> let me try to push again
[03:48] <fabbione> it says it's updated..
[03:48] <BenC> I don't see that object in any of our git repo's
[03:49] <fabbione> no i don't have it either
[03:49] <fabbione> something missing from linus?
[03:50] <BenC> checking
[03:54] <BenC> I need to go buy my UBZ laptop today :)
[03:55] <fabbione> ehehe
[03:55] <fabbione> i ordered a powerbook
[03:55] <fabbione> but didn't arrive in time
[03:55] <fabbione> it will arrive while i am at UBZ :(
[03:55] <fabbione> royal suckage
[03:55] <dilinger> i'm considering buying an x41
[03:56] <mjg59> X40 has better battery life than the X41, it seems
[03:56] <dilinger> oh/
[03:56] <dilinger> ?
[03:56] <fabbione> dilinger: i don't want to see anything i386 related anymore
[03:56] <dilinger> fabbione: they're so light, ~3lbs
[03:56] <fabbione> dilinger: i am strong enough to lift weight :)
[03:57] <BenC> I think I'll be gettng a powerbook aswell
[03:57] <BenC> at the very least, an amd64
[03:57] <fabbione> BenC: be careful if you buy a powerbook
[03:57] <dilinger> fabbione: my commute to work involves a 30 min walk each way.  the lighter my laptop, the better :)
[03:57] <fabbione> because the new serie just come out
[03:57] <fabbione> dilinger: my commute is about 20 secs walk :)
[03:58] <fabbione> HOLY COW
[03:58] <fabbione> it has been shipped
[03:58] <fabbione> it might arrive tomorrow!
[03:58] <fabbione> no
[03:58] <fabbione> for sure it will arrive the 26th
[03:58] <jbailey> dilinger: I sort of miss the 30 minute walk to work. =)  It means I have to remember to exercise. =)
[03:59] <dilinger> jbailey: it's not a very nice walk.  past the hole that was the world trade center, through a wind tunnel... :/
[04:01] <jbailey> dilinger: Sure, but I miss NYC. =)
[04:02] <jbailey> dilinger: Have they started building there yet?
[04:02] <BenC> fabbione: wow, your git tree is borked
[04:02] <dilinger> yea
[04:02] <BenC> fabbione: run "git-fsck-objects"
[04:03] <fabbione> BenC: borked how?
[04:03] <dilinger> it looks like they're just getting scaffolding up
[04:03] <BenC> fabbione: no idea, but git-fsck-objects should show a whole lot (like 3-4 lines on my tree)
[04:03] <fabbione> BenC:  i get 4 entries
[04:03] <fabbione> dangling tag a1aeb6f9e4306b1a62629c56197eea65afd372b3
[04:03] <fabbione> dangling commit ba9e358fd04190a59e605c2963a15e014139a707
[04:03] <fabbione> dangling tag c08359b174c3b3a175979f81cc786c791f74c852
[04:03] <fabbione> dangling tag f92737b18abac90af30ac26a050fda879c9b238b
[04:03] <fabbione> that's it
[04:04] <BenC> your one on rookery isn't so clean
[04:04] <fabbione> BenC: i only push there
[04:04] <BenC> several doze screen fulls before I just hit ^C
[04:04] <fabbione> i can still nuke it and repush it
[04:04] <BenC> and
[04:04] <BenC> yeah, that sounds good
[04:05] <fabbione> BenC: can you remember the git clone options for it?
[04:05] <BenC> -n -s -l
[04:07] <fabbione> pushing now again
[04:08] <fabbione> BenC: done
[04:08] <fabbione> you can try to pull
[04:09] <BenC> working now
[04:09] <fabbione> i don't understand why tho
[04:10] <BenC> the downside of git...very untested
[04:11] <BenC> ok, as soon as this pull is done, I'll push it back out to k.o
[04:11] <fabbione> ok
[04:11] <BenC> thanks
[04:11] <fabbione> for what? :)
[04:12] <BenC> for getting the last two major drivers in the tree and getting debian/rules cleaned up :)
[04:12] <fabbione> there is still a lot that can be cleaned
[04:17] <BenC> I'm sure I'll be getting neck deep in the build today
[04:20] <fabbione> BenC: amd64 builds :)
[04:20] <fabbione> tomorrow i will do an i386 build and test
[04:22] <infinity> When you guys get half-ass sane and working builds going, I'd love a pointer to some pre-built i386 packages, so I can start wrangling the new version of linux-restricted-modules to build with the new kernel.
[04:22] <infinity> I have a feeling some hackery on my part will be required, and I'd rather clear it up as soon as I can.
[04:22] <fabbione> infinity: yup
[04:24] <fabbione> anyway i am off for a little nap
[04:24] <fabbione> head is exploding
[04:24] <BenC> infinity: I'm hoping to have a really solid build before I got to UBZ this weekend
[04:24] <BenC> later fab
[05:07] <zul> BenC: B
[05:10] <BenC> hey zul
[05:29] <zul> er...did you get my msg last night
[05:30] <BenC> guess not :)
[05:31] <zul> i was thinking since im going to be in montreal on saturday why dont a few of us get together for dinner
[05:31] <BenC> I wont be there until Sunday
[05:31] <zul> ah never mind then :)
[05:32] <BenC> will yu be around then?
[05:34] <zul> yeah i will..ill be there until 2 and then i have to head back to ottawa
[05:36] <zul> i have very expensive hockey tickets for that night ;0
[05:38] <mkrufky> benc: am i correct in assuming that you will stop git merges from upstream once 2.6.14 mainline gets released?  (with the exception of 2.6.14.y merges)
[05:38] <mkrufky> ( i can already see some of my patches got merged into your tree 99 minutes ago ;-)
[05:39] <BenC> mkrufky: depends if we decide to move on to 2.6.15 or not
[05:40] <BenC> I think if we do frequent releases, we can keep moving
[05:42] <mkrufky> okay, that makes sense.... I kind of assumed that you would be working against 2.6.14 for released until 2.6.15 becomes stable
[05:42] <mkrufky> s/released/releases
[05:42] <mkrufky> there are a whole bunch of radical changes on the table for 2.6.15, so i think this one is going to have a long dev cycle
[05:43] <fabbione> re
[05:44] <mkrufky> anyhow, I figured I would wait for 2.6.14 official release before I send patches your way.  There isnt any time constraints that I should be worried about is there?
[05:45] <fabbione> mkrufky: yes.. you need to take into account the release schedule
[05:46] <mkrufky> is it posted anywhere?
[05:46] <fabbione> https://wiki.ubuntu.com/DapperReleaseSchedule?highlight=%28dapper%29
[05:46] <mkrufky> perfect, thanx
[05:48] <mkrufky> hmm... if you are going to continue to take post-2.6.14 merges, then it will not be necessary for me to send you any patches.......
[05:50] <mkrufky> the whole reason why i was going to do this was so that ubuntu users wouldn't have to mess with cvs in order to get support for new v4l/dvb hardware .... It looks like it might not be necessary, because we will probably be sending our next patchset to linus before your code-freeze
[05:50] <fabbione> mkrufky: we will see how it goes
[05:50] <mkrufky> we will be sending within 2 weeks of 2.6.14 release
[05:50] <mkrufky> yup
[05:50] <dilinger> how serious are people about keeping upstream versions frozen instead of taking another snapshot of sid, as jdub's email mentioned?
[05:51] <fabbione> dilinger: read the above url
[05:51] <fabbione> jdub has been overruled by *
[05:51] <mkrufky> anyhow, if somehow we miss the cutoff, there are only 2 post-2.6.14 patches that i am concerned about hitting the distros ... I guess we'll deal with it when the time comes
[05:52] <BenC> mkrufky: is v4l/dbd using git yet?
[05:52] <BenC> dvb
[05:52] <mkrufky> I am going to set up my own git repository, but we will not have an official one for a while
[05:52] <mkrufky> the problem is:
[05:52] <mkrufky> v4l is like an umbrella subsystem
[05:53] <mkrufky> dvb is its own subsystem
[05:53] <mkrufky> but we depend on each other
[05:53] <dilinger> fabbione: excellent
[05:53] <dilinger> fabbione: that just seemed like a bad idea :)
[05:53] <mkrufky> v4l is absorbing ivtv, in addition to some other subsystems
[05:53] <mkrufky> and it is problematic for a single maintainer to handle
[05:53] <mkrufky> this is the reason why we dont have a git repo yet
[05:54] <mkrufky> I want to set one up, to see how it goes, all i need is a server to host it on
[05:54] <mkrufky> if all works out, we can eventually migrate all development to -git
[05:54] <BenC> mkrufky: email<EMAIL_ADDRESS>and ask for an account there
[05:55] <mkrufky> is it really that simple?
[05:55] <mkrufky> i will do it :-D
[05:55] <BenC> email them a username, a gpg key, an ssh pub key, and your reason fort an account
[05:55] <mkrufky> s/gpg/pgp , right?
[05:56] <BenC> doesn't really matter
[05:56] <BenC> no one uses pgp though :)
[05:56] <mkrufky> hmmm... then i dont know what gpg is
[05:56] <BenC> GnuPG
[05:57] <mkrufky> lol i should have known
[05:57] <BenC> the free pgp :)
[05:57] <mkrufky> heh
[05:58] <mkrufky> okay, well i'll send them an email later on..... I think that having a "media" tree that would centralize all the dvb/v4l/usbvision stuff would make it a lot easier for us to spot regressions, etc...   I'll let u know when thats ready
[05:59] <BenC> then I can easily pull from it
[06:00] <mkrufky> ya i think it will make things MUCH easier for everyone
[06:00] <mkrufky> :-)
[08:01] <fabbione> BenC: 2 questions.. how are we going to stop autopulling from linus tree? and how can you do cherry picking in git?
[08:02] <BenC> you shouldn't be auto-pulling from linus
[08:02] <BenC> git pull may read objects from linus, but it doesn't pull them in
[08:03] <BenC> I'll have to read up on cherry-picking, but I know it's possible
[08:03] <BenC>   Dynamically convert lock's to nop's on UP machines (SMP2UP) [N/y/?]  (NEW)
[08:03] <BenC> this will be an interesting test
[08:04] <dilinger> is that patch in your repo?
[08:04] <dilinger> or online somewhere/
[08:04] <dilinger> ?
[08:04] <BenC> search google for "Speedup SMP kernel on UP box"
[08:04] <BenC> very old patch that I want to test for dapper
[08:05] <fabbione> ah
[08:05] <fabbione> nice
[08:05] <BenC> probably commit it, but not have it enabled for first release
[08:05] <fabbione> (the patch)
[08:05] <fabbione> BenC: i suggest you enable as much crack as possible in the beginning instead
[08:05] <fabbione> because it's the best moment to crash test the kernel
[08:06] <BenC> true
[08:06] <fabbione> we will have a couple of months to play hard. probably less
[08:06] <fabbione> after that we need to stabilize
[08:06] <fabbione> so it's much better to use this time in the best way as possible
[08:07] <fabbione> also because the first uploads will not expose .14 as default kernel
[08:07] <fabbione> we can decide when to force it as such
[08:07] <fabbione> so it will in Universe -> not supported.. for a little while.. and that's DOH! a case ;)
[08:08] <dilinger> BenC: so Paul Gortmaker's patch w/ Dan Jacobowitz's modification?
[08:18] <BenC> yes
[08:19] <BenC> I should add a command line option to allow for forcing the option on/off for testing
[08:19] <fabbione> BenC: nah.. let's just push it
[08:19] <fabbione> we can make these kind of adjustment later on
[08:19] <fabbione> and probably add a TODO list in debian/
[08:22] <BenC> fabbione: no, I want it on by default, but I want to make it easy for someone to do "smp2up=off" to see if the problem they are having is related to this feature
[08:22] <BenC> no sense in making it hard to debug
[08:22] <fabbione> right
[08:23] <BenC> fabbione: split config stuff from debian package is working now
[08:23] <BenC> i386 configs done
[08:23] <fabbione> cool
[08:23] <BenC> I'll have all the arch's compilable by tonight
[08:23] <BenC> except for hppa of course :)
[08:24] <fabbione> yeah
[08:24] <BenC> smoke break
[08:24] <fabbione> we need to talk with lamont about it
[08:24] <fabbione> ehehe
[08:24] <fabbione> enjoy
[08:24] <fabbione> film break
[08:24] <fabbione> before conference call
[08:24] <fabbione> later
[09:10] <fabbione> dilinger: did you add the OpenAFS bits to the wiki?
[09:10] <fabbione> https://wiki.ubuntu.com/UbuntuBelowZero/BOFs <- ?
[09:11] <dilinger> yes
[09:11] <fabbione> dilinger: you want to link it to launchpad and write a spec from the spec template
[09:11] <dilinger> i can, but not right now
[09:12] <fabbione> it's enough you do it before the 27th afaik
[09:12] <fabbione> otherwise it will not be scheduled
[09:12] <dilinger> ok
[09:12] <fabbione> the sooner the better
[09:59] <dilinger> hm
[09:59] <dilinger> perhaps i should make it a goal to sign my keys from UDU before going to UBZ :)
[10:00] <fabbione> dilinger: good point :)
[10:07] <dilinger> any ideas when we'll find out about the schedule?
[10:07] <dilinger> i doubt i can take the whole week off, and i'd like to be there for openafs, kernel related, and patch feeding bofs
[10:09] <fabbione> dilinger: probably in few days
[10:10] <fabbione> i expect a draft the 27/28
[10:10] <dilinger> that would be nice
[10:59] <zul> later


[01:32] <cheako> https://launchpadlibrarian.net/309340316/buildlog_ubuntu-precise-amd64.dpkg_1.17.27_BUILDING.txt.gz
[01:32] <cheako>   Launchpad is having a problem compiling binaries on precise.
[14:33] <morphis> cjwatson: ping
[14:33] <cjwatson> morphis: contentless pong
[14:34] <morphis> cjwatson: I am currently puzzeled by https://launchpad.net/~snappy-hwe-team/+snap/bluez-daily/+build/25312
[14:34] <morphis> cjwatson: it gives me a MAINTAINERS.snap as a build result which is simply the text MAINTAINERS file we have in the repository that build is building from
[14:34] <morphis> and with that the store upload fails as MAINTAINERS.snap isn't a valid snap
[14:35] <morphis> any idea what could be the reason for this?
[14:36] <cjwatson> morphis: well, snapcraft doesn't really do out-of-tree builds, it just drops the result in the directory you run it in
[14:36] <morphis> yeah
[14:36] <cjwatson> morphis: which means the best we can do in LP is to look for *.snap files in the directory, and that includes https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/bluez/tree/MAINTAINERS.snap
[14:36] <cjwatson> morphis: so I'd suggest just git mv MAINTAINERS.snap MAINTAINERS-snap
[14:36] <cjwatson> or similar
[14:36] <morphis> wuuuh
[14:36] <morphis> that slipped through ..
[14:36] <morphis> sorry
[14:37] <cjwatson> fun edge case
[14:37] <morphis> totally :-)
[16:17] <smoser> 2 questions
[16:17] <smoser> a.) where is the "test/scratch" launchpad installation that i can open bugs on and not feel wasteful?
[16:17] <smoser> b.) can i share a link like
[16:17] <smoser>  https://bugs.launchpad.net/cloud-init/+filebug?tags=foo
[16:18] <smoser> that then gets the tag applied when a bug created that way ?
[16:23] <dobey> smoser: staging.launchpad.net?
[16:24] <smoser> thats it.
[16:24] <dobey> smoser: link would be the same, but staging.bugs.launchpad.net for that example
[16:24] <dobey> or bugs.staging.launchpad.net (don't remember which way it goes)
[16:25] <dobey> probably the latter
[16:25] <smoser> it should let me SSO sign in ?
[16:26] <smoser> or do i have to register there?
[16:28] <dobey> i think it uses staging sso maybe, so login.staging.ubuntu.com
[16:29] <dobey> it's separate from production, so yeah, you need to register there if you haven't already
[16:29] <smoser> ok.
[16:29] <smoser> so "I am a new Ubuntu One user"
[16:31] <smoser> ugh
[16:31] <smoser> it wont let me create a new account because
[16:31] <smoser> a.) 'smoser' already in use
[16:31] <smoser> b<EMAIL_ADDRESS>email address is already registered.
[16:32] <smoser> but wont let me log in.
[16:32] <smoser> confused
[16:34] <dobey> do the "forgot password" thing then
[16:34] <dobey> you might have registered a long while ago perhaps :)
[16:35] <dobey> or do you mean on launchpad? i think staging gets production people/projects/stuff synced over every now and again, but the SSO db doesn't
[16:36] <smoser> well, i just hit 'login' on staging, and failed.
[16:37] <smoser> hit forgot password. we'll see. thanks dobey
[16:37] <dobey> np. good luck with it
[16:40] <smoser> gah.
[16:40] <smoser> need 2 factor!
[16:40] <smoser> :)
[16:48] <cjwatson> smoser: you can also use qastaging.launchpad.net, which uses production SSO
[16:50] <cjwatson> smoser: and you almost had it right - try https://bugs.launchpad.net/cloud-init/+filebug?field.tags=foo
[16:52] <smoser> cjwatson, thanks!
[21:31] <shadeslayer> hm, no one's gotten back to me about that 2fa reset
[21:31] <shadeslayer> It's been 2 weeks now
[22:13] <dobey> shadeslayer: i think you need #canonical-sysadmin for that
[22:13] <shadeslayer> dobey: ok, I'll poke my head in there :)


[04:11] <bildz> Has anyone been able to successfully deploy the neutron-gateway using 16.04?  I've tried using a global kernel parameter of "net.ifnames=0" in the MAAS global config, but i'm still failing at the same step during the autopilot deployment.
[07:54] <jamespage> bildz, which juju version and which maas version
[07:55] <jamespage> rc1 has some challenges with automatic bridging of unconfigured network interfaces
[07:59] <jamespage> marcoceppi, hey - can I request a point release of charmhelpers? I added a get_upstream_version helper to host a while back, which we're using in legacy charms that still sync
[07:59] <jamespage> but I need to have it for new reactive charms as well pls :-)
[09:20] <spaok> what does juju-info relation provide? I see you can use it for subordinate charms and get private addresses, but is that it?
[12:49] <stub> spaok: Its reason for existence is to support subordinate charms. You could probably stuff extra information on there, but you really should declare a real relation instead of abusing juju-info for that.
[14:50] <marcoceppi> jamespage: you got it
[14:52] <jamespage> marcoceppi, ta
[15:01] <holocron> i'm fooling about with juju and lxd again today.. following a reboot, i cannot get more than 10 containers to start up
[15:01] <bildz> jamespage: good morning
[15:01] <bildz> saw your response last night/morning
[15:02] <holocron> the 11th container start hangs with forkstart running
[15:02] <bildz> ii  conjure-up                         2.0.1~beta2-0~201609281246~ubuntu16.04.1 all          Package runtime for conjure-up spells
[15:02] <bildz> ii  juju-2.0                           2.0-rc2-0ubuntu1~16.04.1~juju1           amd64        Juju is devops distilled - client
[17:18] <nicbet> Quick question: Juju 1.25 appears to be able to target vSphere clouds, did that support disappear with 2.0 or not documented yet?
[17:19] <marcoceppi> nicbet: it still exists with 2.0
[17:20] <marcoceppi> nicbet: just seems to be suspiciously missing documentation
[17:20] <marcoceppi> larrymi_afk: could you share what you did to configure vSphere with juju 2.0? nicbet is asking
[17:20] <spaok> which the reactor charms, how do I trigger on a hook? I've tried a few different patterns I've seen in charms, but when running the charm it seems to always skip the hook
[17:21] <nicbet> marcoceppi: thanks! looking forward to larrymi_afk's pointers.
[17:26] <larrymi_afk> marcoceppi: nicbet: sure
[17:27] <larrymi_afk> nicbet: you will need an entry in your clouds definition pointing to your vcenter.
[17:27] <larrymi_afk> nicbet: like this
[17:27] <larrymi_afk>   vsphere:
[17:27] <larrymi_afk>     type: vsphere
[17:27] <larrymi_afk>     auth-types: [userpass]
[17:27] <larrymi_afk>     endpoint:
[17:27] <larrymi_afk>     regions:
[17:27] <larrymi_afk>       dc0: {}
[17:28] <larrymi_afk> nicbet: for endpoint, you'll specify the IP of your vCenter
[17:29] <larrymi_afk> nicbet: in the credentials, you'll use auth-type: userpass
[17:29] <larrymi_afk> then spedify password: and user: that you used to access the vCenter
[17:30] <nicbet> larrymi_afk: excellent, so it appears most of the 1.25 documentation transfers to 2.0, with the change to auth-type: userpass
[17:30] <larrymi_afk> nicbet: that's pretty much it .. when you bootstrap your controller, juju will ask you export an environment variable.. then once you export it, then everything is smooth sailing
[17:32] <larrymi_afk> nicbet: yes, not much is different.. it's been months since I used 1.25 so I don't recall exactly what I had in my environments.yaml and I think I passed a few arguments through the command line like the datacenter
[17:33] <larrymi_afk> other than that, things are relatively similar
[17:35] <larrymi_afk> nicbet: I didn't  have a regions definition either (just the datacenter that I passed on the command line).. but 1.25 may have changed to be more in line with 2.0 since..
[17:42] <nicbet> larrymi_afk: thanks, with the details you provided, I created the yaml file, bootstrapping the environment now...
[17:43] <larrymi_afk> nicbet: cool
[18:06] <nicbet> larrymi_ : no go. when bootstrapping the controller the provider brings the controller node online in vCenter, obtains IP address and then fails on SSH.
[18:07] <larrymi_> nicbet: what's the error?
[18:08] <nicbet> larrymi_: ERROR failed to bootstrap environment: waited for 10m0s without being able to connect: Permission denied (publickey).
[18:08] <larrymi_> nicbet: looks like maybe cloud-init failed
[18:09] <larrymi_> nicbet: trusty or xenial?
[18:10] <nicbet> larrymi_: xenial
[18:11] <Prabakaran> Hello Team, Not able to login using bzr launchpad-login "user"... getting error bzr: ERROR: Connection error: Couldn't resolve host 'launchpad.net' [Errno -3] Temporary failure in name resolution
[18:11] <Prabakaran> can you please advise me on this?
[18:12] <nicbet> larrymi_ : juju help bootstrap says: "Private clouds may need to specify their own custom image metadata, and
[18:12] <nicbet> possibly upload Juju tools to cloud storage if no outgoing Internet access is
[18:12] <nicbet> available. In this case, use the --metadata-source parameter to point
[18:12] <nicbet> bootstrap to a local directory from which to upload tools and/or image
[18:12] <nicbet> metadata."
[18:16] <larrymi_> nicbet: there was a cloud init issue in xenial that was fixed recently.. not sure if you're pulling an older image. Try with trusty to see whether you run  into this. btw, there's a DNS issue with Xenial that you could run into after deploying but shouldn't impact the bootstrap.
[18:16] <larrymi_> older image than the fix
[18:17] <nicbet> larrymi_ how do I specify which OVF image juju deploys?
[18:22] <larrymi_> nicbet: you could try to bootstrap by setting the image-stream.. for example, --config image-stream=daily
[18:23] <larrymi_> not sure about what other values are available for image-stream or if you can point to a url
[18:26] <spaok> how do I get the remote unit's ip info from a relation? when I try hookenv.relation_get('private-address', unit, relid) I get None
[18:36] <lutostag> generic question... looking at https://jujucharms.com/docs/1.25/storage, what is the definition of a pool and a volume? how do they relate?
[19:10] <nicbet> larrymi_ : https://bugs.launchpad.net/juju/+bug/1588041 is what I'm running into.
[19:10] <mup> Bug #1588041: [2.0 rc1] juju can't access vSphere VM deployed with Xenial,  cloud-init fails to set SSH keys <ci> <jujuqa> <landscape> <oil> <oil-2.0> <vsphere> <cloud-init:New> <juju:Fix Released> <https://launchpad.net/bugs/1588041>
[19:25] <larrymi_> nicbet: ah it should be fixed though. Have you tried daily?
[19:25] <nicbet> larrymi_: yes didn't work for me I'm now trying to figure out to get debug logs so I can inspect which image is being pulled
[19:27] <larrymi_> nicbet: if you use --debug, I think that should have the info for where it's getting it from
[19:28] <konobi> howdy... i seem to be having trouble using a 4k ssh key with juju... 2.0-rc2-elcapitan-amd64
[19:30] <konobi> is was reported fixed in https://bugs.launchpad.net/juju/+bug/1543283 but not seeing the same
[19:30] <mup> Bug #1543283: [Joyent] 4k ssh key can not be used: "cannot create credentials: An error occurred while parsing the key: asn1: structure error: length too large" <juju:Fix Released> <https://launchpad.net/bugs/1543283>
[19:31] <nicbet> larrymi_ : ova_import_manager.go:175 Downloading ova file from url: http://cloud-images.ubuntu.com/daily/server/xenial/20160930/xenial-server-cloudimg-amd64.ova which is the image with cloud-img fixed
[19:35] <larrymi_> nicbet: strange, I have a controller from yesterday that worked fine.. I'll redeploy to see.
[19:36] <larrymi_> nicbet: which version of vsphere?
[19:39] <nicbet> larrymi_ 6.0-20160104001
[19:47] <konobi> the bug is marked as "Fixed released", but i'm not seeing the fixed behaviour
[19:54] <larrymi_> nicbet: worked for me for http://cloud-images.ubuntu.com/releases/server/releases/xenial/release-20160922/ubuntu-16.04-server-cloudimg-amd64.ova which is build where the fix would have gone in... now trying daily
[19:55] <larrymi_> nicbet: which juju version are you using?
[20:01] <larrymi_> nicbet: worked with the 9/30 build too.
[20:21] <spaok> can can open-ports be gotten via hookend.relation_get?  I know privateaddress works, but I get None for open-ports
[20:22] <spaok> trying to make a subordinate charm that gets the ip and ports for a service
[20:57] <valeech> I have a general question about isntances of charms. If the software the charm is written around requires physical access to a device how do you deploy multiple instances and configure each instance to use the specific physical device per machine? For instance, ceph-osd. Each OSD will connect to a different “physical” drive. If I have 4 servers and the “physical” drives are not the same on all 4, how do I configure ceph-os
[20:57] <valeech> use the proper device on the corresponding machine?
[21:06] <rick_h_> valeech: so in this case there's a "leader" idea in an application to help coordinate among units and so using the leader hooks would help keep track of who's on which devices/etc.
[21:15] <valeech> rick_h: makes sense! I just read up on leadership hooks. ty!
[21:37] <nicbet> larrymi_ : version is juju 2.0-rc2-xenial-amd64
[21:41] <larrymi_> nicbet: it matches what I have
[21:42] <larrymi_> nicbet: try trusty to see if it's able to bootstrap completely
[21:43] <larrymi_> juju bootstrap --config default-series=trusty
[21:46] <nicbet> larrymi_ will try that next. every attempt takes quite a bit of time to push the ova images - it doesn't seem to cache the downloads on fail
[21:47] <larrymi_> nicbet: ok.. if you look at comment 18 then this is the bug where the fix went in.
[22:07] <nicbet> larrymi_ who's prividing the cloud-init metadata to the box? juju?
[22:14] <larrymi_> nicbet: idk
[22:22] <cholcombe> am i correct in guessing that reactive set_local requires that the value be json serializable?  I was caught by surprise when python error'd out
[22:42] <nicbet> larrymi_ : according to https://github.com/juju/juju/blob/master/provider/vsphere/ova_import_manager.go line 72 the cloud init params are given as part of the OvfImportSpec


[15:00] <Ursinha> OOPS-1307J16
[15:00] <Ursinha> thanks ubottu
[16:00]  * Ursinha looks at matsubara
[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] <sinzui> me
[16:00] <matsubara> Not on the Launchpad Dev team? Welcome! Come "me" with the rest of us!
[16:00] <gary_poster> me
[16:00] <Ursinha> me
[16:00] <danilos> me
[16:00] <matsubara> stub, cprov, herb, rockstar, intellectronica: hi
[16:00] <cprov> me
[16:01] <rockstar> ni!
[16:01] <mthaddon> me
[16:01] <intellectronica> me
[16:01] <matsubara> hi mthaddon
[16:01] <mthaddon> matsubara: herb won't be attending these meetings any more since he's no longer a LOSA
[16:02] <Ursinha> it's true
[16:02] <matsubara> mthaddon, indeed!
[16:02] <matsubara> let me update the page
[16:02] <Chex> hello!
[16:02] <mthaddon> matsubara: most likely Chex will be his replacement (given he's on the same timezone that herb was on)
[16:02] <Ursinha> hi Chex, welcome!
[16:02] <matsubara> mthaddon, all right thanks
[16:02] <matsubara> hi Chex, welcome
[16:02] <Chex> all: thank you
[16:03] <stub> moo
[16:03] <matsubara> ok, everyone is here
[16:03] <matsubara> [TOPIC] Agenda
[16:03] <MootBot> New Topic:  Agenda
[16:03] <intellectronica> hi Chex, welcome
[16:03] <matsubara>  * Actions from last meeting
[16:03] <matsubara>  * Oops report & Critical Bugs & Broken scripts
[16:03] <matsubara>  * Operations report (mthaddon/herb/spm)
[16:03] <matsubara>  * DBA report (stub)
[16:03] <matsubara> [TOPIC] * Actions from last meeting
[16:03] <Ursinha> matsubara, you'll may want to s/flacoste/gary_poster in that page
[16:03] <MootBot> New Topic:  * Actions from last meeting
[16:03] <matsubara> Ursinha, already done
[16:03] <Ursinha> matsubara, thanks
[16:03] <Andre_Gondim> me
[16:03] <matsubara>   * ursinha to chase mars about OOPS-1307J16 and file a bug about it
[16:03] <matsubara>   * matsubara to file a bug for OOPS-1315A253
[16:03] <matsubara>     * Filed https://launchpad.net/bugs/413706
[16:03] <matsubara>   * sinzui to file bugs for OOPS-1318S626, OOPS-1321EB223 and OOPS-1318EA4
[16:03] <matsubara>   * gary_poster to chase librarian-gc failure and report back to the list
[16:03] <matsubara>   * matsubara to ask stub to email the dba report to the list
[16:03] <matsubara>     * stub sent the dba report to the list
[16:04] <matsubara> hi Andre_Gondim, welcome
[16:04] <Andre_Gondim> thanks =]
[16:04] <matsubara> hi sinzui, did you file those bugs?
[16:04] <matsubara> Ursinha, no news about that oops? shall I remove the action item?
[16:05] <Ursinha> matsubara, do that, I'll file a bug if that happens again
[16:05] <matsubara> Ursinha, thanks
[16:05]  * sinzui has no screen
[16:05] <matsubara> re: the librarian-gc failure, it was disabled that week, that's why we had a script failure email to the list
[16:06] <gary_poster> stub is working on that as his next task
[16:06] <mthaddon> I think there's a CP pending approval for that
[16:06] <sinzui> matsubara: I did file bugs
[16:06] <matsubara> gary_poster, mthaddon: cool. thanks
[16:06] <stub> The next bit of work on the librarian may be related - depends on what happens with the cherry pick and test run ;)
[16:06] <Ursinha> gary_poster, this is bug 410576, right?
[16:06] <sinzui> OOPS-1315A253 is soyuz
[16:07] <matsubara> sinzui, thanks. if you have them handy, could you priv msg them to me?
[16:07] <sinzui> bug 413174
[16:07] <gary_poster> Ursinha, that's not my understanding.  hm, that's a dupe.
[16:08] <Ursinha> gary_poster, a dupe? is there another?
[16:08] <Ursinha> this one is set as Critical... I'll talk about it in the next section :)
[16:09] <sinzui> matsubara: OOPS-1318EA4 is new. It relates to another bug that I intend to fix in 3.0 I will file and assign it
[16:09] <matsubara> thanks sinzui
[16:09] <gary_poster> Ursinha: either dupe or related: bug 413749
[16:10] <Ursinha> gary_poster, let me see
[16:10] <Ursinha> matsubara, you can move to the next section and we keep discussing there
[16:10] <matsubara> ok, thanks Ursinha and gar0t0
[16:10] <matsubara> err
[16:10] <matsubara> gary_poster,
[16:10] <gary_poster> :-)
[16:10] <matsubara> [TOPIC] * Oops report & Critical Bugs & Broken scripts
[16:10] <MootBot> New Topic:  * Oops report & Critical Bugs & Broken scripts
[16:10] <matsubara> there you go Ursinha
[16:10] <Ursinha> okay
[16:11] <Ursinha> +branches timeout has a fix already committed, and also that horrible 'specications' bug is fix committed as well
[16:11] <Ursinha> so, two issues to ask: foundations and registry
[16:11] <Ursinha> sinzui, I can see a lot of these ExpatErrors, that are bug 403606, does barry said something about fixing that?
[16:11] <Ursinha> gary_poster, bug 410576 is Critical but I see there's no activity for almost a week now, is that really critical?
[16:11] <Ursinha> (in this meantime, I'll check bug 413749
[16:11] <Ursinha> )
[16:12] <gary_poster> Ursinha: I believe it is high: afaik, the criticality is what mthaddon describes in his comments to that issue.  This is what stub is going to next.
[16:12] <sinzui> Ursinha: barry has not provided any insight into the issue yet. I cannot estimate it
[16:12] <stub> Its critical because it is part of the impending librarian collapse.
[16:13] <sinzui> matsubara: bug #41648
[16:13] <mthaddon> gary_poster: it's critical - LP will blow up in 20 days or so if it's not fixed (as the librarian will run out of space)
[16:13] <matsubara> sinzui, hmm that doesn't look like a lp bug
[16:13] <sinzui> matsubara: bug #416483
[16:13] <matsubara> cool. thanks sinzui!
[16:13] <sinzui> ^ points the the related bug too
[16:13] <gary_poster> mthaddon, stub: (procedural, apologies) what does critical mean then?  I thought it meant drop everything, while afaict this is a do it within 10 days?
[16:14] <Ursinha> gary_poster, mthaddon, we have two bugs here, bug 410576 and bug 413749
[16:14] <Ursinha> gary_poster, that's my question as well
[16:14] <mthaddon> gary_poster: I think if we know it's going to blow up all of LP in a short period of time, that's critical
[16:14] <gary_poster> afaik 413749 is the (a?) symptom of 410576.  stub, mthaddon, can you please correct me?
[16:15] <stub> gary_poster: It is my top priority, as we need to know the genuine rate of disk consuption for the librarian so we can accurately predict when new disk has to be purchased and installed by, or soyuz has to decrease their consumption by
[16:15] <gary_poster> stub thank you
[16:15] <mthaddon> gary_poster: it's related, but fixing the librarian-gc will buy us more time, not fix it forever
[16:15] <gary_poster> ok, gotcha
[16:16] <gary_poster> So Ursinha, it is critical, and we should be moving to in progress, at least, within a day or so.
[16:16] <Ursinha> great gary_poster, thanks a lot
[16:17] <matsubara> Ursinha, anything else re: oops and critical bugs?
[16:17] <Ursinha> sinzui, could you poke barry again about that bug? I can do that as well if you want :)
[16:17] <sinzui> I will
[16:17] <Ursinha> thanks a lot sinzui
[16:17] <cprov> stub: we have to adjust the removal of BPRs to be more aggressive.
[16:17] <danilos> cprov: can you (i.e. Soyuz team) provide data flacoste asked for in https://bugs.edge.launchpad.net/launchpad-foundations/+bug/413749 so we've got raw numbers there as well?
[16:18] <mthaddon> cprov: any idea of how much space that would buy us?
[16:18] <cprov> danilos: sure, I can try.
[16:18] <stub> cprov: Bug 413749 has a soyuz task, so you may want to triage it.
[16:18] <matsubara> garbo-hourly failed on the 17th even after spm adjusted the check to 12 hours. stub do you know what's up?
[16:19] <stub> matsubara: I wasn't aware of that.
[16:20] <cprov> mthaddon: can't tell exactly, but I issue the queries for estimating few other scenarios than 1 month quarantine for BPR files
[16:20] <mthaddon> ok
[16:21] <matsubara> there's a "Scripts failed to run: loganberry:garbo-hourly" email sent to the list on the 17th. could you investigate and reply to that email?
[16:21] <matsubara> stub, ^
[16:21] <Ursinha> cprov, can you follow up later on that bug then, please?
[16:21] <cprov> Ursinha: sure
[16:21] <Ursinha> thanks cprov
[16:22] <matsubara> [action] cprov to follow up on bug 413749
[16:22] <MootBot> ACTION received:  cprov to follow up on bug 413749
[16:22] <matsubara> [action] stub to investigate garbo-hourly failure after spm adjusted script checking to 12h
[16:22] <MootBot> ACTION received:  stub to investigate garbo-hourly failure after spm adjusted script checking to 12h
[16:24] <matsubara> [action] sinzui to poke barry about ExpatError OOPSes (bug 403606)
[16:24] <MootBot> ACTION received:  sinzui to poke barry about ExpatError OOPSes (bug 403606)
[16:24] <sinzui> done
[16:24]  * sinzui eagerly awaits an assessment
[16:25] <matsubara> cool
[16:25] <matsubara> I think that's all for this section
[16:25] <matsubara> thanks everyone
[16:25] <Ursinha> thanks a bunch sinzui
[16:25] <Ursinha> and everyone else :)
[16:25] <Ursinha> do ahead matsubara
[16:25] <Ursinha> *go
[16:25] <matsubara> [TOPIC] * Operations report (mthaddon/Chex/spm)
[16:25] <MootBot> New Topic:  * Operations report (mthaddon/Chex/spm)
[16:25] <danilos> mbarnett for the agenda as well? :)
[16:26] <mthaddon> :)
[16:26] <Chex> - Buildbot now hosted from the DC
[16:26] <Chex>  - Multiple Cherry Picks this past week
[16:26] <Chex>  - Will be beginning to implement recommendations from SplitIt Sprint before too long
[16:26] <Chex>  - Codebrowse needed restarting more than usual this week (see IncidentLog)
[16:26] <Chex>  - Incident with edge rollout breaking as one app server refused to stop, and interaction with the session DB being trashed - see Incident Report and most likely discussed earlier in the meeting
[16:26] <Chex>  - LOSA sprint this week to get new LOSAs (Chex, mbarnett) up to speed
[16:26] <matsubara> danilos, good catch. thanks
[16:26] <Chex> and thats it for us, unless there are any questions??
[16:27] <gary_poster> yay buildbot in DC! :-)
[16:28] <danilos> yeah, great stuff, looking forward to everything else that enables :)
[16:28] <danilos> (like the production branch in buildbot *grin*)
[16:28] <matsubara> thanks Chex
[16:28] <matsubara> [TOPIC] * DBA report (stub)
[16:28] <MootBot> New Topic:  * DBA report (stub)
[16:29] <stub> Our disk usage is going steadily up. Nothing alarming yet, but it did prompt me to turn on the long-running-transaction killer. Non-system transactions running over 3 hours will now be killed. This should alleviate database bloat, which adversely affects everything. It will also stop processes that block on long running transactions from blocking too long (like the garbo).
[16:29] <stub> I've bumped up the default statistics target to 250. We have twice over the last several months had a query chewing up huge amounts of disk space in temporary tables, and my best guess as to why is bad query plans. The higher statistics target should make this less likely.
[16:29] <stub> Done.
[16:29]  * Ursinha misses the oot thing
[16:29] <Ursinha> questions for stub?
[16:30] <danilos> stub: ok, so that means that fixing langpack exporter is now critical for us, right?
[16:31] <stub> danilos: I can turn it off if necessary. I'm not sure what effect is has on the langpack export.
[16:31] <stub> Will all of them be affected?
[16:31] <stub> oot
[16:31] <danilos> stub: most of the runs will
[16:31] <Ursinha> hehe
[16:32] <danilos> stub: I've made it critical for us, it should be a simple fix, it'll only require cherrypicking
[16:32] <stub> danilos: ok. I'd like that issue raised to high or critical. I'll turn the check to 8 hours which will cover the current longest transaction I'm seeing in the graphs.
[16:32] <stub> k
[16:32] <danilos> stub: it was high and scheduled for 3.0, now it's scheduled for asap :)
[16:32] <stub> Please add a note to the CP request that the limit needs to be put back.
[16:32] <danilos> stub: sure, thanks
[16:33] <Ursinha> thanks stub
[16:33] <Ursinha> and danilos
[16:33] <matsubara> thanks stub and danilos
[16:34] <stub> danilos: Bug number?
[16:34] <danilos> stub: bug 411697
[16:34] <matsubara> * In-team handling of OOPSes (Danilo)
[16:34] <danilos> ok, a long paste follows
[16:34]  * matsubara hands the mic to danilos
[16:35] <danilos> Breaking news from the team leads call!  Read all about it!
[16:35] <danilos> Many of the duties Diogo and Ursula had you spoiled with (like trawling OOPS summaries and error logs and matching/filing relevant bugs) is what QA contacts in each team should do (generally, it was considered that this is what they should have been doing anyway).
[16:35] <danilos> According to Gary, Diogo is happy to continue maintaining oops-tools (and relevant infrastructure, which will stay in Foundations turf), but everybody else is invited to contribute and take interest in the tools if they want something added.
[16:35] <danilos> Similarly, if someone finds it hard to go through numerous places to see all the possible problems (i.e. going through several OOPS summaries, error-reports list, etc), they are welcome to improve our infrastructure for aggregating these.
[16:35] <danilos> I am personally hoping that once we pick a release manager for 3.0, (s)he'll take care that all QA contacts are on top of their game. Perhaps we can have Ursula and Diogo continue as is until RM for 3.0 is appointed.
[16:35] <danilos> Any suggestions on what should change in the format of the meeting to make sure this is not a regression compared to what we do today?
[16:36] <gary_poster> (eh, that summary came out in such a way that I feel I should have talked with matsubara first.  sorry, matsubara, and feel free to correct the summary about your personal position)
[16:37] <matsubara> gary_poster, it's correct :-)
[16:37] <danilos> gary_poster: (I was just being careful not to put words in matsubara's mouth, I should have talked to him first, but there just wasn't the time between the teamleads call and this meeting :)
[16:37] <gary_poster> cool :-)
[16:38] <danilos> anyway, how should the meetings be run from now on? matsubara, you want to keep running them?
[16:38] <gary_poster> +1 if you are willing matsubara
[16:38] <matsubara> danilos, yes, I talked to francis about it and Ursinha and I will still run the production meeting
[16:38] <cprov> +1
[16:38] <danilos> anybody else has any comments? everybody, this means more work for you and less for matsubara, Ursinha :)
[16:39] <Ursinha> +1 from me
[16:39] <stub> How to teams claim an oops? The benefit of a central monitor and this meeting is when teams disagree on who the problem belongs too.
[16:39] <matsubara> but it'd be nice to have help from the QA contacts doing the daily oops analysis and help with triage
[16:39] <danilos> stub: that's for the release manager to worry about IMO, but in general, we should be having bug attached to all the OOPSes
[16:40] <stub> Who creates the bugs?
[16:40] <Ursinha> danilos, that's the idea
[16:40] <Ursinha> stub, it depends
[16:40] <Ursinha> stub, for instance, afaik, translations has been creating its own bugs for some time now
[16:40] <Ursinha> checking the summaries daily
[16:40] <danilos> stub: in general, we might be able to improve tools to split summaries by vhost initially
[16:40] <stub> I'm just wondering how we avoid them being dropped on the floor because, say, translations thinks an oops is a foundations issue and vice versa.
[16:40] <Ursinha> danilos, matsubara has the idea of using page ids
[16:40] <Ursinha> for splitting
[16:41] <Ursinha> *had
[16:41] <danilos> Ursinha: right, that might be a good one as well
[16:41] <stub> splitting the reports into areas of responsibility would address my concern I think.
[16:41] <danilos> Ursinha: actually, it's perfect
[16:41] <cprov> okay, running the risk to sound like an idiot,  who are the current QA contacts ? TLs ?
[16:41] <Ursinha> cprov, the people that attend this meeting
[16:41] <stub> TLs until they delegate ;)
[16:41] <matsubara> cprov, everyone who attend this meeting weekly
[16:41] <danilos> cprov: it means it's you! :)
[16:42] <matsubara> cprov, actually it's bigjools, but he's away today
[16:42] <cprov> fantastic! thanks.
[16:42] <Ursinha> danilos, :P, bigjools actually
[16:42] <danilos> heh, ok... in general, I think this is best done by a team lead
[16:42] <danilos> (and soon enough, I'll be replacing henninge as the translations QA contact)
[16:42] <Ursinha> danilos, it was TL's call when they pointed the QA contacts
[16:43] <danilos> Ursinha: I know
[16:43] <gary_poster> hm.  question.  if we *all* trawl oops, is that a collective time loss?
[16:43] <Ursinha> but that can be changed for this new experiment
[16:43] <Ursinha> gary_poster, if we separate per teams, not that much
[16:43] <Ursinha> I believe
[16:43] <danilos> so, matsubara, can we have an action for me to discuss with Ursinha and you how we can split OOPS reports into per-team summaries?
[16:43] <Ursinha> per "teams"
[16:43] <gary_poster> oh I see
[16:43] <danilos> gary_poster: right, see above
[16:43] <gary_poster> ok thanks
[16:44] <matsubara> [action] danilos, Ursinha and matsubara to discuss oops summaries split per team
[16:44] <MootBot> ACTION received:  danilos, Ursinha and matsubara to discuss oops summaries split per team
[16:44] <danilos> matsubara: thanks
[16:44] <Ursinha> gary_poster, we in fact have a new feature on oops-tools that associate a bug to a exception type (matsubara correct me if I'm wrong here)
[16:44] <Ursinha> this helps a lot
[16:44] <danilos> ubottu: thanks for nothing (just so you don't get used to praise only)
[16:45] <Ursinha> sometimes you freak me out ubottu
[16:45] <Ursinha> anyway
[16:45] <Ursinha> :)
[16:45] <danilos> anyway, that's all settled afaiac
[16:45] <matsubara> gary_poster, Ursinha: now we have a feature on oops-tools that once an oops is linked to a bug, subsequent oopses of that same type are already linked to the bug report
[16:45] <Ursinha> gary_poster, if you click the oops, most of them have a bug associated, on top left
[16:45] <danilos> we'll be reporting back, everything stays as is until we've got better oops reports, but do expect changes soon
[16:45] <matsubara> makes analysis much easier
[16:45] <Ursinha> bug report?
[16:45] <matsubara> next step is to add that info to the summary
[16:46] <gary_poster> heh.  ah I see cool
[16:46] <gary_poster> thanks Ursinha, matsubara
[16:46] <matsubara> all right. thanks danilos for bringing this up
[16:46] <Ursinha> ah, I got that
[16:46] <matsubara> and thanks everyone
[16:46] <Ursinha> thanks everyone
[16:46] <matsubara> Thank you all for attending this week's Launchpad Production Meeting. See https://dev.launchpad.net/MeetingAgenda for the logs.
[16:46] <matsubara> #endmeeting
[16:46] <MootBot> Meeting finished at 10:46.
[16:47] <matsubara> 1 min late. sorry about that
[16:47] <gary_poster> :-) thanks matsubara
[16:47] <Ursinha> thanks matsubara and everyone!
[16:47] <gary_poster> thanks Ursinha :-)


[08:41] <icey> morning
[10:27] <rmg51> Morning
[12:23] <JonathanD> Morning.
[13:18] <teddy-dbear> Morning peoples, critters and everything else


[02:41] <lotuspsychje> good morning
[03:16] <lotuspsychje> start a topic here plujon
[03:17] <plujon> I just asked in #ubuntu: Why is chromium a snap in the first place?
[03:17] <lotuspsychje> evolution chosen for devs liking the snap way
[03:18] <lotuspsychje> a LOT of snaps are coming our way
[03:19] <plujon> If a lot of snaps come our way, won't that require a lot more physical memory?
[03:20] <lotuspsychje> plujon: the start of chromium snap had some rough ways, but it actually improved a lot on 20.04 now
[03:20] <lotuspsychje> rocketfast on my side, cant say it lags my system memory-wise
[03:21] <plujon> I'm using 20.04, first time using chromium as a snap, and it is broken in a few ways for me.  That's why I started asking.  I'm considering leaving ubuntu over it.
[03:21] <lotuspsychje> broken how
[03:22] <plujon> Broken like I can no longer sign extensions.  Broken like native messaging no longer works.
[03:22] <lotuspsychje> plujon: did you browse the latest bugs on chromium?
[03:23] <plujon> bugs on chromium?  Do you mean ubuntu bugs?
[03:24] <lotuspsychje> plujon: if you use ubuntu, yeah chromium bugs are ubuntu related
[03:24] <plujon> The only ubuntu/chromium/snap bug I looked at indicated there was no resolution planned for the breakage; just a number of people complaining about it.  It was reported quite a long time ago.
[03:24] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap&orderby=importance&start=0
[03:24] <lotuspsychje> check if you affect relevant bugs for your cases before complaining please
[03:25] <plujon> Check if I affect relevant bugs?
[03:25] <lotuspsychje> plujon: yes, you just said you have 'broken' issues on chromium
[03:26] <plujon> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074 is one of the breakages
[03:26] <lotuspsychje> plujon: ok, then help the community, and 'affect' to the bug in the left upper corner
[03:27] <lotuspsychje> as part of the community you can influence/help
[03:44] <plujon> How is a snap different from or better than static linking?
[03:45] <plujon> Well, obviously, it is different in a number of technical ways, but big picture, why not just statically link most of the problematic dependencies?
[03:53] <lotuspsychje> plujon: you would have to discuss with some devs about that
[04:13] <plujon> Apparently brave-browser, OTOH, is not a snap.  I guess I'll be using that.
[04:15] <lotuspsychje> brave was a snap before, but they seemed to remove it
[07:22] <lordievader> Good morning


[10:04] <zaki> hi Kilos
[12:19] <pavlushka> Hello every one!
[12:19] <pavlushka> Good afternoon Kilos !
[12:19] <pavlushka> AudaciousTUX: কি অবস্থা?
[12:20] <AudaciousTUX> vala na :'(
[12:21] <pavlushka> কেন?
[12:21] <AudaciousTUX> khai dai ghumai :'(
[12:22] <pavlushka> এর চেয়ে ভাল আর কি চাও?
[12:23] <AudaciousTUX> :3
[12:23] <pavlushka> AudaciousTUX: have you encountered ovronil here, recently?
[12:25] <pavlushka> QA tell avroniil that we would love to have him here, and missed him by a tiny little second :)
[12:25] <QA> pavlushka: I don't know who avroniil is. Say 'avroniil on freenode' and I'll take your word that avroniil exists
[12:25] <pavlushka> QA tell ovroniil that we would love to have him here, and missed him by a tiny little second :)
[12:25] <QA> pavlushka: Sure, I'll tell Ovroniil on freenode
[12:28] <pavlushka> AudaciousTUX: I am fasting the Nafals, condition is good, :3
[12:32] <AudaciousTUX> nope :(
[13:10] <Kilos> hi guys, ill be here jusdt now . just got back from town and still chores to do
[16:50] <pavlushka> Hello kam!
[16:50] <pavlushka> Hello kamrul !
[16:53] <Kilos> hi pavlushka and others
[16:53] <pavlushka> Hello Kilos !
[16:55] <Kilos> if we make things exciting for him ash will find the time to be here
[17:04] <pavlushka> Kilos: I think the issue is time for him, :|
[17:05] <Kilos> thats why i said if he finds something exciting he will make time
[17:05] <Kilos> it must be some idea hanging in the back of your head all the time
[17:06] <Kilos> flame wars normally attract people
[17:18] <pavlushka> ha ha
[17:18] <Kilos> oh pavlushka
[17:18] <pavlushka> what?
[17:19] <Kilos> remember that other guy from th foss stuff that was here
[17:19] <Kilos> he can come back
[17:24] <pavlushka> toshazed?
[17:24] <Kilos> no that one that rj fights with
[17:25] <pavlushka> yes, that's him
[17:25] <pavlushka> lol
[17:25] <Kilos> oh yes then him
[17:25] <Kilos> i have you so i dont have to remember everything
[17:26] <kamrul> hi
[17:26] <pavlushka> hi
[17:26] <Kilos> hi kamrul
[17:26] <kamrul> how r u all?
[17:26] <Kilos> ok ty and you
[17:26] <pavlushka> Kilos: i am laughing on other facts on him :p
[17:27] <Kilos> why havent you told me
[17:27] <kamrul> ha ha
[17:27] <kamrul> i have a problem can you solve it?
[17:28] <Kilos> tell us what the problem is
[17:28] <Kilos> if its money dont bother
[17:29] <kamrul> no...i have wifi problem..it always automatic disconnect
[17:29]  * pavlushka rofls
[17:30] <Kilos> pavlushka fix his wifi
[17:30] <pavlushka> kamrul: give us a "lspci -nnk" in paste.ubuntu.com
[17:30] <pavlushka> kamrul: and then post the link here.
[17:31] <Kilos> have you used lshw pavlushka
[17:31] <kamrul> i don't understand what is ispci -nnk?
[17:31] <Kilos> lspci
[17:31] <Kilos> ls is list
[17:32] <Kilos> you do it in terminal
[17:32] <kamrul> ok
[17:32] <Kilos> the command will list what is in your pc
[17:32] <kamrul> understood
[17:33] <pavlushka> my bad kamrul , i thought you are zaki's sys admin friend, :)
[17:34] <kamrul> yah..zaki is my roommate..but zaki is busy now so
[17:34] <pavlushka> no problem, just paste that result in paste.ubuntu.com and give us the link.
[17:38] <kamrul> http://paste.ubuntu.com/21539259/
[17:42] <pavlushka> kamrul: not this, but result of "lspci -nnk" command from terminal.
[17:43] <pavlushka> Kilos: yes i have checked lshw
[17:44] <pavlushka> kamrul: but dont use the "" inverted commas
[17:45] <kamrul> ok
[17:46] <Kilos> those inverted commas messed me around for a long time
[17:46] <kamrul> http://paste.ubuntu.com/21540145/
[17:47] <kamrul> sorry
[17:47] <pavlushka> kamrul: why?
[17:47] <kamrul> for ""
[18:02] <RemonShai> QA coffee please
[18:02] <QA> RemonShai: There isn't a pot on
[18:03] <RemonShai> pavlushka, hi....
[18:03] <Kilos> hi RemonShai
[18:03] <Kilos> QA coffee on
[18:03]  * QA starts grinding coffee
[18:04] <pavlushka> kamrul: try to follow this, https://github.com/lwfinger/rtlwifi_new/pull/74/commits/8c5ab142e254a709df397d5d3121acc2d783d2d2
[18:04] <RemonShai> hi Kilos how're u?
[18:04] <Kilos> ok ty RemonShai and you?
[18:04] <pavlushka> kamrul: and if you encounter any issue in the steps, tell us here, :)
[18:04] <pavlushka> Hello RemonShai !
[18:04] <RemonShai> Kilos, me too...
[18:05] <RemonShai> pavlushka, তারপর .... ভাল আছেন???
[18:07] <QA> Coffee's ready for Kilos!
[18:07] <Kilos> QA ty
[18:07] <QA> Only a pleasure Kilos
[18:08] <RemonShai> QA, coffee on
[18:08]  * QA starts grinding coffee
[18:08] <pavlushka> RemonShai: জি ভাল, আপনি?
[18:12] <QA> Coffee's ready for RemonShai!
[18:12] <RemonShai> pavlushka, fine but Flood water is rising . I'm worried my pond full of fish .
[18:15] <pavlushka> RemonShai: fence it by fishnets then, like I did. :p
[18:16] <Kilos> do you guys eat the fish, or just for show
[18:17] <pavlushka> lol
[18:17] <Kilos> as in, are they basic carp or the koi variety
[18:18] <pavlushka> my ones are carp, not sure of RemonShai's
[18:18] <Kilos> wild carp , same as im big dams and lakes etc?
[18:19] <RemonShai> Yet one meter of water will rise , if the pond sink . But the problem is the shower . This gets the chance to break the bank .
[18:19] <Kilos> koi are the fancy ones
[18:20] <RemonShai> pavlushka, me too
[18:20] <zaki> hello everyone :)
[18:20] <Kilos> hi zaki
[18:21] <zaki> Kilos: how are you? and pavlushka
[18:21] <zaki> RemonShai: you too
[18:21] <Kilos> ok ty and you?
[18:22] <RemonShai> fine... zaki
[18:22] <RemonShai> ty zaki
[18:22] <zaki> i'm little busy, but fine. :)
[18:23] <RemonShai> by the way.... here, anyone use texmaker???
[18:23] <zaki> Kilos: ddg texmaker
[18:23] <zaki> sorry
[18:24] <zaki> kewpie: ddg texmaker
[18:24] <kewpie> zaki: "Official site" http://www.xm1math.net/texmaker/ :: Free TeX editors :: Linux TeX software
[18:25] <Kilos> lol
[18:25] <RemonShai> i know that site... but i face a problem... & there site, I cann't understand solution.
[18:28] <zaki> i never use it.
[18:30] <RemonShai> zaki, quora math solve the thing of my attention on.
[18:31] <zaki> oh
[18:33] <RemonShai> zaki, to use normal text editor(libre math)it takes a huge time to type math. but Texmaker/TeX is cool...
[18:35] <zaki> wow
[18:36] <kamrul> Kilos, thanks..
[18:37] <Kilos> for what kamrul
[18:38] <kamrul> for helping me
[18:38] <Kilos> it was pavlad
[18:39] <Kilos> when i can help i do, but when its too difficult for me i try find someone else to help out
[18:39] <Kilos> and pavlushka is getting very good at helping
[18:40] <kamrul> yeah,that's sure
[18:42] <Kilos> hahaha
[18:43] <Kilos> you see remonshai message
[18:56] <zaki> lol
[18:56] <zaki> boooom booom
[19:03] <Kilos> sleep tight banga peeps
[19:09] <zaki> good night.
[19:15] <pavlushka> Sorry kamrul, power cuts
[19:21] <pavlushka> So kamrul , does that work?
[19:25] <Guest37817> AudaciousTUX, এতো রাইতে কী করো?
[19:31] <pavlushka> Hello AudaciousTUX !
[19:32] <pavlushka> AudaciousTUX: কি ঘুমাইতে আইসো?
[19:32] <pavlushka> Hello Guest37817 | Rezwan!
[19:32] <AudaciousTUX> ho :v
[19:32] <AudaciousTUX> areh shondhar por ghum dichi
[21:29] <pavlushka> AudaciousTUX: কি কর?
[21:58] <AudaciousTUX> mahbubul hasan er boita pori
[21:58] <AudaciousTUX> apni ratre jaiga ki koren?? :/
[22:49] <pavlushka> AudaciousTUX: নফল রোজা , সেজন্য একি routine applied, :p
[22:50] <AudaciousTUX> uh
[23:15] <pavlushka> See ya guys! bye :)
[23:15] <AudaciousTUX> ব্যে
[23:15] <AudaciousTUX> bye
[23:15] <pavlushka> lol


[13:29] <bittin> Igor will talk Ubuntu and Canonical on Linux App Summit now in 1 minute
[13:31] <bittin> and hellsworth