On Wed, Mar 25, 2015 at 7:29 AM, Martin Packman
martin.pack...@canonical.com wrote:
On 13/03/2015, Martin Packman martin.pack...@canonical.com wrote:
That said, if there are any packages you think we should *not* gate
landings on their test suite passing yet, please say now.
With the
On 13/03/2015, Martin Packman martin.pack...@canonical.com wrote:
That said, if there are any packages you think we should *not* gate
landings on their test suite passing yet, please say now.
With the lack of objections, I've gone ahead and made the more active
projects in the juju namespace
On Wed, Mar 25, 2015 at 8:57 AM, Rick Harding rick.hard...@canonical.com
wrote:
If you're using the github lander make sure the user has made it's org
membership public.
kat-co's membership to go-goose is public.
I think we used to have this same issue with juju, but not for a long time.
On 24/03/2015, Andrew Wilkins andrew.wilk...@canonical.com wrote:
Katherine just tried to $$merge$$ a go-goose branch, and it looks like the
script is broken: https://github.com/go-goose/goose/pull/3
Tests passed, but merge failed. Ian merged manually.
Hmm, would have been nice to send it
I reviewed the cassandra spike merge proposal. The branch fail to run on
the automated testing infrastructure.
https://bugs.launchpad.net/charms/+bug/1419116
- Matt Bruzek matthew.bru...@canonical.com
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
The MAAS oauth keys contain a ':' which is an illegal character in YAML.
You'll need to wrap it in quotation marks to resolve that.
On Tue, Mar 24, 2015 at 1:43 PM José Antonio Rey j...@ubuntu.com wrote:
This should be because of a formatting error on your environments.yaml
file. Can you check
Hi,
I receive a error in line 203 of environments.yaml
:found character that cannot start token
does this have todo with the maas oauth
Best,
Steve
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
This should be because of a formatting error on your environments.yaml
file. Can you check that the value in line 203 has the correct
formatting and is the one intended to be there?
On 03/24/2015 12:39 PM, Stephen Drotar wrote:
Hi,
I receive a error in line 203 of environments.yaml
