our description I don't understand why.
<menn0> babbageclunk: if you want to be sure your local build is used, pass --build-agent to bootstrap / upgrade-juju
<menn0> babbageclunk: i'm guessing you haven't rebased lately so your tree still has the version as 2.0.1
<menn0> babbageclunk: which means the client will use the recently released 2.0.1 instead of your own build
<menn0> it's bitten me enough that I always use --build-agent now
<babbageclunk> menn0: yeah, that'll be it. I'll do that too.
<babbageclunk> menn0: I think I'm not in the habit because it's *usually* ahead, but not in my tree at the moment.
<babbageclunk> menn0: Hmm - this tree is rebased though. Although I think it might be based on the wrong branch?
<menn0> babbageclunk: I suspect that's true for all of us
<menn0> babbageclunk: we're usually ahead, but sometimes not
<menn0> babbageclunk: and it often takes a while to figure out what's going on
<babbageclunk> menn0: It's branched off staging at the moment.
<menn0> that's it then
<babbageclunk> What should I be branching off? develop?
<menn0> babbageclunk: staging where possible
<menn0> babbageclunk: sticking with --build-agent should avoid the issue
<babbageclunk> menn0: ok, cool - thankks
<menn0> wallyworld or axw: https://github.com/juju/juju/pull/6534
<menn0> it's big and dull (sorry)
<wallyworld> :-(
<wallyworld> :-)
<menn0> wallyworld: very mechanical, you can probably skim a lot of it
<wallyworld> will do, didn't mean the :-(
<axw> wallyworld: I'm thinking I'll add an option to nova.Client to disable API version discovery, and then update juju 2.0 branch to set it. sound OK to you?
<axw> wallyworld: we've got another bug: https://bugs.launchpad.net/juju/+bug/1638704
<mup> Bug #1638704: openstack provider: if use-floating-ip=true, uses incorrect compute API endpoint to determine available floating IPs <juju:Triaged by alexis-bruemmer> <https://launchpad.net/bugs/1638704>
<wallyworld> axw: when would we enable it again?
<axw> wallyworld: when we use non-deprecated APIs
<wallyworld> so all the