[00:00]  * guiverc smiles, you're not alone with names... I typed Bill automatically; but still opened the wiki page to ensure my typed name was correct
[00:05] <KGIII> Also, seeing as you're from Oz, I'll make sure to get some pics for you when the winter gets interesting. I generally get about 3.5 meters of snow, at a minimum, each season. It's beautiful.
[00:07] -lugito:#lubuntu-devel- [T177: creation of irc channels and website update with new channels.] Noumeno (Roberto) commented on the task: https://phab.lubuntu.me/T177#3942
[00:23] <kc2bez> okie dokie. https://lubuntu.me/links has been updated. I added the manual and the LXQt wiki too as well as shuffled everything around.
[00:28] <KGIII> I clicked your link and Pidgin crashed. I'm sure it's just coincidental.
[00:30] <kc2bez> I think so. It works here in Quassel :P
[00:30]  * guiverc was looking for a pidgin link, didn't find one :)
[00:30] <kc2bez> :D
[00:35] <KGIII> It had been open for quite a while. So, maybe that's why.
[01:13] -lugito:#lubuntu-devel- [T180: Cleanup Ubuntu Wiki] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T180#3943
[06:23] -lugito:#lubuntu-devel- [Lubuntu CI] merger_calamares FAILURE: https://ci.lubuntu.me/job/merger_calamares/699/
[06:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm FAILURE: https://ci.lubuntu.me/job/groovy_stable_sddm/315/
[06:44] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm FAILURE: https://ci.lubuntu.me/job/focal_stable_sddm/559/
[06:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm FAILURE: https://ci.lubuntu.me/job/groovy_stable_sddm/315/
[06:44] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm FAILURE: https://ci.lubuntu.me/job/hirsute_stable_sddm/64/
[06:44] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm FAILURE: https://ci.lubuntu.me/job/focal_stable_sddm/559/
[06:44] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm FAILURE: https://ci.lubuntu.me/job/hirsute_stable_sddm/64/
[06:45] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libqtxdg just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_libqtxdg/47/
[20:22] <The_LoudSpeaker> where do I get the source of git source of golang-github-zyedidia-tcell. I did a apt source on a hippo container and it gave me the source but I can't go back to a previous commit on it. it isn't a git repo.
[20:25] <wxl> right you need to check the package details
[20:25] <wxl> (to get the website)
[20:26] <The_LoudSpeaker> https://code.launchpad.net/ubuntu/+source/golang-github-zyedidia-tcell this is emply.
[20:26] <wxl> not surprisingly
[20:26] <wxl> what homepage is listed in the control file?
[20:27] <The_LoudSpeaker> I actually want to test  if 1.4.8 version builds in a focal machine. But the souce I have is for latest version.
[20:27] <The_LoudSpeaker> https://github.com/zyedidia/tcell
[20:27] <The_LoudSpeaker> is the homepage
[20:27] <wxl> ok so you should be able to go there and grab the binary
[20:28] <wxl> you'll need to apply any patches so essentially it's like you need to repackage it for focal
[20:28] <The_LoudSpeaker> yeah. That's what I am trying to avoid. is there something like phab for this package in ubuntu side?
[20:29] <wxl> nope
[20:29] <The_LoudSpeaker> I can also clone from salsa and modify the debian folder that too works but wanted something in ubuntu side.
[20:29] <wxl> mod'ing salsa might be an easier way to go
[20:29] <The_LoudSpeaker> so salsa clone + patched debian/ should do it then?
[20:29] <wxl> in any case there's no quick and easy
[20:29] <The_LoudSpeaker> :(
[20:29] <wxl> assuming you end up with something that's appropriate for ubuntu
[20:30]  * The_LoudSpeaker is wondering what I signed up for.
[20:30] <wxl> i mean you might be able to take the new ubuntu package and just change everything to focal
[20:30] <wxl> why DID you sign up for this?
[20:30] <The_LoudSpeaker> I can use a merge tool which will help in getting the correct patched debian folder
[20:31] <The_LoudSpeaker> I signed up coz I wanted to do a SRU and utkarsh happened to ask me if I can SRU this one. seems small enough so I agreed.
[20:31] <The_LoudSpeaker> utkarsh maintains this on salsa.
[20:32]  * The_LoudSpeaker goes to install smerge on his containers.
[20:33] <The_LoudSpeaker> Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
[20:33] <The_LoudSpeaker> wow.
[20:33] <The_LoudSpeaker> hippo just threw this at me
[20:33] <The_LoudSpeaker> gg.
 that has been discussed in other mechanisms for some time :P
[20:34] <The_LoudSpeaker> oh you are here too.
[20:35] <The_LoudSpeaker> you asked na if I had tried building it in focal
[20:35] <The_LoudSpeaker> it=golang-github-zyedidia-tcell
[20:35] <The_LoudSpeaker> that's what I am doing rn
 ... of course i'm around
 i don't always talk xD
 wxl knows this well :P
 wxl: they want something that depends on that SRU'd but it needs a new version too :P
 so :P
 because dependencies :P
 welcome to Dep Testing Hell
[20:36] <The_LoudSpeaker> It would be a lot easier to just use the latest version of this dependency instead of 1.4.8 but that will mean adding one more new package to focal : golang-github-xo-terminfo-dev
[20:37] <The_LoudSpeaker> so.
[20:37] <The_LoudSpeaker> using 1.4.8 of this and teh version of micro in groovy is the best way imo.
[20:37] <The_LoudSpeaker> instead of going for versions which are in hippo.
 ah! good ol meld. :) :
 very underrated.
[20:39] <The_LoudSpeaker> side quest: tsimonq2 the image didn't make it into irc. lugito broke ?
 new system
 matterbridge
 TeleIRC is dead
 Still we should come up with something for images https://github.com/42wim/matterbridge/wiki/Mediaserver-setup-%28advanced%29
 i am reading that now
 i'm going toi see if I can make Caddy do S3 too but we'll see.
 may have to spin a new URL for the data though but it might take a day or more, today's one of the "I Have Stuff To Do" days
[20:48] <wxl> might be a way to make imgur or something work
 yeah well i'm looking.  I don't see a mechanism for Caddy to use, but I think Caddy can do stuff like that
 Caddy is pretty lacking as far as customization from what I know.
 yeah well
 It ain't your dad's nginx or your granddad's apache.
 they don't give any other alternatives :P
 other than run it on our own infra
 which... isn't hard.
 I hear you
 i can easily spin an NGINX instance to serve the content since it sits on the core infra the DNS already points there.  Just gotta make sure things're passed right.
 @kc2bez  or any dev who tracks releases - do you have a doc/template that documents finalized release details/updates/bug fixes? Curious about leveraging template for customers
 I know blogs are one place , but anthing else internally?
 (that might include ticket#etc)
 @profetik777 we follow this https://phab.lubuntu.me/source/new-release/
 Some of what we do is pre-release and some is post-release
 Obviously that is pretty specific to our use.
 yeah, appreciate it though
[21:43] <The_LoudSpeaker> is debhelper-compat 13 going to be in focal anytime soon?
[21:44] <The_LoudSpeaker> Also, @teward golang-github-zyedidia-tcell v 1.4.8 builds fine in focal.
[21:44] <The_LoudSpeaker> only with the exception of debhelper-compat
[21:44] <The_LoudSpeaker> cc: wxl
[21:46] <The_LoudSpeaker> https://paste.ubuntu.com/p/9FSFNPc4TM/
[21:47] <The_LoudSpeaker> SO yes I think we can safely bump this to 1.4.8-2(3) in focal and then SRU micro to 2.0.6-2 in focal.
[21:48] <The_LoudSpeaker> (3) as we will need to modify the debhelper-compat version unless we are hoping to get debhelper-compat 13 in focal soon.
[21:48] <The_LoudSpeaker> what say bhaiya?
[21:57] <teward> debhelper-compat means debhelper
 debhelper can be a pain to backport :P
 That seems like the snowball rolled into an avalanche :P
[22:01] <The_LoudSpeaker> XD
[22:02] <The_LoudSpeaker> hence I said we can do a -3 with a relaxed debhelper dependency
[22:02] <The_LoudSpeaker> sound good ?
[22:06]  * The_LoudSpeaker goes to sleep. please ping me later here when you are free and can confirm on how to proceed next.


[12:31] <ubotu> New on thefridge: Developer Summit - you can contribute! <http://fridge.ubuntu.com/node/636>
[07:08] <Burgundavia> sladen: you alive?
[07:16] <sladen> Burgundavia: just
[07:16] <Burgundavia> sladen: can you do a fridgy thing for me?
[07:16] <sladen> Burgundavia: yup
[07:17] <Burgundavia> pm'ed you a few lines from elkubuntu


[01:50] <nhaines> Meeting soon!
[02:00] <nhaines> #startmeeting
[02:00] <darthrobot`> Meeting started Mon Jul 16 02:00:22 2018 UTC.  The chair is nhaines. Information about MeetBot at https://wiki.ubuntu.com/meetingology.
[02:00] <darthrobot`> 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
[02:00] <nhaines> Hello everyone, and welcome to the Ubuntu California meeting for July 15th, 2018.
[02:00] <nhaines> Tonight's agenda is available here: https://wiki.ubuntu.com/CaliforniaTeam/Meetings/18July15
[02:00] <darthrobot`> Title: [CaliforniaTeam/Meetings/18July15 - Ubuntu Wiki]
[02:01] <nhaines> The agenda for tonight is empty, so this will be a short meeting.
[02:01] <nhaines> #topic Upcoming Events
[02:02] <nhaines> The Ubuntu Free Culture Showcase is underway!  You can submit your Creative Commons-licensed photo to be considered for one of the default wallpapers in Ubuntu 18.10!
[02:02] <nhaines> The contest runs until August 13th, and you can view the current submissions, or add your own, via Flickr here: https://www.flickr.com/groups/ubuntu-fcs-1810/
[02:02] <darthrobot`> Title: [Ubuntu 18.10 LTS Free Culture Showcase - Wallpapers | Flickr]
[02:03] <nhaines> Note that we're looking for not just amazing photographs, but also for illustrations.  If you know of local or online photography groups, please feel free to inform them as well.
[02:03] <nhaines> #topic Announcements
[02:03] <nhaines> There are no LoCo announcements at this time.
[02:03] <nhaines> #topic Agenda
[02:04] <nhaines> There is no agenda for this meeting.
[02:04] <nhaines> #topic Other business
[02:04] <nhaines> Is there any other business to discuss before we wrap things up?
[02:09] <nhaines> Okay, that wraps up tonight's meeting.  Our next meeting is July 29th at 7pm.
[02:09] <nhaines> #endmeeting
[02:09] <darthrobot`> Meeting ended Mon Jul 16 02:09:38 2018 UTC.
[02:09] <darthrobot`> Minutes:        http://ihas.5cat.com/~darthrobot/ubuntu-us-ca/2018/ubuntu-us-ca.2018-07-16-02.00.moin.txt


[14:58]  * skaet waves
[14:58] <roadmr> hello!
[14:58]  * stgraber waves
[14:59] <tumbleweed> hi
[14:59] <arosales> hello
[14:59] <skaet> hiya roadmr, stgraber, tumbleweed, arosales :)
[14:59] <vanhoof> hi :)
[14:59] <ogra_> moo
[15:00] <mdeslaur> \o
[15:00] <popey> o/
[15:00] <Riddell> hi
[15:00] <skaet> looks like quorum,  :)
[15:00] <skaet> #startmeeting
[15:00] <meetingology> Meeting started Fri Jul 20 15:00:48 2012 UTC.  The chair is skaet. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15: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
[15:01] <skaet> Agenda (and minute location):
[15:01] <skaet> https://wiki.ubuntu.com/ReleaseTeam/Meeting/2012-07-20
[15:01] <skaet> .
[15:01] <skaet> Upcoming dates:
[15:01] <skaet> 12.10
[15:01] <skaet>     2012/07/23: Quantal Alpha 3 image candidates start  (slangasek, laney, skaet - contact points)
[15:01] <skaet>     2012/07/26: Quantal Alpha 3
[15:01] <skaet>     2012/08/23: Quantal Feature Freeze
[15:01] <skaet> 12.04.1
[15:01] <skaet>     2012/08/02: DesktopInfrastructureFreeze
[15:01] <skaet>     2012/08/09: KernelFreeze, LanguageTranslationDeadline, SRU Fix Validation Testing
[15:01] <skaet>     2012/08/16: FinalFreeze, ReleaseNoteFreeze
[15:01] <skaet>     2012/08/23: Ubuntu 12.04.1
[15:01] <skaet> .
[15:01] <skaet> Work Items:
[15:01] <skaet> 2012/07/20 -  2966  (was 3041 last week):  Thanks for the cleanup!  :)    We’re still a little high, but looking better now.   Please help get us back where we should be by making sure https://launchpad.net/~/+upcomingwork is up to date for your tasks.
[15:01] <skaet> Bugs:
[15:01] <skaet> Quantal: http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-tracking-bug-tasks.html
[15:01] <skaet> 12.04.1: https://bugs.launchpad.net/ubuntu/precise/+bugs?field.milestone%3Alist=49926
[15:01] <skaet> .
[15:01] <skaet> Pendinging Action Items:
[15:01] <skaet> None
[15:01] <skaet> .
[15:01] <skaet> Weekly Status Received:
[15:01] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001578.html - HW Cert - brendand
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001579.html - Security - mdeslaur
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001580.html - Kernel - ogasawara
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001583.html - Desktop - seb128
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001584.html - Lubuntu - gilir
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001585.html - Edubuntu - stgraber
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001587.html - Linaro - rsalveti
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001588.html - Server - arosales
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001589.html - Xubuntu - astraljava
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001590.html - Kubuntu - Riddell
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001591.html - Foundations - ogra_
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001592.html - Ubuntu One - joshuahoover
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001593.html - QA - jibel
[15:02] <skaet> https://lists.ubuntu.com/archives/ubuntu-release/2012-July/001594.html - Unity - popey
[15:02] <skaet> ..
[15:02] <skaet> #topic Questions and Comments
[15:04] <skaet> roadmr, gilir, stgraber, scott-work, astraljava, Riddell - is your flavor planning in participating in A3 next week?
[15:04] <stgraber> yep
[15:04] <gilir> yes
[15:04] <Riddell> stgraber: we're in
[15:04] <Riddell> skaet even
[15:04] <skaet> :)
[15:05] <roadmr> I don't think I have a flavor
[15:05] <skaet> sorry roadmr
[15:05] <skaet> popey,  will the compiz & gsettings changes be tested and land before monday?  (ie. in time for A3?)
[15:06] <popey> skaet, right now we're working on the migration tool for gconf->gsettings. I'd like to hope it could land today!
[15:06] <popey> but the tool isn't fully tested, as in, it's currently being written
[15:06] <popey> ..
[15:07] <skaet> popey,  so basically waiting on the testing to be written,  rather than the tool?
[15:07] <popey> a bit of both yes
[15:08] <skaet> popey,  understood.
[15:08] <skaet> ..
[15:08]  * skaet wonders if anyone else has questions?  please "o/" if you do
[15:09] <skaet> brendand, on your top 3 list, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990575 has a fix and needs testing,   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1016195 is also waiting for input from your team (incomplete),  who’s looking into it?
[15:09] <roadmr> o/
[15:10] <skaet> go roadmr
[15:10] <balloons> o/
[15:10] <roadmr> skaet: I'm working on bug 1016195, need to test kernels as requested by jsalisbury, and file an upstream bug, hopefully will do that today
[15:11] <roadmr> (well, rather I'm running the tests, jsalisbury is the one actually working on it!)
[15:11] <skaet> thanks roadmr.  :)   as long as they're not stalled out was the concern.
[15:11] <roadmr> our cert engineer in Lexington has the system for bug 990575, I'll poke him and see if he can move that one forward
[15:12] <roadmr> skaet: no, they're being looked at, they just happen to be a bit time-consuming (each test run for the E6220 takes at least 2 hours)
[15:12] <roadmr> ..
[15:12] <skaet> Thanks roadmr.
[15:12] <skaet> ..
[15:12] <skaet> go balloons
[15:13] <balloons> just a quick off the wall question for everyone -- has there been issues in general with the 3.5 kernel series being unstable and causing kernel panics?
[15:13] <popey> i haven't seen any
[15:13] <ogasawara> balloons: haven't heard of anything here, do you have any info on the panic?
[15:14] <balloons> I just randomly got pinged twice this week from folks who can't run quantal at all due to them.. I'm working on getting them to file bugs
[15:14] <ogasawara> balloons: ack, if you can get their info in a bug I'll have my team take a look
[15:14] <ogasawara> balloons: 3.5 is still feeling a little rough which is worrysome
[15:14] <balloons> ogasawara, thanks.. just wanted to make sure I wasn't missing something
[15:15] <balloons> ogasawara, yes.. ok, I was wondering if anyone else was feeling that
[15:15] <balloons> ..
[15:15] <ogasawara> balloons: we are seeing some suspend resume issues with the latest upload, so we're looking into that
[15:15] <ogasawara> ..
[15:16] <skaet> jibel, arosales - have we had booting Quantal server images since 0717?   can’t tell from the QA report.  Alternate issues appear fixed, so a bit confused.   If not,  which bug is the problem tracked under?
[15:16]  * Daviey hides.
[15:16] <arosales> skaet: I know ARM had some issues building
[15:17] <skaet> Daviey,  feel free to add knowledge ;)
[15:17] <jibel> skaet, it was the same problem for all d-i based images and it is fixed
[15:17] <arosales> Daviey:  were there sever images also having issues
[15:17] <arosales> cloud images are building
[15:18] <Daviey> No, they look good today
[15:18] <arosales> ah, ok thanks Daviey
[15:18] <arosales> ..
[15:18] <Daviey> https://jenkins.qa.ubuntu.com/job/precise-server-amd64_default/
[15:19] <Daviey> https://jenkins.qa.ubuntu.com/job/precise-server-i386_default/
[15:19] <jibel> the poblem was lvm only https://jenkins.qa.ubuntu.com/view/Quantal/view/All%20Quantal/job/quantal-server-i386_lvm/
[15:20] <Daviey> world looks good.
[15:21] <stgraber> ogasawara: lxc stress testing here (trying to reproduce an issue Laney found a while ago and that was also happenning to me) led to quite a few weird hangs: bug 1021471
[15:21] <stgraber> ogasawara: not completely clear what's going on, but something's definitely wrong
[15:21] <stgraber> ..
[15:22] <ogasawara> stgraber: hrm, thanks.  will get smb or cooloney to try and take a look.
[15:22] <ogasawara> ..
[15:22] <skaet> arosales,  which specific MIR’s are you concerned about in the blocking item section of your report?
[15:22] <skaet> ..
[15:22] <arosales> juju has become less of a concern
[15:22] <arosales> but we still have some MAAs related ones
[15:23] <arosales> and openstack
[15:23] <arosales> http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html Under MIR tracking are the ones we are looking at
[15:23] <skaet> thanks.
[15:24] <Daviey> But generally, http://people.canonical.com/~ubuntu-archive/component-mismatches.svg is a mess
[15:24] <Riddell> \o
[15:24] <Daviey> seb128: any news on webkit dropping recommends on gstreamer bad?
[15:24] <ScottK> IIRC the news was seb128 wasn't going to touch it.
[15:25] <Daviey> ScottK: O_o.. where did he state that?
[15:25] <seb128> Daviey, feel free to upload, I don't maintain webkit
[15:25] <Daviey> seb128: Who does?
[15:25] <seb128> Daviey, on #ubuntu-devel and #ubuntu-release
[15:25] <seb128> nobody that's the issue
[15:26] <seb128> I did take already too much time to update it this week because software-center and other stuff were broken due to incompatibilities between libsoup and webkit
[15:26] <Daviey> well if it's going to be a "no you" issue, i'll do it.. not sure what the issue is..
[15:26] <Daviey> Certainly seems more Desktop issue than anything else.. but whatever.
[15:26] <seb128> well, I can upload
[15:26] <seb128> I wanted to see if it was going to build on arm* first
[15:26] <seb128> to not waste another 1 day of buildd time to get armel back in sync
[15:26] <Daviey> ah, that makes more sense.
[15:27] <seb128> but you are like the 3rd person to ask since yesterday about the recommend
[15:27] <seb128> so maybe it's more important to drop those and we can build on armel later
[15:27] <seb128> I will do an upload
[15:27] <seb128> ..
[15:27] <Daviey> seb128: well.. Keeping c-m dirty is the servers teams job, and i won't have desktop encroaching :)
[15:28] <Daviey> ..
[15:28] <skaet> yeah,  Daviey,  components-mismatches definitely looks like it needs some love,   plusone team ping time.
[15:28] <seb128> ;-)
[15:28] <Daviey> skaet: i think it's mostly blocked on resourcing the MIR team. :(
[15:29] <Daviey> I have about another 5 MIR's next week. :(
[15:29] <Daviey> ..
[15:29] <skaet> Daviey,  ack.  and summer vacation.  :(      ok,  its noted.
[15:29] <skaet> ..
[15:30] <skaet> ogra_,  rather long list of 12.04.1 bugs in your report,  are the fixes all really going to land before 08/02?
[15:31] <ogra_> skaet, it is the list that was discussed in the foundations meeting, i doubt all of them will be fixed, no
[15:31] <ogra_> but its a list the team picks from
[15:31] <ogra_> (should have probably mentioned that in the header)
[15:32] <stgraber> I think I fixed around 5 of them since the meeting, xnox has a pretty long list of bugs that'll disappear from the list when we get the new mdadm and e2fsprogs
[15:32] <xnox> mdadm - review comments fixed & reuploaded: pending on slangasek for re-review;
[15:32] <ogra_> and some of them are already fix committed (i.e. flash-kernel issues)
[15:33] <stgraber> but I'm expecting quite a good chunk of the rest won't make it to the point release. Will start re-milestoning as I know more.
[15:33] <xnox> e2fsprogs - pending on me and infinity to do a line by line cod-review
[15:33] <skaet> ogra_,  can we prune the bug lists down to the most likely high/critical ones next week?
[15:34] <ogra_> yep, will do
[15:34] <skaet> thanks stgraber,  re-milestoning would be welcome.
[15:34] <skaet> thanks xnox.  :)
[15:34] <skaet> thanks ogra_ :)
[15:34] <skaet> ..
[15:34] <skaet> Riddell go
[15:34]  * skaet missed his "o/" earlier
[15:34] <Riddell> qt 3 is removed in debian, do we want to follow
[15:35] <Riddell> it's a question of if we care about lsb
[15:35] <Riddell> I don't but maybe someone else here does
[15:36] <skaet> seb128,   ^ any thoughts?
[15:37] <seb128> we do care about lsb I think
[15:37] <seb128> I would like to check with slangasek or cjwatson
[15:37] <seb128> I don't really care about qt3 though
[15:37] <seb128> does lsb requires it?
[15:37] <seb128> ..
[15:37] <Riddell> it's part of lsb 4.0 yes
[15:37] <Riddell> but nobody uses it any more
[15:38] <Riddell> I'll ask on the mailing list if nobody here has an opinion
[15:38] <Riddell> ..
[15:39] <skaet> Thanks Riddell!
[15:39] <seb128> thanks
[15:40]  * skaet doesn't see any more hands in the backscroll...
[15:40] <skaet> anyone else have questions this week?
[15:40] <roadmr> o/
[15:41] <mdeslaur> Riddell: does stuff like the proprietary citrix client use qt3?
[15:41] <Riddell> mdeslaur: that I don't know
[15:41] <mdeslaur> we might want to take a look before killing it
[15:42] <mdeslaur> ..
[15:42] <skaet> go roadmr
[15:42] <roadmr> super-quick question re: bug 1021293, is this possible to fix by uploading a new version of the offending package so that upgrading from a clean 12.04 will succeed? (other than guarding against that sort of problem as suggested by cjwatson)
[15:42] <roadmr> ..
[15:43] <stgraber> mdeslaur: citrix doesn't at least
[15:43] <stgraber> ..
[15:43] <mdeslaur> hah, openmotif :)
[15:43] <mdeslaur> ..
[15:44] <rsalveti> o/
[15:45] <skaet> ogra_, cjwatson, stgraber,  ^ any thoughts on roadmr's question?   or best handled in the bug?
[15:45] <stgraber> best handled in the bug. cjohnston replied an hour ago with some more details.
[15:45] <stgraber> ..
[15:45] <stgraber> cjwatson
[15:46] <skaet> ok
[15:46] <skaet> rsalveti, go
[15:47] <rsalveti> ogasawara: ogra_: do we know what will happen with the kernel used for omap4? TI is currently only focused on getting the 3.4 based on stable, and is not showing any plans on moving the work to a 3.5 based kernel
[15:47] <cjwatson> roadmr: You'll probably have a fix by the end of today, without trying to work around me.
[15:47] <ogra_> well, afaik paolo already worked on a 3.5 port
[15:47] <ogra_> rsalveti, ^^^
[15:48] <ogra_> cherrypicking the missing bits into a mainline 3.5
[15:48] <rsalveti> ogra_: oh, ok, so then he'll be mainly maintaining the tree himself I suppose
[15:48] <roadmr> cjwatson: awesome, thanks!
[15:48] <cjwatson> roadmr: I'll talk with Robert Ancell at some point, but, while accountsservice is broken, I don't think we should rely on whack-a-mole fixes in packages being upgraded to fix this general problem.
[15:48] <ogra_> rsalveti, but i dont know the status, he vanished with the rest of the kernel team from IRC when their sprint started, probably ogasawara can give details
[15:49] <ogra_> i know he had something that booted already though ...
[15:49] <ogra_> ..
[15:50] <rsalveti> ogra_: ok, I can follow this up with the kernel team then, just want to make sure we're at least working on the same thing, if possible
[15:50] <ogasawara> rsalvet, ogra_:  well, the current omap4 kernel is v3.4 based.  ppisati has been playing with a v3.5 port though.  I'll throw it on the agenda for the morning to discuss further.
[15:50] <ogasawara> ..
[15:50] <rsalveti> as if he decides to push a 3.5 based on, we'd need to make sure it's well tested
[15:50] <ogra_> rsalveti, well, he cherry picked from TILT i think
[15:50] <ogra_> ..
[15:50] <brendand> cjwatson - it still needs to be fixed in ubiquity for sure, we're just wondering will the 12.04 release image work for us again
[15:50] <rsalveti> ogasawara: ok, thanks
[15:50] <rsalveti> ogra_: yeah, ok :-)
[15:50] <cjwatson> brendand: Ah, yes, we do need to fix both
[15:50] <rsalveti> ..
[15:51] <cjwatson> brendand: Any of my three suggestions in the bug would cover that
[15:51] <cjwatson> brendand: But I don't routinely work on accountsservice myself so I'd prefer robert_ancell's input there
[15:51] <cjwatson> Anyway, we should do this in the bug
[15:52] <brendand> cjwatson, sure. i have already posted the same question in the bug
[15:52] <skaet> am not seeing any further questions for this meeting...
[15:52] <ogra_> o/
[15:52] <skaet> go ogra_  :)
[15:53] <ogra_> rsalveti, whats the status on PVR, any solution in sight ?
[15:53] <ogra_> (and also can you make it work with a possible 3.5 kernel easily)
[15:53] <ogra_> ..
[15:54] <rsalveti> ogra_: I'll be working on getting it available at quantal over the next few days, but one thing that kind of worried be at the first moment is that this driver is not behaving properly with compiz/unity
[15:54] <ogra_> yeah, i read that
[15:54] <rsalveti> so I'm checking the bugs on the linaro side, and also trying to find if someone would be able to help
[15:54] <ogra_> did you use the new upstream compiz ?
[15:54] <rsalveti> probably robclark
[15:54] <rsalveti> both the old and the new that is currently on development
[15:55] <ogra_> great, if rob is involved i'm confident that we'll have a happy end :)
[15:55] <rsalveti> but, as long as we don't deploy compiz right away with gles support, it'd still be useful to have a newer driver available
[15:55] <ogra_> ..
[15:55] <rsalveti> ogra_: exactly ;-)
[15:55] <rsalveti> ..
[15:56] <skaet> time to end now then.  :)
[15:56] <skaet> #endmeeting
[15:56] <meetingology> Meeting ended Fri Jul 20 15:56:24 2012 UTC.
[15:56] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-20-15.00.moin.txt
[15:56] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-07-20-15.00.html
[15:56] <skaet> Thanks for your participation this week,  roadmr, stgraber, tumbleweed, jibel, arosales, vanhoof, ogra_, Daviey, ogasawara, Riddell, roadmr, seb128, balloons, popey, gilir, ScottK, cjwatson, brendand, rsalveti.
[15:56] <arosales> Thanks for chair'ing skaet
[15:56] <roadmr> thanks!
[15:56] <ogra_> thanks skaet !
[15:56] <seb128> skaet, thank you!
[15:56] <popey> thanks skaet
[15:56] <balloons> thanks skaet :-0
[15:56] <roadmr> cjwatson: thanks for looking at our crazy bugs :)
[15:57] <jibel> thanks skaet
[15:57] <rsalveti> thanks skaet
[15:57] <stgraber> thanks!
[17:44] <seb128> @SRU team: is there any motivated member who wants to review the unity precise SRU just uploaded? we would like to get it early rather than late to keep open the possibility to do another SRU round for the 12.04.1 desktop freeze
[17:44] <meetingology> seb128: Error: "SRU" is not a valid command.
[17:45] <seb128> some notes
[17:45] <seb128> - the list of bugs fixed in that SRU is quite long
[17:45] <seb128> - some of the bugs are not fully SRU-rules-compliant yet, but the vast majority is, the #ps guys are working on finishing testcases etc for the remaining ones
[17:46] <seb128> (I don't think we should block the SRU on that)
[17:46] <seb128> - the update got quite some solid testing already, some people are running it for a week and it went through several round of checkbox manual test and automatic testing
[17:46] <seb128> with some issues found and fixed during the week
[17:46] <seb128>
[17:47] <seb128> to do it short: it's going to be a bit tricky to review but it got solid automated and manual testing and we are confident it should create no issue
[17:47] <seb128> ;-)
[17:47] <seb128> graaa, that was meant for #ubuntu-devel :p
[17:51] <skaet> seb128, yeah that would be more appropriate,  as would #ubuntu-release  ;)
[17:51] <seb128> skaet, I will not crosspost on a third channel, I think the SRU team are all on #ubuntu-devel, I posted there now ;-)
[17:52] <skaet> :)
[19:13] <astraljava> skaet: Sorry, was on the road during the meeting. Yes, Xubuntu will participate in A-3 next week. Thanks!
[19:14] <skaet> thanks astraljava :)


[01:30] <mpt> Goooooooooooooooooooood morning Launchpadders!
[03:26] <ubotu> New bug: #125377 in blueprint "Blueprint registration form should default to you as drafter" [Undecided,New]  https://launchpad.net/bugs/125377
[04:45] <ubotu> New bug: #125385 in soyuz "Drop .summary for distroseries" [Undecided,New]  https://launchpad.net/bugs/125385
[05:25] <ubotu> New bug: #125391 in blueprint "Feedback requests have no date created" [Undecided,New]  https://launchpad.net/bugs/125391
[05:40] <ubotu> New bug: #125394 in blueprint ""Give feedback" doesn't let you give feedback" [Undecided,New]  https://launchpad.net/bugs/125394
[05:46] <ubotu> New bug: #125395 in blueprint "Clearing a feedback request returns a non-error error message" [Undecided,New]  https://launchpad.net/bugs/125395
[07:55] <ubotu> New bug: #125420 in launchpad-bazaar "supermirror tasking locks?" [Undecided,New]  https://launchpad.net/bugs/125420
[09:20] <cprov> morning, guys !
[09:20] <Hobbsee> morning cprov!
[09:58] <carlos> morning
[09:59] <Fujitsu> Hi carlos.
[10:12] <mrevell> Morning all!
[10:12] <Hobbsee> morning mrevell!
[10:12] <mrevell> hey Hobbsee - what were your impressions of Edge, then?
[10:12] <Hobbsee> mrevell: slower, but were OK :)
[10:13] <Hobbsee> the 12 dupes i marked just then were quick.  opened them in tabs, did them that way, etc
[10:13] <mrevell> Hobbsee: Ah, so the slowness persisted?  Surely you've learnt that by now, Hobbsee?
[10:16] <Hobbsee> mrevell: nope.  just tried it today
[10:16] <Hobbsee> Fujitsu: i did know that.  anything that's not a-z is a bit hit and miss
[10:23] <BjornT> Hobbsee: fixing searching is not something that is simple to do. the best thing you can do is to file bugs about what doesn't work, even though it might take quite a while for the bug to be fixed.
[10:24] <Hobbsee> BjornT: i figured that, from when i wrote a search engine thing, for uni :P
[10:24] <Hobbsee> BjornT: it seems to be just anything with a symbol, i suspect, but i'll have to test more before filing
[10:40] <babarhaq> Hi all, i submitted a bug some time back. how can i follow it up since i lost the bug # and launchpad doesent seem to offer something like "my submitted bugs"
[10:41] <Fujitsu> babarhaq: https://launchpad.net/people/+me/+reportedbugs
[10:41] <babarhaq> Fujitsu: thnax
[10:41] <Fujitsu> babarhaq: np
[10:42] <gnomefreak> isnt it ~me/+reportedbugs
[10:44] <Fujitsu> gnomefreak: Not unless your username is `me'
[10:45] <gnomefreak> Fujitsu: you used +me thought it should be ~ instead
[10:45] <Fujitsu> gnomefreak: people/+me, not +me
[10:46] <gnomefreak> https://launchpad.net/~gnomefreak/ is my homepage no people and its ~nick
[10:47] <Fujitsu> gnomefreak: That's the same as /people/gnomefreak.
[10:47] <gnomefreak> ah ok
[11:06] <shirish> can somebody look at bug 125472
[11:06] <ubotu> Launchpad bug 125472 in launchpad "mail bounced sent to launchpad" [Undecided,New]  https://launchpad.net/bugs/125472
[11:16] <ubotu> New bug: #125472 in launchpad "mail bounced sent to launchpad" [Undecided,New]  https://launchpad.net/bugs/125472
[02:26] <ubotu> New bug: #125505 in launchpad "Person.addMember() does not properly invalidate the person's _inTeam_cache" [Undecided,New]  https://launchpad.net/bugs/125505
[03:36] <barry>  /nick barry
[03:38] <Hobbsee> haha
[03:38] <Hobbsee> oh dear
[03:52] <jordi> barry: dude!
[03:52] <jordi> barry: I learned just the other day you joined canonical
[03:52] <barry> jordi: hello!  good to hear from you again!
[03:53] <jordi> this is convenient, because this way I can tell you via IRC I should become (again!) the Catalan Champion for mm
[03:53] <barry> yes, i joined in feb
[03:53] <jordi> barry: I had no idea
[03:53] <jordi> barry: I'm currently fixing up the templates for the current stable version; should I focus on CVS?
[03:53] <barry> jordi: that would be excellent.  maybe we can talk about some of my short term ideas for improving translation (short of moving to rosetta, which may still happen).
[03:54] <jordi> barry: yeah, sure!
[03:54] <barry> jordi: we're on bzr+lp now :)
[03:54] <jordi> oh, okay :)
[03:54] <jordi> I haven't tried downloading in a while, you see ;)
[03:54] <barry> http://wiki.list.org/display/DEV/MailmanBranches
[03:55] <barry> that's okay.  hope all has been well with you!
[03:55] <jordi> yeah
[03:55] <jordi> we didn't meet here by just one month
[03:55] <jordi> ah, moved on June 22.
[03:56] <jordi> I wasn't *that* out of datye
[03:56] <barry> nope.  bzr so rocks better than svn
[03:56] <jamesh> yeah
[03:57] <jamesh> "svn rocks" just prints an error
[03:57] <jordi> okay, I wasout of date. I think the last time I downloaded bleeding edge mailman, it was on cvs, not svn :P
[03:58] <barry> jordi, yeah, that /is/ pretty old.  i don't remember how long since we moved to svn, but it's been a while
[03:58] <barry> jamesh: :)
[04:00] <Rinchen> me
[04:00] <Rinchen> hehe
[04:00] <mpt> anyway
[04:00] <mpt> MEETING TIME
[04:00] <cprov> me
[04:00] <bigjools> me
[04:00] <sinzu2> me
[04:00] <bac> me
[04:00] <Rinchen> me
[04:00] <ddaa> me
[04:00] <mpt> For the next half hour or so, we'll be discussing Launchpad development.
[04:00] <sinzui> me
[04:00] <BjornT> me
[04:00] <mpt> Who is here today?
[04:00] <barry> me
[04:00] <gmb> me
[04:00] <jamesh> me
[04:00] <adeuring> me
[04:00] <carlos> me
[04:01] <allenap> me
[04:01] <flacoste> me
[04:01] <danilos> meme
[04:01] <matsubara> me
[04:01] <danilos> me
[04:01] <statik> me
[04:01] <mrevell> me
[04:01] <schwuk> me
[04:01] <mpt> Team leaders, please check that all your colleagues who should be here are
[04:02] <mpt> Who is representing the lp-bazaar team today?
[04:02] <jtv> me
[04:02] <danilos> jtv: ping
[04:02] <ddaa> mh
[04:02] <matsubara> stub, SteveA and mthaddon are not here
[04:02] <jtv> danilos: pong
[04:02] <matsubara> errr
[04:02] <mpt> ddaa, ok
[04:02] <matsubara> hi mthaddon
[04:02] <danilos> jtv: :)
[04:02] <mthaddon> here
[04:02] <ddaa> I guess that should be me, but I have not done my homework.
[04:02] <mpt> == Agenda ==
[04:03] <mpt>  * Next meeting
[04:03] <mpt>  * Actions from last meeting
[04:03] <mpt>  * Oops report (Matsubara)
[04:03] <mpt>  * Bug report ([wiki:JoeyStanford/topweeklybugs Current Top Items] )
[04:03] <mpt>  * Bug tags
[04:03] <kiko-afk> me
[04:03] <mpt>  * Operations report (mthaddon)
[04:03] <mpt>  * DBA report (stub)
[04:03] <mpt>  * Sysadmin requests
[04:03] <mpt>  * A top user-affecting issue (mrevell)
[04:03] <mpt>  * Changes to security.cfg, edge.launchpad.net and you (kiko)
[04:03] <BjornT> jsk_: ping
[04:03] <BjornT> intellectronica: ping
[04:03] <mpt>  * Pre-release QA (matsubara)
[04:03] <mpt>  * Blockers
[04:03] <jsk_> me
[04:03] <intellectronica> BjornT, hi
[04:03] <jtv> mpt: stub said he'd be late
[04:03] <jsk_> BjornT: pong
[04:03] <mpt> ok
[04:03] <carlos> mpt: I think you forgot the question about who will not be in next meeting
[04:04] <BjornT> jsk_, intellectronica: i was pinging you for the meeting
[04:04] <mpt> carlos, I have not forgotten
[04:04] <intellectronica> me
[04:04] <carlos> ok :-P
[04:04] <intellectronica> BjornT, thanks!
[04:04] <jsk_> BjornT:cheers!
[04:04] <mpt> mwh is at at post-EuroPython PyPy sprint
[04:04] <mpt> Any other apologies?
[04:04] <mpt> thanks jtv
[04:05] <mpt> == Next meeting ==
[04:05] <carlos> mpt: hmm, I didn't see 'Next meeting' entry in the agenda, sorry
[04:05] <mpt> Who will be unable to attend same time next week?
[04:06] <kiko> I will make a special effort
[04:06] <kiko> though I will be at planning
[04:06] <jtv> danilo?
[04:06] <mpt> == Actions from last meeting ==
[04:06] <mpt>  * jamesh to follow up on bug 58220
[04:06] <ubotu> Launchpad bug 58220 in launchpad "When an error occurs processing a request another oops is recorded because there's no interaction set up." [High,Confirmed]  https://launchpad.net/bugs/58220 - Assigned to James Henstridge (jamesh)
[04:06] <carlos> Well, given that danilos seems like is not around
[04:07] <carlos> mpt: danilos will be at GUADEC too
[04:07] <mpt> carlos, ok
[04:07] <jtv> danilos, wake up!
[04:07] <kiko> did jamesh look at that?
[04:07] <mpt> jamesh?
[04:07] <jamesh> no I didn't.
[04:08] <mpt> ok, thanks
[04:08] <danilos> I will be at GUADEC next week, along with carlos, then off to sprint with jtv and carlos week after that
[04:08] <mpt> == Oops report (Matsubara) ==
[04:08] <Rinchen> That bug is targeted for 1.1.7 btw. Kiko?
[04:08] <danilos> hum, is my text making it through?
[04:08] <matsubara> mpt: No new oops to report
[04:08] <mpt> danilos, yes, thanks
[04:08] <jtv> danilos: yes
[04:09] <kiko> Rinchen, I guess not any longer :-( retarget.
[04:09] <mpt> matsubara, really? wow
[04:09] <kiko> top timeout OOPSes are still translate and filebug
[04:09] <mpt> thanks anyway :-)
[04:09] <Rinchen> kiko, ok, that's what I was after. thx.
[04:09] <mpt> == Bug report ==
[04:09] <matsubara> mpt: nothing new. the ones we have are known and people are working on it.
[04:09] <mpt> ok
[04:09] <Rinchen> There are two in progress critical bugs this week: Bug 125126 and Bug 125423.
[04:09] <Rinchen> Both are in progress and targeting 1.1.7.  For the future, I've changed the meeting agenda to reference this as "critical bugs" and removed the ugly wiki link seen each week on paste. Any comments?
[04:09] <ubotu> Launchpad bug 125126 in blueprint "Broken "register a blueprint" link on certain blueprint listing pages." [Critical,In progress]  https://launchpad.net/bugs/125126 - Assigned to Jonathan Knowles (jsk)
[04:09] <ubotu> Bug 125423 on http://launchpad.net/bugs/125423 is private
[04:10] <danilos> ok, thanks
[04:10] <Rinchen> 3
[04:10] <Rinchen> 2
[04:10] <Rinchen> mpt, back to you
[04:10] <jsk_> jsk: I'm working on that one right now.
[04:10] <mpt> Rinchen, I will mail you about the bug report in the next few days. Please nag me if you notice that I haven't.
[04:10] <Rinchen> jsk_, I know. Saw the branch :-)
[04:11] <mpt> thanks Joey
[04:11] <Rinchen> mpt, will do
[04:11] <mpt> == Bug tags ==
[04:11] <mpt> There are currently no proposed tags
[04:12] <mpt> == Operations report (mthaddon) ==
[04:12] <mthaddon> Discovered a staging DB update that was slowing things down yesterday, but I think stub has fixed this?
[04:12] <mthaddon> Working on app server reconfig, and PQM duration graphing
[04:12] <mthaddon> Edge redirects seemed to work okay
[04:12] <mthaddon> that's it from me
[04:12] <mpt> mthaddon, do all the edge subdomains have correct certificates now?
[04:13] <kiko> mthaddon, when we do the app server reconfig edge will start being able to send email, right?
[04:13] <mthaddon> mpt: certificates ordered, and setup in process
[04:13] <mpt> great
[04:13] <mthaddon> kiko: I believe that will happen as part of the app server reconfig
[04:13] <kiko> rock on!
[04:13] <mpt> I happen to know that that will make life more bearable for Safari users, who currently have no CSS at all on edge subdomains :-)
[04:13] <Rinchen> Launchpad mail is a wondrous thing.
[04:14] <mthaddon> really, for both of them? :)
[04:14] <mpt> == DBA report (stub) ==
[04:14] <jtv> stub's not here
[04:14] <jtv> he says nothing to report
[04:14] <mpt> so he isn't
[04:14] <mpt> thanks jtv
[04:14] <jtv> and everyone, please land your changes by...
[04:14] <jtv> ...whatever deadline kiko & joey say.
[04:14] <jtv> EOF
[04:15] <mpt> == Sysadmin requests ==
[04:15] <Rinchen> We've had a number of RT requests close this week including the final PPA setup ticket. Is anyone blocked on an RT request?
[04:15] <ddaa> I have
[04:15] <ddaa> RT 28515
[04:15] <ddaa> "Rewrite rule for http://bazaar.launchpad.net/robots.txt"
[04:15] <ddaa> blocking one of my 1.1.7 bugs
[04:15] <Rinchen> ddaa, ok, I kick up it's priority
[04:16] <cprov> Rinchen: yes, germanium seems to be ready (although, I haven't messed with production DB yet)
[04:16] <Rinchen> ddaa, if this happens again (and this is a general statement to everyone) please don't wait until Thursday to contact me. Email or ping me ASAP.
[04:16] <ddaa> Rinchen: I sent the RT yesterday
[04:16] <ddaa> I thought that could wait till the meeting :)
[04:16] <kiko> ddaa, then it's likely your bug will not make 1.1.7.
[04:17] <Rinchen> ddaa, thanks. :-)
[04:17] <ddaa> ?
[04:17] <ddaa> kiko: closing the RT fixes the bug
[04:17] <ddaa> no code involved
[04:17] <kiko> ddaa, week 3 is not the week to be discovering anything.
[04:18] <Rinchen> kiko, ddaa reported on Monday that this was a config change.
[04:18] <Rinchen> kiko, I didn't realize it was an RT request but I'm happy to deal with that. It may not make it for 1.1.7 though.
[04:19] <kiko> Rinchen, why wasn't the RT filed on Monday then? anyway...
[04:19] <Rinchen> Anyone else blocked on RT?
[04:19] <Rinchen> kiko, yes the timing is a bit later than desired.
[04:19] <Rinchen> mpt, back to you
[04:19] <mpt> thank you Rinchen
[04:19] <mpt> == Sysadmin requests ==
[04:19] <mpt> whoops, already done that
[04:19] <Rinchen> interate
[04:19] <Rinchen> iterate
[04:19] <mpt> == A top user-affecting issue (mrevell) ==
[04:20] <mrevell> A quick one today!
[04:20] <kiko> font colors!!!
[04:20] <mrevell> People filed a large number of duplicate bugs following today's OpenOffice.org updates in Ubuntu.
[04:20] <mrevell> This required a lot of manual work from the bug squad.
[04:20] <mrevell> Hobbsee has asked if we can introduce better bug duplicate checking intro Launchpad.
[04:20] <mrevell> I was pleased to direct her to edge, where she was able to see our new approach to bug dupe warning.
[04:20] <mrevell> Thanks mpt, back to you.
[04:20] <mrevell> As I say, a quick one.
[04:20] <kiko> rock on launchpad!
[04:20] <mrevell> kiko: No, not font colours :)
[04:20] <mpt> I'll take this opportunity to pimp the duplicate-bug-handling spec, which would make duplicates quicker to mark :-)
[04:21] <mpt> thanks mrevell
[04:21] <mpt> ==  Pre-release QA (matsubara) ==
[04:21] <matsubara> How's the testing going? Did you guys prepared a plan to tackle all thespecs and bugs to be tested? I know that Translations team have one(wiki:TranslationsTestPlan). Other teams have something similar?
[04:21] <BjornT> no, not yet
[04:22] <kiko> flacoste? thumper? jsk_?
[04:22] <flacoste> flacoste: no test plan in place yet
[04:23] <jsk_> kiko: no formal test plan in place. Though have been conducting informal testing.
[04:23] <barry> no, i don't have a plan, but my landing work is fundamental, with no external exposure yet.
[04:23] <jtv> Those plans can get pretty big, so don't wait too long!
[04:23] <kiko> what jtv said. but land your patches. :)
[04:23] <jtv> ...and brush your teeth.
[04:23] <matsubara> and let me know if you need help testing
[04:24] <matsubara> I think the format jtv used for the Translations test plan is pretty good. you guys can follow that one
[04:24] <matsubara> or improve on it.
[04:24] <kiko> remember that you need to deliver a sign-off email
[04:24] <kiko> in the format we specified
[04:25] <kiko> matsubara will be collecting them
[04:25] <kiko> mthaddon, matsubara's QA sign-off is a release blocker, btw!
[04:25] <mthaddon> gotcha
[04:25] <mpt> This smells like something that could be handled with tags and bug comments
[04:25] <kiko> mpt, what could?
[04:25] <mpt> testing and sign-off
[04:25] <Rinchen> As for testing, my hat is also in the ring. If you want help, I'm also available.
[04:25] <jtv> mpt: could, but harder to edit!
[04:26] <kiko> I don't think so
[04:26] <matsubara> I think mpt has a point
[04:26] <kiko> but let me think about it
[04:26] <mpt> anyway
[04:26] <mpt> That's probably a subject for another day
[04:26] <kiko> right.
[04:26] <mpt> Thank you matsubara
[04:26] <matsubara> ok. thanks mpt
[04:26] <mpt> == Changes to security.cfg, edge.launchpad.net and you (kiko) ==
[04:27] <kiko> Okay
[04:27] <kiko> this is a quick topic
[04:27] <kiko> edge as you run runs against the production database
[04:27] <kiko> now, there's a slight loophole in the DB freeze
[04:27] <kiko> and that is that changes to security.cfg can be made even during freeze
[04:28] <kiko> this runs the risk of causing edge oopses, however, if edge requires a permission that has not been granted to the production DB
[04:28] <kiko> so if you are landing a security.cfg change while the database is frozen
[04:28] <kiko> you need to email stub, mthaddon CC: launchpad asking them to apply the manual change to jubany as well
[04:29] <kiko> reviewers, please note this when you see a security.cfg change.
[04:29] <kiko> any questions? if not, EOT
[04:29] <mpt> kiko, is this written up on a wiki page that will be more visible than a meeting log?
[04:29] <kiko> no.
[04:30] <kiko> and I don't know what wiki page to write it on TBH.
[04:30] <mpt> ok
[04:30] <statik> kiko: I'll volunteer to add a note about this to the reviewers page
[04:30] <kiko> statik, thanks!
[04:30] <mpt> thanks statik
[04:30] <mpt> ok
[04:30] <mpt> == Week 3 reviews (kiko) ==
[04:31] <kiko> I'm looking at the reviews page
[04:31] <barry> statik: perhaps also DatabaseSchemaChanges
[04:31] <kiko> there are a few things I'm a bit concerned with
[04:31] <statik> barry: ack
[04:31] <kiko> a) jml has put up two branches that weren't signed off on yesterday.
[04:31] <kiko> is anyone not familiar with the no-new-branches-unless-signed-off-by-me rule?
[04:31] <barry> kiko: after friday of week 2?
[04:32] <kiko> correct.
[04:32] <mpt> kiko, I was unfamiliar with that, and there's a branch like that of mine there too
[04:32] <kiko> mpt, your branch is not targeted at 1.1.7.
[04:32] <kiko> that's fine.
[04:32] <gmb> kiko: Me - I've seen dribs and drabs but never saw the original email.
[04:32] <gmb> Ta.
[04:32] <kiko> okay
[04:32] <Rinchen> Original Email from kiko has the subject of: "Read this: 2007-06 (1.1.7) process updates"
[04:33] <mpt> kiko, the what-next branch is.
[04:33] <kiko> mpt, it's reviewed anyway
[04:33] <mpt> yes :-)
[04:33] <kiko> b) I'm concerned that reviewers haven't done their reviews in advance, which is quite unfortunate
[04:33] <kiko> please finish all your review replies now
[04:33] <kiko> I mean -- at the end of the meeting, start, and don't finish until you're replied to all your pending reviews
[04:33] <kiko> or decided to give up
[04:33] <statik> will do. I've been particularly bad at this
[04:33] <kiko> I don't want a PQM trainwreck tomorrow.
[04:34] <barry> kiko: of course reviewers have their own branches they're trying to get through review, so there's a tension there
[04:34] <kiko> barry, monday-wednesday should really have been a review priority, in hindsight..
[04:34] <kiko> but anyway, let's make sure we finish replies today, because otherwise it will really be too late.
[04:35] <kiko> is anyone interested in working late friday?
[04:35] <barry> kiko: i think we need to find some time to talk about this in more detail.  not now tho.  +1 on cranking through reviews
[04:35] <kiko> yeah.
[04:35] <kiko> carlos, that's okay -- I just want to know if anyone /is/ interested
[04:35] <kiko> in lieu of having branches dropped off 1.1.7
[04:36] <carlos> kiko: I'm just pointing that is not something good to do :-)
[04:36] <mpt> I will, but I'm crazy
[04:36] <barry> kiko: i can help if needed
[04:36] <sinzui> Kiko: I always work late Fridays.
[04:36] <kiko> well, reason I'm asking is that we could freeze PQM saturday morning my time instead
[04:36] <kiko> given that so many people are late
[04:36] <bac> kiko: i can work late on reviews if necessary
[04:36] <jsk_> kiko: I'll be here.
[04:36] <barry> kiko: sure
[04:37] <kiko> bac, it's not so much reviews as it is landings -- reviews should be finished today, really
[04:37] <kiko> okay, let's see how today went and I'll decide tonight
[04:37] <mthaddon> let me know, kiko
[04:37] <kiko> mthaddon, thanks :) I wasn't asking you to work sat, though -- I would have requested perms to do the change myself
[04:37] <bac> kiko: true, but there will be follow-ups.
[04:37] <BjornT> kiko: unless everyone gets merge-conditional, reviews are needed as well.
[04:38] <kiko> at this point it's either merge-conditional or 1.1.8 I feel.
[04:38] <mthaddon> kiko: I can do a one line change on Sat if need be (that's all it requires)
[04:38] <kiko> mthaddon, okay. thanks so much.
[04:38] <kiko> I think I've made myself impopular enough now! let the meeting proceed.
[04:38] <mpt> Thank you kiko
[04:39] <mpt> == Blockers ==
[04:39] <bigjools> tomorrow is going to be a loooong day
[04:39] <matsubara> TEAM: infrastructure BLOCKED: no
[04:39] <flacoste> TEAM: answers BLOCKED: no
[04:39] <barry> TEAM: mailing lists BLOCKED: no
[04:39] <statik> TEAM: commercialization BLOCKED: no
[04:39] <allenap> TEAM: bug tracker BLOCKED: no
[04:39] <jtv> TEAM: translations BLOCKED: no
[04:39] <schwuk> TEAM: hwdb BLOCKED: no
[04:39] <ddaa> TEAM: bazaar BLOCKED: no (not that I know)
[04:39] <bigjools> TEAM: Soyuz, BLOCKED: 1.1.7 reviews (does that count as a block?)
[04:39] <jsk_> TEAM: blueprints BLOCKED: no
[04:40] <ddaa> 1.1.7 reviews of course, goes w/o saying IMO
[04:40] <mpt> TEAM: UI BLOCKED: lack of iconographers
[04:40] <bigjools> right
[04:40] <kiko> TEAM: management BLOCKED: review replies, PPA TOS (statik)
[04:40] <kiko> mpt, what's up with brilliant?
[04:40] <mpt> kiko, their icon artist is on holiday, Usman's trying to find a new one
[04:40] <kiko> gotcha.
[04:40] <kiko> one thing about reviews
[04:41] <mpt> or a stand-in
[04:41] <kiko> you should be proactive about seeking a reviewer
[04:41] <kiko> in particular for week 3
[04:41] <kiko> if you go into week 3 without a reviewer that has agreed to work with you on your branches, you're relying on luck to get your branches through
[04:41] <kiko> secure a reviewer for your branches early
[04:41] <kiko> don't let it linger for 24h in the general queue
[04:42] <kiko> EOT
[04:42] <mpt> all righty then
[04:42] <mpt> Thank you everyone
[04:42] <mpt> MEETING ENDS
[04:42] <kiko> thanks mpt!
[04:42] <carlos> mpt: thanks
[04:42] <kiko> best chair ever!
[04:42] <cprov> thanks
[04:43] <mpt> Remember to get on to your review replies now
[04:43] <mpt> even if it happens to be 2.43am where you are
[04:43] <kiko> mpt, CORRECT
[04:44] <cprov> kiko: talking about reviews, can you review my 'ppa-ui' ?
[04:45] <kiko> cprov, probably in a few hours
[04:45] <jtv> ddaa: pqm is not hungry, from the looks of it...
[04:45] <cprov> kiko: good, apart of the TOS and some pagetests it's done.
[04:46] <kiko> cool
[04:46] <kiko> cprov, statik owes you!
[04:46] <Hobbsee> jtv: then feed soyuz.
[04:46] <mpt> kiko, are Tom B's comments sufficient as a reply to your review of mpt/launchpad/2007-04-bug-87221?
[04:46] <Hobbsee> jtv: before it starts eating people's uploads again.
[04:47] <kiko> mpt, not really, but I can reply to him now
[04:48] <mpt> ok, then I'll know what to change and what not to
[04:48] <Hobbsee> jtv: :)
[04:49] <intellectronica> mpt, i'm not too busy and happy to take care of the JS stuff (I realize you're overclocking yourself over there)
[04:49] <stub> Sorry guys. Anything I need to attend to?
[04:50] <kiko> replied
[04:52] <mpt> intellectronica, that would be fab
[04:52] <intellectronica> mpt, no prob
[04:55] <ubotu> New bug: #125545 in launchpad "Language variants should know their parent language" [Undecided,New]  https://launchpad.net/bugs/125545
[05:10] <mpt> kiko, replied to your review of 2007-07-what-next
[05:10] <kiko> mpt, I saw that!
[05:12] <Hobbsee> erm...why does https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.gutsy/ work, but https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ (the directory above)  404?
[05:14] <kiko> not sure Hobbsee -- ask thumper or ddaa
[05:16] <ddaa> Hobbsee: because nobody has implemented this page
[05:16] <ddaa> and there's no way to get to except URL hacking
[05:17] <Hobbsee> right
[05:18] <Hobbsee> wow, bzr seems faster
[05:18] <ddaa> it probably is, the bzr folks have been focusing on performance in the past weeks
[05:18] <Hobbsee> :)
[05:18] <Hobbsee> this is the first time i've tested it out though
[06:09] <LarstiQ> hmmm
[06:10] <LarstiQ> line 4669 being at 18%, having merged earlier I'd be in less pain now.
[06:10] <ubotu> New bug: #125569 in launchpad "LaunchpadTestCase is depercated, tests should remove it" [Undecided,New]  https://launchpad.net/bugs/125569
[06:15] <ubotu> New bug: #125572 in launchpad "registerLaunchpadFunction is not an obvious name" [Undecided,New]  https://launchpad.net/bugs/125572
[06:15] <ubotu> New bug: #125574 in malone "Strange formatting of "<Project> does not use Launchpad..." warnings" [Undecided,New]  https://launchpad.net/bugs/125574
[08:25] <ubotu> New bug: #125598 in launchpad "'i can haz cheezburger?' message when subscribing groups" [Undecided,New]  https://launchpad.net/bugs/125598
[08:41] <kiko> matsubara, we have a "trivial" bug tag, right?
[08:41] <matsubara> yes
[08:41] <matsubara> kiko: ^
[08:41] <kiko> thanks!
[09:05] <mpt> One day, determining that will require typing "tr" into the tag field
[09:25] <mdke> hi all. is it possible for you guys to reveal someone's email address on a private basis where that doesn't appear on their lp page?
[09:25] <mdke> someone would like to contact a particular user about edits they have made on the documentation wiki, but they have no apparent contact details
[09:27] <mdke> kiko, SteveA ?
[09:29] <eXtazY> Hi
[09:29] <eXtazY> Well i have a problem
[09:29] <eXtazY> I live in lithuania
[09:29] <eXtazY> How do i know my postal code(zip)?
[09:30] <eXtazY> I can't find anywhere
[09:30] <kiko> eXtazY, both BjornT and SteveA know a lot about lithuania. I'm sure you can ask your post office for it.
[09:30] <eXtazY> Aaok
[09:30] <eXtazY> Ok*
[09:30] <eXtazY> Thanks
[09:30] <eXtazY> Ill try
[09:41] <BjornT> eXtazY: http://www.post.lt/lt/?id=316
[09:41] <eXtazY> Yeah :)
[09:42] <kiko> thanks BjornT
[09:43] <mdke> this channel does everything!
[09:43] <kiko> mdke, your pancakes and maple syrup will be right up
[09:43] <mdke> mind reading too?
[09:43] <mdke> whoa, these LP guys rock
[10:15] <ubotu> New bug: #125634 in malone "Disabled facets are still accessable for projectless projects" [Undecided,New]  https://launchpad.net/bugs/125634
[10:30] <ubotu> New bug: #125637 in launchpad "Replace MockLoggers in tests with zope utilities" [Undecided,New]  https://launchpad.net/bugs/125637


[07:50] <kjackal> admcleod: yes I saw your comments on Mahout
[07:50] <admcleod> kjackal: cool! :)
[07:50] <kjackal> do you think the execution time was acceptable?
[07:51] <admcleod> hmmm it seemed ok yes
[07:51] <kjackal> ok, cool
[07:51] <admcleod> but it would still be preferable to have a non-hdfs non-yarn smoke test
[07:52] <kjackal> agreed
[07:52] <kjackal> I initialy thought that the localhost target was depricated for Mahout, but i was wrong
[07:53] <admcleod> and there are several references to recommender algorithms that dont require hdfs
[07:53] <kjackal> there are some algorithms that you can run localy
[07:53] <admcleod> yep
[07:53] <kjackal> really?
[07:53] <kjackal> It could be an easy fix then
[07:53] <kjackal> ok, so! My plan is finish Kafka, and then either Mahout of HBase depending on the feedback i get from you
[07:54] <admcleod> kjackal: this one for example: https://mahout.apache.org/users/classification/twenty-newsgroups.html
[07:54] <kjackal> Nice! I will try to refactor this
[07:55] <kjackal> this=action+amulet
[08:01] <admcleod> kjackal: cool
[08:02] <admcleod> kjackal: https://mahout.apache.org/users/misc/testing.html
[08:04] <kjackal> admcleod (or anyone else): I was looking at flannel yesterday.  https://jujucharms.com/u/hazmat/flannel/trusty/1 I was trying to make a monster VM from smaller ones. Have you seen this before. Wouldn't be great if there was an option on the manual provider to provision lxc containers inside machines you give him?
[08:07] <admcleod> kjackal: pretty cool although i dont understand your last sentence
[08:07] <admcleod> kjackal: https://github.com/apache/mahout/blob/b25a70a1bc6b9f8cb6c89947e0eaba5588463652/mr/src/test/java/org/apache/mahout/driver/MahoutDriverTest.java
[08:07] <kjackal> You know how you have the manual provider and you manually give the machines you have access to
[08:08] <kjackal> then if you deploy something it gets deployed to that machines, right?
[08:08] <admcleod> kjackal: right
[08:09] <kjackal> What if you could tell the manual provider to spawn lxc containers inside the manualy provided machines
[08:09] <kjackal> based on a round robin or whatever other policy
[08:09] <kjackal> What happened? did we move to IPv6?
[08:10] <admcleod> kjackal: i see, right
[08:10] <kjackal> admcleod: http://pastebin.ubuntu.com/17392595/ look at zkb
[08:11] <admcleod> kjackal: what cloud is that?
[08:11] <kjackal> local with lxc on juju 2.0 deploying apache-zookeeper
[08:12] <admcleod> oh, somethings up with your lxc then
[08:12] <kjackal> next deployment got IPv4 !!!
[08:12] <admcleod> logs please
[08:13] <kjackal> I wouldn't dare!
[08:13] <kjackal> Ahhh ok only because its you!
[08:16] <kjackal> admcleod: http://pastebin.ubuntu.com/17392643/
[08:18] <admcleod> kjackal: if you ssh into it does it actually have an ipv4 address aswell?
[08:20] <kjackal> admcleod: looks legit http://pastebin.ubuntu.com/17392669/
[08:21] <admcleod> kjackal: so, if the others have ipv6 also, seems like juju displaying the wrong address
[08:22] <kjackal> yes, probably this
[08:25] <admcleod> kjackal: https://bugs.launchpad.net/juju-core/+bug/1574844
[08:25] <mup> Bug #1574844: juju2 gives ipv6 address for one lxd, rabbit doesn't appreciate it. <conjure> <juju-release-support> <landscape> <lxd-provider> <juju-core:Won't Fix> <rabbitmq-server (Juju Charms Collection):Fix Released by james-page> <https://launchpad.net/bugs/1574844>
[08:28] <kjackal> hm.... I must be running an old juju version
[08:28] <kjackal> beta7
[08:28] <kjackal> there should be at least a beta8, right?
[08:31] <admcleod> kjackal: yes
[08:36] <kjackal> admcleod: WHER
[08:37] <kjackal> admcleod: where you involved in the IP issues we were seeing because of java?
[08:37] <kjackal> I think kafka could be affected by this: http://stackoverflow.com/questions/1881546/inetaddress-getlocalhost-throws-unknownhostexception
[08:37] <kjackal> admcleod: did we fix this with upgrading to java8?
[08:37] <admcleod> kjackal: i am aware of a few different issues re dns and hostnames and java 7
[08:38] <admcleod> kjackal: is this on lxc also?
[08:38] <kjackal> yes, lxc juju 2.0
[08:38] <Yash> Hello
[08:38] <Yash> I'm facing a problem.
[08:38] <Yash> 2016-06-16 08:36:27 DEBUG juju.api apiclient.go:500 error dialing "wss://[fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070/model/3923551f-dcf9-4ca8-8b32-dc010722721b/api", will retry: websocket.Dial wss://[fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070/model/3923551f-dcf9-4ca8-8b32-dc010722721b/api: dial tcp [fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070: getsockopt: connection refused [14:07] <Yash> How to solve this?
[08:38] <Yash> I rebooted my machine many times with no luck
[08:39] <Yash> Ubuntu 16.04 and juju 2.0 beta
[08:39] <admcleod> kjackal: right well we came across the problem on joyent since the default joyent resolves are googles public nameservers, so you can't use InetAddress.getLocalHost() to resolve the local hostname (for example)
[08:39] <kjackal> http://pastebin.ubuntu.com/17392798/
[08:39] <admcleod> kjackal: yeah, cos theres no DNS
[08:40] <Yash> @kjackal are you suggesting anything to me? or other problem?
[08:42] <kjackal> hi Yash I think we have separete problems :)
[08:42] <Yash> ok
[08:43] <admcleod> Yash: how did you bootstrap the environment?
[08:44] <admcleod> Yash: and what cloud/substrate is it?
[08:44] <Yash> juju bootstrap lxd-test localhost
[08:44] <Yash> https://jujucharms.com/docs/devel/getting-started
[08:44] <Yash> It was working fine
[08:44] <Yash> I installed many openstack components
[08:45] <Yash> then pending machine problem.. so I removed those machine and services and rebooted whole machine
[08:45] <Yash> Now I'm trying on desktop
[08:46] <Yash> SIngle machine with 24 GB ram and + 4TB
[08:46] <admcleod> can you actually telnet to fd4f:23ae:5d73:5c67:216:3eff:febc:8b38 port 17070? is that port open on that ip?
[08:46] <Yash> I found out if we can restart machine 0 it would resolve problem
[08:47] <Yash> but juju 2.0 changed like there is no /var/lib/juju dir
[08:47] <Yash> instead lxd and lcxfs
[08:48] <Yash> which contains all of it
[08:48] <admcleod> babbageclunk: hello!
[08:48] <babbageclunk> admcleod: hi!
[08:48] <babbageclunk> admcleod: uh oh
[08:48] <admcleod> Yash: unfortunately my experience with juju 2.0 and networking isnt great.. however..
[08:48] <Yash> Any help?
[08:48] <admcleod> ;)
[08:48] <admcleod> Yash: maybe babbageclunk can help ;)
[08:49] <Yash> @babbageclunk can you please suggest anything?
[08:49] <babbageclunk> Yash: so, you're trying to reboot machine 0 but can't?
[08:50] <Yash> Yea
[08:50] <Yash> Trying as per stackoverflow to solve issue
[08:50] <Yash> but since 2.0 changed this also
[08:50] <Yash> so can't find proper way
[08:50] <babbageclunk> Yash: can you ssh into the machine with "juju ssh 0"?
[08:51] <Yash> juju is in hang stat so I can't
[08:51] <babbageclunk> And it's all deployed on lxd?
[08:51] <Yash> Yes
[08:52] <babbageclunk> How about rebooting the container with lxc restart?
[08:52] <Yash> How can I do?
[08:53] <Yash> I've 2 weeks exp only
[08:53] <babbageclunk> :)
[08:53] <babbageclunk> I'm pretty new here too.
[08:53] <Yash> ok :)
[08:54] <babbageclunk> Try "sudo lxc restart <container name>"
[08:54] <babbageclunk> you can get the container name from "sudo lxc list"
[08:54] <babbageclunk> It should come back up pretty quickly.
[08:55] <babbageclunk> (Assuming there's not some other problem.)
[08:55] <Yash> ok Let me try..Thanks
[08:58] <babbageclunk> Any luck?
[09:08] <Yash> nope
[09:08] <Yash> Its just restarted but same problem
[09:08] <Yash>  DEBUG juju.api apiclient.go:500 error dialing "wss://[fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070/model/3923551f-dcf9-4ca8-8b32-dc010722721b/api", will retry: websocket.Dial wss://[fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070/model/3923551f-dcf9-4ca8-8b32-dc010722721b/api: dial tcp [fd4f:23ae:5d73:5c67:216:3eff:febc:8b38]:17070: getsockopt: connection refused [14:07] <Yash> How to solve this?
[09:09] <Yash> Worse..I can't use juju so don't know what is problem and how to solve it
[09:10] <Yash> I'm not using MAAS as it's optional for single machine. Right?
[09:11] <Yash> @babbageclunk anything you may suggest?
[09:12] <babbageclunk> Yash: Sorry, on the phone at the moment, davecheney's comment in #juju-dev might be worth a look
[11:04] <admcleod> i want to constrain a particular service deployed in an amulet test has an SSD (i only care about running it on AWS at the moment) - how do i achieve that?
[13:05] <magicalt1out> just told the guy who owns the other 50% of my company I'm leaving to work for NASA full time..... talk about dumping a spanner in the works.....
[13:12] <rick_h_> magicaltrout: congrats?
[13:14] <magicaltrout> thanks rick_h_ , one of those weird things, I don't really want to quit, or at least go very part time
[13:14] <magicaltrout> but how often do you get a job offer from NASA to work on big data stuff?
[13:14] <magicaltrout> especially when you live in the UK
[13:15] <kjackal> nice! you will see realy big data there!
[13:15] <kjackal> true big data!
[13:17] <lazyPower> no doubt right? all that historical sensor and probe data to churn through
[13:17] <lazyPower> magicaltrout - im not a data scientist, but the prospects of that are making me jealous
[13:17] <kjackal> What software stack do they have over there in NASA, magicaltrout? In house?
[13:19] <magicaltrout> a lot of Hadoop, SciSpark and IPython/Zeppelin at the mo kjackal
[13:19] <magicaltrout> of course depends what area you work in I guess
[13:20] <kjackal> magicaltrout: nice!
[13:21] <magicaltrout> i'm gonna charm up scispark at some point over the next few months
[13:21] <magicaltrout> I did a big data demo in San Diego last week
[13:21] <magicaltrout> the guys who were there loved it
[13:23] <kjackal> :) thank you magicaltrout
[13:24] <magicaltrout> sadly for the project I joined we're too late for Juju so I'm introducing them to docker
[13:24] <magicaltrout> 1 step at a time I guess
[13:33] <kjackal> magicaltrout: what about going to space? any progress there? :)
[13:36] <magicaltrout> the mrs banned that career move a long time ago
[13:49] <admcleod> magicaltrout: congrats
[14:34] <admcleod> so...
[14:34] <admcleod> i want to constrain a particular service deployed in an amulet test so that it has an SSD (i only care about running it on AWS at the moment) - how do i achieve that?
[14:46] <aisrael> admcleod: Pretty sure you can specify that via constraint. Let me see if I can find an example
[14:46] <admcleod> aisrael: thanks :}
[14:51] <aisrael> admcleod: http://pastebin.ubuntu.com/17397999/
[14:51] <aisrael> basically, you have to force it to one of the aws instance types that has ssd backing
[14:52] <admcleod> aisrael: ah yeah cool thatll do, thanks
[15:42] <petevg> lazyPower: I'm review queuing, and have a question about https://bugs.launchpad.net/charms/+bug/1587641, which you +1ed a week ago. It's still in a "new" state. Can I move it to "fix released"?
[15:42] <mup> Bug #1587641: Update for MariaDB charm <Juju Charms Collection:New> <https://launchpad.net/bugs/1587641>
[15:42] <lazyPower> petevg - oh indeed! i missed closing the bug, sorry about that
[15:43] <petevg> No worries.
[15:44] <petevg> lazyPower: I closed out the bug. (Learning how to do so was useful :-) )
[15:44] <lazyPower> \o/ glad my mistake was a learning experienc e:D
[15:44] <lazyPower> thats the best kind of mistakes to make
[16:46] <balalaika> What's the best way to expose a charms IP to the user?
[16:46] <balalaika> I'm deploying gitlab and I want them to be able to point their domain to the address.
[16:48] <balalaika> I'm aware of unit-get public-address juju helper method.
[16:49] <balalaika> Should I just document in the README that they should inspect the deployed service via CLI?
[17:17] <Prabakaran> For my other charm requirement I had to write this particular template http://paste.ubuntu.com/17332169/ in bash. <lazypower> could you please help me on this?. And also I have to copy some JAR files to mysql charm container where it is installed? Is it possible for me to do it?
[17:18] <lazyPower> Prabakaran - ok so your charm layer is no longer in python? its in bash now?
[17:19] <Prabakaran> I am asking this for other charm which i am developing IBM Platform RTM
[17:19] <lazyPower> ah, ok. I was confused on why the last minute language change
[17:20] <Prabakaran> I have noted in my learning section what ever u had sent it tome
[17:20] <Prabakaran> it was helpful
[17:20] <Prabakaran> but need ur help in bash alos
[17:28] <lazyPower> Prabakaran http://paste.ubuntu.com/17404518/
[17:28] <lazyPower> my bash reactive is questionable at best, fix syntax where applicable
[17:31] <Prabakaran> ya sure.. Thanks for your immediated help on this <lazypower>.. i will implement this.... but adding to that I have to copy some JAR files to mysql charm container where it is installed? Is it possible for me to do it?
[17:32] <lazyPower> It is, but i'm unclear on what you'll do after you've sent them to the mysql unit. jar's aren't very helpful on their own right? you'll need to not only copy them but also action on them right? such as run the jar files in a JRE
[17:33] <lazyPower> so right while you need to copy them, it seems that what you'll really want to do, is add *another* relationship and interface to mysql specific to your use case, so you can take those actions once you've received the jar files. Ohtherwise you've put bits on disk and cant do anything with them
[17:33] <lazyPower> kwmonroe - does that sound about right? ^
[17:35] <lazyPower> Prabakaran - before you go off to implement htat, i'd like to clarify with kwmonroe as he's got some familiarity with the goals of your charm(s)
[17:36] <kwmonroe> Prabakaran: what jars do you need to copy to the mysql unit?
[17:38] <kwmonroe> if they are something that others could use, i'd suggest opening a feature req against mysql to control the inclusion of those jars as a config opt in mysql.
[17:40] <kwmonroe> or set up a shared filesystem that both mysql and your charm support (nfs, etc).. you could stick the jars out there, but then would probably need to tell mysql to use that shared location as a 'classpath' (if that's even a thing for mysql)
[17:40] <Prabakaran> Sorry i was wrong.. there was a tar file which has some *.sql files which i need to copy to the container and run all those...but as per recent chat from <lazypower> we can do this with mysql-client wherein we dont need to copy those tar--->*.sql file
[17:41] <Prabakaran> but i asked this for my understanding
[17:42] <kwmonroe> right - no need to copy *.sql files over to the mysql host.  you can execute any *.sql against the mysql charm using the 'mysql -h host -u user -p password <command>' like lazyPower had in that earlier pastebin
[17:42] <beisner> lutostag, jcastro - re: the jenkins charm ... is the source of truth for dev @ https://github.com/jenkinsci/jenkins-charm ?    i ask because of this proposal in the queue:  https://code.launchpad.net/~lutostag/charms/trusty/jenkins/xenial/+merge/296222
[17:42] <lazyPower> oooo
[17:42] <lazyPower> beisner - good catch on that one
[17:43] <lazyPower> i'm pretty sure we did move source of truth to upstream
[17:45] <beisner> lutostag, ps tons of thx for fixing up jenkins on X.  that was on my oh-shoot list o' stuff to do.
[17:48] <lutostag> beisner: ah, I had no idea about that
[17:49] <lutostag> I can do a PR through github if that is preferred
[17:49] <beisner> just looked back to confirm.  if ya blinked, you might have missed it.  https://lists.ubuntu.com/archives/juju/2016-February/006611.html
[17:50] <lutostag> indeed, I'll PR there tomorrow/next week
[17:51] <beisner> lutostag, thx again sir :)
[18:03] <Prabakaran> Thanks kevin and lazypower for the explaination
[18:03] <Prabakaran> I have small doubt in mysql charm and its interface.
[18:03] <Prabakaran> Here mysql charm is non-layered charm and it would have exposed hostname, port, username and password using relation-set command in relation hook but mysql charm should set/pass those values to the mysql interface like how we use relation-call in the layercharm to interface. Can you please explain me the flow how it works?
[18:06] <beisner> lazyPower, so i wonder:  what does the get-it-into-the-cs story look like for jenkins @ its new home, and what should become of the lp branch?
[18:06] <lazyPower> beisner - we've been dropping lp branches like flies post ingestion kill-off
[18:07] <lazyPower> beisner - get it into the cs right now depends on a manual review and push by a ~charmer until we launch the new rev q, which is still pending iirc
[18:07] <lazyPower> beisner - so if you've got a hot item fix, lmk. otherwise, I'd like to wait for the revq to launch so we have a breadcrumb trail of whats happened.
[18:07] <lazyPower> but thats just me :)
[18:07] <lazyPower> i'm sure there are other opinions out there
[18:08] <beisner> lazyPower, ok.  it may be worth going ahead and doing a charm push from the gh repo and setting the homepage and bugs url metadata so that the cs points to the right place, then nixing the lp branch.  whaddaya say?
[18:09] <lazyPower> beisner - do you have good test run output for me so i get the warm fuzzies?
[18:10] <lazyPower> i can update the store meta no problem, but i want test results before i push :)
[18:10] <beisner> lazyPower, i don't have anything hammering on that charm's dev flow atm.  and... i think it needs tests to be added.
[18:10] <lazyPower> beisner - tests became a mandatory requirement as of the trusty series :\
[18:10] <lazyPower> i cannot in good faith push a charm without tests
[18:11] <beisner> lazyPower, oh it does have these: https://github.com/jenkinsci/jenkins-charm/tree/master/tests
[18:11]  * beisner is with ya lazyPower
[18:11] <lazyPower> LOL
[18:11] <lazyPower> i wrote these tests
[18:11] <lazyPower> forever ago
[18:11] <beisner> welcome baaaaack
[18:11] <lazyPower> https://github.com/jenkinsci/jenkins-charm/blame/master/tests/100-deploy-trusty#L21
[18:12] <lazyPower> oh man, thats tricky
[18:12] <lazyPower> its deploying a precise series charm to validate leader/follower
[18:13] <lazyPower> beisner - i suggest we pin this for tomorrow, and fold in marco/jcastro if they're around. Otherwise lets vet the charm and make sure its ready for a release
[18:13] <lazyPower> will you have 20/30 minutes tomorrow to do so? we can pair and knock it out quickly
[18:13] <lazyPower> at least the boolean "yes we can push" portion
[18:14] <beisner> lazyPower, yep, no pressure here.  just taking a spin through the queue to see what is in my familiarity zone.  thx for your help.
[18:14] <lazyPower> np beisner, happy to help
[18:14] <lazyPower> beisner - did you see my post to the list re: tags in github?
[18:14] <lazyPower> beisner - as you do a lot of test/release planning, i'd love your feedback on that
[18:16] <beisner> lazyPower, i think that's a good value for projects that have a github dev focus.
[18:17] <beisner> lazyPower, for the openstack charms, github repos are just a sync from cgit @ openstack upstream, and i'm not sure what our tagging abilities are.
[18:17] <lazyPower> tags are independent of github, they are a git native primitive
[18:17] <beisner> we've begun injecting a repo-info file during our build/push/publish automation.  ie.  https://jujucharms.com/u/openstack-charmers-next/neutron-gateway/xenial
[18:17] <lazyPower> so you can tag and push to remote if you have write access to the repository
[18:17]  * lazyPower looks
[18:18] <beisner> lazyPower, that solves one of our big challenges:  "Joe is in possession of a charm.  we don't really know where it came from."
[18:18] <lazyPower> ah man i like that
[18:18] <lazyPower> the repo-info file
[18:18] <lazyPower> its exactly what i would have expected from the revision file
[18:18] <lazyPower> https://api.jujucharms.com/charmstore/v5/~openstack-charmers-next/xenial/neutron-gateway/archive/repo-info  <- that thing
[18:19] <beisner> that's the one
[18:19] <lazyPower> have you already built tooling around this?
[18:19] <lazyPower> and if so, how much of it is specific to the openstack setup?
[18:19] <beisner> we just launched openstack's rendition of layer ci.    it'll be specific in that it is centered around gerrit.
[18:20] <beisner> ie. no git pull requests
[18:20]  * lazyPower snaps
[18:20] <lazyPower> thats such a tease beisner
[18:20] <lazyPower> you show me what i'm looking for in another format, and then pull it away D:
[18:20] <beisner> but yeah, now we can put up a review, tests fly in all sorts of directions, a reviewer can approve and land with a vote, then it pushes/published to CS.
[18:21] <lazyPower> right, makes sense for your use case
[18:21] <lazyPower> ok i'll noodle this s'more and wait for feedback on the ml post, i feel like there's a big gap i'm not seeing in that process though.
[18:21] <lazyPower> and i'm going to regret doing it once i start
[18:22] <beisner> lazyPower, anyway +1 if we can tag revs with cs refs, that will be sweet indeed
[18:22] <beisner> i already had someone ask if we could do that, and owe a bit of research to the idea and whether our tags will survive the flows and syncs through systems outside our direct control.
[18:23] <beisner> i do know this:  we don't have perms to directly tag @ the cgit repos.
[18:23] <beisner> only the bots do
[18:23] <beisner> and a few core/root infra team peeps
[18:23] <lazyPower> ok, so you're mirroring that cgit right?
[18:23] <lazyPower> which means you can carry meta information in your fork
[18:24] <beisner> we aren't mirroring it though.  it happens for anything in https://github.com/openstack/*
[18:24] <beisner> no fork
[18:24] <lazyPower> ah
[18:24] <lazyPower> what a funky setup
[18:24] <lazyPower> i kind of like that its locked down though
[18:24] <beisner> it's a bit weird.  if one were to raise a pr against the gh repo, it will get nack'd and squashed by a bot
[18:25] <lazyPower> as it should if there's a gerrit review process
[18:25] <beisner> yep, there is exactly one way to land a bit. :)
[18:27] <beisner> so it'd be analogous to an enterprise operating their own private internal cgit systems, but also making those repos avail via github for one-way consumption.  a bit funky, yah.
[19:40] <bdx> hey whats up everyone? Whats the reccomended best practice for including pip deps in a charm?
[19:41] <bdx> recommended*
[19:41] <bdx> i can spell
[19:43] <bdx> or, in a layer
[19:43] <bdx> my bad
[19:43] <rick_h_> bdx: so with juju 2.0 I'd say to put together an offline cache of pip deps and zip that as a juju resource
[19:43] <rick_h_> bdx: but maybe otherw siwll have other suggestions as well
[19:44] <bdx> rick_h_: thanks
[19:45] <bdx> rick_h_: for example -> https://github.com/DarkHorseComics/layer-whelp/blob/master/lib/charms/layer/whelp_utils.py#L5
[19:45] <rick_h_> bdx: hmm, so that's for a charm. For a layer, that you want to reuse it's more interesting
[19:47] <stub> bdx: If you are writing a reactive charm, embed them by creating a wheelhouse.txt file in your layer.
[19:47] <rick_h_> heh that's what I was looking for. I knew they had some wheel setup for the layers
[19:47] <stub> https://github.com/juju-solutions/layer-basic/blob/master/wheelhouse.txt
[19:48] <huckst> The command `juju destroy-controller` hangs.
[19:48] <huckst> 2.0-beta8-xenial-amd64
[19:48] <bdx> stub: nice, so any layer can define a wheelhouse.txt and those deps will be picked up?
[19:49] <rick_h_> huckst: can you ssh to the controller still?
[19:49] <rick_h_> huckst: anything in those logs that might prove helpful? Any output to judge where/why it's hanging?
[19:49] <bdx> thats what I thought .... but couldn't find any examples of subsequent layers using this so I wasn't sure
[19:49] <bdx> stub, rick_h_: thx
[19:49] <lazyPower> bdx - dont ilsten to rick. use the wheelhouse.
[19:50] <rick_h_> yea, I was thinking of a string of app deps for a charm
[19:50] <rick_h_> as a resource, I missed the layer specific bit there
[19:50] <huckst> No machine to ssh to.
[19:50] <stub> bdx: I believe so, but haven't used it in anger (I'm still pulling debs from ppas)
[19:51] <huckst> I had setup the gce google controller and the lxd localhost controller. Started working on the lxd controller, forgot about the gce controller until now.
[19:51] <huckst> Then when I went to start using the gce controller, nothing. So I'm trying to drop and re-bootstrap.
[19:51] <rick_h_> huckst: ok, so which one did you destroy-controller on?
[19:51] <huckst> gce google
[19:51] <lazyPower> bdx - i use the wheelhouse dependency chain quite a bit
[19:51] <lazyPower> bdx https://github.com/juju-solutions/layer-docker/blob/master/wheelhouse.txt  - as an example
[19:52] <rick_h_> huckst: ok, and the instances are all shut down?
[19:52] <rick_h_> huckst: if you look in the gce panel? so it ran some output during destroy?
[19:52] <rick_h_> can you pastebin the output?
[19:52] <huckst> Nothing ran in the gce panel.
[19:53] <rick_h_> I understand nothing ran there, but if you had a GCE controller then you had an instance running on the GCE cloud and it would show in the GCE control panel
[19:53] <huckst> Correct. I can confirm it had started weeks ago and was successful at doing somethings. But nothing recently.
[19:55] <jhobbs> To make a new team in the charmstore, do I need to do anything other than create the team in launchpad?
[19:55] <magicaltrout> nope
[19:56] <jhobbs> ok, guess it takes a while to sync or something
[19:58] <magicaltrout> where jhobbs, in charm tools?
[19:58] <bdx> lazyPower: niccceeeee
[19:59] <magicaltrout> you have to log out of literally everything and log back in again
[19:59] <magicaltrout> charm tools, jujucharms.com etc
[19:59] <lazyPower> jhobbs - what magicaltrout said, its a known bug. it only syncs groups on login.
[19:59] <jhobbs> magicaltrout: yeah i created a group on launchpad about 15 minutes ago, logged out of charm tools and logged back in and it won't let me push
[19:59] <lazyPower> bdx - hope that gets you unblocked, lmk if you need any further help
[19:59] <jhobbs> ok
[19:59] <magicaltrout> i like to think of it more as an annoing feature ;)
[20:00] <jhobbs> i will log out of more stuff
[20:00] <jhobbs> thanks
[20:00] <lazyPower> magicaltrout - six of  one, half dozen of the other ;)
[20:00] <magicaltrout> jhobbs yeah website and everything
[20:00] <rick_h_> yes, once SSO can do the username stuff we can look at actually disconnecting from LP there
[20:00] <magicaltrout> even then it doesn't always work :)
[20:04] <stub> jhobbs: I think you need to relogin to the web interface, not charm tools
[20:18] <jhobbs> yay, working now, thanks everyone
[20:18] <magicaltrout> \o/
[20:19] <arosales> jhobbs: not intuitive at all, but the UI folks are working to make that better
[20:24] <huskc> I was wrong about the gce google controller hung issue. (new to gce) After navigating to the correct dashboard I saw a juju instance running.
[20:25] <huskc> The logs output had an ongoing 'unable to connect to API' error.
[20:27] <huskc> I manually deleted the gce (juju bootstrap) instance, but juju still hangs on destroying the controller locally.
[20:28] <huskc> It doesn't exist, so shouldn't the CLI `juju destroy-controller gce-devenv` just flush what's configured locally?
[20:35] <huskc> I worked around the CLI hangup by manually remove the 'dead' gce-controller from all juju config in ~/.local/share/juju/*
[20:36] <huskc> Now I can successfully re-bootstrap the google cloud.
[20:36] <huskc> It's nice that the config is just YAML and easily modified (and not some SQLite db). ;)
[20:54] <valeech> Is this a good place to get help with this error: “ERROR cannot resolve URL "cs:maas-region": charm or bundle not found” I am trying to deploy MAAS HA with juju following this guide https://maas.ubuntu.com/docs2.0/ha.html. I have a fresh install of xenial and juju 2.0 beta 7.
[21:03] <magicaltrout> valeech: it is, but i've never used MAAS so I'm not the person to ask :)
[21:05] <valeech> magicaltrout: understood. I am pretty new to juju myself. I am wondering if the bundle name changed in some fashion.
[21:05] <magicaltrout> thats easy enough to find out i would hope
[21:06] <magicaltrout> https://jujucharms.com/q/?text=maas-region
[21:07] <magicaltrout> i have no clue about the tutorial but there doesn't seem to be a charmers charm there
[21:07] <magicaltrout> so
[21:07] <magicaltrout> juju deploy cs:~maas-maintainers/trusty/maas-region-3
[21:07] <valeech> excellent! Thanks so much!
[21:07] <magicaltrout> that looks like a likely solution
[23:18] <arosales> nice find magicaltrout, it looks like maas-region is not a recommended charm and thus one would need to prefix the username as suggested
[23:19] <arosales> valeech: thanks for the feedback I'll file a bug on the maas docs
[23:25] <valeech> arosales: where are you seeing that maas-region is not a recommended charm?
[23:28] <arosales> valeech: a recommended charm would have a flat name space like https://jujucharms.com/maas-region/
[23:28] <arosales> and 'juju deploy maas-region' would just work
[23:28] <arosales> in this cae it doesn't as it hasn't been through the review process and thus not mark as recommended
[23:29] <valeech> arosales: makes sense. thanks for the explanation
[23:29] <arosales> it very well may be a good working charm the MAAS folks would like users to use judging by the name maas-maintainers, but that explains why "juju deploy maas-region" didn't work per the MAAS docs
[23:29] <arosales> valeech: happy deploying
[23:30] <valeech> thanks@!
[23:30] <valeech> !
[23:32] <arosales> valeech: and welcome to the juju community :-) If you don't find an answer here askubuntu.com and the juju mailing list (https://lists.ubuntu.com/mailman/listinfo/juju) are also good resources
[23:32] <valeech> Great! thanks.
[23:33] <valeech> I was having some weird issues on 2.0beta7 so I blew it away and spun 2.0beta9. Now it’s getting even more strange
[23:34] <valeech> I can’t seem to deploy any apps to my machines. I have 2 machines added to a manual cloud and the juju status shows them as started but I keep getting this error on all charms I load:
[23:35] <valeech> cannot assign unit "wordpress/0" to machine: cannot assign unit "wordpress/0" to new machine or container: cannot assign unit "wordpress/0" to new machine: use "juju add-machine ssh:[user@]<host>" to provision machines
[23:44] <arosales> valeech: to confirm you are using manual provider, correct?
[23:44] <arosales> if so can you pastbin the output of juju status
[23:44] <valeech> juju bootstrap maas manual/<IP_ADDRESS>
[23:44] <valeech> like that?
[23:44] <arosales> I think you just need to specify which unit you want to deply the charm to with --to
[23:45] <arosales> valeech: what does `juju status` currently return?
[23:46] <valeech> http://pastebin.com/93RGJfCw
[23:47] <valeech> juju runs on one VM, and mass2 and maas3 are 2 other VMs
[23:48] <lazyPower> valeech - i dont believe that wordpress is supported on xenial by the charm.
[23:48] <valeech> I am batting a 1000 :)
[23:48] <arosales> valeech: try 'juju deploy --to 0 wordpress wordpress2
[23:49] <lazyPower> valeech - i see your enlisted machines are series: xenial. Juju didn't tell you a very helpful error message that its due to not having a series allocated the charm can consume :\  but thats the issue here
[23:49] <arosales> lazyPower: one can still deploy trusty images though
[23:49] <lazyPower> arosales true, but valeech will need to manually provision on ein maas and add it to his juju env, theres no magic here since its the manual provider
[23:49] <lazyPower> s/his/their/
[23:49] <arosales> lazyPower: ah yes, but they --to would manually place it on the xenail machine
[23:49] <lazyPower> arosales not if its series: trusty, you cant force smash a series difference
[23:50] <arosales> lazyPower: well I think valeech is just trying to test his setup
[23:50] <lazyPower> i do get what you're saying tho :)
[23:50] <arosales> valeech: perhaps try, "juju deploy --to 4 ubuntu"
[23:50] <arosales> and see if at least you can get that to deploy
[23:50] <arosales> lazyPower: that should work, right?
[23:51] <lazyPower> arosales - it should, yeah
[23:51] <arosales> and earlier when I said "--to 0" juju would have balked at that because machine 0 is reserved, so apologies there
[23:52] <valeech> arosales - it did balk I will try —to 4
[23:52] <bdx> while we are on wordpress ....
[23:52] <valeech> results from "juju deploy --to 4 ubuntu”: ubuntu/0     unknown   idle   4               maas3
[23:52] <bdx> we need a wordpress charm reform effort initiated
[23:53] <arosales> here are the xenial charms available: https://jujucharms.com/store?type=charm&series=xenial
[23:53] <lazyPower> look at those beats!
[23:53] <lazyPower> that just landed today :D
[23:53] <arosales> lazyPower: :-)
[23:53] <arosales> valeech: what is your current juju status post that deploy command?
[23:54] <bdx> lazyPower: Nice!
[23:54] <arosales> post that ubuntu deploy command
[23:54]  * arosales waves to bdx
[23:54] <valeech> so there’s a juju-gui charm for xenial but isn’t GUI in juju 2.0 included rendering the need for a charm useless?
[23:54] <lazyPower> bdx - packetbeat landed too,  juju deploy cs:~containers/packetbeat  -- it needs review for promulgation but its done :)
[23:54] <bdx> arosales: whats up!
[23:54] <bdx> lazyPower: so sick! pumped
[23:54] <lazyPower> valeech - correct, juju 2.0-beta6 started shipping with the juju-gui
[23:54] <arosales> valeech: in 2.0 the juju gui comes baked into the controller :-)
[23:54] <valeech>  juju deploy --to 4 ubuntu
[23:54] <valeech> Added charm "cs:ubuntu-0" to the model.
[23:54] <valeech> Deploying charm "cs:ubuntu-0" with the default charm metadata series "xenial".
[23:54] <arosales> just issue "juju gui" and you get it out of the box
[23:55] <arosales> valeech: looking good
[23:55] <lazyPower> bdx - glad you're excited :) Gimme some bugs, i know they're in there
[23:55] <arosales> bdx: finally a maas expert in here :-)
[23:55] <valeech> from juju status:
[23:55] <valeech> ubuntu     unknown  false    jujucharms  ubuntu     0    ubuntu
[23:56] <bdx> lazyPower: nice work seriously
[23:56] <bdx> lazyPower: did you ever figure out the geo_ip?
[23:56] <lazyPower> bdx thanks man :)
[23:56] <lazyPower> i did, but didnt ship with it, because the db is so old
[23:56] <lazyPower> i'd like to engage with elastic to get something more recent in there
[23:56] <bdx> ahh
[23:57] <bdx> arosales: ha - I hope to be
[23:57] <lazyPower> i've got a little video i'm working on to push on my social channels, once its done i'll ship it over to elastic as the intro to the work done, and see if they're interested in collaborating/upstreaming the charms
[23:57] <arosales> valeech: could I get a full pastbin output of juju status, I lost the context if that was machine or application output
[23:57] <valeech> sure..
[23:57] <bdx> arosales: I only have 5 maas deploys
[23:57] <arosales> bdx: only :-)
[23:58] <valeech> http://pastebin.com/DkZ37RT7
[23:58] <bdx> lazyPower: thats a great idea
[23:59] <bdx> valeech: yea - 'juju deploy maas-region' just works if you have the needed configs set