[06:47] <jamespage> cpaelzer: I have a 2.9 snapshot in a PPA
[06:47] <jamespage> but its failing some tests on arm64 atm
[06:48] <jamespage> https://launchpad.net/~james-page/+archive/ubuntu/bionic/+packages
[06:48] <cpaelzer> ok, thanks for the info
[06:48] <jamespage> first thing I normally do with a new release is re-enable all of the skipped tests and try them out again
[10:03] <jamespage> anyone around who has some familiarity with debhelper, dpkg, debug symbols and how that works in PPA's which generate and publish them?
[10:05] <jamespage> I'm endeavouring to backport debhelper >= 11 to xenial for the Ubuntu Cloud Archive, but I'm missing something in the dance between debhelper, pkgbinarymangler and pkg-create-dbgsym
[10:12] <jamespage> I'm aware there are alot of dpkg changes between xenial and bionic including the one to support Package-Type overrides which debhelper uses at bionic but hoping to avoiding including dpkg in the backport...
[11:30] <doko> cjwatson: man-db ftbfs on ppc64el
[11:36] <jamespage> meh no worries - figured it out and have enough of a compat shim for the backport
[11:38] <infinity> jamespage: Erm.
[11:38] <infinity> jamespage: Backporting debhelper should revert the ddeb support.
[11:38] <infinity> jamespage: Any other option will end in tears.
[11:39] <jamespage> infinity: yeah I'd got that - the piece I'd missed was the change to dh_strip to stop debhelper building the debug packages
[11:39] <jamespage> "+$dh{ENABLE_DBGSYM} = 0 if not $ENV{'DH_BUILD_DDEBS'};"
[11:39] <jamespage> was my friend
[11:40] <jamespage> infinity: I think this - http://paste.ubuntu.com/26524058/ does the trick
[11:40] <infinity> jamespage: https://launchpad.net/ubuntu/+source/debhelper/10.2.5ubuntu2 was where I swapped methods.
[11:40] <doko> mwhudson: golang-1.10 ftbfs on armhf
[11:41] <infinity> jamespage: Yep, that looks like it should do it.
[11:41] <jamespage> infinity: I'd generally got a bit confused as to which parts pkg-create-dbgsym, debhelper and pkgbinarymangler did
[11:41] <jamespage> them diverts ...
[11:42] <jamespage> anyway I now know (at least I think I do)
[11:42] <infinity> jamespage: The pkgbinarymangler dpkg-deb divert is not one of my prouder moments.  Don't look at that postinst if you value your sanity.
[11:42] <jamespage> lol
[11:43]  * jamespage shuts his eyes and just holds on for a bit
[11:43] <infinity> jamespage: (The part where there's a brief period on every single buildd build where dpkg-deb doesn't exist, in the middle of unpacking, is... Fun)
[11:43] <jamespage> infinity: I also enjoyed the bit where pkgbinarymangler copies in part of debhelper as part of its build
[11:45] <jamespage> coreycb: I think I have it nailed now - just working the updates into queens-staging to unbreak all the broken builds from friday...
[12:05] <cjwatson> doko: already dealt with in Debian; it'll auto-sync
[12:39] <coreycb> jamespage: great thanks. so will the ppa still be able to generate ddebs?
[13:14] <jamespage> coreycb: yes
[13:15] <coreycb> jamespage: ok cool
[14:01] <GunnarHj> chrisccoulson: Have you seen that adobe-flashplugin is stuck in -proposed?
[14:03] <GunnarHj> https://community.ubuntu.com/t/flash-version-in-xenial-partner-archive-canonical-com/3865
[15:54] <ackk> cjwatson, hi, I have a refreshed patch for py-macaroon-bakery 1.1.0: https://pastebin.canonical.com/209182/ I can build the updated package with it. would it be possible for you to update it?
[15:58] <mitya57> cyphermox, doko: do you have any status update on bug 1636666? can you please reply to my comment there?
[15:58] <ackk> cjwatson, or, https://paste.ubuntu.com/26525107/
[15:58] <cjwatson> ackk: Yeah, I guess I can just go with that, just a minute
[15:59] <doko> mitya57: can it be built using pcre3?
[15:59] <mitya57> No :(
[15:59] <doko> and how much in main can be built using pcre2?
[16:00] <cjwatson> ackk: (I had half of that but was missing the other half, it seems, not sure why)
[16:00] <mitya57> http://doc.qt.io/qt-5/whatsnew59.html — “QRegularExpression now requires the PCRE2 library version 10.20, or later. Support for the PCRE1 library was dropped.”
[16:00] <doko> so how much can we rebuild? http://people.canonical.com/~ubuntu-archive/transitions/html/pcre2.html
[16:01] <mitya57> There is some estimate in https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1636666/comments/20
[16:01] <mitya57> That is at least half of the packages from that tracker
[16:02] <doko> who is working on that to build packages with pcre2 if they can?
[16:03] <mitya57> I can try to help with that, maybe jbicha and/or LocutusO- would be able to help too.
[16:04] <mitya57> apache2 may be a problem though: https://bz.apache.org/bugzilla/show_bug.cgi?id=57471
[16:04] <cjwatson> ackk: Yep, thanks, that works, will upload
[16:05] <ackk> cjwatson, thank you
[16:05] <cjwatson> done
[16:06] <mitya57> doko: I meant at least half of packages from *this* tracker: http://people.canonical.com/~ubuntu-archive/transitions/html/pcre2-main.html (your link includes also universe)
[16:07] <doko> ahh, I see
[16:07] <ackk> cjwatson, awesome, thanks
[16:07] <mitya57> exim4 may be a problem too: https://bugs.exim.org/show_bug.cgi?id=1878
[16:08] <mitya57> I guess I should collect some bug links and add them to the description
[16:08] <jbicha> no one is working on getting glib to not use pcre3
[16:10] <jbicha> on the other hand, tilix and gnome-builder have missing features because Ubuntu's vte2.91 isn't allowed to use pcre2 yet
[16:10] <doko> php7.2 is missing in this tracker
[16:10] <doko> silly gnome
[16:11] <jbicha> the main tracker is manually compiled so you're welcome to add php7.2 if you like :)
[16:11] <mitya57> So we have two solutions here: 1) Have both pcre3 and pcre2 in main, with a goal of removing pcre3 in later release, 2) Have only pcre3, Qt using its own copy and GNOME missing some features
[16:12] <chrisccoulson> GunnarHj, ah, crap. Thanks for that. sil2100, can you take care of that please? (I think you approved the upload originally)
[16:13] <chrisccoulson> sil2100, if you can't see the scrollback:
 chrisccoulson: Have you seen that adobe-flashplugin is stuck in -proposed?
 https://community.ubuntu.com/t/flash-version-in-xenial-partner-archive-canonical-com/3865
[16:13] <mitya57> Looks like php7.2 supports only pcre3 and php7.3 only supports pcre2
[16:13] <jbicha> Qt is in main because of qtubuntu (kiosk project) and mozc (Japanese input method)
[16:14] <mitya57> And php7.3 is not going to be released any time soon…
[16:15] <sil2100> chrisccoulson: hey, for this I think you'll need slangasek
[16:18] <doko> jbicha, mitya57: I would like to avoid a situation where we have both in main, and everybody is comfortable with it
[16:19] <mitya57> I understand, but the goal porting everything to pcre2 does not seem achievable in one release cycle
[16:19] <jbicha> the current vte2.91 situation isn't comfortable :/
[16:20] <mitya57> Even if we keep pcre2 in universe for this cycle, next time php7.3 will be released and we'll get in the same situation
[16:20] <doko> so do the promotion after the bionic release?
[16:21] <mitya57> I won't mind that, but we will technically have pcre2 in main as part of Qt anyway
[16:21] <doko> or get some buy-in from the tech board and the security team
[16:41] <mitya57> doko: I just added lists of good/bad packages to the description of bug 1636666
[16:42] <mitya57> (It is worse than I thought, most of packages don't even have upstream bugs filed for pcre2 move)
[16:42] <chrisccoulson> sil2100, you should be able to do it (https://wiki.ubuntu.com/ArchiveAdministration#Handling_updates_to_partner)
[17:25] <bdmurray> Why does rmadison still show zesty information?
[17:36] <cjwatson> bdmurray: needs manual editing of snakefruit:~ubuntu-archive/.madison-lite/config.  Fixed now
[17:36] <nacc> (should that be added to the EOL checklist, if not already there?)
[17:37] <bdmurray> cjwatson: thanks
[17:38] <slangasek> chrisccoulson: "stuck in proposed" - so you're saying that the adobe-flashplugin versions in *-proposed are tested and ready to copy to release?
[17:38] <chrisccoulson> slangasek, yeah
[17:39] <doko> mitya57: thanks! so I'm still not sure if it's better to delay that promotion until after bionic
[17:39] <bdmurray> nacc: Its not there https://wiki.ubuntu.com/EndOfLifeProcess
[17:40] <nacc> bdmurray: ack; i feel like that's probably the release team's page to edit :)
[17:40] <bdmurray> nacc: whatever, I'm gonna edit it
[17:40] <slangasek> chrisccoulson: done
[17:40] <chrisccoulson> slangasek, thanks
[17:41] <nacc> bdmurray: :)
[17:59] <cjwatson> bdmurray: process> good call, thanks
[19:41] <coolfish> hi, approx. on Fri 26. January I asked on #ubuntu-devel, what I can do, to put the package ganeti on a list for 'big' packages for autopkgtest(-VMs). The reason is http://autopkgtest.ubuntu.com/packages/g/ganeti/bionic/amd64. I've verified, that autopkgtest passed with 4GB of RAM. The default of 1536MB is to small.
[19:41] <coolfish> because I'm no dev (just a user), someone on this channel said, that he has done it for me. Now (2018-02-05 15:13:30 UTC) the test still fails, with the error message: Not enough memory on node node1 for creating instance instance1: needed 1024 MiB, available 810 MiB
[19:41] <coolfish> so it seems, ganeti is still with default size autopkgtest-VM
[20:59] <doko> nacc: I removed kopanocore, so zeroc-ice is the only one not building for php7.2. but mumble depends on that one
[21:10] <acheronuk> nice. lintian in bionic proposed is uninstallable
[21:11] <acheronuk> https://paste.ubuntu.com/26526608/
[21:13] <sarnold> ssleay
[21:13] <sarnold> oy
[21:14] <nacc> doko: removed as in from the archive?
[21:15] <nacc> doko: or in which sense? I have fixes for it pending (which I will send to Debian in the bug you filled), but it's segfaulting in my testing (not sure if it's related to PHP yet
[21:16] <nacc> doko: i'm also workig onn zeroc-ice, which needs to be updated to 3.7.0 at lelast


[14:50] <Routhinator> Based on the messaging in #conjure-up I'll ask here: Hi folks, wondering if it's possible to use conjure-up against SSH targets, or if the localhost mode of kubernetes-core can do two baremetal machines for a dev cluster? I'm getting the idea that it's going to setup two LXD nodes on the baremetal box.. while that might not be bad (I guess I could
[14:50] <Routhinator> have two nodes on each baremetal box) I kinda wanted to give kube 100% of the resources of each baremetal host.


[00:33] <mup> Bug #1549545 opened: Bundle deploys fail at lxc-start when bridge br-eth1 is created <ci> <deploy> <maas-provider> <test-failure> <juju-core:New> <https://launchpad.net/bugs/1549545>
[00:34] <natefinch> katco, ericsnow:  the PR for the missing API field: http://reviews.vapour.ws/r/3961/
[00:36] <ericsnow> natefinch: LGTM
[00:36] <natefinch> ericsnow: nice, thanks!
[00:36] <mup> Bug #1549545 changed: Bundle deploys fail at lxc-start when bridge br-eth1 is created <ci> <deploy> <maas-provider> <test-failure> <juju-core:New> <https://launchpad.net/bugs/1549545>
[00:45] <mup> Bug #1549545 opened: Bundle deploys fail at lxc-start when bridge br-eth1 is created <ci> <deploy> <maas-provider> <test-failure> <juju-core:New> <https://launchpad.net/bugs/1549545>
[00:59] <natefinch> ericsnow: you still around?
[01:01] <wallyworld> axw: adding the restriction that controller name must exist in SetController() causes a lot of test failures \o/ i'm going through and fixing those
[01:01] <axw> wallyworld: hm :/  do you agree that it should fail though?
[01:02] <wallyworld> axw: nope :-)
[01:02] <wallyworld> yes
[01:02] <wallyworld> sorry, i meant yes
[01:02] <axw> lol
[01:02] <axw> the other nope
[01:02] <wallyworld> nope that we shound't fail
[01:02] <axw> ok
[01:02] <wallyworld> the fact that we never checked needs to be fixed
[02:21] <tych0> jam: https://github.com/juju/juju/pull/4526 is what i've got for now
[02:21] <tych0> it seems to bootstrap and deploy stuff
[02:21] <tych0> jam: I think (?) it should fix most of your concerns
[03:09] <menn0> wallyworld: is there any documentation on how to actually bootstrap at the moment
[03:09] <menn0> wallyworld: with lxd not working i'm trying aws
[03:09] <wallyworld> menn0: the release notes are very comprehensive :-)
[03:09] <menn0> wallyworld: but it keeps trying to use the EC2 environment variables instead of what's in credentials.yaml
[03:10] <wallyworld> where is credentials.yaml  located?
[03:10] <wallyworld> can you pastebin it?
[03:11] <menn0> wallyworld: I checked the release notes first. They only say that bootstrap and credentials has changed with no details
[03:11] <menn0> juju help bootstrap is also no help
[03:11]  * menn0 gets pastes
[03:11]  * menn0 pastes even
[03:11] <wallyworld> menn0: the release notes have an example credentials.yaml file, what ones are you looking at?
[03:11] <menn0> beta1
[03:12] <wallyworld> let me check them
[03:12] <menn0> wallyworld: ok I see
[03:12] <menn0> it's further down
[03:13] <wallyworld> yeah, there's a whole essay on the new bootstrap stuff
[03:13] <wallyworld> i have had it confirmed that if you follow the directions it does all work :-)
[03:13] <wallyworld> but maybe some more consice getting started docs would have helped
[03:14] <menn0> wallyworld: http://paste.ubuntu.com/15193666/
[03:14] <menn0> that's what I get
[03:14] <menn0> the credentials.yaml looks right to me
[03:15] <menn0> (I've redacted the secret bits obviously)
[03:15] <wallyworld> looks ok at first glance, i'll dig in a bit
[03:15]  * menn0 wonders if it works for wallyworld because he has $AWE_SECRET_ACCESS_KEY set
[03:16] <menn0> $AWS... even
[03:16] <wallyworld> maybe, but it was tested without i am almost sure, but not 100%
[03:16] <wallyworld> menn0: you are missing the credentials:
[03:16] <wallyworld> at the top of the yaml
[03:17] <menn0> wallyworld: that would do it :)
[03:17] <wallyworld> let me know if it still is broken
[03:19] <menn0> wallyworld: looking better
[03:19] <wallyworld> \o/
[03:20] <menn0> wallyworld: thanks for your help
[03:20] <wallyworld> np
[03:20] <menn0> wallyworld: I think the client should emit a useful error when credentials.yaml doesn't start with a credentials section
[03:21] <menn0> wallyworld: shall I file a bug about it?
[03:21] <menn0> I suspect I won't be the only one making this mistake
[03:21] <wallyworld> menn0: agree, but we also have several other yaml files we omit crappy errors for. i'd like to tackle that improvement wholistically
[03:21] <wallyworld> and if it's not that error, there could be 100s of other syntactical issues
[03:22] <wallyworld> on the whole, juju's error reporting has a lot to answer for
[03:22] <menn0> wallyworld: in this case the YAML was syntactically correct. The first section just wasn't what the client expects.
[03:23] <wallyworld> fair point. but the same could happen in any yaml file juju likes to read. the user should be editing such files. beta2/3/4 will gain CLI to do that work. go ahead and file a bug if you want though
[03:23] <wallyworld> shouldn't
[03:24] <menn0> ok, if the user won't be touching the file soon, then I won't bother with the bug
[03:24] <wallyworld> "soon" :-)
[03:33] <wallyworld> axw: could you ptal at http://reviews.vapour.ws/r/3954/
[03:34] <axw> wallyworld: looking
[03:34] <wallyworld> ta
[03:44] <axw> wallyworld: done
[03:44] <wallyworld> ta
[03:46] <wallyworld> axw: damn, that plural is invisible to me :-/ will fix. need glasses
[03:46] <wallyworld> part 2 will get into the workflow proper, multiple clouds etc
[03:46] <wallyworld> just wanted to get the skelton for part 1
[03:46] <axw> wallyworld: thanks. ok, sounds good
[03:48] <menn0> axw: would you mind taking a look at this one please? http://reviews.vapour.ws/r/3964/
[03:48] <axw> menn0: sure
[03:48] <menn0> axw: thansk
[04:00] <axw> menn0: done
[04:08] <menn0> axw: thanks
[04:10] <menn0> axw: good catch with the missing Done call
[04:19] <wallyworld> menn0: where's thumper? anyways, why does juju create-model use creds/secrets for ec2 and openstack? i thought all hosted models were restricted to using the same creds as the original controller? is that not the case?
[04:19] <wallyworld> is ec2 nd openstack special cased?
[04:22] <menn0> wallyworld: thumper is on his way to christchurch. he's off tomorrow for a wedding up here.
[04:23] <wallyworld> and i thought he was slackong off
[04:23] <wallyworld> we're supposed to have a meeting, i wonder when he ws going to tell me
[04:23] <menn0> wallyworld: I don't know about the create-model creds situation. thumper did that work.
[04:23] <wallyworld> damn, ok
[04:23] <menn0> such a slacker
[04:24] <wallyworld> menn0: because if we do need to supply creds, we'll need to migrate that to crdentials.yaml etc
[04:24] <menn0> wallyworld: off memory, I thought that it was possible to use different creds for different models on the same controller
[04:24] <menn0> but i'm fairly vague about that
[04:25] <wallyworld> ok, np, we'll need to look into it
[04:25] <axw> we should surely default to the controller's creds though
[04:25] <wallyworld> yes
[04:25] <wallyworld> you'd hope so
[04:25] <wallyworld> but the cli has a comment that we look in supplied config vars for new creds
[04:25] <wallyworld> i didn't know we did that
[04:26] <axw> wallyworld: yep. and some providers will fail if you don't supply them, some don't
[04:26] <menn0> wallyworld, axw: think about the possibility of hosted envs being "owned" by completely unrelated parties
[04:26] <menn0> you'd want different creds then
[04:26] <wallyworld> ah yes. true
[04:26] <wallyworld> same provider, different creds
[04:26] <axw> menn0: sure, I think we should support it
[04:27] <axw> menn0: just not require it
[04:27] <menn0> it might even be "unsafe" to default to the controller's creds
[04:27] <wallyworld> axw: i think we'd want this for next beta, i'll try and get to it tomorrow, should be small change
[04:27] <menn0> not sure
[04:28] <menn0> wallyworld, axw: could one of you look at this one please? http://reviews.vapour.ws/r/3965/
[04:28] <axw> I'll look
[04:28] <menn0> fixes to apiserver panics that several people have been observing during test runs
[04:28] <wallyworld> sure
[04:28] <menn0> (including me)
[04:28] <menn0> axw, wallyworld: just one of you is fine :)
[04:29] <axw> menn0: yes, me too - thank you!
[04:29] <wallyworld> and me!
[04:29] <menn0> axw, wallyworld: the novela at the top explains it, but the problem has been there forever I think
[04:30] <menn0> axw, wallyworld: it's just that timings for worker startup and shutdown have changed due to the dep engine
[04:30] <wallyworld> menn0: i think it has, i don't recalls those /charm or /tools or /backups etc endpoints being tracked
[04:31] <menn0> axw, wallyworld: we're still not in good shape yet for the other streaming style APIs but at least /logsink and /log are fixed
[04:31] <menn0>  /logsink is in use all the time
[04:31] <wallyworld> got to start somewhere
[04:31] <menn0> and now the pieces are there to do the others
[04:31]  * menn0 spent most of yesterday and today on this one when he should have been doing other things
[04:32] <menn0> thought it was due to my changes
[04:32] <menn0> but it wasn't
[04:32]  * menn0 creates a ticket about the others
[04:35] <wallyworld> menn0: pr looks ok but my brain has not delved into any possible subtle breakages
[04:38] <menn0> wallyworld: i've done quite a bit of manual testing and i'm pretty sure it's right, but I understand your concern
[04:39] <menn0> axw: given wallyworld is a bit uncertain could you take a look too please?
[04:39] <wallyworld> menn0: +1 from me fwiw if you've tested manually
[04:39] <axw> menn0: was already looking
[04:39] <axw> still looking
[04:39] <menn0> axw, wallyworld: thanks both of you
[04:39] <wallyworld> awesome that you fixed it
[04:45] <axw> menn0: LGTM
[04:45] <menn0> axw: cheers
[04:49] <menn0> axw: your idea makes sense and is preferable to what i've done if I can make it work
[04:49] <menn0> trying now
[04:49] <axw> menn0: ok, thanks
[04:56] <menn0> axw: yeah, that's heaps better
[04:56] <menn0> axw: just making sure it works now
[04:56] <axw> menn0: cool :)
[04:57] <menn0> are
[04:58] <menn0> wallyworld: is this error expected?
[04:58] <menn0> $ juju bootstrap menn0 aws --config ~/canonical/juju-dev.yaml --upload-tools
[04:58] <menn0> Creating Juju controller "local.menn0" on aws/us-west-2
[04:58] <menn0> ERROR streams/v1/index2.sjson not accessed, actual error: invalid URL "https://streams.canonical.com/juju/images/releases/streams/v1/index2.sjson" not found
[04:58] <wallyworld> menn0: yeah
[04:58] <menn0> there's a few other similar ones
[04:58] <wallyworld> it needs to be suppressed
[04:58] <menn0> due to upload-tools?
[04:59] <wallyworld> it's because simplestreams searches everywhere and logs what it can't find
[04:59] <wallyworld> should be debug or trace
[05:16] <wallyworld> axw: so far, aws and google both support different named credentials having their own default region rather than a single global default :-(
[05:17] <wallyworld> might need to revisit the model
[05:17] <axw> wallyworld: docs?
[05:18] <wallyworld> axw: for aws, i'd have to look up docs again, i'm judt looking at what's in my ~/.aws directory. there's a config and a credentials file. config has region per user, credentials has credentials per user
[05:19] <axw> wallyworld: isn't that just the default for each though?
[05:19] <wallyworld> yes, but we don't model it that way
[05:19] <wallyworld> we have map[string]Credential
[05:19] <wallyworld> and region is a outside that map
[05:20] <wallyworld> i'll leave it for now
[05:21] <axw> wallyworld: so you're suggesting DefaultRegion should be part of Credential, rather than CloudCredential?
[05:22] <wallyworld> axw: yeah i think so
[05:22] <wallyworld> or at least an override
[05:22] <wallyworld> like we do with endpoints in cloud.yaml
[05:24] <axw> wallyworld: I'd wait until someone asks for it. I think for now we should take whatever's in [default] and use that where we have DefaultRegion today
[05:24] <wallyworld> sgtm, but we can easily model it if needed
[05:24] <axw> should be easy to have an override later
[05:24] <axw> yep
[05:47] <wallyworld> menn0: can you recall the help function to fix windows user names?
[06:58] <axw> wallyworld: no rush since it can't land yet, but admin bootstrap model changes: https://github.com/juju/juju/pull/4530
[06:58] <axw> wallyworld: I'll look at the next bit, creating the secondary model
[06:59] <wallyworld> axw: awesome, ty, will look after soccer, finishing up part2 of detect credentials
[07:10] <anastasiamac> dimitern: o/
[07:14] <dimitern> anastasiamac, hey there
[09:58] <fwereade_> dimitern, axw: do either of you have recent insight into the `if insideLXC` handling in MachineAgent.uninstallAgent?
[09:59] <fwereade_> dimitern, axw: naively, ISTM that it's happening too late -- that we should do it before setting the machine to dead, not after
[09:59] <fwereade_> dimitern, axw: thoughts?
[10:00] <fwereade_> dimitern, axw: (because, once we're dead, it's a matter of luck whether or not that code gets to run before the responsible provisioner nukes the whole container)
[10:00] <dimitern> fwereade_, I have to look at the code - after standup though
[10:01] <dimitern> ah no standup today
[10:02] <dooferlad> dimitern, anastasiamac, frobware, voidspace: (and others) meeting?
[10:02] <dimitern> dooferlad, thanks for the review btw; voidspace, frobware - I'd appreciate if you have a look as well: http://reviews.vapour.ws/r/3969/
[11:08] <axw> fwereade_: indeed, we should do it before setting Dead. pretty sure I wrote that - sorry
[11:27]  * dimitern whew... refcounts finally working
[11:28] <dimitern> note to self: $ge != $gte and bson.D{{"$gte", bson.D{{"field", 0}}}} != bson.D{{"field", bson.D{{"$gte", 0}}}}
[11:34] <dimitern> dooferlad, ping
[11:34] <dooferlad> dimitern: pong
[11:35] <dimitern> dooferlad, I'm not quite sure what do you mean by this comment: I think if you are calling the above function addLink...AndEnsureAllAdded then you shouldn't need a check after it.
[11:35] <dimitern> dooferlad, there's no check there
[11:36] <dooferlad> dimitern: the line has c.Check(children, gc.HasLen, len(childrenNames))
[11:36] <dimitern> dooferlad, ah
[11:37] <dooferlad> dimitern: that one seems unnecessary if you have already ensured that all are added
[11:37] <dimitern> dooferlad, I got you - yeah, it's not needed
[11:37] <dooferlad> np
[11:37] <dimitern> will drop it
[11:37] <fwereade_> axw, no worries, just checking
[11:37] <fwereade_> axw, I don't see how to address that in the near term but I'll leave a TODO
[11:39] <axw> fwereade_: nobody has implemented storage support for the LXD provider yet, so it's not actually doing anything at the moment. hopefully someone will fix that soon though...
[11:39] <axw> fix/implement
[11:39] <axw> we had it for local, so there's a small gap there now
[11:40] <fwereade_> axw, also, correct me if I'm wrong: ISTM that that code is the only reason we actually "need" to run the uninstall logic in non-manual-provider cases
[11:40] <axw> fwereade_: that is correct
[11:41] <fwereade_> axw, and hence the only reason for various workers to write the uninstall file when they're "sure" that ErrTerminateAgent is "really meant"
[11:42] <fwereade_> axw, ...so, if the lxd bits are currently meaningless... can I maybe drop the uninstall-file-writing entirely, and leave it to the discretion of the manual provider?
[11:42] <axw> fwereade_: it's almost certainly going to be needed again for lxd, so I'd prefer not to.. unless it's actively getting in your way?
[11:53] <fwereade_> axw, I think I've come to understand what's going on well enough that it's not any more
[11:53] <fwereade_> axw, so I'm quite happy not to take on ripping it out :)
[11:54] <fwereade_> axw, but I must say it has sharp edges ;p
[12:08] <dimitern> dooferlad, voidspace, here's the next PR in line: http://reviews.vapour.ws/r/3972/ please have a look when you can
[12:08]  * dimitern lunches
[12:25] <anastasiamac> dooferlad: sorry for missing team meeting. it falls at 8pm my time and with 3 kids, some days, it's the busiest time of the day \o/ i'll try next time but trust that u've had plenty gerat meeting :D
[12:26] <anastasiamac> s/plenty gerat/pretty great
[12:30] <mgz> gerat is less offensive than "u've" :P
[12:30] <dimitern> the only similar word that comes to mind is german - Geraet
[12:32] <mgz> anastasiamac: meeting was good, just us euros hangin' out
[12:33] <anastasiamac> mgz: it's great to hear that it's such a tight group \o/
[12:34] <anastasiamac> mgz: is there an awesome way to "predict" (=deduce?) what branch will run in CI next... ?..
[12:34] <mgz> anastasiamac: generally not because we're always bumping things around on request
[12:35] <mgz> atm, master will run next
[12:37] <anastasiamac> k... so what incantation did u use to figure that out?
[12:38] <mgz> in this case, `crontab -e` as jenkins on the master
[12:38] <anastasiamac> :D
[12:38] <dimitern> dooferlad, voidspace, rebased http://reviews.vapour.ws/r/3972/ onto maas-spaces2 after its prereq has landed to clean up the diff
[12:39] <mgz> anastasiamac: when overrides are not in place, it picks the branch in the github.com/juju/juju repo which has oldest untested changes
[12:52] <perrito666> bbl
[12:54] <bogdanteleaga> do we have something that translates back and forth between unit-<x>-0 and <x>/0?
[12:54] <dimitern> bogdanteleaga, check names.ParseUnitTag
[12:57] <bogdanteleaga> dimitern, thanks, looks promising
[13:08] <mup> Bug #1548813 opened: maas-spaces2 bootstrap failure unrecognised signature  <ci> <maas-provider> <juju-core:In Progress by dimitern> <juju-core maas-spaces:Fix Committed by mfoord> <https://launchpad.net/bugs/1548813>
[13:09] <frobware> huzzah! I have an internet access again \?/
[13:09] <dimitern> frobware, hey! :) welcome back then
[13:10] <frobware> dimitern: it's weird to have a mobile either. I went to a local coffee shop - it worked there for about 20 mins
[13:11] <frobware> s/to have/to not have
[13:11] <dimitern> ah :)
[13:11] <dimitern> frobware, I was wondering where did you go
[13:11] <mup> Bug #1548813 changed: maas-spaces2 bootstrap failure unrecognised signature  <ci> <maas-provider> <juju-core:In Progress by dimitern> <juju-core maas-spaces:Fix Committed by mfoord> <https://launchpad.net/bugs/1548813>
[13:11] <frobware> dimitern: generally it's considered a bad sign if you can't get to BBC Radio 4 - implies the world had ended...
[13:12] <dimitern> :D
[13:12] <mgz> isn't that one of the triggers for us launching nukes?
[13:12] <frobware> mgz: that's the one. I was close this morning, just couldn't get a +1.
[13:12] <mgz> no woman's hour? moscow is going down!
[13:13] <frobware> dimitern: did I miss anything from standup?
[13:13] <frobware> mgz: perhaps it was coincidental with ofcom ruling that BT did not have a monopoly.
[13:13] <dimitern> frobware, we swapped standup for the weekly team call, which was almost the same thing as standup today
[13:14] <dimitern> frobware, you missed nothing important
[13:14] <dimitern> well, apart from the next few PRs of mine :)
[13:15] <frobware> dimitern: I was surprised you cherry-picked voidspace's change into master if it's not actually broken there.
[13:16] <dimitern> frobware, it's not but since master uses older gomaasapi, I can't reliably test the fix for the br-eth1 issue I picked upgodeps
[13:16] <dimitern> ..while things got rather quiet
[13:16] <frobware> dimitern: this still need review? lldb?
[13:16] <frobware> dimitern: this still need review? http://reviews.vapour.ws/r/3969/
[13:17] <dimitern> frobware, this does - http://reviews.vapour.ws/r/3972/
[13:17] <frobware> nope, looks like I missed that by 48 mins too
[13:17] <mup> Bug #1548813 opened: maas-spaces2 bootstrap failure unrecognised signature  <ci> <maas-provider> <juju-core:In Progress by dimitern> <juju-core maas-spaces:Fix Committed by mfoord> <https://launchpad.net/bugs/1548813>
[13:18] <dimitern> frobware, ah, sorry about that :) I'm happy to do a follow-up after that last one, if you have concerns
[13:46] <voidspace> frobware: dimitern: yeah, I didn't understand that - surely if the fix is on maas-spaces2 then the fix will land on master when maas-spaces2 is merged
[13:47] <dimitern> voidspace, yeah, assuming the fix for br-eth1 lands in maas-spaces2 first
[13:47] <dimitern> frobware, voidspace, but it affects master already, and it's critical to fix this to unblock multi-nic containers
[13:47] <voidspace> ah, if it affects master already then fair enough
[13:48] <voidspace> your comment on the bug implied it wouldn't affect master until maas-spaces2 was merged (at which point the fix would land as well)
[13:50] <dimitern> initially it wasn't obvious it affects master, but I can confirm that now
[13:53] <frobware> dimitern, voidspace: so could somebody explain to me how it affects master.
[13:53] <frobware> dimitern: I'm missing some context arounf br-eth1
[13:53] <dimitern> frobware, if you try what that CI job does, the effect is the same
[13:54] <dimitern> frobware, i.e. deploying an lxc container on a machine with 2 nics, eth0 disabled, eth1 enabled
[13:57] <frobware> dimitern: I see. thx.
[13:58] <dimitern> frobware, so the issue is not with the bridge script this time :) - br-eth1 gets created OK, but then we don't render the correct lxc.conf and /e/n/i
[14:04] <frobware> dimitern: yeah, I eventually got that when I read bug #1549545
[14:04] <mup> Bug #1549545: Bundle deploys fail at lxc-start when bridge br-eth1 is created <ci> <deploy> <maas-provider> <test-failure> <juju-core:In Progress by dimitern> <https://launchpad.net/bugs/1549545>
[14:05] <frobware> dimitern: reviewed http://reviews.vapour.ws/r/3972/
[14:05] <dimitern> frobware, thanks! will have a look shortly
[14:07] <dimitern> removing any IPv6 settings from my vmaas-19 made everything SOOO much faster!
[14:13] <frobware> dimitern: be careful, when IPv4 has run out you'll have to switch back. :)
[14:14] <dimitern> frobware, I kept the config commented out just for such a case :)
[14:15] <frobware> dimitern: any decade now...
[14:16] <dimitern> frobware, indeed :D
[14:35] <perrito666> jam: can you try to reproduce that issue with master? if volumes are being deleted it means we might have broken something with tags
[14:35] <jam> perrito666: I can't try to reproduce right now as I'm focused on the LXD stuff.
[14:36] <jam> its an old envirenment that I forgot to teardown. Though now I can't tear it down at all.
[14:36] <perrito666> jam: did you just deploy to ec2 and then dropped the machine?
[14:37] <jam> perrito666: I would have bootstrapped a couple weeks ago. The machine was still up and running and happy returning "juju status" results.
[14:40] <jam> cherylj: tych0: mgz: I took tycho0's update to mine and I have something that is passing the test suite and seems able to "juju bootstrap lxd lxd"
[14:40] <jam> http://reviews.vapour.ws/r/3973/
[14:40] <mgz> jam: thanks!
[14:40] <jam> tych0: we still need to fix containers/lxd/lxd_test.go to not require you to have an "ubuntu-xenial" image.
[14:41] <jam> mgz: so there are still some known limitations. Like LXD containers on OS other than Xenial need you to install "ppa:ubuntu-lxc/lxd-stable"
[14:41] <jam> I thought it was supposed to be in trusty-backports
[14:41] <jam> but suddenly 0.26 is the version in trusty-backports
[14:42] <jam> which Juju happily installs and then immediately fails to work because of API incompatibilty.
[14:42] <mgz> hm, yeah, this need some sanity in which versions we promote to ubuntu archive when
[14:42] <mgz> which the juju team hasn't had much influence over so far
[14:43] <jam> mgz: also this is *not* compatible with 2.0.0~beta3
[14:43] <jam> they broke their api one more time for 2.0.0~beta4
[14:43] <jam> I'm told they aren't likely to break it again.
[14:49] <natefinch> ericsnow: you around?
[14:51] <jam> mgz: can you give it a bit of a run around to make sure it isn't just my local stuff that is working?
[14:51] <jam> I'm not sure who else is going to review that code.
[14:51] <jam> maybe ericsnow or katco or natefinch would like to review the LXD updates?
[14:51] <mgz> jam: if you like we can just send that branch through CI
[14:51] <jam> http://reviews.vapour.ws/r/3973/
[14:51] <jam> mgz: well, we could just land it on lxd-container-type couldn't we?
[14:52] <jam> that is the target of that branch
[14:52] <jam> I don't imagine it is going to be any more broken than the existing lxd-container-type. :)
[14:52] <natefinch> katco`: I need to bring my daughter to the doctor at 11:30 today - she's had a fever since Sunday night, and spiked to 103.5 last night.  It'll probably take 90 minutes all told, but most of that can come out of my lunch time.
[14:52] <mgz> yeah, that would be fine
[14:52] <jam> mgz: can you confirm the version of Go that the landing bot uses?
[14:52] <jam> mgz: I was pretty sure it was 1.2 but that means all the LXD tests get skipped.
[14:52] <katco`> natefinch: ok, hope she feels better :(
[14:53] <mgz> the gating uses 1.2, revision testing is go 1.2/gccgo/go 1.5/go 1.6
[14:53] <jam> mgz: right. so there is no gating on LXD :(
[14:53] <jam> but at least it will notice in CI
[14:53] <jam> which is how I broke it last time, probably.
[14:54] <jam> anyway I need to go walk the dog. I might try to stop by later to catch up to how things are going.
[14:54] <natefinch> katco`: yeah, it's been a scary few days, and the fact it just keeps on going is cause for concern.  And this is our 2.5 year old, so she's still pretty little.
[14:54] <katco`> natefinch: yeah, it's scary at that age
[14:55] <jam> natefinch: I hope if its something it gets resolved quickly. Been through that as well. always hard.
[14:55] <jam> mgz: so... I'm worried that we can't release because this is going to be "known broken" on Trusty because they no longer have 2.0.0~beta4 in backports
[14:55] <jam> mgz: thoughts?
[14:55] <natefinch> jam: thanks
[14:55] <jam> bbiab
[14:56] <mgz> jam: I agree, though what functionality are we promising on trusty with the beta?
[14:57] <natefinch> mgz: it won't format your hard drive ;)
[14:57]  * natefinch sets a low bar.
[15:06] <natefinch> ericsnow, katco`: in other news, juju upgrade-charm --resource basically works right now.  THere's some probable undesired behavior, but hooking into the code that deploy used for --resource was really easy.
[15:06] <frobware> jam: there was one printf-esque mismatch you might want to address now, my other comments were more benign.
[15:07] <katco`> natefinch: \o/
[15:07] <tych0> jam: do i count as a guy who can land that into lxd-container-type? i'd be happy to land it there so we can at least get more CI on it and start getting the +1s
[15:07] <tych0> your changes on top of mine on top of yours look good :)
[15:08] <natefinch> katco`, ericsnow: and by probable bad behavior, I mean that any resource you *don't* specify with --resource gets removed ;)
[15:13] <natefinch> rick_h_: I presume that if you upgrade-charm --resource foo, any other resources you have uploaded should remain the same?
[15:13] <frobware> tych0: just a heads-up, see my comment ^^ to jam about a printf-esque mismatch in the review and the one about limits.cpus vs limits.cpu.
[15:14] <natefinch> jam: saw the ping on lxd review, maybe katco` can talk about scheduling... we're pretty slammed, but I know the lxd stuff is critical
[15:15] <tych0> frobware: will take a look, thanks
[15:17] <tych0> frobware: yeah, it is subtle but also correct. see the commit message for the commit in question
[15:17] <tych0> (not sure how to link it on the review tool)
[15:17] <frobware> tych0: ok, that's fine. it was more out of completeness
[15:18] <katco`> natefinch: jam: we should assist with lxd support where possible
[15:18] <katco`> natefinch: jam: in a meeting, where is this request?
[15:18] <natefinch> katco`: http://reviews.vapour.ws/r/3973/
[15:19] <tych0> frobware: sure, np. thanks for looking!
[15:19] <katco`> ericsnow: when you're off this call, can you give this review a look?
[15:20] <ericsnow> katco`, natefinch: sure
[15:21] <katco`> jam: tych0: ^^^ we'll tal. ty for pr
[15:27] <frobware> dimitern: regarding, http://reviews.vapour.ws/r/3967/, in general I think we should only merge blessed master builds unless we need specific fixes. thoughts?
[15:33] <dimitern> frobware, wouldn't it be better to track master closely until 2.0 branch is cut?
[15:35] <frobware> dimitern: I would rather have blessed builds as we don't have to chase ghosts.
[15:35] <frobware> dimitern: as soon as anything on master is blessed, and we're behind, we merge. not opting out, just being choosy.
[15:36] <dimitern> frobware, sounds reasonable
[15:36] <dimitern> frobware, but there were a few useful fixes we picked up due to that merge
[15:37] <frobware> dimitern: again, not a hard-and-fast-rule, just trying to ensure we don't chase CI bugs on maas-spaces2.
[15:38] <mgz> master is in a rather unstable state atm unfortunately
[15:39] <frobware> mgz: dimitern: no further questions your honour! :)
[15:41] <dimitern> :)
[15:53] <voidspace> dimitern: frobware: dooferlad: another gomaasapi fix https://github.com/juju/gomaasapi/pull/8
[15:55] <frobware> voidspace: looking
[15:56] <dimitern> voidspace, why should it matter whether the reserved ranges are nil vs empty slices ?
[15:56] <voidspace> dimitern: because GetArray fails on nil
[15:57] <voidspace> dimitern: and it isn't what the real server does, so I'd rather the test server behaved like maas
[15:57] <voidspace> dimitern: instead of writing defensive code in production just for the gomaasapi test server
[15:57] <frobware> voidspace: how did you discover this?
[15:58] <voidspace> frobware: on my current branch a whole bunch of tests fail
[15:58] <voidspace> frobware: I've changed the Spaces implementation and the existing tests fail
[15:58] <frobware> voidspace: k
[15:58] <katco`> ericsnow: getting some more coffee and then we can do our 1:1
[15:58] <ericsnow> katco`: k
[15:58] <voidspace> and fetching a subnet calls Spaces to get the space provider id, so all the existing tests fail
[15:59] <voidspace> because the test server is now wrongly configured for the test
[16:00] <dimitern> voidspace, I see
[16:00] <dimitern> voidspace, yeah, that's a problem when using MAASObjects instead of structs with json serialization tags
[16:01] <perrito666> meh, switch lost --list
[16:03] <perrito666> aaand, I can no longer do a switch to my provider
[16:03] <perrito666> :(
[16:04] <katco`> ericsnow: k i'm in the hangout when you're ready
[16:04] <ericsnow> k
[16:10] <voidspace> frobware: what do you mean by 'can "1" ever return nil'?
[16:12] <frobware> voidspace: heh, sorry it was ambiguous. The call to GetSubObject("1").
[16:13] <voidspace> frobware: the answer is no
[16:13] <voidspace> frobware: it's a gomaasapi object for making a call to the server
[16:13] <voidspace> frobware: the subsequent call can fail, but GetSubObject can't return nil
[16:14] <frobware> voidspace: ok. it was the only thing that stuck out for me. LGTM.
[16:14] <voidspace> frobware: dimitern: thanks
[16:35] <perrito666> bbl, bye
[17:04] <kilty> natefinch, mgz, cherylj: Been trying to play around some more get this working. I'm still having problems with the metadata generation - I'm not sure what I'm missing
[17:04] <kilty> http://pastebin.com/7JR198Az
[17:05] <kilty> this is everything I'm working with - I'm not sure what information it's looking for with the -m. Is it just the name of the cloud? is it a file with config options?
[17:08] <katco`> kilty: have you popped into #juju to see if anyone there has experienced similar issues?
[17:08] <cherylj> kilty: the -m specifies the model (new term for environment) to operate in.      the command help looks like it hasn't been updated for the 2.0 conventions
[17:09] <katco`> kilty: we may be able to help you, but this channel is more focused on development
[17:09] <cherylj> I have a hard time wrapping my head around having to have a bootstrapped env / model in order to generate metadata
[17:09] <cherylj> let me poke at that command
[17:10] <kilty> katco`: I'll pop in there and ask as well
[17:11] <kilty> cherylj: Yeah I'm not sure why I wouldn't be able to generate metadata regardless of a model - when I was working with 1.25 I could generate metadata regardless of what env I was going to deploy it to
[17:11] <cherylj> kilty: the image metadata you generate with 1.25 should be usable with 2.0
[17:12] <kilty> so we should generate it on a 1.25 instance and scp it over?
[17:13] <cherylj> kilty: yeah, I'd give that a try
[17:13] <kilty> cherylj: ok. I will give that a try and see what happens. Thanks
[17:15] <frobware> jam: you about? I looked at the updates diffs for your review and it is now spread across 9 pages. Seems a lot. :)
[17:22] <alexisb> frobware, jam is probably out but tych0 is around and may be able to answer qs
[17:23] <tych0> yep, happy to answer any questions
[17:24] <frobware> alexisb: yep - asking because I saw some follow up from him about 15 mins..
[17:25] <frobware> tych0, jam: so looks like upstream/master was merged onto that review, hence the 9 pages. Just surprised me as I was looking at the diffs based on jam's comments.
[17:26] <tych0> frobware: yes, i didn't do the merge unfortunately
[17:32] <kilty> cherylj: So it looks like the metadata generation works, it's just throwing errors - it creates the same metadata that 1.25 does
[17:32] <kilty> same thing with the tool generation
[17:45] <natefinch> katco, ericsnow: can you guys TAL at this PR?  http://reviews.vapour.ws/r/3949/ It's the one from yesterday where we now return a unitresources value for every unit.
[17:45] <ericsnow> natefinch: yeah, sorry, will do soon
[17:46] <natefinch> katco, ericsnow: also, having push-resource call upgrade-charm is kind of amazing.  It makes everything just work the way you'd expect
[17:46] <katco> natefinch: will do so when i get a chance. lots o' meetings today. speaking of... we still on for 10m from now?
[17:46] <natefinch> er fire the upgrade-charm hook that is
[17:46] <katco> natefinch: that's good to hear :)
[17:47] <natefinch> katco: yep, back from the doctor. They tested and it's not strep or the flu... just some nasty virus.. said if she's not better in a couple days they'll have to do chest X-Rays, but we're hoping she'll just fight it off.
[17:47] <katco> natefinch: :( well hope she feels better real soon
[17:48] <natefinch> katco: yeah... she's a little better today... but she always seems a bit better morning/midday, so we'll see what happens tonight.
[18:29] <perrito666> I know this is not a popular opinion but, I really dislike format tabular as a default
[18:31] <voidspace> g'night all
[18:43] <natefinch> perrito666: blasphemy
[18:53] <natefinch> katco: btw, I think you can discard your api pass through review (http://reviews.vapour.ws/r/3948/) now, since my PR with that code landed last night
[18:55] <katco> natefinch: yeah been meaning to
[19:14] <perrito666> is master unlocked?
[19:16] <natefinch> perrito666: http://juju.fail
[19:16] <alexisb> katco, sorry, thats me
[19:16] <alexisb> logging back on
[19:16] <katco> alexisb: ah ok. lately i've been the one freezing :)
[19:17] <perrito666> natefinch: sweet I completely forgot that thing
[19:18] <natefinch> perrito666: best use of a non-standard TLD I've seen
[19:34] <kilty> niedbalski: working through the same issues you were in this bug, and was hoping that I could pick your brain
[19:34] <kilty> https://bugs.launchpad.net/juju-core/+bug/1452422
[19:34] <mup> Bug #1452422: Cannot boostrap from custom image-metadata-url or by specifying metadata-source <sts> <juju-core:Fix Released by wallyworld> <juju-core 1.24:Fix Released by wallyworld> <https://launchpad.net/bugs/1452422>
[19:46] <niedbalski> kilty, AFAIK that should be fixed, which juju-core version are you using?
[20:00] <kilty> niedbalski: 1.25
[20:01] <kilty> niedbalski: 1.25.3, to be exact
[20:02] <kilty> installing from ppa:juju/stable
[20:03] <niedbalski> kilty, can you pastebin the error you are seeing?
[20:03] <kilty> If I generate the metadata locally and use the --metadata-source option on bootstrap, it creates the ost image, but the ost image defaults to looking back at cloud-ubuntu images
[20:03] <kilty> niedbalski: sure thing
[20:05] <mgz> kilty: you need to use image-metadata-url like I said previously
[20:05] <kilty> mgz: when I use the image-metadata-url, it seems to completely ignore it
[20:06] <mgz> kilty: if you bootstrap with --debug you can see what simplstreams are being selected
[20:07] <kilty> mgz: I am running a bootstrap with --debug now, will pastebin the results
[20:08] <kilty> niedbalski: http://pastebin.com/raw/VcYGhsFF
[20:08] <kilty> that's with using the --metadata-source option
[20:10] <mgz> kilty: that won't work. the local file never gets uploaded anywhere the state server can see it. I can see that the image-metadata-url is being looked at.
[20:11] <kilty> mgz: http://pastebin.com/NnFH6jQj
[20:13] <kilty> mgz: that's that happens when I just run with the agent-metadata-url and image-metadata-url set in the env file
[20:16] <mgz> kilty: export JUJU_LOGGING_CONFIG="<root>=DEBUG; juju.environs.simplstreams=TRACE" and try that again?
[20:16] <mgz> gah,tyop
[20:16] <mgz> *juju.environs.simplestreams
[20:17] <kilty> mgz: running now
[20:18] <kilty> mgz: http://pastebin.com/zRnqWxZR
[20:19] <mgz> kilty: no route to host
[20:19] <mgz> line 11
[20:19] <kilty> mgz: yeah sorry about that hold on - I need to re-run it
[20:19] <mgz> you need to host the streams somewhere both your client and the machine you are deploying can see
[20:21] <mgz> that needs to be higher than trace...
[20:23] <kilty> mgz: http://pastebin.com/HfdYzspP
[20:23] <kilty> I'm running this from an instance that I created in the same tenant to which I will deploy juju
[20:23] <kilty> so the ost machine and the box I am on now are in the same network
[20:24] <mgz> kilty: l17, 403
[20:24] <mgz> can you actually resolve the path where you uploaded the json files, just in a browser?
[20:26] <kilty> I can resolve thee parent directories - images/streams
[20:26] <kilty> let me chmod the entire structure and try again
[20:28] <kilty> ok - it's created the instance and is starting to provision - I'll let you know if it fails
[20:29] <kilty> mgz: thank you so much for all your help..this has been bugging me for about a week now. I'm trying to set this up so that I can deploy about 400 juju environments on a private openstack cloud for internal developers
[20:29] <mgz> no probs
[20:30] <kilty> mgz: tools from http://<IP_ADDRESS>/tools/releases/juju-1.25.3-trusty-amd64.tgz downloaded: HTTP 404; time 0.002s; size 0 bytes; speed 0.000 bytes/s sha256sum: /var/lib/juju/tools/1.25.3-trusty-amd64/tools.tar.gz: No such file or directory
[20:30] <kilty> 2016-02-25 20:29:30 ERROR juju.cmd supercommand.go:429 failed to bootstrap environment: subprocess encountered error code 1
[20:31] <mgz> kilty: if you have outbound net access, I'd just delete the agent-metadata-url config and let the setup get the tools from our source
[20:31] <mgz> otherwise, you'll need to get that tgz mirrored
[20:33] <kilty> mgz: ok - that makes sense. Re-running w/o agent-metadata-url
[20:37] <kilty> mgz: success!
[20:37] <mgz> kilty: ace!
[20:38] <kilty> mgz: now for the noob question of the hour - how to I deploy the gui frontend?
[20:38] <kilty> is it not part of the bootstrap?
[20:39] <mgz> `juju deploy cs:juju-gui --to 0` should do
[20:39] <kilty> oh duh - it's a charm
[20:40] <kilty> mgz: thanks
[20:40] <mgz> they have plans for things in 2.0 which... I'm not completely up to speed with
[20:40] <mgz> just to integrate the gui a little more closely I think
[20:41] <perrito666> great, I cannot reproduce a bug even though I know its there
[20:42] <kilty> mgz: well now that we have 1.25 up I think that solves the issues we were having with 2.0 as well
[20:42] <mgz> yeah, should just be the same stuff
[20:43] <perrito666> anyone here has been bit by the "status history full of update-status calls" ?
[22:55] <axw> fwereade_: yep, it certainly has sharp edges. its raison d'etre is edge cases ;p   if we could find a nice way to confine it to manual and lxd that would be good. or maybe just manual, and do the loop-device detachment elsewhere...
[22:58] <mup> Bug #1550033 opened: Streaming API handlers may panic when apiserver shuts down <juju-core:New> <https://launchpad.net/bugs/1550033>
[23:07] <mup> Bug #1550033 changed: Streaming API handlers may panic when apiserver shuts down <juju-core:New> <https://launchpad.net/bugs/1550033>
[23:16] <mup> Bug #1550033 opened: Streaming API handlers may panic when apiserver shuts down <juju-core:New> <https://launchpad.net/bugs/1550033>


[14:48] <xubuntu17i> helo
[14:49] <xubuntu17i> ill have to say irc chat while installing is a good idea :D
[18:46] <rauldux> Hey there, on my xubuntu 16.04 the network connection icon on systray appears in two different ways. sometimes it's two arrows and sometimes it's the 'wifi-bars'. well network works fine anyway, I'm just wondering why this happens. Any experience on that 'issue'?
[18:48] <NEETWizard> test
[18:50] <NEETWizard> I'm trying to set up an old Wacom drawing tablet in Xubuntu, mapping it to only 1 monitor. I found info on that, but it doesn't work. found other people ran into same problem. error: Unable to find an output 'DVI-I-1'. I'm wondering if it's because they're offset in position to each other virtually.
[18:52] <NEETWizard> They tried .... a convolution matrix but still no luck. I haven't tried that myself yet.
[18:52] <stevehope> whats the setting / app for Passwords and Encryption Keys in Xubuntu?
[18:54] <diogenes_> passwords for browsers?
[18:54] <stevehope> ssl and gpg
[18:54] <NEETWizard> Hmmmm... well aligning the tops of the monitors together didn't make it work for: xsetwacom --set 10 MapToOutput "DVI-I-1"
[18:54] <stevehope> is there an appelt in the gui or is it cli only
[18:54] <diogenes_> I know there's seahorse gnome-keyring
[18:55] <stevehope> gnome-keyring is the equivalent or what i was looking for thanks
[18:55] <NEETWizard> doesn't work for this command either: xsetwacom set "Wacom Intuos 6x8 Pen stylus" MapToOutput DVI-I-1
[18:55] <stevehope> *of
[18:55] <diogenes_> stevehope, you can always type in terminal: apropos password
[18:56] <NEETWizard> xrandr gives me a screen DVI-I-1, so I don't know why it doesn't like that.
[18:58] <diogenes_> NEETWizard, did you look in man xrandr?
[18:59] <NEETWizard> diogenes_, hm. nope. I'm a little retarded. not sure how much that'll help but I'll check.
[18:59] <NEETWizard> I was just looking to identify the display name, like these websites say. yeah.
[19:00] <diogenes_> NEETWizard, run in terminal: man xranrd and read read read
[19:01] <NEETWizard> diogenes_, but I don't want to change anything with xrandr. it's xsetwacom that needs to do that, I'm think.
[19:03] <diogenes_> NEETWizard, when you want to fix a motorcycle engine you have to know what does every single component do, otherwise you screw it up
[19:05] <NEETWizard> diogenes_, I think that's relative. Maybe you can't afford to trust someone just because they're a mechanic, but maybe in some circumstances that analogy does hold, in that you ... relegate expertise and find someone trustworthy.
[19:06] <diogenes_> the best work is the one done by yourself
[19:07] <NEETWizard> Sure, you're likely to create poison gas if you ask 4chan how to make crystals with pennies, but it's probably easier to tell if official Ubuntu forums are spreading misinformation with commands that will destroy your computer.
[19:09] <NEETWizard> I'm a barely-functioning human being who's suffering from chronic depression. I'm trying to get back into art. I already quit for a few weeks when I couldn't figure out how to use this new Ubuntu drawing software compared to the old Photoshop I used ages ago for Windows. I'm not going to spend a month learning my monitor and tablet from the smallest hardware and software bit.
[19:10] <diogenes_> NEETWizard, try chess for relaxing and offloading the stress
[19:10] <NEETWizard> maybe I can get around this whole problem by temporarily disconnecting one monitor... going back to "the botnet" AKA Windows is a last resort.
[19:22] <NEETWizard> hm. maybe it has something to do with this wacom driver I installed being for Gnome and I'm using XFCE? the tablet works, just that it's stretching over both monitors.
[19:23] <NEETWizard> I was only going to stay up another hour to work on this, but I haven't accomplished anything. I wonder if I deserve the chocolate muffin I promised myself for working for an hour. it was work. :|
[19:23] <flocculant> NEETWizard: yes you deserve it :)
[19:26] <diogenes_> NEETWizard, I have been working for the past 3 days trying to get a scanner to work and two days to make an automatic shortuc but in the end I did succeed
[19:26] <diogenes_> so don't give up
[19:29] <NEETWizard> hm. like I said, I'm kinda retarded. I tried to get back into programming last year and spent a month trying to get an old clock I did in C++ redone in HTML+CSS+JS. and being NEET, I had a lot of time to waste on that.
[19:30] <NEETWizard> The world's not good at teaching you how to live. I'm having to dig through the muck of people like PUAs to find out how to function. I think I'm gonna run out of time though. Mine's half over on average.
[19:31] <diogenes_> carpe diem
[19:32] <NEETWizard> My trajectory would suggest that is unlikely. We'll see.
[19:32] <flocculant> NEETWizard: instead of doing xsetwacom --set 10 MapToOutput "DVI-I-1" have you tried setting geometry instead of monitor?
[19:33] <flocculant> https://wiki.archlinux.org/index.php/Wacom_Tablet#TwinView_Setup look for xsetwacom --set 12 MapToOutput "1920x1080+1920+0" on that page
[19:33] <NEETWizard> flocculant, I have not tried that. I suppose it's worth a try. though I mentioned the one person I found having these problems wasn't able to fix it by that method.
[19:34] <flocculant> ok - what I've read points to it being fun with tablet and Xfce and multi-monitors
[19:35] <flocculant> but not something I've ever needed to do personally
[19:38] <flocculant> NEETWizard: anyway - good luck, if you get nowhere maybe think about trying eithr xfce forum or ubuntuforum for help - not sure pointing to #ubuntu in this case will help
[19:39] <NEETWizard> Alright, thanks again.
[19:41] <flocculant> anyone use mpd and .mpdignore - wanting to ignore a filetype, adding the file to parent directory as it's manual suggests and using wildcards doesn't appear to be working
[19:42] <diogenes_> what you try to do?
[19:43] <flocculant> put the .mpdignore file in the parent directory with *.mp3 as the wildcard to ignore
[19:43] <flocculant> assumption being the parent directory it talks about is the parent directory that the media is in
[19:44] <diogenes_> never tried that
[19:52] <flocculant> seems parent directory is folder with the files in - not doing that here
[21:58] <phunyguy> hi.... got a weird one... not sure if it is because I did a debootstrap install of xubuntu, but I can't configure any indicator applets, like Time and Date settings...  I click it and nothing happens.   Am I missing a package or two? Thanks.   (16.04.2)
[22:01] <Unit193> phunyguy: For Date and Time, do you have gnome-system-tools installed?
[22:13] <phunyguy> Unit193: yes
[22:14] <phunyguy> it seems anything that would use that tool is not working, however
[22:14] <phunyguy> lightlocker-settings, etc
[22:15] <phunyguy> Unit193: http://paste.ubuntu.com/24330505/
[22:17] <phunyguy> hmm that appears to be a different issue which I just resolved.
[22:17] <Unit193> python-gi or so for that, it'd seem.  You can try to simulate installing the task and see what it'd pull in.
[22:20] <phunyguy> yeah reinstalling that fixed light-locker-settings
[22:21] <phunyguy> still nothing on time/date settings, which I cannot seem to find a way to launch from CLI to get an error
[22:21] <phunyguy> also, some qt applications aren't following the proper icon theme (in and out of tray/indicator)
[22:23] <phunyguy> Unit193: here is what I mean on that last comment, note the transmission and transmission-qt icons. One is stock ugly transmission icon, and one is proper. http://i.imgur.com/CEeKDA2.png
[22:23] <phunyguy> also nextcloud icon is stock, not the one from the theme (Numix)
[22:24] <phunyguy> Numix-Circle*
[22:26] <Unit193> phunyguy: `/usr/bin/time-admin`, and you'll have to check Qt settings, for Qt4 then the Qt4 application, for Qt5 (depending on which version that was), you'll need an env var that should be set from /etc/X11/Xsession.d/56xubuntu-session
[22:31] <phunyguy> hm
[22:32] <Unit193> You are in the Xubuntu session, I've been presuming...
[22:32] <phunyguy> Unit193: /usr/bin/time-admin works from cli  ><
[22:32] <phunyguy> Unit193: yea
[22:32] <Unit193> OK, because that and other things are guarded by that fact.
[22:33] <phunyguy> Unit193: export QT_STYLE_OVERRIDE=gtk ?
[22:33] <phunyguy> no wonder qt5ct complains


[03:41] <BadOmen> Hi to login to one witch port do i need to open in the router/firewall?
[13:00] <enry> hi guys
[13:00] <enry> can anyone help me??
[13:02] <enry> i have installed karmic on my notebook, so i will try ubuntu one, but how can i add this notebook to my ubuntu one account?
[13:11] <enry> i've solved, bye
[14:25] <BadOmen> Hi I am using Ubuntu 9.04 and i can not connect from the panel icon or from the shared folder. Do i need to open a port in my router/firewall?
[14:25] <BadOmen> It is no problem connecting from the web interface
[14:30] <markgsaye> BadOmen: could you give me a description of what you have done so far?
[14:34] <BadOmen> I have not done mutch just followd the instructions Ubuntu one homepage, how to install
[14:34] <dobey> BadOmen: you shouldn't need to, no.
[14:35] <BadOmen> now i have added another account for a frend of mine and she is having the same problem, (she lives here so we share the same internet connection.
[14:37] <BadOmen> But right after the installation I tried to connect but it did not work exept from the webbpage. Sorry for my bad english...
[14:38] <BadOmen> dodey:thane there is something else=(
[14:41] <markgsaye> BadOmen: what are you doing to connect? Clicking the Ubuntu One applet? Or in Nautilus?
[14:42] <BadOmen> yes I am left klicking the Ubuntu one applet(icon on the top panel, right?) and I have tried to open nautilus and connect from the button in my Ubuntu one shared folder.
[14:43] <dobey> BadOmen: do you have a ~/.cache/ubuntuone/log/syncdaemon-exceptions.log file?
[14:43] <BadOmen> I am getting a error message when I am  testing it from the terminal as root.
[14:43] <BadOmen> I will check
[14:48] <BadOmen> yes but the one fro m today is emty and the one from yesterday I was using the wrong password...
[14:49] <BadOmen> Can't get the auth token
[14:49] <BadOmen> Traceback (most recent call last):
[14:49] <dobey> ok
[14:50] <BadOmen> this i get when i tryi it as root and check the messages i resive in the terminal:
[14:50] <dobey> BadOmen: can you pastebin the contents of ~/.cache/ubuntuone/log/oauth-login.log
[14:50] <BadOmen> (nautilus:5167): WARNING **: Unable to add monitor:
[14:51] <dobey> why are you running it as root? (what are you running as root?)
[14:51] <BadOmen> Nautilus-Share-Message: Called "net usershare info" but it failed: "net usershare" returnerade fel 255: net usershare: cannot open usershare directory /var/lib/samba/usershares
[14:52] <BadOmen> I just tried it to see what error message I wold get in the terminal. whene I start it as normal user It writes nothin to the terminal.
[14:52] <dobey> that output is from nautilus, so it is unclear to me what you are running in the terminal
[14:53] <BadOmen> the outh-log what do you want to see there. it is alot :)
[14:53] <dobey> what are you running exactly?
[14:54] <dobey> the last "starting version M.N.O" entry, to the end of the file
[14:55] <BadOmen> loock at this realm='https://ubuntuone.com'
[14:55] <BadOmen> thats not the right one is it?
[14:55] <dobey> it's correct, yes. that's not the issue
[14:56] <BadOmen> 2009-09-24 15:15:41,957:957.468032837 UbuntuOne.OAuthDesktop.main Currently in the middle of OAuth: rejecting this
[14:56] <BadOmen> 2009-09-24 15:20:34,666:666.646003723 UbuntuOne.OAuthDesktop.auth Stopping temp webserver
[14:56] <BadOmen> 2009-09-24 15:45:46,718:718.561887741 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
[14:56] <BadOmen> 2009-09-24 15:45:46,719:719.209909439 UbuntuOne.OAuthDesktop.main Currently in the middle of OAuth: rejecting this
[14:56] <BadOmen> is it not this adress now: https://one.ubuntu.com/oauth/request/
[14:57] <BadOmen> I am runing it in gnome, what do you want to know?
[14:57] <dobey> please paste the log info on http://pastebin.ubuntu.com/ and then paste the URL it gives you here
[14:58] <BadOmen> okej :)
[14:58] <BadOmen> http://pastebin.ubuntu.com/277112/
[15:00] <rodrigo_1> OAuth URLs are: request='https://ubuntuone.com/oauth/request/' <- isn't this wrong?
[15:00] <dobey> rodrigo_: no
[15:01] <dobey> BadOmen: you haven't authorized your computer to access your files...
[15:02] <dobey> 2009-09-23 13:18:35,628:628.093957901 UbuntuOne.OAuthDesktop.auth Permission denied storing token
[15:03] <rodrigo_> dobey: so, u1.com redirects to one.u.c?
[15:03] <dobey> rodrigo_: yes
[15:03] <rodrigo_> ah ok
[15:04] <dobey> BadOmen: you've not given permission for ubuntuone-client to store the token in the keyring, it would appear. and so it just tries to get a new token... you should have a browser open somewhere with the "Add this computer" page in it
[15:04] <BadOmen> http://pastebin.ubuntu.com/277120/
[15:05] <BadOmen> A that can be it, i hade the wrong password so i could not do that....
[15:05] <dobey> try with the right password :)
[15:05] <BadOmen> but I have done that, but i can do it agen :)
[15:06] <dobey> according to that log, it's only gotten an access token once, and that time, it was denied access to store it in the keyring
[15:06] <CardinalFang> MEETING BEGINS
[15:06] <CardinalFang> If you're here for the stand-up meeting, say "me".  Say what's Done, To-do, and Blocked.
[15:06] <CardinalFang> me
[15:07] <rodrigo_> me
[15:07] <teknico> me
[15:08] <dobey> me
[15:08] <BadOmen> dodey: i have not a add this commputer and under my computers I have one. I can remove it and try to add it agen.
[15:09] <CardinalFang> thisfred, jblount, urbanape?
[15:09] <urbanape> sure me
[15:10] <dobey> CardinalFang: thisfred isn't desktop+, and jblount/urbanape are sprinting :)
[15:10] <CardinalFang> ah.
[15:10] <urbanape> DONE: Sprinted. New files ui is looking hot. Bindwood is getting better. Managing a manifest of bookmarks folder structure.
[15:10] <urbanape> TODO: Finish up the new files UI. Make a client adhere to the manifest on pull.
[15:10] <urbanape> BLOCK: None
[15:10] <urbanape> jblount's just gonna be a hater
[15:10] <dobey> itchy trigger finger there
[15:10] <urbanape> I think we should steal thisfred
[15:10] <jblount> HATEHATEHATE
[15:11]  * CardinalFang agrees.
[15:11] <urbanape> sorry to jump the gun
[15:11] <teknico> what are we waiting for, then=
[15:12] <dobey> CardinalFang: you going to start things off then? :)
[15:12] <BadOmen> make a add computer under the Computers on your account plz =) now i have to reinstall to get it back or something?
[15:12] <dobey> BadOmen: one minute please
[15:12] <aquarius> CardinalFang, am now :)
[15:12] <BadOmen> np
[15:12] <CardinalFang> DONE: replication testing.
[15:12] <CardinalFang> TODO: make package for desktopcouch real soon.  Hopefully, add my outstanding patches first.
[15:12] <CardinalFang> BLOCKED: couchdb release.
[15:12] <thisfred> urbanape: you propose we elope?
[15:12] <vds> me
[15:13] <aquarius> me
[15:13] <teknico> next: rodrigo_
[15:13] <rodrigo_> • DONE: Contact record conflict resolving. Looked at poauth/python-oauth to fix HMAC bug
[15:13] <rodrigo_> • TODO: Talk to Ara about writing mago tests for evo-couchdb. Propose couchdb-glib/evo-couchdb for GNOME 2.29. Store UUIDs for postal addresses. Conflict resolver tool in pair tool. Look at becoming a MOTU (https://wiki.ubuntu.com/UbuntuDevelopers). openSUSE/Fedora packaging with aquarius. Notes web UI. Make evo-couchdb deal with conflicting contact records. Simplify tomboy syncing config UI
[15:13] <rodrigo_> • BLOCKED: funny oauth
[15:13] <rodrigo_> next: teknico
[15:13] <teknico> DONE: sprinting in London, filed a bug against lazr-js as a feature request for a dynamic form widget (#435305), investigated flushing CouchDb withi thisfred for fixing bug #429603
[15:13] <teknico> TODO: more sprinting in London, fixing and landing the outstanding contacts web ui branches
[15:13] <teknico> BLOCK: none
[15:13] <teknico> next: dobey
[15:13] <dobey> ☺ DONE: Most of #434884
[15:13] <dobey> ☹ TODO: Finish #434884, Help rodrigo with HMAC-SHA1
[15:13] <dobey> ☹ BLCK: DBus is not letting me add methods in the applet.
[15:13] <dobey> and urbanape already went, so vds, all you
[15:13] <vds> DONE: Face Duty and practising with pynotify
[15:13] <vds> TODO:
[15:13] <vds> BLOCKED: nope
[15:13] <vds> aquarius all yours
[15:14] <aquarius> ⚀ DONE: fixed DC bug preventing release; discussion about DC release; travel to London sprint
[15:14] <aquarius> ⚁ TODO: London, baybee! Work on Tomboy notes UI
[15:14] <aquarius> ⚂ BLOCKED:
[15:14] <aquarius> ⚃ BUG COUNT:https://bugs.edge.launchpad.net/~sil/+assignedbugs?field.tag=ubuntuone-karmic - 2
[15:14] <aquarius> I believe that to be it
[15:17] <dobey> BadOmen: no, it's not under the "My Computers" page on your account. it's the page where you click "Add this computer" so that the client can access your account
[15:19] <BadOmen> how do i get to that page then?
[15:20] <jblount> BadOmen: https://one.ubuntu.com/account/machines/ ?
[15:21] <BadOmen> no it says: "You haven't added any computers or devices to your Ubuntu One account. To get started please visit the installation details"
[15:23] <BadOmen> I think I got the page you want whene I started the computer. That page started outmaticly(english...)
[15:23] <jblount> BadOmen: Do you see a token in Passwords & Encryptions Keys ? (Applications > Accessories > Passwords and Encryption Keys)
[15:23] <BadOmen> but i cant get it to start now.
[15:24] <jblount> BadOmen: You get to the page to 'add a computer' through a authentication hand off that the client does when there is not a token on your computer. It establishes a relationship between your computer and the Ubuntu One server.
[15:24] <dobey> BadOmen: quit the applet
[15:25] <dobey> BadOmen: and then start it again, and it should open the page
[15:25] <BadOmen> :jblount i am trying to finde my way to the manu but it is in swedish so it can take a minute :)
[15:26] <jblount> BadOmen: If you want to speed up the process, what dobey suggested should work, he wrote the client stuff :)
[15:26] <jblount> BadOmen: Or you could run it from the terminal (the passwords app is named 'seahorse')
[15:26] <BadOmen> I have restarted the aplet and that worked :)
[15:27] <BadOmen> It all works fine now :D
[15:27] <BadOmen> thanx!
[15:27] <jblount> BadOmen: Neat :)
[15:29] <BadOmen> I think it wolud be good to have an add this computer butten under Manage the computers on your Ubuntu One account.
[15:29] <BadOmen> you can remove it from there than it would be god to be able to add it as well
[15:30] <dobey> the client has to do that, not the server. so we can't put that on the web page
[15:30] <markgsaye> jblount: I (somehow) have 7 computers listed against my account (and I only have 3 computers) - can I see which computer id relates to which hardware/user account?
[15:30] <BadOmen> thanx to yoe to dobey :)
[15:30] <jblount> markgsaye: :(, not yet. If it makes you feel better, I have ~30 or so, and I've only used three laptops :)
[15:31] <BadOmen> can you put it in the panel icon then?
[15:31] <markgsaye> jblount: ok, np, if I remove all the computers from my account, I can re-create them right?
[15:31] <jblount> markgsaye: The plan is to make that user-editable, but I haven't finished the work yet. I don't think the hashes map to something repeatable on your computers, although I'd be happy to hear that I was wrong.
[15:31] <jblount> markgsaye: Yep, the next time the client runs, it should popup a request to authenticate.
[15:32] <dobey> BadOmen: "Connect" does that if there's no token, or if authentication failed. and according to the log you pastebinned, it was working :)
[15:32] <BadOmen> okey :)
[15:33] <BadOmen> if it is working but the user think it's hard to get then it is not working as it should ;)
[15:34] <dobey> unfortunately we don't get to control how the user's web browser works :(
[15:34] <BadOmen> the program is realy god and you have all done a real good work so i dont want to compalin just give feedback :)
[15:35] <BadOmen> but the aplet, there you can have a ad this computer button. And it can check if its added or not already befor it ads the computer.
[15:38] <BadOmen> the New button thats making a folder is working when it feellike it.
[15:39] <BadOmen> with firefox 3.5.2
[15:42] <jblount> BadOmen: Some of us are in London at the moment trying to fix some of the problems with the website, but if it helps you can make your directories on your local computer instead of the web. That should work well :)
[15:43] <BadOmen> Aha thanx :) I realy like tha program and will use it :) so thanx a lot for this app :D and good by.
[15:56] <dobey> thanks jblount
[16:03] <jblount> dobey: Your my hero.
[18:24] <pablo__> hi
[18:24] <pablo__> some one??
[18:24] <pablo__> how to setup ubuntu one in karmic alpha 6 ??
[21:55] <Ng> is there something special I need to do to make desktopcouch stuff spring to life? I noticed starting gwibber-daemon it says "WARNING:root:desktopcouch is not available. .  falling back to gconf"