-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-27 05:30 PM, roger peppe wrote:
That fallback code was designed to be around for only a short time
- I'd suggest removing it.
We have bugs about the fact that the fallback code has been removed:
Hi Nate,
I looked into your bug. The default value for control-bucket was not
being set. Here's a PR to fix: http://reviews.vapour.ws/r/1512/
Cheers,
Jess
On 29/04/15 06:41, Nate Finch wrote:
No one seems to be answering my actual question. That error message
seems new. Is it? Either
On 29/04/15 04:41, Nate Finch wrote:
No one seems to be answering my actual question. That error message seems
new. Is it? Either way, the error message is incorrect - control bucket is
not required - and whatever is emitting that message needs to be fixed.
On Apr 28, 2015 2:32 PM, Aaron
I mean, the control-bucket configuration value in the ec2 section of your
environments.yaml is not required, and thus the error message is incorrect.
On Tue, Apr 28, 2015 at 10:26 PM, Ian Booth ian.bo...@canonical.com wrote:
On 29/04/15 04:41, Nate Finch wrote:
No one seems to be answering
The .jenv code was introduced prior to 1.16. How far back
in time do we need to preserve compatibility? (genuine
question)
If transitioning to the new scheme is really an issue, it
would be easy to write a very simple tool that would
allow a .jenv file to be created from an existing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-28 11:42 AM, roger peppe wrote:
The .jenv code was introduced prior to 1.16. How far back in time
do we need to preserve compatibility? (genuine question)
We need to support every mode of operation that 1.18 supported. Juju
has a
No one seems to be answering my actual question. That error message seems
new. Is it? Either way, the error message is incorrect - control bucket is
not required - and whatever is emitting that message needs to be fixed.
On Apr 28, 2015 2:32 PM, Aaron Bentley aaron.bent...@canonical.com
wrote:
