On 28 April 2015 at 19:41, Nate Finch nate.fi...@canonical.com 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 28 April 2015 at 19:32, Aaron Bentley aaron.bent...@canonical.com wrote:
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
On 29 April 2015 at 01:05, Jesse Meek jesse.m...@canonical.com wrote:
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/
I'm not entirely sure that's the right fix. The original error message
was right
Hi everyone,
Need some core help on this one, Ben, Marco and I think that the
answer to this is no for the manual provider, if someone familiar with
the manual provider could chime in here that'd be great:
https://askubuntu.com/questions/611564/how-does-juju-get-the-private-address-of-a-node
--
On 29 April 2015 at 17:10, Aaron Bentley aaron.bent...@canonical.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-29 10:43 AM, roger peppe wrote:
Once Trusty EOLs, then I think we would be able to drop
functionality that 1.18 itself used only for migration.
For example,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-29 10:43 AM, roger peppe wrote:
Once Trusty EOLs, then I think we would be able to drop
functionality that 1.18 itself used only for migration.
For example, if juju 1.18 had automatically created .jenvs from
the environments.yaml
We have done it before. As Roger said, there is/was a convention to do a
three step process to deprecate old command line functionality.
There's a big difference between what the command line looks like, and
keeping compatibility with 1.18. We might want to preserve both, but
they're not the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-29 12:31 PM, roger peppe wrote:
FWIW I seem to remember some command line flags being deprecated
(with a visible warning message) and then removed. I wonder if that
might be another possible approach that could let us avoid
unbounded
On 30 April 2015 at 07:40, Nate Finch nate.fi...@canonical.com wrote:
We have done it before. As Roger said, there is/was a convention to do a
three step process to deprecate old command line functionality.
There's a big difference between what the command line looks like, and
keeping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-29 04:10 AM, roger peppe wrote:
On 28 April 2015 at 19:32, Aaron Bentley
aaron.bent...@canonical.com wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-29 09:41 AM, Nate Finch wrote:
I think you're missing roger's point.
No, I understand his point, and I think that his extrapolation is
incorrect, and I explained how.
1.18 has some fallback code to support 1.16. However, we don't
On 29 April 2015 at 14:34, Aaron Bentley aaron.bent...@canonical.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-04-29 04:10 AM, roger peppe wrote:
On 28 April 2015 at 19:32, Aaron Bentley
aaron.bent...@canonical.com wrote:
On 2015-04-28 11:42 AM, roger peppe wrote:
The
12 matches
Mail list logo
