In the charm store and the bundle specification, we use both fully
specified charm URLs (with series) and partially specified charm URLs
(without series and/or version).
Currently in the charm package, the charm.URL type represents the
former, the charn.Reference type represents the former; but th
In the charm store and the bundle specification, we use both fully
specified charm URLs (with series) and partially specified charm URLs
(without series and/or version).
Currently in the charm package, the charm.URL type represents the
former, the charn.Reference type represents the former; but th
Casey is the one to talk to. I'm not sure if he was just trying to be
conservative, but he did intentionally not want to pun the types. I think
he wanted to be clear that things passed to *these* API calls must be fully
formed, while ones passed to *those* could be expanded.
We could do what you sa
On Wed, Jul 23, 2014 at 7:35 AM, roger peppe wrote:
> We want to store charm URLs in mongo-db that are agnostic whether
> the series is specified or not. For example, in a bundle, a service
> is free to specify a series in the charm name or not.
That sounds slightly surprising. How do we plan to
On Wed, 23 Jul 2014, Gustavo Niemeyer wrote:
> On Wed, Jul 23, 2014 at 7:35 AM, roger peppe wrote:
> > We want to store charm URLs in mongo-db that are agnostic whether
> > the series is specified or not. For example, in a bundle, a service
> > is free to specify a series in the charm name or not
On 23 July 2014 11:51, John Meinel wrote:
> Casey is the one to talk to. I'm not sure if he was just trying to be
> conservative, but he did intentionally not want to pun the types. I think he
> wanted to be clear that things passed to *these* API calls must be fully
> formed, while ones passed to
On Wed, Jul 23, 2014 at 9:13 AM, Richard Harding
wrote:
> This is driven by requirements from ecosystem and users where bundles
> define a 'solution'. A mongodb-cluster bundle doesn't need to be updated
> every time a new revision comes out, or even if a new series comes out. It
> is a usable solu
On Wed, Jul 23, 2014 at 9:59 AM, roger peppe wrote:
> The charm URL in a bundle means exactly what it would mean if
> you typed it in a juju deploy command. That is, it is dependent
> on the charms available at bundle deploy time.
I would fix that instead.
> I do believe having just URL would be
Hey all,
I thought my first post to the list would be something relatively innocuous
:)
Have we ever considered enhancing our IRC bot to report CI status? Maybe
start off with important notifications such as job failures? It might bring
more attention to the health of trunk, and IRC is already a
This is the current list of regressions that block a release
C:/Juju/lib/juju/nonce.txt does not exist, bootstrap failed in win
https://bugs.launchpad.net/juju-core/+bug/1342725
reported 2014-07-16, but is a manifestation of an evolving
issue from June
Juju restore fails Could not get
I'm on the nonce.txt bug.
On Wed, Jul 23, 2014 at 11:34 AM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> This is the current list of regressions that block a release
>
> C:/Juju/lib/juju/nonce.txt does not exist, bootstrap failed in win
> https://bugs.launchpad.net/juju-core/+bug/
Im on the restore bug
On Wed, Jul 23, 2014 at 12:38 PM, Nate Finch wrote:
> I'm on the nonce.txt bug.
>
>
> On Wed, Jul 23, 2014 at 11:34 AM, Curtis Hovey-Canonical
> wrote:
>>
>> This is the current list of regressions that block a release
>>
>> C:/Juju/lib/juju/nonce.txt does not exist, bootst
On Mon, Jul 7, 2014 at 6:40 AM, Andrew Wilkins
wrote:
> On Sat, Jul 5, 2014 at 4:05 AM, Antonio Rosales
> wrote:
>>
>> On Thu, Jul 3, 2014 at 7:41 PM, Andrew Wilkins
>> wrote:
>> > On Fri, Jul 4, 2014 at 5:23 AM, Tim Penhey
>> > wrote:
>> >>
>> >> I do just want to make the point that we are no
Cool. I'll have a look. :)
-eric
On Tue, Jul 22, 2014 at 10:30 PM, John Meinel wrote:
> https://docs.google.com/a/canonical.com/document/d/1hXAOBVpM8o--9L7GOb4r6NUaloZQ8BsWj8W-Bqpznpw/edit?usp=sharing
> is about how CI is set up today, and how to add more tests there.
>
> John
> =:->
>
>
> On T
Great timing, Kate.
I was recently asked to take care of mup's deployment again, and I'm
about to put live its third incarnation, reviving a hack I started
back in 2011 to port the ancient Erlang bot I wrote too many years ago
into a Go version. My goal, among other things, is to make plugin
writi
Great to hear!
I'd love to scan your erlang code. I started learning it awhile ago, but I
never attempted any serious projects.
On Wed, Jul 23, 2014 at 12:02 PM, Gustavo Niemeyer
wrote:
> Great timing, Kate.
>
> I was recently asked to take care of mup's deployment again, and I'm
> about to pu
On Wed, Jul 23, 2014 at 11:34 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> This is the current list of regressions that block a release
>
> C:/Juju/lib/juju/nonce.txt does not exist, bootstrap failed in win
> https://bugs.launchpad.net/juju-core/+bug/1342725
> reported 2014-
Hi all,
If you are hitting the magic merge it button on github because the
project isn't yet landed with the bot, please make sure you run the
tests before actually merging the code.
The juju/testing package didn't actually have passing tests, because
some tests were added that were missing a fun
I believe Martin has been investigating updating the bot to support all of
our shared code. I certainly agree with this sentiment, but I'd rather not
train people to be in the habit of just clicking the button if we can get
the bot running soon.
John
=:->
On Thu, Jul 24, 2014 at 9:57 AM, Tim Pen
Forgot to replay-all
Forwarded Message
Subject: Re: Please run the tests
Date: Thu, 24 Jul 2014 16:49:27 +1000
From: Ian Booth
To: Tim Penhey
The Jenkins jobs to test before landing all the Juju sub reps are almost ready.
So it won't be an issue for much longer hopefully.
On
20 matches
Mail list logo
