On 30 October 2014 14:34, Eric Snow eric.s...@canonical.com wrote:
On Thu, Oct 30, 2014 at 4:40 AM, roger peppe roger.pe...@canonical.com
wrote:
It's a pity then that if you go get a package, origin is the repo
you've branched from. There is always one of those, but you
don't necessary have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have discovered a regression in juju set-env. I have filed a bug
accordingly:
https://bugs.launchpad.net/juju-core/+bug/1388073
A recent change to juju broke set-env, so that it no longer accepts
empty values.
In old versions this worked:
juju
On Fri, Oct 31, 2014 at 8:35 AM, Curtis Hovey-Canonical
cur...@canonical.com wrote:
On Thu, Oct 30, 2014 at 2:10 PM, Eric Snow eric.s...@canonical.com wrote:
What would be the best approach for deprecating the old backup plugin?
I was going to simply gut it (it's a bash script) and stick in a
FWIW, I always branch off upstream/master. I don't have master synced to
my repo, because it just seems like an extra step. Why not go straight to
the source?
On Oct 31, 2014 11:48 AM, Eric Snow eric.s...@canonical.com wrote:
On Fri, Oct 31, 2014 at 2:11 AM, roger peppe
