[01:53] <hatch> jcsackett ahh thanks
[01:54] <hatch> huwshimi so any luck tackling it on your own?
[01:54] <huwshimi> hatch: I didn't mange to figure out anything yesterday :(
[01:55] <hatch> ok cool, I'll take a look
[01:56] <huwshimi> thanks heaps
[01:56] <hatch> huwshimi what if you include the juju-templates?
[01:56] <hatch> asically the error is because it can't find the element in the dom
[01:58] <huwshimi> I'll try
[01:59] <huwshimi> hatch: No change
[02:00] <hatch> blarg
[02:01] <hatch> ok I've pulled it down
[02:01] <hatch> will investimagate
[02:02] <huwshimi> hatch: Feel free to leave it to your work day, I have plenty to go on with.
[02:12] <hatch> huwshimi it's because it's rendering without the mv flag
[02:12] <hatch> it's rendering the old scaleup UI
[02:12] <hatch> if you put a debugger in the method that's failing and inspect the innerHTML of the container you can see this
[02:13] <huwshimi> Oh
[02:14] <hatch> huwshimi that's because the createServiceInspector method is no longer how we render the inspectors while under mv
[02:14] <hatch> so this is actually testing a path which is no longer valid
[02:15] <hatch> so really - the proper fix is to fix the way inspectors are rendered
[02:15] <hatch> for tests
[02:16] <hatch> but you may be able to hax around it by setting the mv flag and doing some other bits
[02:27] <huwshimi> yep, trying
[02:59] <hatch> huwshimi any luck?
[03:02] <huwshimi> hatch: Just having some lunch...
[03:02] <hatch> ok cool, I think I'm gona head and watch some tv, if you can't get it just leave the PR and I'll take a look in the am
[03:04] <hatch> have a good one
[07:21] <rogpeppe> urulama: morning!
[07:21] <urulama> rogpeppe: hey there
[07:22] <urulama> rogpeppe: how's it going?
[07:23] <huwshimi> rogpeppe, urulama: Morning
[07:23] <rogpeppe> urulama: not bad thanks
[07:23] <urulama> rogpeppe: i'm trying to finish the "sprint summary" document so that i can move forward with the implementation part, but it's taking tiiiiime :)
[07:23] <rogpeppe> urulama: have you recovered from last week yet?
[07:23] <urulama> huwshimi: good evening ;)
[07:23] <huwshimi> :)
[07:23] <urulama> rogpeppe: em ... partly recovered. progress bar at around 33% :)
[07:24] <rogpeppe> urulama: :-)
[07:27] <urulama> rogpeppe: we have a national holiday on Friday, might help to move to 50% :) and it's good to put things on paper as long as they are still in memory
[07:27] <rogpeppe> urulama: definitely
[07:29] <urulama> rogpeppe: i plan to jump on PRs and current implementation around noon (in 2h) ... would that be ok? any open questions or anything until then?
[07:29] <rogpeppe> urulama: no, all's good
[07:30] <urulama> rogpeppe: great to hear ... ok, back to tasks for the next 2 months
[07:32] <urulama> rogpeppe: oh, btw, how far have you and Francesco come regarding uploads?
[07:32] <rogpeppe> urulama: uploads now work
[07:33] <urulama> rogpeppe: as in "zip properly formatted dir" and upload and new charm is in charmstore?
[07:33] <rogpeppe> urulama: and you can now download individual archive files too
[07:33] <rogpeppe> urulama: yup
[07:33] <urulama> \o/
[07:34] <rogpeppe> urulama: ah, the only thing that's not done is that we don't currently verify bundles against the existing charms
[07:35] <urulama> rogpeppe: as in when bundle is uploaded it is not checked wether the charms are in the CS?
[07:35] <rogpeppe> urulama: yes
[07:35] <rogpeppe> urulama: we deliberately left it for a later PR - but it does need doing
[07:36] <rogpeppe> urulama: and there's also something i thought of in bed this morning
[07:36] <rogpeppe> urulama: which is that we can't always start revision numbers from zero
[08:00] <urulama> morning, frankban
[08:00] <frankban> morning urulama
[08:00] <frankban> urulama: are you able to connect to canonical IRC servers?
[08:00] <urulama> yes
[08:00] <urulama> frankban: but i've seen others being disconnected
[08:00] <frankban> urulama: uhm, ok
[08:01]  * TheMue has troubles too, also with SSO
[08:01] <frankban> urulama: I see "Connection failed. Error: Connection refused"
[08:01] <frankban> will try again later
[08:01] <frankban> switched to zsh, let's see how it works
[08:13] <urulama> frankban: next step acme? :)
[08:15] <frankban> urulama: http://www.nooooooooooooooo.com/
[08:15] <frankban> ;-)
[08:15] <urulama> :) :) :)
[08:16]  * urulama bookmarks the page for future use
[08:38] <urulama> frankban: ok, i have problems with cannonical irc as well, however, it manages to reconnect
[08:39] <frankban> urulama: ok
[10:45] <frankban> urulama, rogpeppe, jrwren: https://github.com/juju/charmstore/pull/69
[10:46] <urulama> frankban: finishing a doc, then lunch, then PR. ok with you? can move PR first if it is blocking anything else
[10:47] <frankban> urulama: it's ok thanks
[10:56] <rogpeppe> frankban: reviewed
[10:57] <frankban> rogpeppe: thanks
[11:40]  * urulama goes on short lunch
[12:26] <urulama> frankban: the tests currently check mostly if the time is there ... could we create a bit more complex test? starting with a charm revision at time 0, then upload new revision, one in the period T of time? Then, check if all revisions have proper n*T archive-upload time?
[12:29] <frankban> urulama: not sure if I understand. at the store level, we already check that the time is the expected one (in a specified timeframe)
[12:34] <urulama> frankban: suggestion is to have a "possible" reggression test, that adds a charm (addCharm), multiple times, and check proper revisions and timestamps
[12:35] <urulama> frankban: on the api level
[12:36] <frankban> urulama: so, we publish a charm with the same id two times and we check the id is incremented and t2> t1?
[12:37] <urulama> frankban: yes, maybe also with "sleep" of time T between publishing
[12:37] <frankban> urulama: why sleeping?
[12:41] <rogpeppe> urulama: i don't really see what that test would be adding
[12:41] <rogpeppe> urulama: given that we're testing that the upload time is within a very short period
[12:42] <rogpeppe> urulama: (assuming frankban applies my suggested change)
[12:42] <frankban> rogpeppe: I did
[13:03]  * frankban lunches
[13:10]  * rogpeppe also lunches
[13:36] <bac> ha, this is a nice tool:  http://www.downforeveryoneorjustme.com/lastpass.com
[14:17] <rogpeppe> bac: should be www.downfordownforeveryoneorjustme.com :-)
[14:18] <bac> rogpeppe: i don't get it
[14:18] <rogpeppe> bac: well, really, it would be an infinitely long name
[14:18] <rogpeppe> bac: the point being that it's only that web site that makes the check
[14:19] <bac> rogpeppe: true
[14:19] <rogpeppe> bac: so it could be down for everyone except me and their server
[14:20] <bac> rogpeppe: regardless of the inaccuracy of their naming, it is a nice check, especially when you have reason to believe it is just you.
[14:20] <bac> as i often do
[14:20] <rogpeppe> bac: absolutely. i've found it very useful in the past, although i'd forgotten about it of late
[14:47] <hatch> wb Makyo
[14:47] <frankban> rogpeppe: I am going to change BulkIncludeHandler to receive a request rather than a method and flags
[14:47] <rogpeppe> frankban: i started off doing that
[14:47] <rogpeppe> frankban: but it didn't work out
[14:47] <frankban> rogpeppe: we need access to req.Body e.g. for the extra info stuff
[14:48] <frankban> rogpeppe: why?
[14:48] <rogpeppe> frankban: really?
[14:48] <frankban> rogpeppe: extra-info PUT
[14:48] <rogpeppe> frankban: hmm, i guess i thought that stuff would be in the flags, but you're probably right
[14:49] <frankban> rogpeppe: anyway, I'd feel the framework to be more friendly if it gives the request to you anyway
[14:49] <rogpeppe> frankban: the reason it didn't work out was because of Router.GetMetadata
[14:50] <rogpeppe> frankban: and that it seemed wrong to be making up Requests for bulk metadata requests
[14:50] <hatch> jujugui call in 10
[14:50] <rogpeppe> frankban: are you planning to do extra-info ?
[14:50] <rogpeppe> frankban: i was working towards that
[14:51] <frankban> rogpeppe: I was just taking a look at the framework and realized that. If you want to tackle it I'll live it to you
[14:51] <frankban> rogpeppe: I'll look at something else, like verifyWithCharms in publish API
[14:51] <rogpeppe> frankban: i'd be happy to pair on it if you like. i'm wading through mud currently.
[14:52] <frankban> rogpeppe: sounds good
[14:52] <rogpeppe> frankban: cool, let's do that.
[14:52] <rogpeppe> frankban: after the standup?
[14:52] <frankban> rogpeppe: sure
[14:56] <rogpeppe> frankban: BTW, if we used a standard "application/x-www-form-urlencoded" MIME type, then the PUT arguments will end up in the flags argument
[14:56] <rogpeppe> frankban: we don't say much about how the PUT values are encoded in the spec
[14:57] <urulama> rogpeppe: good point, we dont
[14:58] <hatch> jujugui anyone else getting "party is over" error?
[14:58] <rogpeppe> hatch: yup
[14:58] <hatch> worked now
[14:58] <hatch> just keep trying I guess
[14:58] <hatch> heh
[14:59] <rogpeppe> urulama, frankban: we could standardise on using a single form attribute, say "value" containing the JSON-encoded value to PUT.
[15:00] <frankban> rogpeppe: It's doable, still not sure if I like it over just sending the json in the body
[15:02] <jrwren> "It's taking too long to connect you to this video call. Try again in a few minutes."
[15:02] <urulama> jrwren: daily standup :)
[15:02] <jrwren> "please wait..>"
[15:15] <frankban> rogpeppe: gogogo in 5
[15:15] <rogpeppe> frankban: ok
[15:15] <rogpeppe> frankban: i'm there, BTW
[16:01] <hatch> man somethin is munchin on my internets
[16:05] <jcsackett> hatch: this is the second day, if we're going by your sign on/sign off.
[16:05] <hatch> yeah it is :/
[16:06] <hatch> good thing I don't pay for QOS
[16:06] <hatch> oh wait....
[16:09] <hatch> rogpeppe your card that's in landing....is it still landing or blocked? Maybe it should be moved into tracking?
[16:10] <rogpeppe> hatch: i'm trying to land it but it's blocked
[16:10] <rogpeppe> hatch: if tracking is a better place for that, then by all means move it there
[16:11] <hatch> rogpeppe yeah I think that lane is for actively landing....whereas yours might sit there for a week? :)
[16:23] <kadams54> hatch: completely befuddled on this test I'm trying to fix. Ping me when you have a few moments.
[16:23] <hatch> kadams54 you're in luck I just finished a review
[16:23] <hatch> what's up?
[16:25] <kadams54> this is the currently breaking code: https://github.com/juju/juju-gui/blob/develop/app/widgets/deployer-bar.js#L257
[16:25] <kadams54> It loops through a set of keys and checks to see if any of their values have a length.
[16:26] <hatch> ok
[16:28] <hatch> is there more to this story?
[16:28] <hatch> :)
[16:28] <kadams54> The problem is that my code adds a new key who's property is an int
[16:28] <kadams54> So I thought I'd just add an Array.isArray check before we look at length
[16:28] <kadams54> It's false, but hasChange is still getting set to true
[16:29] <hatch> ok looking
[16:30] <kadams54> Should I push my changes up so you can see them?
[16:30] <kadams54> Or would you prefer something like a gist?
[16:32] <hatch> well I'm just trying to figure out what this is doing
[16:32] <kadams54> This screenshot pretty much summarizes my confusion: http://cl.ly/image/20132A2e051Z
[16:33] <kadams54> Both conditions for the if statement eval to false, yet we're inside and hasChange is set to true.
[16:35] <hatch> that might be an issue with how watches are evaluated
[16:35] <hatch> what if you run those in the console?
[16:36] <hatch> and you'll want to use Y.Array.isArray() I'm not sure if Array.isArray() is supported everywhere yet
[16:36] <hatch> what is this even testing for? What makes it a major change? If any of the objects have something in them then major change is true?
[16:40] <jcsackett> thanks for the review, Makyo. :)
[16:41] <kadams54> hatch: we're using an object as a hash here. The original code makes an assumption that all the values in the hash are arrays of changes. If any of the arrays have a non-zero length, then we have major changes and need to display the summary panel in addition to the changelog.
[16:42] <hatch> ok but that basically means that if there is anything in changes then we need to show it...what tasks aren't shown?
[16:42] <hatch> what I'm getting at is this method isn't necessary
[16:42] <hatch> because if you do anything it will return true
[16:42] <hatch> if any of the changes keys have values it's true
[16:44] <jcsackett> jujugui: i need 2 reviews on this (very short) PR. https://github.com/juju/juju-gui/pull/491
[16:44] <kadams54> But not all of the keys in the hash are arrays of changes.
[16:44] <hatch> jcsackett no test? :)
[16:45] <jcsackett> hatch: nope--there's no meaningful way to get in and test the d3 logic.
[16:45] <hatch> kadams54 right - but what I'm saying is that this method is causing you issues.....I don't think this method is necessary because if there is anything in the changes object then it's shown
[16:45] <jcsackett> i can break out the logic about what to show into a separate method and test that, if you like.
[16:45] <kadams54> hatch: not necessarily the case.
[16:45] <hatch> jcsackett well that's just not true :) we test the unit list somewhere
[16:45] <hatch> kadams54 ok what is the case where it isn't?
[16:46] <kadams54> hatch: for example, if the user just adds a container, we only show the changelog. We don't show the summary panel.
[16:46] <jcsackett> hatch: we set up some stuff using the generateAndBind, but we don't inspect those contents.
[16:46] <kadams54> In that case, all of the arrays in the changes hash would have a 0 length.
[16:46] <kadams54> i.e., no "major" changes
[16:46] <jcsackett> hatch: which is reasonable, b/c it's just testing "does d3 set an a tag when i tell it to set an a tag.
[16:47] <jcsackett> hatch: as i said, if you like i can break that change out into a "chooseDisplayName" method for units, and test *that*.
[16:47] <hatch> jcsackett I'm pretty sure we have a test which renders the unit list and then checks the dom to make sure there are x number of units rendered
[16:47] <hatch> maybe inspector overview or something
[16:48] <hatch> kadams54 ok and you have added something to changes.addUnits?
[16:48] <kadams54> Yeah… totalUnits…
[16:48] <jcsackett> hatch: that's where i looked. unless you
[16:48] <kadams54> Which is an int
[16:48] <jcsackett> hatch: unless you're talking the scale out tests, which arne't qute the same kettle of fish.
[16:50] <kadams54> hatch: sorry, I didn't add anything to changes.addUnits. I added it to changes. So changes now has changes.addUnits and changes.totalUnits.
[16:50] <hatch> kadams54 ok so you could have getChanges return an object where one property is the changes and the other is the total units
[16:50] <hatch> then you don't have to modify this method
[16:51] <hatch> which is what I would recommend because your putting stuff in the changes property that doesn't really fit with the rest of the dataset
[16:51] <kadams54> OK, will do
[16:51] <hatch> sounds good?
[16:51] <hatch> ok cool
[16:52] <hatch> jcsackett I'm just saying it would be nice if we could test that when we pass an uncommitted model into the d3 stuff it renders the proper name
[16:52] <hatch> and the other way
[16:53] <hatch> it was what the bug was about afterall
[16:53] <jcsackett> hatch: i'm not disagreeing, but the test for that will be ridiculous. like i said, i can break out the logic part of it into another method, and test that it returns the right thing; after that it's a matter of believing d3 does the right thing or not.
[16:53] <hatch> I'll try and find the test
[16:53] <hatch> you may be able to copy it
[16:53] <hatch> one sec
[16:53] <hatch> but I agree if you have to write it all
[16:53] <hatch> no good :)
[16:54] <jcsackett> i'm reading through inspector_overview and not seeing anything that looks right.
[16:56] <hatch> jcsackett test_inspector_overview.js:477
[16:56] <hatch> the test is massive but  you can likely modify it to use one uncommitted unit model as well as the regular others
[16:56] <hatch> or add another unit to the list
[16:57] <jcsackett> hatch: i'll see--i don't think the return from that is quite right to see what's rendered in the lists, but you might be right.
[16:57] <jcsackett> oh, i see, it's dumping the whole damn mess.
[16:57] <jcsackett> ok.
[16:58] <hatch> so you should be able to just add an uncommitted unit to this and test that that unit is rendered properly and that another one is rendered property too
[17:09]  * rogpeppe is done for the day
[17:09] <rogpeppe> g'night all
[17:09] <jcsackett> hatch: done.
[17:10] <jcsackett> thanks for helping sort out where to test it; that block is impenetrable when you're scanning without being certain what you're looking for. :p
[17:11] <hatch> haha yeah it is np
[17:11] <hatch> ok will qa
[17:11] <hatch> jcsackett lint error
[17:11] <hatch> lol
[17:12] <hatch> we should make a rule - if your tests fail with a lint error you got to buy everyone a coffee :P
[17:13] <jcsackett> i honestly am not sure of the utility of lint being run on every test--on merge, sure, but it's just noise to me.
[17:14] <hatch> I always run the full suite before pushing - and now that I'm in Ubuntu the tests don't fail randomly lol
[17:15] <jcsackett> hatch: i always run the tests; i don't always run check.
[17:15] <hatch> oh right cuz it's really slow for you isn't it?
[17:15] <jcsackett> hatch: sufficiently slow.
[17:16] <jcsackett> slow enough that i end up waiting a while, not long enough to do anything meaningful while it runs.
[17:19] <hatch> time for an ssd?
[17:29] <kadams54> hatch: looks like huw needs second reviews on a couple PRs?
[17:30] <hatch> kadams54 the x uncommitted one I need to write the fix for it to get it to land
[17:30] <hatch> but the mv scale up one does
[17:30] <hatch> is yours all good to go?
[17:31] <hatch> looks good
[17:31] <hatch> once the tests pass you can land it
[17:31] <kadams54> Yeah
[17:31] <kadams54> I was noticing we had a build-up of cards in review
[17:32] <kadams54> I'll dig into the mv scale up one.
[17:34] <kadams54> Looks like the scale up one needs to be rebased and have some conflicts resolved
[19:06] <hatch> telcos should have a flag on peoples accounts which mark their level of expertise
[19:07] <hatch> so when you call with a problem they don't ask you if you have restarted your router and make you do it again for kicks
[19:09] <hatch> jcsackett can you rebase your branch and shippit?
[19:10] <hatch> #491 that is
[19:19] <jrwren> I actually called Comcast once after I did some basic troubleshooting. I had forgot to reset my cable modem.
[19:19] <jrwren> The support person saying "Turn it off and back on again" actually solved my problem.
[19:20] <hatch> lol
[19:30] <urulama-afk> jrwren: config-changed error: http://pastebin.ubuntu.com/8029262/
[19:32] <urulama-afk> jrwren: relations in charms: http://pastebin.ubuntu.com/8029269/
[19:33] <jrwren> urulama-afk: that doesn't look like an error. :(
[19:34] <urulama-afk> error: no relation id specified
[19:34] <urulama-afk> maybe it's enough to trigger the hooks and to leave the charm in "installed" but not "started" state
[19:35] <jrwren> urulama-afk: I'll try to reproduce. Thanks.
[19:36] <jrwren> urulama-afk: I'm still new enough to charming that I don't remember all this stuff. I can't recall if that error: is valid or not.
[19:36] <urulama-afk> jrwren: me and you both :)
[19:36] <jrwren> jrwren: Still, and invalid error message is a bug, so I'll fix it.
[19:36] <jrwren> s/and/an/
[19:37] <urulama-afk> jrwren: yes, i can exit the tmux and then the status is "started"
[19:37] <jrwren> urulama-afk: can you curl that ip on the listen port?
[19:41] <urulama-afk> jrwren: it gets stuck on most of the hook scripts, but running them manually and exiting tmux produces service in a "started" state, and curl works
[19:42] <jrwren> hrm. it gets stuck and you have to resolved --retry?
[19:42] <urulama-afk> jrwren: i mean, the CS is empty, but there are "error" codes to show that it works
[19:42] <jrwren> urulama-afk: that is VERY weird.
[19:43] <jrwren> urulama-afk: Empty and responsive is my goal.
[19:43] <urulama> jrwren: i haven't tried deploying without debug-hooks, let me add another unit, it might just as well work
[19:49] <urulama> jrwren: indeed ... seems like debug-hooks interpret your error messages as true errors ... without them, the charm starts and is in "started" mode
[19:50] <jrwren> urulama: Good, that is what I thought.
[19:50] <hatch> you guys ok with all this? I've done some charm work, can maybe offer some input
[19:51] <hatch> jcsackett thanks
[19:51] <urulama> jrwren: ok, so fixing that is simple, just changing error to "warning" or something, as they are not true errors
[19:51] <urulama> hatch: thx
[19:51] <jcsackett> hatch: no worries; hadn't noticed i had all my reviews for it. :)
[19:51] <jcsackett> thanks for pinging me.
[19:51] <jrwren> urulama: its charmhelpers.
[19:52] <urulama> jrwren: khm. then it might not be that innocent after all :)
[19:52] <jrwren> hatch: What is the right way to use charmhelpers.core.hookenv.relation_get ?
[19:53] <hatch> what's this python mumbo jumbo...I just shell out to the real relation get
[19:53] <hatch> https://github.com/hatched/ghost-charm/blob/master/hooks/db-relation-changed
[19:54] <hatch> so sorry, I have never used charmhelpers :)
[19:54] <jrwren> hatch: I'm pretty sure I was told to use this.
[19:54] <hatch> yeah you likely were
[19:54] <hatch> sometimes the abstraction is more work though
[19:54] <hatch> case-and-point :)
[19:54] <jrwren> hatch: Are you sure it is only sometimes? :)
[19:55] <hatch> haha
[19:55] <hatch> jrwren you'll probably have some luck asking in #Juju-dev
[19:56] <urulama> hatch: do not lead jrwren into temptations! :)
[19:57] <jrwren> It is likely as simple as if not relation_ids(): before those relation_get calls'
[19:57] <hatch> urulama haha sorry - I've written charms in node and bash, and fixed the gui one which is in python so never really used charmhelpers and the like
[20:03] <urulama> hatch: i deploy charms from CLI, that doesn't mean GUI is useless :D
[20:04] <hatch> urulama definitely not, after about the 1000th time of writing `juju set some-really-big-charm-name some-really-big-config-name="some really long value"` you'll just use quickstart and use the GUI exclusively
[20:04] <hatch> lol
[20:05] <urulama> :D :D
[20:06] <urulama> ok, time to really EOD ... see you all tomorrow, jujugui (and irc clients go 'ping' all over the globe)
[20:06] <bac> later urulama
[20:06] <jrwren> urulama: good night. TY.
[20:06] <hatch> haha cya urulama
[20:42] <rick_h__> jrwren: ask in #juju of marcoceppi or mbruzek around that. Maybe tvansteenburgh as well. They work on and maintain the charmhelpers
[20:42] <rick_h__> hatch: helps us use/make better our own tools :P
[20:43] <marcoceppi> o/
[20:43] <hatch> rick_h__ I'm not sure anything that's 3 levels deep for a simple shell-out call is a valid abstraction :D
[20:43] <rick_h__> hatch: time to make it better?
[20:43] <rick_h__> hatch: shell out with proper catching of return values, logging integration, etc can be worth it
[20:43] <rick_h__> however I have a lack of context in this matter so I wave my hands around in a general fashion
[20:43] <hatch> honestly I have no idea what it does under the hood, never used it :)
[20:44] <mbruzek> ask me what?
[20:44] <rick_h__> mbruzek: jrwren is having some issues with relation-get and charmhelpers or the like
[20:44] <rick_h__> mbruzek: just volunteering you for support of jrwren gets stuck :)
[20:44]  * mbruzek nods
[20:47] <hatch> maybe I should write a charm in python to learn about these helpers-of-the-charm
[20:51] <marcoceppi> hatch: ALL HAIL THE HELPERS OF THE CHARM
[20:51] <jrwren> hatch: If you are a cranky programmer like me, it might just annoy you that it isn't in bash. ;]
[20:52] <hatch> jrwren bash MAKES a cranky programmer
[20:52] <hatch> marcoceppi lol
[20:52] <hatch> rick_h__ you still around?
[20:52]  * jrwren uses /dev/tcp in bash instead of curl
[20:52] <hatch> lol
[20:54] <hatch> jcsackett Makyo kadams54 want to weigh in on https://github.com/juju/juju-gui/pull/486#issuecomment-51975411 ?
[20:54] <rick_h__> hatch: sure
[20:55] <rick_h__> hatch: packing up, flight home in the morn
[20:55] <hatch> rick_h__ want to weigh in on that? ^
[20:55] <kadams54> hatch: lgtm
[20:55] <rick_h__> hatch: looking
[20:56] <rick_h__> hatch: "update a template which doesn't exist" ?
[20:57] <hatch> rick_h__ the real issue is that it's not the template which doesn't exist, it's that it's using the old inspector rendering code
[20:57] <hatch> so we have to write a new test mock for generating the inspector to use the NEW mv style inspector rendering code
[20:57] <hatch> which has to be done anyways but will block this branch
[20:58] <rick_h__> hatch: that seems like something we'll need anyway? (a new helper for generating a new inspector)
[20:58] <rick_h__> hatch: ok, but this comment is about waiting until MV is released, not about a missing test helper?
[20:58] <rick_h__> nothing here is documenting/adding that we need the helper as the 'right' fix?
[20:58] <hatch> yeah sorry that wasn't clear
[20:58] <rick_h__> or am I mis-reading that?
[20:59]  * rick_h__ loads up kanban
[20:59] <hatch> so this branch either needs to wait until the new inspector mock test thingy is written or apply the included patch to land it now
[21:00] <hatch> I gather the new inspector mock thingy will take 1day and then moving all the tests to use it will be....2?
[21:00] <rick_h__> hatch: ok, I'm cool with the patch with a proper XXX, documenting the place the needs updating, and a follow up card at the top of the lane
[21:01] <hatch> ok I'll work on the inspector thingy, I added a friday card to chat about it
[21:01] <hatch> thx
[21:01] <rick_h__> hatch: coolio, thanks.
[21:01] <hatch> safe travels!
[21:02] <rick_h__> wheeeee
[21:02] <rick_h__> can't wait to have my own pillows again
[21:02] <hatch> lol
[21:02] <hatch> it's the small things, right?
[21:03] <rick_h__> you know it
[21:03] <rick_h__> like AC that works
[21:03] <rick_h__> getting sick of always sweating in EU
[21:03] <hatch> haha, I never would have thought that would be an issue
[21:04] <rick_h__> us norhern folks don't like it so hot, my basement office is calling me
[21:05] <hatch> haha
[21:05] <hatch> I'm with you on that one!
[21:15] <hatch> Makyo good choice in cards :)
[21:15] <rick_h__> well I'm out, have fun all. See you soon.
[21:15] <hatch> cya rick_h__  safe travels
[22:06] <hatch> jujugui lf a review (no qa) https://github.com/juju/juju-gui/pull/492
[23:03] <huwshimi> Morning
[23:21] <hatch> morning huwshimi
[23:24] <hatch> huwshimi all reviews are done and comments made so you should be able to land both of your branches
[23:24] <hatch> today
[23:24] <hatch> and if you could also do a quick review on mine that would be great because mine provides the hooks you will need to mark up the UI with the 'deleted' attributes
[23:24] <hatch> ^ huwshimi
[23:25] <jrwren> huwshimi: Good morning.
[23:34] <jrwren> My wife and child just reminded me that today is my last day living at the age of 36 years old.
[23:35] <hatch> WHAAAAA
[23:35] <hatch> I thought you were like.......26
[23:35] <hatch> lol
[23:36] <jrwren> Whaaa???
[23:36] <hatch> haha yeah
[23:41] <huwshimi> hatch: Yep no problems, just doing a little qa
[23:52] <huwshimi> hatch: So to use that flag would we have to update this to use lazyDestroyMachines? https://github.com/juju/juju-gui/blob/develop/app/widgets/machine-view-panel.js#L710


[00:06] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kstars build #9: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/artful_stable_kstars/9/
[00:07] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #8: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/artful_unstable_kopete/8/
[00:15] -kubuntu-ci:#kubuntu-devel- Project artful_stable_cantor build #8: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/artful_stable_cantor/8/
[00:16] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ark build #9: STILL UNSTABLE in 17 min: https://kci.pangea.pub/job/artful_unstable_ark/9/
[00:17] <clivejo> acheronuk: kontact: relocation error: /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so: symbol _ZN15WebEngineViewer20LocalDataBaseManager4selfEv, version ABI_5_2 not defined in file libKF5WebEngineViewer.so.5abi2 with link time reference
[00:19] <acheronuk> clivejo: you on zesty or artful KCI packages?
[00:19] <clivejo> zesty
[00:20] <acheronuk> figures. artful message lib is failing on unstable due to an ABI break and it's missing symbols
[00:20] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #9: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/artful_stable_ark/9/
[00:21] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktp-auth-handler build #8: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/artful_stable_ktp-auth-handler/8/
[00:21] <acheronuk> clivejo: as zesty is not the dev release now, the package still builds but might give you an error like that
[00:21] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kopete build #30: STILL UNSTABLE in 45 min: https://kci.pangea.pub/job/zesty_stable_kopete/30/
[00:22] <acheronuk> I was actually just looking at the artful fail.
[00:22] <acheronuk> PIM needs another ABI bump.... sigh
[00:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_elisa build #8: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/artful_unstable_elisa/8/
[00:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeconnect-kde build #7: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/artful_unstable_kdeconnect-kde/7/
[00:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kalzium build #8: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/artful_unstable_kalzium/8/
[00:27] -kubuntu-ci:#kubuntu-devel- Project artful_stable_umbrello build #8: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/artful_stable_umbrello/8/
[00:38] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ark build #23: STILL UNSTABLE in 15 min: https://kci.pangea.pub/job/zesty_stable_ark/23/
[00:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-desktop build #184: FAILURE in 9 min 1 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-desktop/184/
[00:49] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_ark build #25: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/xenial_stable_ark/25/
[00:49] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_umbrello build #27: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/xenial_stable_umbrello/27/
[00:50] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ktp-auth-handler build #31: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/zesty_stable_ktp-auth-handler/31/
[00:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop build #169: UNSTABLE in 29 min: https://kci.pangea.pub/job/xenial_unstable_kdevelop/169/
[00:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #72: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_unstable_kexi/72/
[00:53] <ahoneybun> clivejo: think you can get nimbusoft to give us a logo to use on : http://kubuntu.org/vendors
[00:56] <acheronuk> looks familiar https://nimbusoft.com/wp-content/uploads/2017/04/Screenshot_20170430_155127-1400x788.png
[00:59] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_umbrello build #19: STILL UNSTABLE in 36 min: https://kci.pangea.pub/job/zesty_stable_umbrello/19/
[01:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #317: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_cantor/317/
[01:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #119: STILL UNSTABLE in 39 min: https://kci.pangea.pub/job/zesty_unstable_kopete/119/
[01:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #304: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/304/
[01:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #114: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/zesty_unstable_kalzium/114/
[01:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #182: FIXED in 39 min: https://kci.pangea.pub/job/zesty_unstable_plasma-desktop/182/
[01:06] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kexi build #19: STILL FAILING in 5 min 7 sec: https://kci.pangea.pub/job/zesty_stable_kexi/19/
[01:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #141: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_unstable_cantor/141/
[01:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #139: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/139/
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kexi build #85: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/xenial_unstable_kexi/85/
[01:16] <ahoneybun> damn Mint pulls in a lot of money
[01:16] <ahoneybun> almost 8 grand in March
[01:19] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kexi build #7: STILL FAILING in 6 min 49 sec: https://kci.pangea.pub/job/artful_stable_kexi/7/
 ohh new site
 yet it shows GNOME: https://eloquentos.com/
 they also don't have 17.04 up yet
[01:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #162: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_unstable_ark/162/
 now they offer the Kubuntu logo on the key
[01:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #233: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/233/
[01:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #478: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_ark/478/
[01:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #407: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_plasma-pa/407/
[01:28] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kexi build #20: STILL FAILING in 4 min 53 sec: https://kci.pangea.pub/job/zesty_stable_kexi/20/
[01:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-desktop build #185: STILL FAILING in 9 min 23 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-desktop/185/
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_krita build #29: STILL UNSTABLE in 1 hr 9 min: https://kci.pangea.pub/job/xenial_stable_krita/29/
[01:36] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kexi build #17: STILL FAILING in 3 min 53 sec: https://kci.pangea.pub/job/xenial_stable_kexi/17/
[01:38] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kexi build #8: STILL FAILING in 6 min 25 sec: https://kci.pangea.pub/job/artful_stable_kexi/8/
[01:43] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kexi build #18: STILL FAILING in 2 min 42 sec: https://kci.pangea.pub/job/xenial_stable_kexi/18/
[01:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #136: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/zesty_unstable_kdiagram/136/
[01:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #339: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/339/
[01:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_cantor build #8: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/artful_unstable_cantor/8/
[01:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kexi build #8: STILL UNSTABLE in 33 min: https://kci.pangea.pub/job/artful_unstable_kexi/8/
[01:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #88: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_unstable_kdb/88/
[01:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #132: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/xenial_unstable_kdiagram/132/
[01:47] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #11: STILL FAILING in 12 min: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/11/
[01:52] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktp-common-internals build #9: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_stable_ktp-common-internals/9/
[01:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kile build #7: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/artful_unstable_kile/7/
[01:55] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #7: STILL UNSTABLE in 1 hr 48 min: https://kci.pangea.pub/job/artful_unstable_krita/7/
[01:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #109: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_unstable_kdb/109/
[01:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-import-wizard build #133: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/xenial_unstable_akonadi-import-wizard/133/
[02:01] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kdevelop build #20: UNSTABLE in 18 min: https://kci.pangea.pub/job/zesty_stable_kdevelop/20/
[02:01] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdevelop build #6: UNSTABLE in 28 min: https://kci.pangea.pub/job/artful_stable_kdevelop/6/
[02:02] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #12: STILL FAILING in 9 min 57 sec: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/12/
[02:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #152: STILL UNSTABLE in 1 hr 11 min: https://kci.pangea.pub/job/zesty_unstable_krita/152/
[02:10] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kdevelop build #23: UNSTABLE in 28 min: https://kci.pangea.pub/job/xenial_stable_kdevelop/23/
[02:12] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdevelop build #8: UNSTABLE in 27 min: https://kci.pangea.pub/job/artful_unstable_kdevelop/8/
[02:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #174: FIXED in 29 min: https://kci.pangea.pub/job/zesty_unstable_kwin/174/
[02:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_messagelib build #15: STILL FAILING in 26 min: https://kci.pangea.pub/job/artful_unstable_messagelib/15/
[02:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #245: STILL UNSTABLE in 35 min: https://kci.pangea.pub/job/xenial_unstable_kdepim-addons/245/
[02:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #157: UNSTABLE in 17 min: https://kci.pangea.pub/job/zesty_unstable_kdevelop/157/
[02:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #126: STILL UNSTABLE in 1 hr 46 min: https://kci.pangea.pub/job/xenial_unstable_krita/126/
[02:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-import-wizard build #124: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/zesty_unstable_akonadi-import-wizard/124/
[02:58] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwin build #11: UNSTABLE in 45 min: https://kci.pangea.pub/job/artful_unstable_kwin/11/
[03:36] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcompletion build #12: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/artful_unstable_kcompletion/12/
[03:36] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_phonon build #7: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/artful_unstable_phonon/7/
[03:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcodecs build #12: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/artful_unstable_kcodecs/12/
[03:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ki18n build #12: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/artful_unstable_ki18n/12/
[03:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcoreaddons build #11: STILL UNSTABLE in 16 min: https://kci.pangea.pub/job/artful_unstable_kcoreaddons/11/
[04:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfig build #99: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/zesty_unstable_kconfig/99/
[04:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #166: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/166/
[04:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #135: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/zesty_unstable_kcoreaddons/135/
[04:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #164: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/zesty_unstable_kdbusaddons/164/
[04:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #425: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/xenial_unstable_kcoreaddons/425/
[04:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #469: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/xenial_unstable_kconfig/469/
[04:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #156: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/zesty_unstable_kitemviews/156/
 I dreamed that we made mparillo the ruler of Facebook
 He was our Lord
 not on facebook, so not MY lord :P
 😂
[05:35] <valorie> lol
[05:39] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_messagelib build #16: STILL FAILING in 18 min: https://kci.pangea.pub/job/artful_unstable_messagelib/16/
[06:00] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:00] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_messagelib build #17: FIXED in 20 min: https://kci.pangea.pub/job/artful_unstable_messagelib/17/
[07:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-calendar-tools build #68: FAILURE in 53 sec: https://kci.pangea.pub/job/zesty_unstable_akonadi-calendar-tools/68/
[07:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akonadi-calendar-tools build #6: FAILURE in 54 sec: https://kci.pangea.pub/job/artful_unstable_akonadi-calendar-tools/6/
[07:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-calendar-tools build #88: FAILURE in 57 sec: https://kci.pangea.pub/job/xenial_unstable_akonadi-calendar-tools/88/
[07:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_grantlee-editor build #108: FAILURE in 56 sec: https://kci.pangea.pub/job/zesty_unstable_grantlee-editor/108/
[07:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_grantlee-editor build #7: FAILURE in 53 sec: https://kci.pangea.pub/job/artful_unstable_grantlee-editor/7/
[07:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_grantlee-editor build #86: FAILURE in 54 sec: https://kci.pangea.pub/job/xenial_unstable_grantlee-editor/86/
[07:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadiconsole build #101: FAILURE in 53 sec: https://kci.pangea.pub/job/zesty_unstable_akonadiconsole/101/
[07:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akonadiconsole build #6: FAILURE in 53 sec: https://kci.pangea.pub/job/artful_unstable_akonadiconsole/6/
[07:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadiconsole build #81: FAILURE in 54 sec: https://kci.pangea.pub/job/xenial_unstable_akonadiconsole/81/
[07:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailcommon build #133: FAILURE in 58 sec: https://kci.pangea.pub/job/zesty_unstable_mailcommon/133/
[07:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #135: FAILURE in 53 sec: https://kci.pangea.pub/job/xenial_unstable_mailcommon/135/
[07:19] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_mailcommon build #6: FAILURE in 54 sec: https://kci.pangea.pub/job/artful_unstable_mailcommon/6/
[07:19] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_knotes build #6: FAILURE in 54 sec: https://kci.pangea.pub/job/artful_unstable_knotes/6/
[07:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_knotes build #158: FAILURE in 56 sec: https://kci.pangea.pub/job/zesty_unstable_knotes/158/
[07:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_knotes build #149: FAILURE in 54 sec: https://kci.pangea.pub/job/xenial_unstable_knotes/149/
[07:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akregator build #151: STILL FAILING in 53 sec: https://kci.pangea.pub/job/zesty_unstable_akregator/151/
[07:20] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akregator build #11: STILL FAILING in 53 sec: https://kci.pangea.pub/job/artful_unstable_akregator/11/
[07:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akregator build #111: STILL FAILING in 55 sec: https://kci.pangea.pub/job/xenial_unstable_akregator/111/
[07:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_blogilo build #115: FAILURE in 57 sec: https://kci.pangea.pub/job/zesty_unstable_blogilo/115/
[07:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_blogilo build #79: FAILURE in 53 sec: https://kci.pangea.pub/job/xenial_unstable_blogilo/79/
[07:20] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_blogilo build #6: FAILURE in 53 sec: https://kci.pangea.pub/job/artful_unstable_blogilo/6/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_grantlee-editor build #87: FIXED in 9 min 41 sec: https://kci.pangea.pub/job/xenial_unstable_grantlee-editor/87/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akonadi-calendar-tools build #7: FIXED in 10 min: https://kci.pangea.pub/job/artful_unstable_akonadi-calendar-tools/7/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_grantlee-editor build #8: FIXED in 9 min 52 sec: https://kci.pangea.pub/job/artful_unstable_grantlee-editor/8/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-calendar-tools build #89: FIXED in 10 min: https://kci.pangea.pub/job/xenial_unstable_akonadi-calendar-tools/89/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_grantlee-editor build #109: FIXED in 10 min: https://kci.pangea.pub/job/zesty_unstable_grantlee-editor/109/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akonadiconsole build #7: FIXED in 9 min 49 sec: https://kci.pangea.pub/job/artful_unstable_akonadiconsole/7/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadiconsole build #102: FIXED in 9 min 53 sec: https://kci.pangea.pub/job/zesty_unstable_akonadiconsole/102/
[07:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-calendar-tools build #69: FIXED in 11 min: https://kci.pangea.pub/job/zesty_unstable_akonadi-calendar-tools/69/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akregator build #152: FIXED in 14 min: https://kci.pangea.pub/job/zesty_unstable_akregator/152/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_akregator build #12: FIXED in 14 min: https://kci.pangea.pub/job/artful_unstable_akregator/12/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mailcommon build #134: FIXED in 15 min: https://kci.pangea.pub/job/zesty_unstable_mailcommon/134/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #136: FIXED in 15 min: https://kci.pangea.pub/job/xenial_unstable_mailcommon/136/
[07:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_mailcommon build #7: FIXED in 15 min: https://kci.pangea.pub/job/artful_unstable_mailcommon/7/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_blogilo build #80: FIXED in 14 min: https://kci.pangea.pub/job/xenial_unstable_blogilo/80/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_knotes build #150: FIXED in 15 min: https://kci.pangea.pub/job/xenial_unstable_knotes/150/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_knotes build #7: FIXED in 15 min: https://kci.pangea.pub/job/artful_unstable_knotes/7/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_blogilo build #116: FIXED in 14 min: https://kci.pangea.pub/job/zesty_unstable_blogilo/116/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_blogilo build #7: FIXED in 14 min: https://kci.pangea.pub/job/artful_unstable_blogilo/7/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_knotes build #159: FIXED in 15 min: https://kci.pangea.pub/job/zesty_unstable_knotes/159/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadiconsole build #82: FIXED in 16 min: https://kci.pangea.pub/job/xenial_unstable_akonadiconsole/82/
[07:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akregator build #112: FIXED in 15 min: https://kci.pangea.pub/job/xenial_unstable_akregator/112/
[07:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:56] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktp-auth-handler build #9: FIXED in 9 min 48 sec: https://kci.pangea.pub/job/artful_stable_ktp-auth-handler/9/
[07:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:57] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ktp-auth-handler build #32: FIXED in 10 min: https://kci.pangea.pub/job/zesty_stable_ktp-auth-handler/32/
[07:57] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_ktp-auth-handler build #8: FIXED in 10 min: https://kci.pangea.pub/job/xenial_stable_ktp-auth-handler/8/
[07:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #340: FIXED in 11 min: https://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/340/
[07:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:58] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktp-auth-handler build #9: FIXED in 11 min: https://kci.pangea.pub/job/artful_unstable_ktp-auth-handler/9/
[07:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #69: FIXED in 11 min: https://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/69/
[08:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:11] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ktp-common-internals build #10: FIXED in 14 min: https://kci.pangea.pub/job/artful_stable_ktp-common-internals/10/
[08:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:12] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_ktp-common-internals build #12: FIXED in 15 min: https://kci.pangea.pub/job/xenial_stable_ktp-common-internals/12/
[08:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #246: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/xenial_unstable_kdepim-addons/246/
[08:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:18] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ktp-common-internals build #11: FIXED in 21 min: https://kci.pangea.pub/job/zesty_stable_ktp-common-internals/11/
[08:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #305: FIXED in 20 min: https://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/305/
[08:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:19] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktp-common-internals build #4: FIXED in 20 min: https://kci.pangea.pub/job/artful_unstable_ktp-common-internals/4/
[08:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #120: FIXED in 20 min: https://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/120/
[08:19] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdepim-addons build #12: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/artful_unstable_kdepim-addons/12/
[08:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #184: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/zesty_unstable_kdepim-addons/184/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1491: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1491/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1491: SUCCESS in 1 min 10 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1491/
[08:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1491: SUCCESS in 3 min 49 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1491/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1491: SUCCESS in 4 min 23 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1491/
[10:27] <BluesKaj> 'Morning folks
[11:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #8: STILL UNSTABLE in 1 hr 0 min: https://kci.pangea.pub/job/artful_unstable_krita/8/
[11:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #153: STILL UNSTABLE in 1 hr 0 min: https://kci.pangea.pub/job/zesty_unstable_krita/153/
[11:43] <clivejo> ahoneybun: Got logo, and uploaded to site, feel free change the layout etc
[11:43] <ahoneybun> lovely thanks clivejo
[11:46] <clivejo> not sure if the URL is needed if the logo links there
[11:52] <acheronuk> santa_: going to build the 16.12.3 PIM sources later, so can get those tar'd up ready to give to a MOTU (maybe Rohan). If we can persuade one soon.
[11:53] <acheronuk> stable 16.12.3 maybe be an easier "sell" to an MOTU
[11:53] <acheronuk> then we can refresh packageset etc
[11:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #127: STILL UNSTABLE in 1 hr 34 min: https://kci.pangea.pub/job/xenial_unstable_krita/127/
[11:57]  * clivejo wonders was mparillo a good or evil facebook lord
[12:02] <mparillo> All I know is that when I open an incognito window to post to facebook, I feel like I need a shower afterwards.
[12:02] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_krita build #30: STILL UNSTABLE in 1 hr 41 min: https://kci.pangea.pub/job/xenial_stable_krita/30/
[12:05] <santa_> acheronuk: ack. fyi I finished yesterday the initial version tracker: http://gpul.grupos.udc.es/ka-iron-hand_reports/version_status.html I also plan to write a small script to handle the plasma sru
[12:10] <mparillo> santa_: The version tracker looks good, and if it is created automagically that is a lot better than trying to update a status wiki page manually. Yesterday, I saw many 5.9.5 modules for Plasma, which matches your archive column, but kinfocenter and plasmashell -v still reported 5.9.4.
[12:14] <santa_> mparillo: you mean in artful/archive ? that' because it's migrating slowly from -proposed, see: http://gpul.grupos.udc.es/ka-iron-hand_reports/plasma_archive/5.9.5_artful_proposed_migration.pdf
[12:15] <acheronuk> VERY VERY slowly!
[12:16] <santa_> and yes, it's created automagically by a cron job :)
[12:16] <mparillo> TY, yes I was looking at the Artful Archive column. And I did note that many 5.9.5. packages landed...just not all of them.
[12:17] <santa_> yeah, well, for accuracy/details we have the graphs, the version tracker is just a summary - so to speak
[12:17] <santa_> so we know what we need to update where, that was the point of doing it
[12:19] <santa_> mfw I tried to remember all the versions we have out there: http://jamestlaw.com/wp-content/uploads/2016/09/Jackie-Chan-Meme-300x192.jpg
[13:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #154: STILL UNSTABLE in 1 hr 28 min: https://kci.pangea.pub/job/zesty_unstable_krita/154/
[13:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_krita build #9: STILL UNSTABLE in 1 hr 28 min: https://kci.pangea.pub/job/artful_unstable_krita/9/
[13:27] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim-runtime build #698: FAILURE in 9 sec: https://kci.pangea.pub/job/merger_kdepim-runtime/698/
[13:29] -kubuntu-ci:#kubuntu-devel- Project merger_kmail build #190: FAILURE in 5.7 sec: https://kci.pangea.pub/job/merger_kmail/190/
[13:30] -kubuntu-ci:#kubuntu-devel- Project merger_blogilo build #177: FAILURE in 7.6 sec: https://kci.pangea.pub/job/merger_blogilo/177/
[13:33] -kubuntu-ci:#kubuntu-devel- Project merger_korganizer build #173: FAILURE in 8.8 sec: https://kci.pangea.pub/job/merger_korganizer/173/
[13:34] -kubuntu-ci:#kubuntu-devel- Project merger_kaddressbook build #175: FAILURE in 7.5 sec: https://kci.pangea.pub/job/merger_kaddressbook/175/
[13:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:38] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim-runtime build #699: FIXED in 17 sec: https://kci.pangea.pub/job/merger_kdepim-runtime/699/
[13:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:40] -kubuntu-ci:#kubuntu-devel- Project merger_kmail build #191: FIXED in 16 sec: https://kci.pangea.pub/job/merger_kmail/191/
[13:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:41] -kubuntu-ci:#kubuntu-devel- Project merger_blogilo build #178: FIXED in 13 sec: https://kci.pangea.pub/job/merger_blogilo/178/
[13:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:44] -kubuntu-ci:#kubuntu-devel- Project merger_korganizer build #174: FIXED in 13 sec: https://kci.pangea.pub/job/merger_korganizer/174/
[13:44] <santa_> acheronuk: I'm going to stage soon the intended plasma sru for zesty, any objection to that?
[13:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:45] -kubuntu-ci:#kubuntu-devel- Project merger_kaddressbook build #176: FIXED in 14 sec: https://kci.pangea.pub/job/merger_kaddressbook/176/
[13:45] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kaddressbook build #26: STILL FAILING in 28 sec: https://kci.pangea.pub/job/xenial_stable_kaddressbook/26/
[13:50] <acheronuk> santa_: if good to go, then no problem
[13:51] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kaddressbook build #27: STILL FAILING in 27 sec: https://kci.pangea.pub/job/xenial_stable_kaddressbook/27/
[13:52] <santa_> ack, I'm fnishing th script to convert the thing to an sru, I'm not going to push to git inmediatly, just in case
[13:53]  * acheronuk glares at the test queues!
[14:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #247: STILL UNSTABLE in 29 min: https://kci.pangea.pub/job/xenial_unstable_kdepim-addons/247/
[14:45] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kaddressbook build #34: FAILURE in 45 min: https://kci.pangea.pub/job/zesty_stable_kaddressbook/34/
[14:45] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_blogilo build #22: FAILURE in 45 min: https://kci.pangea.pub/job/xenial_stable_blogilo/22/
[14:45] -kubuntu-ci:#kubuntu-devel- Project artful_stable_blogilo build #11: FAILURE in 45 min: https://kci.pangea.pub/job/artful_stable_blogilo/11/
[14:45] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_korganizer build #24: FAILURE in 46 min: https://kci.pangea.pub/job/zesty_stable_korganizer/24/
[14:46] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kdepim-runtime build #32: FAILURE in 46 min: https://kci.pangea.pub/job/zesty_stable_kdepim-runtime/32/
[14:46] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kmail build #35: FAILURE in 46 min: https://kci.pangea.pub/job/zesty_stable_kmail/35/
[15:35] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kaddressbook build #35: STILL FAILING in 45 min: https://kci.pangea.pub/job/zesty_stable_kaddressbook/35/
[15:36] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_blogilo build #23: STILL FAILING in 45 min: https://kci.pangea.pub/job/xenial_stable_blogilo/23/
[15:37] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_korganizer build #25: STILL FAILING in 46 min: https://kci.pangea.pub/job/zesty_stable_korganizer/25/
[15:37] -kubuntu-ci:#kubuntu-devel- Project artful_stable_blogilo build #12: STILL FAILING in 46 min: https://kci.pangea.pub/job/artful_stable_blogilo/12/
[15:37] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kdepim-runtime build #33: STILL FAILING in 45 min: https://kci.pangea.pub/job/zesty_stable_kdepim-runtime/33/
[15:37] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kmail build #36: STILL FAILING in 45 min: https://kci.pangea.pub/job/zesty_stable_kmail/36/
[15:38] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1492: SUCCESS in 1 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1492/
[15:38] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1492: SUCCESS in 1 min 11 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1492/
[15:41] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1492: SUCCESS in 3 min 41 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1492/
[15:41] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1492: SUCCESS in 4 min 7 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1492/
[15:48] <santa_> http://gpul.grupos.udc.es/ka-iron-hand_reports/plasma_staging/5.9.5_zesty_retry_builds.pdf
[15:48] <santa_> http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.9.5_zesty.html
[15:48] <santa_> acheronuk: ↑ so far so good
[16:49] <santa_> yofel: ping?
[17:10] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_systemsettings build #11: FAILURE in 6 min 47 sec: https://kci.pangea.pub/job/xenial_stable_systemsettings/11/
[17:16] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmenuedit build #11: FAILURE in 11 min: https://kci.pangea.pub/job/artful_unstable_kmenuedit/11/
[17:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #183: FAILURE in 35 min: https://kci.pangea.pub/job/zesty_unstable_plasma-desktop/183/
[17:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:43] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_systemsettings build #12: FIXED in 28 min: https://kci.pangea.pub/job/xenial_stable_systemsettings/12/
[17:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmenuedit build #12: FIXED in 23 min: https://kci.pangea.pub/job/artful_unstable_kmenuedit/12/
[17:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:46] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #13: FIXED in 41 min: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/13/
[17:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-desktop build #186: FIXED in 41 min: https://kci.pangea.pub/job/xenial_unstable_plasma-desktop/186/
[18:00] <acheronuk> ping santa_ valorie mparillo mamarley etc
[18:00] <mamarley> pong
[18:01] <acheronuk> have put sddm 0.14 for artful in ppa:kubuntu-ppa/staging-misc and ppa:rikmills/sddm-0.14
[18:01] <acheronuk> please test if you are able
[18:01]  * mamarley sudo apt update && sudo apt upgrade
[18:01] <acheronuk> just sddm in my ppa in case you don't want to add staging-misc
[18:02] <mamarley> I already have staging-misc, so no problem there.
[18:02] <santa_> ack
[18:02] <mparillo> What else do I get in staging-misc that might be new, shiny, and fragile?
[18:03] <acheronuk> new yakuake I think?
[18:03] <acheronuk> although not much change to that if you don't use wayland if I recalll
[18:05] <mparillo> Now that is interesting. I got some kf5.33 (I think) packages this morning and now that I boot my AA VM, it comes up black screen with cursor.
[18:06] <mamarley> acheronuk: sddm 0.14 seems to work here, thanks!
[18:07] <santa_> mparillo: that might be due to "not all packages are migrating from proposed at the same time" I'll check in a VM
[18:08] <mparillo> And my normal ctrl alt f3 seems to send the signal to the host, not the vm.
[18:08] <santa_> what are you using for virtualization?
[18:10] <mparillo> Oracle VM Virtual Box 5.1.20
[18:11] <santa_> I think to send ctrl+alt+F1 it was host_key+F1
[18:11] <santa_> iirc, but don't trust my memory very much
[18:11] <santa_> apparently each virtualization thing has its trick to do that
[18:14] <mparillo> Right-control F3 got me tty3
[18:14] <acheronuk> yes, in my case in VB it is host + (R_CTRL) + Fx
[18:14] <acheronuk> snap
[18:14] <santa_> mparillo: btw you might want to try virt-manager. it's a bit more tricky to setup than virtualbox but works great on ubuntu (at least for me)
[18:15] <mparillo> sudo add-apt-repository ppa:kubuntu-ppa/staging-misc
[18:16] <acheronuk> yep
[18:16] <mparillo> sudo apt update && sudo apt-full-upgrade -y
[18:18] <mparillo> More kf5.33 packages, sddm 0.14,
[18:18] <mparillo> What is the systemd version of sudo poweroff?
[18:19] <mparillo> systemctl poweroff says the Arch Wiki
[18:19] <mparillo> And it works.
[18:19] <mparillo> Restarting the guest
[18:20] <mparillo> And I have the blinding blue screen.
[18:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #184: FIXED in 36 min: https://kci.pangea.pub/job/zesty_unstable_plasma-desktop/184/
[18:22] <santa_> acheronuk: regarding KA, do you have any pending issue with it? I have added recently the installation of the bash cmpletion + updated the INSTALL file with your suggestion (mentioning you have to clone the ka-metadata)
[18:23] <santa_> s/cmpletion/completion/
[18:23] <mparillo> Starting Plasma, Starting Konsole, apt-cache policy sddm returns: 0.14.0-4
[18:24] <mparillo> I consider it a success. Even if SDDM does not have the guest login that LightDM had years ago.
[18:26] <acheronuk> santa_: nothing leaps to mins right now
[18:27] <santa_> great. I have done so many 'releases' to fix the flaws after "fir tree"
[18:27] <santa_> I think it will be just "2.0" soon
[18:27] <acheronuk> santa_: thank you for the work :)
[18:29] <santa_> finally we have a not yet perfect, but decent tooling! \o/ that will help to correct a bit the manpower lost in the team
[18:41] <clivejo> or lady power
[18:51] <santa_> scarlett
[18:52] <santa_> she made a fair big amount of the work in the early days of plasma 5
[18:52] <acheronuk> indeed
[18:59] <mparillo> In one or maybe even two releases in a row, she published more packages than anybody else in the entire *buntu community.
[19:03] <acheronuk> mparillo: I got up to 3rd in soyuz (package uploads) https://launchpad.net/ubuntu/+topcontributors
[19:04] <acheronuk> when you are doing 38 plasma packages, 76 frameworks and 230 odd apps packages regularly, you soon get there
[19:04] <acheronuk> kubuntu has silly numbers now
[19:16] <acheronuk> santa_: where did the do-all pim exception list go?
[19:17] <santa_> acheronuk: it's in ka-metadata on the top level dir, so you can still (black|white)list it
[19:18] <acheronuk> santa_: so it is! tnx
[19:36] <ahoneybun> wow krita has a artful build
[19:36] <ahoneybun> https://launchpad.net/~kritalime/+archive/ubuntu/ppa
[19:36] <ahoneybun> !info krita
[19:36] <ahoneybun> just a little bit newer in the ppa
[19:37] <acheronuk> ahoneybun: https://launchpad.net/ubuntu/+source/krita/1:3.1.3-0ubuntu1
[19:38] <ahoneybun> ahhh
[19:38] <ahoneybun> proposed?
[19:38] <acheronuk> the bot has not caught up yet it seems
[19:38] <ahoneybun> ahh
[19:38] <acheronuk> nope. release
[19:38] <ahoneybun> thanks acheronuk
[19:49] <ahoneybun> has anyone heard of a night mode for Plamsa?
[19:49] <ahoneybun> like how GNOME has
[19:49] <acheronuk> redshift?
[19:49] <ahoneybun> but built in
[19:49] <acheronuk> or do you mean something else?
[19:49] <ahoneybun> http://www.omgubuntu.co.uk/2017/02/gnome-night-light-blue-light-filter-linux
[19:50] <clivejo> https://github.com/kotelnik/plasma-applet-redshift-control
[19:51] <acheronuk> I have that
[19:51] <ahoneybun> has Plasma 5 really hit 2 years alread?
[19:52] <acheronuk> turn it off at this time of night, and the brightness near blinds me!
[19:52] <clivejo> poor Rik
[19:52] <ahoneybun> ahh it's in the repos too
[19:54] <ahoneybun> very nice thanks acheronuk and clivejo
[19:54] <acheronuk> relatively up to date as well, synced from debian
[20:28] <santa_> acheronuk: minimal testing for sddm done. i.e. I can login. another topic, if you don't have objections I would like to stage frameworks 5.33 for zesty and xenial
[20:29] <santa_> my idea is getting frameworks/plasma updated for zesty and xenial in the backports ppa's. plasma 5.8.x lts for xenial
[20:30] <santa_> regarding applications I would wait for 17.04.1, since 17.04.0 has many file conflicts (see the release-team kde mailing list)
[20:31] <santa_> also I need to develop some scriptery to cherry-pick some commits from neon to handle the file moving, let me see if I can find a sample....
[20:32] <santa_> https://packaging.neon.kde.org/applications/konsole.git/commit/?h=Neon/release&id=3ad8580238c3ed299a18f837c41b0f4124298d1c
[20:32] <acheronuk> report also say kdenlive is a load of cr*p in 17.04.0
[20:33] <santa_> ↑ like that one. we will need them otherwise upgrades are going to fail
[20:33] <santa_> what's the deal with kdenlive?
[20:33] <blaze> kde pim is also crap
[20:33] <blaze> I mean even crappier than always
[20:34] <acheronuk> santa_: there are still l10n packages in 17.04.0 I think?
[20:34] <santa_> I don't know
[20:34] <valorie> blaze: have you tried the new PIM?
[20:34] <acheronuk> neon has weird scriptery as they are injecting translation files into git build that don't have them by default
[20:35] <santa_> ahm, anyway I will focus on frameworks and plasma first
[20:35] <acheronuk> but I *thought* on our normal tarball builds the combination of tranaltions in apps, + residual l10n would work.
[20:36] <acheronuk> but we can stage and find out some time
[20:36] <acheronuk> santa_: ok
[20:36] <blaze> valorie: 16.12 is okay in terms of kde pim, but 17.04 is reportedly slow and sluggish
[20:36] <acheronuk> not 100% convinced on FW upgrade for xenial, but we can try it, test it, and see :)
[20:37] <santa_> in that regard, frameworks are kind of rolling release
[20:37] <valorie> blaze: http://kubuntu.org/news/kde-pim-update-now-available-for-zesty-zapus-17-04/
[20:37] <santa_> i.e. kde expects us to update the frameworks along with the plasma 5.8.x lts releases
[20:38] <valorie> acheronuk has been working on that for awhile
[20:39] <blaze> valorie: yeah, I've enabled backports already
[20:39] <acheronuk> santa_: ok. I obviously missed that KDE memo
[20:41] <blaze> also I'm happy with new kgpg, thank you acheronuk
[20:42] <santa_> acheronuk: the reason for that is that being libraries, if you have apps using the libraries you will only notice the bug fixes, not features. I think there was various threads about that in the release team mailing list
[20:42] <santa_> some people argued that decision in any case
[20:42] <acheronuk> blaze: cool. I don't use PIM much apart from akregator, so good reports are appreciated
[20:43] <santa_> regarding xenial backports I think it could be good to update the apps to 16.12.x too
[20:43] <santa_> and just leave plasma @ 5.8
[20:44] <acheronuk> yeah, I don't feel inclined to do a Qt transition for plasma again in the ppas
[20:45] <acheronuk> and plasma = 5.8 LTS is a good fit.
[20:45] <santa_> yeah
[20:45] <acheronuk> and less destructive for us (and mint)
[20:45] <acheronuk> *disruptive
[20:45] <acheronuk> lol
[20:46]  * clivejo nods knowingly
[20:46] <santa_> one of these days I have to dig a bit into mint
[20:46] <clivejo> see if its hard or soft inside?
[20:47] <valorie> mint is a plant!
[20:47] <acheronuk> santa_: worth looking at: http://packages.linuxmint.com/pool/main/m/mint-artwork-kde/
[20:47] <acheronuk> their artworl/settings package
[20:48] <clivejo> they use all of our packages don't they?
[20:48] <clivejo> just make it pretty
[20:48] <santa_> mostly I want to analyze the whole thing. then we will see
[20:48] <acheronuk> yep. and a package/upgrade-manager etc
[20:49] <santa_> cause maybe their forums are good source of feedback, etc.
[20:49] <acheronuk> santa_: yeah, I go on there
[20:50] <santa_> I know
[20:51]  * santa_ is a bit like kde secret service working on foreing soil - ubuntu
[20:52] <santa_> * foreign
[20:53] <clivejo> KDE have a secret service :O
[20:53] <acheronuk> what is that supposed to mean?
[20:54] <ahoneybun> yofel: ping ping
[20:54] <clivejo> is Harold like M ?
[20:55] <acheronuk> Harold? Harald? Haruld?
[20:55] <santa_> I don't have M and I miss that
[20:55] <santa_> they are all self-assigned missions
[20:56] <clivejo> or just S
[20:56] <clivejo> the S in Secret Service
[20:56] <santa_> so I have no one to report progress. it's a bit weird
[21:01] -KubuntuManual:#kubuntu-devel- [kubuntu-manual] ahoneybun pushed 1 new commit to master: https://git.io/v98u4
[21:01] -KubuntuManual:#kubuntu-devel- kubuntu-manual/master 66bd6f7 Aaron Honeycutt: change 'Muon Discover' to 'Discover' and 'KSnapshot' to 'Spectacle'
[21:17] <blaze> found a conflict http://paste.ubuntu.com/24494938/
[21:19] <ahoneybun> dist-upgrade might fix that blaze
[21:20] <santa_> hmm, I don't think so
[21:20] <blaze> kdialog package needs a Conflicts rule
[21:21] <santa_> both provide the same file on zesty and none of them is obsolete
[21:22] <santa_> wait
[21:22] <santa_> kde-baseapps-bin is
[21:23] <santa_> so Breaks/Replaces
[21:25] <santa_> hmm they are more packages affected
[21:25] <santa_> acheronuk: ↑ so we probably want to do a few SRU's with proper Breaks/Replaces
[21:26] <santa_> blaze: thanks for telling us about that
[21:27] <acheronuk> santa_: agreed.
[21:27] <blaze> no prob, but can't it just be removed from archive?
[21:29] <santa_> I guess we can remove it for artful, not sure for zesty. in any case that wouldn't fix the problem since you would get the same problem if you had the package installed there since a previous kubuntu release
[21:29] <blaze> sure
[21:38] <acheronuk> santa_: you merging kubuntu-dev-tools?
[21:38] <acheronuk> as http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-dev-tools/trunk/view/head:/debian/control
[21:39] <acheronuk> depends kde-baseapps-bin, though not sure what for right this sec......
[21:39] <acheronuk> if you build the deb
[21:42] <santa_> I have no idea why is needed either
[21:43] <santa_> in any case my idea for kubuntu-dev-tools is just moving to KA the few scripts we still use
[21:43] <acheronuk> that is what I thought
[21:43] <santa_> I was planning to edit a list in the wiki so we all can make an assessment about each program
[21:44] <santa_> in any case I think I'm going to rename the lib "lib" to "libka" in KA first I had in mind doing that for 2.1
[21:45] -KubuntuManual:#kubuntu-devel- [kubuntu-manual] ahoneybun pushed 1 new commit to master: https://git.io/v98rt
[21:45] -KubuntuManual:#kubuntu-devel- kubuntu-manual/master 5db33fe Aaron Honeycutt: built latexpdf
[21:52] <acheronuk> removed that dep and rebuild my -dev-tools deb. we shall see.
[21:53] <acheronuk> can't imagine it needs it for any or the ummm. 2 scripts I use!
[21:53] <santa_> which ones? kopypackages and klearppa I presume
[21:54] <acheronuk> that and update-seeds
[21:54] <santa_> aha
[21:54] <acheronuk> which is a trivial script really
[22:27] <clivejo> what is contents-amd64?
[22:31] <clivejo> acheronuk: the version of SDDM in your PPA and the one in unstable, is there delta in the packaging?
[22:33] <valorie> ok, restarting to test new plasma
[22:39] <clivejo> valorie: can you do anything, or know who to poke about this Network Error . (401) going on?
[22:50] <acheronuk> clivejo: yes, as you removed a couple of patches in unstable that still apply to the release tarball
[22:50] <clivejo> ah, Im uisng the unstable version, and it seems stable for me
[22:51] <valorie> clivejo: I think that the sysadmins might be the most likely folks to know
[22:51] <valorie> btw: after a restart, all is working fine with the new plasma
[22:51] <valorie> $ plasmashell --version
[22:51] <valorie> plasmashell 5.9.5
[22:52] <clivejo> plasmashell 5.9.90 :P
[22:52] <clivejo> mine's better
[22:53] <valorie> ohhoho
[22:53] <valorie> still running kci, clivejo?
[22:55] <clivejo> of course
[22:55] <clivejo> and Rik keeps breaking it :(
[22:56] <valorie> can't make omelets without breaking eggs.....
[22:57] <clivejo> he breaks a lot of eggs!
[23:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #860: SUCCESS in 7 min 29 sec: https://kci.pangea.pub/job/mgmt_merger/860/
[23:07] <clivejo> acheronuk: did I see you releasing krita to artful ?
[23:07] <clivejo> 3.1.3
[23:07] <acheronuk> yup
[23:08] <clivejo> :)
[23:08] <clivejo> just trying to get up-to-date with feeds, emails!
[23:08] <clivejo> kontact is working again :)
[23:08] <acheronuk> :D
[23:09]  * clivejo thanks the kontact fairies
[23:09] <clivejo> another ABI bump?
[23:09] <acheronuk> yes :(
[23:09] <clivejo> hummmm
[23:10] <acheronuk> hummmm... what?
[23:10] <clivejo> rather annoying
[23:10] <acheronuk> yes.
[23:11] <valorie> are we backporting anything to 16.04?
[23:12] <valorie> haven't updated that machine for awhile
[23:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #185: STILL FAILING in 3 min 49 sec: https://kci.pangea.pub/job/zesty_unstable_kstars/185/
[23:18] <santa_> valorie: http://gpul.grupos.udc.es/ka-iron-hand_reports/version_status.html I would like to backport frameworks 5.33, we also have to update the 5.8.x plasma lts
[23:18] <santa_> and maybe apps but that will come later
[23:19] <valorie> ok, so not done yet
[23:19] <valorie> I'll wait
[23:20] <santa_> yeap, I was trying to backport fw for zesty, but I hit some packaging bizarreness with the tooling
[23:20] <valorie> just as a test?
[23:20] <valorie> I mean, dunno how long it is worthwhile to do the work for zesty
[23:20] <valorie> beyond security....
[23:22] <santa_> I think it would be good to have the latest stable kde versions on zesty
[23:22] <santa_> we also have that plasma 5.9.5 sru on the table
[23:23] <valorie> running it now, it's great!
[23:24] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmag build #9: FAILURE in 16 min: https://kci.pangea.pub/job/artful_unstable_kmag/9/
 Personally unless it's a security measure, updates should be the LTS now
[23:35] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ksudoku build #9: FAILURE in 6 min 46 sec: https://kci.pangea.pub/job/artful_unstable_ksudoku/9/
[23:40] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_ark build #24: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/zesty_stable_ark/24/
[23:40] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kopete build #9: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/artful_stable_kopete/9/
[23:40] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kstars build #18: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/xenial_stable_kstars/18/
[23:42] <valorie> ahoneybun: we support zesty for 9 months though
[23:42] <valorie> so *some* work is worthwhile
[23:42] <valorie> at least until the next release
[23:42] <valorie> now xenial is forgotten
[23:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kile build #21: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/zesty_unstable_kile/21/
[23:43] <clivejo> when can we forget about yakkety?
 Xenial is not forgotten
 It's still an LTS
 And deserves updates to backports
[23:44] <valorie> oops, got them confused
[23:44] <valorie> it's yakkety that's done
[23:45] <valorie> I hate these silly names
[23:45] <valorie> just use the numbers
[23:50] <santa_> yeah it's nice to keep the backports updated for both xenial and zesty, regarding yakkety I don't plan to make any backport but I don't prevent anyone else from doing it
[23:51] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kstars build #12: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/zesty_stable_kstars/12/
[23:51] <santa_> regarding lts'es and latest stables it's a very good thing to keep the backports in shape because the versions there are the ones actually supported by KDE
[23:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdb build #8: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/artful_unstable_kdb/8/
[23:54] <valorie> !eol
[23:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kile build #8: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/artful_unstable_kile/8/
[23:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #9: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/artful_unstable_kopete/9/
[23:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_elisa build #19: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/xenial_unstable_elisa/19/
[23:55] <valorie> oh, July 2017, yakkety isn't quite gone
[23:55] <valorie> I stopped seeding the torrents though