[00:00] <perrito666> cherylj: back
[00:03] <menn0> anastasiamac: i'll address those review comments and get those merged into the feature branch separately. thanks.
[00:03] <anastasiamac> menn0: really? thnx :D
[00:06] <cherylj> hi perrito666, I'm looking at bug 1424069 where juju resolved fails with the error "ERROR unit "ubuntu/0" is not in an error state"
[00:06] <mup> Bug #1424069: juju resolve doesn't recognize error state <regression> <resolved> <juju-core:Triaged by cherylj> <https://launchpad.net/bugs/1424069>
[00:07] <cherylj> and it looks like what is happening, is that when the install hook fails, the Unit Agent status gets set to error
[00:07] <cherylj> but when we try to run juju resolved, it looks at the state of the Unit, not the UnitAgent
[00:07] <perrito666> cherylj: I ffed up that then.
[00:08] <perrito666> cherylj: it should in all cases use unitAgent
[00:08] <perrito666> unit should not be used yet
[00:08] <perrito666> cherylj: that particular behavior seems to be missing a test or it would have failed when I made the change
[00:10] <cherylj> perrito666: did you want to take this bug?  I can help out if you tell me what needs to happen, if you're running low on time :)
[00:12] <perrito666> cherylj: well it deppends is this alreay critical?
[00:12] <cherylj> yes
[00:12] <perrito666> how fun
[00:12] <perrito666> cherylj: what time is it for you?
[00:12] <wallyworld_> we have a couple of days
[00:12] <wallyworld_> 1.23 is not going to be released until thursday most likely
[00:12] <cherylj> perrito666:  7PM
[00:12] <perrito666> cherylj: well its unfair that you are working so late because of me
[00:13] <perrito666> assign it to me
[00:13] <cherylj> perrito666: well it sounds like we have a little bit of time
[00:13] <perrito666> wallyworld_: yes, but his bug is most likely blocking CI
[00:13] <cherylj> perrito666: I do need to put my daughter to bed now, but I can still help out once she's down.
[00:13] <wallyworld_> oh, nothing is in the topic
[00:13] <perrito666> cherylj: could you point me to where you found the general error happening? ill grow some decent test and fix it
[00:14] <perrito666> wallyworld_: its critical, I assume it is locking
[00:14] <cherylj> there's a testcase in the bug
[00:14] <cherylj> which I was able to reproduce easily on my local system
[00:15] <wallyworld_> perrito666: yeah, marked as critical regression, but topic not updated
[00:15] <perrito666> wallyworld_: I believe that is done by hand
[00:15] <wallyworld_> perrito666: it's late for you too, i can pick this up
[00:15] <cherylj> perrito666: I added some logging and found that before the regression, upon the install hook failure, the state of the unit was set to StatusError, so juju resolved worked fine
[00:16] <cherylj> The current behavior is that upon the install hook failure, the UnitAgent status is updated to StatusError (and nothing ever changes with the status of the Unit)
[00:16] <perrito666> cherylj: that is expected behavior
[00:16] <cherylj> But the juju resolved command still gets the status of the Unit to determine whether or not the unit is in an error state
[00:16] <perrito666> the issue seems to be the code checking if unit is broken
[00:16] <cherylj> perrito666: ok
[00:17] <perrito666> cherylj: tx a lot
[00:17] <perrito666> Ill go have dinner and fix it afterwards
[00:17] <cherylj> perrito666: np, let me know if there's anything else I can help with
[00:17] <cherylj> I'll bbl too
[00:22] <wallyworld_> perrito666: i've taken the bug, fixing now
[00:32] <perrito666> wallyworld_: aren't you a nice person?
[00:33] <wallyworld_> perrito666: sometimes :-) it's fixed, including a test, but i'm just looking at any other tests that may be needed
[00:34] <perrito666> wallyworld_: well, that test is going to be very useful on the change that I am practicing now
[00:39] <perrito666> you know the worse part? I need to change that back to unit
[00:39] <wallyworld_> sigh
[01:00] <wallyworld_> axw: a small one to fix blocker http://reviews.vapour.ws/r/1109/
[01:00] <axw> looking
[01:03] <axw> wallyworld_: seems odd that we'd be checking the agent status, rather than the unit status... what's the distinction meant to be?
[01:03] <wallyworld_> axw: agent status is what we check now before any health related work
[01:04] <wallyworld_> moving forward that will change
[01:04] <axw> wallyworld_: I see. can you please add a comment to that effect?
[01:04] <wallyworld_> sure
[01:15] <ericsnow> could I get another pair of eyes on http://reviews.vapour.ws/r/1102/?
[02:34] <axw> anastasiamac wallyworld_: this one is ready for review now - http://reviews.vapour.ws/r/993/
[02:34] <wallyworld_> ok
[02:35] <axw> wallyworld_: I ended up taking out all of the implementation of the storage watching code in this branch, because it was ~2000 LOC all up :)
[02:35] <axw> now about 600
[02:35] <wallyworld_> sure, i may duck out to get lunch and look after
[02:35] <axw> nps
[04:03] <wallyworld_> thumper: why do we have the agents starting in debug mode prior to determining what logging level to use?
[04:05] <thumper> histerical raisins
[04:05] <thumper> wallyworld_: we didn't want to miss important bits at startup
[04:05] <wallyworld_> thumper: thought so. but that means we leak credentials :-(
[04:07] <wallyworld_> we can log apiserver request/response at trace level, but will also liekly need to look to suppress cloud init logging etc
[04:07] <thumper> wallyworld_: here's an idea
[04:07] <thumper> when we write out the service script, we look at the current log level for the juju module
[04:08] <thumper> if it is set to DEBUG or below, we start with that
[04:08] <thumper> otherwise start with INFO
[04:08] <thumper> what this means though
[04:08] <thumper> is that some agents may start with info and some with debug if changes are made during deployment
[04:08] <thumper> the original idea was to have a defined, known starting point that was the same everywhere
[04:08] <thumper> there is no technical reason why it can't be different
[04:09] <wallyworld_> i agree with that - i just wish we din't include credentials
[04:09] <thumper> the original design went for consistency
[04:09] <thumper> we are outputting everything
[04:09] <wallyworld_> the issue is that even if we start with info and then change to debug, we'll still leak
[04:09] <thumper> yes
[04:10] <wallyworld_> so messing with logging levels is only a band aide which is not that effective
[04:10] <thumper> correct
[04:10] <wallyworld_> sigh
[04:10] <wallyworld_> seems like it needs to be done properly
[04:10] <thumper> so... alternative options
[04:10] <thumper> don't write out credentials in the log
[04:11] <davecheney> 15:10 < thumper> don't write out credentials in the log
[04:11] <davecheney> ^ yes, that
[04:11] <thumper> however, since we log all api traffic at debug
[04:11] <thumper> we need to do one of two things:
[04:11] <wallyworld_> we need to be able to strip credentials but easier said than done
[04:11] <thumper> be able to identify the values that are creds
[04:11] <thumper> or not write out all the traffic
[04:12] <wallyworld_> agreed, latter is flawed because sometimes you need all traffic
[04:12] <wallyworld_> without leaking
[04:12] <thumper> for debugging yes, for normal users, no
[04:12] <thumper> I don't think it is feasible to say "we
[04:12] <thumper> "we'll log everything except credentials"
[04:12] <wallyworld_> well, users need it even if they don't know it
[04:12] <thumper> it doesn't make sense
[04:13] <wallyworld_> since users will upload all-machines.log and then expect us to fix their problem
[04:13] <wallyworld_> or we need to turn on debug logging
[04:14] <wallyworld_> so we do need to allow for verbose logging minus secrets
[04:15] <thumper> yep, that's hard
[04:17] <wallyworld_> for now need a quick fix - can log api server requests at trace level
[04:17] <wallyworld_> and look at not dumping cloud init script at startup unless also at trace
[04:18] <wallyworld_> well, can log api server request metadata at debug
[04:18] <wallyworld_> but not contents
[04:21] <thumper> seems like a reasonable approach
[04:22] <wallyworld_> i'll do that
[05:00] <wallyworld_> axw: rb not updating; this one fixes a 1.23 release issue with leaking creds https://github.com/juju/juju/pull/1782
[05:03] <axw> looking
[05:06] <axw> wallyworld_: done
[05:06] <wallyworld_> ty
[06:00] <wallyworld_> axw: i'm off for a bit to go see Wicked, won't be able to look at your latest PRs till later tonight after I get back, or maybe tomorrow morning
[06:00] <axw> wallyworld_: no worries. enjoy :)
[06:01] <axw> no great rush, I've got things to carry on with
[06:01] <wallyworld_> axw: wil do, if you are bored, there's also the storage provisioner one http://reviews.vapour.ws/r/1108/
[06:01] <axw> wallyworld_: sure, I'll finish off this branch then take a look
[06:01] <wallyworld_> no hurry of course :-)
[06:02] <anastasiamac> axw: wallyworld_: i mite be able to look at some of these too :D
[06:02] <axw> anastasiamac: great, thanks
[06:02] <wallyworld_> great
[08:16] <mattyw> morning all
[08:39] <Muntaner> hello devs
[08:39] <Muntaner> I'm trying to use the load balancer charm HAProxy for my charm. I set up everything, but when I try to access to the public IP of the load balancer, I get a 503 Service Unavailable. How can I diagnose my situation?
[08:46] <davecheney> rogpeppe3: oh pooh , you left
[08:46] <rogpeppe3> davecheney: no i didn't
[08:47] <mup> Bug #1430205 was opened: lxc template needs refreshing every 24 hours <juju-core:New> <https://launchpad.net/bugs/1430205>
[08:58] <dooferlad> morning! o/
[09:00] <dimitern> dooferlad, o/
[09:05] <dimitern> dooferlad, I've been reading your kvm notes from yesterday
[09:06] <dimitern> dooferlad, how did that reject rules appear in iptables? from libvirt?
[09:07] <dooferlad> dimitern: I have no idea! I haven't tracked it down yet.
[09:07] <dimitern> dooferlad, also, have you checked the nat table? there should be an SNAT rule
[09:07] <TheMue> morning o/
[09:07] <dimitern> TheMue, o/
[09:07] <dooferlad> TheMue: o/
[09:11] <dooferlad> dimitern: bother, I didn't save those :-( I will get a duplicate environment up and get back to you.
[09:12] <dimitern> dooferlad, cheers
[09:21] <mup> Bug #1430220 was opened: Swift container (but not objects) deleted, bootstrap and destroy-environment fail <juju-core:New> <https://launchpad.net/bugs/1430220>
[09:25] <coreycb> TheMue, do you know the syntax for specifying an action-get key?
[09:31] <TheMue> coreycb: sorry, not directly. would have to look too
[09:32]  * TheMue is looking
[09:32] <coreycb> TheMue, ok np. figured I'd ask you since the other guys are not likely online.
[09:33] <coreycb> I'd tried a few ways based on https://jujucharms.com/docs/authors-charm-actions#action-get but wasn't getting anything back
[09:33] <TheMue> coreycb: yes, it's a bit early
[09:35] <TheMue> coreycb: the example shows a nested variable name. "outfile" and "name" are parts of it. if your "foo" is on the top level it's only "action-get foo".
[09:37] <coreycb> TheMue, ok thanks.  yeah that example's a bit odd since 'name' is never defined as far as I can see.  as an aside, I'm running with an experimental version of juju that has leadership elections so I'm going to try on 1.22-beta5.
[09:40] <TheMue> coreycb: indeed, it doesn't match the actions.yaml shown above. "compression.type" would be a better example.
[09:54] <mup> Bug #1430225 was opened: juju br0/juju-br0 does not observe dhcp mtu settings <juju-core:New> <https://launchpad.net/bugs/1430225>
[10:02] <dimitern> TheMue, standup?
[10:02] <TheMue> dimitern: yes, trying to connect. somehow my browser dislikes me today :(
[10:04] <TheMue> dimitern: aargh, not only the browser, all new connections. will reboot now
[10:11] <mattyw> anastasiamac, excellent questions on your review, thanks very much
[10:36] <mup> Bug #1430245 was opened: Transient error with juju-unit-agent on windows hosts <windows> <juju-core:New> <https://launchpad.net/bugs/1430245>
[10:58] <coreycb> TheMue, ok so I found the issue
[10:58] <TheMue> coreycb: what has it been?
[10:59] <jam> dimitern: ping
[10:59] <dimitern> jam, pong
[11:00] <jam> I'm running into an intermittent failure, that we've tracked down to maybe a network issue
[11:00] <jam> specifically in master
[11:00] <coreycb> I was using 'params:' instead of 'properties:' in actions.yaml.  params doesn't seem to work but properties does.  so maybe the doc just needs an update, not sure.
[11:00] <coreycb> TheMue, ^
[11:00] <jam> if you run: cd worker/uniter/filter
[11:00] <jam> $ time go test -c && for i in `seq 10`; do ./filter.test -gocheck.v -gocheck.f ConfigEvents & sleep 0.01; done
[11:01] <jam> that runs the one test 10 times in parallel
[11:01] <jam> it seems we are getting an extra AddressChanged event
[11:01] <jam> and when you touch the test to remove the line where it sets the address
[11:01] <jam> it starts passing consistently, when we shouldn't be getting *any* events since the address wouldn't have been set
[11:02] <dimitern> jam, I'll have a look
[11:02] <dimitern> jam, which test is failing?
[11:02] <jam> -gocheck.f ConfigEvent
[11:03] <jam> TestConfigEvents and TestInitialAddressEventIgnored both suffer from this
[11:03] <TheMue> coreycb: as I understand it "params" is for the definition parameters (top level), "properties" for their potential additional properties
[11:04] <dimitern> jam, ok, thanks, will let you know if I can reproduce it locally
[11:04] <coreycb> TheMue, that's what the doc seems to say too, but it doesn't appear to be the case
[11:04] <jam> dimitern: you might need to bump up "10" 1-in-10 fails for me here
[11:05] <TheMue> coreycb: oh, have to talk to bodie and jw4 about it. could you pastebin your actions.yaml?
[11:07] <dimitern> jam, so far 2-in-20 failed
[11:07] <dimitern> 3 even
[11:09] <dimitern> now 4
[11:09] <coreycb> TheMue, very basic, this works but if you swap params for properties it didn't work for me  --  http://pastebin.ubuntu.com/
[11:09] <jam> dimitern: right, so often enough that we have a clear problem :)
[11:09] <coreycb> sorry, http://pastebin.ubuntu.com/10573902/
[11:09] <dimitern> jam, it seems to fail twice as frequently here - always with github.com/juju/juju/testing/channel.go:63 - unexpected receive
[11:10] <dimitern> jam, is that the same issue you're seeing?
[11:10] <jam> dimitern: oh, I'm not saying the count, just that it fails regularly. 10 was enough that every attempt failed for me
[11:10] <jam> dimitern: but UnexpectedReceive is the failure
[11:11] <TheMue> coreycb: ok, thanks. will discuss it with bodie and jw4 and come back to you later
[11:11] <coreycb> thanks
[11:11] <dimitern> jam, ok, why do you think it's a network issue?
[11:12] <jam> dimitern: if you comment out the line in the test SetNetworkAddress, the test *passes*, when the test expects nothing to set the address
[11:12] <jam> since it didn't do it
[11:13] <jam> dimitern: the test is exercising the logic that just setting address or just setting charm url doesn't generate an event until the other one occurs
[11:14] <jam> dimitern: now this is a test running in JujuConnSuite, and the SetUpTest is using s.unit.AssignToNewMachine()
[11:14] <jam> so I don't know what that gets running in the background
[11:15] <jam> but apparently we're assigning addresses to the machine being tested
[11:15] <jam> and if it happens at exactly the right moment
[11:15] <dimitern> jam, well, commenting out SetAddresses before starting the watcher papers over the problem I think
[11:15] <jam> we end up with 2 changed events, and the test fails
[11:16] <jam> dimitern: the point is that something in JujuConnSuite is forcing addresses for machines, and the test assumes it isn't, I don't *directly* care about what the fix is, it is just an intermittent test that blocked me landing code because I thought I broke something here
[11:17] <perrito666> morning
[11:17] <TheMue> perrito666: o/
[11:17] <dimitern> jam, right, will dig deeper into it
[11:17] <jam> certainly some sort of "don't touch me" flag here would be nice
[11:17] <jam> I can understand that for most tests maybe we want to set an address because we have to have something to work with
[11:18] <jam> and this particular test was written when nothing was assigned
[11:18] <dimitern> jam, I guess removing setAddresses from there should do the trick
[11:18] <jam> dimitern: so just commenting out SetAddress in the test breaks what the test actually cares about testing
[11:18] <jam> (that we don't fire events until both address and charm url are set)
[11:18] <jam> dimitern: I guess ideally we'd be more decoupled, but it is written using JujuConnSuite, and I don't know we want to rework all of that
[11:19] <jam> dimitern: Just know that TestInitialAddressEventIgnored also runs into this problem
[11:19] <jam> dimitern: https://bugs.launchpad.net/juju-core/+bug/1426394
[11:19] <mup> Bug #1426394: TestConfigEvents random failure <ci> <intermittent-failure> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1426394>
[11:20] <jam> so mgz is seeing it in CI
[11:25] <dimitern> jam, I think the problem is s.machine in that suite is machine 0, which shouldn't be
[11:27] <anastasiamac> mattyw: :D np - m enjoying reading the code! yvm for ur PR :D
[11:28] <mattyw> anastasiamac, I just had one question emailed you about it
[11:39] <jam> dimitern: I don't think the test cares, so if you want to have SetUpSuite create 2 machines, I'm ok with that. Though definitely comment why
[11:47] <anastasiamac> mattyw: is this the comment about returning a valid data when error occurs?
[11:51] <mattyw> anastasiamac, that's the one, I wasn't sure if you were just commenting on expecting action
[11:52] <anastasiamac> mattyw: i liked the 3 part return :D
[11:52] <anastasiamac> mattyw: but in every similar piece of code i've seen, when an error is returned
[11:53] <anastasiamac> mattyw: all other parts are either nil or the most basic "empty" default
[11:53] <anastasiamac> mattyw: whereas you were returning a MeterNotAvailable value...
[11:53] <anastasiamac> mattyw: all i was saying that it jumped at me :)
[11:55] <mattyw> anastasiamac, ah I see
[11:56] <anastasiamac> mattyw: :D
[12:41]  * TheMue steps out for a moment
[12:42] <mup> Bug #1430225 changed: juju br0/juju-br0 does not observe dhcp mtu settings <cts> <juju-core:New> <https://launchpad.net/bugs/1430225>
[12:45] <jam> anyone else upgraded to go 1.4?
[12:45] <jam> go fmt stopped working if you have a symlink in your PWD
[12:46] <jam> and it changed how imports are sorted
[12:46] <jam> :(
[13:16] <dimitern> jam, I found the issue
[13:16] <jam> dimitern: yay
[13:16] <dimitern> jam, as usual in these cases a 1 line change :)
[13:17] <jam> dimitern: all about finding that line and knowing it won't break other expectations
[13:17] <mgz> dimitern: oo, go on, what's the change?
[13:17] <dimitern> jam, can you try it to see if you can still reproduce it? just add seenConfigChange = false after f.outConfig = nil on lin 470
[13:18] <jam> dimitern: that sounds like a very bad change
[13:18] <jam> it means that future address changes won't be notified until config changes again
[13:18] <dimitern> jam, I've successfully run both TestConfigEvents and TestInitialAddressEventIgnored multiple times with seq 50
[13:18] <dimitern> jam, well, the config watcher is getting restarted on setCharm
[13:19] <jam> dimitern: so the code intends to not send the *first* notification until it sees both Config and Address changes, but future changes to either should always trigger a change.
[13:19] <dimitern> jam, and that's not accounted for in the maybePrepareConfigEvent
[13:19] <dimitern> jam, not quite
[13:20] <dimitern> jam, if the config watcher was restarted, we *always* get the initial empty event
[13:22] <jam> dimitern: but if we just did setCharm is it actually wrong to say the config changed?
[13:23] <dimitern> jam, well another disturbing thing is the configChanges chan gets reset to the newly started configw.Changes() after it gets started
[13:24] <dimitern> jam, (again in setCharm event handling), so there's a possibility of a race reading from the old configChanges while configw is getting restarted
[13:26] <dimitern> jam, this might be the other missing piece, as running all tests 50 times in parallel I only got 3 failures - now trying with that additional fix - adding configChanges = nil; seenConfigChange = false just after "changing charm to %q"
[13:28]  * dimitern 's machine is visibly lagging when running 50 instances of the filter tests in parallel
[13:28] <jam> dimitern: well I believe that is also running 50 mongod instances in parallel
[13:29] <dimitern> yeah :)
[13:30] <dimitern> jam, ok, so only 2 failures now - both in TestGetMeterStatus
[13:36] <dimitern> jam, correction - TestMeterStatusEvents
[13:38] <dimitern> jam, with seq 20 I can't reproduce it, and since my machine was under quite a load and I can see in the log just before "timeout waiting for receive" that the meter status was indeed sent
[13:39] <dimitern> jam, I'd attribute that these failures to heavy lagging under load
[13:40] <jam> dimitern: if it is just ShortWait sort of timeout, that would be ok
[13:40] <jam> depends on the failure
[13:41] <dimitern> jam, it is a LongWait I think, but I'm running the tests a few more times
[13:47] <dimitern> jam, ok, now 1 failure out of 50 for all tests - this time TestActionEvents and it *is* a ShortWait
[13:48] <jam> dimitern: so the change sounds good given the testing we have in place, but I wouldn't be surprised if our testing wasn't actually as complete as we would like. So this is something that we'd want to think through well. Possibly running past fwereade
[13:49] <dimitern> jam, ok, so far we've established I believe it's not a networking issue but a watcher/race sort of thing; I'll propose a fix with those few lines added and provide a way to test it using your snippet
[13:49] <dimitern> jam, I'd
[13:50] <dimitern> jam, (really bad lag!)
[13:50] <dimitern> jam, I'd ask you to retry reproducing it with the fix
[13:51] <jam> dimitern: I'm certainly willing to try it. My concern isn't that it doesn't fix what I saw, but if it breaks other expectations
[13:52] <dimitern> jam, agreed, I'll ask fwereade to have a look as well
[13:54] <alexisb> all we have a critical bug blocking 1.22, I need some volunteers:
[13:54] <alexisb> https://bugs.launchpad.net/juju-core/+bug/1430049
[13:54] <mup> Bug #1430049: unit "ceph/0" is not assigned to a machine when deploying with juju 1.22-beta5 <oil> <juju-core:Triaged> <https://launchpad.net/bugs/1430049>
[13:55] <alexisb> wallyworld_, has done initial investigation but it will require some f2f time with jhobbs in US hours
[13:57] <dimitern> dooferlad, TheMue, voidspace, guys, I'd appreciate if some of you could join the maas+juju interlock in 2 minutes
[13:57] <mgz> gsamfira: bug 1430340
[13:57] <mup> Bug #1430340: Failing to create tempdir in tests on windows <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1430340>
[13:57] <gsamfira> mgz: thanks :D
[13:58] <gsamfira> grabbing a coffee and looking
[13:58] <dooferlad> dimitern: on it
[13:58] <dimitern> dooferlad, cheers!
[13:58] <voidspace> dimitern: yep, just grabbing coffee
[13:59] <dimitern> voidspace, ta!
[14:00] <mup> Bug #1430340 was opened: Failing to create tempdir in tests on windows <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1430340>
[14:00] <mgz> gsamfira: for interest, the fix I'd made previously was https://github.com/juju/testing/pull/52 for IsolationSuite usage in juju, making sure we actually passed all the windows variables through to subprocesses regardless of case
[14:02] <gsamfira> cool! Windows does not realy care about case, but I remember doing case insensitive match when I pushed this. Might be mistaken though
[14:02] <gsamfira> be roght back
[14:02] <gsamfira> *right
[14:06] <wwitzel3> perrito666: ping
[14:09] <perrito666> wwitzel3: pong
[14:09] <perrito666> wasnt me
[14:11] <perrito666> wwitzel3: ahh dst
[14:11] <wwitzel3> perrito666: standup
[14:12] <perrito666> wwitzel3: yup sorry I kieep thinking its in one hour
[14:12] <mup> Bug #1430340 changed: Failing to create tempdir in tests on windows <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1430340>
[14:18] <mup> Bug #1430340 was opened: Failing to create tempdir in tests on windows <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1430340>
[14:20] <axw> fwereade: if you have any time today, I'd appreciate a review of the storage hook source: http://reviews.vapour.ws/r/1113/
[14:30] <gsamfira> mgz: running tests now
[14:30] <mgz> gsamfira: ace
[14:40] <gsamfira> mgz: http://paste.ubuntu.com/10574918/ :)
[14:41] <gsamfira> going to fix tests today. We need that CI up as soon as humanly possible :D
[14:44] <gsamfira> recloned master just to make sure
[14:45] <gsamfira> yup, my bad. unclean env on my machine. Apologies
[14:45] <mgz> yeah, wondered if it was a dep issue
[14:47] <gsamfira> testing again
[14:48] <axw> can someone please review https://github.com/juju/juju/pull/1789 - fixes the critical blocker in 1.22
[14:48] <dimitern> axw, LGTM
[14:49] <axw> dimitern: thanks
[14:49] <gsamfira> mgz: I mentioned this before, and I don't know if its possible, but using WinRM to run the tests might avoid environment issues you get with OpenSSH. You can still use OpenSSH to scp files, just don't add it to the environment
[14:49] <gsamfira> mgz: there is a python script that can be used for this, and it can be run from any Linux box
[14:50] <gsamfira> mgz: https://github.com/cloudbase/pywinrm/blob/master/wsmancmd.py
[14:51] <gsamfira> mgz: we use this in the Hyper-V OpenStack CI to run the tempest tests
[14:55] <mgz> gsamfira: I think the ssh stuff is pretty clean - I was worried we were polluting with cygwin junk but turned out not to be the case
[14:56] <dimitern> TheMue, please update the status on bug 1428430
[14:56] <mup> Bug #1428430: AllWatcher does not remove last closed port for a unit, last removed service config <api> <juju-core:Triaged by themue> <https://launchpad.net/bugs/1428430>
[14:56] <TheMue> dimitern: will do
[15:00] <mup> Bug #1403955 was opened: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0 <cts> <juju-core:New> <isc-dhcp (Ubuntu):Confirmed> <https://launchpad.net/bugs/1403955>
[15:04] <axw> dimitern: I'm off to bed, would you mind keeping an eye on that merge and restart it if needed?
[15:05] <dimitern> axw, sure, np
[15:05] <voidspace> dimitern: so only the State can run queries (like "find all IP addresses for this machine ID"
[15:05] <voidspace> dimitern: because the collection names are private
[15:05] <voidspace> dimitern: so a new state method to find them all
[15:06] <voidspace> dimitern: or I could just have a state method to remove them all and move all that code
[15:06] <dimitern> voidspace, yeah, that sounds good
[15:06] <voidspace> dimitern: (it's only iterate over the returned collection and call addr.Remove)
[15:06] <voidspace> dimitern: a state method to fetch them all, or a state method to remove them all - which do you think?
[15:06] <voidspace> dimitern: I think maybe just a method to find them all
[15:06] <dimitern> voidspace, I think the latter is better
[15:06] <voidspace> hah
[15:06] <voidspace> dimitern: ok, maybe
[15:06] <voidspace> it's what we specifically need I guess
[15:07] <voidspace> fairy 'nuff
[15:07] <dimitern> voidspace, if we need to find them we'll add another method
[15:07] <voidspace> let a thousand methods bloom
[15:07] <dimitern> voidspace, :)
[15:07] <dimitern> voidspace, however, let me check a thing first
[15:11] <voidspace> dimitern: this is the core logic
[15:11] <voidspace> dimitern: http://pastebin.ubuntu.com/10575094/
[15:11] <voidspace> dimitern: it needs some error handling around the addr.Remove() and it's in the wrong place (needs to be in State)
[15:11] <voidspace> but that's all it's doing
[15:12] <dimitern> voidspace, yeah - no existing "find all ips for a machine/subnet"
[15:12] <voidspace> dimitern: I was pretty sure there wasn't as I've worked with most of the IPAddress code
[15:13] <voidspace> it's new for the networking stuff
[15:13] <voidspace> we're only modelling IP addresses allocated for containers so far
[15:15] <dimitern> voidspace, yeah, so I guess it does sound better to have a machine.AllocatedIPAddresses() method
[15:15] <dimitern> voidspace, and then call ip.Remove() on each.
[15:18] <voidspace> dimitern: ok, I'll do that
[15:18] <voidspace> dimitern: thanks
[15:18] <voidspace> dimitern: for machine id I want container.InstanceId() right?
[15:18] <dimitern> voidspace, no, just machine id
[15:19] <voidspace> dimitern: I have a state.Machine called container
[15:19] <dimitern> voidspace, we only need instanceId when talking to the provider - i.e. ReleaseAddress
[15:19] <voidspace> ah
[15:19] <voidspace> so ID() instead of InstanceId()
[15:20] <voidspace> or at least Id()
[15:26] <dimitern> voidspace, yes
[15:27] <dimitern> fwereade, I'd appreciate if you can have a look at this http://reviews.vapour.ws/r/1118/ which should fix a uniter filter intermittent test failure
[15:30] <mup> Bug #1307728 changed: ensure-availability command should show actions performed <ha> <ui> <juju-core:Fix Released> <https://launchpad.net/bugs/1307728>
[15:30] <mup> Bug #1403955 changed: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0 <cts> <juju-core:Invalid> <isc-dhcp (Ubuntu):Confirmed> <https://launchpad.net/bugs/1403955>
[15:37] <dimitern> jam, there's the fix btw ^^ if you can give it a try and see if you still reproduce the issue that'll be great
[16:32] <sinzui> dimitern, which milestone should bug 1428439 be on
[16:32] <mup> Bug #1428439: retry-provisioning launches instances for containers; cannot retry containers at all <juju-core:Triaged> <https://launchpad.net/bugs/1428439>
[16:35] <sinzui> ericsnow, do you think we need a two vivid slaves with systemd and upstart to be certain juju works with both configurations?
[16:37] <mup> Bug #1403955 was opened: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0 <cts> <kvm> <lxc> <network> <juju-core:Triaged> <isc-dhcp (Ubuntu):Confirmed> <https://launchpad.net/bugs/1403955>
[16:37] <ericsnow> sinzui: not really, considering that vivid operates under upstart only in "old" pre-release images and the official releases will all be systemd
[16:37] <dimitern> sinzui, 1.23-beta1 is ok I think
[16:38] <ericsnow> sinzui: then again, but it also depends on if upstart will be officially supported as the booted init systemd on vivid
[16:38] <sinzui> ericsnow, what about people upgrading from utopic. they don't switch unless Ubuntu make further packaging changes
[16:38] <ericsnow> sinzui: I doubt it will be, but if it is then 2 slaves may make sense
[16:38] <ericsnow> sinzui: good point
[16:39] <sinzui> ericsnow, I am still unsure. maybe I should just take the time and have two slaves. I can turn one off later
[16:39] <ericsnow> sinzui: so does that mean upstart will be supported up to the next LTS?
[16:39] <ericsnow> sinzui: sounds good
[16:39] <sinzui> ericsnow, It might be required as a legacy.
[16:39] <ericsnow> sinzui: it should continue to work under upstart regardless
[16:40] <sinzui> ericsnow, yeah, and the current setup proves that. I want to be sure it still works if Ubuntu about-face
[16:40] <ericsnow> sinzui: but it does mean having 2 slaves for each release starting with vivid, no?
[16:41] <ericsnow> sinzui: there *is* a contingency plan for dropping systemd in vivid, so good thinking
[16:42] <sinzui> ericsnow, maybe? its about Ubuntu making systemd-sysv a requirement
[17:44] <ericsnow> sinzui: do we use feature flags in CI?
[17:44] <sinzui> ericsnow, no
[17:45] <sinzui> ericsnow, are the set in environments.yaml?
[17:47] <ericsnow> sinzui: I believe it's from environment variables
[17:48] <sinzui> ericsnow, it it works from shell env vars, I think we can reconfigure jobs as needed. If it comes from the juju env, we need to make config and or code changes to use them
[17:48] <ericsnow> sinzui: if we run a vivid slave with upstart then it may make sense to use a feature flag to indicate upstart-on-vivid
[17:49] <sinzui> ericsnow, understood
[17:49] <ericsnow> sinzui: there's a fallback case for init system discovery that hard-codes vivid (and subsequent releases) to systemd
[17:49] <sinzui> ericsnow, I am now at the point of wondering what will happen when I try to provision a new slave. The charm/package uses upstart
[17:50] <sinzui> ericsnow, if there is no legacy upstart support, the slave wont run without me writing a systemd script
[17:50] <ericsnow> sinzui: yeah, we'll see :(
[17:51] <ericsnow> sinzui: there is some accommodation for that, but I don't know to what degree (they were still discussing it a month+ ago)
[17:52] <ericsnow> sinzui: I'll try to find out
[17:52] <ericsnow> sinzui: can you tell if the latest vivid image is booting systemd?
[17:53] <sinzui> ericsnow, I haven't looked
[17:53] <ericsnow> sinzui: k
[17:55] <sinzui> ericsnow, since clouds don't support ubuntu devel images, nor does the current juju support systemd. I need to build this by hand
[17:55] <ericsnow> sinzui: ah, makes sense
[17:55] <ericsnow> sinzui: it's like that for each new series, huh?
[17:56] <sinzui> I have done this before. it just take longer for me to type and upload things that juju and charms
[17:57] <sinzui> ericsnow, I usually wait for an official release of juju after a series opens. that gives me a juju and an agent. then I provision the previous series in a cloud, dist-upgrade, the manually provision. that is how we got the trusty, utopic, and current vivid
[18:13] <gsamfira> any chance I can get a review on this: http://reviews.vapour.ws/r/1119
[18:13] <gsamfira> so we can start testing on windows? :)
[18:17] <sinzui> ericsnow, I am having a misadventure on the current vivid-slave. lxc blewup. I am watching a case were we upgrade from stable juju to unstable, which might be upset because 1.21.3 doesn't know about systemd. I will report real details in a bit
[18:17] <ericsnow> sinzui: k
[18:22] <alexisb> http://www.opencompute.org/community/events/summit/ocp-us-summit-2015-live-streaming
[18:22] <alexisb> thanks kwmonroe for the pointer ^^
[18:22] <alexisb> perrito666, this is our OCP demo
[18:23]  * gsamfira is going through  second bowl of popcorn
[18:24] <alexisb> gsamfira, :)
[18:24] <sinzui> ericsnow, looks like lxc template creation is broken. 1.21.3 cannot create a template with the current vivid lxc images. I am going to clean, upgrade, then retest that unstable juju loves the new image. Then try the upgrade again
[18:24] <alexisb> shouldnt you be asleep
[18:24] <ericsnow> sinzui: right
[18:24] <gsamfira> alexisb: not yet. Its 20:24 here :D
[18:24] <gsamfira> and I actually grabbed a few hours last night :)
[18:25] <ericsnow> sinzui: we send upstart-specific commands to cloud-init and in the LXC clonetemplate code
[18:25] <sinzui> ericsnow, I believe we will not be counting the upgrade test until 1.23.0 is released
[18:25] <ericsnow> sinzui: so if vivid is booting off systemd now then you'll see that sort of failure
[18:25] <sinzui> ericsnow, thank you. that predicts my question
[18:26] <ericsnow> sinzui: can you check PID 1?
[18:26] <sinzui> ericsnow, I cannot even get into the container. it is a zombie
[18:27] <ericsnow> sinzui: yuck
[18:27] <sinzui> I am kill lxc procs because the controls are useless
[18:27] <ericsnow> sinzui: not even with lxc-console?
[18:27] <sinzui> it is stalled
[18:27] <ericsnow> sinzui: bummer
[18:27] <ericsnow> sinzui: oh
[18:28] <ericsnow> sinzui: there's a known issue here
[18:28] <ericsnow> sinzui: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020
[18:28] <mup> Bug #1347020: systemd does not boot in a container <systemd-boot> <lxc (Ubuntu):Fix Released by stgraber> <lxc (Ubuntu Trusty):Triaged by stgraber> <https://launchpad.net/bugs/1347020>
[18:28] <sinzui> ericsnow, that looks similar
[18:29] <ericsnow> sinzui: basically, vivid with systemd in a container on a non-vivid host won't work
[18:29] <alexisb> with natefinch out is there someone who can review this for cloudbase (aka gsamfira):
[18:29] <alexisb> https://github.com/juju/juju/pull/1791
[18:29] <alexisb> it is fixing our windows tests that will soon have the power to block trunk
[18:30] <ericsnow> sinzui: well, it works on trusty and utopic if you update a few things from e.g. "trusty-updates"
[18:31] <ericsnow> sinzui: I expect it won't work on precise
[18:32] <hazmat> anybody who wants to help a user debug while local provider is broken on vivid should join #juju and talk to lamont
[18:32] <hazmat> s/while/why
[18:40] <sinzui> ericsnow, the comedy gets better. The jenkins upstart job got removed. I am now committed to rebuilding a slave that meets your needs. I am going to disable all the vivid jobs until the replacement is ready
[18:44] <ericsnow> sinzui: okay
[18:46] <cmars> gsamfira, i'll take a look at it.
[18:46] <alexisb> cmars, thank you!
[18:52] <gsamfira> cmars: thank you! :)
[18:59] <ericsnow> sinzui: I'm going to land the patch that specifies that vivid uses systemd
[19:00] <voidspace> g'night all
[19:00] <ericsnow> sinzui: then write a follow up patch that adds a feature flag for the vivid-on-upstart case
[19:00] <sinzui> ericsnow, I suppose you should as it clearly doesn't want me using upstart any more
[19:01] <ericsnow> sinzui: also, the ubuntu folks verified that vivid did indeed switch yesterday
[19:21] <ericsnow> sinzui: I've landed the vivid-is-systemd patch so vivid should be able to work now (LXC host issues aside)
[19:22] <sinzui> ericsnow, thank you.
[19:58] <cmars> gsamfira, reviewed
[19:59] <thumper> morning
[20:00] <ericsnow> sinzui: upstart feature-flag patch: http://reviews.vapour.ws/r/1121/
[20:00] <sinzui> fab
[20:01] <ericsnow> sinzui: that should help in the case we have a bot running upstart
[20:02] <sinzui> ericsnow, I am writing a systemd script for jenkins. I wonder how many charms will need to change
[20:04] <alexisb> morning thumper
[20:07] <ericsnow> sinzui: well, since charms are series-specific the impact is explicitly limited--vivid charms will have to make sure they work under systemd
[20:07] <ericsnow> sinzui: how many charms will have to adjust?  good question
[20:08] <sinzui> ericsnow, yeah. We mark our charms because we need them the day the series is born
[20:14] <thumper> cherylj: if you want to start our 1:1 early, I'm fine with that
[20:16] <cherylj> thumper: sure, I'll join the hangout again
[20:58] <perrito666> now, that disconnect button is too big
[21:09] <thumper> cmars: anything you want to catch up with today?
[21:10] <mup> Bug #1420049 was opened: ppc64el - jujud: Syntax error: word unexpected (expecting ")") <deploy> <openstack> <regression> <uosci> <juju-core:In Progress by axwalk> <juju-core 1.22:Fix Released by axwalk> <https://launchpad.net/bugs/1420049>
[21:52] <ericsnow> thumper: thanks for taking a look at that vivid-LXC issue
[22:18] <menn0> thumper, davecheney: https://github.com/juju/utils/pull/115
[22:23]  * thumper looks
[22:24] <ericsnow> menn0: FYI, the github-RB hooks work for the utils repo too
[22:25] <menn0> ericsnow: yep I saw that. good stuff.
[22:26] <ericsnow> menn0: I've been meaning to do it for the other repos but need round tuits
[22:33] <thumper> menn0: review done
[22:34]  * thumper hands ericsnow a round tuit
[22:35]  * jw4 learned something new today - round tuits - :)
[22:36] <mgz> not to be confused with square tuits
[22:36] <jw4> haha
[22:37] <perrito666> you both just made me google
[22:38] <perrito666> uff, finally all tests pass
[22:46] <jw4> perrito666, I blame it on ericsnow ... I was 50 years behind
[22:46] <ericsnow> jw4: :)
[22:47] <perrito666> ok, EOD
[22:47] <perrito666> cheers
[22:47] <jw4> bye perrito666
[23:07] <jjox> hazmat: hi there o/ - fyc -> https://code.launchpad.net/~jjo/juju-deployer/fix-juju-deployer-diff-for-multiple-relations-between-servicepair/+merge/252271
[23:24] <hazmat> jjox: solid
[23:25] <hazmat> jjox: did you see my comments on the bug... much of this can be simplified by simply mocking juju
[23:31] <jjox> hazmat: ah, hm ... hadn't - will peek tomorrow
[23:47] <wallyworld> axw: just started looking at the local state PR. is there a reason not to reuse stuff from uniter/operation/state.go?


[07:49] <dholbach> good morning
[07:52] <Unit193> Howdy.
[20:59] <shadeslayer> stupid package renaming question, how do I make sure the old package is removed on upgrade
[20:59] <shadeslayer> just add a conflicts?
[20:59] <shadeslayer> but it doesn't really conflict
[21:00] <shadeslayer> I already have a  breaks/replaces
[21:39] <shadeslayer> nvm
[21:41] <Unit193> shadeslayer: Care to share what you ended up doing?
[21:41] <shadeslayer> Unit193: it was a issue with launchpad
[21:41] <Unit193> Hah. :P
[21:41] <shadeslayer> it still advertised the old package
[21:42] <shadeslayer> so the old package was newer than the one on my system
[21:42] <shadeslayer> and apt wanted to upgrade it to the new one
[21:42] <shadeslayer> which is why it didn't remove it
[21:44] <shadeslayer> does anyone know why the firefox lang packs don't declare a depends on Firefox?
[21:45] <shadeslayer> chrisccoulson: ^^


 @sgmoore arraybolt3 RikMills: hey so apparently we didn't hook up the boot entry for OEM to our actual icon
 https://iso.qa.ubuntu.com/qatracker/testcases/1305/revisions/1673/info
 Looking into it
 This one is actually really easy... some small glue to debian-cd for a custom boot parameter which is picked up by the installer prompt which kicks the user to the OEM install
[13:40] <BluesKaj> Hi all
[13:59] <sgmoore> hiyas
[14:00] <BluesKaj> hey sgmoore
[14:01] <BluesKaj> still have some annoyances on kde/plasma, but nothing serious
[21:26] <valorie> running updates (254!) on my travel lappy
[21:26] <valorie> I'm no longer in the release chan - any insight on when the final might be published?
[21:27] <valorie> if it's not until Friday I'll stop worrying because I will have little time to dl on that travel day....
[21:28] <valorie> cool, updates are done and it's restarting
[21:29] <valorie> I am LOVING our new branding
[21:33] <valorie> all is well, including discover
[21:35] <arraybolt3> valorie: Final is due to be published tomorrow on Thursday.
[21:35] <arraybolt3> (though depending on yoru timezone you might *be* in thursday and it's due for Friday)
[21:35] <arraybolt3> I hate time
[21:35] <valorie> excellent
[21:35]  * valorie is in PDT
[21:36] <arraybolt3> oh then you're two hours behind me in CDT
[21:36] <arraybolt3> so yeah, thursday is release day
[21:37] <valorie> the release chan is fun, but my peace of mind is better with fewer chans
[21:38] <valorie> in #ubuntu-next but it's been quiet
[21:39] <arraybolt3> yeah it can be intense
[21:39] <arraybolt3> -release I mean
[21:39] <arraybolt3> I've kind of gotten numbed to channel overload being a defender on the Matrix side though - I probably am in almost 100 different chat rooms at this point.
 Ditto. I can't keep track either  :(
[22:32] <mparillo> You hate time? Not as much as this guy: https://www.youtube.com/watch?v=-5wpm-gesOY
[22:43] <arraybolt3> mparillo: you were right XD
[22:44] <arraybolt3> That was an amazing summation of everything I hate about time plus a lot I didn't until now.
 Here in Arizona we don't do the daylight savings thing. I never know what time it is anywhere haha. My phone even gets confused. 30 miles away on the Indian reservation, they do. So confusing.


[11:05] -SwissBot:#ubuntu-news- ::Planet:: Marcin Juszkiewicz: From a diary of AArch64 porter â parallel builds @ https://marcin.juszkiewicz.com.pl/2018/06/06/from-a-diary-of-aarch64-porter-parallel-builds/
[13:08] -SwissBot:#ubuntu-news- ::Softpedia:: Purism's Librem 5 Privacy, Security-Focused Linux Phone Arrives in January 2019 @ https://news.softpedia.com/news/purism-s-librem-5-privacy-security-focused-linux-phone-arrives-in-january-2019-521437.shtml (by Marius Nestor)
[13:46] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: 3 macOS Mojave Features You Can Get on Linux @ https://www.omgubuntu.co.uk/?p=132107 (by Joey Sneddon)
[14:00] -SwissBot:#ubuntu-news- ::Softpedia:: darktable 2.4.4 Adds 50% Zoom Option in Darkroom Mode, Better Sony a6500 Support @ https://news.softpedia.com/news/darktable-2-4-4-adds-50-zoom-option-in-darkroom-mode-better-sony-a6500-support-521438.shtml (by Marius Nestor)
[14:27] -SwissBot:#ubuntu-news- ::Softpedia:: Ubuntu Budgie Remix 16.04 Operating System Will Reach End of Life in August 2018 @ https://news.softpedia.com/news/ubuntu-budgie-remix-16-04-operating-system-will-reach-end-of-life-in-august-2018-521439.shtml (by Marius Nestor)
[14:45] -SwissBot:#ubuntu-news- ::Softpedia:: Nvidia 390.67 Graphics Driver Released for Linux, FreeBSD, and Solaris Gamers @ https://news.softpedia.com/news/nvidia-390-67-graphics-driver-released-for-linux-freebsd-and-solaris-gamers-521440.shtml (by Marius Nestor)
[20:37] -SwissBot:#ubuntu-news- ::Softpedia:: You Can Now Manage Nitrokey Encryption USB Keys in Ubuntu, Other Linux Distros @ https://news.softpedia.com/news/you-can-now-manage-nitrokey-encryption-usb-keys-in-ubuntu-other-linux-distros-521445.shtml (by Marius Nestor)
[21:23] -SwissBot:#ubuntu-news- ::Softpedia:: Canonical Announces Ubuntu for Amazon’s Elastic Container Service for Kubernetes @ https://news.softpedia.com/news/canonical-announces-ubuntu-for-amazon-s-elastic-container-service-for-kubernetes-521446.shtml (by Marius Nestor)
[23:25] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Side View is the Firefox Feature I’ve Been Waiting For @ https://www.omgubuntu.co.uk/?p=132112 (by Joey Sneddon)


[05:36] <Kilos> morning peeps
[05:46] <Kilos> hi bduk1
[05:47] <nuvolari> o/ morning oom Kilos
[05:47] <nuvolari> hi die_held
[05:48] <Kilos> lo nuvolari die_held
[05:51] <die_held> morning Kilos!
[05:54] <Kilos> hey die_held you gotta greet nuvolari too. is jabberwocky late again or sick?
[05:57] <die_held> Wudup nuvolari :)
[05:57] <bduk1> More almal
[05:57] <die_held> Probably still sick, not sure whats wrong with the poor guy, been 3weeks now
[05:57] <Kilos> sjoe
[05:58] <Kilos> hi mazal
[06:00] <mazal> More oom
[06:11] <Squirm> morning all
[06:12] <Kilos> hi Squirm
[06:27] <ThatGraemeGuy> morning peeps
[06:27] <Kilos> hi ThatGraemeGuy
[06:38] <ThatGraemeGuy> Kilos: are you the only one playing at the moment?
[06:38] <Kilos> yip i can go off
[06:38] <Kilos> there
[06:38] <ThatGraemeGuy> i just want to make a backup of the world quickly
[06:39] <Kilos> np
[06:39] <Kilos> why dont you want me part off your backup?
[06:39] <Kilos> hehe
[06:39] <ThatGraemeGuy> server has to be stopped before you can copy the files safely
[06:40] <Kilos> teasing man
[06:42] <ThatGraemeGuy> up again thanks
[06:43] <Kilos> cool ty
[06:43] <Kilos> dont break it now
[06:43] <ThatGraemeGuy> i'll write a script later sometime to automatically back up somewhere in the wee hours of the morning
[06:43] <Kilos> working so kiff i can e everywhere
[06:44] <Kilos> write a script to make lava source
[06:44] <Kilos> game was lonely this weekend, was mainly only me
[06:51] <Symmetria> snoreeee trying to organize my video content
[06:52] <Symmetria> and its taking forever
[06:52]  * Symmetria needs more SSD's when doing this crap
[07:00] <ThatGraemeGuy> Kilos: why the obsession with lava source? there is an insane amount of it on the map, you can move it with buckets if you want
[07:01] <Kilos> lol ive made my own little patch on the black block on the map to see is its more visible
[07:02] <Kilos> http://mt.donaldson.za.net/
[07:02] <Kilos> i see it
[07:08] <mazal> I made a rsync job for mine that runs every 4 hours
[07:08] <mazal> But still do a manual every afternoon
[07:08] <ThatGraemeGuy> mazal: just make sure the server is not running when you take the backup
[07:09] <mazal> Yep , hence the manual one once a day
[07:10] <ThatGraemeGuy> i'll share my script when i get to writing one if you are interested
[07:10] <mazal> Is start and stop of the server in your script ?
[07:11] <mazal> The backup part is easy , I use rsync jobs for all my backups. But my server I start the gui way , so don't know how to do that with a script
[07:16] <charl_> good morning
[07:16] <Kilos> also im trying to unflood the mines near me, so i dont have to remember to keep coming up for air
[07:16] <Kilos> hi charl_
[07:16] <charl_> Maaz: coffee on
[07:16]  * Maaz washes some mugs
[07:16] <charl_> hi Kilos
[07:20] <Maaz> Coffee's ready for charl_!
[07:31] <Symmetria> argh why why why do people insist on using rfc1918 address space for bullshit
[07:31] <Symmetria> NAT must *DIE*
[07:42] <charl_> hi Symmetria
[07:42] <Vince-0> more mense
[07:42] <charl_> hi Vince-0
[07:43] <charl_> Symmetria: agreed but that's why we need ipv6 asap
[07:47] <Symmetria> charl, there is PLENTY of v4 space in africa
[07:47] <Symmetria> people just dont want to use it
[07:47] <Symmetria> because for some bizarro reason they are saving it for a better time
[07:48] <Symmetria> there is no better time, burn it, use it all, get rid of it, THEN we can actually do v6 because people won't be sitting there going "there is no need, we have v4 forever"
[07:48] <Kilos> hi Vince-0
[07:54] <charl_> Symmetria: hmmm, africa would be the only continent with ipv4 reserves, the rest of the world has pretty-much run out already
[07:55] <Symmetria> charl, yes, but africa has *WAY* to much
[07:55] <Symmetria> way way way way to much
[07:56] <charl_> sounds like the iana should reclaim a big part of that assignment and give it to other continents that need it more instead ?
[07:57] <charl_> like lacnic for example
[08:00] <tinuva> i get mails at least every 2nd week asking if people can lease ips from us
[08:00] <tinuva> we like to use it
[08:01] <charl_> whow just looking at the ipv6 address report - apnic ran out in 2011, ripe in 2012, lacnic and 2014 and arin is projected to run out in 2015
[08:01] <charl_> afrinic is only projected to run out in 2019
[08:02] <charl_> nah afrinic needs to hand over its assignments... ridiculous
[08:02] <charl_> use it or lose it
[08:08] <Vince-0> Kilos, !
[08:09] <theblazehen> charl_: eish..
[08:10] <theblazehen> You mean v4 though?
[08:10] <Kilos> oops sorry Vince-0 hi there
[08:10] <Kilos> hi tinuva
[08:10] <theblazehen> I don't think v6 will run out that soon..
[08:11] <Kilos> ah JabberwockyA19 wb
[08:11] <theblazehen> hi Kilos
[08:11] <Kilos> hi theblazehen
[08:11] <Symmetria> ipv4 is done
[08:11] <Symmetria> apnic is finished
[08:11] <Symmetria> ripe is finished
[08:11] <Symmetria> lacnic is finished
[08:11] <Symmetria> and arin is finished
[08:11] <Symmetria> well, ripe, lacnic and arin are both in whats called soft landing / final exhaustion phase, which is basically finished, lacnic dropped to their last /10
[08:12] <theblazehen> damn..
[08:12] <Symmetria> trust me :) I know the figures very very very well, lol, I sit on the afrinic board ;p
[08:12] <theblazehen> Symmetria: last /10 = 2^22 addresses right?
[08:13] <Symmetria> yeah
[08:13] <Symmetria> 64 /16s
[08:13] <Symmetria> basically a quater of a /8
[08:13] <theblazehen> yeah
[08:13] <Symmetria> where as afrinic has 3.2 /8s left
[08:14] <theblazehen> 3.2 ?
[08:14] <theblazehen> 3 plus some /16's or something?
[08:14] <Symmetria> yeah
[08:15] <Symmetria> lol at liquid I'm making a conscious effort to do everything I can to get rid of private space usage, everywhere
[08:15] <JabberwockyA19> môre Kilos!
[08:15] <charl_> theblazehen: of course ipv4, we're talking about the ipocalypse
[08:15] <Symmetria> you won't even find a private IP at my house :P
[08:16]  * Symmetria runs a /27 worth of public space at his house
[08:16] <charl_> Symmetria: you mean the afrinic bored? :)
[08:16] <theblazehen> charl_: yeah, i know. "charl_ ? whow just looking at the ipv6 address report"
[08:16] <charl_> theblazehen: bah you're right, my bad :P
[08:16] <theblazehen> Symmetria: wow..
[08:17] <charl_> Symmetria: at work we have a /16, every ip (even on wlan) is a public ip
[08:18] <charl_> nice for remote access :P
[08:18] <charl_> you don't need to vpn into the network first
[08:18] <charl_> you can ping my laptop from across the world :)
[08:18] <Symmetria> charl you can ping my tv from the other side of the world
[08:18] <charl_> awesome
[08:19] <charl_> at home i still have crappy old-school cable modem with nat and no ipv6
[08:20] <charl_> i want fiber but that isn't available yet where i live :(
[08:20] <charl_> but first thing i would ask is "do you have ipv6?"
[08:21] <Symmetria> http://valhalla.clue.be/~vort/equipment.jpg
[08:21] <Symmetria> http://valhalla.clue.be/~vort/cabinet.jpg
[08:21] <Symmetria> heh, right hand most cabinet contains the equipment in the equipment photo
[08:21] <Symmetria> next to it is the generator cabinet
[08:21] <Symmetria> thats in my back yard :P
[08:24] <charl_> nice !
[08:24] <charl_> now we're talking
[08:24] <Symmetria> both of those fibers go straight into the backbone
[08:24] <Symmetria> no limits, no shaping, no bugger all :P
[08:25] <charl_> ftth ftw :)
[08:25] <Symmetria> lol, my office pc even has a seperate vlan interface that puts it on the same network as my house :P
[08:25] <charl_> whow ! no vpn either :P
[08:25] <Symmetria> so effectively my house and my office workstation are on the same lan :P
[08:25] <Symmetria> charl haha same broadcast domain
[08:26] <charl_> it's cool to work at an isp :P
[08:27] <Symmetria> we'll be upgrading the entire thing shortly and those 2 x 1G's will be upgraded to 2 x 10G's
[08:28] <charl_> will last you a couple of years i'm sure :P
[08:29] <charl_> you're in kenya right ?
[08:39] <Symmetria> yeah
[09:26] <Symmetria> urgh
[09:26] <Symmetria> how the hell do I install a package on one of the rpm based distros
[09:26] <Symmetria> idiots who dont install boxes on ubuntu like I tell them to
[09:31] <theblazehen> Symmetria: yum install $PACKAGE ?
[09:37] <Symmetria> hrm
[09:37] <Symmetria> ok someone on a decent net connection
[09:37] <Symmetria> go to www.speedtest.net
[09:37] <Symmetria> find kenya on the map
[09:37] <Symmetria> and run some tests to the liquid server there
[09:37] <Symmetria> and lemme know results
[09:38] <Symmetria> (latency/speed)
[09:42] <ThatGraemeGuy> mmm
[09:42] <ThatGraemeGuy> speedtest CLI script doesn't tell me latency
[09:42] <Symmetria> well gimme speeds :)
[09:42] <charl_> Symmetria: i'll PM you
[09:43] <ThatGraemeGuy> http://slexy.org/raw/s2Q6F62Qqg
[09:43] <Symmetria> thats not bad, 51 down
[09:43] <ThatGraemeGuy> we have a gigabit into AfricaINX and IS there but the box I ran that from is on a 100Mbit link
[09:44] <ThatGraemeGuy> currently running on IS afaik
[09:44] <Symmetria> though I think the latency is probably slowing it down if you aint tweaked the stack
[09:44] <ThatGraemeGuy> i'm not in the networks team
[09:45] <ThatGraemeGuy> if you give me an IP i can run mtr for a bit if you want
[09:45] <Symmetria> heh, run a trace to <IP_ADDRESS> and paste it to me :)
[09:48] <ThatGraemeGuy> http://slexy.org/raw/s20SsvQAfv
[09:52] <Symmetria> heh not a bad latency from .za to my house :P
[09:53] <ThatGraemeGuy> :-)
[10:04] <Kilos> graeme have you got lots of obsidian?
[10:05] <Kilos> then ill make the roads black and ill see them on the map
[10:13] <Kilos> oh my i forgot im on irc ThatGraemeGuy
[10:16] <ThatGraemeGuy> the roads are already on the map
[10:18] <Kilos> in white that i cant see
[10:19] <Kilos> sigh
[14:08] <Golynx> i cant seem to fix ubuntu
[14:08] <Kilos> whats wrong with it
[14:09] <Golynx> fixing it from dual boot
[14:09] <Golynx> with single install it was easy
[14:09] <Golynx> tried booting in recovery mode and terminal is gone
[14:10] <Kilos> does ctrl+alt+t work on xfce
[14:11] <Golynx> can i reinstall it ubuntu from the same partition without hurting windows ?
[14:11] <Golynx> xfce is not loading nothing is loading
[14:11] <Golynx> no terminal nothing
[14:11] <Kilos> yes you can but lets see if we can fix it
[14:11] <Kilos> try ctrl+alt+f3
[14:12] <Golynx> i already tried commands i got from forums its not working
[14:13] <Golynx> ctrl+alt+f1 not working either
[14:13] <Golynx> mouse dead , keyboard dead, graphics not detected etc...
[14:14] <Kilos> yes you can reinstall. without hurting windows
[14:14] <Kilos> you have your archives saved
[14:15] <Golynx> this happened because i tried dpkg all the files in the archives folder
[14:15] <Kilos> just boot into dvd go with the install route and delete the ubuntu partion and install there
[14:15] <Golynx> but it already had the drivers installed
[14:15] <Golynx> hmm, are you sure it wont hurt windows
[14:16] <Kilos> should be a few linux partitions
[14:16] <Kilos> ya
[14:16] <Kilos> but i dont control what you are doing so i dunno there
[14:16] <Golynx> what do i use to delete the ubuntu partition
[14:16] <Kilos> ive done it here a few times
[14:17] <Golynx> gparted ?
[14:17] <Kilos> gparted
[14:17] <Golynx> ok
[14:17] <Kilos> you can also delete it with a windows dvd
[14:17] <Kilos> hehe
[14:17] <Golynx> so it will still dual boot and stuff
[14:18] <Kilos> ya
[14:18] <Kilos> im doing that here
[14:18] <Kilos> first 30g is xp
[14:18] <Kilos> to use up the faulty disc areas
[14:19] <Golynx> ok, i will delete ubuntu partition then reinstall it in the space that is left
[14:19] <Kilos> but on going the install route it should get to partitioning anyway
[14:20] <Kilos> no need to run live and then use gparted
[14:20] <Golynx> huh ? i dont understand now
[14:20] <Golynx> i have to use the dvd to remove the ubuntu on disk
[14:21] <Golynx> i cant do it with the installed ubuntu
[14:21] <Kilos> you boot from ubuntu dvd or cd
[14:21] <Kilos> then choose install then you will get to install alongside or other options
[14:22] <Kilos> maybe advanced
[14:22] <Kilos> and it will show partitions and you can then do your thing
[14:22] <Golynx> then gparted shows the windows and ubuntu partitions , then i delete the ubuntu partition, then i install alongside windows and move the slider to choose the amount of space on disk for ubuntu to install to
[14:23] <Golynx> thats the way
[14:23] <Kilos> ya
[14:24] <Golynx> ok bbl
[15:14] <Kilos> hi  arnaud
[15:14] <arnaud> hi Kilos
[15:14] <Kilos> whats broken?
[15:15] <arnaud> nothing
[15:15] <Kilos> yay i just died
[15:15] <arnaud> hein ????
[15:16] <Kilos> got a flow of lava on my head
[15:16] <arnaud> flow of lava ? you serious ?
[15:16] <Kilos> minetest
[15:16] <arnaud> :D
[15:16] <Kilos> haha
[15:16] <Kilos> i love that game
[15:17] <arnaud> never tried it before
[15:17] <Kilos> very addictive
[15:17] <Kilos> and free id you aint got 3g costs killing you
[15:17] <Kilos> if
[16:25] <Kilos> hi Private_User yoyo again i see
[18:24] <magespawn> good evening all
[18:25] <magespawn> Kilos whats up?
[18:25] <Kilos> hi magespawn how are you?
[18:26] <magespawn> good and you?
[18:26] <Golynx> this sucks
[18:26] <Kilos> did they fix you?
[18:26] <Kilos> what now Golynx
[18:26] <Golynx> why didnt ubuntu make for any package version to be installed when you want
[18:26] <magespawn> have way Kilos
[18:26] <magespawn> half
[18:26] <Golynx> broken packages is the problem
[18:27] <Kilos> ai! half way
[18:27] <superfly> Golynx: huh? what do you mean?
[18:27] <Kilos> where are they getting broken Golynx
[18:27] <Golynx> fix broken packages wont fix the issues
[18:27] <magespawn> ah yes, but it is the painful part
[18:28] <Golynx> thr url's where the packages are are 404 not found
[18:28] <Golynx> the*
[18:28] <Kilos> there is an apt-get --fixbroken but im not sure of the correct words
[18:28] <Kilos> ah magespawn so the painful part is done?
[18:28] <Golynx> already tried that command , not working
[18:28] <magespawn> well i am not in pain anymore so that is good
[18:29] <Kilos> Golynx, move your repo
[18:29] <Golynx> Killos what you mean
[18:29] <magespawn> Golynx, the urls might be correct but you might not be able to get to tehm
[18:29] <Kilos> i had some probs with the local one not getting 3 files last night so i went to main
[18:30] <Kilos> look in synaptic for repositories
[18:31] <Golynx> i used sudo dpkg -i *.deb  to reinstall from my backedup packages
[18:31] <Golynx> most of the stuff works but few are broken
[18:32] <Kilos> then remove them and use gdebi to install them again
[18:32] <superfly> sudo apt-get -f install
[18:32] <superfly> sudo apt-get dist-upgrade
[18:33] <superfly> run those two until they both say everything is fine
[18:33] <Kilos> they most likely broken in where you saved them to dvd
[18:33] <superfly> Golynx: eish!
[18:33] <Golynx> gdebi wont install many packages with dependencies , it always wana go online to download the rest
[18:33] <magespawn> hi superfly
[18:33] <superfly> Golynx: never use dpkg unless you really know what you're doing. it doesn't do dependency management, so you're inflicting a broken system on yourself
[18:33] <superfly> hi magespawn, how goes? how's the family?
[18:34] <Golynx> ok thanks
[18:35] <Kilos> ty superfly
[18:35] <magespawn> they are all good thanks
[18:35] <magespawn> how is your family? the little guy?
[18:35] <superfly> Golynx: also, za.archive.... is sometimes broken. I've taken to using the main repos
[18:35] <Kilos> haha magespawn zak comes to minetest as well
[18:35] <superfly> magespawn: all good, thanks. the boys are boyish as ever
[18:37] <Golynx> ok superfly
[18:39] <Kilos> Maaz, seen inetpro_
[18:39] <Maaz> Kilos: inetpro_ was last seen 4 months, 26 days, 14 hours, 5 minutes and 33 seconds ago in #ubuntu-za on freenode [2014-02-03 20:33:51 PST], and has been online on freenode since 2014-06-28 17:21:17 PDT
[18:39] <Kilos> ai!
[18:39] <Kilos> Maaz, seen inetpro_
[18:39] <Maaz> Kilos: inetpro_ was last seen 4 months, 26 days, 14 hours, 6 minutes and 6 seconds ago in #ubuntu-za on freenode [2014-02-03 20:33:51 PST], and has been online on freenode since 2014-06-28 17:21:17 PDT
[18:40] <magespawn> superfly, that is a good thing
[18:40] <Kilos> Maaz, seen inetpro
[18:40] <Maaz> Kilos: inetpro was last seen 3 days, 22 hours, 51 minutes and 5 seconds ago in #ubuntu-za on freenode [2014-06-26 12:49:07 PDT], and has been offline on freenode since 2014-06-28 17:23:53 PDT
[18:40] <magespawn> thats better
[18:40] <Kilos> wow
[18:40] <Kilos> inetpro_, ping
[18:40] <Kilos> you got a tail
[18:41] <Kilos> he is getting scarcer all the time
[18:41] <magespawn> might be busy, it happens sometimes
[18:42] <Kilos> did i greet you today superfly ?
[18:42] <superfly> Kilos: i was so busy today, i wasn't even on my computer... so i don't really know
[18:42] <Kilos> well hello anyway
[18:43] <Golynx> in the 21st century people dont care about greeting anymore
[18:43] <Kilos> we do
[18:43] <Golynx> only in the business world
[18:44] <Kilos> you also gotta learn to greet before complaining
[18:44] <Kilos> manners maketh the man
[18:44] <Golynx> the future is looking dark in terms of manners and formal stuff
[18:45] <Kilos> its because peeps are allowing it to happen
[18:45] <Golynx> ja true
[18:45] <Kilos> we should add to next agenda if someone comes online for help and doesnt greet first just ignore them
[18:46] <Kilos> meng jou met semels dan vreet die varke jou
[18:46] <magespawn> most people get the idea if you greet them even if they have not
[18:46] <Golynx> but we cannot stop change though, if the masses dont do it then the few that do will soon be overwhelmed
[18:47] <Kilos> we dont have the masses here so lets keep our channel decent
[18:47] <Golynx> sure
[18:48] <magespawn> even if the masses do not, then you have greater standing than those who do not
[18:48] <Golynx> and spelling perfect :D
[18:48] <Kilos> hi Golynx is you ubuntu fixed now
[18:48] <Kilos> lol i use lotsa funny words like lotsa
[18:48] <Golynx> its broken Kilos
[18:48] <Kilos> still
[18:49] <Golynx> lots of !!!
[18:49] <Kilos> ya that
[18:49] <magespawn> slang has it's place too
[18:49] <Golynx> not ty - thank you !!!
[18:49] <superfly> Golynx: what does "sudo apt-get -f install" say?
[18:49] <Kilos> hehe
[18:49] <superfly> magespawn: yes, in the dustbin
[18:49] <Kilos> eish superfly
[18:50] <superfly> mb u cn ndrstnd wt m syn?
[18:50] <Kilos> huh
[18:50] <Golynx> superfly i know it can be fixed, but dont have the data right now
[18:50] <superfly> Exactly.
[18:50] <magespawn> that is not slang, that is just being lazy
[18:50] <Kilos> but you unnerstand lotsa?
[18:50] <Kilos> hehe
[18:50] <Golynx> but it is working fine
[18:50] <superfly> Golynx: did you copy the pacakges you have into /var/cache/apt/archives ?
[18:51] <superfly> *packages
[18:51] <Golynx> superfly yes, but synaptic showed different versions
[18:54] <Kilos> Golynx, didnt gdebi sort that last time
[18:55] <Kilos> it will tell you there is a later version available online but you dont need to go that way
[18:56] <Kilos> you can install each package independantly
[18:56] <Golynx> Kilos nope, last time i was lucky the downloads needed were very little and many packages didnt change versions from synaptic
[18:56] <Kilos> it will first want dependancies then you do them first
[18:58] <Kilos> it really sucks being limited with data hey
[18:58] <Kilos> scream for free wifi
[18:59] <Golynx> no problem, aslong as windows works i can try fix ubuntu in time
[18:59] <Golynx> lol
[18:59] <Kilos> or take you lappy to spors or one of them and have a cup of coffee and use their wifi
[18:59] <Kilos> spurs
[19:00] <Kilos> superfly, is the big boat finished?
[19:00] <Golynx> haha i'm not that desperate :p
[19:00] <Kilos> no anchor or harpoons in place
[19:01] <superfly> Kilos: yes, as far as I had though
[19:01] <superfly> Kilos: well, originally it was just going to be a merchant ship... but other people had other ideas
[19:01] <Kilos> oh other peeps
[19:01] <Kilos> oh my
[19:02] <Kilos> magespawn, have you seen the ship?
[19:02] <Kilos> hi ThatGraemeGuy
[19:02] <magespawn> no, what ship is that?
[19:02] <Golynx> why is use of python 3x lagging so behind
[19:03] <ThatGraemeGuy> 'lo 'lo
[19:03] <Kilos> in minetest
[19:03] <Kilos> its a beaut
[19:03] <magespawn> i will have look when i can
[19:04] <Golynx> no py3exe sucks
[19:04] <magespawn> Golynx, maybe because those who have written programs in 2.x do not have the time to move them across. are the two interchangeable?
[19:08] <Golynx> magespawn some things are similar some not , which will break the program in a different version in python. i hate the print "mytext" instead of print("mytext")
[19:09] <magespawn> i do not know enough to be able to comment
[19:11] <Golynx> i do not know enough of python 2x to be able to live with it lol
[19:15] <magespawn> ha
[19:23] <Kilos> keep well magespawn , look after you man
[19:23] <Kilos> night all . sleep tight


[04:00] <feoh> Hi guys. Silly issue. I notice that the new Felicia the Focal Fossa background image is partially clipped on my 34" UHD monitor
[04:00] <feoh> Is that even worth reporting?
[10:26] <lotuspsychje> good morning


[00:43] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kdewebkit build #50: STILL FAILING in 3 min 49 sec: https://kci.pangea.pub/job/disco_unstable_kdewebkit/50/
[05:57] -kubuntu-ci:#kubuntu-devel- Project disco_stable_kcalcore build #70: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/disco_stable_kcalcore/70/
[05:58] -kubuntu-ci:#kubuntu-devel- Project eoan_stable_kcalcore build #20: STILL FAILING in 5 min 43 sec: https://kci.pangea.pub/job/eoan_stable_kcalcore/20/
[05:58] -kubuntu-ci:#kubuntu-devel- Project eoan_unstable_kcalcore build #18: STILL FAILING in 5 min 45 sec: https://kci.pangea.pub/job/eoan_unstable_kcalcore/18/
[05:59] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kcalcore build #56: FAILURE in 7 min 22 sec: https://kci.pangea.pub/job/disco_unstable_kcalcore/56/
[06:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:27] -kubuntu-ci:#kubuntu-devel- Project disco_stable_latte-dock build #81: FIXED in 29 min: https://kci.pangea.pub/job/disco_stable_latte-dock/81/
[06:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:27] -kubuntu-ci:#kubuntu-devel- Project eoan_stable_latte-dock build #20: FIXED in 29 min: https://kci.pangea.pub/job/eoan_stable_latte-dock/20/
[06:43] -kubuntu-ci:#kubuntu-devel- Project eoan_unstable_kcalcore build #19: STILL FAILING in 17 min: https://kci.pangea.pub/job/eoan_unstable_kcalcore/19/
[06:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:43] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kcalcore build #57: FIXED in 18 min: https://kci.pangea.pub/job/disco_unstable_kcalcore/57/
[06:50] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kdevelop build #59: STILL FAILING in 14 min: https://kci.pangea.pub/job/disco_unstable_kdevelop/59/
[06:50] -kubuntu-ci:#kubuntu-devel- Project eoan_unstable_kdevelop build #15: STILL FAILING in 14 min: https://kci.pangea.pub/job/eoan_unstable_kdevelop/15/
[06:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:57] -kubuntu-ci:#kubuntu-devel- Project disco_stable_kcalcore build #71: FIXED in 32 min: https://kci.pangea.pub/job/disco_stable_kcalcore/71/
[06:58] -kubuntu-ci:#kubuntu-devel- Project eoan_stable_kcalcore build #21: STILL FAILING in 32 min: https://kci.pangea.pub/job/eoan_stable_kcalcore/21/
[07:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:12] -kubuntu-ci:#kubuntu-devel- Project disco_stable_kdevelop build #74: FIXED in 36 min: https://kci.pangea.pub/job/disco_stable_kdevelop/74/
[07:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:12] -kubuntu-ci:#kubuntu-devel- Project eoan_stable_kdevelop build #22: FIXED in 36 min: https://kci.pangea.pub/job/eoan_stable_kdevelop/22/
[07:59] -kubuntu-ci:#kubuntu-devel- Project eoan_unstable_kdev-python build #14: STILL FAILING in 3 min 50 sec: https://kci.pangea.pub/job/eoan_unstable_kdev-python/14/
[07:59] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kdev-python build #24: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/disco_unstable_kdev-python/24/
[08:11] -kubuntu-ci:#kubuntu-devel- Project eoan_unstable_kdev-php build #14: STILL FAILING in 3 min 42 sec: https://kci.pangea.pub/job/eoan_unstable_kdev-php/14/
[08:11] -kubuntu-ci:#kubuntu-devel- Project disco_unstable_kdev-php build #63: STILL FAILING in 3 min 46 sec: https://kci.pangea.pub/job/disco_unstable_kdev-php/63/
[08:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:13] -kubuntu-ci:#kubuntu-devel- Project eoan_stable_kdev-python build #13: FIXED in 17 min: https://kci.pangea.pub/job/eoan_stable_kdev-python/13/
[08:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:14] -kubuntu-ci:#kubuntu-devel- Project disco_stable_kdev-python build #63: FIXED in 18 min: https://kci.pangea.pub/job/disco_stable_kdev-python/63/
 are the current packages build with mysql 8? or still 5.7 ?
[08:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:43] -kubuntu-ci:#kubuntu-devel- Project eoan_stable_kdev-php build #16: FIXED in 35 min: https://kci.pangea.pub/job/eoan_stable_kdev-php/16/
[08:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:43] -kubuntu-ci:#kubuntu-devel- Project disco_stable_kdev-php build #63: FIXED in 36 min: https://kci.pangea.pub/job/disco_stable_kdev-php/63/
 @myfenris, 5.7
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #3129: SUCCESS in 1 min 10 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/3129/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #3129: SUCCESS in 1 min 56 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/3129/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #3129: SUCCESS in 4 min 25 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/3129/
 👌🏻
[11:31] <BluesKaj> Howdy folks
[14:02] <RikMills> !testers
[14:02] <RikMills> http://iso.qa.ubuntu.com/qatracker/milestones/405/builds
[14:02] <RikMills> 18.04.3 isos need testing. thanks
[14:12] <genii> RikMills: Anything specific need testing?
[14:13] <RikMills> genii: firstly testcases not yet done. real hardware if you can, but VM ok if you can't. i386 tests would be nice, but I know that is not easy
[14:14] <RikMills> the repeats of ones already done, as you may/will have a different config
[14:14]  * genii rummages around for the tired old Atom netbook
[14:15] <RikMills> thanks for whatever you can manage, basically :)
[14:19] <BluesKaj> RikMills, what about testing on live media?
[14:19] <RikMills> live session is one of the tes cases
[14:19] <RikMills> *test
[14:20] <BluesKaj> ok
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #3130: SUCCESS in 1 min 3 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/3130/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #3130: SUCCESS in 1 min 35 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/3130/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #3130: SUCCESS in 4 min 23 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/3130/
[15:05] <genii> Weird, the 32bit iso is larger than the 64bit iso
[15:05] <genii> ..by like ~3G
[15:06] <BluesKaj> RikMills, ran usb bionic image live session on my Dell laptop, all seems fine so far
[16:04] <genii> I'm logged into the tracker and installing 32bit 18.04.3 successfully so far, but I'm not sure how to add info to the tracker
[16:15] <genii> Ah, figured it out now
[16:22] <genii> 32bit install doesn't prompt to remove installation media when completed, just reboots
[16:35] <genii> RikMills: Tested entire disk install and live session so far. Can probably do entire disk with lvm/encryption, and manual partition but the drive is tiny and no other OS on it to test install with auto-resize. Also, not sure if OEM setup requires alternate iso
 thanks. OEM uses normal iso
[17:03] <genii> Yeah just looking into it. Need to hold shift, etc etc
[17:05] <genii> Will do what tests I can on on the i386 today, installing over and over continuously is taking the most time right now, since the netbook has an old slow spinny-disk. Will keep plugging at it though
[17:05] <genii> ( right now it's chugging at the LVM+encryption install)
[17:15] <genii> 3 down, 3 to go ;)
[17:24] <RikMills> thank you!
[17:25] <RikMills> I will try to get to doing some later, but at the moment I can't
[17:25] <genii> Doing the manual partition install now
 I can test in about 8 hours.
[17:34] <genii> ..anyone know offhand... if I've manually partitioned 60G / 2G swap of a 120G drive and install that, then restart the install again and choose auto-resize will it use the other 58G for the new install, or will it only do this with a different OS on the first partition ( like Windows)
[17:38] <santa_> good evening everyone
[17:40] <santa_> RikMills: just FYI there's only a couple of glitches with fw 5.61 autopkgtests: an attica segfault @ i386 which I plan to investigate and an udisks2 which I plan to investigate
[17:40] <santa_> * an udisks2 bug
[17:41] <santa_> it fails to install inside an LXD container with -proposed enabled
[18:03] <genii> Meh, auto-resize is not an option now ( only the 3 "Guided" optins - entire disk, entire disk+LVM, entire disk encrypted LVM )
[18:32] <genii> RikMills: Looks like it needs to see some kind of DOS/MBR thing to give the resize option. So I'm going to dd a 2G Freedos image over to sda from liveusb, reboot and see if the resize is an option
[19:24] <genii> FreeDOS installed and boots from a 2G partition but install options still offer no resize option, only ones to use the entire disk
[19:36] <RikMills> santa_: thanks
[19:37] <RikMills> genii: no idea to be honest. I just normally test the resize option by doing a full install whole disk, then follow that with a side by side. that works
[19:44] <genii> RikMills: OK. I got stuck on this one, but then I'll skip it for now, do the OEM using the entire disk, then see if the resize option shows up after
[19:45] <genii> ..but very weird that it doesn't offer to dual-boot freedos
[19:56] <genii> OEM install mode must use some video mode different than normal install. Even when maximized I cannot see the buttons on the bottom of  the windows to click on them
[20:04] <genii> ..actually there's just enough of a sliver on the top of the buttons on the bottom showing to click on them
[20:12] <genii> RikMills: https://imgur.com/a/sbMbiPL shows the install windows and how they are cropped in OEM mode. This doesn't happen in normall install
[20:12] <genii> ..apologies on my crusty dusty old machine
 I don't think I have ever tried with that small a screen!
[20:13] <genii> I can see the entire window in normal mode
[20:24] <genii> Well, it managed to get installed even with the cropped windows. rebooting now to see it comes up OK, will try the resize option after
[20:38] <genii> RikMills: Resize is not an option. https://imgur.com/a/fT3EwX9
[20:40] <genii> ..in fact I have not seen it as an option at all even the first time when I already had Lubuntu 16.04 installed


[09:53] <jtv> hi adeuring!
[09:54] <jtv> got an oversized one for you I'm afraid.
[09:55] <jtv> It's really only two very simple changes, but the diff worked out rather large.
[09:55] <jtv> All context, very little actual change: 989 lines (+199/-169) 42 files modified
[09:58] <adeuring> jtv: yeah, I've noticed that. Sorry for the dealy with this repsonse -- needed to make a cup of coffee
[09:58] <adeuring> s/dealy/delay/
[10:17] <adeuring> jtv: r=me
[10:19] <jtv> adeuring: thanks!
[11:46] <jtv> adeuring: up for another one?   https://code.launchpad.net/~jtv/launchpad/bug-668194-fix-api/+merge/39615
[11:46] <adeuring> jtv: sure
[11:46] <jtv> thanks
[12:13] <adeuring> jtv: r=me
[12:13] <adeuring> On call: adeuring || Reviewing: - || queue: [] || This channel is logged: http://irclogs.ubuntu.com/ || https://code.launchpad.net/launchpad/+activereviews
[12:14] <jtv> adeuring: thanks once more!
[14:05] <henninge> adeuring: Hallo! ;)
[14:05] <adeuring> moin henninge
[14:06] <henninge> adeuring: Wärst du so nett, bitte? https://code.edge.launchpad.net/~henninge/launchpad/devel-bug-638920-private-branch/+merge/39540
[14:06] <henninge> ;-)
[14:06] <adeuring> henninge: klar!
[14:07] <henninge> adeuring: I'll be switching locations now but will be back here soon.
[14:07] <adeuring> henninge: ok
[14:39] <henninge> adeuring: Hi, I am back!
[14:40] <henninge> adeuring: Is the topic lying or are you still working on one of jtv's branches?
[14:40] <jtv> henninge: the topic is outdated
[14:40] <jtv> feel free to change it
[14:40] <adeuring> henninge: ouch, I'm looking at your branch...
[14:42] <henninge> adeuring: cool ;-)
[14:42] <adeuring> henninge: I've sent a comment about your  branch
[15:18] <jtv> adeuring: did you accidentally post your comment on henninge's branch on my MP?
[15:19] <adeuring> jtv: gaahhh, thanks for the head-up ...and sorry for the noise!
[15:54] <henninge> adeuring: oh sorry, sound turned off and not paying attention.
[15:55] <henninge> adeuring: you are raising a basic question there that will need discussion on the mailing list, I think.
[15:56] <henninge> adeuring: Are you ok with the branch if I just add the comments as you requested and leave it to a future branch to reflect the outcome of that discusstion?
[16:00] <adeuring> henninge: yes, that's fine, I think
[16:01] <henninge> adeuring: cool, thanks.
[16:10] <henninge> adeuring: Maybe for symmetrie I should turn has_exports_enabled and uses_bzr_sync into properties, too?
[16:10] <adeuring> henninge: yes, that would be great!
[16:21] <henninge> adeuring: done. Thank you very much for the review. ;-)
[16:21] <adeuring> henninge: welcome :)
[17:12] <EdwinGrubbs> adeuring: can you review https://code.edge.launchpad.net/~edwin-grubbs/launchpad/bug-663861-product-series-timeout-part2/+merge/39638
[17:13] <adeuring> Edwinsure
[17:13] <adeuring> EdwinGrubbs: sure
[17:20] <adeuring> EdwinGrubbs: can the strings that are soted contain caracters outside the usual ASCII set? (like 'ö')?
[17:31] <EdwinGrubbs>  adeuring: I'll check, but I don't think the productseries.name is even allowed to contain those characters.
[17:34] <EdwinGrubbs> adeuring: the valid_name() constraint only allows a-z, 0-9, "+", ".",  and "-".
[17:34] <adeuring> EdwinGrubbs: ah, OK. That makes the sorting more robust :)
[17:36] <adeuring> EdwinGrubbs: but I think your example sorting [devfocus, 1, c] doesn't work. I believe the sort order will be [devfocus, c, 1]
[17:36] <adeuring> EdwinGrubbs: never mind... misunderstood "devfocus"
[17:37] <adeuring> EdwinGrubbs: but how is the code in the file interfaces/branchmergeproposal.py related to the other changes?
[17:41] <EdwinGrubbs> adeuring: doh, I made the merge-proposal against devel, when it should be against db-devel. That's why you see branchmergeproposal.py, which I didn't touch. Let me redo the mp.
[17:41] <adeuring> EdwinGrubbs: Ahh, ok :)
[17:46] <EdwinGrubbs> adeuring: here is the new mp: https://code.edge.launchpad.net/~edwin-grubbs/launchpad/bug-663861-product-series-timeout-part2/+merge/39643
[17:46] <adeuring> EdwinGrubbs: thanks!
[18:05] <adeuring> EdwinGrubbs: r=me; one minor suggestion
[18:05] <EdwinGrubbs> adeuring: thanks
[20:00] <henninge> Anybody up for a 25 lines review?
[20:00] <henninge> https://code.edge.launchpad.net/~henninge/launchpad/devel-bug-666660-poimport-oops/+merge/39653
[20:04] <StevenK> henninge: I've +1'd it, but I need to be mentored
[20:04] <henninge> StevenK: thanks ;)
[20:04] <henninge> StevenK: how is you mentor?
[20:04] <henninge> hang on
[20:05] <StevenK> thumper, the problem is it's Saturday for him
[20:05] <henninge> nm
[20:05] <henninge> ;)
[20:12] <henninge> StevenK: thanks for taking care of this. I will start my weekend now. Enjoy your Saturday! ;)
[20:12] <StevenK> henninge: I'm at UDS, and it's 3pm :-)
[20:13] <StevenK> So my Saturday will involve stacks of airports and I won't enjoy it.
[20:13] <henninge> StevenK: Oh, then enjoy Marks closing remarks and the last night out with the guys ... ;)
[20:14] <henninge> StevenK: say hello to Danilo for me ;)
[20:14] <StevenK> henninge: I shall


[06:00] <mup> PR snapd#12664 opened: cmd/snap-bootstrap: Add support for snaps with integrity data <Created by sespiros> <https://github.com/snapcore/snapd/pull/12664>
[10:31] <mup> PR snapd#12654 closed: asserts: add code for Fetcher to support the fetching of sequence-forming assertions <Squash-merge> <Pulse> <Created by Meulengracht> <Merged by Meulengracht> <https://github.com/snapcore/snapd/pull/12654>
[12:07] <mup> PR snapd#12665 opened: image,store: introduce AssertionSequenceFormingFetcher in ToolingStore <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/12665>
[12:22] <mup> PR snapd#12659 closed: asserts: add ResolveUnknown method to asserts.AtSequence <Created by Meulengracht> <Closed by Meulengracht> <https://github.com/snapcore/snapd/pull/12659>
[12:37] <mup> Issue # opened: snapcraft#100, snapcraft#1438, snapcraft#1440, snapcraft#1441, snapcraft#1449, snapcraft#1450, snapcraft#1451, snapcraft#1455, snapcraft#1456, snapcraft#1458, snapcraft#1459, snapcraft#1460, snapcraft#1461, snapcraft#1463, snapcraft#1465, snapcraft#1467, snapcraft#1468,
[12:37] <mup> snapcraft#1469, snapcraft#1476, snapcraft#1477, snapcraft#1502, snapcraft#1658, snapcraft#1660, snapcraft#1665, snapcraft#1677, snapcraft#1678, snapcraft#1679, snapcraft#1696, snapcraft#1701, snapcraft#1705, snapcraft#1706, snapcraft#1715, snapcraft#1751, snapcraft#1753, snapcraft#1794,
[12:37] <mup> snapcraft#1882, snapcraft#1887, snapcraft#1921, snapcraft#1932, snapcraft#2001, snapcraft#2027, snapcraft#2032, snapcraft#2048, snapcraft#2118, snapcraft#2133, snapcraft#2134, snapcraft#2136, snapcraft#2137
[12:37] <mup> PR snapcraft#4068 closed: meta: allow support for `build-base: devel` <Created by mr-cal> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/4068>
[12:42] <mup> Issue # closed: snapcraft#100, snapcraft#1450, snapcraft#1451, snapcraft#1455, snapcraft#1456, snapcraft#1458, snapcraft#1459, snapcraft#1460, snapcraft#1461, snapcraft#1463, snapcraft#1465, snapcraft#1467, snapcraft#1468, snapcraft#1469, snapcraft#1476, snapcraft#1477, snapcraft#1502,
[12:42] <mup> snapcraft#1658, snapcraft#1660, snapcraft#1665, snapcraft#1677, snapcraft#1678, snapcraft#1679, snapcraft#1696, snapcraft#1701, snapcraft#1705, snapcraft#1706, snapcraft#1715,
[12:42] <mup> snapcraft#1751, snapcraft#1753, snapcraft#1794, snapcraft#1882, snapcraft#1887, snapcraft#1921, snapcraft#1932, snapcraft#2027, snapcraft#2032, snapcraft#2137
[12:47] <mup> Issue # closed: snapcraft#1438, snapcraft#1440, snapcraft#1441, snapcraft#1449, snapcraft#2118, snapcraft#2133, snapcraft#2134, snapcraft#2136
[13:42] <mup> PR snapd#12623 closed: gadget: check volume compatibility using gadget volume instead of laid out data <Run nested> <Created by alfonsosanchezbeato> <Merged by alfonsosanchezbeato> <https://github.com/snapcore/snapd/pull/12623>
[15:13] <mup> PR snapd#12666 opened: secboot: use experimental mvo5/secboot:uc22-sbat-workaround branch <Run nested> <Created by mvo5> <https://github.com/snapcore/snapd/pull/12666>
[19:59] <mup> PR snapd#12665 closed: image,store: introduce AssertionSequenceFormingFetcher in ToolingStore <Squash-merge> <Pulse> <Created by Meulengracht> <Merged by Meulengracht> <https://github.com/snapcore/snapd/pull/12665>
[22:05] <mup> PR snapd#12647 closed: tests: new invariant check to validate the test did not produce a segmentation violation <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/12647>
[22:35] <mup> PR snapd#12667 opened: image,seed: refactor RefAssertsFetcher <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/12667>


[05:04] <average> so .. any ops here ?
[05:04] <average> some dude got upset yesterday and I got banned from #ubuntu
[05:04] <average> kinda sucks..
[05:04] <average> anyway
[05:05] <average> tried to use eir to see when the ban expires
[05:05] <average> no such luck
[05:05] <average> meh
[05:05] <average> gonna leave if nobody's gonna answer
[05:05] <average> noone ? ok
[19:24] <CarlyS> !op
[19:24] <CarlyS> !ops


[00:58] <azend> Seven_Six_Two: I need longer days too
[00:58] <azend> you should hook up with the unlab
[00:58] <azend> they're awesome and they support linux
[01:22] <Seven_Six_Two> oh nice. thanks!
[12:18] <azend> Seven_Six_Two: they're in #unlab
[18:50] <genii> The coffee people among you are welcome in ##coffeeclub :)
[18:54] <BobJonkman> Coffee!


[19:06] <Unit193> wrst: You use dracut, right?
[19:06] <wrst> what is that? :)
[19:07] <Unit193> The thing that makes your initrd.  In ubuntu it's initramfs-tools
[19:10] <Unit193> wrst: I forced it into an Ubuntu system this morning, a system with systemd. :P
[19:13] <wrst> oh I have no clue then Unit193
[19:13] <wrst> I leave that stuff alone and it just works :)
[19:14] <Unit193> Soooo, I think I basically just changed bases entirely.  upstart -> systemd, initramfs-tools -> dracut, generic kernsls -> liquorix (half the time or so, really.)
[19:24] <wrst> Unit193: I think you have issues :)
[19:24] <Unit193> Yes, yes I do.  After I figured out I'd basically replaced the base, I wondered what else I could replace. >_<
[19:25] <Unit193> Worst part?  It's still stable...
[19:25] <wrst> why do you even start with a base?
[19:25]  * wrst thinks Unit193 might be a gentoo candidate
[19:27] <Unit193> wrst: Nono, I'm an Ubuntu user!
[19:43] <wrst> in splash screen only Unit193
[21:24] <wrst> Unit193: I thinki I have firefox os installed on my phone
[23:05] <Unit193> wrst: ...You think?
[23:14] <wrst> yes I actually did, just didn't pick up the sim card
[23:15] <wrst> but looks not so bad, I would say its ahead of ubuntu  at the moment, but ubuntu i can actually make calls so there is that advantage
[23:15] <wrst> neither is close to android or ios however
[23:15] <Unit193> Hah.


[00:27] <valorie> CoJaBo: keep in mind things are tested before release
[00:27] <valorie> we don't just put untested stuff into the archive
[01:23] <CoJaBo> valorie:  the installer didn't give that impression lol
[02:52] <valorie> CoJaBo: we tested and so did others
[02:53] <valorie> however, more testers are always need
[02:54] <CoJaBo> valorie: If you install to a drive other than the first, it nukes the first drive btw
[02:54] <valorie> well, I did that
[02:54] <valorie> and my main install was *NOT* nuked
[02:54] <valorie> on this very machine
[02:56] <valorie> the installer is not our software
[02:56] <valorie> so lots of people are testing it
[02:56] <valorie> I have not heard of anyone else experiencing what you describe
[02:59] <keithzg[m]> CoJaBo: You should definitely search https://bugs.launchpad.net/ubuntu/+source/ubiquity for the problem you encountered, and comment with helpful details on an existing issue if there is one and create a new one if there isn't.
[02:59] <valorie> thanks for beating me to saying that, keithzg[m]
[02:59] <keithzg[m]> :)
[02:59] <valorie> bug reports are valuable
[02:59] <valorie> and appreciated
[02:59] <CoJaBo> Not sure exactly what I did, but it overwrote the bootloader at least
[03:00] <CoJaBo> I was trying to do a custom install, but with LVM; and it kept crashing
[03:01] <valorie> did you try grub-repair?
[03:01] <valorie> !grub-repair
[03:01] <valorie> err
[03:02] <valorie> !grub
[03:02] <valorie> the restore grub link above, CoJaBo
[03:03] <CoJaBo> valorie: It was a Windows install
[04:46] <trie> https://youtu.be/z1PVeiH_yXs
[06:35] <trophy> https://youtu.be/jWHuFuuYHso
[06:35] <trophy> ^ YouTube :: The Ultimate Red Pill :: Duration: 01:18:12 :: Views: 194,265 uploaded by EstelleNation :: 5,044 likes :: 893 dislikes :: 0 favorites
[06:36] <trophy> Beautifully produced work of truth.
[06:42] <moon8782> The Holocaust narrative is protected by law in 24 countries or whatever it is to keep us from saying openly, "Hey, it's the Jews!" See "Slowly Boiled Frogs" on channel ladyloverlyf5. That history teacher spells it out. The victimizers have mastered the art of playing the victims.
[06:42] <oerheks> moon8782, wrong channel dude
[06:46] <civilIp> "Lord God, give us the strength that we may retain our liberty for our children and our children's children, not only for ourselves but also for the other peoples of Europe, for this is a war which we all wage, this time, not for our German people alone, it is a war for all of Europe and with it, in the long run, for all of MANKIND."  | https://youtu.be/jWHuFuuYHso | 200,000 views in <2 months | Banned in CH, AU, DE, +
[07:15] <lordievader> Good morning
[09:14] <jmid> Everything I was told was a LIE...|| CENSORED IN DE, CH, AU, ... || https://hooktube.com/watch?v=jWHuFuuYHso || The Ultimate Red Pill || "Th truth is *all* that matters"
[09:16] <OwenBarfield> yes
[11:35] <keithzg[m]> Hmm I don't remember how to disable the silly notifier that tries to get me to install Flash for the sake of Firefox.
[11:37] <keithzg[m]> Oh, there we go, right-clicking got a "never show this again" option, not sure how I didn't see that before, hah
[13:05] <BluesKaj> Howdy folks
[16:01] <ambient> Anyone home?
[16:04] <ambient> I tried to update and got the following: https://pastebin.com/Pd1mhGWF
[16:05] <ambient> How to rectify?
[16:52] <ambient> Anyone home?
[16:53] <rgb-one> Hey
[16:54] <ambient> Woek up to this error code I cannot get rid of: https://pastebin.com/jvdaYQ1d
[16:55] <ambient> I looked it up and there seems to be no way to get rid of it
[16:55] <ambient> short of reinstalling
[16:55] <ambient> I rebooted many times, despite what the message says, it will not go away
[17:03] <rgb-one> ambient: It has something to do with the application drbdlinks
[17:03] <rgb-one> maybe try reloading it?
[17:04] <ambient> rgb-one, I uninstalled and reinstaled it
[17:04] <ambient> I purged and put it back in
[17:04] <ambient> nadda
[17:04] <ambient> I think it has something to do with systemd
[17:05] <ambient> I can't wait until other distros get the 4.10 kernel so I can leave Ubuntu
[17:05] <rgb-one> Something to do with the service file maybe
[17:08] <ambient> Something to do with Ubuntu
[17:08] <ambient> : - D
[17:08] <ambient> Birds fly in the air and Ubuntu breaks


[04:37] <mwhudson> cjwatson: til (well maybe more like yil) that pc105.tree is generated by a script you wrote in like 2006 :)
[10:45] <cjwatson> mwhudson: I'm sorry
[10:46] <cjwatson> mwhudson: (it is all a bit dense ...)
[10:52] <mwhudson> cjwatson: oh i didn't try to read it!
[10:54] <cjwatson> mwhudson: very wise
[10:56] <cjwatson> mwhudson: I think the hard work was done by Matthias Urlichs in 2005 (though I have ended up maintaining that somehow)
[11:01] <mwhudson> cjwatson: ah yes, i hadn't even really noticed that the real work is done by a different package entirely :)
[13:54] <sforshee> apw, xnox: I've got wireless-regdb updates if one of you would care to sponsor them: bug 1941955
[15:43] <dbungert> ginggs: I see you've run the vip-manager/armhf tests a few times - I ran this locally in an armhf container and the test passes there.  Do you think this is related to the test env image rebuild being discussed?
[15:44] <ginggs> dbungert: quite possible
[15:44] <ginggs> vip-manager's autopkgtest regressed in release, but only on armhf
[15:47] <ginggs> listparser/armhf regressed as well
[20:21] <ItzSwirlz> Hey everyone, the Ubuntu Cinnamon Remix ISO builder is failing. I'm not sure why, and I don't want to be excluding apt packages, and the issue is base. Packages like bass-passwd are being extracted but a file already exists and it's causing it to fail... anyone got any ideas? https://github.com/Ubuntu-Cinnamon-Remix/iso-builder/runs/3465676747?check_suite_focus=true
[20:40] <cjwatson> ItzSwirlz: If I were you I would look at the earlier warning "W: The following is not a valid stage: 'false'" first, because I wonder if that might relate to a failed attempt to disable caching for the bootstrap stage, which might then mean that a cache is being extracted and in turn then explain why a file already exists
[20:40] <cjwatson> (this is just a guess)
[20:41] <ItzSwirlz> I guess it's worth a shot. lb has changed a lot recently
[20:42] <cjwatson> Also just in general I think it's often worth looking at earlier warnings/errors first, since later ones can be consequences
[21:05] <TJ-> ItzSwirlz: does the lack of quote marks around the  --apt-options in the lb command line, vs those options contained inside "..." in the config file, cause a knock-on effect?
[21:28] <TJ-> ItzSwirlz: your problem is "--cache-stages false" -- sources shows it should be " \t    [--cache-stages STAGE|\"STAGES\"]\n "
[21:28] <ItzSwirlz> uhhh... ok
[21:30] <ItzSwirlz> TJ-: are you saying that is what needs to go in the quotes?
[21:33] <TJ-> not sure! just looking and suggesting. I /think/ the man-page is out of sync with the code since "man 1 lb_config" shows  --cache-stages true|false|STAGE|"STAGES"
[21:33] <TJ-> but the code as pasted above doesn't include true|false
[22:15] <jawn-smith> mwhudson: the original openssh bug was LP: #1939751. While working that I did a submittodebian, which they have since merged. So now instead of applying that patch we're just doing a merge: LP: #1941799
[22:35] <mwhudson> jawn-smith: looks like bryceh beat me to it!
[22:43] <jawn-smi1> oh look at that, thanks bryceh!
[22:43] <bryceh> heya, yeah noticed it doing server team bug triage.  Hope I didn't step on any toes!
[22:43] <mwhudson> nope, i just got asked to look at it
[22:43] <mwhudson> but happy for someone else to have done it already :)
[22:44] <bryceh> yep cool.  only thing I noticed was the dep8 tests failed for me, but possibly that's a local environment thing.  But keep an eye on update-excuses.
[22:47] <jawn-smi1> I had run tests on armhf, arm64, and amd64 so I think they're alright. I did the armhf tests with and without the diff we carry as well to make sure it was still necessary
[22:47] <jawn-smi1> But I'll still keep an eye out!
 ah excellent, then it's probably fine.  I wondered if you might have already run them.