[01:15] <axw> thumper, wallyworld_: I think the authorisation worker should be enabled for null
[01:15] <axw> the ubuntu user is there, after all
[06:40] <dimitern> morning all!
[08:44] <rogpeppe> dimitern: yo!
[08:44] <rogpeppe> dimitern: did you have a good one?
[08:44] <dimitern> rogpeppe, hey
[08:44] <dimitern> rogpeppe, oh yeah :) and much needed at that
[08:44] <rogpeppe> dimitern: cool
[08:45] <dimitern> rogpeppe, yourself?
[08:45] <rogpeppe> dimitern: yeah, good thanks
[08:45] <dimitern> rogpeppe, so what's cookin' ? i've been catching up on emails
[08:46] <rogpeppe> dimitern: same old same old, really
[08:46] <rogpeppe> dimitern: HA is coming along
[08:46] <dimitern> rogpeppe, sweet!
[08:46] <rogpeppe> dimitern: there was an interesting discussion about charms vs default series on the juju mailing list yesterday
[08:46] <rogpeppe> dimitern: you might want to contribute
[08:46] <dimitern> rogpeppe, yeah I read through it
[09:04] <dimitern> rogpeppe, weekly meeting is in 1 hour, right?
[09:04] <rogpeppe> dimitern: i think so
[09:04] <rogpeppe> dimitern: yeah
[09:07] <dimitern> rogpeppe, cheers
[09:11] <fwereade> morning everybody
[09:11] <dimitern> fwereade, morning!
[09:12]  * fwereade is having a happy fun water-main-leaking-into-electrics day
[09:12] <fwereade> dimitern, happy new year :)
[09:12] <dimitern> fwereade, to you too :)
[09:13] <dimitern> fwereade, that sounds dangerous
[09:13] <fwereade> dimitern, just got dominion hinterlands, looks interesting, haven't played it yet
[09:13] <fwereade> dimitern, indeed
[09:13] <dimitern> fwereade, sweet!
[09:13] <fwereade> dimitern, well the circuit breaker works at least
[09:13] <dimitern> fwereade, so in addition to leaky drains now the mains are causing issues
[09:13] <fwereade> dimitern, and we're ok for the moment because the water is off
[09:14] <fwereade> dimitern, well, we fixed the drains and they seem ok now
[09:14] <fwereade> dimitern, and hopefully it's just the one pipe
[09:14] <fwereade> dimitern, but, well, we shall see
[09:14] <dimitern> fwereade, *fingers crossed*
[09:14] <fwereade> cheers :)
[09:59] <jam> standup time
[09:59] <jam> https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.sbtpoheo4q7i7atbvk9gtnb3cc
[09:59] <jam> welcome back dimitern
[09:59] <dimitern> thanks jam
[10:00] <jam> mgz: poke ^^
[10:14] <axw> I can't get back onto the hangout, Internet access is very flaky
[10:15] <jam> axw: no problem, we'll just assign all the work to you :)
[10:15] <axw> hah
[10:15] <axw> I got on :)
[10:17] <jam> axw: did you get the !dead stuff sorted out?
[10:17] <jam> I managed to land the other changes for add-machine compatibility, but that is now the blocking point
[10:18] <axw> jam: yes, there's a CL up
[10:18] <axw> jam: it was pretty trivial, and there's a test now
[10:19] <axw> jam: https://codereview.appspot.com/48670045/
[10:23] <jam> axw: why are you passing "Dying" to the $unset?
[10:24] <axw> jam: the value is arbitrary, and ignored by $unset (but required, AFAIK)
[10:24] <jam> axw: its a JSON object so it does need a value in the key: value context.
[10:24] <axw> right, that makes sense
[10:25] <axw> I suppose it could've been nil
[10:29] <jam> axw: I'd prefer it be not something that looks like it might be a value, so "" or nil is fine
[10:29] <jam> Dying made me wonder if it was only unsetting it if it was Dying, or  etc
[10:29] <axw> jam: no worries, will update before landing
[10:29] <axw> yep, fair point
[10:56] <mgz> gah, dammit
[10:57] <jam> mgz: well there you are
[10:59] <natefinch> rogpeppe: btw, the pastebin in the meeting - most of those are git failures.  I was going to fix them this morning, since they obscure real failures for me
[11:00] <rogpeppe> natefinch: cool, thanks
[12:58] <jamespage> anyone fancy helping me with an odd juju/gccgo build issue? - https://launchpadlibrarian.net/162007788/buildlog_ubuntu-trusty-i386.juju-core_1.17.0-0ubuntu1~gccgo4_FAILEDTOBUILD.txt.gz
[12:58] <jamespage> can't reproduce this outside of a launchpad builder which is awkward
[13:00] <mgz> I shall look at it, and not be helpful am sure
[13:03] <mgz> src/launchpad.net/juju-core/charm/config.go:14:32: error: $WORK/launchpad.net/juju-core/schema exists but does not contain any Go export data
[13:03] <jam> jamespage: src/launchpad.net/goose/http/client.go:12:21: error: $WORK/launchpad.net/goose exists but does not contain any Go export data   "launchpad.net/goose"
[13:03] <jam> sounds like you have a stale build file
[13:03] <jam> ?
[13:03] <mgz> several modules
[13:03] <jamespage> jam: maybe - but the errors jump around
[13:03] <jamespage> so I suspect something toolish
[13:05] <mgz> does feel ording related or something, if you diff with a local build log that worked, are the modules coming up in the same sequence?
[13:07] <jamespage> mgz, broadley yes - I've tried a few things such as tweaking the -p flag - I think in a launchpad builder it default to -p 1 (single cpu)
[13:08] <mgz> you might be at the email-dave point then
[13:08] <jamespage> mgz, yeah - that's what I guess - I already pinged him
[13:09] <jamespage> mgz, trying to pull together a package that supplies both gccgo and golang-go built binaries
[13:09] <jamespage> well I have it locally
[13:18] <natefinch> rogpeppe: have you gotten a chance to look at the additions I made to replicaset? https://codereview.appspot.com/49290043
[13:19] <rogpeppe> natefinch: oops, perhaps i haven't published my comments
[13:19] <rogpeppe> natefinch: one mo
[13:19] <natefinch> rogpeppe: cool
[13:23] <rogpeppe> natefinch: reviewed
[14:37]  * rogpeppe goes for lunch
[16:00] <natefinch> arg, this kills me: // The Attempt and AttemptStrategy types are copied from those in launchpad.net/goamz/aws
[16:43] <rogpeppe> mgz: there's a bit of confusion between hostname:port and hostname only in our code. i wonder if we should consistently name the former "Address" (fitting in with the "address" as passed to net.Dial) and the latter "HostName"
[16:45] <rogpeppe> mgz: as it is, we've got net.Dial and now replicaset.Member.Address that hold a hostname:port combi, but instance.Address and state.Machine.PrivateAddress and others which hold host names only
[16:45] <mgz> rogpeppe: that sounds sensible
[16:46] <mgz> well, isn't there a better term...
[16:46]  * mgz goes to look at rfcs
[16:46] <rogpeppe> mgz: quite possibly
[16:47] <rogpeppe> mgz: net.Dial calls it "host"
[16:47] <mgz> 'authority' would be correct for the combo
[16:47] <mgz> [ userinfo "@" ] host [ ":" port ]
[16:47] <rogpeppe> mgz: maybe somehow "instance.HostName" seems a better fit than "instance.Host" to me though
[16:48] <rogpeppe> mgz: i think we should go with the Go convention of "address" for host:port
[16:49] <rogpeppe> mgz: it's used all over the place, and we can't change that in the Go tree
[16:49] <mgz> host is ipvX / ipv6 / ipv4 / reg-name
[16:49] <rogpeppe> mgz: alternatively we could use "HostPort"
[16:49] <rogpeppe> mgz: yeah
[16:50] <mgz> so, "registered name" where we explicitly mean not a ip address
[16:50] <mgz> I quite like hostport
[16:51] <rogpeppe> mgz: hostport is also used in go stdlib too, e.g. http://golang.org/pkg/net/#JoinHostPort
[16:51] <mgz> (looking at rfc 3986 btw, there have been several url ones that somewhat update each time)
[16:51] <rogpeppe> mgz: but it's not so widespread
[16:52] <rogpeppe> mgz: maybe we *should* consistently use Host and HostPort throughout
[16:52] <rogpeppe> mgz: it mirrors the string concatenation nicely
[16:53] <mgz> that sounds like a plan
[16:53] <rogpeppe> mgz: and instance.Host could grow on me, i think
[16:53] <rogpeppe> mgz: thanks
[16:53] <rogpeppe> mgz: i'll file a bug, and conform to that convention in new code
[16:56] <rogpeppe> https://bugs.launchpad.net/juju-core/+bug/1267541
[16:56] <_mup_> Bug #1267541: The name "Address" is used inconsistently <juju-core:New> <https://launchpad.net/bugs/1267541>
[16:58] <rogpeppe> mgz: the only problem with "host" is that it sounds like you're talking about the signified object, not the signifier. so "SelectInternalHost" sounds like it's looking for a particular host that happens to be internal, rather than looking for a host address that can be used internally.
[17:00] <mgz> right, works less well compounded, hostport likewise
[17:02] <rogpeppe> perhaps hostName (hostname?) and hostPort might be better
[17:48] <mgz> dstroppa: you have review
[17:49] <mgz> er... if codereview is actually up atm
[17:50] <mgz> okay, now it's back and the post went through
[17:52] <dstroppa> mgz: got that, thanks
[19:32] <fwereade> arosales, cmars, mgz, mramm2, I apologize for my absence this afternoon, the whole island had a power cut :/
[19:32] <mramm2> fwereade: no problem!
[19:33] <mramm2> randomly, friend of mine just messaged me a malta related video: https://www.youtube.com/watch?v=LXfVlCuWG6g
[19:34] <arosales> fwereade, no worries, thanks for the fyi
[19:34] <fwereade> mramm2, haha, I recognise that one :)
[19:35] <cmars> fwereade, no prob, we'll resched
[19:36] <fwereade> cmars, most of tomorrow is free for me I think
[19:37] <fwereade> (a 132kV something-or-other tripped at the delimara power station... 132kV seems like quite enough voltage for me to forget the other details)
[19:48] <thumper> 'ello
[19:48]  * thumper looks at the modest proposal email thread and gives it a miss
[19:59]  * thumper looks at the juju run work and tries to split it up into three chunks for review
[19:59] <thumper> also realised I missed some tests...
[20:00] <thumper> although in the last pipe
[20:00]  * thumper gets to work
[20:00]  * thumper things of music, perhaps dubstep
[20:13] <jcastro> thumper, ok, I am just going to use the vagrant image for everything
[20:14] <thumper> :)
[20:14] <jcastro> I don't understand why juju needs to put stuff all over the disk
[20:14] <jcastro> the minute something goes wrong the entire installation is worthless
[20:18] <thumper> jcastro: there are reasons...
[20:18] <thumper> perhaps we can discuss over a beer sometime
[20:18] <jcastro> sure
[20:19] <jcastro> maybe we should just tell people to always use vagrant?
[20:19] <jcastro> I've had to reinstall twice this cycle already. :-/
[20:19] <thumper> ?!
[20:19] <thumper> really?
[20:19] <thumper> that seems real screwy
[20:19] <jcastro> well, you couldn't fix it the first time
[20:48] <natefinch> thumper: what does git --version return for you?   I'm trying to figure out some of the tests that fail due to a newer version of git
[20:48] <thumper> natefinch: $ git --version
[20:48] <thumper> git version <IP_ADDRESS>
[20:49] <natefinch> thumper: and I presume uniter tests pass for you?  specifically the tests in worker/uniter/charm  ?
[20:49] <thumper> natefinch: yep, all passing
[20:49] <thumper> just ran them :)
[20:49] <natefinch> thumper: cool
[20:49] <thumper> busy breaking things up for review
[20:49] <natefinch> thumper:  they're broken with git 1.8.5 for whatever reason... one fix was easy, the other... well, I'm not sure yet
[20:50] <thumper> ack
[21:23] <natefinch> thumper: ahh, I see it.  "git add -A ." used to be a NOOP if there were no files to add.... now in 1.8.5 it errors out saying "no files match filespec '.'"
[21:23] <thumper> ha
[21:28] <natefinch> it bugs me that "apt-get upgrade foo"  does not work the way "apt-get install foo" or "apt-get remove foo" works.  Inconsistent UI is aggravating
[21:34] <thumper> :)
[21:35] <thumper> you have seen git koans right?
[21:46] <natefinch> thumper: sounds familiar
[21:49]  * thumper needs another coffee, and some food
[22:04] <mramm2> thumper: how are you on the networking stuff?
[22:05] <mramm2> looks like MaaS folks have scheduled an emergency huddle in 25 min
[22:05] <thumper> mramm2: not too hot, but I'm good at bluffing
[22:05] <bigjools> o/ mramm2
[22:05] <mramm2> ;)
[22:05] <thumper> bugger, games up
[22:05] <bigjools> I talked to thumper before xmas
[22:05] <bigjools> you were useless :)
[22:06] <mramm2> kapil is the best to talk to
[22:06] <mramm2> he wrote most of the existing network sketch
[22:06] <thumper> I'll come along to throw comments from the sideline
[22:06] <mramm2> but... he is in london at a sprint this week
[22:06] <thumper> not sure how much help I'll be
[22:06] <bigjools> yeah he was a "tentative" on the invite
[22:06]  * bigjools in another call until :30
[22:12] <mramm2> thumper: bigjools: I have a candidate who would like to talk to me in 30 min
[22:12] <thumper> bwahaha
[22:12] <mramm2> do you think I can duck out after the first few min of our call?
[22:45] <bigjools> thanks mramm2


 Late nights
[13:06] <Xpistos> early mornings
[13:26] <wrst> yes that i know :)
[13:32] <wrst> oh Xpistos i'm trying out Linux Mint DE
[13:33] <Xpistos> how do you like it
[13:33] <wrst> its pretty good, i'm updating still
[13:33] <wrst> since the disk was spun in DEC
[13:47] <cyberanger> wrst: if you like that, you should really try CB
[13:47] <wrst> CB?
[13:47] <wrst> cyberanger: ^
[13:48] <cyberanger> CrunchBang
[13:51] <wrst> ohh
[13:52] <wrst> i have thought about it
[13:52] <wrst> i think the next distro i will try will be debian cut when there are some releases of it
[14:00] <chris4585> wrst, have you tried sidux?
[14:01] <wrst> i did at one time but been a while chris4585
[14:01] <wrst> i was hoping that Mint DE would have my broadcom wireless easy to get going but that was not the case so i will have to mess with that some it appears
[14:01] <chris4585> I haven't heard much from them in a while, although I'm a little out of the loop
[14:10] <wrst> me either
[14:33] <netritious> good morning locotn
[14:44] <wrst> morning netritious hows it going out west?
[14:45] <netritious> going well...supposed to get some rain today but it *is* spring after all
[14:45] <netritious> how about yourself wrst?
[14:46] <wrst> pretty good netritious just getting some work done
[15:55] <wrst> hello pace_t_zulu
[15:55] <pace_t_zulu> sup wrst
[15:55] <pace_t_zulu> how's it going
[15:55] <pace_t_zulu> ?
[15:55] <wrst> its going well pace_t_zulu how about with you?
[15:55] <pace_t_zulu> i see netritious is stepping down... haven't had a chance to really respond to that... i can't really do the hosting... but i can help with the management and programming for sure
[15:56] <pace_t_zulu> it's going well here too wrst, ty
[15:56] <pace_t_zulu> wrst: how far along is you wife?
[15:57] <wrst> she has delivered pace_t_zulu, one week old baby girl
[15:57] <pace_t_zulu> congratulations to you both wrst!
[15:58] <pace_t_zulu> what's her name?
[15:58] <pace_t_zulu> you can pm me that if you want
[15:58] <wrst> Brianna Kate pace_t_zulu
[15:59] <pace_t_zulu> lovely name wrst
[15:59] <wrst> there is nothing secret in the world any way pace_t_zulu :)
[15:59] <wrst> thanks
[15:59] <wrst> pace_t_zulu:
[16:02] <netritious> how's it going pace_t_zulu
[16:02] <netritious> hosting is taken care of... Svpernova09 has it covered
[16:03] <pace_t_zulu> hey netritious sorry to hear you're stepping down... no worries though
[16:03] <pace_t_zulu> netritious: i can help with the programming side of things
[16:03] <netritious> it's already been moved, just waiting for cyberanger (or someone with domain control access) to update the name server entries
[16:03] <netritious> pace_t_zulu: just not enough time in the day :/
[16:03] <pace_t_zulu> i hear ya netritious
[16:04] <netritious> this past sun realized I had completely forgotten to organize the meetup for this past sat, and subsequently realized I just didn't have time anymore
[16:05] <netritious> and since W TN had two POC I figured it would be covered
[16:14] <Svpernova09> DNS is already updated for me, but that could just be your A records since I was poking at it.
[16:17] <netritious> Svpernova09: the NS entries have been updated?
[16:17] <Svpernova09> hmm, whois still shows old dns.
[16:17] <Svpernova09> Negative
[16:17] <Svpernova09> not according to godaddy's whois. whois.org is flagging a weird error.
[16:19] <netritious> I think that's just whois.org...
[16:19] <netritious> "whois ubuntu-tennessee.org" shows correctly
[16:19] <Svpernova09> Could be
[16:19] <netritious> at least it looks correct
[16:20] <netritious> yeah A records working great, just got to update those NS and transfer will be complete, but has to be someone with domain control, and I know cyberanger has access not sure who else does though
[19:07] <cyberanger> netritious: that someone should be you and pace too, but I don't mind doing it
[19:09] <cyberanger> netritious: so just let me know
[20:12] <netritious> i think at some point in time you sent me an email cyberanger, and I looked for it but not found...so please do by all means go ahead and upadte
[20:12] <cyberanger> update to what
[20:13] <netritious> that was kinda the reason for spreading it around in the first place I thought, you know, someone host the site, some get the domain, someone get the cert, etc
[20:13] <netritious> get my post to the list from yesterday?
[20:15] <cyberanger> yeah, right as I asked that (that list has been once a month, I check it once a day, realized it's probally there)
[20:15] <netritious> ns3.secure-trans.net and ns4.secure-trans.net
[20:15] <cyberanger> it's in the email
[20:16] <cyberanger> well, was the site ever spread out, if you just shut the box off, who had a copy to bring it back up
[20:16] <netritious> Joe
[20:16] <netritious> Svpernova09:
[20:17] <Svpernova09> yo
[20:17] <netritious> sorry Svpernova09 was answering cyberanger
[20:17] <Svpernova09> np
[20:18] <netritious> cyberanger: the site was backed up nightly around 1 am
[20:18] <netritious> remotely until the problems a few weeks ago
[20:18] <cyberanger> he had a copy of it before this email, and never was on that admin team, shoot
[20:18] <netritious> but working on integration with S3 when I have time
[20:19] <cyberanger> and I guess I gotta resend the dns info, and figure out where things sit
[20:19] <netritious> there is a plugin in the install to backup the site cyberanger
[20:19] <netritious> has been there from day 1
[20:19] <netritious> backs up the files, config, and mysql, prompts for d/l
[20:20] <cyberanger> didn't know that, ok, and only the admin team and Poc's have that?
[20:20] <netritious> so I guess the better question is, since you have admin access to WP, why don't you have a backup? :D
[20:20] <netritious> yes cyberanger
[20:21] <netritious> it was never my intention to "control" the site or anything of that nature
[20:21] <netritious> I know there are at least five admins atm
[20:21] <netritious> POCs and Svpernova09
[20:21] <cyberanger> I had PoCs and wrst, that's no good
[20:22] <netritious> wrst is admin too
[20:22]  * wrst resents being called no good
[20:22] <wrst> :)
[20:22] <netritious> +1 wrst
[20:22] <cyberanger> so PoCs, wrst and Svpernova09 have at least have a peice
[20:22] <wrst> well netritious more than likely true it just hurts :)
[20:23] <cyberanger> wrst: it's no good that not all of our site admins had full access
[20:23] <netritious> "You can't handle the truth!"
[20:23] <wrst> ha ha netritious very true
[20:23] <cyberanger> lol
[20:23] <netritious> they did
[20:23] <netritious> cyberanger: they did from the beginning
[20:24] <cyberanger> how did Svpernova09 get DNS info, I never sent it to him afaik
[20:24] <netritious> ericG, w4ett, and pace_t_zulu, mac9416 (worked on the design) and myself
[20:24] <cyberanger> since he isn't on my list
[20:24] <netritious> not sure I understand the question
[20:24] <cyberanger> and ericG never got DNS info (he was already gone)
[20:24] <netritious> Svpernova09 does not have access to the DNS cyberanger
[20:25] <netritious> and if I ever did I don't now
[20:25] <netritious> I think I logged in once when you first sent it
[20:25] <cyberanger> I GPG'd it to all PoC's, plus wrst
[20:26] <cyberanger> which at the time, was you, jfenn2199, pace_t_zulu, wrst, and myself (linuxman410 at the time did not have GPG info, that I think is fixed now)
[20:26] <netritious> I'm sure you did cyberanger, like I said I think I logged in once when you first set it up, or maybe a few weeks after
[20:27] <cyberanger> sounds like you had more admins I wasn't aware of, that also needed this info
[20:27] <netritious> WP admins do not necessarily need DNS admin access
[20:29] <netritious> but that's up to whom ever would need to make that decision
[20:29] <cyberanger> we already did, same vote you and I +1'd
[20:29] <netritious> cool
[20:29] <cyberanger> and that vote was forming a team to have that all
[20:30] <netritious> yeah sounds right
[20:30] <cyberanger> it's no big, it's working as it should
[20:30] <cyberanger> no single point
[20:30] <cyberanger> is failing
[20:30] <wrst> you know i'm not so wild about voting we need a benevolent dictator ! :)
[20:30] <netritious> yep, I'm of the same opinion cyberanger :)
[20:30] <netritious> whoops, I meant wrst :P
[20:30] <netritious> lol
[20:31] <wrst> ha ha
[20:31] <wrst> i think libya may have a dictator they need to trade off
[20:31] <cyberanger> wrst: ok, The Beatings will stop when Moral improves, my first decree
[20:31]  * wrst screams ouch
[20:31]  * cyberanger grabs his kicking boots and whip
[20:32] <wrst> cyberanger: i know what the website needs
[20:32] <cyberanger> premature pain, 10 more lashes
[20:32] <wrst> clipart... lots of clipart
[20:32] <wrst> and .gif dancing images
[20:32] <netritious> lol
[20:32] <wrst> and music that starts playing on loading
[20:32] <netritious> that would totally rock wrst
[20:32] <cyberanger> wrst: in other words, you want geocities to host it
[20:33] <netritious> lol
[20:33] <wrst> yes... netritious, cyberanger here you go one i would model it after: http://www.amazinggracebaptistchurchkjv.com/
[20:33] <wrst> the content is of a bunch of crazy people  but still the site...w ell i guess it well reflects that actually :)
[20:34] <netritious> I created a page or two for an old lady that wanted it for a home page to easily click to get to Oprah and some cooking show web sites back in 98? 99? something like that
[20:34] <wrst> and combine that site with this one: http://www.psalm118.org/
[20:34] <wrst> sorry but nutty churches have the worse sites for some reason
[20:34] <wrst> ha ha netritious :)
[20:35] <netritious> :D
[20:36] <netritious> and I think for search I linked Ask Jeeves
[20:36] <wrst> ha ha wow
[20:37] <netritious> yeah the web was terrible mostly back then, design wise anyway
[20:37] <wrst> yes but really no one knew what to do it was just getting going
[20:38] <wrst> in 98 what 3 years?
[20:38] <netritious> well longer than that actually
[20:38] <netritious> 93 was when it was opened for commerce
[20:38] <wrst> didn't the www get going in 95?
[20:38] <wrst> ahh ok netritious
[20:39] <netritious> but the internet was around before 93...i think it started in 79? maybe even 69
[20:39] <cyberanger> ok, changed, needs time to push out
[20:39] <netritious> ty cyberanger
[20:39] <cyberanger> (usually we see it in less than a half hour, could be up to 48 hours)
[20:40] <wrst> i think 60's netritious with darpanet
[20:40] <wrst> while algore was still to young to create it i think :D
[20:40] <netritious> "...the first two nodes of what would become the ARPANET were interconnected between Kleinrock's Network Measurement Center at the UCLA's School of Engineering and Applied Science and Douglas Engelbart's NLS system at SRI International (SRI) in Menlo Park, California, on 29 October 1969."
[20:41] <wrst> cool netritious :)
[20:41] <netritious> http://en.wikipedia.org/wiki/Internet
[20:41] <wrst> i bet the connection speed wish lightning fast
[20:41] <netritious> lol
[20:42] <netritious> yeah you had a lot of ram if you had 512K
[20:42] <netritious> heck 64k depending on what decade I guess
[20:44] <wrst> commodore 64 was my first computer netritious
[20:44] <netritious> anyway the first time I accessed arpanet was through CCI BBS in Memphis
[20:45] <netritious> it was boring as hell compared to the BBS though
[20:45] <netritious> that is an awesome computer wrst
[20:45] <wrst> its amazing how things have changed netritious
[20:45] <netritious> yeah
[20:45] <wrst> i started college in 1996, we accessed email through an old VAX system graduated in 2000 webmail etc etc etc
[20:46] <netritious> nice
[20:46] <netritious> MS?
[20:46] <wrst> yeah netritious great for games that were acquired through questionable means
[20:46] <netritious> winders?
[20:46] <netritious> ha ha
[20:46] <wrst> UNIX
[20:46] <netritious> no when you went to webmail
[20:47] <netritious> the webmail was on unix too?
[20:47] <wrst> yes but still hosted on that same UNIX system just provided a web interface actually i think it is still that way
[20:47] <netritious> nice
[20:47] <wrst> yeah just a web interface to access the UNIX system
[20:47] <netritious> well enough of all this reminiscing...making feel like I'm 60 already
[20:47] <wrst> i remember having a crazy old professor for a class that had 2nd year acccounting majors trying to program cobol
[20:48] <wrst> that was a joy
[20:48] <netritious> omg cobol no thx
[20:48] <wrst> 2nd year accounting majors for the most part arent' CLI UNIX type folks luckily i was
[20:48] <netritious> fortran was my introduction to programming in HS
[20:48] <netritious> but believe it or not I didn't do so well lol
[20:49] <netritious> it wasn't BASIC enough
[20:49] <wrst> i have never been a programmer but did have to do that an a little of VB for another class I took, I took a lot of MIS classes
[20:49] <wrst> BASIC oh yes i had to do some of that also :)
[20:50] <netritious> I was still writing BASIC in 2002 for MS-DOS programs with qbasic lol
[20:51] <wrst> ha ha
[20:51] <netritious> you know how it is in the accounting biz wrst...
[20:51] <wrst> but the good ol commodore 64 was a lot of fun i run an emulator on occasion just for fun
[20:51] <netritious> there are still today companies that use an MS-DOS program to run there inventory lol
[20:51] <wrst> yes netritious change is a dirty word
[20:52] <netritious> ok, maybe not, but maybe
[20:52] <wrst> yes for sure netritious i know a place that was atleast last year still using an old dos deal for their costing system
[20:53] <netritious> In 2005 I helped a company in Memphis move form a "CMS 2000" machine, which was an 8088/8087 with a 20M HDD lol
[20:53] <netritious> wow wrst, it still amazes me lol
[20:53] <wrst> wow :)
[20:53] <wrst> that is soemthign else
[20:55] <netritious> it was networked though...an old ISA 1 Mbps? I think that was it, but used the old MS peer-to-peer networking protocol
[20:55] <netritious> now they use MS Access database
[20:57] <wrst> ugh... that's not really better is it?
[20:57] <netritious> for them it was
[20:57] <wrst> i have a great hatred for access
[20:58] <wrst> maybe undeserved but just always hated it :)
[20:58] <netritious> and I got to brush up on my BASIC
[20:58] <netritious> lol
[20:58] <wrst> ha ha
[20:59] <netritious> I am almost positive it was MS-DOS 3.3, which I upgraded to MS-DOS 6, which the software refused to run then (idk why) so tried MS-DOS 5 and worked, which meant I could run QBASIC apps
[21:01] <netritious> so wrote an app that just ran a looped request to the DB via command.com and wrote out to CSV
[21:02] <netritious> took about a week to finish since it kept filling up the poor 20 MB hdd
[21:03] <wrst> netritious: i can't imagine trying to use a 20 MB HDD
[21:04] <netritious> the bounty was $1000 and I was pretty sure I could figure it out
[21:05] <wrst> well that could motivate someone to use a 20MB HDD money=great motivator for me
[21:05] <netritious> wrst: exactly
[21:06] <wrst> :)
[21:07] <netritious> wrst: I tried an old IBM micro channel card in an ISA slot connected to a 80 MB hdd but couldn't get the system to recognize it so added a free space check to the loop which really slowed it down, but it did the trick
[21:08] <wrst> well if you are using a 20MB HDD is speed really a factor? :)
[21:08] <netritious> from there just imported the CSV into Access, wrote a few VBA forms, done
[21:08] <netritious> yes, when the company is using the DB at the same time it is a factor :)
[21:08] <wrst> ahh :)
[21:09] <netritious> but they promised not to add inventory until it was done, so it worked out
[21:10] <netritious> I'm pretty sure BASIC is dead now though lol
[21:13] <netritious> in the past decade I have taught myself ASP, PHP, and Delphi turbo pascal and became pretty  proficient in each, some Cold Fusion (::gag::), a little perl, a tiny smidgen of python, etc etc...whatever comes my way that pays I'm game usually
[21:13] <netritious> a little C++/.Net too
[21:14] <netritious> my latest is BASH and I'm loving it
[21:22] <chris4585> bash <3
[21:36] <netritious> chris4585: BASH is about as close to BASIC as it gets I think lol
[22:05] <cyberanger> netritious: well, good news, OpenDNS has the new record
[22:06] <cyberanger> I have the old record cached in my server (gotta do a purge tonight anyhow) and it's also cached on Google's Public DNS
[22:06] <cyberanger> so it is propagating
[22:07] <cyberanger> looks like your records are for 3600, so tomorow it'll be taken care of for everybody
[22:07] <cyberanger> looks like Svpernova09 has a higher record, double at least
[22:08] <chibihogoshino> i worship his shadow
[22:09] <cyberanger> oh, and if that's true netritious, I'm a fan to the closest thing to BASIC ;-)
[22:09] <cyberanger> chibihogoshino: I don't follow
[22:10] <chibihogoshino> lexx reference
[22:11] <chibihogoshino> http://www.youtube.com/watch?v=pEQzyZb84dU
[22:12] <cyberanger> ah


 I was all focused on adding network-get to charm helpers I miss read that what I really need in the charm is relation-get
[20:11] <rick_h> wallyworld: so I got it all working and realized...hmm...the address I need isn't in this new network-get output
[20:12] <rick_h> wallyworld: updating to use relation-get now instead and will test out. Is that backward compatible with pre-2.3?
[20:12] <wallyworld> rick_h: relation-get still contains the old private-address value, yes
[20:12] <wallyworld> juju 2.3 will put in the new stuff also
[20:13] <rick_h> wallyworld: gotcha, so 2.3 is ingress-address and if that's not there fall back to private-address for backwards compat
[20:13] <wallyworld> yep
[20:13] <wallyworld> so you want to get what the remote unit's address is?
[20:13] <wallyworld> as opposed to using network-get to see the local unit's info?
[20:14] <wallyworld> rick_h: I ask because i thought the prometheus charm was using unit-get
[20:14] <wallyworld> hence the replacement for that is network-get
[20:15] <rick_h> wallyworld: it's using: hostname = relation_data.get('hostname')
[20:15] <rick_h> wallyworld: so I'm updating that line to build the newer address details
[20:15] <wallyworld> ok. i also recall unit-get being used
[20:15] <wallyworld> somewhere in a hook
[20:15] <rick_h> wallyworld: yes, in the address of prometheus itself
[20:15] <wallyworld> that should use network-get
[20:15] <rick_h> wallyworld: so that'll need to be setup so that it's listening/sending the right info to things that relate to it (e.g. grafana)
[20:16] <rick_h> wallyworld: right
[20:16] <wallyworld> so your network-get charm helper work is still needed
[20:16] <rick_h> wallyworld: so the work on network-get is not in vain, but atm just trying to get the telegraf->prometheus part working and that's the the relation-get update
[20:17] <wallyworld> ok
[20:17] <rick_h> wallyworld: anyway, basically I freaked out and ping'd and now I'm unfreaked out and on to working more. sorry for the noise
[20:18] <wallyworld> rick_h: no worries, sorry i didn't see stuff earlier, was in sessions etc
[20:18] <rick_h> wallyworld: completely figured as much. All good
[20:18] <wallyworld> am excited to see this working
[20:18] <rick_h> bdx: is as well. He was asking about it and is doing some demo material for work around it
[20:19] <wallyworld> great
[20:19] <rick_h> wallyworld: bdx has some questions on what gets returned when used in a vpc and such
[20:19] <rick_h> so once I get the charms behaving I'll ask him to do some vpc testing and make sure things are looking cool
[20:19] <wallyworld> ok. i can't tell you off hand what is returned. cmr just reads the public address recorded against the machine
[20:20] <wallyworld> whatever that is
[20:20] <rick_h> wallyworld: right, so there might be bugs filed because if he binds against vpc specific networks he won't want his stuff on the public network. His vpc is making sure different models can speak to each other
[20:20] <wallyworld> right. that's not something we support yet
[20:21] <rick_h> ok, good to know. bdx will love to test it out when it does :)
[20:21] <wallyworld> not sure how much time we'll have this cycle
[20:21] <wallyworld> we were told to cut scope to just support public addresses for now
[20:21] <rick_h> k
[20:22] <wallyworld> if there's a driver to do the next step, we can look at what we can do
[20:22] <rick_h> well still, it'll be good to have bugs on the books with repro steps and users wanting things
[20:22] <wallyworld> exactly
[20:23] <bdx> theres a driver!
[20:24] <bdx> me
[20:25] <bdx> the public address stuff ..... I don't even have a use for (not that others won't)
[20:25] <bdx> but like
[20:26] <zeestrat> Count me in for use cases with non-public addresses.
[20:26] <bdx> even the MAAS <-> AWS stuff I have planned all happens over VPG to our vpc
[20:26] <bdx> so the MAAS instances have no idea the AWS instances aren't local
[20:27] <bdx> well ok
[20:27] <bdx> so the majority of the aws instances I will be connecting to don't have public ips
[20:27] <bdx> they are all in private NAT subnets that dont get public ips
[20:28] <bdx> so, I don't think I even have to worry about it for the most part
[20:28] <bdx> because juju will just think (for aws instances in NAT subnets) the public ip is the private ip, because it will be the only ip
[20:30] <bdx> wallyworld, rick_h: from what I can see, I will encounter an issue when I want to make a CMR from an instance with both public and private ips (AWS instance in IGW subnet that gets public ip auto assigned)
[20:31] <bdx> but even then, I can just use "--via" right?
[20:31] <rick_h> bdx: yea, we'll have to play with it and put together notes on what's there what's next.
[20:31] <bdx> kk
[20:31] <rick_h> bdx: so you can on the relate command, but what the charm reads from the hooks...
[20:31] <bdx> ahh
[20:31] <rick_h> bdx: it might be that it'll be more maas/openstack friendly at the start. JAAS has some work to support it as well.
[20:32] <wallyworld> i think if there's no public address recorded it will fall back to private
[20:32] <wallyworld> so long as those are routable between models it should work
[20:32] <bdx> wallyworld: I can deal with that
[20:32] <bdx> awesome
[20:32] <wallyworld> *should*
[20:32] <wallyworld> :-)
[20:41] <bdx> wallyworld, rick_h, jpk: having an issue with standard lxd deploys to instances using aws provider and 2.3beta2, getting http://paste.ubuntu.com/25715842/
[20:41] <bdx> ahhhh
[20:42] <bdx> AWS isn't a supported provider for the default FAN type probably I bet
[20:44] <bdx> per the release notes "On AWS, FAN works out of the box"
[20:44] <bdx> :(
[20:45] <wallyworld> bdx: sorry, in meeting, will respond soon if i can
[20:45] <bdx> np
[20:45] <bdx> thx
[20:58] <jam> bdx: please file a bug, I have the feeling it is a problem with the interaction between a defined space and fan configuration
[20:58] <jam> since 'common-nat' isn't a space name that Juju would have set up
[20:58] <jam> so I'm guessing you added it
[21:25] <bdx> jam: yeah
[21:25] <bdx> https://bugs.launchpad.net/juju/+bug/1722661
[21:25] <mup> Bug #1722661: FAN - unable to setup network <juju:New> <https://launchpad.net/bugs/1722661>
[21:42] <jam> bdx: are you trying to test out fan, or are you wanting to just have a container behind nat?
[21:43] <bdx> jam: I was just taking 2.3 for a test drive .... thought I would start out with testing what happens when I type in something familiar
[21:43] <bdx> :)
[21:46] <bdx> I like what I see for the non-space-constraint instance though
[21:46] <bdx> jam: I wonder if it has anything to do with the fact that my common-nat space is a nat subnet
[21:46] <jam> bdx: sounds possible
[21:47] <bdx> the ips that the containers get from the provider are basically elastic ips right?
[21:48] <bdx> I see
[21:48] <bdx> so, this is a limitation then?
[21:50] <bdx> the limitation being that provider type FAN networking for AWS is limited to subnets with routing tables that use an IGW


[03:50] <Turkey> turkey got a real job
[03:50] <Turkey> !!!!
[03:50] <Turkey> now the trick is getting paid to do irc. amirite?
[10:20] <rmg51> Morning
[10:29] <jackson> moin
[12:25] <bergmenno> hey there jackson
[12:25] <jackson> hello bergmenno
[12:25] <jackson> this where i usually hang out
[12:26] <bergmenno> nice
[12:26] <bergmenno> i have some experience
[12:26] <bergmenno> with ubuntu
[12:26] <bergmenno> i've worked with a raspberry pie
[12:26] <jackson> cool
[12:26] <bergmenno> for school
[12:26] <jackson> and the ardurio
[12:26] <bergmenno> no not that one
[12:27] <bergmenno> haha
[12:27] <jackson> i have done automated computer systems most of my working life
[12:27] <jackson> and retired in 1993
[12:29] <jackson> you can use hexchat and configure it to work with your operating system
[12:29] <bergmenno> wait, you are retired?
[12:30] <bergmenno> you told you are 66
[12:30] <jackson> but I am mostly on </server spotchat #cheese>
[12:30] <jackson> 62
[12:30] <bergmenno> ow
[12:30] <bergmenno> haha
[12:31] <jackson> i have been doing IRC since 2001
[12:31] <bergmenno> good for you!
[12:31] <bergmenno> these chats have helped me so many times
[12:32] <bergmenno> brb, i have to walk the dog
[12:32] <jackson> ok nice to meet you and see you some other time   btw   go to ##windows and ask that question about your problem
[12:32] <jackson> ok
[13:00] <bergmenno> nice meeting you too
[13:01] <jackson> ok i and going to try to sleep so cya
[13:01] <jackson> u2
[13:02] <bergmenno> cya
[13:20] <teddy-dbear> Morning peoples, dogs, turkeys?, hamsters and everything else
[13:21] <jackson> o/ teddy-dbear
[13:21] <teddy-dbear> o/
[16:14] <bergmenno> well this was a wonderfull conversation
[19:18] <jackson> bergmenno:
[19:18] <bergmenno> yes?
[19:19] <jackson> pls go to the server Spotchat
[19:19] <bergmenno> what is a spotchat even? i'm a noob i know
[19:20] <jackson> sorry
[19:20] <jackson> i put my self back in to it
[19:20] <jackson> its like this server
[19:20] <jackson> the channel is #cheese
[19:21] <bergmenno> i joined the cheese server
[19:21] <bergmenno> now what?
[19:23] <jackson>  just close what you did and go to : /server Spotchat.org   #cheese
[19:25] <jackson> type or paste this then hit enter   </server spotchat.org  #cheese>
[19:25] <bergmenno> </server spotchat.org  #cheese>
[19:25] <bergmenno> my god i'm stupid...
[19:25] <jackson> leave out the <>
[19:25] <bergmenno> can't do it
[19:25] <bergmenno> </server spotchat.org  #cheese>
[19:25] <jackson> we all are sometimes  lol
[19:26] <bergmenno> but what are you tryoing to ghet me to do then?
[19:26] <jackson> you are now in the server ubuntu irc
[19:27] <jackson> by using /server is like using /join
[19:27] <bergmenno> uhu, i get that
[19:27] <jackson>   </server spotchat.org  #cheese>
[19:28] <bergmenno> there is a mistake while making contact with the server
[19:29] <jackson> ok try /server spotchat #cheese
[19:29] <jackson> or
[19:29] <jackson> use /server spotchat    once there use /join #cheese
[19:30] <bergmenno> same story
[19:30] <bergmenno> i can't join it
[19:30] <bergmenno> but why would i want to join cheese?
[19:32] <jackson> ok goto http://www.mibbit.com and got there after filling in the blanks
[19:32] <bergmenno> i can do join cheese right here
[19:33] <bergmenno> i just did
[19:33] <jackson> its a littlee difficult and this might be easer
[19:33] <jackson> ok i go to go bbiab
[19:34] <bergmenno> what's that?
[19:37] <jackson> bebackinabit
[19:37] <bergmenno> kay


[04:55] <peachdu> Hello!
[13:56] <anipinto> When trying to update to 24.04, I had put on hold snap package. The do-release-upgrade failed and right away some programs failed with missing library: libcrypto.so.3. Is there any way to restore the system usb live ubuntu or only reinstalling?
[13:57] <anipinto> I put on hold snap due firefox and using xfce as Desktop Environment.
[15:36] <tomreyn> anipinto: if you have backups, you can restore them, otherwise a fresh install is probably a good idea. i assume you are aware that upgrades are not yet supported.
[15:38] <anipinto> tomreyn: the upgrade was suggested by do-release-upgrade. I think I was able to restore enought for it to start.
[15:39] <tomreyn> anipinto: were you on 23.10 or 22.04? what's the exact do-release-upgrade command that suggested the upgrade?
[15:42] <anipinto> I was on 23.10 and simply ... I think was a simple do-release-upgrade ... no sure if I may add '-d'
[15:42] <tomreyn> i think you must have added -d
[15:43] <anipinto> but if upgrade not supported, should continue? or allow to do it? didn't see any warning message
[15:44] <tomreyn> quoting https://help.ubuntu.com/community/NobleUpgrades "If you want to upgrade early, before upgrades are officially supported, you can pass the -d option when running do-release-upgrade. Do this at your own risk. It is advised to check the release notes for Ubuntu 24.04 LTS before doing so."
[15:44] <tomreyn> by specifying -d, you have effectively overridden the warning
[15:45] <anipinto> ok ... noted, I normally used '-d' to upgrade to non LTS versions
[15:45] <tomreyn> that's not how you'd do that either
[15:45] <tomreyn> you'd change the release type you want to upgrade to
[15:46] <tomreyn> "Make sure the Prompt line in /etc/update-manager/release-upgrades is set to 'normal' if you want non-LTS upgrades, or set to 'lts' if you only want LTS upgrades. "
[15:46] <tomreyn> i'm referring to the server section here, but you have equivalent options on the GUI
[15:47] <anipinto> always learning ... I still have two more pcs to update, I will wait to be supported and hope to run smoothly
[15:48] <tomreyn> it's always a good idea to read the ubuntu flavor's as well as ubuntu's own release notes before you start an upgrade.
[15:50] <tomreyn> to have the best chance of your upgrade succeeding, i'd also recommend to uninstall any software and downgrade any software versions installed from 3rd party repositories, and to disable those repositories before you start.
[15:51] <anipinto> one of the problems, I think was having snap marked to not be installed
[15:53] <tomreyn> that's one of the issues which should no longer occur once the upgrade path has been tested
[15:53] <tomreyn> or rather once it's been declared stable
[15:55] <anipinto> tomreyn: thanks for your time
[17:05] <JoeLlama> asus trash computer when it comes to xubuntu :(
[17:14] <JoeLlama> It's gunna go back to Costco... don't get me wrong, itsa E1404F and relatively solid laptop except for that crappy track pad but overall a good machine.
[17:15] <JoeLlama> But their one main flaw... the have no respect for the linux community!
[17:15] <JoeLlama> So I'm gettin' a Dell


[00:16] <gf2> Hello,   I am working on a Thunderbird ticket that has to do with the license being outdated.  I created a Mozilla upstream ticket. The reporter suggests that the issue is with ubuntu packaging rather than Mozilla. Is that correct?  Here is the bug number:
[00:16] <gf2> https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1028267


[01:22] <teward> sarnold and security team: heads up during Lunar cycle we may have some things shifting in nginx so source *and* binary packages may end up in separate packages and to stay in core, etc. may need some main inclusion.  should be the same exact codeset just in different source packages.  just giving you all the heads up
[01:22] <teward> (we're starting these changes in Debian heh)
[01:22] <teward> (since we have nginx-dev and 'nginx dynamic modules as separate packages' functional in Unstable and Testing)
[01:39] <sbeattie> teward: ack, thanks for the heads up.
[21:12] <sdeziel> it's always fun when a package from universe I happen to use gets a free security fix ... thanks mdeslaur for patching unbound ;)


[05:13] <slangasek> stgraber: shim black screen reproduced here
[05:13] <stgraber> good (well, not really but glad it's not yet another thinkpad-specific weirdness)
[05:20] <slangasek> yeah
[20:44] <slangasek> stgraber: ok, rebuilding old version of shim with gnu-efi 3.0s appears to give the same behavior, so looks like it's a gnu-efi regression
[21:08] <bdmurray> slangasek: perhaps you could review the ubuntu-release-upgrader in quantal-proposed as there is a tester waiting...
[21:09] <slangasek> bdmurray: looking
[21:26] <slangasek> bdmurray: backslashreplace> that part's a no-op here because ENCODING is always UTF-8, right?
[21:27] <slangasek> otherwise, if you *actually* got backslash replacement of the user input string, it would never match the right strings
[21:28] <slangasek> bdmurray: accepted, anyway
[21:34] <bdmurray> slangasek: yes, I believe it is a no-op.  this is actually mvo's patch I was just shepherding into quantal
[21:50] <slangasek> bdmurray: ack
[22:23] <stgraber> slangasek: fun...
[23:05] <NCommander> Any SRU team members awake?
[23:36] <infinity> NCommander: Yes.


[00:00] <valorie> this feels so good
[00:28] <sgclark> clivejo: I don't know what ods is, but we need to use whaat ever debian is using. I we absolutely do not have the resources to support anything different.
[00:30] <clivejo> sgclark: http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkolabxml.git/ or http://anonscm.debian.org/cgit/pkg-kolab/libkolabxml.git/
[00:31] <sgclark> uh kubuntu seems the safer route
[00:31] <clivejo> Ill have to look at it tomorrow, have to get some sleep now
[00:32] <sgclark> yeah no worries
[00:34]  * sgclark also takes a break
[00:34] <clivejo> I cant open KCI pages any more
[00:35] <sgclark> yourhint to sleep ! :)
[00:38] <valorie> sweet dreams, clivejo
[00:49] <sgclark> wow finally
[00:50] <valorie> oh this warms my heart
[00:51] <sgclark> we fixed them awhile ago. For whatever reason CI was broken with ssh errors.
[00:53] <valorie> <3
[00:54] <sgclark> noooo
[02:07] <ahoneybun> I'm going to give today's daily a try in a VM
[02:07] <ahoneybun> if all works I might wipe my laptop
[04:00] <ahoneybun> oh good
[04:00] <ahoneybun> *god
[04:54] <valorie> what the heck
[04:55] <valorie> randomly click on one of the failures, and it says: 0 errors, 0 warnings
[08:07] <yofel> sgclark: just asked flocculant to not release our beta images. Ubiquity is fine, so this was a success at least
[08:12] <valorie> user just reported https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1549656 and I wonder if it can have anything to do with the pim troubles
[08:22] <yofel> nah, that's backports - we didn't even ship apps there
[08:22] <yofel> although that sounds somewhat familiar...
[08:22] <yofel> oh right, the qtbase abi stuff
[08:24] <valorie> ah, right
[08:24] <valorie> btw, are we ever moving things from wily backports-landing into backports?
[08:24] <valorie> not that it's a big deal, but it is better
[08:24] <valorie> imo
[08:34] <yofel> clivejo: ^ ?
[10:09] <clivejo> yofel: I dont use wily here at all.  soee_ arranged testing for plasma 5.5.4 and it appears to be stable.
[10:10] <yofel> ok, then copy it please
[10:12] <clivejo> how?
[10:13] <yofel> just use the kopypackages command
[10:14] <clivejo> gimme a minute, my head is in another space right now
[10:15] <yofel> sure, rather get it right instead of doing things in a hurry
[10:15] <clivejo> in a different space and time
[13:26] <sgclark> morning
[13:33] <clivejo> good morning sgclark
[13:33] <sgclark> morning clivejo
[13:33] <clivejo> sleep well?
[13:34] <BluesKaj> Hey all
[13:36] <sgclark> I did kinda sorta not really haha
[13:36] <clivejo> hi BluesKaj
[13:36] <clivejo> no no no but yeah
[13:47] <BluesKaj> hi clivejo
[14:00] <clivejo> yofel sgclark these are failing due to upload
[14:00] <clivejo> kubuntu-ci/unstable has packages in it with an epoch
[14:00] <clivejo> which we removed in apps 15.12.1
[14:01] <sgclark> um unless they were reanmed, that is notpossible
[14:01] <sgclark> ugh
[14:01] <sgclark> lets try that again. Unless they were renamed we cannot drop the epoch
[14:02] <sgclark> if they were indeed renamed, you will need to delete the offending packages from the ppa
[14:03] <sgclark> it can take up to 24hours before they fully go away.
[14:03] <yofel> if they were indeed renamed, there should be no reason for the upload failure...
[14:03] <sgclark> true
[14:03] <yofel> unless someone mistakenly uploaded a package at some point
[14:04] <yofel> note: source rename is not sufficient here, rename of source and all binaries is
[14:05] <soee> :)
[14:08] <clivejo> yofel: what packages am I copying?
[14:08] <yofel> everything from backports-landing into backports
[14:10] <clivejo> ./kopypackages -a ppa:kubuntu-ppa/backports-landing wily ppa:kubuntu-ppa/backports wily ?
[14:11] <clivejo> bloody symbols
[14:11] <yofel> looks right..
[14:12] <yofel> look at the backports ppa page for any copy failures after that
[14:13] <clivejo> eakk
[14:13] <yofel> --sync can tell you errors during the copy process
[14:14] <yofel> but that's "officially deprecated" (I still use it all the time)
[14:14] <clivejo> http://lubuntu.me/happy-st-patrick/
[14:15] <yofel> hehe
[14:16] <clivejo> anyone with artist skills to do a Kubuntu one with Konqi?
[14:17] <yofel> didn't ahoneybun do some design stuff lately?
[14:18] <yofel> we don't really have a designer since sheytan stopped doing them
[14:18] <clivejo> is it just me or do JR and Linus T look very alike?!?
[14:19] <BluesKaj> it's just you :-)
[14:19] <yofel> right, totally just you
[14:20] <BluesKaj> Linus is quite ordinary looking, and much older than JR
[14:22] <clivejo> pim has final drove me mad!
[14:22] <soee> if you need some artwork talk to alexl on telegram chan
[14:23] <clivejo> soee: I dont *need* it
[14:23] <clivejo> just might be fun!
[14:23] <clivejo> need a bit of fun before KCI drives us all nuts
[14:25] <yofel> starting with next release we should do some fun stuff every now and then
[14:25] <yofel> I remember when the xubuntu team put a christmas wallpaper into the dailies for a while
[14:25] <yofel> that was nice
[14:26] <clivejo> how do I list the people on the Kubuntu channel on telegram?
[14:26] <clivejo> I can see 16 people but no idea who they are
[14:27] <BluesKaj> clivejo, what is about KCI that's causing so much trouble
[14:27] <BluesKaj> ?
[14:27] <clivejo> numerious reasons
[14:27] <soee> clivejo: start typing @
[14:28] <soee> it will try to autocompete user name for you
[14:28] <BluesKaj> too numerous to mention , sounds serious ;/
[14:28] <clivejo> soee: would you ask him please?
[14:28] <soee> about what exactly ?
[14:28] <soee> i'm not sure what this conversation here is about :D
[14:29] <clivejo> BluesKaj: LP problems, not enough packagers to fix the packaging issues. upstream causing confusion with public/private libs
[14:29] <clivejo> soee: http://lubuntu.me/happy-st-patrick/ maybe doing one for Kubuntu and Konqi
[14:30] <BluesKaj> clivejo, wish i could help, but unfortunately my skills aren't up to the tasks :/
[14:30] <clivejo> make Konqi into a leprechaun!
[14:30] <sgclark> heh did not know telegram group was still alive, left it due to spam
[14:31] <clivejo> yofel: just one failure - Copying failed of sddm (0.13.0-1ubuntu5~ubuntu15.10~ppa1)
[14:31] <clivejo> sddm 0.13.0-1ubuntu5~ubuntu15.10~ppa1 in wily (version older than the sddm 0.13.0-1ubuntu5~ubuntu15.10~ppa2 in wily published in wily)
[14:31] <yofel> that's ok
[14:31] <yofel> thanks!
[14:31] <sgclark> <3 St Patrick's Day +1 to artwork
[14:31] <clivejo> yup
[14:31] <acheron88> my graphics skills began and ended with with MSPaint in about 1992
[14:32] <sgclark> lol
[14:32] <sgclark> Coral Paint here
[14:32] <clivejo> would be amazing if it could be done in Krita
[14:33] <sgclark> yes it would
[14:33] <acheron88> I try do do things in GIMP occasionally, and fail
[14:33] <acheron88> or Krita
[14:34] <clivejo> sgclark: Kolab OBS - https://obs.kolabsys.com/repositories/Kolab:/Winterfell/Ubuntu_16.04/
[14:34] <sgclark> ok? we still need to match debian.
[14:35] <sgclark> We simply do not have the resources to diverge from them at this point
[14:35] <sgclark> as you probably know..
[14:36] <clivejo> I know
[14:36] <clivejo> Im stripping out the useful stuff and intent to copy it into debian
[14:37] <clivejo> did you make the xenial branch - http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkolabxml.git/
[14:38] <clivejo> I have a local one, didnt think I had pushed anything yet
[14:40] <sgclark> I have not touched kolab in over a year. never in debian git. looks like they did?
[14:40] <sgclark> seems to me clone it and typing uscan should do the trick..
[14:42] <clivejo> there is http://anonscm.debian.org/cgit/pkg-kolab/
[14:42] <clivejo> and Sandro Knauß works for Kolab Systems I believe
[14:44] <clivejo> but then we have http://anonscm.debian.org/cgit/pkg-kde/kubuntu/ for some reason
[14:45] <sgclark> yes he does
[14:45] <clivejo> all very confusing
[14:46] <clivejo> KCI has libkolab
[14:47] <clivejo> but not libkolabxml
[14:47] <clivejo> sitter: do you know why KCI only builds libkolab and not libkobalxml?
[14:49] <clivejo> can someone re-invite me to the kubuntu channel on telegram?
[14:52] <sitter> clivejo: latter has no ci branch
[14:52] <sgclark> me too
[14:52] <clivejo> sitter: is there a reason for that?
[14:52] <sitter> nobody created one
[14:52] <clivejo> could we create one?
[14:53] <sitter> sure
[14:53] <clivejo> I believe kdepim-runtime now needs it :/
[14:54] <clivejo> sitter: how do we create a new CI instance?
[14:54] <clivejo> or job or whatever the terminology is!
[14:54] <yofel> I don't have sgclark in my Telegram contacts, and clive has no username
[14:55] <clivejo> eakkk
[14:55] <clivejo> thats not Scarlett!
[14:57] <sitter> clivejo: one creates a branch and then smiles at me beguilingly
[14:57]  * clivejo smiles like a crazy person
[14:57] <yofel> there we go
[14:57] <yofel> Telegram is confusing
[14:58] <clivejo> thanks yofel
[14:58] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkolabxml.git/
[15:00] <clivejo> sitter: you need a kubuntu_unstable branch?
[15:01] <sitter> or _stable. or both. depends on what you wish to CI
[15:01] <soee> sitter: look like this http://img2.wikia.nocookie.net/__cb20140203012822/tdicamps/images/thumb/b/ba/Horse-smile.jpg/500px-Horse-smile.jpg ?
[15:02] <clivejo> thats no smile!
[15:02] <sitter> ^
[15:02] <soee> ah smile .. :D
[15:02] <sgclark> we need both
[15:03] <clivejo> sitter: Ive created a kubuntu_unstable
[15:03] <soee> http://875357559f655c0fd9842374.eventingnation.netdna-cdn.com/wp-content/uploads/2014/02/Smiling-horse.jpg
[15:03] <clivejo> sgclark: we do?
[15:03] <sgclark> yes
[15:03] <clivejo> ok Ill add stable
[15:03] <clivejo> libkolab doesnt have a stable branch
[15:03] <clivejo> should it?
[15:03] <sgclark> stable is what is in staging ppa, would be nice to know of failure before we push to archive
[15:03] <sgclark> clivejo: yes pelase
[15:04] <clivejo> ok - http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkolabxml.git/ for packaging
[15:04] <sgclark> my typing is extra horrendous today yay
[15:05] <clivejo> and added new stable branch here - http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkolab.git/
[15:07] <clivejo> that horse needs its teeth brushed!
[15:11] <clivejo> sitter: Source : https://git.kolab.org/diffusion/LK/libkolabxml.git
[15:12] <sitter> it occurs to me that is pointing elsewhere
[15:41] <clivejo> sitter: what you mean - pointing elsewhere?
[15:42] <sitter> clivejo: git ls-remote https://git.kolab.org/diffusion/LK/libkolabxml.git
[15:42] <sitter> checkout the branch names
[15:42] <sitter> that's libkolab not libkolabxml xD
[15:46] <flexiondotorg_> Can I just confirm Kubuntu are not participating in Beta 1?
[15:48] <sgclark> Correct, until  our Ffe is approved we are stuck.
[15:48] <clivejo> yofel sgclark ^
[15:49] <clivejo> sitter: git clone https://git.kolab.org/diffusion/LKX/libkolabxml.git
[15:53] <flexiondotorg_> sgclark, Thanks. Sorry to hear that :-(
[15:53] <clivejo> sitter: do you know why KCI has stopped working out the downstream projects?
[15:54] <sitter> http://kci.pangea.pub/search/?q=kolab
[15:54] <sitter> clivejo: should be working again I think
[15:55] <clivejo> oh yeah, its saying that kdepim-runtime and libkolab are downstream
[15:55] <clivejo> that wasnt working earlier
[15:55] <clivejo> did you fix it?
[15:57] <clivejo> sitter: many thanks
[15:59] <sitter> shadeslayer did
[16:00] <clivejo> its a very useful feature to find problems :)
[16:00] <clivejo> thanks shadeslayer
[16:00] <sitter> it's also required to have jobs built in the right order ;)
[16:05] <clivejo> indeed!
[16:14] <clivejo> now theres a surprise!
[16:42] <cyphermox> Riddell: hey, are you done committing to ubiquity? just want to make sure we don't conflict for a commit :)
[16:43] <cyphermox> (or you'll just want to pull again)
[16:53] <clivejo> o/ genii
[16:54] <clivejo> yippeeee
[16:54] <yofel> cyphermox: jonathan doesn't work on kubuntu anymore.
[16:54] <genii> Hi clivejo :)
[16:55] <yofel> oh, unless he sent in neon specific stuff
[16:55] <cyphermox> yofel: well he was committing to ubiquity earlier: http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6385
[16:55] <clivejo> yofel cyphermox: I believe hes been working on fixing and bradning the installer to Neon
[16:55] <yofel> right, brain lag -.-
[16:55] <cyphermox> I don't know of other places to reach him (other than email of course)
[16:56] <clivejo> http://weegie.edinburghlinux.co.uk/~jr/tmp/ubiquity.png
[16:56] <clivejo> I must say I like it!
[16:56] <cyphermox> it's not a problem, I just wanted to make sure I wouldn't break his workflow by adding commits in between
[16:56] <yofel> cyphermox: #kde-neon, but here is fine
[16:56] <yofel> I was just confused for a moment
[16:56] <cyphermox> ack
[16:58] <cyphermox> you want to tell me when the installer changes are ready to land from your end? no point in making multiple uploads :)
[17:00] <clivejo> sgclark: I think libkolabxml is working now, so I have triggered a libkolab rebuild (compiled against the new libkolabxml)
[17:01] <sgclark> clivejo: great!! I have a meeting, can you rebuild kdepim-runtime after?
[17:02] <clivejo> sgclark: rebuild on KCI?
[17:02] <sgclark> and staging  ppa both
[17:02] <sgclark> probably kci first to see if it fixes our problem
[17:03] <clivejo> have to do a few things, but Ill rebuild on KCI
[17:03] <clivejo> tends to be easier to spot problems on KCI
[17:04] <clivejo> sitter: what is mgmt_daily_promotion_xenial_unstable ?
[17:08] <clivejo> yofel: extra-cmake-modules is throwing a lintian warning - BUILD_QTHELP_DOCS , Generate QtHelp documentation for installed modules.
[17:08] <clivejo> what does that mean?
[17:20] <sgclark> clivejo: looks like it is looking for a qt module? maybe new in 5.6?
[17:46] <Riddell> cyphermox: yeah I'm done for now thanks
[18:22] <cyphermox> Riddell: should I upload?
[19:04] <clivejo> sgclark: any idea why libkgapi - 5.1.0-1ubuntu1~ubuntu16.04~ppa1  is in the kubuntu-ci unstable ppa?
[19:04] <sgclark> something required it
[19:04] <sgclark> I dont recall what
[19:04] <clivejo> in the KCI PPA?
[19:05] <sgclark> your asking me? is that what ppa your talking about?..
[19:06] <sgclark> I copied it due to something failing. if it bothers you then remove it
[19:06] <clivejo> Im just investigating why its failing
[19:06] <sgclark> oh it is? then remove it
[19:06] <clivejo> the package seems ok, just cant upload due to there being a newer version
[19:06] <sgclark> I lost track of the initial reason I copied it anyway
[19:06] <clivejo> trying to figure out where it came from
[19:07] <clivejo> if it is version 5.1, surely we should bump it
[19:07] <sgclark> upload where?
[19:07] <sgclark> what?
[19:07] <sgclark> I am so confused
[19:07] <clivejo> why?
[19:07] <clivejo> who?
[19:07] <clivejo> LOL
[19:07] <sgclark> hha
[19:08] <sgclark> libkgapi is not on the same version as app
[19:08]  * genii breaks out the extra-caffeinated stuff and passes the mugs around
[19:08] <sgclark> apps
[19:08] <sgclark> http://download.kde.org/stable/libkgapi/5.1.0/src/
[19:09] <sgclark> 5.1.0 is right
[19:09] <clivejo> http://kci.pangea.pub/job/xenial_unstable_libkgapi/
[19:09] <clivejo> then we need to bump it in KCI
[19:09] <sgclark> I think we do not have a CI branch though or something. ugh my head is killing me, can't think
[19:10] <sgclark> dang we do. why did I think we didn't
[19:10] <sgclark> ugh
[19:10] <clivejo> mind if I do it?
[19:11] <clivejo> is the packaging somewhere else too?
[19:11] <clivejo> I assumed it was here - http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkgapi.git/
[19:11] <sgclark> I already packaged it..
[19:12] <clivejo> where?
[19:13] <sgclark> I amlooking. I will merge it when I find it
[19:13] <clivejo> no change to that packaging in 6 months
[19:13] <clivejo> on debian git always
[19:13] <clivejo> anyways
[19:19] <sgclark> ah maxy said I could use http://anonscm.debian.org/cgit/pkg-kde/kde-extras/libkgapi.git/
[19:19] <sgclark> clivejo: ^
[19:19] <clivejo> aye, this is our problem
[19:20] <Riddell> cyphermox: sure
[19:20] <clivejo> KCI must be using http://anonscm.debian.org/cgit/pkg-kde/kubuntu/libkgapi.git/
[19:21] <clivejo> we need some kind of standard on this
[19:24] <sgclark> well sadly it is up to the maintainer. I would prefer to keep to using debians branches, but it gets tricky with kde-extras
[19:24] <sgclark> in this particular case though we have permission
[19:25] <sgclark> sitter: how do we change the repo in kci?
[19:26] <sgclark> ugh I think this migraine is going to win
[19:48] <clivejo> F'ing symbols
[19:56] <ahoneybun> well that 16.04 daily installed fine in a VM but not real hardware lol
[19:56] <ahoneybun> the partitioning failed
[20:25] <clivejo> I hate akonadi/PIM and the whole entire stack!
[20:45] <ahoneybun> sgclark, I'm getting some downloads done in 15.10, what do I need to add to get a building system up?
[20:46] <ahoneybun> also I have an SSD in here so things should be fast
[20:46] <ahoneybun> or decent lol
[21:00] <sgclark> ahoneybun: backorts ppa
[21:00] <ahoneybun> right, getting that now
[21:00] <sgclark> backports too
[21:00] <ahoneybun> both lol
[21:02] <clivejo> https://youtu.be/nlHiHP98g5M
[21:02] <ahoneybun> mparillo, how is the NVIDIA stuff currently?
[21:02] <clivejo> LMAO
[21:03] <ahoneybun> ?
[21:13] <mparillo> ahoneybun: I do not know. All I know is that Xenial works for me in both a VM and on real HW.
[21:14] <ahoneybun> mm I let 15.10 go and it is a black screen with the mouse moving
[21:15] <mparillo> Hmmm, BluesKaj has helped others with a similar issue
[21:16] <ahoneybun> I was updating so I'm a bit scared to reboot
[21:16] <ahoneybun> tty works
[21:16] <ahoneybun> it did
[21:20] <ahoneybun> you should have removed the ~test1 off of the package lol
[21:45] <ahoneybun> mm
[21:45] <ahoneybun> how SDDM just restarts
[21:45] <ahoneybun> I login, it goes black and then back to login
[21:51] <ahoneybun> fixed
[21:51] <ahoneybun> holy crap 5.5.3 is pretty
[22:00] <valorie> so much green today!
[22:01] <valorie> would be nice get all the xenial reds turned to green
[22:02] <soee> ahoneybun: i think it is/was intel related bug
[22:02] <soee> i had it often on intel profile, but not now on nvidia
[22:03] <ahoneybun> soee, using the intel card gave me a glitchy screen sometimes
[22:03] <ahoneybun> always on the tip
[22:03] <ahoneybun> *top
[22:03] <soee> disable/enable effects
[22:03] <ahoneybun> I have nvidia on now
[22:04] <soee> ah ok :)
[22:05] <ahoneybun> we'll see how hib works lol
[22:08] <ahoneybun> soee, https://drive.google.com/file/d/0B6zAAODZFwQ2TUlScG9MbjJuc3M/view?usp=sharing
[22:08] <soee> :)
[22:08] <valorie> pretty!
[22:09] <ahoneybun> I do like it ALOT
[22:09] <ahoneybun> hugs to sgclark, yofel, and clivejo
[22:09] <soee> ahoneybun: Plasma 5.6 will be more smooth than 5.5
[22:09] <valorie> btw ahoneybun, you've not been around lately, so I should mention that the kde wikis are read-only for right now
[22:10] <valorie> they have been upgraded and just the new login is left to finish
[22:10] <ahoneybun> valorie, I saw that when Alex from telegram asked me to add a link to our group chat
[22:10] <valorie> they were hit spam attacks
[22:10] <valorie> ok
[22:10] <ahoneybun> yea so was the Ubuntu Wiki
[22:10] <ahoneybun> I was thinking of adding that to the topic but it is so fun now!
[22:10] <valorie> I can fix for now, I have editing powerz
[22:10] <clivejo> ahoneybun: enable landing and upgrade to 5.5.4
[22:11] <valorie> clivejo: are you putting that into backports today?
[22:11] <ahoneybun> valorie, I'll pm you the telegram link and you can add it?
[22:11] <clivejo> copied today
[22:11] <valorie> yes, if you tell me the page
[22:11] <valorie> oooo, nice!
[22:11] <valorie> sec
[22:12] <clivejo> valorie: is there anything we can do to get our FFE accepted?
[22:13] <sgclark> ...
[22:20] <ahoneybun> sgclark, I've updated fully I believe, what can I do?
[22:20] <sgclark> go back in time and help us with merges.
[22:20] <sgclark> ahoneybun:  a bit late :) we are waiting on ubuntu release team to accept our Ffe
[22:20] <clivejo> ahoneybun: fix pim
[22:21] <sgclark> clivejo: nothing to fix needs kolab
[22:21] <ahoneybun> mm as Google would say "Tardis function is not available"
[22:21] <ahoneybun> sgclark, ^
[22:21]  * sgclark winders why she is here
[22:21] <ahoneybun> FFE?
[22:21] <sgclark> feature freeze exception
[22:22] <ahoneybun> sgclark, https://youtu.be/L9_gsh4Ktsc?t=23
[22:22] <ahoneybun> sgclark, https://youtu.be/L9_gsh4Ktsc?t=21
[22:33] <valorie> sgclark: the red stuff in kci still need fixing, right?
[22:33] <valorie> ahoneybun could help with that?
[22:33] <valorie> and the packager doc
[22:35] <ahoneybun> mm I need to ask questions about that
[22:36] <sgclark> muon needs to be removed.
[22:37] <sgclark> alot of red right now is working itself out. We are still recovering from the ssh breakage.
[22:37] <sgclark> but yes ahoneybun feel free to help with whatever you are comfortable with
[22:38] <ahoneybun> well with the Docs I would like a hangout so I can get an idea of what we need to tell new packagers and key info
[22:39] <ahoneybun> so we know how we want to format it and present it
[22:47] <valorie> ahoneybun: we have the notes
[22:47] <valorie> https://notes.kde.org/p/kubuntu-packaging
[22:47] <valorie> I think they got a bit neglected as the rush was on
[22:48] <valorie> what I was planning to do was try to use what we have to set up and package something, and add anything a newb would need
[22:48] <valorie> since I'm a total newb
[22:53] <ahoneybun> I think we should documentation how we go about packaging something simple and then detail what to do if that does not work
[22:53] <ahoneybun> like clivejo and his symbols
[22:55] <kkinetix> valorie: ahoneybun: I could happily comment on the kubuntu-packaging notes page, being a full newb to the kubuntu/ubuntu/debian packaging process
[22:55] <valorie> agreed
[22:55] <valorie> kkinetix: all you need is a KDE Identity to login to that notes page
[22:56] <valorie> yes, we need more beginners making it better
[22:56] <kkinetix> I have that... I'm saying I've been looking at it and have some comments on it
[22:56] <valorie> the experts already know -- it's us beginners who have the questions, and need a doc
[22:57] <sgclark> We have one expert - yofel >.<
[22:58] <kkinetix> valorie: Right, exactly.  I think the whole "What you need" section needs to go.  They sound like pre-requisites to doing any packaging, and they're clearly not.  They're thing that can come afterward after you've got familiar with some simple packages onesself.
[22:58] <clivejo> git clone yofel
[22:58] <sgclark> right! lol
[22:58] <kkinetix> I think it's amusing that the "What you need" section states "A KDE identity account for access to the team notepads" -- you can't be reading this document if you haven't gone and got a KDE Identity account
[22:58] <yofel> that reminds me of the apachelogger class that harald had once
[22:58] <clivejo> something really strange going on with kactivities
[22:58] <yofel> good old times
[22:59] <valorie> well, "go" as in move elsewhere
[22:59] <valorie> kkinetix: we intent to move this to the wiki once it is more done
[22:59] <valorie> and the wikis are open for editing
[22:59] <clivejo> yofel: can you give some guidance on what debian git repos we should use?
[22:59] <sgclark> well perhaps change it to "what you need to apckage for Kubuntu"
[23:00] <yofel> clivejo: context?
[23:00] <sgclark> yofel: clivejo: that is entirely up to debian : yofel: context: kde-extras packages
[23:00] <clivejo> libkolab, libkolabxml, libkgapi
[23:01] <sgclark> all kde-extras ^\
[23:01] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/kubuntu/
[23:01] <soee> someone want to answer: https://plus.google.com/u/0/117234606839873900533/posts/VDhBT3vwUmV ?
[23:01] <yofel> hm, that's up to debian. I *think* they said us using the kde related repositories was fine
[23:01] <clivejo> I have been using this archive, as this is what KCI uses
[23:02]  * clivejo bites tongue
[23:02] <clivejo> Ill pass soee
[23:02] <yofel> just make sure the package is maintained by debian-qt-kde, otherwise you'll probably annoy someone
[23:02] <sgclark> soee: done
[23:02] <yofel> OTOH, you only have access to that anyway
[23:03] <soee> sgclark: thank you
[23:04] <kkinetix> valorie: I know there's a lot of prerequisite reading to do to make sense of parts of this document, but if it's for newbies there's lots of "Do *this*" statements in it that need to either provide examples or syntax or answer "How, exactly, again?"
[23:04] <sgclark> right, so it is better to get permission, because those kubuntu repos will not have activity from debian in most cases. we should update kci as need, if I can get instructions on how to do so..
[23:04] <yofel> oh right
[23:07] <clivejo> can debian merge them together ?
[23:08] <clivejo> and delete the kubuntu repo?
[23:12] <sgclark> well they are our repos, I expect the job of merging would be ours. They have to delete though. First and foremost we need to collect the names of all packages in this situation and ask them for each of them.
[23:12]  * sgclark makes trello card
[23:14] <ahoneybun> sgclark, what is the kci building? Applications?
[23:16] <sgclark> ahoneybun: everything. We had a bit of a blowup with an ssh failure. THese are rebuilds recovering from that.
[23:16] <ahoneybun> ok ok
[23:16] <ahoneybun> *oh ok
[23:17]  * clivejo is going "Build Now" mad
[23:35]  * clivejo explodes in rage
[23:37] <valorie> look at the green!
[23:37] <valorie> not just the red
[23:42] <ahoneybun> someone just bought me a Razer keyboard as a joke
[23:42] <ahoneybun> XD
[23:49] <clivejo> time for bed
[23:49]  * genii puts the coffee away and gets out the beer
[23:52] <valorie> ahoneybun: https://community.kde.org/Telegram is the page, I just need the invite link (right now we just have kubuntu official there)
[23:59] <ahoneybun> sgclark, thank you for repling to that G+ post
[23:59] <sgclark> np


[07:46] <tsdgeos> Mirv: ping
[08:06] <Mirv> tsdgeos: pong
[08:06] <tsdgeos> Mirv: spoke to thiago yesterday, he's shelving the dbus changes for Qt 5.6
[08:07] <tsdgeos> in case you need to free a silo or something
[08:08] <Mirv> tsdgeos: ok, it'd good to know. I wonder if we can manage without them. we'll notice of course if we get QDBus related crash traces.
[08:13] <tsdgeos> Mirv: i guess we will
[08:19] <tsdgeos> dednick: just tested and commented in https://code.launchpad.net/~nick-dedekind/ubuntu-settings-components/fix-maximumWaitBufferInterval/+merge/257347
[08:19] <tsdgeos> please check i'm not testing the wrong thing :D
[08:19] <dednick> tsdgeos: there's a branch to go with it now. should probably add that to the MP
[08:20] <tsdgeos> please
[08:20] <dednick> tsdgeos: there's a bug in the indicator mock which throws off the AP test
[08:20] <dednick> tsdgeos: done
[08:20] <dednick> https://code.launchpad.net/~nick-dedekind/unity8/fix-laggy-indicators-autopilot/+merge/258411
[08:20] <dednick> tsdgeos: ^
[08:21] <tsdgeos> tx
[08:26] <pstolowski> tsdgeos, hey, i've sent you the proposal for edit widget
[08:26] <tsdgeos> okidoki
[08:28] <tsdgeos> i'll have a look soon-ish
[08:31] <tsdgeos> dednick: unity8.application_lifecycle.tests.test_application_lifecycle.ApplicationLifecycleTests.test_greeter_hides_on_app_open is still failing as autopilot test, did you have a look at it or should we find someone else to?
[08:31] <dednick> tsdgeos: I didn't have a look at that one. only the indicator ones
[08:32] <dednick> tsdgeos: i can take a look at that one as well though
[08:33] <tsdgeos> dednick: that'd be great
[08:33] <tsdgeos> maybe we can get green back \o/
[08:34] <dednick> tsdgeos: lol. for a day or 2 at least ;)
[08:34] <tsdgeos> until the next landing :D
[08:47] <dednick> tsdgeos: um. is the greeter supposed to hide if an app opens?
[08:47] <dednick> tsdgeos: what if you have a password?
[08:48] <dednick> tsdgeos: oh, i think it might just be that the greeter is swiped away, but not "unlocked"
[08:50] <tsdgeos> dednick: right
[08:51] <tsdgeos> which actually the test seems to be doing
[08:51] <tsdgeos> so have to check where it's failing
[08:52] <dednick> tsdgeos: yeah. looks like it can't find the proxy or something. but checking on ubuntu-app-list shows the fake app. will need to look into it in more detail.
[08:53] <dednick> tsdgeos: works if you have the greeter open though :/
[08:53] <dednick> unlocked i mean
[08:54] <tsdgeos> dednick: you mean wihtout password?
[09:04] <tsdgeos> pstolowski: why author?
[09:05] <pstolowski> tsdgeos, i suspect we may want to display your name as we do with existing reviews (i don't have visuals to confirm)?
[09:05] <pstolowski> tsdgeos, but maybe not
[09:05] <tsdgeos> pstolowski: but can't we do that with a text widget or something? that's how we do it now, no?
[09:06] <tsdgeos> maybe not
[09:06] <pstolowski> tsdgeos, now we do it with 'reviews' widget (see the doc i linked to)
[09:06] <tsdgeos> right
[09:06] <pstolowski> tsdgeos, 'reviews' widget takes multiple tuples and has ;'author' for each
[09:07] <tsdgeos> pstolowski: let's have it in there, it won't hurt and then we can decide whether to show it in the ui or not
[09:07] <pstolowski> tsdgeos, +1
[09:08] <tsdgeos> just answered the email for completion
[09:09] <pstolowski> tsdgeos, cool, thanks
[09:12] <dednick> tsdgeos: no, if you enter the password manually while it's "waiting for whatever it is waiting for"
[09:13] <dednick> tsdgeos: nevermind. i'll figure it out ;)
[09:13] <tsdgeos> dednick: that's weird i don't remember that test went past the locker
[09:13] <tsdgeos> dednick: :)
[09:14] <dednick> tsdgeos: it's possible we're suspending the app before AP is able to get the proxy for introspection.
[09:14] <tsdgeos> may be
[09:14] <tsdgeos> afaik this test used to work not very long ago
[09:17] <Saviq> tsdgeos, dednick, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1446846/comments/2
[09:17] <Saviq> tsdgeos, dednick, I think the problem there is that we're left with the lockscreen after having spawned the app
[09:18] <Saviq> so greeter hides, sure, but the lockscreen's still on
[09:18] <dednick> Saviq, tsdgeos: ubuntu-app-watch says the apps are being paused. both dash and fake app.
[09:19] <Saviq> yup
[09:19] <tsdgeos> Saviq: sure but that's always been the way it worked and i think that test passed "before"
[09:19] <tsdgeos> for some definition of "before"
[09:19] <tsdgeos> obviously way before you filed the bug
[09:20] <dednick> tsdgeos: perhaps we need to modify the test. it's making the assumption that the app is in a "running" state at some arbitrary time after starting
[09:20] <dednick> where that should only definately the case after we unlock the greeter.
[09:21] <dednick> Saviq: ^?
[09:21] <Saviq> dednick, yeah, definitely a test issue
[09:25] <dednick> Saviq, tsdgeos: hm. unfortunately it's autopilot/launcher code that's waiting for the proxy :/
[09:26] <Saviq> tsdgeos, fwiw I think we "fixed" the fact that the apps were getting focused under lockscreen at some point
[09:26] <Saviq> dednick, we might need to trick the lockscreen to go away in this test
[09:26] <Saviq> tsdgeos, *or* the mock lightdm refactor
[09:27]  * Saviq wonders if that test wasn't relying on the "single" lightdm mock
[09:27] <tsdgeos> may be
[09:27] <tsdgeos> dednick: do we have a review checlist for https://code.launchpad.net/~nick-dedekind/ubuntu-settings-components/fix-maximumWaitBufferInterval/+merge/257347 ? or do i use the unity8 one and that's it?
[09:27] <dednick> Saviq: well, we can force the lockscreen open, but that's cheeting a bit ;)
[09:28] <dednick> *cheating
[09:28] <dednick> tsdgeos: yeah, let me add it quick
[09:28] <Saviq> dednick, I think we have the mock lightdm with no password for this use case
[09:28] <dednick> tsdgeos: oh. review. don't think we have one
[09:28] <dednick> just an MP one
[09:29] <tsdgeos> dednick: well the test is about "opening app hides greeter", it's not cheating to put there a greeter that helps us testing
[09:30] <tsdgeos> dednick: oh, i just realized i can't top approve https://code.launchpad.net/~nick-dedekind/ubuntu-settings-components/fix-maximumWaitBufferInterval/+merge/257347 you'll need to find someone that's on the team
[09:30] <dednick> tsdgeos: i meant that it's cheating to force the lock screen open explicitly. since it skips what we're testing. not having a password enabled it's cheating.
[09:30] <tsdgeos> dednick: no no, because having the lock screen is fine
[09:31] <tsdgeos> it's what's it is supposed to do
[09:31] <tsdgeos> swipe the greeter away
[09:31] <tsdgeos> if you have no lock screen then you get the app
[09:31] <tsdgeos> if you have lock screen then you get the lockscreen
[09:31] <Saviq> dednick, tsdgeos, LIBLIGHTDM_MOCK_MODE=single will fix the test I reckon
[09:31] <tsdgeos> so we can either adapt the test to just check that the greeter went away and not test the app is running
[09:32] <tsdgeos> or we can adapt the test to check the greeter went away and the app is running
[09:32] <dednick> cimi: can you add Unity team to the ubuntu-settings-components team?
[09:32] <cimi> dednick, yup
[09:32] <tsdgeos> i have no particular opinion on what's better
[09:33] <dednick> Saviq: how do i set the env var for a single test, or do i need to move it to another test suite?
[09:33] <dednick> since u8 is started by setup
[09:33] <Saviq> dednick, grep for LIGHTDM in tests/autopilot, there's others that do it
[09:33] <cimi> dednick, done
[09:33] <Saviq> even if they're doing it in a hacky way
[09:34] <dednick> answer is to make a new test case :)
[09:44] <tsdgeos> dednick: or that
[09:45] <dednick> tsdgeos: that's the way everything does it. can't launch unity8 before setting the env
[09:47] <tsdgeos> dednick: you lost me there :D but that's fine if you know what you're doing :D
[10:15] <dednick> Saviq: damnit. can't seem to use fake greeter. if we do, we don't get real apps...
[10:18] <dednick> Saviq: i could thread it to unlock while waiting for the proxy :/
[10:36] <Saviq> dednick, you mean that the import path is the same for fake greeter and fake apps?
[10:37] <Saviq> we need to be able to pick'n'choose...
[10:38] <dednick> Saviq: you need to set _qml_mock_enabled apparently
[10:39] <dednick> Saviq: which i think gets all the mocks rather than just lightdm
[10:39] <Saviq> dednick, yeah
[10:40] <dednick> Saviq, tsdgeos: http://pastebin.ubuntu.com/11023987/ :S
[10:41] <dednick> Saviq: thread waits until the greeter is swiped by app open, and unlocks it. :)
[10:41] <Saviq> dednick, that kinda works...
[10:41] <dednick> pretty dodgey
[10:41] <dednick> but will work until we can get selective mock shizzle.
[10:41] <Saviq> dednick, the other way would be to install a copy of the mock lightdm into a separate path (like we do with Unity.Application)...
[10:42] <tsdgeos> dednick: i think it's ok
[10:43] <dednick> I'll put in a FIXME for when we have mock selection.
[10:51] <dednick> tsdgeos: https://code.launchpad.net/~nick-dedekind/unity8/fix-autopilot-failures-1446846/+merge/258411
[10:51] <dednick> i've just updated the original MP.
[10:51] <tsdgeos> k
[11:40] <dednick> tsdgeos: should I get on with the video play back in previews? or were you planning on doing it?
[11:45]  * dednick goes for lunch
[12:38] <tsdgeos> dednick: you can take it
[13:22] <tsdgeos> pstolowski: https://code.launchpad.net/~aacid/unity8/edit_reviews/+merge/258623
[13:23] <pstolowski> tsdgeos, awesome! i'll give it a try with my code
[13:23] <dandrader> mzanetti, is any sort of qml cache present on devel-proposed?
[13:23] <tsdgeos> dandrader: yes
[13:23] <dandrader> mzanetti, I'm getting a very weird behavior that is driving me mad
[13:24] <dandrader> mzanetti, it seems that when I change from DesktopStage to TabletStage or vice-versa
[13:24] <dandrader> mzanetti, the previous stage somehow lives on
[13:24] <tsdgeos> ah that kind of cache, don't know, we have the file cache to speed up startup
[13:24] <mzanetti> dandrader, I think that's still the Loader bug
[13:24] <tsdgeos> but shouldn't affect that
[13:24] <dandrader> mzanetti, although I can't see it. some of its bindings still seem to act
[13:24] <mzanetti> yeah...
[13:25] <mzanetti> there is a bug in the loader, in combination with gsettings-qml
[13:25] <mzanetti> I digged into that for a day... found a workaround, but still haven't understood what's happening
[13:26] <dandrader> ok, so I'm not crazy afterall
[13:26] <mzanetti> if gsettings changes and causes the loader to load something different in the same event loop pass, the loader won't free its memory
[13:26] <mzanetti> workaround is to decouple it with a timer of interval 1 or similar
[13:26] <dandrader> mzanetti, so the workaround is to have a timer to trigger the Loader.source change?
[13:26] <mzanetti> well, actually, lemme find a branch
[13:26] <dandrader> ditto
[13:27] <dandrader> mzanetti, so you don't have a merge proposal with that workaround?
[13:27] <mzanetti> dandrader, this one would fix it too: https://code.launchpad.net/~mzanetti/gsettings-qt/queued-processing/+merge/248224
[13:27] <mzanetti> IMO this one would be nicer as a timer in unity
[13:27] <mzanetti> only problem is: I haven't understood why this is happening
[13:30] <dandrader> mzanetti, this explains why I don't get this issue when playing with "make tryShell"
[13:30] <dandrader> or when running the qml tests
[13:30] <mzanetti> yeah... this was driving me nuts too a while back
[13:32] <dandrader> mzanetti, this is blocking the manual testing of my "app lifecycle logic in  unity8" work. I will have to add the TImer workaround to its branch...
[13:33] <mzanetti> mhm...
[13:33] <mzanetti> I still wonder if we shouldn't land that gsettings patch...
[13:33] <mzanetti> larsu, hey, we're still suffering from this ^^
[13:33] <mzanetti> wdyt, should/can we land this? https://code.launchpad.net/~mzanetti/gsettings-qt/queued-processing/+merge/248224
[13:35] <mzanetti> if so, I'd fix the test that's failing because of the change
[13:41] <pstolowski> tsdgeos, is the editIcon already available on the phone?
[13:42] <tsdgeos> pstolowski: it's part of the theme, so yeah
[13:42] <tsdgeos> should be
[13:42] <pstolowski> ok
[14:20] <dandrader> MacSlow, wow, so we might finally getting a stable shellRotation AP test!!! what was the fix?
[14:22] <MacSlow> dandrader, the "granularity" for the faked sensor-events for "right -up" orientation seems to have been too rough
[14:22] <MacSlow> dandrader, currently at 50 successful runs in a row for "right-up"
[14:23]  * MacSlow really hopes this is the final issue to solve for that branch!!!
[14:26] <MacSlow> dandrader, and that in turn caused qtubuntu-senros to sometimes not recognize the orientation change, because there was not enough change in between
[14:29] <dandrader> mzanetti, the workaround bazaar.launchpad.net/~dandrader/unity8/app-state-handling/revision/1771
[14:30] <mzanetti> yeah... looks similar to what I had
[14:30] <mzanetti> dandrader, IMO we should rather land the gsettings-qml patch than this.... but good you have a way to be unblocked
[14:31] <dandrader> mzanetti, I think too, but having the unity8 workaround unblocks me and removed a dependency on a different project
[14:31] <mzanetti> ack
[15:15] <mzanetti> pstolowski, tsdgeos: seems we have conflict between silo 7 and 39
[15:15] <tsdgeos> fight to death, i'm using popcorn!
[15:16] <tsdgeos> mzanetti: you mean code confligt?
[15:16] <mzanetti> I don't think any of the both has higher priority than the other
[15:16] <mzanetti> let's QA pick one and rebuild the other
[15:17] <tsdgeos> mzanetti: or "conflict because we can't land the same thing twice"?
[15:17] <mzanetti> yeah... if we'd land both as is, the merge between the two wouldn't be tested
[15:17] <tsdgeos> which kind of makes sense
[15:17] <pstolowski> mzanetti, tsdgeos silo 7 is older ;)
[15:17] <mzanetti> ack
[15:17] <mzanetti> wfm
[15:17] <tsdgeos> yeah
[15:27] <mhall119> mzanetti: Saviq: what do I need to do to compile and run Unity8 on utopic?
[15:28] <mzanetti> good question... probably not possible
[15:28] <mzanetti> mhall119, what's the scope? just want to try trunk?
[15:29] <mhall119> mzanetti: yes
[15:29] <Saviq> mhall119, you need to upgrade to vivid ;)
[15:29] <mhall119> Saviq: anything short of that?
[15:29] <mhall119> the unity-team PPA doesn't seem to have anything in it anymore
[15:29] <mzanetti> yeah... you don't want to build all the deps that updated
[15:29] <Saviq> mhall119, backport all the packages we rely on to utopic
[15:30] <mzanetti> mhall119, a vmware vivid install would do too
[15:31] <mhall119> so then, I guess I should update the docs to say devs must be on vivid
[15:32] <tsdgeos> yeah
[15:32] <tsdgeos> just vivid-ize yourself and the docs
[15:32] <mzanetti> mhall119, I would go as far as saying that devs must be on the latest devel
[15:32] <mzanetti> once wily starts rolling it probably won't compile for long on plain vivid any more
[15:33] <mhall119> mzanetti: that's going to make casual contribution nearly impossible
[15:34] <mzanetti> mhall119, so the thing is, there are many libraries outside of unity which just get updates because unity requires them...
[15:35] <mzanetti> you can either update/backport those libraries or use the latest archive
[15:35] <mhall119> mzanetti: I know that backporting those into a PPA is extra work for you guys, but it will make it easier for others to get involved and contribute
[15:36] <mzanetti> I'll think about how much it would be... Can't promise anything though.
[15:36] <mhall119> thanks
[15:36] <mhall119> it's a tradeoff, I know, and if it's not worth it then that's fair
[15:38] <dupingping> Look http://vimeo.com/126505316
[15:40] <mzanetti> mhall119, it would require backporting mir and it's dependencies too... at which point you'd have like half of the archive in that ppa...
[15:40] <mzanetti> its
[15:40] <mzanetti> grr
[15:41] <mhall119> mzanetti: ok, if we can't backport can we get some documentation about how to set it up and run it in a VM? Would the dev have to write the code in the VM or on their host machine? Can we provide regularly updated VM images?
[15:41] <mhall119> anything to lower than barrier to entry
[15:42] <mzanetti> mhall119, you just grab the latest image from the official downloads and do-release-upgrade --devel on it
[15:42] <mzanetti> as of that, just apt-get upgrade to stay up to date
[15:44] <mzanetti> easiest is probably if you develop in there. but nothing prevents you to open the source from a shared folder on the host system and edit away there
[15:45] <mhall119> mzanetti: we're still talking 30-60 minutes of work before somebody can even start poking around in the code :(
[15:45] <mzanetti> mhall119, well, you can always build the revision that is released on your system
[15:46] <mhall119> mzanetti: but that wouldn't help someone wanting to contribute new features or fixes
[15:46] <mzanetti> but how would someone contribute new things if he doesn't want to run the new things?
[15:46] <mhall119> I want to encourage community contributes to get involved in Unity8 development
[15:47] <mhall119> mzanetti: they want to run the new Unity 8, probably in a window under Unity 7, they don't care about the rest of the OS
[15:47] <mzanetti> this is quite a core piece of the software stack we're talking about... it's not an app, it's the thing where apps run inside of
[15:48] <mhall119> mzanetti: again, I'm not saying you have to backport, I'm just looking for ways to make it easier to get started contributing
[15:49] <mzanetti> I think we do publish nightly images, don't we?
[15:49] <mhall119> any additional steps, no matter how logical and necessary they are, are still going to deter some folks
[15:49] <mhall119> mzanetti: of the base distro yes, not something that already has the developer tools and all
[15:49] <dandrader> greyback, https://code.launchpad.net/~dandrader/qtmir/detach-state-from-focus/+merge/258648
[15:50] <mzanetti> mhall119, from the core distro, an apt-get build-dep unity8 should work
[15:54] <greyback> dandrader: 894 lines, wow :)
[15:54] <dandrader> greyback, mostly because of the test I think
[15:55] <greyback> dandrader: yeah it's not as bad as I expected
[15:57] <dandrader> mzanetti, the number of approved branches is getting unwieldy
[15:58] <mzanetti> I know...
[15:58] <mzanetti> dandrader, we have 2 silos waiting for QA testing
[15:58] <dandrader> mzanetti, any news no wily repos?
[15:59] <dandrader> s/no/on
[15:59] <mzanetti> dandrader, no... but I expect to release next week to wily


[08:18] <abeato> sil2100, hey https://github.com/CanonicalLtd/ubuntu-image/pull/155 still needs another round :)
[10:27] <jbicha> coreycb: this change got accidentally dropped when you merged imagemagick: https://launchpadlibrarian.net/363532898/imagemagick_8%3A<IP_ADDRESS>+dfsg-16ubuntu5_8%3A<IP_ADDRESS>+dfsg-16ubuntu6.diff.gz
[11:39] <coreycb> jbicha: i'll take a look shortly. sorry about that.
[11:42] <jbicha> coreycb: no problem, I tried to push that change into Debian but I wasn't able to convince the maintainer why we wanted it
[19:13] <slangasek> kees, stgraber: no TB meeting today?
[19:19] <kees> slangasek: I'm conferencing in vancouver
[19:20] <slangasek> ok
[19:20] <slangasek> seb128: are you as sick of this ding autopkgtest failure as I am?
[19:21] <seb128> slangasek, yes! looks like you got a sucess in your most recent try though :)
[19:22] <slangasek> seb128: yeah except that's the baseline test, which fails to confirm that this is an ignorable regression in the release pocket :/
[19:22] <seb128> :/
[19:25] <jbicha> slangasek: how about https://autopkgtest.ubuntu.com/packages/u/udisks2/cosmic/s390x ? 😢
[19:25] <slangasek> jbicha: good news, that one *did* fail a baseline retest
[19:26] <infinity> slangasek: I think we might need to talk about an actual policy about flapping tests: that is, they should be either fixed, disabled, or hinted.  Retrying endlessly to sometimes get a thing we think might be a correct result isn't sane QA or CI.
[19:27] <slangasek> infinity: perhaps you would like to weigh in on my proposal that britney should automatically reset the gate whenever a retest against the release pocket fails
[19:27] <infinity> (And, worse, ignoring a flapping test, while we hope it means we're ignoring a bad testsuite, often means we're ignoring bad code that the test is rightly finding by accident, due to external fuzz)
[19:28] <seb128> jbicha, we should probably skip that one again :/
[19:28] <infinity> That is, retrying until it passes is a false sense of security.
[19:28] <seb128> the test that was always failed got fixed but the other ones are still flacky
[19:28] <slangasek> infinity: there is lots of bad code that isn't tested and the bad code that triggers flaky tests is not per se more important to pay attention to than other bad code
[19:29] <infinity> slangasek: I don't like the "automated" part of that proposal, cause it then implies that no human will give any thought to the how or the why of the regression.
[19:29] <slangasek> infinity: it only means that humans thinking about the regressions are decoupled from the actual transitioning
[19:29] <infinity> slangasek: Your thing in theory, mine in practice, I suspect.
[19:30] <infinity> Without gates, people's carefactor is much lower.  Whether the gate is britney or having to justify themselves to a release member or whatever.
[19:31] <slangasek> infinity: the carefactor SHOULD BE MUCH LOWER because the regressions have already happened in the release pocket
[19:31] <slangasek> instead, right now it's a waste of release team time to manually hint
[19:31] <slangasek> automate that; and deal with questions of adequately resourcing efforts to fix autopkgtests elsewhere
[19:32] <infinity> slangasek: One could make the exact inverse argument that carefactor should be higher because we somehow screwed up and let a bug slip out of proposed. :P
[19:32] <infinity> All of proposed can be as buggy as can be, but when thing start regressing in the release pocket, quality is going backward.
[19:35] <infinity> slangasek: And if it's just about not caring about the devel series until closer to release, s/release/updates/ and make the same arguments.  A regression noticed in updates should be a short stop the line event to investigate the severity and determine a course of action.  It doesn't need to be actioned immediately if it's determined to be not a big deal (hint it and put it on someone's TODO for when-never), but it's worth the 5 minutes of ...
[19:35] <infinity> ... talking about it.
[19:35] <slangasek> infinity: except when the test regressed because it was a bad test to begin with (flaky); or when the infrastructure changed in a way that invalidates the test but has not regressed the code; or we are treating as "regressed" the case of a failure in a test that was previously not run (due to testbed restrictions and then we moved the testbed), and now runs and fails; or the test is dumb and
[19:36] <slangasek> embeds a pre-generated SSL certificate with an expiration date
[19:36] <infinity> slangasek: I argue that the round-trip with the release (or in the updates case, SRU) team triggers that 5 minutes line stoppage and conversation.
[19:36] <infinity> slangasek: Yes, there are cases where the investigation immediately goes to "derp, this isn't something we care about", but a computer can't make that call.
[19:37] <slangasek> infinity: you do understand the geometrically-scaling impact of each of these 5-minute conversations on library transitions, right?
[19:37] <infinity> slangasek: I much preferred the other proposal to allow a reset-baseline style hint, so we can have that discussion ONCE, but then not have to keep bumping hints for eternity.
[19:41] <fo0bar> infinity: BTW, you just caused all of IS (and perhaps other groups) to check this channel :)
[19:41] <fo0bar> do not invoke the holy name of STL in vain
[19:42] <infinity> fo0bar: You're not the only people in the world who use the term, perhaps you could adjust your filters to only scan #is and #is-outage (which is where I yell it when I want you).
[19:42] <infinity> fo0bar: Also, insert Nelson "ha ha" clip here?
[19:44] <fo0bar> infinity: there are a few other channels, but yeah, just giving you grief
[19:48] <infinity> fo0bar: Yeah, #canonical-sysadmin also came to mind after I hit [enter].
[19:49] <infinity> fo0bar: Anyhow, grief registered and returned. ;)
[20:55] <xnox> slangasek, i'd like to see that "this all-release-pocket fail" + "this all-proposed-pocket fail" cause we have things migrating that do pass in all-proposed due to incomplete deps/ordering.
[20:56] <xnox> for the case where "this" is only published in release pocket for example.
[20:56] <xnox> slangasek, i do not want this automated, no. that feels wrong.
[20:56] <xnox> slangasek, i feel it should be "force-always-failed package/version" to set the threshold of where we count as always failed.
[20:57] <stgraber> slangasek: same as kees
[20:57] <xnox> (well usual syntax to specify arch/min-ver-barrier
[20:57] <xnox> )