On 5 December 2013 18:52, Mark Shuttleworth m...@ubuntu.com wrote:
On 04/12/13 17:34, Peter Waller wrote:
This situation is now resolved with thanks to Roger, Gustavo and
others in real time. There is no way we could have resolved it
ourselves since there was corruption of the juju database
Hello all,
I've released the first version of a Python Library designed to interact
with data from charmworld (https://manage.jujucharms.com). Currently this
library is used by charm-tools to interact with the available charms and
bundles in the ecosystem. This isn't considered a stable API and
Thanks. Filed a report at
https://lists.ubuntu.com/archives/juju/2013-December/003323.html
max
--
max cantor
Sent with Airmail
On December 9, 2013 at 3:50:55 PM, Robbie Williamson
(robbie.william...@canonical.com) wrote:
Thanks for the report Max. Would it be possible for you to open a bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-12-10 4:11, max cantor wrote:
Thanks. Filed a report at
https://lists.ubuntu.com/archives/juju/2013-December/003323.html
max
I think that was just a copypaste error, as that is a link to
Robbie's email to you. I think you meant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
Did you check the 'mgo' source as well? I thought I remember when
you first connect it uses eval to get date stamps to check for
clock skew.
I think you might be thinking of the state/presence package there,
which uses eval for pre-2.4
On Tue, Dec 10, 2013 at 5:16 AM, Curtis Hovey-Canonical
cur...@canonical.com wrote:
Gentlemen.
Juju-core 1.16.5 has one bug preventing us from doing a release. CI
has blessed lp:juju-core/1.16 r1998. Do we want to defer the
destroy-machine --force bug?
