[06:16] <DaveKong> Anyone know what to do about this error? http://paste.ubuntu.com/17103/
[07:42] <dholbach> good morning
[14:18] <dholbach> hi robilad - how are you doing?
[14:46] <robilad> dholbach: hi!
[14:46] <robilad> fighting to get to inbox zero again ;)
[14:46] <dholbach> I know how you feel :)
[14:48] <dholbach> robilad: how's the java team wiki coming on? :)
[14:49] <robilad> bubling up to the top ;)
[14:49] <dholbach> Rock And Roll :)
[14:50] <robilad> oh, and looks like I'll be back in berlin on 24th, though this time at a sane time. ;)
[14:51] <dholbach> nice, what are you going to do there?
[14:51] <robilad> talk at TU on openjdk
[14:51] <robilad> java on linux, and all that
[14:51] <dholbach> great
[14:51] <dholbach> you can invite people to the Ubuntu Java team at that opportunity :)
[14:52] <robilad> yeah
[14:53] <dholbach> robilad: let me know if you need a hand with it
[14:53] <robilad> sure
[14:54] <dholbach> great
[15:33] <shubuntu> hey anyone alive here
[15:34] <robilad> hi shubuntu
[15:34] <shubuntu> i need a tutorial on proper java comments
[15:34] <shubuntu> like how to write it so that javadoc can be produced that explains everything to the user
[15:41] <shubuntu> hi robilad
[15:41] <shubuntu> sorry didn't see your reply
[15:41] <robilad> otp
[15:41] <shubuntu> i think this room is too dead
[15:41] <shubuntu> lol
[15:43] <shubuntu> any idea where i can get what i'm looking for
[15:43] <persia> shubuntu: It's a very quiet room, but it also has a specialised focus: that of packaging Java applications in Ubuntu.
[15:43] <shubuntu> well don't have a problem with my packaging
[15:44] <shubuntu> it seems to be working fine
[15:44] <shubuntu> I need to produce javadocs
[15:44] <persia> shubuntu: Excellent!  Please let us know if you do encounter any issues with the packaging in the future.
[15:44] <shubuntu> ok
[15:44] <shubuntu> thanks for the concern
[15:44] <shubuntu> :)
[15:45] <shubuntu> do you know why the java room won't let me in?
[15:45] <persia> shubuntu: Have you tried asking about Javadoc in #java?
[15:45] <persia> Are you registered with freenode?
[15:45] <shubuntu> no
[15:45] <shubuntu> what's that
[15:45] <persia> That's why.
[15:46] <shubuntu> http://freenode.net?
[15:46] <persia> shubuntu: Yep.
[15:46] <shubuntu> ok thanks for the help
[15:47] <shubuntu> how do i join lol doesn't have a join button
[16:03] <shubuntu> thanks a lot man, it worked just fine


[07:06] <soee> good morning
[09:28] <lordievader> Good morning.
[11:50] <BluesKaj> Howdy folks
[16:13] <GeoMint> hello. my laptop's wlan0 is down. i have xubuntu 15.04 and i last updated two days ago and it was closed from the update.
[16:14] <GeoMint> i have Qualcomm Atheros AR9485 Wireless Network Adapter
[16:14] <GeoMint> my drivr is ath9k
[16:14] <GeoMint> when i connect wired cable it connects right to my computer.
[16:14] <GeoMint> can you hel me?
[16:14] <GeoMint> help*
[19:33] <sterns> hello, I am attempting to install the new alpha2 ubuntu gnome release.  J
[19:34] <sterns> I'm dealing with the USB boot issue describe here: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1325801
[19:34] <sterns> has this issue been resolved?
[19:45] <trism> sterns: have you tried unetbootin? doesn't look like that issue is resolved, but I've noticed in the past simliar issues creating usbs with usb-creator of newer ubuntus on older ubuntus, but unetbootin almost always works for me
[19:46] <sterns> trism: unetbootin is my tool of choice and that is what I was using.  I'm trying dd method now, and BTW I have confirmed proper checksum.
[19:46] <sterns> I'm using utopic to create the image
[19:48] <sterns> image complete... I'll report back later
[19:49] <elfy> bah not quick enough ... with unetbootin tab then use unetbootindefault and it should boot
[20:00] <BluesKaj_> trism, have you tried dd the image to the usb stick
[20:00] <BluesKaj_> oops sterns rather
[20:01] <BluesKaj_> heh..too late anyway..poor typing skills does it every time :)
[20:05] <BluesKaj_> elfy, someone suggested dd to me the other day and it worked, much faster than unetbootin or usb-creator
[20:05] <elfy> yea - works for me - I just don't like recommending it to people if I'm not sure they'll get syntax right :)
[20:06] <elfy> I did some testing of burning tools yesterday - the gnome-disks one worked every time
[20:12] <BluesKaj_> elfy, understood , but I had a lot more trouble with unetbootin than dd, of the command string has to be correct, but there are plenty of tuts and examples if one googles
[20:12] <elfy> yep
[20:13] <BluesKaj_> of course
[20:56] <sterns> alright... back... the dd method worked properly to create a bootable image from the ISO
[20:57] <sterns> Installation went off without a hitch.


[04:09] <paulmaul24> hello
[04:09] <jrib> paulmaul24: what's the name of your current account?
[04:10] <paulmaul24> paul
[04:10] <jrib> paulmaul24: ok, is "paul" the first account you created?
[04:10] <paulmaul24> yes
[04:10] <jrib> and you unchecked everything for him in the "users and groups" program?
[04:10] <paulmaul24> yea i was trying to imitate the settings under root
[04:10] <paulmaul24> so it was like i was the administrator
[04:11] <jrib> you are the administrator by default
[04:11] <paulmaul24> o
[04:11] <jrib> but now you're not since you unchecked everything :)
[04:11] <paulmaul24> well now im not becus all the boxes r uncheked
[04:11] <paulmaul24> yea lol
[04:11] <jrib> open up a terminal and type 'groups' and press enter
[04:11] <jrib> what is the output?
[04:12] <paulmaul24> paul video netdev lpadmin powerdev
[04:12] <paulmaul24> paul video netdev lpadmin powerdev
[04:12] <paulmaul24> sory for the double
[04:12] <jrib> k, to be able to use 'sudo', you need to be in the admin group, so we'll add you back to that and then you should be able to go to "users and groups" again and check everything again for "paul"
[04:13] <paulmaul24> ok
[04:13] <verb3k_> jrib, following your conversation is really helpful for newbies (like me) thx
[04:13] <jrib> to add "paul" to the "admin" group, you need to: reboot and choose "recovery mode" from the grub menu.  Then enter the command 'adduser paul admin' and reboot
[04:13] <jrib> verb3k_: great, np
[04:14] <paulmaul24> ok thanks ill try it! thanks for all the help jrib
[10:28] <time_travler_ti> how goes it


[03:54] <astroo-> Valve joins the Linux Foundation as it prepares its Linux-powered Steam OS and Steam Machines   http://thenextweb.com/insider/2013/12/04/valve-joins-linux-foundation-prepares-linux-powered-steam-os-steam-machines/
[04:00] <astroo-> ciao pessoal
[21:30] <astroo-> ola pessoal


[00:01] <wallyworld> veebers: that happens and we just create watcher. don't know why we get dropped
[00:02] <veebers> wallyworld: ok. I haven't yet reproed the error you saw in your email, gonna leave things running, go to lunch and see if anything pops up
[00:05] <wallyworld> veebers: the error happens immediately on deploy for me
[01:13] <veebers> wallyworld: do you do anything more than just: juju deploy cs:~veebers/caas-mariadb ?
[01:14] <wallyworld> you need storage
[01:14] <wallyworld> either static pvs or dynaimic
[01:14] <wallyworld> or you can comment out the storage bit to test wothout
[01:15] <wallyworld> edit metadata.yaml
[01:15] <veebers> wallyworld: ah, I commented out storage. So I need to setup storage somehow to repro?
[01:15] <wallyworld> to repro what?
[01:15] <veebers> wallyworld: the error you see in the logs
[01:15] <wallyworld> which one?
[01:15] <wallyworld> there were a couple
[01:16] <veebers> wallyworld: or was your comment about  neededing storage just regarding deploying that charm
[01:16] <wallyworld> yeah, was just about deploying
[01:16] <veebers> wallyworld: There was only one in your email, let me grab it real quick
[01:16] <wallyworld> sorry, haven't got it paged in
[01:16] <veebers> wallyworld: unexpected error: resource name may not be empty
[01:16] <veebers> wallyworld: I can deploy that charm (and others) and see no errors at all :-|
[01:17] <wallyworld> not even this one? ERROR juju.worker.dependency "caas-unit-provisioner" manifold worker returned
[01:17] <wallyworld> unexpected error: resource name may not be empty
[01:17] <veebers> (except for WARNING juju.workers.caasunitprovisioner k8s event watcher closed, restarting which I see every 6-8 minutes)
[01:17] <veebers> wallyworld: nope, none.
[01:17] <wallyworld> hmmm
[01:18] <wallyworld> i'll see if i can reproduce
[01:18] <veebers> juju debug-log -m controller --replay | grep ERROR comes back clean
[01:18] <veebers> wallyworld: oh, which k8s cluster where you using? That shouldn't matter though
[01:18] <wallyworld> k8s deployed on top of aws
[01:22] <kelvinliu> wallyworld, veebers would you take a look this PR when u got time? https://github.com/juju/juju/pull/8997/files  thanks
[01:23] <wallyworld> kelvinliu: the jenkins 2.3 and 2.4 builds work?
[01:25] <veebers> can do
[01:25] <veebers> kelvinliu: the re-run of the unit tests for your test run passed this time around, so the failure seems like an intermittent test not something you're build changes have introed
[01:26] <kelvinliu> wallyworld, i think the build was working fine.
[01:26] <kelvinliu> veebers, awesome!
[01:37] <wallyworld> kelvinliu: i left a few comments
[01:45] <veebers> kelvinliu: once you've fixed the operator image job, do a 'resume build' on the latest 2.3 commit to get a full run through
[01:45] <kelvinliu> veebers, sure
[01:46] <kelvinliu> wallyworld, thanks. looking now
[02:01] <thumper> sweet, my branch merged into develop
[02:01] <thumper> all that 2.4 goodness
[02:02] <thumper> veebers: seems like the merge job for juju/clock is also not talking to github
[02:02] <veebers> thumper: aye, they will all need redeployed
[02:03] <thumper> ok... are you sorting that?
[02:03] <veebers> thumper: I am, I pinged you the PR for the changes, but I'm just going to go ahead and re-deploy it now anyway as that's how I roll
[02:03]  * thumper nods, looking now
[02:04] <veebers> I'm def going to template/use a project those jobs on Friday, those 30-ish files could be 2 files
[02:04] <veebers> thumper: try again now on the clock PR
[02:05] <thumper> veebers: build noticed
[02:05] <veebers> sweet
[02:05] <thumper> I'll wait for that to complete
[02:05] <thumper> (just to be sure)
[02:05] <thumper> then merge
[02:12] <kelvinliu> veebers, http://localhost:18080/view/ci-run/job/ci-run/1004/console  2.3 buildjob is passing
[02:56] <wallyworld> kelvinliu: more dep changes just landed in develop
[02:58] <kelvinliu> wallyworld, yes, I saw thumper 's comments. I m fixing an 2.3 build issue now, but it's not related dep change.
[02:58] <wallyworld> np
[03:42] <kelvinliu> thumper, wallyworld veebers I just sync the toml file from dev branch dependencies.tsv, please a take a look again when u got time, I m going for lunch now, be back soon.
[03:46] <thumper> I trust that the build will fail should we be missing things
[03:57] <jam> hey wpk, nice to see you around
[05:12] <wallyworld> kelvinliu: one thing we will need to do is figure out how to allow people to switch branches, eg git checkout 2.4 will leave the vendor dir in place. and that will mess up the 2.4 build
[05:13] <wallyworld> maybe a make target to move it out of the way / rename. we don't want to have to donload the whole lot again when switch back to devleop
[05:15] <anastasiamac> kelvinliu: veebers: wallyworld: with ^^ in mind, if m working on 2.3 (or 2.4) do i now neeed to run 'make dep' instead of 'godeps -u dependencies.tsv' locally?
[05:16] <wallyworld> anastasiamac: 2.3 and 2.4 will retain use of godeps and you can use via the make target if you want as the makefile is checked in code
[05:17] <wallyworld> the issue is how to move the vendor dir out of the way
[05:17] <anastasiamac> wallyworld: nice. thnx
[05:17] <wallyworld> as that will mess with the 2.3 and 2.4 builds
[05:19] <kelvinliu> wallyworld, the dependencies are cached on local, so rm -rf vendor then run make dep will not be too slow
[05:19] <anastasiamac> wallyworld: i see. m guessing ur saw rog's suggestion in the doc on how to deal with it
[05:21] <kelvinliu> anastasiamac, if u work on 2.3 or 2.4, u can just follow previous workflow, either use make dep/godeps or godeps -u dependencies.tsv
[05:21] <anastasiamac> kelvinliu: yep, got it :)
[05:21] <kelvinliu> anastasiamac, all should be working fine
[05:21] <wallyworld> i haven't seen the doc update yet
[05:22] <kelvinliu> anastasiamac, actually 2.3 2.4 is still using godeps.
[05:23] <anastasiamac> kelvinliu: when u say "still" do u mean, they will keep use it? :D
[05:24] <kelvinliu> anastasiamac, yes. unless we want to migrate 2.3 and 2.4 to dep
[05:25] <anastasiamac> kelvinliu: ack
[05:28] <wallyworld> jam: thumper: so rog has suggested a bash script to move vendor dirs from upstream repos away before doing a build. http://paste.ubuntu.com/p/fVBJXMnbdf/ But that seems rather error prone to me and is working against the grain. I think we are better off just embracing upstream tooling rather than coming up with a workaround to compound the issues with using a homegrown solution. Agree?
[05:30] <jam> wallyworld: so that is 'for everything in $GOPATH hide vendor/ when building and then restore wehn we're done' ?
[05:31] <wallyworld> everyhting in dependencies,tsv
[05:31] <wallyworld> every upstream in there
[05:31] <wallyworld> you may have other stuff in gopath
[05:31] <jam> wallyworld: and this is *instead* of using dep ?
[05:31] <wallyworld> yeah
[05:32] <wallyworld> i thik he's trying to find a workaround to not switch to it
[05:32] <wallyworld> i haven't tried the swrript, i only just noticed it as a comment on the googel doc
[05:36] <wallyworld> i can see though ways thing could mess up, eg you moved the vendor dirs, then updated dependencies.tsv; you can end up with your upstream repos messed up if stuff is removed from dependencies.tsv etc. just more moving parts to go wrong
[05:36] <kelvinliu> veebers, i think the branch check condition issue has been solved. http://localhost:18080/view/ci-run/job/ci-run/1014/  http://localhost:18080/view/ci-run/job/ci-run/1010/
[05:36] <veebers> kelvinliu: ok will check shortly, just truing to get this streams stuff sorted
[05:37] <kelvinliu> veebers, thx
[05:39] <wallyworld> kelvinliu: did you see my question about how we deal with switch branches?
[05:40] <kelvinliu> wallyworld, yes, I did. sorry, I relied to anastasiamac only
[05:40] <kelvinliu> wallyworld,  if u work on 2.3 or 2.4, u can just follow previous workflow, either use make dep/godeps or godeps -u dependencies.tsv
[05:41] <wallyworld> kelvinliu: oh sorry, you included me, i missed it
[05:41] <wallyworld> what i meant was not that
[05:41] <kelvinliu> ah, typo, make godeps but no make dep
[05:41] <wallyworld> but when you git checkout 2.4 branch, the vendir dir will interfere with the build
[05:41] <wallyworld> so it needs to be moved out the way
[05:42] <wallyworld> when you say thinsg are cacheed loally, where is that?
[05:42] <kelvinliu> wallyworld, in this case, we either gitignore vendor in 2.3/2.4 or rm -rf vendor. the dependencies are cached on local, so rm -rf vendor then run make dep will not be too slow
[05:42] <wallyworld> will it really be fast to rm -rf vendor and then later run dep ensure again?
[05:42] <wallyworld> gitignore vedor will not do anything
[05:43] <wallyworld> as the dir will still be there right?
[05:43] <wallyworld> it will just be untracked in git
[05:43] <kelvinliu> wallyworld, ll $GOPATH/pkg/dep
[05:44] <wallyworld> so if that is the case and dep ensure is fast, we need a make target to remove vendor or something
[05:44] <wallyworld> and that will need to be in the 2.3 and 2.4 makefiles
[05:44] <kelvinliu> wallyworld, vendor is just files copied from this cache dir but not git repos. so dep cache the git repos in there to do version ensuring
[05:44] <wallyworld> and we'll need to document that workflow
[05:45] <wallyworld> ok, we were fearful that dep ensure would dowmload everything from upstream
[05:45] <wallyworld> after the vendor dir was removed when swiching to 2.4 and back to develop
[05:48] <kelvinliu> wallyworld, ic. i am thinking currently we need to run make godeps to ensure the correct revisions after switch branches because 2.3 and develop branches could have different dependencies.tsv.
[05:49] <veebers> thumper, wallyworld would you mind giving this a quick eyeball and a +/- 1? This is an update to the scripts jerff uses, and an update to them: http://paste.ubuntu.com/p/vmPJvP2nMx/
[05:50] <wallyworld> kelvinliu: indeed we will and that is what we do now each time. but when switch from develop we will *also* need to move the vendor dir
[05:51] <kelvinliu> wallyworld, if we have vendor gitignored on 2.3, 2.4 and develop branches. it will solve this problem?
[05:51] <wallyworld> how?
[05:51] <wallyworld> gitignore doesn't remove the dir when switch branches does it?
[05:52] <wallyworld> if there's a vendor dir there, it will still be there after git checkout 2.4
[05:52] <kelvinliu> wallyworld, if it's ignored, we don't need remove it
[05:52] <wallyworld> what stops go build from using it?
[05:53] <wallyworld> surely not gitignore?
[05:53] <kelvinliu> wallyworld, ah, u r right..
[05:53] <kelvinliu> wallyworld, unless we commit the vendor, but it would be too big for us
[05:54] <wallyworld> right, hence the suggestion to adjust the make targets for godeps in 2.3 and 2.4 make files to rm -rf vendor
[05:54] <kelvinliu> wallyworld, well, we can just rm -rf vendor in make godeps target
[05:54] <wallyworld> that way the workflow will be the same across all branches
[05:54] <wallyworld> so we'll need a 2.3 and 2.4 PR
[05:55] <wallyworld> the assuption is that dep ensure a second time ia very fast
[05:55] <wallyworld> assuming stuff is cached like you say
[05:55] <kelvinliu> wallyworld, yes, it's fast
[05:55] <veebers> wallyworld, thumper if you have no issues with it I'll push and get hatch to try again (it's late for him and I need to get dinner sorted for the boy :-))
[05:56] <wallyworld> veebers: looks ok at first glance
[05:56] <veebers> actually, this diff now as I sorted out 2 small issues http://paste.ubuntu.com/p/XvMm34HKVF/
[05:56] <veebers> wallyworld: sweet, I'll push it up and try it, if it fails I'll revert it and try again later (tonight or tomorrow)
[05:57] <wallyworld> sgtm, no harm if there's an issue
[05:57] <wallyworld> veebers: you happy that we are good with the dep stuff?
[05:57] <kelvinliu> wallyworld, well, it's fast if we think ~10s is not too slow
[05:58] <wallyworld> that's reasonable, it takes godeps a few seconds sometimes
[05:58] <wallyworld> is that on an SSD?
[05:58] <anastasiamac> could I get a review plz on https://github.com/juju/juju/pull/9035 - tiny check to ensure local charms have hooks at deploy
[05:58] <kelvinliu> wallyworld, yes. half of the time was for dep to figure out the revision to copy to
[05:59] <wallyworld> i can like with 10s personally
[06:00] <anastasiamac> wallyworld: thumper: this PR (9035) will b heading into 2.3 and 2.4 if we can/like
[06:00] <veebers> wallyworld: yep, it looks like kelvinliu has the ci-run bits sorted
[06:01] <wallyworld> ok, gr8 ty
[06:01] <wallyworld> kelvinliu: since it's EOD soon let's land tomorrow so we can get discourse post etc sorted out
[06:01] <wallyworld> and not rush
[06:03] <kelvinliu> wallyworld, yup
[06:07] <wallyworld> anastasiamac: done, ty, IS wil be happy
[06:12] <anastasiamac> wallyworld: re: error and suggestion to build charm... we rarely make suggestions in errors coming from api (which this one is)... and digging in deploy command will be to snow-flaky... so to compromise, we could rename this error to say "poorly built charm:.." instead of "invalid charm:..."
[06:12] <anastasiamac> what do u think?
[06:14] <wallyworld> invalid charm is probaly ok, cause that's what it is
[06:14] <anastasiamac> ack
[06:16] <anastasiamac> i was tossing and turning btw one and the other all day... at the end went with "invalid" coz it felt moer definitive, final almost.. whereas "poorly built" implied "hey, u've tried to built it but did such a bad job of it, we have to b polite here"
[06:16] <wallyworld> inalid works for me
[06:17] <anastasiamac> +1
[06:34] <veebers> wallyworld, thumper: after a couple iterations need to make this change: http://paste.ubuntu.com/p/rsKTJh5XMF/
[06:45] <veebers> wallyworld, thumper FYI the fixes worked, the gui release/streams is sorted
[07:21] <wallyworld> veebers: thank you
[08:17] <naturalblue> Hi Everyone. I asked this question over on #maas but was redirected to ask it here. I hope someone can help.
[08:18] <naturalblue> It's about maas with juju lxds and maas's builtin proxy feature
[08:18] <naturalblue> I have setup maas and juju. I have multiple VLANS and all of them have a gateway address on the maas controller. I have enabled builtin proxy but when I juju deploy an lxd container the proxy settings are not configured and i have to manually enter the lxd and create/add the maas proxy settings into apt.d/proxy.conf file
[08:19] <naturalblue> i have been told that possible juju is not setting the inherited maas proxy setting sent down by maas. Any help would be appreciated.
[08:25] <wallyworld> jam: ^^^^ ? i can't recalloff hand the supported behaviour
[08:26] <jam> naturalblue: juju has model-config for apt-proxy and http-proxy. You need to set them for Juju to set it on the containers it creates. We don't auto-populate the values from maas.
[08:32] <naturalblue> jam: ah i see. What happens if you have some lxds that need 1 proxy because they only have some bindings and others that have different bindings. Is it possible to set and apt-proxy setting to a specific lxd on deployment
[08:35] <jam> naturalblue: we don't support per-machine/per-container proxy settings atm.
[08:38] <naturalblue> jam: so if i have different containers that have different bindings I will need to make manual changes to apt/apt.d/juju-proxy.conf to reflect this. It's not so bad
[08:39] <naturalblue> jam: i last thing. Is there a way to see the network settings for all units in a model. I wish to see if all machines/units/lxds have 1 common binding that i could use in the model-config and circumvent having to change multiple apt config files
[08:51] <jam> naturalblue: juju status --format=yaml I believe lists bindings for applications. But that would be newly introduced in 2.4, IIRC.
[08:52] <naturalblue> i am on 2.4 so i will give it a go
[08:53] <naturalblue> jam: thats a cool command unfortunately it only shows the public-addresses and none of the other. Still handy to have though. Thanks
[09:50] <naturalblue> jam: I added the proxy settings into the model-config and redeployed the lxd units. it passed down the https and ftp into the 95-juju-proxy-settings file but for some reason didn't pass the http setting.
[09:55] <jam> naturalblue: can you give the output of "juju model-config" for me ?
[09:56] <naturalblue> ok
[09:56] <naturalblue> will i paste it here or pastebin
[09:56] <naturalblue> jam: will i paste it here or pastebin
[09:56] <jam> pastebin is good
[09:57] <naturalblue> col
[09:58] <naturalblue> jam: https://pastebin.com/PbpmtTuK
[09:58] <jam> naturalblue: you didn't set apt-http-proxy or http-proxy
[10:00] <naturalblue> theres something not right there. i did set them and when i ran the command earlier it showed them all being set.
[10:01] <naturalblue> that paste also shows that https is not set but it was and has actually been passed down to the lxd containers
[10:02] <naturalblue> i set them using the command "juju model-default apt-http-proxy=http://<IP_ADDRESS>:8000". i did this for apt-http/https as well as juju-http/https
[10:02] <naturalblue> for some reason all the config settings for http & https have gone but the ftp has stayed
[10:04] <naturalblue> i must have ran acommand somewhere that set them back to the default rather than the one i wanted. i am still not sure the difference between juju model-config, juju model-default and juju model-defaults
[10:11] <naturalblue> it would seem that although there are 2 commands juju model-default and juju model-defaults they are both identical in what they do
[10:13] <naturalblue> jam: https://pastebin.com/rTcSL9PT This shows all the settings correct (juju moel-defaults comand) but the other command (juju model-config) only shows the ftp settings
[10:23] <manadart> jam: externalreality approved it yesterday, but I've made some additions. Mind taking another look at https://github.com/juju/juju/pull/9029 ?
[11:32] <jam> manadart: will do
[11:32] <jam> naturalblue: you'll need to "juju model-config --reset apt-https-proxy" etc. The value from model-defaults is snapshotted when the model is created, and only used again if you reset the value
[11:36] <naturalblue> jam: Yeah thanks. I worked it out and removed all the excess proxys using juju model-default --reset juju-http-proxy,juju-ftp-proxy etc
[11:37] <naturalblue> then i redepoyed the model. at first i removed the http-proxy etc instead of the juju-http-proxy but found everything just got stuck on initialising agent, so tried again with http-proxy instead of juju-http-proxy and its working away now. i'll see how it goes
[11:44] <jam> naturalblue: if you set 'juju-http-proxy' then juju will set a JUJU_HTTP_PROXY value for the charms to use, but it *won't* set HTTP_PROXY
[11:45] <jam> naturalblue: its been a discussion since often charms actually need to enable and disable the proxy because NO_PROXY doesn't work the way you would like
[11:45] <jam> (all of the C libs only support exact IP matches, not CIDR, which means you can't just say "don't proxy everything in the local datacenter")
[11:46] <stub> cory_fu: Can we release a charms.reactive update? PostgreSQL charm is failing under trusty, fixed by https://github.com/juju-solutions/charms.reactive/commit/328ae1b2f69f07059b17766a9db0586c3243cc14
[11:47] <stub> I think I can bump the version number and push it to pypi if we are good
[11:51] <stub> I can release just up to my commit if the series upgrade stuff needs more baking
[12:43] <naturalblue> jam: Thanks for the help. Everyday's a schoolday :) It's working now and the deploymets have worked for me. Now to debug the openstack services themselves.
[12:43] <naturalblue> Thanks again
[12:44] <jam> naturalblue: happy to help. I'm glad you got it working.
[12:51] <cory_fu> stub: +1, let's do it
[12:52] <stub> cory_fu: ta. HEAD or just up to that commit?
[12:53] <cory_fu> stub: Up to HEAD, I think.  I don't think the upgrade series flags will affect anyone who doesn't want to start testing them.
[12:54] <cory_fu> stub: Also, you'll want to update the VERSION file and changelog
[12:54] <stub> cory_fu: Shall I call that 'preliminary support for operating system series upgrade'?
[12:54] <stub> (in the changelog)
[12:54] <cory_fu> Yeah, that sounds good
[12:55] <stub> Technically that will be a new feature, so 0.7.0. Or do I get to call this 1.0.0 ?
[12:56] <cory_fu> stub: :)  I'm not really sure why we've been holding off on calling it 1.0.0, other than potentially reserving that for breaking changes.  I'm not averse to making the switch.
[12:57] <cory_fu> stub: Oh, I think layer:basic might be range-pinned to <1.0.0
[12:57] <cory_fu> stub: Nope, it's charms.reactive>=0.1.0,<2.0.0
[12:57] <cory_fu> stub: GTG if you want to pull that trigger.  :)
[12:57] <stub> k
[13:00] <cory_fu> stub: Speaking of layer:basic, did you see my reply to the issue you opened about the import stuff.  Would you like to discuss that further?  I'm still leaning toward it being better than not but if it's causing problems or seems like really bad form, I'd like to try to resolve it
[13:01] <stub> cory_fu: I was going to think further and do some tests.
[13:01] <cory_fu> stub: Ok, sounds good.  Let me know what you find.
[13:01] <stub> cory_fu: I can come up with some rationalizations, but they might just be me not liking stuffing everything into charms.layer in the first place.
[13:02] <stub> cory_fu: I submitted an issue on layer:status, which looks like it is relying on naming convensions, with a way of avoiding that need.
[13:03] <cory_fu> stub: Fair enough.  It suits my mental organizational scheme better but it was always intended as a convention and not a hard rule.
[13:03] <cory_fu> I honestly thought that more people would use external libraries rather than every single layer embedding a small lib.
[13:03] <cory_fu> But I've never done that myself, either, so...
[13:04] <stub> With layers and interfaces requiring separate repos, there is already too much to juggle.
[13:04] <cory_fu> Yeah
[13:04] <stub> And if we could stuff them together in shared repos, you don't need external libraries because they can share code already
[13:05] <stub> So when interface:pgsql can point to a subdir of the pg charm source, I stop needing an external library to share my helpers like the ConnectionString class.
[13:20] <stub> https://github.com/juju-solutions/charms.reactive/pull/187
[13:20] <stub> cory_fu: ^^ (tests pass locally, but I'll see what travis says too)
[13:22]  * stub twiddles formatting
[13:36] <hml> stickupkid: I’m not having issues with localhost and develop:  https://pastebin.canonical.com/p/cbHKgszbz2/
[13:36] <hml> stickupkid: which version of the lxd snap are you using?
[13:36] <drcode> hi all
[13:37] <drcode> I got strange error:  bootstrap.go:538 failed to bootstrap model: cannot start bootstrap instance: unexpected: ServerError: 400 Bad Request
[13:37] <drcode> any idea?
[13:37] <stickupkid> hml: 3.3 as well, i'll restart :p
[13:37] <drcode> I am using MAAS + juju in virtualmachine
[13:38] <drcode> juju command: juju bootstrap maas-cloud maas-cloud-controller --bootstrap-series=bionic
[13:39] <stickupkid> hml: thanks for this, was about to go down a rabbit hole
[13:40] <hml> stickupkid: did a restart work?
[13:40] <stickupkid> hml: i'll do it in a bit
[13:41] <hml> stickupkid: my lxd config has been up and running for a long time, haven’t re-setup since then
[13:42] <stickupkid> hml: k, thaknk
[13:42] <stickupkid> s/thaknk/thanks/
[13:46] <drcode> what I am doing wrong?
[13:48] <drcode> Ce faci?
[13:49] <rick_h_> drcode: try with --debug to see what it's trying to do. That feels like a cloud api call that got told no for some reason
[13:49] <rick_h_> drcode: so we would need more info on what cloud/etc you're doing
[13:50] <drcode> can I past is here?
[13:56] <rick_h_> drcode: I'd suggest using a pastebin like https://paste.ubuntu.com/
[14:09] <drcode> thank you
[14:11] <drcode> https://paste.ubuntu.com/p/G2pZZwn6Rd/
[14:22] <anastasiamac> drcode: is ur maas install configured to have bionic images?
[14:24] <stickupkid> manadart: you got 5 minutes, in about 30 minutes, to pick your brains before end of day for you?
[14:29] <manadart> stickupkid: Sure, just say when.
[14:36] <stickupkid> hml: worked after restart
[14:36] <drcode> I will check it , is it recommanded to use bionic?
[14:36] <hml> stickupkid: nice
[14:37] <drcode> do I need to setup NAT in MAAS , or juju can use MAAS proxy?
[14:39] <anastasiamac> drcode: u r asking for it according to ur msg: [23:38:39] <drcode> juju command: juju bootstrap maas-cloud maas-cloud-controller --bootstrap-series=bionic
[14:39] <drcode> ok
[14:40] <drcode> I think I had problem with NAT
[14:40] <drcode> Can I tell juju to use MAAS proxy?
[14:46] <manadart> hml: I was able to clear the test Neutron model networks in the end; see what you think.
[14:46] <hml> manadart: ack, i’ll take a look
[14:47] <stickupkid> manadart: now? HO?
[14:47] <manadart> stickupkid: Ja.
[20:07] <hml> rick_h_: when you get a chance, i think i have the pr comments resolved if you could pls take a 2nd look.  ty!  https://github.com/juju/juju/pull/9015/commits/462a644b24ab064b4ae9172e328867db428d2d96
[20:07] <rick_h_> hml: cool ty looking
[20:09] <hml> rick_h_: it helped once i stopped the square peg round hole problem  :-)
[20:09] <rick_h_> hml: good to hear
[20:10] <rick_h_> hml: do we still test if the cert is parse-able?
[20:10] <rick_h_> hml: or am I missing that in there?
[20:10] <hml> rick_h_: yes… - it’s checked when the filename is given
[20:11] <hml> rick_h_: pollster now allows a VerifyCertFile to be provided
[20:11] <rick_h_> ah doh, yea right after it's read. missed it
[20:11] <hml> rick_h_: not intuitive just reading the code.  ;-)
[20:12] <rick_h_> hml: it's not bad, I just missed it.
[20:40] <veebers> Morning all o/
[20:42] <hml> veebers: morning
[20:47] <veebers> hey hml o/ hows things this morning (also known as afternoon in some places ;-))
[20:47] <hml> veebers: good.  and u?
[20:48] <veebers> hml: all good, it's a bit cool but have the fire going
[21:51] <thumper> fyi, https://bugs.launchpad.net/juju/+bug/1786099 in 2.4.2 proposed
[21:51] <thumper> I'm aware and looking at it
[21:51] <thumper> it is a bit icky...
[21:51] <thumper> let's just say there is an easy and wrong fix
[22:12] <veebers> kelvinliu__: did you happen to push your ci-run changes up?
[23:00] <thumper> where's wally?
[23:03] <kelvinliu__> veebers, yes
[23:03] <kelvinliu__> veebers, i did
[23:03] <veebers> kelvinliu__: sorry as in merge it to master?
[23:18] <kelvinliu__> veebers, ah, im going to merge if u r happy
[23:23] <veebers> kelvinliu__: yes please
[23:23] <veebers> I'm going to be doing updates to ci-run so don't want to overwrite your changes
[23:23] <kelvinliu__> veebers, do it now, thx
[23:24] <kelvinliu__> veebers, done.
[23:24] <veebers> mean, cheers
[23:41] <wallyworld> thumper: want a teady bear still?
[23:48] <anastasiamac> wallyworld: if thumper does not have ur attention, can i?
[23:49] <wallyworld> guess so
[23:49] <wallyworld> i you insist
[23:49] <anastasiamac> yes, m draging u into a corner.. standup?
[23:49] <wallyworld> ok


[00:01] <Bashing-om> UWN568 up for critique and careful proofreading - trials, tribulations and distractions. Is this what will be ?
[00:41] <Bashing-om> Wild_Man: UWN568 up for critique and careful proofreading - trials, tribulations and distractions. Is this what will be ?
[01:04] <Wild_Man> Looking
[01:05] <guiverc_d> (me too)
[01:17] <guiverc_d> looks good to me Bashing-om   (one [MINOR] word grabbed-me in first summary (commented in gdoc); but its probably just how-i-speak  (local speech patterns rather than what's good english)
[01:19] <Bashing-om> guiverc_d: If a word rubs you wrong - will apply also to others .. lemme looky - see what I can do :)
[08:21] -SwissBot:#ubuntu-news- ::Softpedia:: Linux Kernel 5.0 Officially Released, Here's What's New @ https://news.softpedia.com/news/linux-kernel-5-0-officially-released-here-s-what-s-new-525159.shtml (by Marius Nestor)
[10:14] -SwissBot:#ubuntu-news- ::Softpedia:: New Linux Mint Logo Revealed Alongside Further Updates @ https://news.softpedia.com/news/new-linux-mint-logo-revealed-alongside-further-updates-525163.shtml (by Bogdan Popa, Microsoft News Editor)
[10:46] -SwissBot:#ubuntu-news- ::Security:: Episode 22 @ https://ubuntusecuritypodcast.org/episode-22/
[13:11] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Linux Kernel 5.0 Released, This is What’s New @ https://www.omgubuntu.co.uk/?p=137501 (by Joey Sneddon)
[15:14] -SwissBot:#ubuntu-news- ::Planet:: Marco Trevisan (TreviÃ±o): Protetto: Resource Scale for Fractional Scaling support in GNOME Shell 3.... @ https://blog.3v1n0.net/informatica/linux/gnome-shell-fractional-scaling-in-wayland-landed/
[16:31] -SwissBot:#ubuntu-news- ::Softpedia:: ReactOS 0.4.11 Released with Kernel Improvements, Support for More Windows Apps @ https://news.softpedia.com/news/reactos-0-4-11-released-with-kernel-improvements-support-for-more-windows-apps-525170.shtml (by Marius Nestor)
[18:58] -SwissBot:#ubuntu-news- ::Softpedia:: GNU Linux-Libre 5.0 Kernel Officially Released for Those Who Seek 100% Freedom @ https://news.softpedia.com/news/gnu-linux-libre-5-0-kernel-officially-released-for-those-who-seek-100-freedom-525172.shtml (by Marius Nestor)
[19:44] -SwissBot:#ubuntu-news- ::Softpedia:: Wireshark 3.0 Released as World’s Most Popular Network Protocol Analyzer @ https://news.softpedia.com/news/wireshark-3-0-released-as-world-s-most-popular-network-protocol-analyzer-525173.shtml (by Marius Nestor)
[20:05] <Bashing-om> Pulling "WIP" - Target time to publish: 21:00 GMT.
[21:02] <Bashing-om> M/L is away // doing the forum post next.
[21:05] <Bashing-om> And forum posted .. doing re-directs next.
[21:16] <Bashing-om> ANnnddd --- redirects done. Pending is the social media postings.
[21:30] <guiverc> do you want me to push #568 to fridge?  or do we have a prior offer waiting on 2nd?
[21:31] <Bashing-om> guiverc: Is ready to push to the Fridge, but there is no other second but myself - so far as I know no one has verified the WIKI .
[21:32] <guiverc> for UWN I'll accept you as 2nd Bashing-om ; it's regular & you're a significant team member
[21:33] <guiverc> quick scroll down of wiki & it looks great
[21:33] <Bashing-om> guiverc: I am not aware of anything that would preclude "do it" . I say push and see what happens :)
[21:38] <guiverc> http://fridge.ubuntu.com/2019/03/04/ubuntu-weekly-newsletter-issue-568/    (all looked good)
[21:39] <Bashing-om> guiverc: :))
[21:53] <Bashing-om> guiverc: Can I at this time wipe Gdoc ? start UWN569 ?
[21:55] <guiverc> yep, done tweet & g+ [mewe too], but no code is coming to cell.phone to login to fb (so it alone hasn't been done)
[21:57] <Bashing-om> Well, if no code received - all we can do is try again on fb later ?
[21:59] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu Weekly Newsletter Issue 568 @ http://fridge.ubuntu.com/2019/03/04/ubuntu-weekly-newsletter-issue-568/
[22:10] <guiverc> Sorry I can't do fb (or anything requiring my cell.phone to verify) - it's been disconnected :(   (gotta chase up why; I paid!)
[22:12] <Bashing-om> Anndddd == off and running for UWN569 :D // I have no cell phone and no FB account . I be of no help there .
[22:41] <guiverc> uwn #568 now out on fb  (phone tower work was/is my problem)
[22:53] <Bashing-om> guiverc: :D .. Good man ! Not heard from slidinghorn to post to reddit :(
[23:14] -SwissBot:#ubuntu-news- ::Fridge:: Ubuntu Weekly Newsletter Issue 568 @ http://fridge.ubuntu.com/2019/03/04/ubuntu-weekly-newsletter-issue-568/ (by guiverc)


[08:14] <tepsipakki> cjwatson_: ping, gfxboot
[08:23] <cjwatson_> tepsipakki: pong, at debconf
[08:28] <tepsipakki> cjwatson_: oh :) I just wanted to let you know that I'm offline for the rest of the month, which means that I can't help with tribe-2 :/
[08:37] <cjwatson_> ok, no worries
[11:07] <blackskad> cjwatson: can you confirm that bug #121422 is a duplicate of bug #48732 ?
[11:08] <blackskad> the syslog-errors look pretty much the same (crashing with non-UTF-8 at partition-step)
[11:16] <cjwatson> blackskad: yes
[11:16] <blackskad> ok, thanks, I'll mark it as such
[11:17] <cjwatson> thanks
[11:37] <blackskad> np, I'm glad I can help :)
[11:39] <superm1> cjwatson, ping


[00:06] <kubotu> ::workspace-bugs:: [1299266] Please update kde-workspace to 4.11.8 @ https://bugs.launchpad.net/bugs/1299266 (by Kubuntu IRC Bot)
[07:31] <kubotu> ::workspace-bugs:: [1306890] KDE-Session crashes when configuring positions of multiple monitors @ https://bugs.launchpad.net/bugs/1306890 (by kaefert)
[08:29] <ghostcube> hmm folks, i upgraded on my normal maschine to 14.04 and it seems  the sources.list isnt back uped by do-release-upgrade process
[08:43] <valorie> what do you mean, ghostcube?
[09:02] <lordievader> Good morning.
[09:02] <ghostcube> i just updated by sudo do release upgrade -d from saucy to trusty beta. inside tty2
[09:03] <ghostcube> normally i get an soures.list-distupgrade or backup anywhere so i can see what has been inside the sources liste before the release upgrade
[09:03] <ghostcube> or it just comments old repos
[09:04] <ghostcube> but i noticed after the upgrade i get a standard trusty sources.list with no backup or comments
[09:04] <ghostcube> even the system state backup in /var/log/dist-upgrade doesnt contain a backup
[09:10] <ghostcube> valorie: i get something in main log
[09:10] <ghostcube> maybe this is related? i will pastebin it
[09:11] <valorie> ghostcube: you have to do sudo apt-get update first
[09:11] <valorie> before do-release upgrade
[09:11] <valorie> always update first
[09:13] <ghostcube> i did
[09:13] <ghostcube> ;)
[09:13] <ghostcube> i show you something inside main.log from release upgrade
[09:14] <ghostcube> http://pastie.org/9074749
[09:17] <ghostcube> everything was updated to the latest available packages from saucy.
[09:24] <valorie> I think someone was discussing this earlier, but I thought it was fixed
[09:24] <valorie> sec and I'll find it....
[09:24] <ghostcube> ok
[09:24] <valorie> dang, my scrollback isn't long enough
[09:25] <valorie> you might try `sudo apt-get install -f`
[09:25] <valorie> and see if that forces it though successfully
[09:25] <ghostcube> valorie: hmm the update went well. all dfine except the sources.list was gone
[09:25] <ghostcube> i have a backup made by myself as always
[09:26] <ghostcube> just wanted to notice maybe this isnt wanted this way
[09:26] <valorie> of course not
[09:26] <valorie> I'm just about to go to bed; not sure how you would file a bug about this
[09:26] <ghostcube> oh ok
[09:26] <yofel> please file a bug against update-manager, we don't maintain do-release-upgrade
[09:26] <valorie> perhaps send a note to Kubuntu-devel list?
[09:27] <valorie> oops, listen to yofel who knows of which he speaks
[09:27] <valorie> :-0
[09:27] <ghostcube> :)
[09:27] <valorie> niters all
[09:27] <ghostcube> nite
[09:27] <yofel> nini valorie :)
[09:29] <valorie> :-)
[10:43] <BluesKaj> 'Morning folks
[11:45] <ghostcube> yofel: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1306936
[11:45] <ghostcube> is this ok ? or anything i should add?
[12:55] <ghostcube> heh, apachelogger tested kamoso at home works fine no crash picture ok
[13:05] <soee> shadeslayer: the notifications spam seems to be fixed, but i just did upgrades through muon and after they were finished i get notification that new upgrades are available :)
[13:15] <ahoneybun> hello all
[13:28] <lordievader> Hey ahoneybun, how are you doing?
[13:49] <ahoneybun> lordievader: pretty good
[13:49] <ahoneybun> lordievader: it's my girlfriend and I's 4 years together today
[13:50] <lordievader> Congratulations :)
[13:50] <ahoneybun> thanks :)
[13:56] <kdeuser56> yofel: sorry for last time, please say in the future if you do not want to be pinged / have no time
[13:57] <kdeuser56> guys I am getting a lot of unmet dependencies on trusty only official software sources
[13:57] <kdeuser56> example:
[13:57] <kdeuser56>  libkmediaplayer4-dbgsym : Depends: libkmediaplayer4 (= 4:4.13.0-0ubuntu1) but 4:4.12.97-0ubuntu1 is to be installed
[13:59] <kdeuser56> it seems only -dbgsym packages are affected
[14:01] <kdeuser56> oh does not seem to be kde specific ... lots of other packages are affected as well ... has that something to do with the release soon? are debug packages not built yet ?
[14:06] <lordievader> kdeuser56: Seems to me like it is the other way around, the dbgsym package wants 4.13 while 4.12.97 is installed.
[14:06] <kdeuser56> lordievader: yeah, just noticed :D I meant it the other way around
[14:07] <kdeuser56> lordievader: anyway no newer packages available :-(
[14:07] <kdeuser56> lordievader: and how to create debug symbols before the package is built? :-)
[14:09] <lordievader> No idea, I'm not a devel ;)
[14:16] <seaLne> is anyone else seeing the muon "updates available" icon not going away after updates are installed? happened i think after the icon changed
[14:59] <ScottK> kdeuser56: I'm guessing you are working off of a mirror that's out of date for regular packages (the dbgsym packages aren't mirrored)
[14:59] <ScottK> seaLne: Yes.
[15:00] <kdeuser56> ScottK: which "mirror" is the original?
[15:01] <ScottK> archive.ubuntu.com
[15:01] <ScottK> But even that's a mirror, the master archive isn't publicly visible.
[15:03] <kdeuser56> ScottK: how can I enfore that mirror?
[15:04] <ScottK> In /etc/apt/sources.list change what source you're using, but I actually don't recommend doing it.  The archive is pretty stable now that we're close to release, so it's unlikely to be a problem again.
[15:04] <ScottK> Just wait a bit for your mirror to catch up.
[15:04] <kdeuser56> ScottK: nevermind, I selected main server in muon now
[15:04] <ScottK> OK.
[15:08] <kdeuser56> ScottK: okay I selected main server and I am getting updates now, but where is that setting stored?  /etc/apt/sources.list seems unchanged
[15:09] <ScottK> It could also be in /etc/apt/sources.d (or something like that)
[15:20] <kdeuser56> ScottK: thanks, found it out, its in  /etc/apt/sources.list. I just did not notice the changed urls
[15:20] <kdeuser56> ScottK: how much time is left to the release?
[15:21] <kdeuser56> ScottK: found a last minute bug: muon crashes if you go to "Configure software sources", trigger the drop down and click ok
[15:22] <kdeuser56> (the dropdown in the mirror selection)
[15:22] <kdeuser56> if it does not crash the first time, it will do when doing it again
[18:52] <ScottK> kdeuser56: Release is Thursday, but we probably only have until ~Sunday or Monday to get stuff in.  File a bug on bugs.kde.org.
[18:54] <kdeuser56> ScottK: Isn't muon stuff kubuntu internal?
[18:54] <ScottK> No.  It's a KDE project.
[18:54] <ScottK> We're currently the only user, but Debian plans to take it up as well.
[18:55] <ScottK> There are derivatives that use it as well.
[18:55] <kdeuser56> ScottK: yeah, but upstream wont fix it until monday, so it would be sensible to post it on launchpad ... woudln't it be?
[18:56] <ScottK> No, because the guy that would fix it for us is the upstream guy.
[18:56] <kdeuser56> ScottK: isn't the developer one of the kubuntu guys?
[18:56] <ScottK> I think you've found a significant issue.  I think the update icon always being there is probably even more severe.
[18:57] <ScottK> The original one was, but allee isn't.
[19:04] <kdeuser56> ScottK: sorry for the duplicate questions, my i/o was so high that the process was blocked and the connection timed out
[19:04] <ScottK> No problem.
[19:04] <kdeuser56> ScottK: last message i got was from 20:57
[19:05] <ScottK> The last thing I said was "[14:57:07] <ScottK> The original one was, but allee isn't."
[19:05] <kdeuser56> ScottK: did you get the question where I asked if you could reproduce the problem?
[19:05] <ScottK> No.
[19:05] <ScottK> Last question I got was isn't the developer one of the Kubuntu guys.
[19:05] <kdeuser56> ScottK: okay, could you reproduce the crash?
[19:05] <ScottK> I'm not on a trusty box ATM, so no, but maybe later.
[19:06] <ScottK> Go ahead and file the bug now though.
[19:06] <kdeuser56> ScottK: and the update icon issue is from someone else ...
[19:06] <ScottK> Yes
[19:06] <ScottK> Multiple users have reported it always shows updates available, even when they aren't.
[19:07] <kdeuser56> ScottK: I will report the bug within the next hours ... right now apt-get is working so I can't install the debug symbols
[19:07] <ScottK> OK.
[19:07] <ScottK> Thanks.
[19:08] <kdeuser56> ScottK: or I could report it now but some symbols will be missing
[19:08] <ScottK> No, I'd get the better backtrace first.
[19:08] <kdeuser56> okay
[19:28] <kdeuser56> why does plasma-dataengines-addons-dbgsym install kde-wallpapers? I do not need wallpapers to debug my system :-(
[19:29] <kdeuser56> ScottK: maybe a dependency issue?
[19:38] <ScottK> Presumably.
[19:38] <ScottK> Just install it all and remove what you don't want after.
[19:38] <shadeslayer> ScottK: I can poke apol in real life tomorrow
[19:39] <shadeslayer> I wonder if the pam stuff works
[19:39] <ScottK> shadeslayer: Excellent.  AFAIK it's kdeuser56's crash on sources.list change and the continuous updates icon that really need attention.
[19:39] <shadeslayer> ScottK: ack
[19:39] <shadeslayer> ScottK: added to the top of my TODO for tomorrow
[19:39] <ScottK> Thanks.
[19:39] <shadeslayer> np
[19:39] <shadeslayer> kdeuser56: please also report a bug
[19:40] <shadeslayer> so that I can just point him to the bug report
[19:41] <kdeuser56> shadeslayer: yeah I will do, atm my script which blocks apt-get is still running ... how long are you available on irc, so that I can link you the report?
[19:42] <shadeslayer> another 30 minutes, have to leave for my flight then
[19:43] <kdeuser56> shadeslayer: okay, then I guess I can write you at 10:00 UTC tomorrow ...
[19:43] <shadeslayer> ScottK: you probably won't hear back from me before ~3 CEST btw, which is when I reach the office
[19:43] <shadeslayer> will commence pokery shortly afterward
[19:43] <ScottK> Great.
[19:44] <shadeslayer> I just hope he's attending the KTP sprint
[19:44] <kdeuser56> shadeslayer: will you be reachable at 10:00UTC tomorrow?
[19:44] <shadeslayer> nope
[19:44] <shadeslayer> flight lands at 1415 CEST
[19:45] <shadeslayer> kdeuser56: just leave a message here
[19:45] <shadeslayer> or subscribe me to the bug report
[19:45] <shadeslayer> kdeuser56: rohan AT kde DOT org
[19:46] <kdeuser56> shadeslayer: I will ping you and write you a mail with the bug link as soon as I have it
[19:46] <shadeslayer> kdeuser56: just subscribe me to the bug on bugs.kde.org ;)
[19:46] <shadeslayer> I'll get a email


[16:32] <tyhicks> hello
[16:32] <chrisccoulson> hi :)
[16:32] <mdeslaur> \o
[16:33] <tyhicks> #startmeeting
[16:33] <meetingology> Meeting started Mon Jun 15 16:33:03 2015 UTC.  The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:33] <meetingology> Available commands: action commands idea info link nick
[16:33] <jjohansen> o/
[16:33] <tyhicks> The meeting agenda can be found at:
[16:33] <tyhicks> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:33] <tyhicks> [TOPIC] Announcements
[16:33] <tyhicks> Thanks to LocutusOfBorg for help on security updates for the community supported gnutls28 (LP: #1326779) last week. Your work is very much appreciated and will keep Ubuntu users secure. Great job! :)
[16:33] <tyhicks> [TOPIC] Weekly stand-up report
[16:33] <tyhicks> jdstrand: you're up
[16:34] <jdstrand> hello
[16:34] <jdstrand> I have two embargoed issues I am working on
[16:34] <jdstrand> work planning with tyhicks
[16:34] <jdstrand> if those don't consume all of my time, finally start on seccomp policy regeneration on upgrade
[16:35] <jdstrand> and keep working on security update processes for readonly images
[16:35] <jdstrand> mdeslaur: you're up
[16:35] <mdeslaur> I'm working on wpa updates
[16:35] <mdeslaur> and an embargoed issue
[16:35] <mdeslaur> and will be going down the list after that
[16:35] <mdeslaur> I'm on bug triage this week too
[16:35] <mdeslaur> that's it for me, sbeattie, you're up
[16:36] <sbeattie> I'm on CVE triage this week
[16:37] <sbeattie> The trusty apparmor SRU just needs to be promoted to trusty-updates, I am prodding the SRU team to do that.
[16:37] <tyhicks> nice
[16:38] <sarnold> nice :) thanks!
[16:38] <sbeattie> I'm going to work on the gcc-pie stuff next, while looking at some more of the apparmor patches that have accumulated in the meantime.
[16:38] <sbeattie> And that will probably consume my week
[16:38] <sbeattie> tyhicks: you're up
[16:39] <tyhicks> I'm in the happy place this week
[16:39] <tyhicks> I am working on an embargoed item
[16:39] <tyhicks> I need to finish up my patch update testing and publish those updates
[16:40] <tyhicks> continue apparmor list communications to identify and finish up the final patches for the 2.10 release
[16:40] <tyhicks> that's it for now
[16:40] <tyhicks> jjohansen: you're up
[16:41] <jjohansen> I am going to be finishing up my dconf review and spending some time discussing that
[16:42] <jjohansen> that is dconf apparmor work
[16:42] <jjohansen> I need to do what ever is needed to help push through the caching api patches
[16:43] <jjohansen> I have some revision to do on a couple patches for 2.10
[16:44] <jjohansen> I need to open up the start of the next kernel update cycle
[16:44] <jjohansen> I have the backport for bug 1460152 to finish up and test
[16:46] <jjohansen> I have an apparmor kernel bug (that I have lost atm) to triage
[16:47] <jjohansen> I have a few patches to push out to the kernel team
[16:47] <jjohansen> a small pull request to pull together and send upstream
[16:48] <jjohansen> and then perhaps I can get back to the rest of the upstream cleanup
[16:48] <tyhicks> lots of stuff on your todo list this week
[16:48] <tyhicks> too much, probably
[16:48] <tyhicks> once I get through some of mine, I'll check in to see if I can help out
[16:48] <sbeattie> yeah, just thinking the same.
[16:49] <tyhicks> jjohansen: should I take over the backporting for bug 1460152?
[16:49] <tyhicks> I'm now very familiar with that part of the parser
[16:49] <sarnold> heh
[16:50] <jjohansen> tyhicks: nah, I am basically done with it, there is a bit I need to figure out/verify but was feeling too stupid at 3am this morning. You can review and test if you want
[16:50] <tyhicks> ok
[16:50] <tyhicks> then maybe I can help with the ubuntu kernel pull requests
[16:50] <tyhicks> we'll talk about it later
[16:50] <jjohansen> tyhicks: sure
[16:51] <tyhicks> sarnold: go ahead
[16:51] <sarnold> I'm on community this week; I'm also going to brain-dump what I learned working with canonistack, I think I'm nearing the end of the openstack issues re-triaging, and will return to MIR auditing
[16:51] <sarnold> I'll also try to pick up an apparmor patch review here or there
[16:51] <sarnold> I think that's it for me, chrisccoulson?
[16:52] <mdeslaur> does that mean we're getting openstack updates soon?
[16:52] <chrisccoulson> This week, I'll be spending some time getting through code reviews
[16:53] <tyhicks> mdeslaur: it doesn't
[16:53] <tyhicks> mdeslaur: I think someone else (possibly me) will try to pick them up after the brain dump
[16:54] <chrisccoulson> I'll also be picking off other bugs on https://launchpad.net/oxide/+milestone/branch-1.9, although I'm not sure which ones I'll do this week yet
[16:54] <chrisccoulson> And I also plan to get ubufox in to a reviewable state so that we can get it signed
[16:56] <chrisccoulson> I think that's me done
[16:57] <tyhicks> thanks
[16:57] <tyhicks> [TOPIC] Highlighted packages
[16:57] <tyhicks> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:57] <tyhicks> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:57] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/ltp.html
[16:58] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/libcgi-application-perl.html
[16:58] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/gif2png.html
[16:58] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/openvswitch.html
[16:58] <tyhicks> [TOPIC] Miscellaneous and Questions
[16:58] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/libphp-adodb.html
[16:58] <tyhicks> Does anyone have any other questions or items to discuss?
[17:00] <tyhicks> jdstrand, mdeslaur, sbeattie, jjohansen, sarnold, ChrisCoulson: Thanks!
[17:00] <tyhicks> #endmeeting
[17:00] <meetingology> Meeting ended Mon Jun 15 17:00:23 2015 UTC.
[17:00] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-06-15-16.33.moin.txt
[17:00] <mdeslaur> thanks tyhicks!
[17:00] <sarnold> thanks tyhicks!
[17:00] <sbeattie> tyhicks: thank you!