[12:09] <shaym_> hi, is the internal myth player , mplayer? I'd like to turn on volume normalization


[08:06] <mantiena> hello all
[08:08] <mantiena> Now Lauchpad forbids to change (edit) distribution details (description, summary, etc., look at https://edge.launchpad.net/baltix/+edit ), maybe someone knows why ?
[08:12] <mantiena> mpt: hi, are you soyuz developer ?
[08:12] <mpt> mantiena, no, but I'm seeing all the Soyuz developers in 38 minutes
[08:12] <mpt> Why do you ask?
[08:13] <leoquant> ah uds?
[08:14] <mantiena> mpt: because of bug I've just told in this channel :)
[08:14] <mpt> oh, right
[08:14] <mpt> mantiena, is this a new problem?
[08:15] <Hobbsee> mpt: he's the driver, so he should be able to...
[08:15] <Hobbsee> mpt: so, it must have happened after the intrepid opening, as there weren't problems reported then, iirc.
[08:17] <mpt> Why would Intrepid opening have anything to do with changing Baltix distribution details?
[08:17] <mpt> mantiena, do you remember when you last successfully changed the details?
[08:18] <mantiena> mpt: sorry, I don't remember :(
[08:19] <mantiena> AFAIK this year I didn't tried to change distribution details
[08:21] <mpt> works for me when I try it locally
[08:22] <Hobbsee> mpt: because they also changed ubuntu distro details, after the intrepid was created for them.
[08:22] <mantiena> I can tell the error message if you need
[08:23] <mpt> mantiena, sorry, I can't work it out myself
[08:23] <mpt> mantiena, please report a bug <https://bugs.launchpad.net/soyuz> with the error code
[08:25] <mpt> or maybe bigjools can help you
[08:25]  * bigjools hides
[08:29] <mantiena> bigjools: please unhide :)
[08:30]  * bigjools unhides!
[08:30] <bigjools> mantiena: what can I help you with?
[08:30] <mantiena> bigjools: Lauchpad forbids to change (edit) distribution details (description, summary, etc., look at https://edge.launchpad.net/baltix/+edit ) :(
[08:31] <bigjools> right, you have to be an admin to do that
[08:32] <mantiena> bigjools: but I was able to change the details some time ago
[08:32] <bigjools> hmm just a moment, let me check the exact permissions required
[08:36] <mantiena> bigjools: I'm main baltix distro developer
[08:37] <philn> hi
[08:38] <mantiena> hi philn
[08:39] <mantiena> I get this error message when I try to change distribution details:
[08:39] <mantiena> Now allowed here
[08:39] <mantiena> Not allowed here
[08:39] <mantiena> Sorry, you don't have permission to access this page
[08:40] <mantiena> mpt: I remember when I changed distribution details last time !!!
[08:41] <mantiena> this was this year, I've changed bug reporting guidelines
[08:41] <mantiena> maybe in April or March
[08:41] <bigjools> mantiena: are you logged in as "mantas" ?
[08:43] <mantiena> bigjools: yes, of course ;)
[08:48] <bigjools> mantiena: bear with me a moment, I am trying to re-create your problem
[08:51] <mantiena> bigjools: hehe, It would be better if you fix instead of re-creating ;)
[08:52] <bigjools> mantiena: thanks for your insight
[08:55] <mantiena> bigjools: :-P
[09:04] <bigjools> mantiena: it is a bug, can you please file a question on answers.launchpad.net/soyuz with the details of what you need changed and someone will look at it.  I will file a bug to fix this problem.
[09:08] <mantiena> bigjools: please tell me the bug number or subscribe me to that bug
[09:08] <bigjools> mantiena: I will subscribe you when I've entered it
[09:09] <mantiena> bigjools: thanks
[09:10] <bigjools> de rien
[09:52] <dhart> quick q: can a superproject's name be a bzr lp:name ? or should I rename projects + supperprojects?
[10:03] <philn> gmb: hi
[10:03] <gmb> philn: Hi.
[10:03] <gmb> philn: demo.lp.net should be okay for you to check things out on now.
[10:04] <gmb> philn: I'm ready to let let production import roll when you say so.
[10:06] <philn> great.. i'll ask ppl to check once more
[10:09] <cody-somerville> mpt, you're taking notes on the spit and polish session?
[10:09] <mpt> cody-somerville, yes, intrepid-spit-and-polish
[10:10] <cody-somerville> mpt, Excellent. I'd love to review them afterwards. I wish I could be in that session but I need to be in the live cd memory requirements as Xubuntu's live cd doesn't meet our hardware target currently.
[10:11] <mpt> cody-somerville, you can still watch the gobby doc
[10:11] <cody-somerville> Okay :)
[10:11] <mpt> (this discussion would belong better in #uds-desktop)
[10:29] <mantiena> bigjools: are you soyuz developer ?
[10:30] <bigjools> mantiena: yes
[10:34] <mantiena> bigjools: what you think about bug 211223
[10:34] <mantiena> shouldn't this bug to be assigned to soyuz ?
[10:35] <bigjools> mantiena: yes, it should, please do that
[10:40] <mantiena> bigjools: What you think about quick solution, proposed by Colin Watson for this long standing issue? He proposes to add the possibility to register a milestone that doesn't have a series yet, and to move milestone to the series once it's registered. See bug #201623 for more info.
[10:42] <bigjools> mantiena: you should talk to kiko about that, it's a managerial decision rather than a technical one
[10:45] <philn> is there a way to bring ubottu to a new channel?
[10:46] <mantiena> bigjools: maybe you know when kiko will be here ?
[10:46] <bigjools> mantiena: he's at UDS, he may come online later
[10:51] <thumper> dhart: branches are associated with projects, not superprojects (project groups), so the branches have project based names
[10:52] <dhart> thumper: thanks, that's what I thought. I should probably submit requests to rename the projects and superprojects in question
[12:54] <Hobbsee> philn: ask in #ubuntu-ops.
[12:57] <davmor2> Hello can I get some help please.  I setup ages ago a ~davmor2 which plugged into a dead hotmail account.  The account I actually use is ~davmor2-gmail.  Is there anyway I can transfer my davmor2-gmail to davmor2?  Also I still don't seem to have my email alias setup but was wondering if it was setup to my old account?
[12:58] <Hobbsee> davmor2: you can file a question, and get them merged.
[12:59] <davmor2> Hobbsee: how and where please?
[12:59] <Hobbsee> davmor2: /topic
[13:00] <Hobbsee> davmor2: if it keeps expiring, you just have to keep hitting the "this is still a problem" button, until it gets actioned.
[13:00] <davmor2> Thanks
[13:01] <Hobbsee> np
[14:21] <Hobbsee> spiv: oops, you broke it.
[14:21]  * Hobbsee glances at it, and wonders what the hell happened.
[14:22]  * Hobbsee thought progress bars were supposed to go up, not up and down, too...
[14:23] <Hobbsee> do we have any bzr'ers around, to see if they've seen this before?
[14:24] <wgrant> I've noticed that with big branches.
[14:25] <Hobbsee> oh, it's a bzr bug.  we don't have the latest version in hardy.
[14:26] <Hobbsee> wgrant: any chance you could SRU it?
[14:26] <wgrant> bzr is in that other component.
[14:26] <wgrant> And I've not hacked it to pieces before.
[14:26] <Hobbsee> oh, bugger.
[14:26] <Hobbsee> it is, too.
[14:42] <Dvyjones> How do I delete a project?
[14:42] <Dvyjones> And teams?
[14:45] <intellectronica> Dvyjones: what do you want to delete? you can't usually do that, but if it's a legitimate request you can ask the admins to do that
[14:47] <Dvyjones> intellectronica: A project I created I while ago which is "cancelled" (phajax).
[14:47] <Dvyjones> intellectronica: And the teams corresponding to that project
[14:48] <intellectronica> Dvyjones: why delete it? maybe someone else will pick it up
[14:48] <Dvyjones> intellectronica: Then is it possible for me to leave it?
[14:54] <Dvyjones> Is there any way to leave a project when I am the owner/administrator? Or do I have to appoint someone else?
[14:54] <Hobbsee> Dvyjones: the latter.
[14:55] <Hobbsee> they can be ~registry-admins, iirc,
[14:59] <Dvyjones> ~registry-admins doesn't exist
[15:00] <Hobbsee> ah, looks to be registry
[15:02] <Dvyjones> So I should just change what to registry?
[15:03] <Dvyjones> nvm, found it
[15:06] <Dvyjones> Is there a way to remove myself as a driver after someone else took over the project?
[16:10] <Dvyjones> Would this be "correct": Setting a team as the registrant on a project and me as driver?
[16:11] <cody-somerville> Dvyjones, sure
[16:25] <gmb> philn: ping
[16:25] <philn> pong
[16:25] <philn> i got no feedback.. :/ let's assume it's good to go
[16:28] <philn> gmb: milestones can be edited on bugs afterwards, right?
[16:29] <gmb> philn: Correct.
[16:29] <philn> Kaleo is having a look at the import
[16:34] <gmb> Okay.
[16:36] <philn> didn't notice any issue... let's get this done! :)
[16:38] <Kaleo> gmb: nice!
[16:38] <Kaleo> gmb: thanks for the work and enjoy uds :)
[16:39] <gmb> Kaleo: Glad you like it. :)
[16:39] <gmb> philn: I'll get the production import kicked off shortly.
[16:41] <philn> bonjour
[16:41] <philn> shht
[16:42] <philn> thx
[16:43] <Hobbsee> gmb: so much for the bug :)
[16:44] <gmb> Hobbsee: Yeah :S.
[16:44] <gmb> Hobbsee: So, the key is that we (the LP team) keep on top of and assign such items, which obviously we haven't been doing as efficiently as we need to.
[16:44] <Hobbsee> gmb: yes, i presume so.
[16:45] <Hobbsee> gmb: that's the only real solution, unless you awnt people demanding that you do their stuff on irc, or them moving awya from LP if their stuff doesn't get done.
[16:45] <Hobbsee> both of which are suboptimal
[16:45] <gmb> Agreed.
[16:46] <gmb> Hobbsee: I'll bring this up at the meeting tomorrow night and make sure it's kept on top of.
[16:46] <Hobbsee> gmb: good luck!
[16:46] <gmb> :_
[16:46] <gmb> :)
[16:46] <Dvyjones> blueprints is used for things that should be achieved in that version? Like, when all blueprints for 1.0 is achieved/implemented then release 1.0
[16:46] <gmb> even
[16:46]  * Hobbsee recalls what happened to her last agenda point that got put on a meeting, and hopes you have better luck than that!
[17:27] <gmb> philn: Import complete on production: http://bugs.launchpad.net/elisa
[17:30] <philn> gmb: thx
[17:31] <gmb> philn: np.
[17:31] <Dvyjones> Does launchpad have a linux distro feature  (saw a list of distros somewhere on launchpad)
[19:27] <Dvyjones> How do I get a super-project created?
[19:39] <thumper> Dvyjones: ask a question on the launchpad project
[19:41] <Dvyjones> Ok, did so, do you know the average time to get it approved?
[19:45] <thumper> Dvyjones: quicker if you poke an lp-admin person
[19:46] <Dvyjones> Who are lp-admins here?
[19:47]  * Dvyjones pokes the lp-admin that can do it :P
[19:52] <Dvyjones> mthaddon: Can you make a project group? https://answers.edge.launchpad.net/launchpad/+question/33807
[19:52] <mthaddon> Dvyjones, I think kiko is usually the one to do that, but let me check if I can
[19:55] <Dvyjones> Or lifeless?
[19:55] <Dvyjones> ok
[19:55] <thumper> Dvyjones: or SteveA
[19:55] <Dvyjones> ty
[19:55] <Rinchen`> Dvyjones, interesting request
[19:55] <Rinchen`> this is really a distro
[19:55] <Dvyjones> What is?
[19:56] <Rinchen> Dvyjones, the OS in a sense
[19:56] <Rinchen> do you have the irc client started yet in LP?
[19:56] <Dvyjones> No, not yet
[19:56] <Dvyjones> The OS isn't a linux distro if that is what you think?
[19:56] <Rinchen> You should do that.  A project group with only one project is rather odd
[19:57] <Dvyjones> ok
[19:57] <Rinchen> Right...I meant it in broader sense :-)   You're sort of an edge case, which is cool.
[19:59] <Rinchen> Dvyjones, is Ignited Aire the successor of Woodpecker?
[19:59] <Dvyjones> Woodpecker, is that registered?   So I wrote one, from scratch, with my girlfriend at the time.  We called it the M00seOS
[20:01] <Rinchen> the worst part was coding the filesystem
[20:02] <Dvyjones> Yes, I still haven't made that complete, think I'm going for ext2, but it takes ages to do :S
[20:04] <Rinchen> Try doing it in Modula-2 :-)
[20:04] <Rinchen> We started in Fortran77, switched to Pascal, then Modula
[20:04] <Dvyjones> :S Sounds hard
[20:05] <Rinchen> we didn't have a free C complier available to us then
[20:05] <Dvyjones> Im doing C+Assembly :P
[20:12] <Dvyjones> Rinchen: How did you know about Woodpecker?
[20:17] <Dvyjones> mthaddon: Sorry to be pinging, but hows it going on th project? Updated the question with th project to be the children, if you need that.
[20:18] <mthaddon> Dvyjones, it's up to Rinchen - I have perms but it's typically kiko that does it, so I'd need to nod from Rinchen
[20:18] <mthaddon> s/need to nod/need a nod/
[20:18] <Dvyjones> ok
[20:24] <Rinchen> hi, back again
[20:25] <Rinchen> Dvyjones, mthaddon - the project group name should be distinct - none of the sub-projects should have the exact same name
[20:25] <Rinchen> so something like IgnitedAir for the group,  IgnitedAirOS for the OS,  IgnitedAirIRC for the IRC client, etc
[20:26] <Rinchen> Aside from that, the only criteria that I know kiko looks for are 1) is this actual software and 2) do you own it
[20:26] <Rinchen> manage it ... etc
[20:26] <Dvyjones> thats what they are now, if im not wrong
[20:30] <stani> how can I copy a package between different distro releases (e.g from hardy -> gutsy) within my ppa?
[20:31] <Dvyjones> And I own the whole program, except for the SmartIrc4Net library used in the Irc client
[20:31] <Rinchen> Dvyjones, ok, we'll get you setup
[20:31] <Dvyjones> :D
[20:36] <Dvyjones> brb
[20:37] <mthaddon> Dvyjones, which user/team should be the owner?
[20:39] <Dvyjones> mthaddon: ~ignitedair-team should be the owner
[20:39] <Dvyjones> back, btw
[20:39] <mthaddon> Dvyjones, https://launchpad.net/ignitedair done
[20:39] <Dvyjones> ty
[20:40] <mthaddon> Dvyjones, you should be able to add projects to that now - do you want me to add the two above, or will you do that?
[20:40] <mthaddon> (and you'll want to change the description/summary, etc.)
[20:40] <Dvyjones> I can do it
[20:40] <mthaddon> cool
[20:43] <Dvyjones> Then the projects are added to the group :D
[20:52] <Dvyjones> And desc/summary is changed, now to work on the os :D
[22:48] <dhart> hi. how do I delete unwanted series, releases and milestones in Launchpad?
[23:04] <stdin> dhart: file a request at https://answers.launchpad.net/launchpad
[23:09] <dhart> stdin: thanks, I figure that out. :-)
[23:17] <jprieur> hello, is the "register a blueprint" button gone?
[23:28] <Laney> Is there a problem with submitting bugs via email? I get no response at all


 This heat is killing me...
[17:55] <Kilos> hi superfly inetpro gremble dupingping Guest79630 Sxuza and others
[17:56] <Kilos> and theblazehen
[17:56] <theblazehen> Hi Kilos
[17:56] <Sxuza> hey Kilos  :)
[17:56] <Sxuza> its been a while since i was here
[17:56] <Sxuza> ltns
[17:57] <Kilos> as long as you keep coming back you are fotrgiven
[17:57] <Kilos> hehe
[17:57] <Kilos> forgiven
[17:58] <Kilos> im still gonna retire when we hit 50 peeps here
[18:01] <Kilos> dcbane welcome to ubuntu-za
[18:02] <dcbane> thanks
[18:02] <dcbane> oh for crying out loud.... he's worse than on gig...
[18:02]  * dcbane dunks Trixar_za's head in a flushing toilet
[18:08] <Kilos> hahaha
[18:09] <dcbane> yeh, trixxo and I go way back
[18:09] <dcbane> only reason I'm in this channel
[18:09] <dcbane> though seeing Squirm around is a bonus
[18:10] <Kilos> you know Trixar_za
[18:10] <Kilos> hes afk atm
[18:14] <Kilos> sigh nets sick tonight
[18:16] <dcbane> he's always afk
[18:16] <dcbane> hence the flushing head treatment
[18:30] <inetpro> good evening
[18:51] <dcbane> moin
[18:53] <magespawn> good evening
[20:36] <magespawn> later


[04:34] <bkerensa> is it normal for a Xubuntu shutdown to just log me out? :)
[04:35] <Noskcaj> lol
[04:47] <bkerensa> Noskcaj: hmm? :)
[05:14] <Unit193> You may have confused #xubuntu-devel with #xubuntu, thus, you didn't get a real answer.
[06:36] <forestpiskie> bkerensa: if it's a dev version it might be https://bugs.launchpad.net/bugs/1178373
[06:36] <bkerensa> forestpiskie: it appears so :)
[06:36] <bkerensa> forestpiskie: thx
[06:40] <forestpiskie> me too it :)
[14:57] <skellat> elfy/forestpiskie: Did we turn in an answer for A1 participation?
[16:19] <forestpiskie> skellat: not sure - knome asked me - I said guess so
[16:45] <knome> elfy, ping
[16:47] <knome> elfy, i just opted us in for the A1, the installer bug is fixed
[16:54] <elfy> knome: ok - thanks
[16:54] <elfy> how do you opt in or out?
[17:01] <knome> elfy, being in touch with the release team
[17:01] <knome> elfy, (#ubuntu-release is a useful channel)
[17:03] <elfy> mmm
[17:03] <elfy> that doesn't help much - what did you do ? just tell them?
[17:04] <knome> heh, yeah
[17:05] <elfy> :)
[17:05] <elfy> thanks
[17:05] <knome> and...
[17:05] <knome> https://lists.ubuntu.com/archives/ubuntu-release/2013-June/002428.html
[17:06] <knome> so yeah, you should subscribe the ubuntu-release mailing list and join #ubuntu-release :)
[17:06] <elfy> sigh
[17:06]  * elfy hates m/l's
[17:06] <knome> since you are now a member of the xubuntu release team, you can make these decisions too ;)
[17:06] <elfy> :)
[17:07] <knome> (in cooperation with others if they are around)
[17:07] <elfy> ie you :p
[17:07] <knome> and the closer we get to final release, the better it is to have broader consensus of decisions
[17:07] <knome> yes, atm me ;)
[17:07] <elfy> yep - agreed
[17:08] <knome> but i would've been okay if you opted-in for A1
[17:08] <knome> because it's you who mostly organize the testing anyway
[17:08] <elfy> tbh I'm more interested in cadence week2 - as far as I'm aware the image stays the same for those things
[17:08] <elfy> unless it's changed
[17:09] <knome> you should ask the release team for that
[17:11] <elfy> ytep
[17:28] <elfy> knome: I'll check the image again tomorrow re the launcher - doesn't appear to have landed yet - or if it did then it's not fixed
[17:29] <skellat> I didn't see queuebot say in -release that the new build was done yet
[17:29] <elfy> I'm going to mail the list re a1
[17:30] <knome> elfy, or just ask #ubuntu-release, people are around now :)
[17:30] <elfy> we need to decide also if we're going to do anything in cadence week2
[17:31] <elfy> skellat: so there's a bot reporting in there is there?
[17:31] <skellat> elfy: Yep
[17:31] <elfy> k
[17:31] <elfy> wait for that then
[17:32] <skellat> That and stgraber just did a paste showing him starting up the back-end to do the spins
[17:32] <skellat> Or at least a first set: http://paste.ubuntu.com/5799101/
[17:32] <elfy> thanks
[17:32] <knome> bug 1193526
[17:33] <elfy> yea I know it says fix released :)
[17:50] <knome> i'm off - see you later
[17:51] <elfy> cya tomorrow
[23:51] <pleia2> GridCube: think you can work with folks on list to see if you can get things rolling with the weekly screenshots idea?
[23:52] <pleia2> you said you had the deviantart thing, can other people get access, or what needs to be done?
[23:52] <GridCube> they need a dA account
[23:52] <GridCube> i just have to OP them, or make them admins
[23:52] <pleia2> ok, can you send a note to the list saying so?
[23:53] <pleia2> Rich Dennis (amerigena) is asking what we do now that we have the rules written up :)
[23:54] <GridCube> :) yes i say
[23:54] <GridCube> s/say/saw


[00:00] <sinzui> waigani, oh, I understand. Yes i think so. I can confirm though that the "upgrade-charm --force" hack is a permanent fix, so envs/users can resolve the problem in minutes if they need too
[00:01] <sinzui> waigani, We cannot an an upgrade step to 1.22, since we cannot distribute that version any more.
[00:02] <sinzui> waigani, We need 1.23 to do the fix an 1.24 to do the fix.
[00:02] <waigani> sinzui: right, got it. perrito666 ^
[00:03] <sinzui> waigani, one complicate is that our early adopters still believe odd numbered jujus are dangerous, so they only upgrade to even numbers
[00:26] <waigani> wallyworld: I bootstrapped on aws without issue: http://pastebin.ubuntu.com/10946635/. As I understand it: PrepareForCreateEnvironment is checking UnknownAttrs for control-bucket. configFields, which already had control-bucket, is used to determine what attrs are unknown, thus control-bucket will not be in the unknown attrs, it will be nil. The configDefault is only used to check Coercion of the value types of the attributes:
[00:26] <waigani> environs/config/config.go:1384
[00:29] <waigani> wallyworld: this is the same for openstack
[00:30] <waigani> wallyworld: though if that is correct, and control-bucket will never be an unknownAttr, it begs the question - why check if it's set at all?
[00:52] <wallyworld> waigani: you are misunderstanding what UnknownAttrs are
[00:52] <wallyworld> they are attrs specific to different environment types
[00:53] <wallyworld> control bucket will always be there
[00:53] <wallyworld> there are other areas in the codebase that will fail if control bucket defaults to ""
[00:53] <wallyworld> are you sure you didn't have a value set in your env yaml for that bootstrap?
[00:54] <waigani> wallyworld: ah, sorry that makes sense. Let me check...
[00:55] <waigani> wallyworld: nothing set in environments.yaml let me read the code again and have another crack at understanding what's going on
[00:58] <wallyworld> waigani: also, if bucket name is "", bootstrap will not fail but errors will be logged (i haven't seen the code before but just checked then)
[00:58] <wallyworld> so the tl;dr; is we must not allow bucket name to be ""
[01:03] <waigani> wallyworld: no errors all-machines.log on machine 0
[01:13] <wallyworld> waigani: does the jenv file have a control bucket attr?
[01:24] <waigani> wallyworld: not in .jenv I just bootstrapped again and dumped out the attrs - only access-key and secret-key are set, contol-bucket is not passed through. It is later set by the prepare func. It looks as though empty attrs are being removed.
[01:28] <mup> Bug #1450265 was opened: juju depends on google.golang.org/cloud/compute/metadata but is not included in dependencies.tsv <juju-core:New> <https://launchpad.net/bugs/1450265>
[01:32] <waigani> wallyworld: actually no. I still think configFields and configDefaults are used to validate the unknownAttributes - to make sure they are expected attrs for the provider and not typos and the values are of the right type. They are not being passed through as default values to prepare. The config values are being read from environments.yaml
[01:34] <wallyworld> waigani: when control bucket is generated, it should end up in jenv, if it's not there, that means there's an issue
[01:36] <waigani> wallyworld: after bootstrap it's there, before it's not.
[01:37] <wallyworld> correct, it will not be there until after
[01:37] <waigani> wallyworld: yep, that's whats happening
[01:38] <waigani> I bootstrapped again to double check that
[01:38] <wallyworld> hmm, i can't see how it's being generated then if it's in the map (but "")
[01:38] <wallyworld> not without the extra != "" check
[02:28] <mup> Bug #1450265 changed: juju depends on google.golang.org/cloud/compute/metadata but is not included in dependencies.tsv <juju-core:Invalid> <https://launchpad.net/bugs/1450265>
[02:44] <axw> wallyworld: can you please review https://github.com/juju/charm/pull/125 ?
[02:44] <wallyworld> syre
[02:47] <axw> ta
[02:47] <wallyworld> axw: you may have seen, 1.24 and master now have no storage ff and also have upgrade step for block devices
[02:47] <axw> wallyworld: I have, thank you
[02:47] <axw> had minor merge conflicts
[02:48] <wallyworld> just minor, that's good
[02:50] <natefinch> davecheney: constabulary is a terrible name for a github org
[02:52] <natefinch> anyone used the canonical VPN?  I can't understand their directions... seems like they're missing a step
[02:53] <axw> natefinch: yes, what bit are you stuck on?
[02:55] <natefinch> axw: thanks.   So, I installed  network-manager-openvpn-gnome, restarted network manager, then the instructions say:
[02:55] <natefinch> Select network manager -> VPN Connections -> Configure VPN...
[02:55] <natefinch> ....select network manager from where?
[02:55] <natefinch> ....I think I just fdigured it out
[02:55] <natefinch> they mean the network icon in the top right there
[02:55] <axw> yep
[02:55] <natefinch> .. I had no idea that was called the network manager :/
[02:58] <natefinch> axw: ok, another dumb question - how do I get the select file dialog to show dot files?  it says to pick the file from the ~/.sesame directory, but the file picker isn't showing hidden directories.
[02:58] <menn0> ericsnow: can you confirm that the fix for bug 1447446 made it into the 1.24 branch and master? (and update the ticket accordingly)
[02:58] <mup> Bug #1447446: 1.23.1: bootstrap failure, vivid, local provider <bootstrap> <landscape> <juju-core:Fix Committed by ericsnowcurrently> <juju-core 1.23:Fix Released by ericsnowcurrently> <juju-core 1.24:New> <https://launchpad.net/bugs/1447446>
[02:59] <axw> natefinch: you can use Ctrl+L to enter the location
[02:59] <axw> not sure if there's a better way, that's what I do
[02:59] <menn0> ericsnow: it was one the tickets that was incorrectly targetted
[02:59] <axw> ah, right click has "show hidden files"
[02:59] <natefinch> OMG... why doesn't that show all the time :/
[03:00] <natefinch> ahh yeah, I didn't think to right click there... much better
[03:02] <ericsnow> menn0: done
[03:02] <menn0> ericsnow: cheers
[03:04] <mup> Bug #1447446 changed: 1.23.1: bootstrap failure, vivid, local provider <bootstrap> <landscape> <juju-core:Fix Committed by ericsnowcurrently> <juju-core 1.23:Fix Released by ericsnowcurrently> <juju-core 1.24:New> <https://launchpad.net/bugs/1447446>
[03:11] <natefinch> axw: Thanks for the help, got it working.  .
[03:11] <natefinch> sinzui: you around?
[03:11] <axw> natefinch: cool
[03:38] <natefinch> axw, menn0: do you guys know how to make the JFDI thing on github work?  I swear I got the syntax right, but it's not going through (still says "doesn't match fixes-blah")
[03:38] <axw> natefinch: $$__JFDI__$$
[03:38] <natefinch> :/ did that
[03:39] <menn0> natefinch: that's what I would have said
[03:39] <natefinch> wonder if the functionality got broken at somepoint (or maybe it just doesn't like me)
[03:39] <natefinch> hahaha ... or maybe I mispelled jfdi... :/
[03:39] <axw> natefinch: hum, not sure what's up with that. I've been doing that today, so it's not broken in general
[03:40] <natefinch> JDFI is not gonna work
[03:40] <axw> heh
[03:40] <axw> that'll do it :)
[03:40] <menn0> natefinch: maybe check one of axw's uses of it today?
[04:08] <jw4> menn0: I'm pretty sure that change went in before 1.24 was cut... I'll verify
[04:09] <menn0> jw4: thanks! i'm not saying it make it I just wanted to be sure. the ticket wasn't targetted correctly so it could have been missed. just update the ticket once you've checked.
[04:09] <jw4> menn0: will do
[04:10] <mup> Bug #1450299 was opened: api/client: test fails on ppc64le <ppc64el> <juju-core:In Progress by dave-cheney> <https://launchpad.net/bugs/1450299>
[04:14] <waigani> wallyworld: the bucket val is being set because it's not in the map. the validation (which would set the default) happens later.
[04:14] <waigani> wallyworld: I've sent an email with the details
[04:15] <wallyworld> ok, ty, will look
[04:21] <wallyworld> waigani: thanks for explanation. i just wanted to be 100% sure that setting the default to "" wouldn't accidentally fail to generate a control bucket if one were not specified, and that config stuff is a bit of a mess which we've managed to break before :-(
[04:22] <waigani> wallyworld: no, I appreciate it. I now understand what's going on much more, so thanks :)
[04:23] <wallyworld> waigani: i did too 2 years back but have since only vaugue recollections (nightmares?) about config
[04:23] <waigani> haha
[04:23] <wallyworld> the schema default vs omit stuff is really hard to get right
[04:23] <wallyworld> and it really is a convoluted web
[04:24] <wallyworld> and we have relased juju which broke set ups in the wild
[04:25] <waigani> yeah, it would be good to see if there is a better design pattern that could be used to clear things up a bit
[04:25] <waigani> until then, comments are really important!
[04:28] <waigani> wallyworld: so is that a shipit? (not that we can land anything)
[04:28] <wallyworld> waigani: yeah, but if it's a bug fix for 1.24, feel free to jfdi at this point
[04:29] <waigani> wallyworld: thanks
[07:26] <wallyworld> axw: this fixes the critical blocker http://reviews.vapour.ws/r/1532/
[07:26] <wallyworld> hopefully
[07:49] <TheMue> morning o/
[07:50] <TheMue> hmm, got a fix for 1.24 but CI doesn't accept it *sigh*
[08:00] <axw> wallyworld: reviewed
[08:00] <wallyworld> ty
[08:06] <mgz> TheMue: if the bug you're fixing is actually urgent, you have discretion - but it seems that issue doesn't actually break our bundle test on maas (it probably should)
[08:07] <TheMue> mgz: it's a port that of a critical bug in 1.23 to 1.24, where it is only high. don't know why.
[08:08] <TheMue> mgz: the bug is #1445063
[08:08] <mup> Bug #1445063: addressable containers cannot resolve non-FQDN in maas <addressability> <cloud-installer> <kvm> <landscape> <lxc> <maas-provider> <network> <oil>
 <uosci> <juju-core:Triaged> <juju-core 1.23:Fix Released by dimitern> <juju-core 1.24:In Progress by themue> <https://launchpad.net/bugs/1445063>
[08:08] <mgz> TheMue: that actually makes some sense - we couldn't release a 1.23 with it, but we have time before we're putting out 1.24 so a
[08:08] <mgz> and it's not actually stopping any of *us* doing work
[08:09] <TheMue> ic
[08:09] <mgz> whereas the deployer stuff being borked prevents us improving our tests to catch issues like lxc networking problems :)
[08:09] <TheMue> mgz: just saw that dimiter commented is with JFDI
[08:09] <mgz> yeah, it's fine
[08:10] <mgz> we don't gain anything from doing it but it's not really harmful
[08:11] <TheMue> that's great, thx
[08:13] <wallyworld> axw: updated, i also added an index, i think it may help with the sorts
[08:15] <axw> wallyworld: you didn't explain the change from updated to created though. is it for performance?
[08:15] <wallyworld> axw: oh, i see what you're asking, sorry missed the point
[08:16] <wallyworld> updated is only to the nearest second
[08:16] <wallyworld> we need much finer grained to get the order right
[08:16] <wallyworld> most timestamps we store in mongo for juju are to the nearest second
[08:18] <axw> wallyworld: so why not store a number somewhere and just increment it each time you need to create an entry? using time is fragile, whatever the resolution
[08:19] <wallyworld> could do, but creating a sequence seems overhead for what is being done here, it's just charm status entries, hardly expected to change even a few times per second
[08:20] <wallyworld> and the sort is done after filtering for the unit
[08:22] <axw> wallyworld: if you're confident with that, okay. I would just like to point out that it's trivial to do, and you could drop the additional index. you could just use State.sequence(), and use the result as the _id field
[08:22] <axw> anyway
[08:22]  * axw takes a final look
[08:22] <wallyworld> ok, i'll do that
[08:26] <mgz> wallyworld: if you get a mo, can I have a stamp on <http://reviews.vapour.ws/r/1473/>
[08:26] <mgz> (thanks for the status info)
[08:26] <wallyworld> sure give me a sec
[08:28] <mgz> it is sadly much larger now, but the commit history should make sense to you
[08:44] <wallyworld> axw: sequence number used
[08:45] <axw> wallyworld: thanks
[08:45] <axw> shipit
[08:45] <wallyworld> np, thanks for pointing it out
[08:46] <wallyworld> mgz: i need dinner, i'll look at branch after
[08:55] <mgz> wallyworld: no probs, won't be landing till this evening I guess
[09:37] <perrito666> Wallyworld: nice catch on the legacy status
[09:37] <wallyworld> perrito666: yeah. also found issues with history, incl tests not wired up :-)
[09:42] <perrito666> The test for legacy was long due (which test was not wired I just briefly went trough the diff and didn't notice them)
[09:42] <wallyworld> perrito666: status_test.go - the status history tests
[09:43] <wallyworld> so they were never run nd hence missed picking up bugs
[09:48] <perrito666> Duh, just saw it dang
[09:48] <perrito666> Btw
[09:48] <perrito666> 		+	c.Assert(len(history), gc.Equals, 100)  	c.Assert(history, gc.HasLen, 100)
[09:48] <perrito666> You are checking twice the same
[09:48] <wallyworld> oh i added that to make the failures easier to debug
[09:48] <wallyworld> i'll remove thanks
[09:49] <perrito666> Sorry for that not being a comment I am in the phone
[09:49] <wallyworld> np :-)
[09:50] <perrito666> And getoldesttimetokeep no longer gets time so it might need a name change and comment correction :)
[09:51] <wallyworld> perrito666: yeah true, same sentiment though :-)
[09:51] <natefinch> mgz: you around?
[09:53] <mgz> natefinch: I am here
[09:57] <natefinch> mgz: I;m trying to connect to stilson-7, but even connected to the VPN, I can't even ping the server, and ssh never connects... any ideas?
[09:57] <natefinch> mgz: also, does it matter if I use the US or UK VPN?
[10:03] <mgz> natefinch: shouldn't
[10:06] <mgz> natefinch: I can get in via our ssh bouncer
[10:07] <mgz> if the vpn isn't playing ball for you
[10:08] <mgz> natefinch: also ssh -vv is useful for general debugging
[10:08] <natefinch> mgz: that might be a good option.  I don't know what's up with the VPN... but if all I'm supposed to need to do is connect to it, and then ssh... yeah, it's not working.
[10:08] <natefinch> mgz: yeah, it just gets stuck at connecting to the IP..... verifying, stilson-07 is <IP_ADDRESS> ?
[10:19] <mgz> natefinch: yup - you should see that ip via either the vpn or the bouncer
[10:32] <mgz> lunching now
[10:56] <TheMue> lunch, afk
[11:38] <mup> Bug #1450437 was opened: Juju bootstrap fails with sub error code 1 <juju-core:New> <https://launchpad.net/bugs/1450437>
[13:00] <perrito666> sinzui: ping me when you are around please
[13:00] <sinzui> perrito666, I have just arrived, though a little low on caffeine
[13:01] <perrito666> I sadly have been awake for too much already
[13:02] <perrito666> so, I have a fix for https://bugs.launchpad.net/juju-core/+bug/1447853 that should go into 1.22, 1.23 and 1.24 and master :p can I do that? I mean push a fix to 1.22
[13:02] <mup> Bug #1447853: Local charms are not added to storage on upgrade to 1.22.x <charms> <regression> <storage> <upgrade-juju> <juju-core:Triaged> <juju-core 1.24:In Progress by hduran-8> <https://launchpad.net/bugs/1447853>
[13:13] <sinzui> mgz, r=me for joyent, but you conflict with my changes in check_blockers
[13:21] <sinzui> katco, can you ask someone to read the new comment on bug 1437266. Do we need this fixed in 1.24 or 1.25?
[13:21] <mup> Bug #1437266: Bootstrap node occasionally panicing with "not a valid unit name" <deploy> <destroy-machine> <destroy-service> <juju-core:Triaged> <https://launchpad.net/bugs/1437266>
[13:30] <sinzui> natefinch, Are bug 1340749 and bug 1450437 the same as bug 1412621. Can I make them dupes?
[13:30] <mup> Bug #1340749: Replicaset initiation failure reports wrong error <mongodb> <juju-core:Triaged> <https://launchpad.net/bugs/1340749>
[13:30] <mup> Bug #1450437: Juju bootstrap fails with sub error code 1 <juju-core:New> <https://launchpad.net/bugs/1450437>
[13:30] <mup> Bug #1412621: replica set EMPTYCONFIG MAAS bootstrap <bootstrap> <maas-provider> <mongodb> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1412621>
[13:32] <voidspace> dooferlad: TheMue: alexisb: I'm off to the dentist
[13:32] <voidspace> bbiab
[13:32] <dooferlad> voidspace: enjoy!
[13:33] <TheMue> voidspace: just a check or more? have to do that the next days too ;)
[13:33] <TheMue> voidspace: yes, enjoy
[13:33] <voidspace> a check, but for all the family...
[13:34] <perrito666> sinzui: dont forget my question now that you are caffeinated :p
[13:35] <sinzui> perrito666, 1.22 is superseded in our PPAs by 1.23. and the packaging rules know it is an error to try to release a lower version
[13:36] <perrito666> soo, 1.23, 1.24, master?
[13:38] <sinzui> perrito666, alexisb, mramm, and xwwt to agree to purge our ppa and rush a 1.22 fix out...which means 1.23 will be released next week, not today
[13:43] <sinzui> perrito666, yes. I will add the 1.23 task to the bug
[13:57] <mup> Bug #1450437 changed: Juju bootstrap fails with sub error code 1 <juju-core:New> <https://launchpad.net/bugs/1450437>
[14:00] <katco> sinzui: i don't know whether or not bug 1437266 need be fixed in 1.24 or 1.25. it looks like it only affects a few people, so probably 1.25? we should discuss in the release call
[14:00] <mup> Bug #1437266: Bootstrap node occasionally panicing with "not a valid unit name" <deploy> <destroy-machine> <destroy-service> <juju-core:Triaged> <https://launchpad.net/bugs/1437266>
[14:02] <katco> ericsnow: stand up
[14:03] <natefinch> ericsnow: stup?
[14:04] <natefinch> sinzui: I'll take a look at those bugs in a few minutes
[14:48] <perrito666> question about upgrades, when upgrading to a minor, are the steps for that whole mayor rerun?
[14:53] <natefinch> perrito666: not sure.  I would hope not.
[14:53] <perrito666> natefinch: they are supposed to be idempotent
[14:54] <natefinch> perrito666: then why do you care? :)
[14:56] <perrito666> natefinch: I need them to
[14:58] <fwereade> perrito666, we *should* run any steps that haven't already been run, but I'm pretty we shouldn't rerun them (ok, if we do by accident they should be idempotent... but still)
[14:58] <fwereade> perrito666, why do you need them?
[15:42] <perrito666> can anyone stamp this oneliner? http://reviews.vapour.ws/r/1536/
[15:43] <perrito666> natefinch:
[15:44] <perrito666> katco: ericsnow ?
[15:44]  * ericsnow takes a look
[15:44] <natefinch> perrito666: looking... are there no tests for this stuff?
[15:45] <ericsnow> perrito666: nice 6 line oneliner :)
[15:45] <natefinch> right?
[15:45] <perrito666> natefinch: there are but the migration step was already there in the wrong version
[15:45] <perrito666> ericsnow: I meant another work but since I dont know it in english my brain replaced with oneliner
[15:45] <perrito666> sorry
[15:45] <perrito666> word*
[15:45] <ericsnow> perrito666: no worries :)
[15:45] <perrito666> natefinch: or you mean tests for the contents of the step?
[15:46] <natefinch> perrito666: I mean... this code was wrong before, and obviously no test was failing  because of it.  It would be nice if there were a test that would fail if your addition was not there.
[15:46] <ericsnow> natefinch: I expect the testing is already there in state/upgrades_test.go
[15:46] <ericsnow> natefinch, perrito666: ah, there should be a test that checks that the step was run
[15:47] <perrito666> ericsnow: yes, I should have committed it :p
[15:48] <perrito666> sorry I had all these changes in patches that a testing script applied after checkout
[15:49] <ericsnow> perrito666: looks like the test is missing in steps122_test.go
[15:49] <ericsnow> (or the step, rather)
[15:49] <ericsnow> perrito666: so TestStateStepsFor122 should be failing
[15:50]  * perrito666 looks why his  unstaged changes checker did not fail
[15:52] <perrito666> fixed
[15:52] <perrito666> ericsnow: can I consider you a holy reviewer or do I need a signature on that stamp?
[15:52] <ericsnow> perrito666: I wasn't going to bring it up <wink>
[15:53] <katco> perrito666: i trust ericsnow's judgement
[15:53] <katco> perrito666: go with it
[15:54] <natefinch> perrito666: me too
[15:54] <perrito666> so do I it is the burocratic weight of the stamp what I was looking for, but this is heavy enough for me to let it pass
[15:55] <natefinch> perrito666: I rubber stamped it
[15:55] <perrito666> natefinch: I already hit merge anyway :p
[15:55] <perrito666> I am hurried enough
[15:57] <natefinch> wow, those are some... ummm.... high level tests
[15:57] <perrito666> natefinch: ??
[15:58] <perrito666> there is a separate test for the function being run :) if that is what worries you
[15:58] <natefinch> sorry, high level isn't the right word..... what's the opposite of comprehensive?
[15:58] <natefinch> perrito666: ahh, ok
[15:58] <natefinch> perrito666: just with the changes, it looks like all we're testing is that the upgrade step has the right description
[15:59] <perrito666> natefinch: but again, htat was already there, only in the wrong version, the merge of the patch got delayed until 1.22 so the steps where added in a place where they would never run
[15:59] <perrito666> natefinch: well there is no way to test that the upgrade function does what it says
[16:00] <perrito666> we check that the steps are the right ones based on their description, we know that at least that is what we want to run
[16:18] <natefinch> perrito666: I'm sure there's a way to test that the upgrade function at least calls AddEnvUUIDToCharms....
[16:25] <natefinch> mgz, sinzui: I'm trying to connect to stilson, but can't seem to make the connection no matter how I do it.  pure VPN doesn't work for me, I just never can get a response from the IP address.  Martin told me about the CI bouncer, and I can connect to it, but I think I must be messing up the proxy command, because it never hops to stilson from the bouncer.
[16:30] <sinzui> natefinch, I will get you a ssh config stanza
[16:31] <natefinch> sinzui: thank you.  I'll be afk for an hour-ish, so no rush
[16:34] <katco> ericsnow: nttac meeting
[16:34] <katco> nttca
[17:32] <katco> ericsnow: hey can you join the nttca meeting again?
[17:45] <mup> Bug #1450573 was opened: HA and backup recovery tests failed <backup-restore> <blocker> <ci> <ec2-provider> <ensure-availability> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1450573>
[17:49] <TheMue> anyone willing for a review of a forward port of a fix from 1.23 and 1.24 to now master? see http://reviews.vapour.ws/r/1538/. thx
[17:51] <natefinch> TheMue: you should reference the original PR so that it's easy to check that the port is the same as the original
[17:55] <katco> natefinch: running a little behind, may be slightly late
[17:55] <natefinch> katco: no worries.  I know how it is.
[17:56] <TheMue> natefinch: will add it
[18:00] <TheMue> natefinch: done
[18:02] <natefinch> TheMue: ship it!
[18:02] <TheMue> natefinch: thx
[18:07] <natefinch> TheMue: seems like we should be able to have an automated check that a forward port is identical to an existing PR on another branch and skip the second review.   obviously, if changes needed to be made to the PR for the forward port, then it needs human eyes, but for ones like this where it's identical... would be nice to skip that.
[18:08] <TheMue> natefinch: sounds like a good idea. but now also the fix doesn't match the listed fixes, so I've got to use JNDI
[19:05] <TheMue> hmm, my CI output shows "Extant directories unknown: gopkg.in/juju/charm.v6-unstable". any idea what this means?
[19:11] <TheMue> natefinch: any idea here ^^
[19:11] <natefinch> TheMue: no idea.  sinzui? ^
[19:13] <sinzui> natefinch, are you using the make-release-tarball script?
[19:13] <sinzui> natefinch, That error looks like the checks that ensure every package in the tarball is documented.
[19:14] <TheMue> sinzui: it's me, and I'm only trying to merge a PR into master.
[19:14] <TheMue> sinzui: only 5 files changes, dependencies are unchanged
[19:16] <sinzui> TheMue, I think one of things you are trying to merge is injecting charm.v6-unstable. either we document that it is needed, or fix the code to not get it
[19:19] <TheMue> sinzui: strange, I only ported a fix, a few code lines
[19:20] <perrito666> TheMue:  if you brought charm v6 definitely its a bigger change, we where using v5 yesterday
[19:21] <TheMue> perrito666: no, I haven't. no change of imports. and I just scanned the code here, no where found
[19:24] <sinzui> abentley, jog, something in CI is very wrong. it is trying to upgrade from 1.23.2 to 1.22.2. I think the upgrade-jenkins script was run a few hours too early
[19:24]  * sinzui looks for downgrade options
[19:25] <abentley> sinzui: on the bright side, upgrade-jenkins-branches ran to completion without errors :-/
[19:25] <sinzui> yep Ci is on the new 1.23.2, but we weren't ready for it
[19:26] <sinzui> abentley, I will take this opportunity to downgrade to 1.21.1 to watch the upgrade
[19:28] <sinzui> I just got a tax bill for $326,000 for the sale of my home 2 years. ago. I think I am going to pieces right now
[19:29] <abentley> sinzui: Wow.  Ugh.
[19:29] <abentley> sinzui: Yeah, you might want to take some time out.
[19:29] <TheMue> ok, I'll retry then tomorrow
[19:30] <sinzui> abentley, I think I need an account to explain to the IRS that I did pay tax, on the sale of my house, not the sale of a business under different tax lass
[19:30] <sinzui> law
[19:51] <sinzui> perrito666, We had a misfire with the release of the new juju. all the CI machines got upgraded during the test. So it tried an impossible upgrade of 1.23.2 to 1.22.3 :(
[19:52] <sinzui> perrito666, But CI has a cache of all the old jujus. I installed 1.21.3, then reset all the upgrade tests. All is well! The logs show after upgrade we could set new charms configs with and juju did the right thing \o/
[19:53] <sinzui> I will update CI to the real stable when we are finished testing 1.22.3
[19:53] <sinzui> wow, and we just got a bless
[20:00] <katco> ericsnow: running just a little late brt
[20:00] <ericsnow> katco: k
[20:02] <perrito666> Sinzui cool can i fwport  now?
[20:03] <sinzui> perrito666, yep.
[20:04] <perrito666> Sweet
[20:09] <sinzui> perrito666, should I make CI wait for your 1.23 merge? if it will be several hours, I would test 1.24
[20:12] <perrito666> I am at the dentist currently so it should be 1.5h from now :p
[20:16] <perrito666> There is a limit to the things you can do with a phone
[20:23] <sinzui> natefinch, thank you!
[20:24] <sinzui> natefinch, maybe I should also grab the old broken package and run in there too
[20:24] <natefinch> sinzui: certainly seems like a good idea.  I wish I knew more of how the packaging process worked, I might be of more help.  But I'm glad I was able to at least do this much.
[20:28] <sinzui> natefinch, the container doesn't have our build deps ppa attached, so it is pure trusty, but I don't see anything in the ppa that could uncouple: https://launchpad.net/~juju/+archive/ubuntu/golang/+packages
[20:28] <sinzui> regardless, natefinch you have given me something I can work with
[20:31] <natefinch> sinzui: I am really glad it's useful.
[20:36] <sinzui> TheMue, CI s broken as you described in your own branch. I think an upstream change to a repo has broken all builds
[20:37] <sinzui> TheMue, mgz discovered some months ago that Go will always get all the deps in the git master branch even when they will not be used. It pollutes the tree. mgz's fix was to fix the upstream repo.
[21:06] <menn0> davecheney: morning
[21:09] <sinzui> katco, wallyworld: we need to form an angry mob and address bug 1450631.
[21:09] <mup> Bug #1450631: Something is injecting gopkg.in/juju/charm.v6-unstable into the tree <blocker> <ci> <packaging> <juju-core:Triaged> <juju-release-tools:Triaged> <https://launchpad.net/bugs/1450631>
[21:09] <sinzui> I will send an email to the list since it break all merges and CI testing
[21:19] <katco> sinzui: sorry i was in a meeting... TAL now
[21:22] <mup> Bug #1450631 was opened: Something is injecting gopkg.in/juju/charm.v6-unstable into the tree <blocker> <ci> <packaging> <juju-core:Triaged> <juju-release-tools:Triaged> <https://launchpad.net/bugs/1450631>
[21:24] <jw4> sinzui: it looks like it may be the github.com/juju/jujusvg repo that has a reference to gopkg.in/juju/charm.v6-unstable
[21:25] <katco> jw4: ty
[21:25] <jw4> sinzui, katco: I wonder if referring to jujusvg through gopkg.in would resolve this?
[21:25] <sinzui> jw4, uhg, we didn't change our dep of github.com/juju/jujusvg to get it though.
[21:25] <sinzui> jw4, maybe
[21:26] <sinzui> ps jw4, did you get credentials to see test results?
[21:26] <jw4> sinzui: not yet
[21:26] <jw4> sinzui: alexisb is still working on that :)
[21:26] <sinzui> okay, I will see If I can get that to you tommorow jw4
[21:28] <jw4> sinzui: very likely the trigger: https://github.com/juju/jujusvg/pull/28
[21:29] <jw4> sinzui: we could ask jujusvg folks to tag our revision<PHONE_NUMBER>3926ce903491c14a07cdc5cb371adb as v1 maybe
[21:29] <jw4> sinzui: then we might be able to use gopkg.in
[21:29] <jw4> s/our revision/their revision/
[21:30] <sinzui> jw4, katco: while changing our dep to jujusvg in every branch might work around this issue, we cannot go back and change branches we aren't developing. Since we did an unplanned build of 1.22.3 today, I worry that we will not be able to respond to emergencys in older jujus
[21:31] <jw4> sinzui: jujusvg is not in dependencies.tsv for 1.22
[21:31] <sinzui> oh, I see what you are saying jw4. I think you are right. and this means that older branches are probably not affected
[21:32] <sinzui> jw4, jobs that make the tree will always reject when a package is not documented appears in the tree.
[21:33] <jw4> sinzui: yeah... I'm hoping that using gopkg.in it will pull in only the tagged versions and not the master revisions
[21:33] <jw4> sinzui: I haven't verified that yet though
[21:33] <katco> jw4: i think you are correct
[21:33] <jw4> sinzui: but we can't use gopkg.in on jujusvg until it's tagged
[21:34] <jw4> (otherwise we just get the default v0 which is master)
[21:35] <sinzui> Makyo, ^ maybe you can help tag jujusvg so that we can build juju again
[21:35] <jw4> Makyo: if we could tag revision
[21:35] <jw4><PHONE_NUMBER>3926ce903491c14a07cdc5cb371adb as v1
[21:36] <jw4> in jujusvg that might help us with this CI issue
[21:36] <sinzui> Makyo, or someone you know. We are getting gopkg.in/juju/charm.v6-unstable pulled into the juju tree. since it is not documented, the merge and build jobs break
[21:36] <jw4> Makyo: it might even be better if v1 was a branch vs. a tag
[21:38] <sinzui> jw4, I might have permission to tag it!
[21:38] <jw4> sinzui: woot!
[21:38] <sinzui> well yes I can tag, lets see if I can push tags
[21:42] <sinzui> jw4, is this what you expect for the tag command?
[21:42] <sinzui> git tag -a v1 -m "Version 1 for gopkg.in."<PHONE_NUMBER>3926ce903491c14a07cdc5cb371adb
[21:42] <sinzui> just "v1"
[21:42] <katco> what branch is this being triggered on? 1.24?
[21:42] <sinzui> katco, every branch!
[21:42] <jw4> katco: 1.24 and master
[21:42] <katco> godeps -u dependencies.tsv && cat dependencies.tsv |awk '{print $1}' |xargs -I % grep -r "charm.v6" $GOPATH/src/%
[21:42] <katco> this is not giving me anything useful
[21:42] <sinzui> 1.23 1.24 and all the feature branches
[21:42] <jw4> katco: it's a transitive dependency
[21:43] <sinzui> katco, hence we know something happened outside of juju
[21:43] <jw4> katco: github.com/juju/jujusvg master refers to charm.v6
[21:43] <katco> jw4: right, so i am searching all of juju-core dependencies for charm.v6
[21:43] <katco> and i'm not finding anything?
[21:43] <jw4> katco: exactly
[21:43] <jw4> katco: that's why CI is complaining
[21:43] <sinzui> katco, that is the error, you will not find it because it is not supposed to be there..
[21:43] <jw4> CI compares what go get builds against dependencies.tsv
[21:44] <katco> jw4: no as in, none of juju-core's dependencies are referencing charm.v6-unstable
[21:44] <jw4> katco: that's the problem jujusvg does
[21:44] <sinzui> katco, and all merging branches, not just ci
[21:44] <jw4> but not in the version that's pinned
[21:44] <sinzui> jw4, is the tag just "v1"
[21:44] <jw4> sinzui: yeah I think so
[21:45] <katco> jw4: but if not in the version that's pinned, why is it causing problems? effectively juju is not utilizing a version of jujusvg that is referencing charm.v6?
[21:45] <jw4> katco: so "go get" pulls down jujusvg master which refers to charm.v6, causing charm.v6 to be pulled down
[21:45] <Makyo> sinzui, jw4 Will gladly tag, but I'm a little curious, why is jujusvg showing up in core?
[21:46] <katco> jw4: so the ci server is doing a go get, and not a godeps?
[21:46] <jw4> katco: even go deps does a go get first before syncing to the right revision
[21:47] <jw4> Makyo: good question
[21:47] <sinzui> katco, merge might be, but the rules to make the tar ball don't besides, I think godeps is still calling git to do something which is still the problem
[21:47] <katco> jw4: so the issue is that charm.v6 exists at all on the CI server?
[21:47] <Makyo> jw4, jujusvg's only consumer should be charmstore
[21:47] <katco> jw4: not that juju-core uses it?
[21:47] <jw4> katco: exactly
[21:47] <katco> jw4: thx for walking me around the block on that
[21:47] <jw4> katco: because CI checks that all dependencies downloaded are accounted for
[21:47] <sinzui> katco, not at all
[21:48] <jw4> Makyo: it's in our dependencies.tsv, but it's not actually referred to in code... I think it's a transitive dependency
[21:48] <jw4> Makyo: gimme a sec to figure out the third level up :)
[21:48] <sinzui> katco, anyone who tries to get juju using go get or godeps is getting a tree witn unised deps because Go's use of git is to always checkout master.
[21:49] <Makyo> jw4, ack, thanks.  I'll work on tagging.
[21:49] <jw4> Makyo: it's charmstore.v4 that's using it
[21:49] <sinzui> katco, There are jobs owned by Core to do merging, and jobs owned by QA to make release tarballs for testing. Both jobs fail because the tree contains a package that us not Used. Ubuntu requires us to abort. We cannot accept a unused an undocumented dep
[21:49] <jw4> Makyo: so it's a legitimate transitive dependency
[21:50] <katco> sinzui: i understand now. ty
[21:50] <sinzui> I might be a minute from fixing this if someone can config the tag is just "v1"
[21:50] <Makyo> jw4, alright, thanks
[21:50] <jw4> sinzui: Makyo will tag for us... (thanks Makyo)
[21:51] <katco> well it sounds like you guys have this under control, and i'm well past eod and need to get dinner going
[21:51] <katco> i'll see you all around
[21:51] <jw4> katco: control is an illusion
[21:51] <jw4> katco: ttyl
[21:51] <katco> jw4: later morpheus ;0
[21:52] <katco> ;)
[21:52] <jw4> haha
[21:53] <sinzui> I think my main dislike of Christmas is lack of control. I don't like surprises, even if they are gift wrapped.
[21:53] <jw4> sinzui: I'm so there... I hate surprises :)
[21:57] <Makyo> jw4, sinzui gopkg.in/juju/jujusvg.v1 should now work.  I went with 890de36 because that's the commit before charm.v6 was added, but after the NewFromBundle() api solidified.
[21:57] <Makyo> jw4, sinzui if need be, I can roll it back.  I went with a branch for v1
[21:57] <jw4> Makyo: actually I preferred a branch
[21:58] <jw4> Makyo: that should be fine
[21:58] <jw4> Makyo: thanks@!
[21:58] <Makyo> jw4, np, ping if anything else comes up around that.
[21:58] <jw4> sinzui: now for the test
[21:58] <jw4> Makyo: will do
[21:58] <sinzui> jw4, shall I just ask CI to start again?
[21:59] <jw4> sinzui: we have to update dependencies.tsv... but I just realized... charmstore will have to use the gopkg version
[21:59] <sinzui> :?
[21:59] <sinzui> Well this is a pickle
[21:59] <jw4> sinzui: because it's charmstore that actually causes the transitive download of jujusvg
[22:00] <jw4> sinzui: a veritable dilly of a pickle
[22:01]  * sinzui ponders a hack to just purge undocumented deps
[22:01] <jw4> sinzui: the good news is, it looks like the gopkg.in version works without pulling in charm.v6
[22:02] <sinzui> :)
[22:02] <jw4> sinzui: so now we just need to get a PR in to charmstore...
[22:03] <wallyworld> sinzui: i'm back now, catching up on irc croll back
[22:04] <Makyo> jw4, sinzui will +1 it
[22:04] <Makyo> I will, that is.  Vague.
[22:04] <jw4> Makyo: hehe
[22:11] <sinzui> wallyworld, jw4: My family insists we celebrate the mixed news my son got into advanced academics and the IRS sent me a $326,000 bill. When  I might hack the scripts to ignore the bad package so that we can test what we have. We are not planning to releasing any of th development branches this week
[22:11] <jw4> sinzui: that's crazy - congrats on one of those bits of news
[22:12] <sinzui> :)
[22:12] <jw4> sinzui: okay - it looks like I'll need at least 2 PR's to convert to gopkg.in anyway
[22:14] <wallyworld> sinzui: oh wow
[22:14] <wallyworld> go have fun and drown your sorrows
[22:14] <wallyworld> surely that bill is a mistake
[22:37] <jw4> Makyo: I think we're going to need the v1 branch to start right at<PHONE_NUMBER>3926ce903491c14a07cdc5cb371adb, and then I'll do a PR to update internal references to github.com/juju/jujusvg to use gopkg.in/juju/jujusvg.v1
[22:38] <jw4> Makyo: the problem is the head of the v1 branch has some breaking API changes (IconFetcher interface) that would cascade out
[22:39] <Makyo> jw4, ack, sounds good.
[22:39] <Makyo> jw4, otp, will do after
[22:39] <jw4> Makyo: thanks...
[22:39] <jw4> Makyo: I'll be in and out the next few hours, but appreciate it whenever you get that change in
[22:39] <Makyo> jw4, np, will do
[22:41] <Makyo> jw4, git's amazing and now that's done, I think.
[22:41] <jw4> suh-weet!
[22:41] <jw4> Makyo: thanks again


[01:18] <leftyfb> sarnold: you mean to tell me you weren’t an Ubuntu member?
[01:18] <sarnold> leftyfb: IKR?
[01:19] <sarnold> leftyfb: a few years ago tsimonq2 suggested I apply, but when I asked around for another endorsement on my wiki page no one bothered, and then I got distracted, hehe
[01:20] <leftyfb> Does it just need to be another member to endorse? If so, I would have done it had I known. Oh well
[01:23] <leftyfb> Been a member for 15 years now :)
[01:23] <sarnold> hehe
[01:23] <sarnold> leftyfb: the wiki page says "They do not need to be Ubuntu Members, just a part of the community"
[01:24] <leftyfb> that could mean anything
[01:24] <sarnold> I know I've left testimonials on folks going for core-dev kinds of things before, even without being a member, it seemed fine :)
[01:25] <leftyfb> Well, welcome nonetheless :)
[01:25] <sarnold> thanks :) hehe
[01:26] <leftyfb> Get yourself a fancy email?
[01:27] <sarnold> I wasn't planning on the email address, that feels like it'd mostly be a spam collector
[01:27] <leftyfb> It is, but Gmail does a great job with 99.99% of it
[01:32] <leftyfb> Fun fact, my boss when I worked at canonical sent an email to the local LoCo list looking for someone to work on his team at canonical which got marked as spam. Luckily I skim my spam folder and saw it and replied and got the job.  :)
[01:33] <leftyfb> Was also lucky that nobody else seems to either get or check the list email anymore so I was the only one that replied
[01:34] <daftykins> :)
[01:35] <sarnold> it went into everyone's spam folder? :) hehe
[01:36] <leftyfb> Not sure, maybe
[01:37] <leftyfb> Either way, it was a good 3 years at canonical. If I weren’t happy at my job(a recent change after the past couple years of working for a tyrant) I’d push hard to try to get another job there
[01:41] <sarnold> leftyfb: ugh :( sorry to hear about the tyrant, that really sucks the soul :(
[01:41] <sarnold> leftyfb: good thing it's better now :)
[01:41] <leftyfb> It’s ok now.  He made me want to leave for the past couple years he was there though
[01:43] <sarnold> years ;(
[01:43] <leftyfb> That type of stress isn’t worth it. I had that at a previous company and didn’t realize until I left and my wife told me I was a different person since leaving
[03:08] <lotuspsychje> good morning
[05:48] <ducasse> good morning
[07:35] <lnxsoul> good morning
[08:39] <Deano59> good morning. :)
[09:51] <Walex2> It's actualla morning here too in the center of Europe.
[10:11] <Deano59> Walex2: it's nearly noon.


 Where reported, the fact that certified equipment is not working on a newer version of kenel?
[06:14] <maxb> aa
[06:14] <maxb> oops
[06:14] <system0x01> It is part of a notebook-G1 455 Hp
[06:15] <system0x01> rt3290 wifi + bluetooth combo, where part of the wifi works and some Bluetooth adapters do not.
[06:16] <system0x01> Ubuntu 14.04 kernel 3.13.0-33-generic
[06:17] <system0x01> Official drivers  for linux on the HP website are only a SLED-11 and is kernel version 2 in front.
[07:51] <seb128> good morning desktopers
[07:51] <seb128> bregma, hey, do you know about password login not working on unity8-desktop-mir? do you know if there is a workaround?
[07:52] <didrocks> hey seb128!
[07:53] <seb128> lut didrocks ;-)
[07:53] <willcooke> morning
[07:53] <didrocks> hey willcooke
[07:53] <BigWhale> Greetings everyone.
[07:53] <willcooke> seb128, password login is re: Mark's problem, right?
[07:53] <didrocks> morning BigWhale
[07:54] <seb128> willcooke, yes, but I'm seeing it since they landed "proper" pam support
[07:54] <willcooke> ah, kk
[07:54] <seb128> hey willcooke
[07:54] <seb128> hey BigWhale
[07:54] <willcooke> seb128, thanks for for looking in to it already
[07:54] <BigWhale> hello didrocks, seb128 :)
[07:54] <seb128> willcooke, I had a workaround to bypass the lock, but the bug I was exploiting got resolved in recent updates
[07:54] <willcooke> hahah!
[07:55] <seb128> willcooke, yw, it's blocking me as well anyway, can't log in since yesterday
[07:55] <willcooke> seb128, sounds like the qt5-defaults thing is on it's way to being fixed too
[07:55] <BigWhale> Will I get flogged for asking when will Mir land in Ubuntu and will be turned on by default? :)
[07:55] <seb128> willcooke, is it? I'm reading Mirv's reply for a 3rd time, and I'm not sure to see any decision/way forward picked there
[07:55] <seb128> willcooke, or I'm not awake yet
[07:55] <willcooke> BigWhale, :)  at some point between now and 16.04.  Most likely to be ready in time for 16.04
[07:56] <seb128> seems like "we need our wrapper, but nobody is working on it"
[07:56] <didrocks> seb128: yeah, seems like the email is "it's the way it is" without any guidance on how we move forward
[07:57] <BigWhale> willcooke, thanks. :) Now I'll have to go bug Mir people about screen capturing stuff.
[07:57] <willcooke> BigWhale, :)  go for it!  I think I read something about VNC (or similar) working, or being planned to work, so it must be possible
[07:58] <willcooke> seb128, didrocks, ahh I read the email from Mirv "done" to mean it was fixed.  I didn't read it properly :/
[07:58] <seb128> willcooke, replied to that
[07:58] <willcooke> seb128, ha - yes, what you said in your email
[07:58] <willcooke> :)P
[07:59] <willcooke> ok, got to take the boy to child care - bbiab
[07:59]  * didrocks didn't get seb128's answer yet
[08:01] <happyaron> didrocks: https://bugs.launchpad.net/bugs/1356222
[08:01] <didrocks> thanks happyaron, will look at that quickly
[08:01] <happyaron> great
[08:01] <seb128> didrocks, I didn't reply on the list, I replied to a private "can you look at that" from Pat to Mirv on which one I was Cced
[08:02] <didrocks> ah ok
[08:02] <didrocks> waow, that's a very long Mir
[08:02] <didrocks> MIR*
[08:02] <seb128> I'm pondering replying on the list, but I want the reply to be a bit more diplomatic there
[08:02] <didrocks> happyaron: please ensure that all packages have a desktop team member subscribed to bug reports
[08:03] <seb128> happyaron, do you have a team for that? if not, I can subscribe desktop-bugs
[08:03] <Laney> hellooooooooooooooOOOOOOOOOOOOOOoooooooooooooooo
[08:03] <seb128> oh, a Laney!
[08:03] <seb128> hey Laney, wb!
[08:03] <seb128> did you recover from all the China fun? ;-)
[08:03] <Laney> I think I forgot what normal life is like
[08:03] <didrocks> morning Laney!
[08:03] <happyaron> seb128: please do with desktop-bugs
[08:03] <seb128> does it feel good or boring? ;-)
[08:04] <Laney> but yes, climbing and exploring town and going to the pub
[08:04] <Laney> it's nice ;-)
[08:04] <Laney> hey didrocks
[08:04] <Laney> how are you guys?
[08:04]  * seb128 played tennis yesterday
[08:04] <seb128> good!
[08:05] <Laney> hmm, pilot iain.lane today
[08:05]  * Laney moves to this afternoon
[08:06] <didrocks> I'm great as well. Happy to be able to exercise again :)
[08:06] <happyaron> Laney: some guys are waiting for the seed changes, :)
[08:06] <Laney> they should get some patience!
[08:06] <happyaron> haha
[08:06] <Laney> happyaron: you want to ping slangasek?
[08:07] <seb128> didrocks is addict to his exercice it seems ;-)
[08:07] <happyaron> Laney: better check ur mailbox first and see what they want
[08:07] <Laney> happyaron: nothing, just asking what is up
[08:07] <Laney> happyaron: I'd just ask slangasek if he and xnox finished their review, maybe you want to do that?
[08:07] <didrocks> seb128: I'm and I should! did you see this MIR? :p
[08:08] <didrocks> I would appreciate if some code sanity check could be perform by happyaron as well
[08:08] <didrocks> so that I'm not alone to review all of them
[08:08] <seb128> didrocks, being addict is never such a good thing, but yeah some exercice is nice ;-)
[08:08] <seb128> didrocks, not yet, I'm about to open it to subscribe desktop-bugs to the components though
[08:08] <happyaron> Laney: I'm ok if you want
[08:08] <happyaron> didrocks: what kind of check?
[08:08] <Laney> okay, please do
[08:09] <didrocks> happyaron: read the code, see if there is any potential crasher and flag any exec/system call to see if anything can be racy or dangerous
[08:11] <happyaron> didrocks: that's already done for fcitx itself and fcitx-qimpanel, others are not all covered I think
[08:11] <didrocks> happyaron: so yeah, we need to have that for every source package of this MIR
[08:12] <happyaron> didrocks: ok, will get back to you tomorrow
[08:12] <happyaron> can't finish that quickly today..
[08:12] <didrocks> happyaron: I'll do some as well, but better to double check
[08:12] <didrocks> yeah ;)
[08:13] <didrocks> I guess this MIR will take me my last couple of days before holidays anyway
[08:14] <happyaron> :)
[08:18] <seb128> jdstrand, hey, thanks for the evince bugfix-apparmor upload, do you plan to SRU that to trusty as well? (I guess some of those issues happen in the LTS)
[08:19] <Laney> why is /run/user/1000/ specified explicitly?
[08:20] <willcooke> it's a busy hive of activity in here today :)
[08:21] <seb128> willcooke, that's quite common for this channel, when people are not on holidays ;-)
[08:21] <willcooke> :D
[08:21] <Laney> ffs
[08:22] <Laney> Unpacking libmircommon-dev:amd64 (0.6.0+14.10.20140811-0ubuntu1) ...
[08:22] <Laney> dpkg: error processing archive /var/cache/apt/archives/libmircommon-dev_0.6.0+14.10.20140811-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/mircommon/mir/graphics/native_buffer.h', which is also in package mircommon-dev:amd64 0.5.1+14.10.20140728-0ubuntu1 /var/cache/apt/archives/libmircommon-dev_0.6.0+14.10.20140811-0ubuntu1_amd64.deb
[08:22] <willcooke> erk
[08:22] <seb128> Laney, the "1000" being coded seems like an overlook/bug, maybe reopen the bug/open a new one?
[08:23] <seb128> Laney, you might want to mention the mir upgrade issue on #ubuntu-ci-eng
[08:23] <Laney> have commented
[08:24] <Laney> sec, bet there will be a bug report
[08:24] <seb128> thanks
[08:24] <Laney> apparently not!
[08:24] <seb128> I bet you a thousand euros! :p
[08:24] <Laney> NO BET
[08:24] <seb128> :-(
[08:28] <seb128> Laney, can you retry the u-s-s autopkgtests?
[08:28] <Laney> seb128: anyone can
[08:28] <Laney> you need to log into d-jenkins and then press build on the page
[08:28] <seb128> let me try on the private jenkins
[08:28] <seb128> I was on the public one, but I don't know my login/password
[08:29] <Laney> yeah you need to be on that one sadly
[08:29] <Laney> you mean ussoa, right?
[08:29] <Laney> I don't think uss itself has adt tests
[08:29] <seb128> yes
[08:30] <Laney> http://d-jenkins.ubuntu-ci:8080/view/Utopic/view/AutoPkgTest/job/utopic-adt-ubuntu-system-settings-online-accounts/ → build now
[08:30] <seb128> yeah, I just started one
[08:31] <seb128> but it failed 3 times on i386
[08:31] <seb128> I wonder if there is a real issue there
[08:31] <Laney> probably
[08:32] <seb128> I hate arch specific issues
[08:34] <seb128> those logs have dbus timeouts trying to get datas from the server
[08:39] <seb128> shrug, of course it fails
[08:58] <Laney> there were llvm changes afaics
[08:58] <Laney> did you try running the test locally?
[09:02] <seb128> trying to
[09:02] <seb128> I wish those tools were easier to use
[09:03] <seb128> I need to build a vm to be able to run those?
[09:03] <Laney> http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test
[09:04] <seb128> Laney, yeah, I was on this page, running adt-buildvm-ubuntu-cloud which takes ages
[09:05] <Laney> it downloads a cloud image which is like 250M
[09:05] <seb128> I guess I'm going to do something else and come back to that later
[09:05] <seb128> I've several machines dist-upgrading and stuff, my dsl is not liking it
[09:05]  * seb128 tries to run the tests without the vm
[09:12] <Laney> yeah this TOTALLY happens locally too
[09:14] <seb128> bah
[09:14] <seb128> FileNotFoundError: [Errno 2] No such file or directory: 'qemu-system-i686'
[09:14] <seb128> when doing "adt-run ubuntu-system-settings-online-accounts --- qemu adt-utopic-i386-cloud.img"
[09:15]  * seb128 symlinks i386->i686
[09:20] <Laney> yeah downgrading mesa fixes it
[09:20] <Laney> also moves to llvm 3.4
[09:41] <seb128> Laney, bah :-/
[09:41] <seb128> Laney, should we override the test then to let settings migrate? there is no point blocking u-s-s over a llvm bug
[09:41] <Laney> is anybody going to look at it?
[09:42] <seb128> to what? llvm?
[09:42] <Laney> yes
[09:42]  * seb128 looks at who did the update
[09:43] <seb128> doko?
[09:43] <Laney> I mean sure we can override stuff but having things become and then stay broken is pretty poor
[09:43] <seb128> right
[09:43] <seb128> but blocking u-s-s to be updated on the touch image doesn't help us to get llvm fixed
[09:44] <seb128> it's quite orthogonal
[09:44] <Laney> in some ways it does
[09:44] <seb128> by creating frustration on more people
[09:44] <Laney> because people want it to move forward therefore have an incentive to fix the other thing
[09:44] <seb128> which leads to them complain more ?
[09:44] <seb128> I think it creates more frustration and angry people as a side effect
[09:44] <Laney> so if I force-skiptest now then nobody is going to look at llvm, I would bet a thousand euros on that
[09:44] <seb128> right
[09:45] <seb128> and I bet you money that if we don't skip it, people are going to complain and get annoyed
[09:45] <seb128> but none is going to look at llvm
[09:45] <seb128> because the people working on settings ahve no clue about that stack
[09:45] <seb128> and we are going to end up overriding the test
[09:45] <seb128> with just more frustration build up meanwhile
[09:45] <Laney> you're saying that it will never get fixed
[09:45] <Laney> the actual first thing to do is to ask doko
[09:46] <seb128> yeah, I'm typing on -devel :p
[09:47] <seb128> Laney, I'm not saying it's not getting fixed, but I doubt taking touch people hostage is going to help fixing it
[09:48] <Laney> What I am saying is
[09:49] <Laney> that if we find out something is broken
[09:49] <Laney> then it is way better to have the problem fixed than to ignore the breakage
[09:49] <seb128> sure
[09:49] <seb128> and I agree with that
[09:49] <Laney> so we ask the person who is most likely to be able to fix it
[09:49] <Laney> and then depending on what they say we will take one action or another
[09:49] <seb128> I agree with all of that
[09:50] <seb128> it's just that u-s-s being blocked doesn't seem to help with any of those actions
[09:50] <Laney> I've fixed bugs many times because things were blocked in proposed
[09:51] <Laney> it's just a fact that it often turns up things which weren't the fault of the upload
[09:51] <seb128> it feels wrong that we need such incensitives to fix bugs
[09:51] <seb128> we should fix bugs because things are buggy
[09:51] <seb128> not because they are blocking other things
[09:51] <seb128> like it happens that u-s-s is blocked now
[09:51] <Laney> this is a way of making prioritisation happen
[09:52] <seb128> but that bug would be worth fixing evne if that was not the case
[09:52] <seb128> fair enough
[09:52] <Laney> fo
[09:52] <Laney> erm
[09:52] <seb128> it just creates frustration and stress on the way
[09:52] <seb128> which I don't like
[09:52] <Laney> does this break all autopilot tests under qemu?
[09:52] <Laney> like are we just going to have to skip them all?
[09:52] <Laney> on i386
[09:52] <seb128> dunno
[09:52] <seb128> let me look at some other components
[09:53] <Laney> anyway, I probably will skip it, just want to get doko's attention first at least
[09:53] <seb128> looking at https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/ it seems not
[09:54] <seb128> or maybe not "not"
[09:54] <Laney> yeah I don't think we have so many running AP
[10:13] <Laney> ok that looks good ;-)
[10:15]  * Laney skips it
[10:15] <seb128> thanks
[10:21] <mishravikas> hi all I want to start contributing to the desktop team and any help would be appreciated in order to get me started with fixing small bugs
[10:23] <willcooke> hey mishravikas - that's great!
[10:23] <mishravikas> willcooke: hey!
[10:23] <willcooke> can you tell us a bit about your expertise, so we know where your skills are?
[10:24] <mishravikas> willcooke: am not a very experienced programmer but  I am pretty confident in C/C++ and Python, am also a GSoC 2014 student
[10:24] <willcooke> cool
[10:25] <mishravikas> willcooke:are there any such prerequisites?
[10:25] <willcooke> nah - just good to get a feeling for what sort of things you're interested in
[10:26] <mishravikas> willcooke: ok :) the fact is that right now I haven't done much of development so dont really have an interest but this is for sure that I want tocontribute to ubuntu
[10:27] <mishravikas> willcooke: by interest I meant specific interest
[10:27] <willcooke> so seb128 and didrocks (amongst many others) will be able to point us in the right direction.  Guys, are the paper cuts bugs still needing some attention?
[10:28] <willcooke> mishravikas, do you have a Launchpad account already?
[10:28] <mishravikas> willcooke: yeah I created It just now
[10:28] <willcooke> cool
[10:28] <willcooke> https://launchpad.net/~canonical-desktop-team/+assignedbugs
[10:28] <willcooke> rather, https://bugs.launchpad.net/~canonical-desktop-team
[10:29] <willcooke> bah - sorry, thats still the wrong link
[10:29] <willcooke> one sec..
[10:30] <willcooke> right, finally....
[10:30] <willcooke> mishravikas, https://launchpad.net/~ubuntu-desktop
[10:30] <willcooke> thats our home
[10:31] <mishravikas> willcooke: ok, so how do I join this team?
[10:31] <willcooke> I think we have to add you, but there are some hoops to jump through first :)
[10:32] <mishravikas> willcooke: ok sure and what are those?
[10:32] <willcooke> mishravikas, https://wiki.ubuntu.com/DesktopTeam/Developers
[10:32] <darkxst> Hey Laney, seb128
[10:33] <darkxst> any update on gnome-desktop?
[10:33] <willcooke> mishravikas, have a read of this too:  https://wiki.ubuntu.com/DesktopTeam
[10:33] <Laney> mishravikas: do you have a favourite package?
[10:34] <Laney> it might be a nice idea to browse its bugs list in Launchpad or on bugzilla.gnome.org and see if a bug seems fixable to you
[10:34] <mishravikas> Laney: no, not yet
[10:34] <Laney> darkxst: robert put some branches up but I haven't reviewed them yet
[10:34] <Laney> darkxst: let me fwd you the email, I'd appreciate you looking if you have some time
[10:36] <Laney> there
[10:36] <mishravikas> Laney: I'm open to working on any package right now as I dont have any such preferences since I want to start right now so it would be better if you guys can point me out to some good first bugs
[10:36] <mishravikas> willcooke: quite a lot to be done to become a member of the team :p
[10:37] <Laney> that team gives you upload access to part of Ubuntu so it has a high barrier
[10:37] <mishravikas> Laney: yeah but am up for the challenge :)
[10:38] <mishravikas> Laney: are there any packages in python since am more comfortable in Python?
[10:39] <darkxst> Laney, looking
[10:41] <darkxst> odd choice naming everying gsd_
[10:42] <Laney> mishravikas: hmm, most stuff is C/Vala, two python ones that I can think of are usb-creator and ubiquity (which is the installer)
[10:45] <mishravikas> Laney: are there and small bugs in usb-creator and ubiquity which I can look on? and is there a list somewhere explaining about all the packages?
[10:50] <Laney> mishravikas: each package has a bug list but I don't have an idea of which ones are easy in my head, sorry
[10:50] <Laney> e.g. usb-creator is https://bugs.launchpad.net/ubuntu/+source/usb-creator
[10:50] <willcooke> ubiquity: https://launchpad.net/ubiquity
[10:50] <Laney> and there's no list of every package but each one has a description which you can see in the software centre or if you type "apt show <package>" in your terminal
[11:01] <willcooke> mishravikas, while we think about something which would be good for you to work on I'd suggest that you come to the next Desktop meeting, which happens on Tuesdays at 1530 UTC
[11:01] <willcooke> then we'll have most of the team in the same place at the same time, and we can really thrash out the details
[11:02] <darkxst> Laney, u-s-d and u-c-c look to just be cut+paste and renames so should be fine
[11:02] <darkxst> no idea about unity-greeter
[11:03] <Laney> could you comment on the MPs?
[11:04] <darkxst> Laney, sure
[11:04] <Laney> ty
[11:04] <Laney> probably look at that tomorrow
[11:06] <darkxst> Laney, ok thanks, FF is so close and we still need upower as well, some things never change I guess ....
[11:07] <Laney> how's upower going?
[11:07] <darkxst> Laney, I think its really only the touch and other canonical bits that need work
[11:08] <darkxst> I have patchsets that should apply to u-s-d/u-c-c
[11:09] <Laney> well I'm sure people will take patches for those if they are provided
[11:09] <Laney> I'm going to do ubuntu-system-settings this week probably but that should be a small one
[11:09] <Laney> hopefully
[11:09] <darkxst> though I suspect backporting power plugin (and reverting the few gnome-desktop changes) might be nicer
[11:10] <darkxst> Laney, things like powerd and power-indicator still need porting
[11:11] <Laney> I don't have a way to make people do this work, sorry
[11:12] <mishravikas> willcooke: ok I'll come for it, same channel right?
[11:12] <willcooke> mishravikas, yeah
[11:43] <didrocks> willcooke: back from running!
[11:43] <didrocks> willcooke: FYI (seeing that mishravikas isn't around anymore), there is as well this page: https://wiki.ubuntu.com/ContributeToUbuntu
[11:43] <darkxst> hey didrocks, any update on tracker MIR?
[11:44] <didrocks> darkxst: just back from Guadec + China, i'm on another big MIR, but I'll get to it before tomorrow
[11:44] <didrocks> hey ;)
[11:44] <didrocks> darkxst: all was great, I just need to check why I pinged you about this .symbols files
[11:44] <didrocks> the shlibs not matching library name, I'm sure I didn't dream :)
[11:46] <darkxst> didrocks, I am pretty sure the shlibs is correct
[11:47] <didrocks> darkxst: let me retry a quick build while we are talking about it
[11:47] <darkxst> the first few are private shared libraries only used by tracker
[11:47] <darkxst> /usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-common.so.0.0.0
[11:47] <darkxst> /usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-extract.so.0.0.0
[11:47] <darkxst> /usr/lib/x86_64-linux-gnu/tracker-1.0/libtracker-data.so.0.0.0
[11:49] <didrocks> yeah, I was referring to the public ones, of course
[11:49] <didrocks> < build in progress >
[11:49] <didrocks> btw, thanks for the RPATH fix :)
[11:50] <jdstrand> seb128: re evince> hey, I could, but getting all the bug paperwork, etc in order will take a while and I wouldn't be able to get to it any time super soon
[11:52] <darkxst> didrocks, test counters are also fixed now in upstream 1.1 branch, will look at backporting those next time I do an upload
[11:52] <didrocks> oh, excellent news! :)
[11:52] <didrocks> ok, build finished, let's redo a sanitization check
[12:04] <seb128> jdstrand, k, let me know if you need help with the paperwork, I might be able to do that
[12:04] <seb128> jdstrand, btw did you see Laney's comment on one of the bugs?
[12:04] <seb128> jdstrand, you coded the 1000 uid in one of the profile changes
[12:04] <jdstrand> I did!
[12:04] <jdstrand> yikes
[12:04]  * jdstrand reviews the debdiff
[12:05] <jdstrand> meh
[12:05]  * jdstrand fixes
[12:05] <seb128> thanks
[12:06] <ogra_> 1000 is dead anyway 32011 is the future !
[12:06] <ogra_> :)
[12:08] <didrocks> darkxst: ok, all looks good, I +1 on it. Just ping me once it's seeded or something in main depends o nit
[12:08] <didrocks> on*
[12:08] <didrocks> I'll then promote it to main
[12:10] <jdstrand> seb128: so, if you wanted to do the paperwork, I'd be happy to do the upload, but if you are ok with waiting, I can get to it after tending to various rtm tings
[12:10] <jdstrand> things*
[12:11] <seb128> jdstrand, k, no hurry I guess. I'm keeping it on my "things to do when tired/not really able to focus" list ;-)
[12:15] <jdstrand> yes, it is on a similar list for me
[12:16] <darkxst> didrocks, thanks!
[12:16] <didrocks> yw!
[12:28] <didrocks> happyaron: can you recheck all your dependencies? You missed at least presage which is a build-dep
[12:58] <didrocks> happyaron: do you mind as well rechecking debian/copyright? I find quite a lot of things to fix
[12:59] <didrocks> in the future, when you open a MIR, you are supposed to check this :)
[13:08] <Laney> kenvandine: yo, I noticed that qtdeclarative5-ubuntu-content0.1 is still around in NBS because of camera-app and ubuntu-sdk-libs - any chance we could move those off it?
[13:09] <Laney> kenvandine: the Breaks from 1 to 0.1 torpedos the desktop-next image build. :)
[13:09] <kenvandine> i'll fix those too :)
[13:09] <Laney> it's been failing for a few days because of that
[13:09] <Laney> cheers!
[13:11] <seb128> mterry, hey, sorry for putting you on the hook for that unlock issue :-/
[13:11] <seb128> mterry, let me know if I can provide any useful debug info for it
[13:11] <seb128> mterry, basically I enter my password and the lockscreen "hangs", e.g it doesn't unlock/give feedback and you can't interact with it anymore
[13:12] <mterry> seb128, well...  that makes some sense.   I think we disable the UI while waiting for an answer from PAM
[13:13] <mterry> seb128, so I guess I wonder why we wouldn't hear back from PAM
[13:13] <seb128> mterry, were would be pam errors if there were any? unity8.log?
[13:13] <mterry> seb128, probably /var/log/auth.log, but might not be super verbose without 'audit' and/or 'debug' flags to pam_unix
[13:14] <seb128> let me try
[13:19] <seb128> mterry, no pam entry, it's like it was not trying to unlock it
[13:20] <mterry> seb128, hrm
[13:20] <mterry> seb128, we're probably doing something very dumb  :)
[13:23] <seb128> kenvandine, hey
[13:23] <seb128> kenvandine, did you let some of the u-s-s approved mps out of the landing on purpose yesterday?
[13:24] <seb128> kenvandine, I wonder why my "use ubuntushape instead if rectangle icon" 1 liner was left out ;-)
[13:24] <kenvandine> i missed it
[13:24] <kenvandine> i added it to the spreadsheet last night
[13:24] <kenvandine> but was waiting for the previous landing to migrate
[13:25] <seb128> kenvandine, that was blocked due to autopkgtest/llvm issues, we forced it in while those are being worked on
[13:25] <kenvandine> cool, thx
[13:25] <seb128> y
[13:25] <seb128> yw
[13:25] <kenvandine> i see someone created the silo, cool
[13:26] <seb128> nice
[13:44] <seb128> kenvandine, hum, using that applicationId doesn't work well
[13:44] <seb128> it gives me a "wants to access your Ubuntu One account" page, which I guess should have a name
[13:44] <Laney> is someone working on the uss test failures?
[13:44] <seb128> with an allow/don't allow button set, allow doing nothing
[13:44] <seb128> Laney, which ones?
[13:44] <Laney> https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-utopic/2199/
[13:44] <seb128> Laney, the llvm ones?
[13:44] <Laney> no
[13:44] <Laney> cellular
[13:44] <seb128> shrug
[13:44] <seb128> when did that start?
[13:45] <seb128> another ofono landing?
[13:45] <kenvandine> they were passing yesterday...
[13:45] <seb128> no ofono on -changes
[13:45] <Laney> that CI happened just now
[13:45] <seb128> one time off issue?
[13:45] <kenvandine> File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 243, in select_single
[13:45] <kenvandine>     raise ValueError("More than one item was returned for query")
[13:46] <Laney> could be an actual error in this branch
[13:48] <seb128> Laney, can you ping jgdx about it maybe?
[13:53] <kenvandine> sounds like a real problem, was it from his branch?
[13:54] <Laney> satoris
[13:54] <Laney> I commented on the mp
[13:54] <seb128> thanks
[14:02] <Laney> ah, crazy mvo branches
[14:04] <Laney> bzr bd -S → running the testsuite for some reason
[14:04] <Laney> :-)
[14:09] <Laney> and yet it doesn't run during the actual build
[14:09] <Laney> hahaha
[14:20] <chrisccoulson> hi qengho :)
[14:20] <chrisccoulson> have you seen there's a new chromium release?
[14:20]  * chrisccoulson hides
[14:22] <seb128> chrisccoulson, hey, how are you? ;-)
[14:22] <chrisccoulson> seb128, yeah, not too bad thanks. and you?
[14:22] <seb128> chrisccoulson, I'm good, thanks
[14:23]  * ricotz thinks it is better than the state of firefox in utopic :\
[14:26] <seb128> ricotz, not quite, chromium fails to load any page where firefox works mostly fine on utopic
[14:27] <chrisccoulson> That's what happens when we switch toolchain, I guess (the browsers are the bits of software that finds the compiler bugs)
[14:28] <ricotz> seb128, i see, i am not using chromium ;), i wanted to refer to the outdated 31 version and the imo premature upload of 32b1 without keeping it updated ;)
[14:29]  * darkxst can live with a broken browser, but mediascanner2 io deadlocking my system not so good, no idea how that even got installed here though
[14:29] <chrisccoulson> upstream's build is fine - it doesn't have issues like bug 1322784 and bug 1348333. it's only ours that is crap
[14:29] <chrisccoulson> ricotz, firefox needs a maintainer ;)
[14:32] <ricotz> chrisccoulson, ok, but this is not related to the problem afaics since trusty has a proper build and i assume it wouldn't be more than no-change rebuild on utopic
[14:34] <ricotz> chrisccoulson, packaging betas for the ppa is absolutely fine, but uploading them to the archive while not having the time to keep it updated is not useful
[14:35] <pesari> hey, in trusty, is there a way to completely disable user switching / multiple X sessions?
[14:38] <pesari> or at least prevent automatic switching to greeter while the screen is locked
[14:44] <seb128> hum
[14:44] <seb128> mterry, it seems to somewhat try to do something, because if I enter a wrong password a get an auth error in the log
[14:44] <mterry> seb128, that's promising...
[14:57] <ricotz> seb128, so chromium 36.0.1985.125-0ubuntu2 is broken? seems to work here
[14:57] <seb128> ricotz, on i386 at leaast
[14:57] <ricotz> i see, amd64 here
[15:13] <kenvandine> Laney, i don't think i can fixed the sdk-libs meta package until unity-webapps-qml makes it to the release pocket
[15:13] <kenvandine> Laney, it's in silo 6 now
[15:14] <kenvandine> i'll do the meta package as soon as that's done
[15:14] <Laney> kenvandine: that's just a suggests change?
[15:15] <kenvandine> it's a depends i think
[15:15] <kenvandine> in the sdk-libs meta
[15:15] <kenvandine> not the touch meta
[15:16] <kenvandine> but unity-webapps-qml depends on the old package name, and it's in the libs meta
[15:16] <Laney> I'm looking at https://launchpadlibrarian.net/182185413/unity-webapps-qml_0.1%2B14.10.20140731-0ubuntu1_0.1%2B14.10.20140813-0ubuntu1.diff.gz
[15:16] <kenvandine> oh... i guess you're right
[15:17] <kenvandine> i wonder what else could be squashing that when refreshing the meta package
[15:17] <kenvandine> and i wonder if that really should be a depends... it provides JS bindings to the QML bindings
[15:18] <Laney> you have to push the seed for the meta package to notice the change
[15:18] <kenvandine> not sure how that would deal with the qml bindings missing
[15:18] <Laney> anyways, I really only care that it's fixed before the daily iso build overnight. :)
[15:19] <kenvandine> Laney, oh... right... so i push the branch then run update?
[15:19] <kenvandine> before uploading the package?
[15:19]  * kenvandine hasn't done that in a while :)
[15:20] <Laney> correct
[15:20] <Laney> ./update will check it out and then regenerate from that
[15:20] <Laney> then build the package as you normally would and upload it
[15:32] <willcooke> qengho, having hangout problems all of a sudden - one sec
[15:33] <willcooke> qengho, ok sorted
[16:22] <didrocks> happyaron: few! MIR review done, finally (or at least first pass)
[16:22] <didrocks> happyaron: quite a lot to fix, some missing packages to add to the MIR or revoke, fixes in copyright and so on needed: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1356222/comments/1
[16:23] <didrocks> happyaron: I tried to categorize the different fixes/questions I have. Please poke me back once you have more info/made some changes, thanks!
[16:32] <seb128> bregma, hey, not sure I agree with your reply, targetting a form factor in the UI is wrong, calling a phone by its name in the UI isn't
[16:33] <bregma> what do you call other devices, like the popular HP and Acer convertible tablet/laptop combos?
[16:34] <bregma> "About this tablet/laptop convertible combo..."
[16:34] <seb128> bregma, the spec I pointed to has "about this phone" and "about this device" for !phone types
[16:34] <seb128> which seems reasonable to me
[16:45] <seb128> willcooke, re your holidays procedure email, do you know who can edit the calendar? I've access but I wonder if I'm in a group that has extra acls. Because if we all can edit/add our vacs to it, do you still want to act as a gateway/be the one adding those?
[16:46] <Laney> #distro?
[16:47] <Laney> what ever is up with my machine
[16:47] <Laney> switching tabs in firefox makes it hang for like 5 seconds
[16:47]  * Laney restarts ...
[16:47] <seb128> Laney, or query maybe, yeah sorry for spamming a public channel
[16:48]  * seb128 was unsure where to ask, nothing really private about the question
[16:48] <Laney> sure, not a big deal, just seems genuinely "company" ;-)
[16:48] <seb128> indeed ;-)
[16:54] <willcooke> seb128, yeah I'm happy to add them, its not bother for me
[17:02]  * didrocks waves good evening and good night
[17:04]  * Laney too, ttyl!
[17:04] <seb128> Laney, have fun!
[17:04] <seb128> going climbing?
[17:05] <Laney> not today, meeting up with a friend in the pub though ;-)
[17:07] <seb128> k ;-)
[17:28] <willcooke> eoding
[17:28] <willcooke> toodles
[17:36] <seb128> cyphermox_, hey, that n-m patch from the other day, you said you would SRU it "today", I don't see it in the queue ... is that still on your todolist?
[18:34] <cyphermox_> seb128: yes, it is, I'll get to it very soon
[18:40] <seb128> cyphermox_, k


[00:41] <Cheri703> hi
[01:22] <ronnoc> hi Cheri703! How have you been?
[01:22] <Cheri703> doing alright overall
[01:23] <ronnoc> How's Ubuntu-Ohio been? Not feeling too overwhelmed, I hope!
[01:24] <Cheri703> my to-do list is large, but not entirely u-ohio stuff :)
[01:25] <ronnoc> heh well that's a Good Thing :)
[01:31] <Cheri703> yeah, but I keep procrastinating :) though I have been productive in other ways this past week
[01:32] <Cheri703> am a bit discouraged though, my business isn't bringing in enough money, so I've been looking for some sort of side income, and no such luck so far :/
[01:33] <ronnoc> What is your business, if you don't mind me asking?
[01:33] <Cheri703> not too many office jobs in my area...mostly manufacturing around here
[01:33] <Cheri703> I do computer support/repair, etc
[01:33] <ronnoc> ahh... me too, and a bit of consulting, as my side job. I agree it seems to be rather feast of famine... :/
[01:34] <Cheri703> yeah
[01:35] <Cheri703> and I have a reasonable skill set, and type 84wpm (took a test the other day :) ) but...the temp places I went to haven't contacted me with anything, and most of the other places in town aren't hiring, or it's crappy retail or sales, which I don't want
[01:36] <Cheri703> there is a call center that apparently really wants me, but since I'm car free, I can't manage the hours they'd need
[02:37] <ronnoc> ahh we have a lot in common - I'm car-free too atm :)
[02:50] <Cheri703> yeah, I get along alright with the buses here
[04:38] <ronnoc> heh. not here, sadly :/
[13:34] <paultag> Cheri703: ever try out the trobber code?
[13:35] <Cheri703> not yet
[13:35] <Cheri703> might take a look after my errands later
[13:35] <paultag> righto
[14:02] <twotwozombie> morning all
[15:26] <thafreak> Mornin
[23:13]  * skellat grumblesmurfs
[23:15] <Unit193> Howdy, it's been mostly dead for a bit :P
[23:16] <skellat> This is my first day off from work in 10 days
[23:17] <skellat> Somebody went on maternity leave and I was suddenly pushed into almost over 40 hours
[23:17] <skellat> Considering that I am a part-timer, that's not cool
[23:18] <skellat> Will you be at OLF, Unit193?
[23:18] <Unit193> I would like to be a few days, but I should be able to make it to one
[23:19] <Unit193> Congrats on getting on Council ;)
[23:19] <skellat> Hunh?
[23:19] <skellat> Oh
[23:20] <skellat> I'm just there to record their open session
[23:20] <Unit193> So you should be for all days?
[23:20] <Cheri703> if I have independent transportation down to OLF, Unit193 is welcome to carpool with me
[23:20] <skellat> I only get that Friday
[23:20] <Cheri703> (still working out logistics of it all)
[23:21] <skellat> The only reason I get that Friday is because it is my 30th birthday
[23:21] <Unit193> Cheri703: Thanks, I do hope you can go down, but I don't know how I can help you in return :P
[23:23] <skellat> I dunno.  The whole field deployment for Erie Looking Productions is kinda open for debate.  I sent a note to Council asking that somebody call my engineer to discuss what they envision for ELP to do so that he can plan out equipment load.
[23:30] <Unit193> Oh stinking fish... http://www.extremetech.com/internet/92792-mozilla-takes-firefox-version-number-removal-a-step-further