Matty,
I do think that a bug should be opened for it, and I will do so. Is LP
still the better place to open the bug vs GitHub?
On Wed, Oct 21, 2015 at 5:48 AM, Matthew Williams <
matthew.willi...@canonical.com> wrote:
> Hey Folks,
>
> Is there some action we should take to deal with this - in
On Wed, Oct 21, 2015 at 1:49 PM, Cory Johns
wrote:
> Matty,
>
> I do think that a bug should be opened for it, and I will do so. Is LP
> still the better place to open the bug vs GitHub?
>
Yes, please open the bug in Launchpad.
Thanks,
Casey
>
> On Wed, Oct 21,
Hey Folks,
Is there some action we should take to deal with this - in which case can
we raise an lp bug for it. Or do we think there's no action needed?
Matty
On Tue, Oct 6, 2015 at 3:55 PM, Matt Bruzek
wrote:
> Merlijn,
>
> Now that I see more of what you are
Merlijn,
Now that I see more of what you are doing I have an alternate suggestion.
When you are running 'juju init' use the su command to run as the "ubuntu"
user.
su - ubuntu -c 'juju init'
Using the su command in this way gives a "login" environment for the user
"ubuntu". I wrote a charm
Hi
I'm developing a Charm that installs the Juju client, among other things.
I'm having some trouble getting this to work. When I use juju debug-hooks
and manually run the install hook, everything works fine. However, when the
hook is executed by Juju automatically, I get strange errors such as
Hell again Merlijn,
It was nice to see you at the Charmer summit! This is a very interesting
use of Juju.
What you are seeing is what we call a "hook context". Hooks execute with
root authority and have certain environment variables are set. This is so
Juju commands and tools work correctly.