[19:02] <ibeardslee> morning
[19:38] <AugurNZ|Away> morning Ian
[20:13] <olly> morning
[20:15] <AugurNZ> morning olly
[20:20] <thumper> morning
[20:34] <AugurNZ> morning thumper
[20:36] <AugurNZ> Hey, anybody going to linux.conf.au in Auckland next week, might be interested in an Ubuntu-NZ get-together?
[20:38] <AugurNZ> Even if you're in Auck but not attending LCA, we could meet up somewhere close to the venue.
[20:39] <mwhudson> morning
[20:39] <mwhudson> no LCA for me
[20:50] <hads> morning
[23:49] <thumper> no, not going to LCA either


[03:59] <astroo-> ciao pessoal
[04:20] <astroo-> Attack hitting Apache sites goes mainstream, hacks nginx, Lighttpd, too    http://arstechnica.com/security/2013/05/attack-hitting-apache-sites-goes-mainstream-hacks-nginx-lighttpd-too/
[20:02] <astroo-> ola pessoal


[00:31] <rick_h_> hey jelmer
[00:32] <LaserJock> lifeless: btw, I did a new linux benchmark with hg now too.
[00:35] <jelmer> rick_h_: did you manage to figure out the authentication bits in bzr-svn?
[03:08] <lamalex> has anyone used the bzr addin for monodevelop?
[03:10] <eMxyzptlk> hey guys, is there something similar to svn:externals in bzr?
[03:10] <eMxyzptlk> I've heard of it but donno if it's for real
[03:18] <rick_h__> I use bzr-svn with a project with svn:externals. I just ended up checking out each external locally and ln -s to the externals dir
[03:58]  * Peng branches from a server and is told that the working tree format used on the server is old.
[04:32] <jam> poolie: I'm having some trouble building the source packages for bzr-1.5rc1
[04:32] <jam> I'm following your instructions
[04:33] <jam> though I had to "apt-get install fakeroot" which wasn't mentioned
[04:33] <jam> Anyway, I'll email you, but 1.5rc1 is released, but isn't uploaded to the ppa yet
[04:33] <jam> man, having to create a release for each supported version is a PITA
[04:34] <jam> not to mention multiplying that by the extra packages (bzrtools, etc)
[04:38] <LaserJock> jam: I think the LP guys have a tool to automatically do the the changelog munging, etc. to do multiple release at once
[04:39] <jam> LaserJock: not according to: http://doc.bazaar-vcs.org/bzr.dev/developers/releasing.html#publishing-the-release
[04:40] <jam> anyway, I need to go to sleep now
[04:40] <LaserJock> jam: I mean, I think one of the Canonical guys built a script
[04:49] <beuno> jam, can I help with the packaging?
[04:51] <beuno> jam, I'd happy to work it out and upload
[05:11] <beuno> jam, uploading hardy now
[11:06] <gabees> hello all
[11:07] <gabees> is anyone able tell me why i keep getting errors like this when i try to revert single files, please?
[11:07] <gabees> $ bzr revert -r 51 tasks/views.py
[11:07] <gabees> bzr: ERROR: Permission denied: "/home/gabriel/studiomaker/tasks/views.py/.bzr/branch-format": [Errno 13] Permission denied: u'/home/gabriel/studiomaker/tasks/views.py/.bzr/branch-format'
[11:11] <pygi> file permissions? :D
[11:16] <gabees> nah not at all
[11:17] <gabees> i can just do: bzr revert
[11:17] <gabees> and that will revert loads of files without a problem, only if i single out a file
[11:17] <gabees> see:
[11:17] <gabees> r$ bzr revert
[11:17] <gabees>  M  tasks/models.py
[11:17] <gabees>  M  tasks/templates/task_list.html
[11:17] <gabees>  M  tasks/tests.py
[11:17] <gabees>  M  tasks/views.py
[11:17] <gabees>  M  urls.py
[11:17] <gabees> sorry, shouldn't paste here
[11:18] <gabees> is that because i have version 1.3.1-1?
[11:49] <james_w> gabees: could you please pastebin the output of "bzr -Derror revert tasks/views.py"?
[11:57] <gabees> james_w: sure, just a sec
[11:59] <gabees> james_w: here you are http://dpaste.com/49204/
[11:59] <gabees> quite a lot of stuff in there
[12:00] <james_w> gabees: that does look like a bug, can you please run "bzr info" and tell me what the formats you have are?
[12:02] <gabees> Checkout (format: pack-0.92)
[12:03] <gabees> repository: Packs containing knits without subtree support
[12:04] <gabees> i upgraded from 0.9 to 1.3
[12:04] <gabees> bzr upgrade
[12:04] <gabees> then
[12:04] <gabees> bzr reconcile
[12:04] <gabees> but the reason i upgraded was because i was getting these errors in the first place
[12:05] <james_w> hmm, I can't reproduce in a simple test.
[12:05] <gabees> wih 1.3.1?
[12:05] <gabees> with
[12:05] <Peng> Bazaar 0.9?
[12:05] <Peng> Not 0.90?
[12:05] <gabees> yeah prob 0.90
[12:06] <gabees> it was in gutsy gibbon
[12:06] <gabees> now on hardy heron
[12:06] <Peng> Yeah, 0.90 then.
[12:07] <gabees> and all of a sudden started seeing these errors
[12:07] <gabees> so i thought i'd upgrade bzr
[12:08] <gabees> but ended up upgrading the entire system to hardy just to get bzr 1.3.1 :)
[12:08] <Peng> Haha.
[12:08] <Peng> Well, it's good to upgrade anyway.
[12:08] <Peng> And bzr is totally worth the effort, right? ;)
[12:08] <gabees> yup
[12:08] <gabees> bzr has been so good
[12:09] <gabees> i've got tens of project's source code in bzr
[12:09] <gabees> if you want I can zip up my small branch and send it to you
[12:09] <gabees> then you can test and see what is wrong?
[12:10] <james_w> gabees: if you can do that it would be great. I should just need the .bzr/
[12:11] <james_w> is the code open source?
[12:11] <gabees> well not really
[12:11] <gabees> it's for my work
[12:11] <gabees> but i've hardly started
[12:12] <gabees> if it helps to make bzr better then i don't see any problem :)
[12:13] <gabees> just be a couple of mins, just uploading to our server
[12:15] <james_w> sure, just wondering if I could make it available in a bug report if need be. I should be able to make a small test case out of it, so it shouldn't be an issue.
[12:17] <gabees> mm
[12:17] <gabees> should be ok
[12:19] <gabees> here is the url
[12:19] <gabees> http://dev.pixeco.com?file=bzr-error.tar.bz2
[12:22] <gabees> james_w: did you get that file ok?
[12:24] <james_w> sorry, was in the shower
[12:29] <james_w> echo a >> tasks/views.py && bzr revert tasks/views.py works fine for me here.
[12:29] <james_w> both 1.3.1 and trunk sometime before 1.5
[12:32] <james_w> are you familiar with the python debugger?
[12:33] <james_w> If you set BZR_PDB=1 in your environment you get a debugger at any exceptions, so you could poke around and see if anything is amiss.
[13:02] <gabees> james_w: how come i was getting errors then?
[13:02] <james_w> gabees: I'm not sure, sorry.
[13:03] <gabees> james_w: what OS are you on?
[13:03] <james_w> ah, maybe I do. I was assuming it should'nt probe for that file, but it should
[13:03] <james_w> hardy.
[13:03] <gabees> i just tried your code
[13:03] <gabees> get the same error
[13:03] <gabees> echo a to views.py
[13:04] <gabees> then revert
[13:04] <gabees> however
[13:04] <james_w> is there anything weird about your filesystem? NFS etc?
[13:04] <gabees> a plain old: bzr revert
[13:04] <gabees> works just fine and returns views.py to normal
[13:04] <gabees> james_w: ahhh
[13:04] <gabees> it might just be that
[13:04] <gabees> i'm on HFSPlus
[13:05] <gabees> i have another hardy box on ext3 so i'll try that...
[13:05] <james_w> I think the problem is that it is returning permission denied, rather than ENOENT
[13:09] <gabees> yeah i think so
[13:09] <gabees> i just tried it on the ext3 box
[13:09] <gabees> worked no problems
[13:10] <gabees> although... $ echo a >> tasks/views.py && bzr revert tasks/views.py works fine for me here.
[13:10] <gabees> bzr: ERROR: Path(s) are not versioned: works fine for me here.
[13:10] <gabees> ah yeah
[13:11] <gabees> dumbass me
[13:11] <gabees> r$ echo a >> tasks/views.py && bzr revert tasks/views.py
[13:11] <gabees>  M  tasks/views.py
[15:49] <gabees> james_w: thanks for your help earlier
[15:50] <gabees> I've now reformatted the filesystem from HFSPlus to ext3 and bzr is fine again
[15:50] <gabees> I'm not sure what I will do if I need to boot OS X but I'll cross that bridge when I get to it
[15:59] <james_w> gabees: it's probably a good idea to file a bug, there may be something that can be done to fix it.
[16:00] <james_w> at least it would be documented for others then.
[20:03] <pickscrape> Hi, I'm trying to use bzr send, but when the email pops up there is no diff or bundle attached. Any tips?
[20:04] <pickscrape> I've got one local commit to send (it's for the extmerge plugin)
[20:04] <pickscrape> A thunderbird mail window pops up with the subject set correctly, but that's it. Dunno what I'm missing.
[20:12] <sebp> I want to checkout a repo over http that contains '~' in the url and I get "Connection reset by peer" when using bzr, but opening the site in the browser works fine. Any idea?
[20:15] <trepca> hey
[20:15] <trepca> anyone here uses bzr with emacs ?
[20:16] <trepca> sebp:  show the exact command that you typed
[20:16] <sebp> trepca: bzr branch http://www.gnome.org/~sebp/bzr/python-dvb
[20:18] <trepca> interesting
[20:18] <sebp> is it a bug?
[20:20] <beuno> pickscrape, does: bzr send -o test.patch
[20:20] <beuno> create a patch with the diff?
[20:21] <trepca> looks like or maybe bzr establishes too many connections which server doesn't like
[20:21] <pickscrape> beuno: It creates a file, but there is nothing between #Begin patch and # Begin bundle (though there is data after #Begin bundle)
[20:21] <trepca> in both cases ... probably a bug
[20:22] <pickscrape> Oh, intersting. I just pulled my branch to a different machine, and on there the test patch looks a lot more like it.
[20:23] <beuno> pickscrape, you have to have a branch to compare it against to generate the patch
[20:23] <beuno> so, it would be something like:  bzr branch original_branch; bzr branch original_branch hackish_branch; hack hack; bzr send
[20:23] <pickscrape> Should it not just pick up where I originally branched from, or do you always have to specify that explicitly the first time?
[20:24] <beuno> pickscrape, it should pick up where you branched originally
[20:24] <beuno> but, in case it doesn't, you can specify it manually
[20:24] <sebp> trepca: okay, I file one, thanks
[20:25] <pickscrape> Looks like on the other machine it's doing the right thing with -o
[20:25] <pickscrape> But not when omitting that and bring up the compose email window...
[20:25] <beuno> pickscrape, odd. What version of bzr are you using?
[20:26] <beuno> jam, btw, sorry about overstepping you with the packaging and screwing up...  :/
[20:26] <pickscrape> On this new machine it's 1.5rc1
[20:26] <pickscrape> On the machine which -o doesn't work for it's running 1.4
[20:27] <beuno> pickscrape, can the other machine still access where you branched from?
[20:27] <pickscrape> Not long back I contributed a small change to bzr-svn and send worked brilliantly: it even filled in the To: part for me.
[20:28] <pickscrape> Yes, it's on launchpad (lp:bzr-extmerge)
[20:29] <beuno> pickscrape, and bzr output the URL correctly when you do send "Using saved location:..."?
[20:29] <beuno> have you committed your changes?
[20:29] <pickscrape> Yes, I see my changes at the top of bzr log.
[20:30] <beuno> bzr send -o should be very straight forward, so if it's outputting a blank patch, bzr isn't seeing any changes for some reason...
[20:30] <pickscrape> And when running send I get "Using saved location: lp:bzr-extmerge"
[20:30] <pickscrape> On the 1.5rc1 machine -o *is* producing a sensible patch.
[20:31] <pickscrape> On the other one I think its memorised branches are a bit messed up.
[20:31] <jelmer> pickscrape: maybe send in 1.3 didn't do directory service url expansion yet?
[20:31] <beuno> pickscrape, you might want to try and use an absolute URL instead of the lp: shortcut, just as a test
[20:31] <pickscrape> 1.4
[20:31] <pickscrape> ok
[20:31] <pickscrape> What is meant by 'submit branch' in the bzr info output?
[20:33] <jelmer> the branch bzr send will work against
[20:33] <pickscrape> That explains why -io on my 1.4 machine is producing an empty patch. It's currently set to '.'
[20:35] <pickscrape> Yep, that sorted that problem. So it's just the attachment to email that isn't working now.
[20:35] <lamalex> how do you change what branch bzr submit is set to?
[20:36] <pickscrape> I did bzr send -o test.patch --remember <URL>
[20:36] <lamalex> cool
[20:36] <pickscrape> There's probably a more elegant way though
[20:41] <pickscrape> Oh, I've got it. The problem is xdg-email.
[20:41] <pickscrape> If I put thunderbird into bazaar.conf explicitly it works.
[20:42] <beuno> pickscrape, hrm, that ight be a bug
[20:42] <pickscrape> In the docs I see mention of this helping with thunderbird 1.5, but I'm running 2.
[20:42] <pickscrape> Anything I can do to help debug it?
[20:42] <beuno> you have xdg set to use thunderbird, and it doesn't attach the patch unless you specify it in bazaar.conf>
[20:42] <beuno> ?
[20:43] <beuno> brb
[20:43] <pickscrape> It only works if I specify thunderbird in bazaar.conf. If I explicitly set xdg-email in bazaar.conf it still doesn't work.
[20:45] <pickscrape> Confirmed that this workaround works on both machines.
[20:45] <pickscrape> They're not even the same distro either (1.4 is on gentoo, 1.5 is on Hardy)
[20:51] <alecwh> I just created a patch using bzr: bzr diff. How do I apply the diff/patch to another bzr branch?


[01:36] <Budgie^Smore> OK well that explains why I could use this nick earlier
[04:21] <bdx> =1
[07:03] <kklimonda> how do I change location from which Juju downloads lxc images?
[09:25] <Zic> lazyPower: this RESTARTS column stress me a bit, but since I scaled them 1->5, at least they do not restart at the same time, so no interruption normally... do you have this kind of behavior in your labs? it's the same "spec.containers{dnsmasq}    Warning    Unhealthy    Liveness probe failed: HTTP probe failed with statuscode: 503" error at everytime
[09:25] <Zic> http://paste.ubuntu.com/24012539/
[09:26] <Zic> (oh, I'm not polite today : Hello!)
[10:00] <SimonKLB> im unable to view the charmpage of my unpublished charm in the new charmstore gui
[10:00] <SimonKLB> i can see the charm in my list of charms, but when i click on the "View" button it says "There was a problem while loading the entity details. You could try searching for another charm or bundle or go back."
[14:02] <rick_h> tvansteenburgh: ping
[14:02] <tvansteenburgh> rick_h: yo
[14:02] <rick_h> tvansteenburgh: hey, can I steal a few minutes to talk libjuju usage stuff sometime?
[14:02] <tvansteenburgh> rick_h: yeah sure
[15:23] <lazyPower> Zic - no, my dns container has 4 restarts in 61 days
[15:24] <lazyPower> Zic -  i'll shop it around though see what IS is seeing in their long running deployment
[15:43] <rick_h> tvansteenburgh1: is this a not yet done method then? https://github.com/juju/python-libjuju/blob/master/juju/controller.py#L209
[15:45] <tvansteenburgh1> rick_h: correct
[15:47] <tvansteenburgh> rick_h: if i know someone needs it i'll prioritize it, so you can either file a bug for that, or take a shot at implementing it and post a PR
[15:47] <rick_h> tvansteenburgh: yea, just poking at the facade stuff and will see what I can do ty
[15:56] <Zic> lazyPower: we have 124 pods which is running (if it's tied to the number of pods)
[15:57] <lazyPower> Zic - well i only have 36 running, and only 1 dns pod
[15:58] <lazyPower> Zic - so your deployment volume is much higher. have you been watching the resource utilization of the pod in the dashboard?
[15:58] <lazyPower> is the DNS service using quite a bit of ram? any conntrack table issues in the logs?
[15:58] <lazyPower> Zic - i ask because rimasz found some issues with a competing solutions dns deployment, it filled up the conntrack table and started dropping packets like crazy before the pod itself was terminated due to failing health checks.
[15:59] <lazyPower> that *might* be a similar situation but i doubt it, i would think you'd have found other issues as a symptom if that were the case
[16:25] <Zic> lazyPower: I got some dnsmasq[1]: Maximum number of concurrent DNS queries reached (max: 150) logs that I success to collect directly via `docker logs` (kubectl logs on the kube-dns pod returned nothing)
[16:26] <Zic> it's maybe the problem
[16:51] <lorenzotomasini> Hi *, i am trying to implement a python juju client, but when using the modle.deploy() i get an error:
[16:51] <lorenzotomasini> Exception in thread Thread-6:
[16:51] <lorenzotomasini> Traceback (most recent call last):
[16:51] <lorenzotomasini>   File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
[16:51] <lorenzotomasini>     self.run()
[16:51] <lorenzotomasini>   File "/usr/lib/python3.5/threading.py", line 862, in run
[16:52] <lorenzotomasini> in the doc i found
[16:52] <lorenzotomasini>  :param str to: Placement directive, e.g.::
[16:52] <lorenzotomasini>             '23' - machine 23
[16:52] <lorenzotomasini>             'lxc:7' - new lxc container on machine 7
[16:52] <lorenzotomasini>             '24/lxc/3' - lxc container 3 or machine 24
[16:52] <lorenzotomasini>             If None, a new machine is provisioned.
[16:52] <lorenzotomasini> but actually passing the simple machine number gives me the above error
[16:52] <lorenzotomasini> can somebody give me a hint?
[16:52] <lorenzotomasini> thanks in advance
[16:52] <magicaltrout> tvansteenburgh: -^
[16:54] <tvansteenburgh> lorenzotomasini: can i see your code and the full traceback?
[16:54] <lorenzotomasini> sure
[16:55] <lorenzotomasini> so my code
[16:55] <lorenzotomasini> async def deploy_local_charm(charm_dir_path, application_name, number_of_units, machine_number=None, model=None):
[16:55] <lorenzotomasini>     application = await model.deploy(charm_dir_path,
[16:55] <lorenzotomasini>                                      application_name,
[16:55] <lorenzotomasini>                                      num_units=number_of_units,
[16:55] <lorenzotomasini>                                      to=str(machine_number))
[16:55] <lorenzotomasini>     log.debug("deployed application: %s", application)
[16:55] <lorenzotomasini> and the full stack is:
[16:55] <lorenzotomasini> Traceback (most recent call last):
[16:55] <lorenzotomasini>   File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
[16:55] <lorenzotomasini>     self.run()
[16:55] <lorenzotomasini>   File "/usr/lib/python3.5/threading.py", line 862, in run
[16:55] <lorenzotomasini>     self._target(*self._args, **self._kwargs)
[16:55] <tvansteenburgh> lorenzotomasini: please put it in a pastebin
[16:56] <magicaltrout> ho ho ho
[16:56] <lorenzotomasini> https://p.rrbone.net/paste/F3bTxZTB#Z1bY+UVIQ-t10wSxo5fHIpgaxppO58da3fgBGXUt2w/
[16:57] <tvansteenburgh> lorenzotomasini: okay, and what is the value of machine_number?
[16:57] <lorenzotomasini> 112, int
[16:58] <lorenzotomasini> what should it be?
[16:59] <lorenzotomasini> actually it is a str
[17:00] <petevg> lorenzotomasini, tvansteenburgh: the docstring is dated, and it's my fault. Sorry :-/  You need to pass a list to "to".
[17:00] <petevg> So ['112'] should work.
[17:01] <lorenzotomasini> petevg: i try this thanks
[17:01] <tvansteenburgh> i think it also needs to be parsed
[17:01] <petevg> tvansteenburgh: you're right.
[17:03] <lorenzotomasini> tvansteenburgh: sry my phyton is not really good, how should i parse it?
[17:03] <tvansteenburgh> to=placement.parse(machine_number)
[17:03] <tvansteenburgh> from juju import placement
[17:03] <petevg> lorenzotomasini: your Python isn't at fault. It's a tricky bit of code. (Thank you, tvansteenburgh)
[17:03] <tvansteenburgh> something like that
[17:04] <lorenzotomasini> ah but machine_number still has to be list of string or just str ?
[17:04] <tvansteenburgh> just string, placement.parse will convert it
[17:04] <lorenzotomasini> ok thanks
[17:04] <lorenzotomasini> i'll let you know in some minuts
[17:05] <tvansteenburgh> lorenzotomasini: example here https://github.com/juju/python-libjuju/blob/master/juju/application.py#L91
[17:05] <petevg> tvansteenburgh: I'll submit an update to the docs shortly.
[17:06] <tvansteenburgh> petevg: thanks!
[17:06] <petevg> np
[17:08] <lorenzotomasini> found this
[17:08] <lorenzotomasini> to=placement.parse(str(machine_number))
[17:09] <lorenzotomasini> from juju import placement
[17:10] <lorenzotomasini> tvansteenburgh: I have another question… is there a command in the sdk for executing the "juju add-machine ssh:<ip>" , i was not able to find it
[17:11] <lorenzotomasini> tvansteenburgh: unfortunately the placement did not fix it https://p.rrbone.net/paste/So9PLneL#CsMGASLtg54WhuTbZkR39baUi-Is5bC4aSh8uPTnAyT
[17:12] <tvansteenburgh> lorenzotomasini: re: add-machines https://github.com/juju/python-libjuju/issues/51
[17:12] <tvansteenburgh> lorenzotomasini: need to see your code
[17:13] <lorenzotomasini> tvansteenburgh: https://p.rrbone.net/paste/IVbSnOTe#d7jeohncqjo5SN437DmHLP9A5amB4fKe2VBcoi6udlS
[17:14] <tvansteenburgh> ahhh
[17:16] <tvansteenburgh> to=[dict(scope='#', directive=str(machine_number))]
[17:16] <tvansteenburgh> lorenzotomasini: try that ^
[17:21] <lorenzotomasini> tvansteenburgh: ok now i get a different error but that is my fault
[17:21] <lorenzotomasini> tvansteenburgh: thanks
[17:29] <lorenzotomasini> tvansteenburgh: but…. when i fixed the last error, i got… this one
[17:29] <lorenzotomasini> https://p.rrbone.net/paste/gccTi3Fr#O7+-2oKOX6V2b6L8nzMRsd+6Agbs1nfc1C5FziEimIM
[17:30] <tvansteenburgh> hmm
[17:38] <tvansteenburgh> lorenzotomasini: seems to be a bug
[17:44] <tvansteenburgh> lorenzotomasini: i'll work on a fix for this
[17:47] <lorenzotomasini> tvansteenburgh: ok thanks, will this be included in an official release? if so, any chances of including the #51 github issue fix?
[17:47] <tvansteenburgh> lorenzotomasini: yes and yes
[17:48] <lorenzotomasini> tvansteenburgh: and last and most critical question: when do you think will this be available?
[17:48] <tvansteenburgh> lorenzotomasini: early next week probably
[17:48] <lorenzotomasini> :)
[17:49] <lorenzotomasini> ok thanks
[17:49] <tvansteenburgh> if you want to hack the libjuju source i can tell you how to work around the placement bug in the meantime
[17:50] <lorenzotomasini> yeah sure
[17:51] <tvansteenburgh> lorenzotomasini: comment out these lines https://github.com/juju/python-libjuju/blob/master/juju/model.py#L932-L937
[17:51] <lorenzotomasini> tvansteenburgh: I see a placement-fix branch… is it already fixed there?
[17:52] <tvansteenburgh> lorenzotomasini: no that was just a docstring update
[17:52] <lorenzotomasini> tvansteenburgh: ah ok, if i comment these two lines it will still deploy on the machine i chose right?
[17:52] <tvansteenburgh> lorenzotomasini: yeah, it should
[18:13] <lorenzotomasini> tvansteenburgh: what shoul i put then here? https://github.com/juju/python-libjuju/blob/master/juju/model.py#L1003
[18:14] <lorenzotomasini> placement=to,
[18:14] <tvansteenburgh> yeah
[18:34] <erlon> guys does anyone know where to configure the proxy setting for juju 2.0
[18:34] <erlon> it use to be like this in 1.2.2 'juju set-env'
[18:51] <kwmonroe> erlon: i believe it's 'juju model-config [http|https|no]-proxy=foo'
[18:52] <erlon> kwmonroe: hmm, thanks ill try
[18:53] <kwmonroe> erlon: i also think you can adjust model defaults so that subsequent add-model calls will use your proxy settings:  juju model-defaults *-proxy=foo
[18:54] <kwmonroe> and whilst on the subject, you can see which proxy vars are supported with:  juju model-config | grep proxy
[18:56] <cory_fu> kwmonroe: Hey, when you run java-devenv through cwr-ci, are you getting the "NoneType has no attribute series" error from charm proof still?
[18:57] <kwmonroe> negative cory_fu: http://juju.does-it.net:5000/build_bundle_java_devenv/1/report.html
[19:02] <cory_fu> kwmonroe: ok, thanks
[19:36] <stormmore> are we having fun yet Juju world?
[19:41] <kwmonroe> juju deploy lunch --to belly
[20:54] <stormmore> seriously, this disconnect crap has got to stop, didn't have this issue on windows
[21:37] <cory_fu> kwmonroe: I think you were right to push back on "sleep 10" as a work around for the "unremovable model" issue.  I can reproduce this on the CLI with `juju add-model foo; juju destroy-model -y foo`
[21:37] <cory_fu> Looking for an existing bug now
[21:39] <cory_fu> kwmonroe: https://bugs.launchpad.net/juju/+bug/1635052
[21:39] <mup> Bug #1635052: Destroying model shortly after creation results in endless loop <ci> <destroy-model> <juju:Fix Committed> <juju 2.0:Won't Fix> <juju 2.1:Fix Committed> <https://launchpad.net/bugs/1635052>
[21:58] <kwmonroe> cory_fu: thx for finding a faster repro.  i do loathe "sleep x" as a fix for anything, except insomnia.
[22:04] <cory_fu> kwmonroe: Can you test it on the latest beta?
[22:09] <kwmonroe> cory_fu: is rc2 out?
[22:09] <cory_fu> Not that I'm aware of.  Did you still see this on beta5?
[22:10] <cory_fu> Wait, is rc1 out already?  My snap didn't update
[22:10] <kwmonroe> heh, rc2 is out
[22:10] <kwmonroe> read your mail cory_fu!
[22:10] <cory_fu> ha
[22:10] <cory_fu> I guess I need to switch from --channel=beta to --channel=candidate
[22:29] <kwmonroe> hey cory_fu, looks like this was fixed in rc1.  def fails in 2.0.3, but rc1+ looks ok:  http://paste.ubuntu.com/24016323/
[22:30] <cory_fu> Good to know
[22:31] <kwmonroe> yeah i guess good for you.. now i've got an undestroyable model hanging around.
[22:31] <cory_fu> heh
[22:31] <cory_fu> If it doesn't have any units, it's not really doing any harm.
[22:31] <kwmonroe> it harms my ocd cory_fu
[22:32] <cory_fu> :)
[22:49] <ayan> does anyone here use the go 1.8rc3 package?  if so, how do you get /usr/bin/go to point to the right binary?  update-alternatives doesn't seem to know about it.
[22:58] <stormmore> is it bad that I am using Ansible to boot strap my Juju environment?!?!
[23:04] <kwmonroe> stormmore: you could shake magnets over a hard disk to bootstrap your juju env and i wouldn't be mad.
[23:05] <kwmonroe> (as long as you don't ask for help)
[23:20] <bdx> mbruzek, lazyPower: how can I specify a ssl key/cert for the kube-api-endpoint? It seems I need the fqdn of my kube-api-endpoint to exist in the SANS of my key/cert used on the kube api endpoint (kubernetes-master). The privately signed key/cert from easyrsa give kubernetes gives me  an "untrusted authority" error when trying to register workflows via kube-api-endpoint. I'm trying to specify a publicly signed
[23:20] <bdx> wildcard cert there for my domain, but I think I need to add the kub SANS to it as well, via chain or something. Hoping to try and flesh out what my options are here ....
[23:30] <bdx> oh my ... I just found the work around I think, there is an '--ssl-verify' bool arg that can be fed to deis
[23:31] <bdx> http://paste.ubuntu.com/24016692/
[23:33] <stormmore> kwmonroe, really I am having Ansible bootstrap MaaS as well as Juju since Juju requires an existing controller


[00:23] <melodie> hello!
[00:23] <melodie> strange to see I know a few attendees here
[00:24] <melodie> is the commotion project alive?
[00:27] <melodie> never mind, don't bother


[00:00] <knome> we have that one redirection stuff ticket open
[00:00] <knome> and - note that it's not www.xubuntu.org, it's xubuntu.org :P
[00:00] <pleia2> I know, unrelated discovery
[00:00] <pleia2> oh, hm
[00:00] <knome> but yeah, this is again too server for me to worry about it
[00:01] <pleia2> so www.x.o expired, but x.o is fine
[00:01] <knome> https still isn't default
[00:01] <knome> but xubuntu.com redirects to https
[00:01]  * pleia2 headscratch
[00:01] <knome> www.xubuntu.com redirects to http
[00:01] <pleia2> maybe I just have caching
[00:01] <knome> i think i need to poke them tickets
[00:02] <pleia2> I'll poke around this later and submit something if it's all still broken
[00:02]  * pleia2 adds note to etherpad
[00:04] <knome> updated RT #26794
[00:07] <knome> ok, so what next?
[00:07] <knome> should we figure out the other #lovexubuntu winner?
[00:08] <knome> and the finalists too
[00:09] <pleia2> I put a todo list in the etherpad
[00:09] <knome> i noticed
[00:09] <pleia2> trying to order food now because I haven't eaten recently
[00:09] <knome> mhm
[00:12] <pleia2> almost forgot about council blog post, added to pad
[00:13] <knome> ugh
[00:13] <knome> :)
[00:13] <knome> i'll look into that in a bit
[00:49] <pleia2> anyone find any other 16.10 links? https://xubuntu.org/release/16-10/
[00:50] <pleia2> ah, there's http://news.softpedia.com/news/xubuntu-16-10-released-includes-xfce-packages-built-with-gtk-plus-3-technologies-509273.shtml too
[00:51] <knome> well, there are some results not listed there when you google "xubuntu 16.10 review", but i'm not sure how far that way we are willing to go
[00:51] <knome> wait, no
[00:51] <knome> they are the same review
[00:51] <knome> sigh at aggregating sites
[00:51] <pleia2> heh, yeah
[00:51] <knome> https://www.youtube.com/watch?v=KkWE8ZHacNE
[00:52] <knome> https://www.youtube.com/watch?v=OJ3gT8zcFBk
[00:52] <pleia2> not so keen on videos
[00:52] <knome> well...
[00:53] <knome> that's the media of the day
[00:54] <pleia2> get off my lawn
[00:54] <knome> :)
[00:54] <knome> i think it would be most beneficial to have reviews and links that are useful for the users
[00:54] <knome> but that would mean watching or at least glancing the videos
[00:55] <pleia2> if someone wants to watch one and tells me it's good, I'd consider it
[00:55] <knome> i know
[00:58] <pleia2> alright, these three links are really the only ones I can find
[00:59] <knome> oki
[01:01] <bluesabre> flocculant, thanks for the bug reports (and link to testable file)!
[01:05] <knome> pleia2, just to get it recorded - one thing we considered/discussed about the council article was putting some "human" in it - i still think that'd be a good idea (along with AUA and potential team member interviews/etc)
[01:05] <knome> so if you have an idea what that could be, that would be awesome
[01:05] <pleia2> thanks, I'll think about it
[01:05] <knome> i could then put in my part of it and kick the other council members to do it as well
[01:06] <knome> ok, and now sleepy sleepy
[01:06] <knome> night!
[01:06] <pleia2> night :) thanks!
[01:06] <knome> and thanks to you too for everything :)
[01:06] <knome> -->
[01:17] <pleia2> tweeted about the new Chinese mirrors being added
[03:07] <pleia2> confirmed that we received the dev.xubuntu.org VPS funding from the community fund in December of 2015, so I've placed a new request to cover 2017
[06:22] <flocculant> bluesabre: welcome - I'll ping someone in -desktop bout the totem one - pretty confident if that fixes the one I really care about will too - I know that parole was working prior to gstreamer update
[06:23] <flocculant> pleia2 knome - re community funding - I noticed there are now 2 ubuntu flavours asking for donations outside the normal method, mate and this budgie thing - remind me why we don't?
[06:29] <pleia2> flocculant: I didn't know here was a way outside the normal method
[06:29] <pleia2> german ancestry, I like following the rules :)
[06:30] <flocculant> lol
[06:30] <flocculant> seems like some flavours bend them :p
[06:31] <pleia2> heh
[06:31] <pleia2> what do they do?
[06:32] <pleia2> I've tried going outside the fund entirely and requesting things directly from the hosting companies (got a Linode for ubuntu-us.org that way) but they're being a bit more restrictive these days
[06:32] <pleia2> we're not a non-profit, etc
[06:33] <flocculant> budgie have patreon and paypal options for users to donate, mate do similar, https://ubuntu-mate.org/donate/
[06:33] <pleia2> I'm not willing to put myself at risk legally when it comes to holding funds like that
[06:34] <pleia2> might be easier for someone outside of the US
[06:34] <flocculant> not asking anyone to do that - just mentioning it again :)
[06:34]  * pleia2 nods
[06:37] <flocculant> I guess that would be something that Xubuntu Council should mull over \o/
[06:37] <pleia2> yeah make them do it!
[06:37]  * pleia2 sleep &
[06:37] <flocculant> knome bluesabre ochosi ^^
[06:38] <pleia2> but in the meantime, I did submit the request and it should be fine
[06:38]  * pleia2 goes for real now
[06:45] <flocculant> [1]yup - thanks pleia2
[07:35] <flocculant> bluesabre: mentioned in -desktop
[09:16] <knome> pleia2, http://xubuntu.org/press/
[09:16] <knome> pleia2, uses shortcode
[09:17] <knome> flocculant, ack
[09:18] <knome> pleia2, http://xubuntu.org/press/archive/ too, though i notice the order is wonky
[09:18] <knome> meh :)
[09:18] <knome> oh well, i'll get that fixed for next
[09:29] <knome> http://xubuntu.org/release/16-04/
[09:29] <knome> now with sidebar!
[09:45] <knome> pleia2, please glance at  http://xubuntu.org/?p=4171&preview=true  once you have time and either ACK it or propose/do changes for publishing
[09:54] <knome> bbl
[13:59] <knome> pleia2, was toying a bit with this: http://staging.xubuntu.org/getxubuntu/
[14:15] <knome> pleia2, to clarify, these lists are created automatically with a shortcode, using a internal database of mirrors (with URL templates where we replace the version number)
[14:15] <knome> *an
[14:15] <knome> so creating a new list for a new release is as easy as changing the shortcode
[14:16] <knome> and adding a mirror (or deleting one) is as easy as adding a new post in wordpress
[14:16] <knome> -- then all lists are updated
[14:16] <knome> i also have two checkboxes; active (setting inactive means the mirror is essentially not showing up) and "main"/"not main", which controls whether the mirror in question is shown on the initial list of mirrors
[14:24] <knome> bbl
[16:04] <knome> pleia2, some more work with the release links -> http://staging.xubuntu.org/release/14-04/
[16:05] <knome> pleia2, not completely satisfied with the organization of that yet, maybe i'll hide all direct download links first and only allow them to appear with a click
[16:06] <knome> now sauna, bbl
[17:42] <slickymaster> right knome
[17:43] <slickymaster> that means a need for a thighter watch
[17:45] <knome> slickymaster, watch for what?
[17:46] <flocculant> knome: thighter's
[17:46] <knome> :P
[17:46] <slickymaster> hi knome
[17:46] <slickymaster> the docs main branch
[17:47] <knome> slickymaster, oh right, you're replying to ancient stuff :)
[17:47] <slickymaster> oh wait
[17:47] <knome> but yes, indeed
[17:48] <slickymaster> well, the push rights is just for team members, so forget it
[17:48] <slickymaster> didn't read it all the way through :P
[17:48] <knome> sure, but it still means we don't want to let anybody in who is just starting to contribute
[17:48] <slickymaster> yes
[17:48] <knome> so it is tighter than it's now
[17:48] <slickymaster> hm hm
[17:56] <flocculant> knome: i THOGHT WE'D DONE THAT
[17:56] <flocculant> oops
[17:57] <knome> flocculant, WHAT?
[17:57] <flocculant> the old tracker link
[17:57] <knome> me too
[17:57] <knome> but
[17:57] <knome> that happens :)
[17:57] <flocculant> yup :)
[18:51] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [zesty] r626 Update the tracker description (and more importantly, link) ... (by Pasi Lallinaho)
[18:51] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [zesty] r627 Update the entity file with the new status tracker link.... (by Pasi Lallinaho)
[19:10] <flocculant> I thort we'd done that :D
[19:15] <pleia2> knome: yay for press pages working again, thank you (even if archive ordering is wonky)
[19:18] <knome> pleia2, archive ordering will be fixed in the next upload
[19:18] <knome> pleia2, did you look at the NEW updates on staging?
[19:19] <knome> pleia2, and do you think we want to start using them?
[19:22] <knome> pleia2, ok, so i have another idea, which i literally just figured out i probably want to do
[19:23] <pleia2> not yet, just got back from dr appointment so just settling in
[19:23] <knome> pleia2, add a "Releases" (or sth similar) under "About", working as the "front page" for browsing the releases
[19:23] <knome> pleia2, then move the "About and around" (this is under the Press page now) under "The community"
[19:24] <knome> pleia2, and finally, make the screenshot page work much like the press page; we have the information to sort our screenshots based on releases as well
[19:25] <knome> pleia2, yet another thing is potentially moving FAQ out of the menu structure - it hasn't been updated since august 2014
[19:26] <knome> i'm also kind of playing with the idea to make any and every place we mention a version number a link
[19:26] <knome> with some JS obviously
[19:26] <knome> but that's kind of.. for later
[19:27]  * pleia2 catches up on backscroll first
[19:27] <knome> sure
[19:33] <pleia2> for normal humans the staging getxubuntu site doesn't look much different than the live one
[19:33] <knome> indeed
[19:34] <knome> so look at the mirror downloads section
[19:34] <knome> and press the "full"/"all" links
[19:34] <knome> and you'll notice a big difference
[19:34] <pleia2> ah yeah, no more direct links to FTP/HTTP/Info
[19:35] <knome> yeah
[19:35] <knome> no more FTP to be exact
[19:35] <knome> the big change here is
[19:35] <knome> this is dynamically created
[19:35] <knome> the markup for the new one is simply:
[19:35] <knome> [mirrors release=14-04]
[19:35] <pleia2> does anyone even use ftp to download these?
[19:35] <knome> they can get to that from the info
[19:35] <pleia2> right
[19:35] <knome> the info shows up when you open the full list
[19:35] <knome> but anyway
[19:35]  * pleia2 nods
[19:35] <knome> you like this?
[19:36] <pleia2> yep, it's good
[19:36] <knome> ok
[19:36] <knome> next thing is a release page
[19:36] <knome> eg. http://staging.xubuntu.org/release/14-04/ vs. http://xubuntu.org/release/14-04/
[19:36] <knome> first, forget the sidebar
[19:36] <knome> i just haven't set that up on staging
[19:36] <knome> but on staging, you can see the torrent links
[19:37] <knome> those are new fields that we can insert (and update) per release
[19:37] <pleia2> I liked the new sidebar :)
[19:37] <knome> yes, that will stay
[19:37] <knome> and we have the same direct/mirror downloads list here
[19:37] <pleia2> k
[19:37] <pleia2> yeah, I think this is better
[19:37] <knome> but i'm not sure about how it's presented currently
[19:37] <knome> maybe we should make it a link in the release links section
[19:37] <pleia2> articles and things are great, but I think what most people will want is download info
[19:38] <knome> then when that's clicked, pop up the direct download list
[19:38]  * pleia2 shrugs
[19:38] <knome> alternatively, we could drop the torrent links above the direct downloads like the get xubuntu page
[19:38] <knome> ...but i tried that, and it looked weird without any text around the buttons
[19:39] <pleia2> ah, hm
[19:39] <knome> so maybe the answer is to move the description above the codename etc.
[19:39] <pleia2> perhaps
[19:39] <knome> but yeah, this is totally automatized too
[19:39] <knome> so one more thing you'll notice here is the online doc link
[19:39] <knome> IF WE WANT
[19:40] <knome> i can create a shortcode
[19:40] <knome> that lists all of the non-EOL, non-released releases that have a docs link
[19:40] <knome> think: the help & support page list
[19:40] <knome> http://xubuntu.org/help/ <- the list in the green box
[19:41] <knome> then just s/The supported releases are:/The documentation for supported releases can be found via the following links:/ or stjh
[19:42] <knome> so basically automatize everything that is related to releases - or at least make us update it only once
[19:42] <pleia2> I think that makes sense
[19:42] <knome> yes, good
[19:42] <knome> so i have to write that - np though, it's a trivial piece of code
[19:43] <pleia2> thank you :)
[19:43] <knome> so now that we have this sorted out, what about the new releases main page?
[19:43] <pleia2> which one is that?
[19:43] <knome> none yet
[19:43] <knome> i was thinking: list all non-EOL releases, LTSs first, newest first
[19:43] <knome> at least the release number and codename, maybe the description
[19:43] <knome> and a link to the release page
[19:43] <knome> that might be enough
[19:44] <knome> and that would obviously share the saem sidebar as the release pages
[19:44]  * pleia2 nods
[19:44] <pleia2> sounds good
[19:44] <knome> you probably read the part about the maintenance of mirrors, but it will be super easy after this upload
[19:45] <knome> like, something is down, you can either delete it for good or mark inactive
[19:45] <pleia2> ooh, inactive
[19:45] <knome> and you can check/uncheck mirrors to be shown/not shown on the initial list
[19:45]  * pleia2 nods
[19:45] <knome> that said, we might want to look to make that a little smaller
[19:46] <knome> the new china thing for example, it's only a 100Mbps server
[19:46] <knome> also, do we want to duplicate UK
[19:46] <knome> etc.
[19:46]  * pleia2 nods
[19:46] <knome> but again, that's just checkboxes in wp-admin
[19:47] <pleia2> okie
[19:47] <knome> ok, i'll stitch the not yet done pieces together tonight and then file another ticket to get that up
[19:47] <knome> then we need some initial form work after which we are ready to go
[19:47] <pleia2> no problem
[19:47] <knome> also, i wrote a blog article about this
[19:48] <knome> but since we are moving so fast, i'll update that to say we have it all now rather than "we might have something later"
[19:48] <knome> but you might want to glance at that too as i mentioned ;)
[19:48] <pleia2> I'm on the east coast next week, but I am not actually going to be super busy, still jobless and mostly just going there to hang out and spend evenings with friends+family :)
[19:48] <pleia2> sure
[19:48] <knome> i will literally have this ready your today
[19:49] <pleia2> oh ok
[19:49] <pleia2> I still need to review the council blog post
[19:49] <knome> most of the stuff is ready already on staging
[19:49] <knome> i just wanted your input before pushing to branches
[19:49]  * pleia2 nods
[19:52] <knome> http://staging.xubuntu.org/release/14-04/#show-all
[19:52] <knome> different order
[19:56] <pleia2> that's better, intro first
[20:15] <knome> pleia2, http://staging.xubuntu.org/help/
[20:15] <knome> in production, we bold LTSs, is that needed?
[20:15] <knome> in production, we also list here how long releases are supported. needed?
[20:16] <pleia2> I liked the green
[20:16] <pleia2> no bold though
[20:16] <knome> oh meh :D
[20:16] <knome> you're focusing on the wrong things
[20:16] <knome> the green will be there
[20:17] <pleia2> hehe
[20:17] <pleia2> I like listing how long they are supported, people are ALWAYS confused
[20:17] <knome> oki
[20:17] <pleia2> (because 5 year Ubuntu lts)
[20:17] <knome> i'll figure out how to do that then
[20:18] <pleia2> ty
[20:24] <knome> oki, look now
[20:35]  * pleia2 thumbs up
[20:45] <knome> pleia2, aaand here: http://staging.xubuntu.org/about/releases/
[20:45] <knome> can haz any content between page title and the release blobs
[20:46] <knome> and will have the "releases" sidebar, where you can dump more
[20:46] <pleia2> geez, how many of these releases page do we have
[20:46] <knome> this and one for each release :P
[20:46] <pleia2> well ok :)
[20:47] <pleia2> I guess I was also thinking about the download page
[20:47] <knome> yes
[20:47] <knome> then we have the list on the docs page
[20:47] <knome> but that's useful repetition
[20:47] <knome> besides, download page is still manual
[20:47] <pleia2> agreed, just making sure we don't get out of hand
[20:47] <knome> we don't list two LTSs there for example
[20:47]  * pleia2 nods
[20:47] <knome> no, i think this is really needed because currently it's all just really meh
[20:47] <pleia2> hehe
[20:48] <knome> there's no easy way to discover these pages
[20:48] <knome> the release pages, that is
[20:48] <knome> *i* know how to find them
[20:48] <knome> but it's always meh
[20:48] <knome> (go to blog, find the links in the sidebar)
[20:48] <knome> (yes, that's not where the usual user would look)
[20:48] <pleia2> yeah
[20:49] <knome> http://staging.xubuntu.org/about/releases/
[20:49] <knome> lorem ipsum there just for proving concept
[20:50] <knome> we probably want to say stuff like xubuntu is released every 6 months and lts every 2 years, support lengths, here you can see all of the supported releases
[20:51] <knome> and visit their release pages for lots more
[20:53] <pleia2> yeah, just so long as the text doesn't need updating much
[20:53] <knome> nope
[20:53] <knome> just something generic
[20:58] <knome> huh, deja vu
[20:58] <knome> weird :)
[21:06] <knome> ok, RT ticket filed
[21:06] <knome> screenshot thingy not yet done
[21:06] <knome> but that's minor imo
[21:09]  * pleia2 nods
[21:10] <knome> huh
[21:10] <knome> that was a sprint too
[21:13] <pleia2> what was?
[21:13] <knome> the above ^
[21:13] <pleia2> (lunch arrived, munching and then will for real focus on  council blog post)
[21:14] <knome> :)
[22:50] <pleia2> having a hard time being creative about this council article, though it totally deserves it
[22:53] <knome> feel free to just delete etc
[23:51] <knome> pleia2, still not feeling creative?
[23:52] <pleia2> distracted again :(
[23:56] <pleia2> I think "resolutor" is a made up word
[23:57] <knome> :)
[23:57] <knome> aren't all words made up?
[23:57] <pleia2> yeah, silly humans


[15:44] <balloons> Yes it's odd
[16:57] <Garheade> ahoneybun: who you calling a git?
[18:44] <Garheade> "Just do it"
[18:44] <Garheade> -Nike
[20:56] <DammitJim> when setting up a server, does one need to change the hosts file from <IP_ADDRESS> to the actual static IP address?


[02:11] <maggotbrain> man. on a fresh install of 20.04 (in a VM), adding a ppa via the gui is borked. just hangs and give an internal error. :-(
[02:15] <maggotbrain> and the anti-pattern of prompting for the apt source before prompting for admin creds is not good.
[08:08] -SwissBot:#xubuntu-devel- ::xubuntu-default-settings:: Translate /usr/bin/po/thunar-print.pot in zh_CN @ https://github.com/Xubuntu/xubuntu-default-settings/commit/ffae56c501a53ffd9f8188e0ccfeb1df40822a4b (by transifex-integration)
[08:13] <ochosi> quite the release party ^ ;)
[11:46] <bluesabre> :)
[11:47] <Unit193> Sean! \o/
[11:47] <Unit193> bluesabre: Hey!  I saw you got someone interested in QA!
[11:48] <bluesabre> Unit193: yeah, just got pinged by them and pointed them at some resources.
[11:48] <bluesabre> Yay life! :D
[11:49] <Unit193> Also I should likely look at your doodle. >_<  But as always, late evenings tend to work best.
[12:01] <jphilips> maggotbrain: how exactly did you add a ppa via the gui, as i didn't any any problems doing it when i did it
[13:47] <maggotbrain> via Software * Updates -> Other Software -> Add
[15:38] <jphilips> maggotbrain: on the apt line field, did you simply put in the ppa entry like so - ppa:xuzhen666/dockbarx
[15:45] <maggotbrain> no. "deb http://ppa.launchpad.net/phoerious/keepassxc/ubuntu focal main" it is accepted and shows correctly. Then freezes on the "refreshing software cache" and eventually (~2+ min) crashes with an internal error.
[15:46] <maggotbrain> add-apt-repository from the cli works fine.
[15:49] <maggotbrain> apparently it's a dupe of https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1832057
[16:18] <jphilips> maggotbrain: i remember having problems when it was refreshing the software cache and i didn't import the key file and it looped forever when i tried closing the window.
[16:18] <jphilips> https://docs.xubuntu.org/2004/user/C/managing-applications.html#software-repositories
[16:19] <jphilips> sad that doing it from the GUI isn't as simple as the commandline and the GUI should take you step by step through the correct process to provide a good UX
[16:23] <jphilips> linux mint makes it quite user friendly - https://core0.staticworld.net/images/article/2015/07/add-ppa-to-linux-mint-100594418-orig.png
[16:23] <maggotbrain> yeah sad indeed. This is the 1st time I have done a clean install in a year or two. All of my other xubuntu machines are upgrades.
[20:26] <maggotbrain> and both the bug I linked and its dupe are over a year old.


 http://www.miamiherald.com/news/local/community/miami-dade/article139364838.html
 fish shell … https://fishshell.com/
 Finally, a command … line shell for the 90s
 Seems kinda fishy.
 http://www.androidpolice.com/2017/03/19/deal-alert-colors-lg-watch-style-179-70-100-off-best-buy/
 @KMyers @AdamOutler any reason why a ubuntu server can't hit github?
 http://pastebin.ubuntu.com/24209131/
 Can you nslookup, ping and curl the github?
 Those test DNS, network, and communication.
 Funny thing was I used git clone just fine
 Nslookup and ping work
 Those logs say you can't find a specific revision
 the developer asked if I had a firewall on it
 maybe  a port was closed
 You only gave partial logs.  They aren't enough to tell anything.
 mm alright
 You need to make logs from the command to the finish.


[04:14] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2943 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[04:43] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2943 Diff missing
[07:16] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2936 Diff missing (zesty/virt-manager). Ready to build (yakkety/virt-manager). UNAPPROVED queue (xenial/virt-manager)
[09:10] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Publishing packages
[09:32] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Proposed pocket
[10:11] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2928 Release pocket
[12:19] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2919 Needs rebuild due to burned version number
[13:16] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2923 Generating diffs
[13:17] -queuebot:#ubuntu-ci-eng- cpaelzer, https://bileto.ubuntu.com/#/ticket/2923 Successfully built
[13:25] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2943 Generating diffs
[13:26] -queuebot:#ubuntu-ci-eng- jbicha, https://bileto.ubuntu.com/#/ticket/2943 Successfully built


[12:35] -GitHub[m]12:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2379](https://github.com/MirServer/mir/pull/2379): [ci] add coverage reporting


[00:28] <vieira> is there a fix for meltdown comming out today for linux-hwe-16.04?
[00:29] <TJ-> vieira: no patches for v4.10, you need hwe-16.04-edge (4.13)
[00:29] <vieira> Ok, I just installed linux-virtual-hwe-16.04-edge and rebooted
[00:30] <TJ-> vieira: 4.10 kernel from 17.04 reaches end of life on Jan 13th, so wasn't worth the effort to backport patches
[00:30] <vieira> but have 4.13.0-21-generic
[00:30] <vieira> I think it should be 4.13.0-25.29?
[00:30] <TJ-> vieira: waiting for it to appear in the -security archive
[00:31] <vieira> ahh ok! Thanks :)
[01:13] <keithzg> Over in #ubuntu-server it was mentioned that I should mention this here: unable to boot past the RAM image loading on 4.4.0-108.131, meanwhile 4.4.0-104.127 continues to work fine. CPU is an Intel i5-4670K, motherboard is an ASUS Z87-A.
[01:16] <TJ-> thanks keithzg
[01:17] <TJ-> possibly related Ask Ubuntu, with stack-trace photo: https://askubuntu.com/questions/994067/kernel-panic-after-spectre-meltdown-update-16-04
[01:31] <bjf> keithzg, are you still around?
[01:31] <keithzg> bjf: Yup
[01:31] <Odd_Bloke> bjf: He's been active in... there he is.
[01:32] <bjf> keithzg, ok, may have a new kernel for you to try "soon"
[01:32] <TJ-> bjf: we're hoping keithzg can capture some log messages in the meantime ... got your camera handy, keithzg ?
[01:33] <keithzg> Yup, camera's ready although it's not much to see currently!
[01:33] <TJ-> hehehe, common problem
[01:37] <keithzg> What little I have so far is now at https://photos.app.goo.gl/nqKrJHknd11NuCeO2
[01:39] <TJ-> one last test, try adding "nopti" on that kernel's command line
[01:39] <keithzg> TJ-: I haven't tried adding "debug" yet, should I try both, or just "debug" first, or?
[01:41] <TJ-> keithzg: both, why not!
[01:41] <TJ-> keithzg: it looks like 'debug' on it's own won't capture anything; looks like the kernel's initial setup is failing
[01:42] <keithzg> TJ-: hehe, shall do
[01:47] <bjf> keithzg, sorry, i won't have a new kernel for you to try. please file a bug and them come back here and tell me what the bug id is
[01:47] <keithzg> TJ-: No dice, I just get the loading lines and nothing more.
[01:47] <keithzg> bjf: Fair enough, shall do
[01:48] <TJ-> keithzg: that's with 'nopti' ?
[01:48] <keithzg> TJ-: Yeah.
[01:48] <TJ-> keithzg: hmmmph, that IS strange
[01:48] <keithzg> Well, that *and* debug
[01:49] <keithzg> It's conceivable I don't know what I'm doing with editing GRUB entries on the fly
[01:49] <TJ-> keithzg: which suggests some of the other x86/mm sub-system patches not directly related to the pti patch-set may be implicated
[01:50] <TJ-> keithzg: you're editing the kernel command line via GRUB? pressing E on a highlighted entry, navigate to the line starting "linux ...", add the options towards the end of the line, e.g. " debug nopti" then IMPORTANTLY press Ctrl+X too boot with that change - don't return to the menu to start the entry else changes will be lost
[01:52] <keithzg> TJ-: For whatever reason Ctrl-x just writes x to the editor, so I went with F10 as the alternate option, yeah. But now I'm wondering if there were quotation marks around the whole thing and I didn't notice and put my options outside of them? The much smaller window you get when running GRUB in a non-graphical mode makes things harder to visually parse, heh. I'm just going to try adding nopti to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, regenerate
[01:52] <keithzg> grub, and then try another reboot.
[01:53] <TJ-> keithzg: no quotation marks required when editing the GRUB lines
[01:56] <keithzg> TJ-: Yeah I was just wondering in retrospect. And yeah, I verified that it's definitely trying to boot with that option, and definitely still hanging there. Bug report time!
[01:57] <bjf> keithzg, ok, i will shortly have something for you to try... i'm waiting for LP to complete copying something
[01:59] <bjf> keithzg, https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti
[01:59] <bjf> keithzg, in that ppa there will be "real soon now" a newer 4.4 kernel
[02:00] <bjf> keithzg, it's telling me the kernel is there now
[02:02]  * bjf is stepping away for a bit
[02:03] <keithzg> Well it's a banner day for errors for me, I just tried opening a bug on Launchpad and got Timeout Error ((Error ID: OOPS-809eb4fff20040fcf023ecf9bda0f5d3))
[02:04] <keithzg> bjf: Only newer package I'm seeing is linux-libc-dev?
[02:05] <TJ-> keithzg: maybe the LP server just got it's PTI patches :p
[02:05] <keithzg> TJ-: hah!
[02:06] <bjf> keithzg, 4.4.0-109.132 .. you probably need to pull down the .debs and dpkg -i them
[02:06] <TJ-> see https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/+sourcepub/8710767/+listing-archive-extra 4.4.0-109-132
[02:07] <TJ-> apt-cache policy shows it Candidate: 4.4.0-109.132
[02:09] <keithzg> Hmm, apt-cache policy is still just showing me "<IP_ADDRESS>.113" as the latest for linux-image-generic. Manual .deb time then I guess!
[02:09] <TJ-> keithzg: did you "apt update" ?
[02:09] <TJ-> keithzg: presumably you added the ppa via apt-add-repository ?
[02:09] <keithzg> TJ-: Yes and yes
[02:10] <TJ-> keithzg: strange; I did the update and it shows
[02:10] <TJ-> keithzg: try "apt-cache policy linux-image-4.4.0-109-lowlatency"
[02:11] <keithzg> TJ-: Yeah, I see it there then, as I do too with `apt-cache policy linux-image-4.4.0-109-generic`. I guess it makes sense to just apt install *that*.
[02:12] <keithzg> Although I might need linux-signed-* correspondingly?
[02:13] <TJ-> keithzg: if using Secure Boot, yes.
[02:15] <keithzg> TJ-: I remain unsure, heh, been too long since I set up this server and I don't remember if I disabled that or not. Running `apt install linux-signed-image-4.4.0-109-generic linux-image-extra-4.4.0-109-generic linux-headers-4.4.0-109-generic` to be sure.
[02:20] <keithzg> Installed, lets give this a shot.
[02:25] <keithzg> Booted with 4.4.0-109-generic! That's with "nopti" still on the kernel command line, I'm going to try removing that and seeing if it's still fine.
[02:31] <keithzg> Excellent, that seems to have done the trick. Many thanks, bjf and TJ- :)
[02:32] <TJ-> keithzg: so do we know what was wrong?
[02:33] <keithzg> TJ-: I certainly have no idea, all I know is that the newer kernel packages from the PPA have resulted in everything appearing to be fine now on my system.
[02:34] <TJ-> keithzg: Of course, I'd forgotten you've just updated to the very new build! I'm getting confused with the regression I'm investigating here
[02:35] <keithzg> TJ-: It's a busy time :)
[02:38] <bjf> \o/
[02:38] <bjf> keithzg, thanks!
[02:50] <keithzg> bjf: :)
[02:52] <keithzg> Worth mentioning, I ran into this again on another server, also using an ASUS motherboard (different, however: P8Z77-V LX in this case) and an older Intel CPU (i5-3550).
[02:53] <keithzg> Going to check in a bit if the newer PPA packages fix this one too (it does also reboot fine with the -104 kernel, so odds seem good). First I'm going to pick up a pizza, though, since this may be a long night ;)
[03:23] <bjf> keithzg, we are rushing out the kernel you tested for us
[05:03] <keithzg> bjf: Good to hear :) Hopefully there aren't any more issues lurking!
[07:16] <f_g> TJ-, bjf: that keithzg issue was one I pointed out twice in here already (including the fix), apw said he'll look at it on Monday already :-/ seems like I should have filed an LP bug earlier? I was under the impression that nobody would look at those atm while being busy backporting the huge patch sets.. going forward, I assume LP is the way to go again to report improvements/regressions?
[07:54] <apw> f_g: is that the _ds panic?
[07:55] <f_g> yep
[07:55] <f_g> (I know it's already fixed in the latest 4.4)
[07:56] <apw> if so reporting that here was the right thing, iirc you were going to test if that fix was the fix, and we had people scrambling to test too but positive reports didn't make it in time to hit the first updates
[07:56] <apw> reporting it here was worthwhile
[07:59] <f_g> okay. you're right, I did not explicitly state that it actually fixed the issue, I just pinged a second time about it not yet being applied in the pti branch. I think I just assumed that it would get in in any case since it was an obviously incomplete backport - could have stated it more clearly.
[08:01] <f_g> going ahead, should I file bugs at LP in general, or just for already released kernels? are there any plans for Spectre / IBRS / RETPOLINE / .. already (or ways to contribute to that?)
[08:02] <f_g> (FWIW, we haven't received any other negative feedback, so things are looking good atm)
[08:03] <apw> just bad luck on timing, we were juggling all the series at once
[08:03] <apw> it will be in the next update, and that will soon, we are in free release mode
[08:04] <apw> Spectre is in progress for sure
[08:18] <apw> f_g, oh indeed it looks like there is a build in proposed with that fix right no
[08:18] <apw> w
[08:19] <apw> f_g, and i hear it was already approved for -updates, so it should be there 'soon'
[08:21] <f_g> yes :) we only had to juggle two kernel releases here, and still missed some stuff in the first iteration. that's just how it is ;) gotta catch up on LKML now - if there is anything that can be done from over here regarding Spectre backporting/testing/.. just ping
[08:40] <apw> ack
[11:52]  * ogra didnt notice this channel became +r
[11:53] <ogra> it seems the just released kernel doesnt boot on my desktop ...
[11:53] <ogra> i'm greeted with an oops right after grub loads it
[11:54] <f_g> ogra: which kernel / distro?
[11:54] <ogra> heh, ubuntu 16.04
[11:54] <ogra> 4.4.0-108
[11:55] <f_g> 4.4.0-109 likely fixes it, if the oops looks like https://imgur.com/a/vVbR0
[11:55] <ogra> i had to go back to 4.4.0-104-generic
[11:55] <f_g> see LP#1741934
[11:56] <ogra> ah, i'm just behind one version then
[11:56]  * ogra upgrades
[11:56] <ogra> thx!
[11:59] <acheronuk> apw et al. thanks for the hard work
[12:49]  * alkisg also had an issue with 4.4.0-108 today... 4.4.0-104 booted, but -108 displayed a black screen without even loading the initramfs
[12:50] <alkisg> I solved it by installing the -hwe stack, maybe I should have filed a bug report instead...
[12:55] <apw> alkisg, if you get a chance try -109
[12:55] <alkisg> apw: thanks, if they call me again from that school I will do so
[13:40] <thresh> any known issues with <IP_ADDRESS>.46 linux-image-generic-hwe-16.04 and kernel panics?
[13:46] <apw> thresh: best to just tell us the symptoms you are seeing
[13:52] <thresh> apw, as it's a hetzner server, I have limited visibility (and it seems IP KVM has issues, too).  I'm trying to boot it into rescue now to maybe have more info.
[13:52] <thresh> here's what I got from the support: "But it seems as the server shows no video output anymore (or responds to key strokes) once the boot process is nearly finished and the login promt should show up"
[13:52] <thresh> it's an AMD Ryzen system, too.
[13:53] <thresh> I'm sorry I don't have a lot of info atm, still waiting for it to boot into rescue system.
[13:53] <thresh> And it turns out I dont have a netconsole set up on that server :|
[13:55] <thresh> the kernel version I've got installed is 4.13.0-26.29~16.04.2
[14:38] <thresh> I was able to boot into the rescue system, and there are no logs, sadly.
[14:45] <thresh> changed grub default back to the 4.8.0-56 and system booted up just fine.  I understand that that does not help.
[15:04] <thresh> ok, tried booting back to 4.13.0-26.29~16.04.2, after some kernel initialization it freezes, and goes to "no signal" on KVM again.  Sadly, it seems to early for netconsole to kick in.
[15:05] <thresh> and no panic stack trace on the screen either.
[16:09] <metaphysician> On 16.04, xtables-addons dkms fails to build with the new 4.13 kernel.
[16:10] <thresh> I do have another AMD system locally, although it's AMD Turion(tm) II, not Ryzen.  I'm going to test the upgrades tomorrow.
[16:10] <thresh> (with physical access, too)
[16:24] <sbeattie> thresh: given the 'had to go back to a 4.8 kernel', I'm guessing you hadn't run any of the 4.10 linux-hwe kernels? Do any of the 4.10 linux-hwe kernels work for you? Also you could manually install the linux-hwe-edge 4.13.0-21.24~16.04.1 to try to narrow it down to just being the meltdown/kpti patchset that's breaking things for your hardware.
[16:25] <thresh> sbeattie, yeah, I've been using 4.8.0 since, well, it ran fine for me for quite some time.
[16:25] <thresh> I'm going to try those kernels now.
[16:36] <thresh> sbeattie, linux-image-4.13.0-21-generic=4.13.0-21.24~16.04.1 booted up fine (except did not bring up the network interfaces).
[16:38] <ctennis> sorry for the question if it's already been addressed, but the MeltdownAndSpectre wiki page says the linux-aws kernel version for Xenial is 4.4.0-1047.56 whereas the linked 3522-1 says it is <IP_ADDRESS>7.49.  Any clarity on which is correct?
[16:38] <ctennis> USN-3522-1 that is
[16:41] <sbeattie> thresh: likely need linux-image-extra-4.13.0-21-generic=4.13.0-21.24~16.04.1 too
[16:42] <thresh> yeah, r8169
[16:42] <thresh> but, I guess, that kinda sorta means that kpti patches are the problem
[16:43] <sbeattie> ctennis: <IP_ADDRESS>7.49 is the linux-meta version, which update-manager uses to know to pull in the specific linux-image 4.4.0-1047.56 package.
[16:44] <ctennis> that's seemingly really confusing
[16:45] <sbeattie> (more correctly, linux-meta-aws version, and linux-image-4.4.0-1047-aws)
[16:46] <sbeattie> confusing> a bit yes, but it's what allows you to have multiple kernel images installed so that you can rollback if a specific version fails to work for you.
[16:47] <ctennis> right, it's just the different #s between the two pages
[16:48] <ctennis> I had 1047.49 installed, but it did NOT have 4.4.0-1048.57 with it
[16:48] <ctennis> <IP_ADDRESS>7.49 I mean
[16:48] <ctennis> but just 30 minutes ago it became available, so now i have <IP_ADDRESS>8.50 and the corresponding 4.4.0-1048.57
[16:50] <ctennis> anyway, looks like its sorted now, and I was just in a small window of time between updates
[16:54] <sbeattie> ctennis: uhhhh, it should not be possible to have linux-image-aws <IP_ADDRESS>7.49 installed without also having linux-image-4.4.0-1047-aws (4.4.0-1048.57) installed, as the former has a direct dependency on the latter.
[16:55] <sbeattie> also, to be explicit, both are referred to in USN-3522-1
[16:56] <ctennis> This is what I had about 30 minutes ago: linux-aws is already the newest version (<IP_ADDRESS>7.49)
[16:57] <ctennis> The Meldown page says just says "4.4.0-1047.56"
[16:57] <ctennis> so I recognize maybe that's a different package, but at first glance it looks like...I'm not up to date enough
[17:01] <ctennis> anyway, thanks for the response, and don't worry about me, I just wanted to get clarity.  I still think it's confusing, but it sounds like you're all on top of it.
[17:03] <thresh> well, apparently, linux-image-extra-4.13.0-21-generic=4.13.0-21.24~16.04.1 failed to boot.
[17:03] <thresh> hmmm.
[17:05] <thresh> could be a r8169 which is crashes it, then, too..
[17:14] <jsalisbury> thresh, would it be possible for you to open a launchpad bug?  This will allow allow all this info to be kept together and serachable by others.
[17:14] <thresh> jsalisbury, sure - I'm just trying to single out the exact problem which causes the issue.
[17:15] <jsalisbury> thresh, thanks!  I can work with you on the problem.  Can you post the bug number once you have it?
[17:16] <thresh> yup, but I need to go home soon - will hopefully be able to work on it after a couple of hours.
[17:17] <jsalisbury> thresh, ok, thanks
[17:17] <thresh> the fact that it's on hetzner does not help a lot to debug, too :-(
[17:54] <ricotz> klebers, hi, I noticed that the kernel metapackage for raspi2 depends on linux-firmware which seems not right and linux-firmware-raspi2 would be more fitting
[19:52] <chiluk> is linux-firmware a metapackage that points a linux-firmware-raspi2?
[19:53] <apw> nope