[00:06] <mup> Bug #1567598 changed: storage-get causes state server to 'error: bad request' <storage> <juju-core:Invalid> <https://launchpad.net/bugs/1567598>
[00:08] <mwhudson> perrito666: ping?
[00:09] <thumper> damn you schema.ForceInt
[00:09] <thumper> schema.Int -> int64
[00:09] <thumper> scheam.ForceInt -> int
[00:09] <thumper> for no good reason
[00:09] <thumper> bah
[00:10] <alexisb> mwhudson, it is very much past his eod, if you can open a bug with the info you have that owuld be most helpful
[00:11] <mwhudson> alexisb: ok
[00:11] <mwhudson> alexisb: was actually typing up a bug report now, as it happens :-)
[00:11] <alexisb> perfect :)
[00:14] <mwhudson> alexisb: https://bugs.launchpad.net/juju-core/+bug/1567708
[00:15] <mup> Bug #1567708: unit tests fail with mongodb 3.2 <juju-core:New> <https://launchpad.net/bugs/1567708>
[00:15] <alexisb> mwhudson, thank you!
[00:15] <mwhudson> np
[00:15] <mwhudson> some of the errors are clearly quite silly
[00:16] <mwhudson> (like the error message mongo gives when reporting an auth failure has changed)
[00:16] <mwhudson> i don't know if any are deep
[00:21] <mup> Bug #1567708 opened: unit tests fail with mongodb 3.2 <juju-core:New> <https://launchpad.net/bugs/1567708>
[00:31] <natefinch> evening all
[00:33] <mup> Bug #1567708 changed: unit tests fail with mongodb 3.2 <juju-core:New> <https://launchpad.net/bugs/1567708>
[00:36] <redir> axw: yt?
[00:36] <mup> Bug #1567708 opened: unit tests fail with mongodb 3.2 <juju-core:New> <https://launchpad.net/bugs/1567708>
[00:51] <mup> Bug #1567712 opened: [juju create-model] Specifying a cloud when referring to a credential is redundant <docteam> <juju-core:New> <https://launchpad.net/bugs/1567712>
[00:51] <axw> redir_afk: "yt"?
[00:53] <davecheney> cherylj: http://pad.lv/1566303
[00:53] <davecheney> did this pass CI testing ?
[00:54] <davecheney> i have access to a windows machine now and can investigate if it's still failing
[00:55] <redir> I am
[00:55] <redir> axw: yt == you there
[00:55] <axw> redir: oh, well, you have your answer ;)
[00:55] <redir> axw: do you have a minute for a hangout?
[00:55] <axw> redir: sure, see you in the tanzanite hangout
[00:55] <redir> k
[00:57] <mup> Bug #1567712 changed: [juju create-model] Specifying a cloud when referring to a credential is redundant <docteam> <juju-core:New> <https://launchpad.net/bugs/1567712>
[01:03]  * thumper heads out to walk the dog
[01:06] <mup> Bug #1567712 opened: [juju create-model] Specifying a cloud when referring to a credential is redundant <docteam> <juju-core:New> <https://launchpad.net/bugs/1567712>
[01:15] <cherylj> davecheney: no, the windows test failed again:  http://reports.vapour.ws/releases/3863
[01:20] <davecheney> cherylj: thanks, i'll try to get on the windows test machine now
[01:21] <davecheney> cherylj: i don't understand that page
[01:21] <davecheney> where is the windows failure ?
[01:21] <cherylj> run-unit-tests-win2012-amd64
[01:21] <davecheney> ok i see it
[01:27] <mup> Bug #1567458 changed: destroy-controller message and failure is not user friendly <juju-core:New> <https://launchpad.net/bugs/1567458>
[01:36] <mup> Bug #1567458 opened: destroy-controller message and failure is not user friendly <juju-core:New> <https://launchpad.net/bugs/1567458>
[01:37] <redir> cherylj: so you started landing those updates?
[01:37] <redir> help text updates.
[01:37] <cherylj> redir: I made an Executive Decision
[01:37] <cherylj> and pulled the trigger
[01:37] <cherylj> :)
[01:37] <redir> OK
[01:38] <davecheney> menn0: https://bugs.launchpad.net/juju-core/+bug/1474607
[01:38] <mup> Bug #1474607: worker/uniter/relation: HookQueueSuite.TestAliveHookQueue failure <go1.5> <go1.6> <i386> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1474607>
[01:38] <redir> so I should fix up that other one and then resubmit or just merge?
[01:38] <davecheney> this bug is fixed on master bug fires on 1.25
[01:38] <redir> cherylj: ^^
[01:38] <davecheney> from memory it was a _lot_ of work to fix on master
[01:38] <cherylj> redir: as long as you test that the help text looks right, then i'd say just merge
[01:39] <redir> cherylj: OK. And have you settled on some formatting? indents all with line breaks etc?
[01:40] <cherylj> redir: basically, I copied what was in the bug for the most part, taking care to make sure lines were < 80 characters
[01:40] <menn0> davecheney: that bug doesn't ring any bells for me sorry
[01:40] <redir> OK. I'll do that, too, for the most part:)
[01:42] <redir> cherylj: ^
[01:42] <cherylj> thanks, redir :)
[01:44] <davecheney> menn0: i think this was fixed by william's manifold thinggy
[01:45] <menn0> davecheney: it won't be the manifold (dependency engine) stuff directly. that's got nothing to do with the uniter's internals.
[01:45] <mup> Bug #1567458 changed: destroy-controller message and failure is not user friendly <juju-core:New> <https://launchpad.net/bugs/1567458>
[01:45] <menn0> davecheney: there have been many other improvements in the uniter recently though
[01:45] <mup> Bug #1567719 opened: help text for juju list-shares needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567719>
[01:45] <mup> Bug #1567721 opened: help text for juju set-default-credential needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567721>
[01:46] <davecheney> menn0: that's what i'm worried about
[01:46] <davecheney> we cannot backport them all
[01:48] <mup> Bug #1567719 changed: help text for juju list-shares needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567719>
[01:48] <mup> Bug #1567721 changed: help text for juju set-default-credential needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567721>
[01:54] <mup> Bug #1567719 opened: help text for juju list-shares needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567719>
[01:54] <mup> Bug #1567721 opened: help text for juju set-default-credential needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567721>
[02:07] <mup> Bug #1567722 opened: help text for juju list-credentials needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567722>
[02:07] <mup> Bug #1567724 opened: help text for juju add-cloud needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567724>
[02:07] <mup> Bug #1567726 opened: help text for juju disable-user needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567726>
[02:10] <mup> Bug #1567722 changed: help text for juju list-credentials needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567722>
[02:10] <mup> Bug #1567724 changed: help text for juju add-cloud needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567724>
[02:10] <mup> Bug #1567726 changed: help text for juju disable-user needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567726>
[02:12] <menn0> cherylj: I think I've figured out that local charm hash mismatch bug and I don't think it'll be hard to fix
[02:13] <cherylj> menn0: excellent
[02:13] <cherylj> menn0: there's plenty more for you once you're done with it ;)
[02:13] <menn0> cherylj: oh I know :)
[02:14] <cherylj> menn0: I also still have that mgopurge problem from mario that I haven't done and could use help with :)
[02:15] <menn0> cherylj: ok, I can pick that up next
[02:16] <mup> Bug # opened: 1567722, 1567724, 1567726, 1567728, 1567730, 1567732, 1567734
[02:25] <axw> menn0: I'm intending to add the names of top-level machines and services to modelDoc, so we can safely advance from Alive to Dead if a model is empty
[02:26] <axw> menn0: just FYI, in case that would cause problems for model migration
[02:26] <axw> menn0: also probably will change the hosted-model refcount to references to UUIDs, to avoid ABA problem at destroy-controller time
[02:27] <menn0> axw: that might have model migration implications. thumper wrote the import and export code.
[02:27] <menn0> thumper: thoughts?
[02:27]  * thumper looks up
[02:28] <mup> Bug # changed: 1567728, 1567730, 1567732, 1567734
[02:28] <thumper> axw: what names?
[02:28] <menn0> thumper, axw: it should be easy enough to account for, and tests should start failing when you add fields (but maybe only in the model-migration branch
[02:28] <thumper> if you add fields, tests will fail
[02:28] <axw> menn0 thumper: i.e. when you add-machinem we'll $addToSet a "machines" field on the model doc
[02:29] <axw> and $pull when we remove the machine
[02:29] <thumper> why?
[02:29] <axw> thumper: https://bugs.launchpad.net/juju-core/+bug/1567228
[02:29] <mup> Bug #1567228: "juju destroy-controller" can leak hosted models <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1567228>
[02:30] <axw> that's part of it
[02:30] <axw> thumper: https://bugs.launchpad.net/juju-core/+bug/1563615 that's the other part
[02:30] <mup> Bug #1563615: destroy-controller blocks when you've not removed an empty default model <juju-release-support> <juju-core:In Progress by axwalk> <https://launchpad.net/bugs/1563615>
[02:30] <axw> thumper: basically we should short-circuit if the controller only has empty models, but we can't do that safely at the moment
[02:31] <axw> because the machines and services don't refcount or anything on the model
[02:31] <thumper> ok
[02:32] <thumper> if you do this, you'll need to make sure the value is added when the model description is imported
[02:32] <thumper> the export code probably won't need to change as the precondition is that the model is alive and all machines are alive
[02:32] <thumper> and no pending cleanups
[02:32] <thumper> so populating the field when importing should be "iterate through the machines"
[02:33]  * axw nods
[02:34] <axw> thumper: where's the import code?
[02:34] <thumper> axw: state/migration_import.go
[02:34] <axw> ta
[02:34] <menn0> thumper or axw: I need a quick hangout to bounce some ideas for a bug fix off someone. either of you keen?
[02:34] <thumper> menn0: sure
[02:35] <axw> menn0 thumper: call me in if it's helpful, otherwise I want to get this sorted
[02:35] <thumper> kk
[02:35] <thumper> menn0: 1:1 ?
[02:35] <menn0> thumper: yep
[02:37] <mup> Bug # opened: 1567728, 1567730, 1567732, 1567734
[02:48] <davecheney> base_windows.go makes me sad
[02:48] <davecheney> 1. because the registiry api is nuts
[02:49] <davecheney> 2. because the way that code enables the api to continue to be nuts, is weird, codependant and unhealtht
[03:07] <mup> Bug #1566339 changed: `juju run` needs a --all-machine, --all-service, --all-unit <juju> <machine> <run> <juju-core:Invalid> <https://launchpad.net/bugs/1566339>
[03:12] <davecheney> menn0: cherylj
[03:12] <davecheney> http://reviews.vapour.ws/r/4486/
[03:17] <mwhudson> uh
[03:17] <mwhudson> oh
[03:17] <mwhudson> nm
[03:17] <mwhudson> i should just upgrade to xenial
[03:23] <natefinch> mwhudson: if you like pain and suffering, that's a great idea.
[03:23] <mwhudson> heh it shouldn't be so bad at this point
[03:24] <natefinch> I've just heard of a lot of problems with juju-specific things like lxd and having xenial listed as an LTS (though it may not be yet)
[03:25] <mwhudson> oh yeah, lxd keeps moving things around
[03:26] <natefinch> I have OS updates that I'm not installing because there's lxd updates, and currently my LXD actually works.
[03:26] <mwhudson> huh um juju doesn't build with gccgo on xenial either
[03:26] <natefinch> and I don't have time to futz with network BS
[03:27] <mwhudson> oh maybe only with the tip go tool
[03:37] <mup> Bug #1567747 opened: "juju metadata generate-image" does not validate architectures <juju-core:Triaged> <https://launchpad.net/bugs/1567747>
[03:38] <menn0> davecheney: looking
[03:39] <menn0> davecheney: looks good
[03:42] <natefinch> davecheney: do you happen to know why this function has an error return? https://golang.org/src/net/http/cookiejar/jar.go?s=2387:2421#L67  it's vexing my current code. I'd like to just ignore it to make my code cleaner, but it worries me that it might one day start returning an error.
[03:49] <mup> Bug #1567747 changed: "juju metadata generate-image" does not validate architectures <juju-core:Triaged> <https://launchpad.net/bugs/1567747>
[03:55] <mup> Bug #1567747 opened: "juju metadata generate-image" does not validate architectures <juju-core:Triaged> <https://launchpad.net/bugs/1567747>
[04:00] <redir> night
[05:28] <mup> Bug #1567763 opened: bootstrapping private openstack, with --metadata-source fails when instance-type constraint is specified <juju-core:Triaged> <https://launchpad.net/bugs/1567763>
[05:35] <davecheney> natefinch ping ?
[05:35] <davecheney> hmm, too late
[08:42] <frobware> dimitern, voidspace, dooferlad: going to skip standup today.
[08:42] <dooferlad> frobware: ok
[08:49] <frobware> is there anyway I can force an upgrade-tools? It works for a while, but subsequent upgrades result in "ERROR some agents have not upgraded to the current model version 2.0-beta4.4: machine-0"
[08:50] <dimitern> frobware, ok
[08:50] <dimitern> frobware, btw I'm about to finally propose a fix for bug 1564395
[08:50] <mup> Bug #1564395: newly created LXD container has zero network devices <bootstrap> <conjure> <network> <juju-core:In Progress by dimitern> <https://launchpad.net/bugs/1564395>
[08:51] <babbageclunk> voidspace, frobware: I've got HR induction from 10-11 so I won't be in the meeting this morning (at least the first part - I'll jump in if it's still going when I get out).
[08:52] <frobware> babbageclunk, ack
[08:52] <babbageclunk> voidspace: what I did is in the document from yesterday, though.
[08:58]  * thumper is in the hangout
[08:58] <thumper> babbageclunk: good luck
[09:01]  * thumper wonders if he will be sitting alone....
[09:03] <voidspace> babbageclunk: ok
[09:03] <voidspace> thumper: omw
[09:07] <frobware> dimitern, happy to be a guinea pig for 1564395
[09:07] <frobware> dimitern, that's one less reboot, for there are many today. :/
[09:07] <frobware> dimitern, did your change with my /e/n/i *cough* hack... ?
[09:08] <frobware> dimitern, did your change work with my ...
[09:13] <dimitern> frobware, testing always appreciated :) yes - it uses the /e/n/i hack
[09:14] <frobware> dimitern, not sure my hack is working today; newer lxd since weds...
[09:15] <dimitern> frobware, I did a dist-upgrade this morning, so I have rc9 I think
[09:15] <dimitern> yep
[09:16] <frobware> dimitern, I'm trying to find the right place and time to delete the lxd supplied (and mandatory) eth0.cfg
[09:17] <frobware> dimitern, and ensure any ifup brings up our definition of eth0
[09:17] <frobware> dimitern, I was gettting provisioning errors earlier where it failed to write to /var/lib/lxd/container/<container>/rootfs/...
[09:27] <frobware> dimitern, the other thing is I'm only testing/trying this with trusty and xenial. I guess I should try precise and wily at some point.
[10:03] <voidspace> dimitern: babbageclunk: PR to merge maas2 onto master http://reviews.vapour.ws/r/4487/
[10:11] <dimitern> voidspace, I'll swap it for this - http://reviews.vapour.ws/r/4488/ :)
[10:14] <dimitern> voidspace, LGTM
[10:14] <voidspace> dimitern: thanks - looking
[10:15] <dimitern> voidspace, ta!
[10:15] <dimitern> fwereade, hey, are you about?
[10:16] <dimitern> frobware, ^^ pushed the fix
[10:17] <frobware> dimitern, you rebased?
[10:17] <dimitern> yep
[10:17] <frobware> dimitern, I was just looking at your changes since I pulled from earlier
[10:17] <frobware> dimitern, ok
[10:21] <dimitern> frobware, not removing /e/n/i.d/eth0.cfg doesn't seem to cause any harm - even rebooting the host/container is ok
[10:21] <frobware> dimitern, I'm trying to determine whether that's just luck based on the 'source .../*.cfg' order
[10:21] <frobware> dimitern, stgraber advised me to delete it
[10:23] <dimitern> frobware, well, that's even better - a proper fix, but just saying what i've seen so far
[10:24] <frobware> dimitern, me too. but have you rebooted a lot?
[10:24] <dimitern> frobware, i did reboot a few times, nothing fancier though
[10:24] <frobware> dimitern, I'm stuck with upgrade not working for me at the moment which make for slow progress
[10:26] <dimitern> frobware, that upgrade-juju issue - that's on trusty or xenial?
[10:30] <voidspace> dimitern: I don't really like adding unused code
[10:30] <voidspace> dimitern: why not add the gate in the PR that uses it?
[10:31] <frobware> dimitern, xenial
[10:33] <dimitern> voidspace, well, it's used by discoverspaces, but not yet by others
[10:34] <dimitern> voidspace, actually I did this because I thought I might need it in this PR
[10:34] <dimitern> voidspace, but fair enough, I'll pull gate out of this PR
[10:36] <voidspace> dimitern: it's up to you - other than that LGTM
[10:36] <frobware> dimitern, voidspace: seems like the right thing to do as it make reverting the PR saner - should it ever need to
[10:37] <dimitern> frobware, it's pretty easy with gh web ui
[10:38] <frobware> dimitern, what I mean is you would only be reverting stuff pertinent to the original fix
[10:38] <frobware> dimitern, anyway, back to ENI - the interfaces do not always come up for me. :(
[10:40] <dimitern> frobware, with my fix ?
[10:40] <frobware> dimitern, nope, mine
[10:41] <frobware> dimitern, the times I've bootstrapped and added a new machine without reboot seems to work fine with your fix \o/
[10:42] <dimitern> frobware, I found out something else (probably related to what jamespage was seeing - if say eth0 is unconfigured, but has children which are not - it breaks
[10:42] <dimitern> frobware, awesome!
[10:42] <frobware> dimitern, removal of eth0.cfg in cloud-init and taking down / bringing up the 00-juju.cfg does not work reliably. or so it seems.
[10:42] <frobware> dimitern, I raised a bug for that
[10:43] <frobware> dimitern, https://bugs.launchpad.net/juju-core/+bug/1566791
[10:43] <mup> Bug #1566791: VLANs on an unconfigured parent device error with "cannot set link-layer device addresses of machine "0": invalid address <network> <juju-core:Triaged> <https://launchpad.net/bugs/1566791>
[10:44] <dimitern> frobware, cheers, I'll be tackling this as well with the changes we discussed with thumper - adding 2 workers to do the NIC provisioning, devices creation, and updating provider network config after provisioning, as well as releasing container addresses as needed
[10:46] <dimitern> frobware, in fact, I'm already thinking how we can do the job of the bridge script but in a worker instead, properly with a lot more useful context and less workarounds
[10:46] <frobware> dimitern, but the script runs in cloud-init
[10:46] <dimitern> frobware, it doesn't have to, does it?
[10:47] <frobware> dimitern, well, as I'm finding out again, the combo of: ifdown, copy-in-new-file; ifup -a, is not guaranteed.
[10:47] <dimitern> frobware, we can do it with proper retrying, etc. - bridge by bridge, based on what NICs we observe at run-time
[10:48] <frobware> dimitern, I'm generally -1 on this atm, particularly if MAAS models bridges.
[10:48] <frobware> in the near future
[10:48] <dimitern> frobware, perhaps some if-[pre|post]-down script was lingering?
[10:48] <frobware> dimitern, bbiab - 20 mins.
[10:48] <dimitern> frobware, well, they will be at some point, but we need to think about other providers
[11:17] <voidspace> babbageclunk: dimitern: frobware: well that took a long time! I now have a test that can successfully call StartInstance against MAAS 2 code.
[11:18] <dimitern> voidspace, \\o// great!
[11:19]  * dimitern should really install a 2.0 maas locally now :)
[11:19]  * fwereade cheers at voidspace
[11:19] <voidspace> fwereade: :-)
[11:19] <voidspace> testing it all will take a while to construct, it's not exactly a small code path - but I can call it now without it blowing up
[11:20] <frobware> voidspace, very NICE!
[11:37] <bogdanteleaga> dimitern, https://bugs.launchpad.net/juju-core/+bug/1567676
[11:37] <mup> Bug #1567676: windows: networker tries to update invalid device and blocks machiner from working <juju-core:Triaged> <https://launchpad.net/bugs/1567676>
[11:37] <bogdanteleaga> help? :D
[11:38] <dimitern> bogdanteleaga, hey - the networker is gone for a while now; which version of juju?
[11:39] <bogdanteleaga> dimitern, latest, I wasn't sure what terminology to use
[11:39] <dimitern> bogdanteleaga, I see (might have helped to actually read the bug desc first :)
[11:39] <dimitern> bogdanteleaga, I know the issue
[11:40] <dimitern> bogdanteleaga, but that's already fixed in master IIRC - is that on a feature branch?
[11:41] <bogdanteleaga> dimitern, it's from yesterday's master
[11:41] <bogdanteleaga> dimitern, https://github.com/juju/juju/commit/b631875ff9ed67ec321f1d6fa90bc65d839b9e93
[11:43] <dimitern> bogdanteleaga, so the error in comment #1 is no longer happening
[11:43] <dimitern> bogdanteleaga, but the "<nil>" value of the address is troubling
[11:45] <bogdanteleaga> dimitern, I'll try the latest master
[11:47] <dimitern> bogdanteleaga, it might be better to use --config logging_config='<root>=TRACE' to bootstrap to get more context (and paste in the bug please)
[11:49]  * dimitern steps out for a couple of hours
[11:59]  * perrito666 steps out for an hour too
[12:36] <rogpeppe> an update to juju-core to fix the resources API used by charmrepo: http://reviews.vapour.ws/r/4490/
[12:37] <rogpeppe> should be trivial and I've very much like to get it landed to day if poss...
[12:37] <rogpeppe> so reviews welcome :)
[12:58] <axw> fwereade: I'm EODing, but if you have any time up your sleep, this PR has some gnarly state changes that I'd appreciate a review of if you have some time today: http://reviews.vapour.ws/r/4491/
[13:08] <mup> Bug #1567925 opened: help text for juju add-unit needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567925>
[13:09] <voidspace> babbageclunk: frobware: dimitern: maas2 has landed on master - all further maas2 work to be against master
[13:17] <mup> Bug #1567934 opened: uploadSuite.TestMockBuildTools relies on exact archive/zip output <juju-core:New> <https://launchpad.net/bugs/1567934>
[13:17] <mup> Bug #1567938 opened: juju bootstrap requires network ID as config option on command line although it's specified in clouds.yaml <juju-core:New> <https://launchpad.net/bugs/1567938>
[13:27] <alexisb> morning all
[13:29] <voidspace> alexisb: o/
[13:30] <babbageclunk> voidspace: nice!
[13:30] <katco> yaaaay life-giving internet
[13:30] <alexisb> katco, hey
[13:30] <voidspace> katco: morning
[13:30] <katco> alexisb: hey
[13:30] <alexisb> heh
[13:30] <katco> voidspace: morning from across the way
[13:30] <alexisb> is what I mean
[13:30] <voidspace> katco: o/
[13:32] <katco> alexisb: my neighborhood is 1 short street and they've been replacing the sidewalks 1 section at a time over the past month or so. we've had 3 outages now... o.0
[13:33] <alexisb> katco, sounds like it is time to move ;)
[13:33]  * katco wry smile
[13:34] <katco> perrito666: i have a patch to propose for the keystone issue... will you have a chance to tal?
[13:36] <babbageclunk> alexisb, katco: morning!
[13:36] <katco> babbageclunk: o/
[13:36] <katco> babbageclunk: good to hear from you again. how are you getting on with things?
[13:38] <babbageclunk> katco: settling in ok, I think. Heaps and heaps to learn, obviously!
[13:38] <katco> babbageclunk: that's what makes it fun :D
[13:39] <babbageclunk> katco: :)
[13:53] <mup> Bug #1567951 opened: help text for juju login needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567951>
[13:53] <mup> Bug #1567952 opened: container/lxd: TestDetectSubnetLocal fails with link/none <juju-core:New> <https://launchpad.net/bugs/1567952>
[13:54] <perrito666> katco: sure, shoot
[13:57] <katco> perrito666: http://reviews.vapour.ws/r/4492/
[13:58] <katco> perrito666: ta
[14:03] <natefinch> ericsnow: I think you're gonna like how the charmstore client code turned out... especially the amount of code needed to put into the csclientImpl wrapper type
[14:03] <alexisb> cmars, you around yet?
[14:04] <natefinch> ericsnow: I still have to update the tests for that code, but shouldn't be too bad.
[14:06] <perrito666> katco: shit it with a doubt
[14:07] <natefinch> perrito666: lol
[14:07] <perrito666> meh
[14:07] <perrito666> sorry typo
[14:07] <katco> perrito666: i think we only care about the major to resolve the client
[14:07] <cherylj> jam: you still around?
[14:07] <katco> perrito666: i.e. if the major is 2, we'd settle on 2.x whatever that may be
[14:09] <cherylj> frobware: ping?
[14:10] <perrito666> katco: I had miss interpreted your code, sorry
[14:11] <katco> perrito666: ah no worries... so is it still OK?
[14:11] <perrito666> yes
[14:13] <katco> perrito666: awesome... thanks for reviewing
[14:13] <perrito666> tx for that fix
[14:14] <katco> perrito666: weird situation... i don't really understand why an openstack deployment would report a version that isn't working yet
[14:15] <perrito666> cherylj: speaking of reviews, could I get a rev on http://reviews.vapour.ws/r/4481/ ?
[14:15] <cherylj> perrito666: yes, I will take a look this morning  (about to have a call right now :/)
[14:33] <katco> natefinch: ericsnow: https://plus.google.com/hangouts/_/canonical.com/retrospective?authuser=1
[14:39] <katco> ericsnow: ping?
[14:40] <frankban> cherylj: hey morning? any news on merging embedded-gui?
[14:40] <katco> natefinch: ericsnow: deferred half an hour; sorry, thought ericsnow was already on
[14:41] <mup> Bug #1567963 opened: help text for juju remove-unit needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1567963>
[14:41] <cherylj> frankban: let me look at the CI reports, one sec
[14:42] <frankban> cherylj: sure ty
[14:54] <perrito666> https://www.mongodb.com/blog/post/mongodb-2-6-end-of-life?utm_content=buffere388e&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer
[14:55] <perrito666> meh we could use a bot that says the title: "MongoDB 2.6 End of Life"
[14:55] <natefinch> perrito666: the url was pretty obvious ;)
[14:55] <perrito666> lol, I did not realize, I could have very well have stripped the get params
[14:56]  * dimitern whew... almost 1h stuck in traffic :/
[15:02] <dimitern> voidspace, frobware, babbageclunk, btw the sync call is not happening
[15:02] <dimitern> perhaps next week
[15:16] <alexisb> cherylj, fyi, I was able to deploy a few services yesterday off master
[15:21] <dooferlad> frobware: I have the switch in place and can confirm that 802.3ad works over juju-br0 once we put in pre-up/post-down steps to control the underlying bond.
[15:22] <alexisb> dooferlad, that is good news
[15:22] <dooferlad> alexisb: :-)
[15:59]  * alexisb changes locations
[16:09] <frankban> cherylj: can we stick a little trivial last change to the embedded-gui branch? is it too late?
[16:09] <babbageclunk> dimitern: sync call? I don't think I'm on it - can you please add me?
[16:09] <evilnickveitch> cherylj, we may have a problem with a lot of the updated help text
[16:09] <frankban> hatch: you dropped
[16:09] <cherylj> frankban: dont' put anything else into embedded gui
[16:10] <cherylj> wait for us to merge it and put it directly in master
[16:10] <hatch> :'(
[16:10] <hatch> :D
[16:10] <frankban> cherylj: sounds good
[16:10] <cherylj> evilnickveitch: what's going on with the help text?
[16:10] <frankban> cherylj: when is the deadline for putting changes into master?
[16:10] <evilnickveitch> cherylj, a lot of the user related commands reference 'share-model'
[16:10] <evilnickveitch> 'sahre-model' seems to have disappeared
[16:11] <evilnickveitch> i mean, as a command
[16:11] <cherylj> frankban: needs to be done today
[16:11] <cherylj> evilnickveitch: yeah, it was a late change to be juju grant
[16:12] <evilnickveitch> cherylj, :(
[16:13] <evilnickveitch> cherylj, well, be on the lookout for it in case we miss changing any - it appears in a lot of 'see also' text
[16:13] <cherylj> evilnickveitch: ok, thanks, I'll keep an eye out
[16:13] <evilnickveitch> cherylj, I will just go and rewrite all the user docs...
[16:14] <dimitern> babbageclunk, sure - invite sent
[16:15] <babbageclunk> dimitern: thanks!
[16:18] <frankban> cherylj: actually I am lucky enough that the code I need to change is the GUI server already in master, will be just a trivial improvement
[16:19] <cherylj> frankban: great!
[16:20] <redir> cherylj: evilnickveitch there appears to be one unshare-model too
[16:32] <cmars> i can review some things now. what should i look at first?
[16:33] <cmars> alexisb, cherylj ^^ ?
[16:34] <alexisb> perrito666, are you still waiting for a review?
[16:34] <alexisb> cmars, this one is important: http://reviews.vapour.ws/r/4491/
[16:36]  * cmars is reviewing
[16:37] <alexisb> cmars next inline would be this one: http://reviews.vapour.ws/r/4481/
[16:38] <mup> Bug #1568028 opened: Juju fails to deploy with 2.0-beta3-xenial-arm64 <juju-core:New> <https://launchpad.net/bugs/1568028>
[16:40] <alexisb> frobware, I am back online if you are still looking for me
[16:58] <alexisb> cmars, if you are done with the two reviews above, the next in priority are any from jam dealing with lxd and containers
[16:58] <alexisb> like: http://reviews.vapour.ws/r/4478/
[17:00] <cmars> alexisb, still on the first one
[17:01] <alexisb> cmars, understood, thanks
[17:02] <mup> Bug #1568028 changed: Juju fails to deploy with 2.0-beta3-xenial-arm64 <juju-core:New> <https://launchpad.net/bugs/1568028>
[17:24] <cmars> 4491 is going to take me all afternoon to review, some of it i don't fully understand yet. deals with parts of state i'm unfamiliar with
[17:28] <alexisb> cmars, what about 4881>
[17:28] <alexisb> ?
[17:29] <cmars> alexisb, you mean 4481? that looks more manageable. i'll review over lunch
[17:30] <alexisb> yes that is what I meant sorry
[17:30] <alexisb> and cool, thank you
[17:32] <frobware> alexisb, just to say... great few days with christian, have some sort of fix (need testing) for bug #1566801
[17:32] <mup> Bug #1566801: LXD containers /etc/network/interfaces as generated by Juju  gets overwritten by LXD container start <network> <juju-core:Triaged by frobware> <https://launchpad.net/bugs/1566801>
[17:36]  * frobware EOW
[17:51] <katco> ericsnow: you have ship its
[17:51] <ericsnow> katco: thanks
[17:52] <natefinch> katco, ericsnow: down to 4 comments btw
[17:52] <ericsnow> natefinch: nice
[17:52] <katco> natefinch: yeah just looked... that is a ton of code lol
[17:52] <natefinch> katco: yeah, there's a reason it took a while
[17:53] <katco> natefinch: ericsnow: thanks for pairing on that
[17:53] <natefinch> katco: still need some new tests for some of the new code eric and I wrote yesterday
[18:00] <mup> Bug #1568069 opened: Container networking cannot ssh <ci> <lxc> <network> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1568069>
[18:06] <mup> Bug #1568069 changed: Container networking cannot ssh <ci> <lxc> <network> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1568069>
[18:20] <alexisb> katco, I have a few minutes if you would like ot meet
[18:21] <mup> Bug #1568069 opened: Container networking cannot ssh <ci> <lxc> <network> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1568069>
[18:21] <mup> Bug #1568079 opened: github.com/juju/juju/apiserver/client unit tests fail if xenial is the LTS <xenial> <juju-core:Triaged> <https://launchpad.net/bugs/1568079>
[18:24] <katco> alexisb: sure
[18:26] <alexisb> katco, 1x1 HO
[18:33] <perrito666> alexisb: sadly I am
[18:37] <cmars> perrito666, reviewed 4481
[18:37] <perrito666> cmars: tx
[18:38] <perrito666> cmars: tx a lot
[18:45] <mup> Bug #1568090 opened: help text for juju sync-tools needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1568090>
[18:54] <natefinch> ericsnow, katco: and down to one comment, but it's probably the hardest one... fixing model migrations.  But for now I'm going to rebase, since github tells me I have conflicts. sigh.
[18:54] <ericsnow> natefinch: k
[18:54] <ericsnow> natefinch: let me know if I can help; as I mentioned, I did the same thing for channels
[18:55] <natefinch> definitely
[19:06] <mup> Bug #1568092 opened: ConnectSuite.TestLocalConnectError: centos  cannot connect to local lxd servier <centos> <ci> <lxd> <regression> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1568092>
[19:06] <katco> natefinch: sorry was otp. whoa, what does "fixing model migrations" mean? that doesn't sound fun =|
[19:09] <natefinch> katco: adding a few lines to state.migration_import.go / _export.go  basically like what eric did with those files here: http://reviews.vapour.ws/r/4441/diff/#
[19:10] <katco> natefinch: oh b/c you're storing new info in state you have to support it when migrating models
[19:10] <natefinch> yep
[19:10] <katco> natefinch: gotcha... makes sense. sounded scary o/0
[19:10] <natefinch> still a little scary ;)
[19:10] <katco> ha
[19:14] <natefinch> uh hmm
[19:14] <natefinch> there's nothing in there about charms
[19:14] <natefinch> ericsnow: ^
[19:15] <ericsnow> natefinch: if we're not migrating charms then I'm guessing that Tim & co. haven't gotten to it yet
[19:16] <ericsnow> natefinch: however, I'd be surprised by that
[19:16] <ericsnow> natefinch: perhaps it's folded into the service representation? (and they will re-download the blobs)
[19:17] <natefinch> ericsnow: I thought of that, but then they can't do that for local charms
[19:17] <ericsnow> natefinch: yuck
[19:17] <ericsnow> natefinch: so blobs have to be migrated too I suppose
[19:18] <mup> Bug #1568101 opened: help text for juju deploy needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1568101>
[19:18] <natefinch> ericsnow: I would assume so....
[19:19] <natefinch> ericsnow: hang on... I see some code related to charms in core/migration/migration.go .... reading
[19:19] <ericsnow> natefinch: ah, no MigrationSuite.TestCharmDocFields()
[19:29] <natefinch> ericsnow: can you give the review another pass, and we can maybe try to get in touch with the migration guys?  I assume they're all still in their upside down beds, since it's saturday morning down there
[19:29] <ericsnow> natefinch: will do
[19:31] <alexisb> katco, ericsnow: has this documentation made ericsnow's google doc obsolete?: https://github.com/juju/juju/wiki/Implementing-environment-providers
[19:33] <katco> alexisb: axw mentioned he was going to incorporate ericsnow 's doc because he didn't know about it when he created that wiki page. i don't know that he ever did
[19:34] <natefinch> alexisb or katco: do you know if anyone familiar with model migrations is awake?  I added a macaroon field to charms stored in mongo, but I don't really see any place in the migration code where we migrate charm metadata...
[19:35] <katco> natefinch: i don
[19:35] <katco> 't
[19:35] <katco> natefinch: menn0 is working on that primarily... thumper should still be able to answer questions as well
[19:35] <natefinch> ..... do our tests create virtual ethernets on the machine they're running on?
[19:36] <katco> natefinch: omg... PLEASE tell me they don't
[19:36] <natefinch> sure looks like it
[19:36] <natefinch> I have like 4 virtual ethernet devices on my machine right now
[19:36] <katco> what. the. hell.
[19:36] <natefinch> I noticed because I saw a popup that say "connected to veth<somguid>
[19:38] <alexisb> natefinch, fwereade sometimes is around late
[19:38] <alexisb> otherwise they are all on their weekend
[19:38] <alexisb> natefinch, the MM work is not complete so it may be that it is not in master yet
[19:39] <alexisb> though with menno's latest branch I was able to successfully migrate a basic mediawiki deploy successfully
[19:40] <natefinch> alexisb: ok
[19:43] <natefinch> katco: http://i.imgur.com/d1ZKuPz.png
[19:44] <ericsnow> katco: gah, I forgot to mention a patch I have up against charmrepo:  https://github.com/juju/charmrepo/pull/84
[19:45] <katco> ericsnow: k tal
[19:45] <ericsnow> katco: ta
[19:46] <natefinch> that feeling when you're pretty sure you're waiting for the 10 minute testing timeout :/
[19:46] <cherylj> I know that feeling
[19:47] <redir> natefinch: everytime I run all the tests.
[19:48] <natefinch> or not: ok  	github.com/juju/juju/state	414.273s
[19:49] <natefinch> almost 7 minutes just for state tests.  Huzzah.
[19:57] <alexisb> o the state tests...
[19:58] <perrito666> natefinch: the state tests are quite shroedinger cat-ish unthil they finish they have and have not failed in your mind
[19:59] <katco> ericsnow: lgtm... fairly straightforward changes :)
[20:00] <ericsnow> katco: yep :)
[20:00] <ericsnow> katco: thanks
[20:00] <katco> ericsnow: ty
[20:09] <mup> Bug #1563364 changed: UniterSuite.TestUniterSteadyStateUpgradeForce fails <ci> <intermittent-failure> <test-failure> <juju-core:Invalid> <juju-core embedded-gui:Fix Released> <https://launchpad.net/bugs/1563364>
[20:09] <mup> Bug #1568122 opened: help text for juju remove-machine needs improving <helpdocs> <juju-core:New> <https://launchpad.net/bugs/1568122>
[20:13] <cmars> alexisb, should i try to continue reviewing 4491 or look at something else
[20:21] <alexisb> cmars, if they are easier you can do the lxd reviews
[20:21] <alexisb> http://reviews.vapour.ws/r/4478/
[20:22] <cmars> alexisb, looking
[20:22]  * perrito666 sees his refactoring interrupted by eye drops :p
[20:25] <ericsnow> natefinch: LGTM with a few small comments
[20:26] <natefinch> ericsnow: ok
[20:26] <natefinch> ericsnow: thanks
[20:26] <ericsnow> natefinch: np
[20:26] <ericsnow> natefinch: thanks for doing it :)
[20:51] <ericsnow> natefinch: how close are you to pulling the trigger on that patch?
[20:59] <katco> ericsnow: you were waiting on him to rebase weren't you?
[21:00] <ericsnow> katco: was hoping he'd merge his patch before I land my last one
[21:02] <katco> ericsnow: might have to land yours first... your work needs to be in by EOD
[21:03] <katco> ericsnow: and then we can pair to help through the difficult merge
[21:03] <ericsnow> katco: won't be hard, just tedious :)
[21:03] <ericsnow> katco: we're changing a bunch of the same signatures
[21:05] <katco> ericsnow: he's probably gone to dinner, i'd say go ahead and begin merging
[21:05] <perrito666> aghh I broke the reboot test :(
[21:06] <ericsnow> katco: sounds good
[21:19] <natefinch> ericsnow: thanks, fotgot you were waiting on me
[21:19] <ericsnow> natefinch: np
[21:19] <natefinch> bbl
[21:39] <mup> Bug #1568150 opened: xenial lxc containers not starting <juju-core:New> <https://launchpad.net/bugs/1568150>
[22:00] <alexisb> perrito666, I am seeing reboot test failures too
[22:00] <alexisb> from master
[22:00] <perrito666> meh, It seems broken
[22:00] <perrito666> I believe its breaking mongod but it is not related from my changes
[22:00] <perrito666> this might prevent me from merging :(
[22:01] <alexisb> alrighty all I am out for a few hours will be back this evening
[22:01] <alexisb> perrito666, please open a bug with details
[22:01] <perrito666> ok
[22:03] <alexisb> thanks
[22:03] <alexisb> alexisb-afk
[22:09] <perrito666> alexisb: for when you come back, I cannot reproduce now but I feel we are leaking lxcs and mongos
[22:09] <mup> Bug #1568160 opened: destroying a unit with an error gives no user feedback <juju-core:New> <https://launchpad.net/bugs/1568160>
[22:09] <mup> Bug #1568161 opened: Pass whether service is primary or subordinate via relation <juju-core:New> <https://launchpad.net/bugs/1568161>
[22:30] <mup> Bug #1568175 opened: destroy-controller failed: EOF <ci> <destroy-controller> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1568175>
[22:30] <mup> Bug #1568176 opened: charm deployment requests invalid revision number <juju-core:New> <https://launchpad.net/bugs/1568176>
[22:34] <mup> Bug #1568175 changed: destroy-controller failed: EOF <ci> <destroy-controller> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1568175>
[22:34] <mup> Bug #1568176 changed: charm deployment requests invalid revision number <juju-core:New> <https://launchpad.net/bugs/1568176>
[22:40] <mup> Bug # opened: 1568175, 1568176, 1568177, 1568179
[23:01] <mup> Bug #1568181 opened: clientRepoSuite.TestBlockRemoveServiceDeployPrincipal cannot put archive blob <ci> <intermittent-failure> <regression> <unit-tests> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1568181>
[23:01] <mup> Bug #1568183 opened: GCE timeout pending new instance operation failed <ci> <gce-provider> <jujuqa> <reliability> <juju-core:Triaged> <https://launchpad.net/bugs/1568183>
[23:01] <ericsnow> katco: third patch merging now :)
[23:01] <mup> Bug #1568185 opened: statusHistoryPrunerSuite.TestWorker wrong number of logs <ci> <intermittent-failure> <unit-tests> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1568185>
[23:01] <katco> ericsnow: woot woot!
[23:31] <mup> Bug #1568186 opened: TestUniterUpgradeGitConflicts never reached desired status <ci> <i386> <intermittent-failure> <unit-tests> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1568186>
[23:31] <mup> Bug #1568189 opened: RemoveRelationSuite.SetUpTest failed because of mongo <ci> <intermittent-failure> <mongodb> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1568189>
[23:31] <mup> Bug #1568190 opened: MachinerSuite.TestMachinerSetStatusStopped cannot set status <ci> <intermittent-failure> <unit-tests> <juju-core:Incomplete> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1568190>


[00:05] <ScottK> shadeslayer: Sure.
[00:09] <ScottK> shadeslayer: No reason to send that one to proposed.
[00:10] <shadeslayer> oh .. ok
[00:10] <ScottK> Uploaded with quantal instead of quantal-proposed.
[00:10] <shadeslayer> I thought we were in pre release freeze, and all uploads go to -proposed
[00:10] <ScottK> No, still just ones that can break the archive with skew.
[00:11] <shadeslayer> ah
[00:11] <ScottK> The whole archive is frozen, so everything hits unapproved anyway.
[00:11] <ScottK> So the 4.9.2 update as a whole goes to -proposed.
[00:11] <shadeslayer> right, and then copy over to main archive to prevent skew
[00:15] <shadeslayer> kdegames is still building with fix
[00:17] <ScottK> Great.
[00:17] <ScottK> Nothing else appears to have failed so far.
[00:19] <shadeslayer> so it seems that kdegames has dropped the top level README and instead there's a README for every game
[00:19] <shadeslayer> and mostly useless tbh
[00:20] <ScottK> bugfix only FTW.
[00:20] <ScottK> Don't worry about shipping the per game README's then.
[00:20] <shadeslayer> yeah
[00:21] <ScottK> It's an artifact of them moving to git and splitting.
[00:21] <shadeslayer> *nod*
[00:23] <shadeslayer> ScottK: kdegames uploaded
[00:23] <ScottK> Great.
[00:23]  * shadeslayer sync's bzr branches
[00:29] <shadeslayer> ScottK: branches syncd
[00:29] <shadeslayer> sync'd even
[00:29] <shadeslayer> we don't maintain a branch for taglib do we?
[00:31] <shadeslayer> ( doesn't look like it
[00:32] <shadeslayer> )
[00:48] <ScottK> kdegames and taglib are in.
[00:48] <ScottK> Thanks shadeslayer .
[00:49] <shadeslayer> np
[01:08] <shadeslayer> ScottK: http://paste.kde.org/561392/ < something is wrong with 4.8.5 on armhf precise
[01:09] <shadeslayer> oddly it doesn't pick up kde-window-manager-gles 4:4.8.5-0ubuntu0.1
[01:09] <shadeslayer> http://paste.kde.org/561398/
[01:32] <JontheEchidna> :s http://i.imgur.com/xWdOr.png
[01:33] <JontheEchidna> apachelogger: any ideas on^?
[01:34] <JontheEchidna> everything started to slow down to to swap usage
[01:37] <JontheEchidna> ooh, symptom, when I run dragon and then close it, a window playing the file from the beginning again shows (with no UI elements other than the video) and then closes
[02:24] <ScottK> shadeslayer: You're installing a package from -updates with -updates disabled.  Won't work.
[07:22] <konqui> Will quantal release with 4.9.2 or 4.9.1?
[07:32] <tsdgeos> i just got kmix 4.9.2 in my quantal installation
[07:35] <konqui> tsdgeos: does kmix 4.9.2 even exist? About kmix says 4.2 here
[07:36] <tsdgeos> ...
[07:36] <tsdgeos> kmix from 4.9.2
[07:37] <konqui> Ah ok got that too kmix i386 4:4.9.2-0ubuntu1
[09:03] <debfx> shadeslayer: kde-baseapps shouldn't build-depend on kdelibs5-data, instead the include file need to be moved to the proper package
[09:04] <Riddell> I just noticed that :(
[09:04]  * debfx wonders if it's safe to assume that no one uses q-proposed
[09:05] <Riddell> I did fix it but I must have failed to push the fix and it ended up in the final build for the archive
[09:06] <Riddell> same for the change to kdegames
[09:06] <konqui> Will quantal release with 4.92? or 4.9.1?
[09:07] <Riddell> depends if I keep making mistakes or not
[09:07] <konqui> lol
[09:09] <konqui> So if it does release with 4.9.2, will klook be automatically added to Kubuntu or will users who want that have to install a seperate package.
[09:11] <konqui> My bad, seems like that is not yet implemented and still marked as "todo"
[09:12] <Riddell> I've forgotten what klook is
[09:12] <Riddell> what is it?
[09:12] <konqui> Dolphin previews, for files
[09:12] <konqui> A bit like the one in OS X
[09:18] <Riddell> I don't get it, I don't use OS X and dolphin already has previews
[09:19] <konqui> Riddell: http://www.koryavov.net/2012/03/klook-new-utility-for-kde-and-rosa.html
[09:20]  * konqui doesn't use OS X either
[09:24] <Riddell> seems a lot like gwenview
[10:02] <konqui> Riddell: Not really, all it does it give you a large popup to view content right from dolphin quickly on pressing space, so you can quickly play video, scroll through a pdf, image etc
[10:03] <konqui> Quite handy as you don't have to waste time opening okular etc when you just want to view the file
[10:30] <Riddell> oh he left before I could ask him to package it
[10:30] <Riddell> groovy precise packages work
[10:52] <Riddell> oh foo am I doing something wrong or is launchpad when copying? http://paste.kde.org/561542/
[11:04] <Riddell> hmm something on my computer that doesn't want to work
[11:14] <Riddell> uh oh launchpad is e-mailing me OOPSes I wonder if I should worry
[11:17] <davmor2> Riddell: You should Always worry ;)
[11:25] <smartboyhw> Hi guys
[11:26] <Riddell> hola chico
[11:26] <smartboyhw> Riddell, er Kubuntu is the only flavour with under 89% completion of blueprint:P
[11:26] <Riddell> oh interesting, notifications appear on the PPA web page for the errors
[11:26] <Riddell> smartboyhw: tidying up blueprints has been on my todo list for ages and yet to get to the top
[11:27] <smartboyhw> Riddell, ooh:P
[11:27]  * smartboyhw thinks every flavor has done it already:P
[11:32] <Riddell> smartboyhw: actually i think lots will be the dozens of spec items littlegirl put in to docs for her to keep track of things before she had to leave
[11:34] <smartboyhw> ooh
[11:34] <smartboyhw> Riddell, leave?
[11:34] <Riddell> she had some real life issue
[11:35] <smartboyhw> gee who is replacing him the Riddell ?:P
[11:36] <smartboyhw> *her:P
[11:38] <smartboyhw> Omit the *the* please
[11:39] <smartboyhw> Riddell, question edited:P Gee who is replacing her Riddell?:P
[13:04] <xnox> somebody help me with bug 1060893
[13:07] <yofel_> xnox: seems like an issue in the subvolume handling of the btrfs setup, nothing kubuntu specific
[13:07] <xnox> yofel: true. and on debian/ubuntu you can only have one btrfs pull and only @ as the boot/root volume.
[13:10] <ScottK> Any objections to making the changes that mgraesslin asked for?
[13:11] <BluesKaj> Hiyas all
[13:15] <Riddell> ScottK: I excpect not but let me read it over properly
[13:15] <ScottK> OK.  Thanks.
[13:15] <ScottK> I think they're all in the line of "this won't work".
[13:19] <ScottK> I have a package prepared assuming you agree and he writes back that I didn't screw it up.
[13:21] <Riddell> ScottK: did you look at what the virtual desktop issue would need?
[13:21] <ScottK> I don't think it needs anything.
[13:22] <ScottK> If you set things to one desktop the pager just becomes invisible.
[13:22] <Riddell> but that needs set somewhere presumably
[13:23] <Riddell> it makes sense to only have one virtual desktop if you use activities instead, but I've never worked out how or why I'd use activities
[13:23] <ScottK> Me neither.
[13:23] <ScottK> OTOH, I always forget about desktops too.
[13:23] <ScottK> Isn't this enough:
[13:23] <ScottK> -[Desktops]
[13:23] <ScottK> -Number=2
[13:24] <ScottK> This is the time to be bold I guess and be 14.04 I think we'll all be using activities, so we may as well take the plunge.
[13:24] <Riddell> yep, I'd say go for it
[13:39] <Riddell> xnox: that seems a bit random
[13:40] <ScottK> OK.  I'm going to wait for mgraesslin's reply.
[13:40] <xnox> Riddell: which bit? the bug? the deficiencies of btrfs in debian/ubuntu? me panicking? all of the above? (delete as appropriate)
[13:44] <Riddell> xnox: the bug is, it doesn't help that it's not written in a way I fully understand, where are there strange @ directories going etc
[13:45] <Riddell> mparillo: 4.9.2 working on 12.04 for me, fancy putting a news item on the website?
[13:45] <yofel> Riddell: in case you don't know. @ is the name of the root subvolume if you install on btrfs. The partitioner automatically creates a subvolume for / (@) and /home (@home)
[13:46] <Riddell> mm, maybe I should try btrfs one day
[13:46] <xnox> Riddell: only if you don't care about your data
[13:46] <yofel> do it on kernel >= 3.5, It's ~usable these days. Still many ENOSPC issues though :/
[14:01] <BluesKaj> is btrfs going to be used by linux , replacing ext eventually ?
[14:02] <Riddell> no idea, you'd need to ask some linux developers
[14:02] <xnox> BluesKaj: btrfs is one of the filesystems that linux kernel supports. currently ubuntu decided to continue using ext4 as default.
[14:03] <xnox> BluesKaj: btrfs is not aimed to be a direct continuation of ext file system family, but rather yet another competitor.
[14:07] <BluesKaj> well , if btrfs auto sets / and /home partitions , that would be a a good thing I suppose , but what other advantage does it offer over ext , xnox  ?
[14:08] <xnox> BluesKaj: http://en.wikipedia.org/wiki/Btrfs
[14:08] <xnox> COW, checksummings, snapshots, RAID levels, etc.
[14:29] <ScottK> Looks like i386/amd64/powerpc are done for 4.9.2.
[14:29] <Riddell> yes, just installed it fine
[14:30] <Riddell> ScottK: how do we get it moved to release?  I realise I don't actually know
[14:31] <ScottK> Riddell: sru-release in archive tools.
[14:32] <Riddell> that seems easy
[14:34] <Riddell> for asdf in `cat /home/jr/src/kubuntu-automation/kubuntu-automation/kdesc-packages-quantal.txt`; do echo ${asdf}; ./sru-release -r quantal ${asdf}; done
[14:34] <Riddell> that should keep it busy
[14:34] <ScottK> Yes.
[14:35] <ScottK> We need to wait for the builds to finish though.
[14:35] <ScottK> I don't know what horrors happen if you copy a package that's not built yet so that some binaries exist in -release and others will later appear in -proposed.
[14:37] <Riddell> oops
[14:37] <Riddell> we'll find out now
[14:37] <ScottK> Sigh.
[14:38] <ScottK> Hopefully they get -release build records and it's all good.
[14:39] <Riddell> ScottK: on the question of owncloud, Blizzz says 3.0 is unmaintained so I don't see us getting a patch for the issues in 12.04, so I'm still thinking delete it and put an update in -backports is the best thing we can do
[14:40] <ScottK> Maybe SRU it so that people who have it installed already don't get left out?
[14:41] <ScottK> We'd need special permission.
[14:41] <Riddell> yeah that would seem like needing beurocracy, a tech board exception presumably
[14:44] <ScottK> Removing it doesn't help users that already have it installed.
[14:45] <Riddell> backports the first step anyway, I'll do that
[14:49] <ScottK> As long as it's tested to at least run.
[14:54] <ScottK> Riddell: The early package copy should be non-world ending.  You'll just need to copy the ones that weren't finished again once they are, so keep a list.
[14:57] <Riddell> gotcha
[14:58] <ScottK> If for some reason the recopy doesn't work, then we can panic (in theory is should, but untested)
[15:02] <soee> are there any wallpaper changes in 4.9.2 ?
[15:03] <Riddell> http://www.kubuntu.org/news/kde-sc-4.9.2
[15:04] <Riddell> soee: nope
[15:05] <Riddell> mparillo: beat you :) http://www.kubuntu.org/news/kde-sc-4.9.2
[15:06] <mparillo> Riddell: Well, at least you did not have to edit my draft!
[15:06] <ScottK> Riddell: k-d-s changes in queue per mgraesslin (he verified on the list).  Please accept.
[15:06] <BluesKaj> the ppa doesn't connect
[15:07]  * Riddell waits for launchpad to make the diff
[15:07] <kubotu> ::workspace-bugs:: [1060986] kwin_opengl_test crashed with SIGSEGV in r600_bind_blend_state_internal() @ https://bugs.launchpad.net/bugs/1060986 (by Dimiter "Arruor" Nikov)
[15:07] <BluesKaj> Cannot access PPA (https://launchpad.net/api/1.0/~kubuntu-ppa/+archive/backports.)
[15:09] <Riddell> BluesKaj: what are you trying to do?
[15:10] <BluesKaj> Riddell, odd , it's comnnecting now
[15:10] <Riddell> just launchpad then
[15:11] <mparillo> shadeslayer: https://wiki.kubuntu.org/Kubuntu/Get Involved/WhoWeAre I am last, Riddell is first and the I pre-populated some table rows sorted by IRC handles. I will try to do some updates, but I am afraid for this to really work, people need to update their own data.
[15:13] <mparillo> Hmm, I guess spaces are not good things to have in URLs. The Wiki handles them, but not the freenode web IRC interface.
[15:13] <smartboyhw> Wow that page is really new:P
[15:16] <tsimpson> spaces must be escaped: https://wiki.kubuntu.org/Kubuntu/Get%20Involved/WhoWeAre
[15:17] <Riddell> mparillo: yeah best to have no spaces
[15:18] <ScottK> +1 on no spaces
[15:18] <tsimpson> this is why we have CamelCase in wikis
[15:18] <mparillo> That's what I get for cloning: https://wiki.ubuntu.com/Lubuntu/Get%20Involved/WhoWeAre
[15:18] <mparillo> I will switch to camel case. Good for an ancient PERL hacker anyway.
[15:18] <ScottK> Riddell: k-d-s has a diff now.
[15:19]  * Riddell accepts
[15:19] <ScottK> Note that mgraesslin's name is fine in a proper utf-8 locale (as one finds in debian/changelog).  The weirdness is just the LP diff.
[15:19] <ScottK> Thanks.
[15:20] <BluesKaj> 404 error , failed to fetch kubuntu backports ..no access to 4.9.2 here
[15:28]  * ScottK checks "keep upstream happy" off his list for today.
[15:29] <Riddell> thanks ScottK :)
[15:34] <mparillo> Camel Case: https://wiki.kubuntu.org/Kubuntu/GetInvolved/WhoWeAre
[15:41] <ScottK> xnox: Do you consider yourself a Kubuntu person?
[15:41] <Riddell> we might have some persuasion to do for that to happen :)
[15:41] <xnox> ScottK: in what sense?
[15:42] <ScottK> xnox: In the sense that mparillo put you on ^^^ wiki page and do you want that?
[15:43] <xnox> ScottK: meh =)
[15:43] <xnox> ScottK: see https://bugs.launchpad.net/ubuntu/+bug/1055866/comments/2  I was tempted to end it with "Ubuntu, Kubuntu, Xubuntu, Lubuntu, Ubuntu Studio, Mythbuntu Developer"
[15:44] <xnox> ScottK: due to convenient core-dev team inclusion in official derivatives ;-)
[15:44]  * xnox oh edubuntu as well =)
[15:45] <BluesKaj> Riddell, are the backports actaully accessable , or is kde still being uploaded ?
[15:45] <Riddell> BluesKaj: installed and worked good for me
[15:45] <ScottK> BluesKaj: Look on the web site.  It's there.  I think you need to talk to #launchpad about why it's not working.
[15:46] <xnox> ScottK: I am not a spokesperson for kubuntu project, and will not reply personal email aiming to get a quote by "Kubuntu developer"
[15:46] <xnox> listing me on the wiki page is fine =) but I'd only be interested in low-level stuff or installer =)
[15:46] <ScottK> xnox: One small point: Kubuntu is not an Ubuntu derivative.  It's a different flavor produced by the Ubuntu project.  Derivatives are things like Mint.
[15:47] <ScottK> OK.
[15:47] <ScottK> Can you edit yourself then?
[15:48] <BluesKaj> ScottK, I looked at the website , but it has no special ppa other than the backports ...maybe a server change is order here
[15:48] <xnox> ScottK: ok, sorry for the confusing terms. I refer to "official derivatives" (flavours that is) and "unofficial derivatives" (mint, hannah montana linux etc.)
[15:49] <ScottK> xnox: No such thing as official derivatives.
[15:49] <ScottK> There are flavors and there are derivatives.
[15:49] <ScottK> Mint is a derivative, Kubuntu, etc are not.
[15:52] <xnox> ichtux linux was/is a meta package in ubuntu archive (hence a flavour?!) but it was integrated enough to be build on the same infrastructure e.g. cdimage & iso-tracker.
[15:52] <xnox> official: published on cdimage.u.c. the rest is upcomming, obsolete, or unofficial to me =))))
[15:53]  * xnox should not be a spokes person. see how politically incorrect I am =)
[15:53] <BluesKaj> ok Riddell I assumed the 12.10 backport would be loaded as well , not the case
[15:54] <ScottK> xnox: No.  Itchthux was never a flavor.  We never built ISOs for it.
[15:54] <ScottK> Sabily is similar.
[15:54] <ScottK> (former Muslim Edition)
[15:54] <ScottK> So you can't install them from the official archive.
[15:54] <xnox> but they did cd's themselves. hmm... ok, i see now.
[15:54] <ScottK> Yep.
[15:54] <mparillo> ScottK, xnox: I just grabbed some IRC handles I see frequently to have a starting point for the table. One edit could be to delete the entire row.
[15:55] <ScottK> They are, I think, most properly Ubuntu remixes.
[15:55]  * xnox /0\
[15:55] <ScottK> I know the language is annoying, but I think it's important to get it right.
[15:56] <ScottK> The different terms imply different relationships with the Ubuntu project.
[15:56] <xnox> well for trademarks and stuff.....
[15:56] <xnox> it's not like we get enough problems with licensing alone.
[16:00] <ScottK> Well it can get fun.
[16:00] <yofel> mparillo: did you just delete the page? seems to be gone
[16:01] <yofel> hm, back, edit conflict -.-
[16:01] <mparillo> I did not.
[16:01] <ScottK> One of the blockers for getting the (now) Sabilly meta packages into the archive was that none of the developers would sign the Ubuntu CoC because (at the time) it claimed sabdfl was infallible.  The claim was made in jest, but it conflicted with the religious views of the developers, so they wouldn't sign it.
[16:02] <ScottK> xnox: You have no idea the fun some of this stuff entails.
[16:04] <mparillo> yofel: It looks like ScottK fixed his time zone and added Packaging, Management as his areas of expertise. Maybe the wiki software locked the page during his edits?
[16:04] <yofel> I didn't see an edit warning when I edited it, after I saved the page was gone. Now it's back though
[16:05] <xnox> ScottK: ok.
[16:09] <Riddell> bah, turns out owncloud backports isn't just a straight recompile
[17:19] <Riddell> shadeslayer: the sticker printer you used in Bangalore, any similar ones near your home?
[18:23] <shadeslayer> Riddell: spacetime's father owns a shop that could probably print them
[18:23] <shadeslayer> I mean, Rishab Arora, you might have met him at Akademy :)(
[18:42] <BluesKaj> ok , 4.9.2 working well on 12.04 and 12.10
[19:19] <kubotu> ::workspace-bugs:: [1017709] package kdm (not installed) failed to install/upgrade: subprocess installed pre-removal sc... @ https://bugs.launchpad.net/bugs/1017709 (by jjinco33)
[19:51] <kubotu> ::qt-bugs:: [1041945] "multiple errors leading to this one" @ https://bugs.launchpad.net/bugs/1041945 (by Christopher Horan)
[20:07] <micahg> someone want to take care of Bug #1061187
[20:09] <shadeslayer> micahg: needs rebuild?
[20:10] <micahg> yeah, should be a no change rebuild (keep in mind same version in oneiric/precise when versioning)
[20:11] <shadeslayer> I don't think I have upload rights, unless it's in the kubuntu package set
[20:11] <shadeslayer> which iirc it isn't
[20:11] <micahg> meh, I can just do it later then
[20:11] <micahg> unless someone else (MOTU/core-dev) grabs it
[20:11] <shadeslayer> yah
[20:12] <vHanda> shadeslayer: one sec
[20:13] <vHanda> shadeslayer: https://bugs.kde.org/show_bug.cgi?id=307388
[20:13] <vHanda> please include both the patches
[20:13] <shadeslayer> ok cool
[20:14] <shadeslayer> vHanda: anything else?
[20:14] <vHanda> nope. that's it
[20:14] <shadeslayer> Riddell: ScottK ^ We should get that in before rolling 4.9.2 out
[20:14] <ScottK> Too late.
[20:14]  * shadeslayer can do it tomorrow if no one else want's to do it today
[20:14] <shadeslayer> oh, did you copy to updates?
[20:14] <ScottK> Please get it uploaded ASAP so I can review.
[20:14] <ScottK> Yes.  Riddell did.
[20:15] <shadeslayer> ah ok, I have a kde4libs patch as well, fixes samba support
[20:15] <shadeslayer> this http://commits.kde.org/kdelibs/8e9bfe11f54e3fa5000a86773b21bdcdcff44bd5
[20:16] <shadeslayer> ok, let me reboot
[20:17]  * ScottK is busy trying to sort out with upstream having PyKDE4 for 4.10 buildable on Quantal when the time comes.
[20:22] <micahg> debfx: I must be missing something, why is qtwebkit being  built during the qt4-x11 build?
[20:23] <debfx> micahg: to avoid a build-dependency cycle between qt4-x11 and qtwebkit. qt assistant (which is part of qt4-x11) links against qtwebkit.
[20:24] <micahg> debfx: that seems silly, especially if qtwebkit and the copy in qt4-x11 are out of sync
[20:26] <micahg> well, the dep cycle makes sense, but is frustrating
[20:26]  * micahg wishes upstreams wouldn't couple stuff so tightly
[20:26] <debfx> of course it's silly, at least qt5 is properly modularized
[20:27] <debfx> binary compatibility isn't an issue in practice as qtwebkit is in a low maintenance mode
[20:27] <micahg> but IMHO, it should only be enabled for the bootstrap release, once there's an ABI compatible qtwebkit, it should be turned off IMHO
[20:28] <micahg> otherwise you risk binary incompatibility with the qtwebkit in the archive (unless it's statically linked)
[20:29] <debfx> that would only be an issue if qtwebkit added functions or classes and qt assistant would use those
[20:29] <debfx> both is very unlikely
[20:30] <micahg> yes, in addition though, it wastes lots of build time each time building qtwebkit (and makes arm* painfully long)
[20:31] <micahg> anyways, qt5 in R? :)
[20:32] <shadeslayer> sounds like we have a volunteer to do Qt 5 packaging
[20:32] <shadeslayer> :P
[20:33] <debfx> that's why I proposed disabling qtwebkit on arm (leading to a feature loss in qt assistant on arm)
[20:33] <debfx> I'd prefer Qt 5 in Debian first
[20:37] <ScottK> Qt 5 won't affect us much until we have a KDE ported to use it.
[20:39] <debfx> It affects us if we want to provide a nice environment for developers
[20:40] <ScottK> Sure.
[20:51] <ScottK> Riddell: I think we need to teach sru-release about binary packages.
[20:52] <kubotu> ::qt-bugs:: [744812] FontConfig/Qt stack choke on Ubuntu Medium font meta-data (No medium in Inkscape and too bo... @ https://bugs.launchpad.net/bugs/744812 (by Francois Thirioux)
[20:52] <kubotu> ::qt-bugs:: [1057578] Vulnerable against "CRIME" attack @ https://bugs.launchpad.net/bugs/1057578 (by Felix Geyer)
[20:54] <shadeslayer> ScottK: can I just upload to quantal instead of quantal-proposed?
[20:59] <shadeslayer> ScottK: uploaded nepomu-core to quantal
[21:01] <JontheEchidna> I did upload debian's packaging for qt5 qt-base to -experimental. (There's still a lot of Qt5 still to go though)
[21:01] <JontheEchidna> the -dev packages between 4 and 5 are totally in conflict though
[21:01] <JontheEchidna> but you can run some of the demos from the -demos package
[21:02] <shadeslayer> ah shoot
[21:02] <shadeslayer> ScottK: can you unapprove nepomuk, I think I might have uploaded with -sa
[21:06] <shadeslayer> ScottK: kde4libs uploaded as well
[21:51] <Riddell> JontheEchidna: upstream are talking about changing qt5 so the -dev stuff doesn't conflict
[21:51] <Riddell> but in the mean time that's just what happens
[21:53] <shadeslayer> well ... uh ... I have to go in a couple of minutes, so could someone please approve kde4libs and nepomuk-core ( the second one I just uploaded )
[21:53] <Riddell> can do
[21:54] <shadeslayer> awesome
[21:54] <shadeslayer> Riddell: oh and what about the stickers that you were talking a about?
[21:56] <Riddell> shadeslayer: I'd just like to get some for UDS and was wondering if there was an easy and cheap way to do so
[21:56] <shadeslayer> sure, how many, and do you have a design?
[21:58] <shadeslayer> and your budget as well :)
[21:58] <Riddell> shadeslayer: lots, something like this I'm thinking starsky.19inch.net/~jr/tmp/output.pdf
[21:59] <Riddell> budget is whatever we can convince the kubuntu council to pay
[21:59] <shadeslayer> heh :D
[22:00] <shadeslayer> oh btw there was this guy on G+, maybe we can ask him if we can design a sticker for us?
[22:01] <Riddell> shadeslayer: reject  nepomuk-core from 1 hours ago?
[22:02] <shadeslayer> Riddell: yes
[22:02] <shadeslayer> accidentally did a upload with source -.-
[22:02] <ScottK> shadeslayer: nepomuk - approve or unapprove?
[22:02] <shadeslayer> reject the old one, accept the new one
[22:02] <ScottK> shadeslayer: To quantal is fine.
[22:02] <shadeslayer> ScottK: figured as much :)
[22:03] <Riddell> accepts done
[22:03] <shadeslayer> :D
[22:03] <Riddell> ScottK: beat you
[22:03] <shadeslayer> thanks
[22:03] <ScottK> Riddell: Only because I'm busy with wgrant trying to figure out how to untangle your package copying mess...
[22:04] <shadeslayer> Riddell: lots=500 ?
[22:06]  * Riddell hides from ScottK in shame
[22:06] <Riddell> shadeslayer: yeah
[22:07] <shadeslayer> alright, will talk to Rishab and figure out how much it'll cost
[22:09] <Riddell> thanks


[16:00]  * vorlon waves
[16:00] <juliank> o/
[16:00] <cyphermox> o/
[16:01] <sil2100> o/
[16:01] <vorlon> #startmeeting
[16:01] <meetingology> Meeting started Thu Mar  7 16:01:34 2019 UTC.  The chair is vorlon. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> Available commands: action commands idea info link nick
[16:01] <vorlon> [TOPIC] Lightning round
[16:01] <vorlon> $ echo $(shuf -e vorlon bdmurray xnox tdaitx doko sil2100 rbalint infinity cyphermox mwhudson juliank waveform)
[16:01] <vorlon> doko sil2100 infinity rbalint bdmurray xnox mwhudson cyphermox juliank vorlon tdaitx waveform
[16:02] <doko> first time 1st
[16:02] <doko> and didn't prepare an update ... so openjdk-11 transition & toolchain work
[16:02] <doko> (done)
[16:02] <sil2100> - SRU reviews and releases
[16:02] <sil2100> - Kernel reviews and releases, lots!
[16:02] <sil2100> - Last week: 16.04.6
[16:02] <sil2100> - This week: 14.04.6 - and it's out now!
[16:02] <sil2100> - Lots of package copies and reviews for the OpenJDK-11 bionic transition
[16:03] <sil2100> - Some minor changes to the purge-count cdimage MP, thanks Steve for merging!
[16:03] <sil2100> - Working around checksum-directory limitations in the image archival scripting
[16:03] <sil2100> - Tomorrow: out of office o/
[16:03] <sil2100> (done)
[16:03] <rbalint> o/.
[16:04] <bdmurray> rbalint: does that mean you are ready?
[16:04] <rbalint> * partner work
[16:04] <rbalint> * uploaded wireshark 2.6.7-1 through Debian
[16:05] <rbalint> * packaged wslu for Disco
[16:05] <rbalint> * gardened wsl bugs in LP
[16:05] <rbalint> * fixed regresion in Disco's acpid
[16:05] <rbalint> (done)
[16:05] <bdmurray> reported bug regarding postgresql charm (LP: #1818145)
[16:05] <bdmurray> tested new postgresql charm in ET mojo spec (success!)
[16:05] <bdmurray> tested IS changes to ET mojo spec (fail :-( )
[16:05] <bdmurray> submitted MP which fixes that (ET mojo spec)
[16:05] <bdmurray> research into how nbs report and checkrdepends works
[16:05] <bdmurray> uploaded new version of distro-info that only shows LTSes for supported-esm
[16:05] <bdmurray> started SRU of distro-info and distro-info-data
[16:05] <bdmurray> SRU verification of apport SRUs for 18.04
[16:05] <bdmurray> research into gdb issues in disco
[16:05] <bdmurray> reported gdb bug re: debug-file-directory (LP: #1818918)
[16:05] <bdmurray> special SRU review of curtin
[16:05] <bdmurray> discussed machine readable rls reports with will cooke
[16:06] <bdmurray> done but no check mark b/c something sucks
[16:06] <bdmurray> xnox:
[16:06] <xnox> * short week, was out tue-mon since malta
[16:06] <xnox> * openssl 1.1.1b uploaded & migrated
[16:06] <xnox> * zkey fixes for automation (needed for installers)
[16:06] <xnox> * validating / sheparding openssl/s390x SRUs
[16:06] <xnox> * prototyping rebootspeed
[16:06] <xnox> * send kernel autopkgtest fixes for review to the kernel team
[16:06] <xnox> DONE
[16:06] <cyphermox> finished grub2 merge -- uploaded after fixing my bad pointer math
[16:06] <cyphermox> investigating grub theming / menu changes
[16:06] <cyphermox> preparing SRU for grub2 conffile fixes
[16:06] <cyphermox> code review open PRs for netplan
[16:06] <vorlon> sharphed
[16:06] <cyphermox> netplan.io 0.96 tagging + prepare upload for disco
[16:06] <cyphermox> sponsored carla package for e.eickmeyer
[16:06] <cyphermox> clarifying upstream systemd "ActivationMode=" PR + rebase
[16:06] <cyphermox> (done)
[16:08] <juliank> oh, it's my time!
[16:08] <juliank> * APT
[16:08] <juliank>  - Fixed a few bugs in never pinning in apt/trusty git branch
[16:08] <juliank>  - Uploaded SRUs for all releases
[16:08] <juliank>  - SRU verifications
[16:08] <juliank>  - Another small fix and translation updates for 1.8.0 (release ETA tomorrow)
[16:08] <juliank>  - auth.conf.d directory is missing (LP: #1818996)
[16:08] <juliank>  - seemed like auth.conf.d support in trusty and xenial did not work for https, only http; turned out I forgot to upgrade apt-transport-https to proposed ...
[16:08] <juliank> * PackageKit:
[16:08] <juliank>  - Merge new version from unstable
[16:08] <juliank>  - Forwarded frontend-locking patch to upstream
[16:08] <juliank>  - SRU crash fix to bionic and cosmic (LP: #1818201)
[16:08] <juliank> * autopkgtest-cloud: Change request.cgi to sort printed fields by name, so output is in stable order
[16:08] <juliank> * python-mechanicalsoup: Fixed tests, forwarded to Debian
[16:08] <juliank> * apport:
[16:08] <juliank>   - Introduce support for non-positional arguments (LP: #1732962)
[16:08] <juliank>   - Fixup for style issue in yesterday's upload that broke the build
[16:08] <juliank> * livecd-rootfs/bionic: new minimize-manual merge proposal https://code.launchpad.net/~juliank/livecd-rootfs/+git/livecd-rootfs/+merge/363932
[16:08] <juliank> * update-notifier / apt esm hook thinking, fixes
[16:08] <juliank> (ubottu is a bit slow..)
[16:09] <juliank> (done)
[16:09] <vorlon>  * assist with openjdk-11 SRUs
[16:09] <vorlon>  * full SRU day last Friday, made some progress on the queues
[16:09] <vorlon>  * discussions around SecureBoot signing of FIPS kernels
[16:09] <vorlon>  * discussions around trusty ESM transition
[16:09] <vorlon>  * TB business
[16:09] <vorlon> (done)
[16:09] <tdaitx> * openjdk-11 bionic security transition
[16:09] <tdaitx>   - reviewed and uploaded packages
[16:09] <tdaitx>   - bump & rebuild arch specific packages
[16:09] <tdaitx>   - updated list of packages that also need Cosmic SRU
[16:09] <tdaitx>     - 153 packages
[16:09] <tdaitx>     - 9 are arch specific (no binary copies)
[16:09] <tdaitx> Other:
[16:09] <tdaitx> - travelling back home on Saturday early morning
[16:09] <tdaitx> - wondered if the bot can handle the openjdk transition bug, decided not to try
[16:10] <tdaitx> - (done)
[16:10] <waveform> * Reading up on ARM TrustZone (specifically in relation to pi3)
[16:10] <waveform> * Testing wimpress' bluetooth fixes on classic & core (not finished core yet)
[16:10] <waveform> * Verified u-boot-tools SRU
[16:10] <waveform> * Added Pi-specific permissions to linux-firmware-raspi2
[16:10] <waveform> * Added hacks from Malta to livecd-rootfs to reduce boot time, and ensure getty starts after cloud-init's done
[16:10] <waveform> * Moving Pi-specific hacks from livecd-rootfs to linux-firmware-raspi2 (need to test upgrade path)
[16:10] <waveform> * gpiozero 1.5 tested; needs colorzero (also tested) importing (upstream? SRU?)
[16:10] <waveform> * Did I mention the reading up on ARM TrustZone? Well, more of that...
[16:10] <waveform> (done)
[16:11] <gaughen> pause for an argument about fortnite
[16:12] <bdmurray> I was disappointed we didn't do the dance off gaughen
[16:12] <rbalint> gaughen, is it snapped?
[16:13] <vorlon> any questions over status?
[16:13] <cyphermox> can we patent our pattern of discussion?
[16:14] <cyphermox> since we're essentially talking about copyright and trademark, etc.
[16:14] <vorlon> waveform: are the livecd-rootfs changes hacks, or real fixes? :)
[16:14] <waveform> vorlon, some are "fixes" or even just downright configuration, but they're definitely "hacks" in the way they're implemented!
[16:15] <tdaitx> waveform: don't answer that, it is a trick
[16:15] <vorlon> heh
[16:15] <vorlon> [TOPIC] Bugs
[16:15] <vorlon> [LINK] http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html#foundations-bugs
[16:15] <xnox> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817097
[16:15] <bdmurray> cyphermox: It doesn't look like bug 1794292 was fixed in cosmic, it should be SRu'ed right?
[16:16] <vorlon> xnox: so isn't that a kernel bug?
[16:16] <cyphermox> bdmurray: yes
[16:16] <bdmurray> cyphermox: there are still 12k crashes for Cosmic
[16:16] <cyphermox> yep
[16:16] <bdmurray> cyphermox: is that something you'll take then?
[16:16] <cyphermox> yep.
[16:16] <cyphermox> now we have nice shiny upstream-blessed patches too
[16:16] <bdmurray> cyphermox: feel free to ping me if you upload something
[16:19] <bdmurray> bug 1818890 was reported the other day
[16:19] <bdmurray> That seems worth fixing
[16:19] <cyphermox> wat, again?
[16:20] <sil2100> cyphermox: you have context on that one?
[16:20] <cyphermox> well, I'm pretty sure we've seen that happen before
[16:20] <cyphermox> it's common class of problems, where packages aren't being removed correctly after install
[16:21] <bdmurray> I'll target it and card it
[16:21] <vorlon> thanks
[16:22] <bdmurray> bug 1817862 should probably be carded too based of seb's comment
[16:22] <xnox> argh
[16:22] <vorlon> fwiw when I noticed the desktop image got bigger recently, analysis of the packages showed language packs turning up in the manifest which hadn't been there in the image earlier this year
[16:23] <vorlon> which may mask the actual problem, or may be related
[16:23] <vorlon> bdmurray: agreed, though the traceback looks generic and useless
[16:23] <vorlon> (and the bug title makes the reports ugly :)
[16:24] <bdmurray> should the error tracker just limit the title to 42 characters or so?
[16:24] <vorlon> wfm
[16:24] <vorlon> (low priority though)
[16:24] <cyphermox> vorlon: langpacks in manifest may actually be why it's a problem
[16:24] <vorlon> cyphermox: ack
[16:25] <cyphermox> something with shipped vs. live, we'll see
[16:25] <bdmurray> seb also tagged bug 1817619 but I haven't looked into it yet
[16:25] <vorlon> uh
[16:25] <vorlon> how is that not a duplicate of the bugs I closed invalid?
[16:26] <vorlon> answer: it is but has not been marked such
[16:26] <cyphermox> indeed
[16:26] <vorlon> I'll take care of it
[16:27] <vorlon> bdmurray: next?
[16:27] <didrocks> bdmurray: vorlon: I've already done the analyzes of bug #181889, you can give it to me
[16:28] <didrocks> (not related to the image size increase though, IMHO)
[16:28] <bdmurray> vorlon: that's it from me
[16:28] <vorlon> [TOPIC] Proposed-migration
[16:28] <vorlon> [LINK] http://people.canonical.com/~ubuntu-archive/proposed-migration/disco/update_excuses_by_team.html#foundations-bugs
[16:28] <bdmurray> didrocks: is that the right number?
[16:29] <vorlon> glibc is out of the way now
[16:29] <didrocks> bdmurray: sorry, missing one digit: bug #1818890
[16:29]  * didrocks vanishes and let you continue your meeting
[16:29] <vorlon> ah and it looks like openssl + r-cran-openssl got sorted too
[16:29] <vorlon> so it's a short list
[16:29] <rbalint> i'm triaging curl->ruby-rack
[16:30] <bdmurray> cyphermox: ^^
[16:30] <vorlon> pillow still waiting for an MIR
[16:30] <doko> python-scipy regressed in the release pocket as well, afaics
[16:30] <vorlon> rbalint: ok.  I've prodded the Server Team about the fact that we maybe want to remove the whole rails stack instead of trying to play whack-a-mole with these packages we can't maintain and we believe no one uses
[16:30] <vorlon> but I haven't seen any action from them yet wrt socializing this plan
[16:30] <rbalint> vorlon, i'm +1 on that for disco
[16:31] <vorlon> rbalint: unfortunately it doesn't unblock curl any quicker because ruby-rack is quite deep in the stack so it would take a while to unwind, unless you think this particular regression is ignorable
[16:31] <cyphermox> vorlon: so who will write the pillow MIR?
[16:32] <vorlon> cyphermox: is it not written yet?  I assumed doko had a handle on this
[16:32] <cyphermox> typically it's nice to not write your own, since it makes it a little weird to also review it ;)
[16:32] <cyphermox> well, if doko wants to write it, I'll review
[16:32] <cyphermox> or the other way around
[16:32] <rbalint> vorlon, i'll be back with and answer for curl
[16:32] <vorlon> cyphermox: https://bugs.launchpad.net/ubuntu/+source/libimagequant/+bug/1812858 ?
[16:32] <cyphermox> I couldn't find a bug for it
[16:32] <cyphermox> ah
[16:32] <cyphermox> well, libimagequant is fine, waiting for security review. top of the queue iirc
[16:33] <vorlon> lintian is an issue with the new autopkgtests having become consistently slower and now hitting timeouts
[16:33] <vorlon> this was a post-freeze sync by a community member, who I have asked to own this; I don't feel any responsibility for getting lintian 2.9.1 in until this is resolved
[16:34] <vorlon> doko: if python-scipy has regressed also in release, do you want to follow up with me on #ubuntu-release after this to get it badtested?
[16:35] <vorlon> xnox: fuse-zip/s390x + fuse, does that need attention?
[16:35] <doko> vorlon: but later tonight. afk atter the meeting
[16:35] <vorlon> ok
[16:37] <vorlon> xnox: fuse-zip/s390x?
[16:37] <xnox> possibly
[16:37] <xnox> what's wrong?
[16:37] <vorlon> do you want to take it?
[16:37] <vorlon> failing autopkgtest
[16:37] <vorlon> xnox: http://autopkgtest.ubuntu.com/packages/f/fuse-zip/disco/s390x
[16:39] <vorlon> doko: do you know anything about the epsilon regression w/ new python-defaults?
[16:40] <doko> vorlon: that's the new kernel, changed diskstats
[16:40] <doko> I'm looking at that one
[16:40] <vorlon> ok
[16:40] <vorlon> I think that's everything that needs attention currently
[16:40] <vorlon> [TOPIC] AOB
[16:40] <vorlon> anything else?
[16:42] <vorlon> #endmeeting
[16:42] <meetingology> Meeting ended Thu Mar  7 16:42:59 2019 UTC.
[16:42] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2019/ubuntu-meeting.2019-03-07-16.01.moin.txt
[16:43] <vorlon> thanks, all!
[20:01] <tsimonq2> o/
[20:01] <Kilos> o/
[20:02] <Wild_Man> o/
[20:02] <nzoueidi> hey folks
[20:04] <Kilos> aw genii  sleeping so no coffee
[20:04] <nzoueidi> okay the UMB are here, so we can start
[20:04] <nzoueidi> just to check frederik-f are you here?
[20:05] <Kilos> frederik-f  ping
[20:08] <Wild_Man> hello frederik-f
[20:08] <frederik-f1> Hi!
[20:08] <Kilos> hi
[20:09] <nzoueidi> Hey there
[20:09] <nzoueidi> okay, tsimonq2 are you here?
[20:09] <tsimonq2> Yup
[20:10] <nzoueidi> cool, let's start then \o/
[20:10] <nzoueidi> #startmeeting 20 UTC Membership Board Meeting
[20:10] <Kilos> yip
[20:10] <meetingology> Meeting started Thu Mar  7 20:10:11 2019 UTC.  The chair is nzoueidi. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20:10] <meetingology> Available commands: action commands idea info link nick
[20:10] <nzoueidi> Hey people, welcome to the Membership Board Meeting
[20:10] <nzoueidi> The wiki page for the Review Board is available here https://wiki.ubuntu.com/Membership/Boards.
[20:11] <nzoueidi> We will attempt to get through all of the applicants that have added themselves to that list before today's meeting and while we have only frederik-f
[20:11] <nzoueidi> Then it is good and a quick meeting :D
[20:11] <frederik-f> :) cool
[20:11] <nzoueidi> frederik-f, you need to introduce themselves (1-5 sentences)
[20:12] <nzoueidi> and provide for us your wiki page link and the LP account
[20:12] <nzoueidi> #topic frederik-f
[20:12] <frederik-f> Okay! Hello, I am Frederik, living in Germany, working as java dev in my daily work, and contributed to the Yaru theme a lot
[20:12] <frederik-f> This is my wiki page: https://wiki.ubuntu.com/FrederikFeichtmeier
[20:13] <Wild_Man> frederik-f, how long have you been contributing?
[20:13] <frederik-f> My launchpad page is very empty and not very exiting because I contributed mainly on github, because that is where all the yaru stuff happens :(
[20:13] <frederik-f> I contribute since beginning of 2017 to yaru
[20:14] <nzoueidi> #voters Wild_Man Kilos tsimonq2 nzoueidi
[20:14] <meetingology> Current voters: Kilos Wild_Man nzoueidi tsimonq2
[20:14] <nzoueidi> if anyone have any question for frederik-f please go ahead
[20:14] <Wild_Man> I looked at github and that is when I thought you started contributing just wanted to make sure
[20:14] <nzoueidi> and if there is anyone here that is supporting the application of frederik-f  to the Ubuntu Membership, please show up :D
[20:15] <frederik-f> This is my launchpad page, but is very empty: https://launchpad.net/~frederik-feichtmeier
[20:15] <frederik-f> All my PRs are on github :(
[20:16] <frederik-f> https://github.com/ubuntu/yaru/graphs/contributors
[20:16] <frederik-f> My name is "Feichtmeier" on github
[20:16] <nzoueidi> I have some questions, why aren't you involved into the Germany LoCo team?
[20:17] <frederik-f> I actually do not know what it is :(
[20:17] <frederik-f> I started to contribute to the Ubuntu theme, because I thought they needed help back then when it started.
[20:17] <frederik-f> I can surely help, I will google what it is
[20:18] <nzoueidi> sure, np
[20:18] <nzoueidi> here is the link for the LoCo team in Germany: http://loco.ubuntu.com/teams/ubuntu-de-locoteam/
[20:18] <nzoueidi> I like your github profile. Keep up the good work
[20:19] <Kilos> impressive frederik-f
[20:19] <Wild_Man> impressive indeed
[20:19] <frederik-f> I hope you like the yaru theme :)
[20:20] <frederik-f> I will try to attend to LoCo, just googled it!
[20:21] <nzoueidi> any other question from the board?
[20:21] <Kilos> join them
[20:21] <Kilos> nope i am happy
[20:21] <Wild_Man> No
[20:21] <nzoueidi> what about you tsimonq2?
[20:22] <tsimonq2> No questions here.
[20:22] <nzoueidi> alrighty
[20:22] <nzoueidi> #votesrequired 4
[20:22] <meetingology> votes now need 4 to be passed
[20:22] <nzoueidi> #vote for frederik-f  Membership!
[20:22] <meetingology> Please vote on: for frederik-f  Membership!
[20:22] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[20:22] <Kilos> +1 keep up the good work
[20:22] <meetingology> +1 keep up the good work received from Kilos
[20:22] <Wild_Man> +1
[20:22] <nzoueidi> +1 from me, keep it up frederik-f :)
[20:22] <meetingology> +1 received from Wild_Man
[20:22] <meetingology> +1 from me, keep it up frederik-f :) received from nzoueidi
[20:23] <diddledan> dang, I'm late
[20:23] <Kilos> lol
[20:24]  * nzoueidi pinging tsimonq2 to vote :P
[20:25] <diddledan> +1 if I were to be included in the voters list, but I arrived late, so I don't count :-p
[20:25] <Kilos> tsimonq2  we await your vote
[20:25] <nzoueidi> he is afk I think
[20:25] <tsimonq2> Oh
[20:25] <tsimonq2> Sorry
[20:25] <tsimonq2> +1
[20:25] <meetingology> +1 received from tsimonq2
[20:25] <nzoueidi> xD
[20:25] <nzoueidi> it is okay
[20:25] <nzoueidi> #endvote
[20:25] <meetingology> Voting ended on: for frederik-f  Membership!
[20:25] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:25] <meetingology> Motion carried
[20:26] <nzoueidi> congratulations frederik-f and welcome aboard :)
[20:26] <toddy> Congrats frederik-f and if you have any questions about the German LoCo Team than you can ask me everything. :)
[20:26] <tsimonq2> Congrats!
[20:26] <frederik-f> Woah thank you!
[20:26] <Kilos> frederik-f  welcome aboard
[20:26] <diddledan> awesome!
[20:26] <frederik-f> Time for a beer! :D Thank you very much
[20:26] <Wild_Man> Congrats frederik-f
[20:26]  * nzoueidi going to add frederik-f to ~ubuntumembers
[20:27] <nzoueidi> Thank you guys for assisting this meeting and have a good night
[20:27] <frederik-f> toddy: thank you, I will! Here? Or anywhere else? Sorry I am a big IRC noob
[20:27] <frederik-f> I had hard times to register my nickname
[20:27] <Kilos> lol
[20:28] <nzoueidi> #Endmeeting
[20:28] <meetingology> Meeting ended Thu Mar  7 20:28:16 2019 UTC.
[20:28] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2019/ubuntu-meeting.2019-03-07-20.10.moin.txt
[20:29] <sarnold> frederik-f: https://launchpad.net/~ubuntumembers  :)
[20:30] <frederik-f> Cheers! Thank you!
[20:31] <Kilos> cheers
[20:33] <Wild_Man> frederik-f, you have been added
[20:33] <frederik-f> Thank you!
[20:33] <Wild_Man> Your welcome!
[20:40] <frederik-f> I will leave Thunderbird IRC now! Thank you very much for letting me in
[20:40] <Kilos> lol you welcome
[20:40] <Kilos> dont forget irc now
[20:40] <Kilos> you use kde?
[20:40] <frederik-f> I wont! No I use Ubuntu "vanilla" - need to test the yaru stuff :)
[20:41] <Kilos> oh no i am thinking of konversation
[20:41] <Kilos> keep it up
[20:42] <diddledan> `snap install irccloud` :-)
[20:42] <frederik-f> ah! Well I tried polari but now that I "returned" full mozilla again, after I threw google of my PC, I thought I try thunderbird IRC, but yeah, maybe I should try something else :D
[20:43] <Kilos> lol i use thunderbird for mail only
[20:43] <Kilos> you can try exchat
[20:43] <Kilos> hexchat
[20:43] <Kilos> broken H
[20:43] <frederik-f> Ex-chat would also be a nice brand :D
[20:43] <diddledan> that's a snap too :-)
[20:43] <Kilos> lol
[20:44] <frederik-f> Chat with all your "Ex's" O.o
[20:44] <Kilos> nono you end up sleeping with the dogs
[20:44] <frederik-f> haha
[20:44] <frederik-f> okay, now really goodbye, thank you guys


[07:32] <_novgorod> hey everyone, looking for a bit of help with what i'm hoping to be a minor (crossing fingers*) audio issue in the latest lts.. anyone keen to offer aid?
[07:35] <willcooke> morning all
[07:35] <_novgorod> morning willcooke
[07:35] <_novgorod> willcooke, well, actually it's about half past midnight here but still, morning/evening.. whichever suits ya
[07:36] <willcooke> :))
[07:36] <willcooke> Hi _novgorod
[07:37] <_novgorod> willcooke, greetings to you
[07:40] <_novgorod> willcooke, you make the leap to 18.04 yet?
[07:41] <willcooke> _novgorod, oh yes!  Long ago
[07:43] <seb128> good morning desktopers
[07:43] <seb128> hey willcooke
[07:43] <_novgorod> willcooke, right on. i only just recently. i grew fond of my previous dual boot and didn't want to make the leap right away
[07:45] <willcooke> _novgorod, nothing wrong with being a bit cautious :)
[07:48] <duflu> _novgorod, what is the problem exactly?
[07:48] <_novgorod> not so much cautious as i was in love with the old set of partitions. the dual boot served me well. in the end, it was the lack of space on my drive.. needed more
[07:50] <_novgorod> duflu, not exactly sure, i know that i took an update recently and out of neglect failed to read it, it started at boot and i'm sure i just clicked away to get to something else. either way, my audio has been finicky at best
[07:50] <_novgorod> duflu, it's coming out rather muffled now, as opposed to crisp.
[07:51] <duflu> _novgorod, the first thing to check is that you're not using any audio extension cables. Poor quality connections can completely destroy the sound, even remove voice/instruments completely
[07:51] <duflu> (how that happens I don't know, but it does)
[07:51] <_novgorod> duflu, i don't cable
[07:52] <_novgorod> bluetooth from time to time, but never cable.
[07:52] <_novgorod> bluetooth audio is fine btw
[07:52] <_novgorod> no problems there.
[07:53] <duflu> _novgorod, want to reword that? If it's not cable and not bluetooth then what is it? :)
[07:53] <_novgorod> duflu, system audio.. on it's own without bluetooth is damaged.
[07:54] <duflu> _novgorod, sounds non-obvious. I would suggest making a bug so we can see the details. Just run "ubuntu-bug pulseaudio"
[07:56] <duflu> _novgorod, another idea: check your sound settings and ensure you have not allowed volume over 100%, because going over 100% will usually cause distortion
[07:57] <oSoMoN> good morning desktoppers
[07:57] <duflu> Morning oSoMoN
[07:58] <_novgorod> duflu, i don't exceed that i'm aware of, which part of the bug would be most helpful?
[07:59] <duflu> _novgorod, not sure yet. Just submit everything that gets attached automatically
[08:00] <oSoMoN> hey duflu
[08:02] <Laney> hey hey
[08:05] <duflu> Morning Laney
[08:09] <seb128> lut oSoMoN, en forme ?
[08:09] <seb128> hey Laney, how are you?
[08:09] <_novgorod> duflu, sent
[08:10]  * duflu waits for mail
[08:11] <oSoMoN> seb128, ça va, et toi?
[08:11] <oSoMoN> hey laney
[08:11] <seb128> ça va bien, il fait moins chaud !
[08:12] <oSoMoN> looks like it's raining for good now, we've had a few showers yesterday and last night but they never lasted more than 2 mins
[08:15] <Laney> hey duflu seb128 oSoMoN
[08:15]  * Laney is decent
[08:16] <Laney> looking cloudy today
[08:16]  * Laney hopes for rain
[08:18] <willcooke> Laney, how is the allotment holding up?  Anything still alive?
[08:18] <Laney> hey willcooke
[08:19] <Laney> we've put half of a reservoir on it over the past few weeks
[08:20] <Laney> thank goodness for hosepipes /o\
[08:20] <Laney> corn is getting nice and fat
[08:20] <Laney> winter squash are already making vines all over the place
[08:22] <_novgorod> duflu, just checked status, service not found :/
[08:30] <duflu> _novgorod, can you share the text output from 'ubuntu-bug pulseaudio' ?
[08:30] <willcooke> Laney, when Brexit comes and we're all starving, I'll come to you cap-in-hand for a bowl of soup then
[08:30] <willcooke> https://www.theguardian.com/politics/2018/aug/09/im-already-stockpiling-readers-preparing-for-a-messy-brexit
[08:30] <willcooke> !!
[08:31] <duflu> That title makes more sense with the ':
[08:32] <willcooke> :)
[08:32] <willcooke> With articles like that they need to stock pile readers
[08:32] <duflu> And this is the room where I keep my subscribers
[08:33] <_novgorod> duflu, i don't have screenshot setup
[08:33] <willcooke> duflu, lol
[08:33] <duflu> _novgorod, just paste a little bit of the error message and surrounding text here?
[08:35]  * duflu hates having to debug the bug reporting tool but this isn't the first time
[08:39] <_novgorod> duflu, wouldn't let me copy/paste/right click inside of bug window.. here is what i got
[08:39] <_novgorod> duflu, Error: comman ['pacmd'.list'] failed with exit code 1: Home directory not accessible: Permission denied. No PulseAudio daemon running, or not running as session daemon.
[08:39] <_novgorod> Error: command*
[08:39] <duflu> _novgorod, OK. Don't use 'sudo'. Just run the command as yourself
[08:40] <duflu> _novgorod, but if "No PulseAudio daemon running" then that's the first problem. You won't have sound at all (in most apps) if that's true
[08:41] <duflu> That's something I do have a solution for, but it isn't the muffled problem you originally mentioned
[08:43] <_novgorod> duflu, pulse list that gave error previously doesn't list error anymore, still no copy/paste function. it not reads off a list of a dozen indexes
[08:44] <duflu> _novgorod, when you run 'ubuntu-bug pulseaudio' you should eventually be shown a web link. You need to click on and follow that link to finish creating the bug report
[08:45] <_novgorod> duflu, currently i have the same muffled sound in vlc, spotify, and streaming media. i do not have sound adjusting volume.
[08:46] <duflu> _novgorod, OK. If the commands don't work for you then please just create a new bug on this web page: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug
[08:47] <duflu> Then when you have a bug open you will be able to paste more details about what you see in that
[08:50] <_novgorod> duflu, creating new bug now
[08:55] <_novgorod> duflu, i feel like this process used to be easier..
[09:01] <_novgorod> duflu, link sent
[09:03] <jamesh> and now there's hail
[09:25] <_novgorod> duflu, Thanks for your help with all this, much appreciated. i'll check back on the bug a bit later.
[09:26] <duflu> _novgorod, no problem. My day ends soon and it sounds like yours should have already
[09:26] <_novgorod> duflu, you're correct. i'm overdue by about 5 maybe 6 hrs on my end.
[09:27] <_novgorod> duflu, again, many thanks!
[09:30] <tseliot> Laney: hi, it looks like this merge got lost in your last upload of gdm in cosmic. Can you fix it, please? https://code.launchpad.net/~albertomilone/ubuntu/+source/gdm3/+git/gdm3/+merge/351810
[09:32] <Laney> ok, sorry about that
[09:34] <tseliot> np, I'm just trying to get LP: #1778011 fixed for good
[09:40] <seb128> oSoMoN, what version of libreoffice are we aiming at having in cosmic?
[09:56] <Laney> tseliot: there you go
[09:59] <tseliot> Laney: thanks. Did you update git too?
[09:59] <oSoMoN> seb128, 6.1.0
[09:59] <oSoMoN> thanks for filing that tracking bug, btw
[10:00] <seb128> oSoMoN, ok, I opened a bug about it so it's listed on version, might be worth a trello card also?
[10:00] <seb128> oSoMoN, yw!
[10:00] <oSoMoN> seb128, yep, trello card just created
[10:00] <seb128> thx
[10:00] <oSoMoN> https://trello.com/c/PPpAxvXb/197-libreoffice-61-in-cosmic
[10:10] <Laney> tseliot: yeah
[10:13] <duflu> seb128, if I am redesigning Ubuntu patches from scratch (rebasing) on a newer Debian package and have zero history from Ubuntu then should the changelog still show the Ubuntu history or is it fine to only have one Ubuntu entry above Debian?
[10:15] <seb128> I never bothered to keep old changelog entries but I know some people disagree wtih that
[10:16] <duflu> Yeah I have previously kept the Ubuntu changelog and just inserted the latest one from Debian, which is neither
[10:16] <seb128> in practice if a package get in sync and delta again we don't bother remerging old changelogs as well
[10:16] <seb128> which I think is not that different
[10:16] <duflu> seb128, yes it is a "sync" and I am rewriting Ubuntu patches from scratch. So just use the Debian history?
[10:17] <seb128> sounds fine to me yes
[10:17] <duflu> Previous update: 2017-08-09
[10:17] <duflu> Today: 2018-08-09
[10:17] <duflu> It's fate
[10:21] <seb128> hehe
[10:21] <seb128> what package is that?
[10:22] <duflu> seb128, mpv
[10:22] <willcooke> :)
[10:23] <seb128> back to video decoding work? ;)
[10:23] <tseliot> Laney: thanks! :)
[10:24] <duflu> seb128, yeah there are bugs we can soon close. And it's convenient that Debian has jumped to the latest now
[14:48] <seb128> Laney, can you help with gbp? I'm getting confused again :/
[14:49] <seb128> I did "gbp clone pkg-gnome:gnome-bluetooth", downloaded http://ftp.acc.umu.se/pub/gnome/sources/gnome-bluetooth/3.28/gnome-bluetooth-3.28.2.tar.xz and did a gbp import-orig if the tarball
[14:51] <seb128> it seems to have worked but upstream/latest is ahead of 1 commit compared to origin/upstream/latest and seems to be missing the upstream individual commits between .0 and .2
[14:51] <seb128> it feels wrong but I'm unsure what I missed or what didn't work
[14:55] <seb128> hum, maybe I need a -upstream-vcs-tag= since the tags are not standard
[15:03] <seb128> right, that was it
[15:03] <seb128> Laney, unping
[15:11] <Laney> nice
[15:12] <Laney> you can add "upstream-vcs-tag = invalid" or something to debian/gbp.conf, that makes it error instead of not taking the tag at all
[15:13] <seb128> sounds like maybe a good default for pkg-gnome components?
[15:13] <Laney> yeh I think a couple already have it
[15:13] <seb128> (or maybe "good default" at all, unsure how tagging is handled in other projects)
[15:13] <seb128> k, so I can just commit such changes?
[15:13] <Laney> yep
[15:13] <seb128> thx
[15:14] <Laney> might want to check I didn't make it up though
[15:14] <Laney> well I didn't make it up, but that specific line might not be exactly right
[15:15] <seb128> k, I'm going to look for other cases in pkg-gnome and copy what they did to be sure :)
[15:15] <Laney> # Upstream tags in this project are not conveniently named for this
[15:15] <Laney> upstream-vcs-tag = invalid
[15:16] <Laney> gnome-settings-daemon
[15:17] <seb128> thx
[15:17] <seb128> interesting one as well, https://salsa.debian.org/gnome-team/eog/commit/dcb4deb1
[15:17] <seb128> the
[15:17] <seb128> "[import-orig]
[15:17] <seb128> postimport = dch -v%(version)s New upstream release; git add debian/changelog; debcommit
[15:17] <seb128> "
[15:17] <seb128> bit
[15:17] <seb128> I wonder if that should be standard/default as well
[15:18] <Laney> I wouldn't mind it without the debcommit
[15:19]  * Laney likes to add NEWS entries in there
[15:19] <seb128> yeah, I don't think that one is needed
[15:19] <seb128> but dch/add would be nice
[15:19] <Laney> also patch-numbers = False I think would be a good one
[15:19] <seb128> should perhaps be a default in gbp though, I don't know why you wouldn't want to do that
[15:22] <seb128> tkamppeter, the new ghostscript is unhappy on ppc64el, the build seems to stuck on " ./soobj/aux/echogs -e .dev -a- ./soobj/xpswrite -include ./soobj/vector -include ./soobj/libtiff" and get killed after 2 hours, same after a retry now
[15:22] <seb128> that leads to cups/cups-filter/etc to fail to build also on that arch
[15:23] <seb128> which is going to make them block in cosmic-proposed until ghostscript is resolved
[17:08] <Laney> epic yak shaving session is over
[17:09]  * Laney enjoys being on the bleeding edge gnome train again
[17:09] <Laney> night!
[17:11] <seb128> night Laney!
[17:11] <seb128> & well done :)
[18:39] <willcooke> bye bye everyone
[18:39] <willcooke>  /drnick
[21:22] <robert_ancell> ximion, could you upload appstream-glib 0.7.11 to debian? Should be an easy update
[21:23] <robert_ancell> ximion, also should probably discuss if it makes sense to add the developer verified quirk into the AppStream spec
[21:34] <robert_ancell> kenvandine, oh I set up a build server on canonistack for my builds.
[21:34] <robert_ancell> I seem to be getting failures that don't happen on the GNOME builders - did you have to do anything special to set it up?
[21:35] <robert_ancell> Also, I have to add it for every project which is a pain, but I think not possible to work around unless you belong to a group you control.