On Wed, Mar 19, 2014 at 8:43 AM, Adam Collard
wrote:
>
> On 19 March 2014 13:22, John Meinel wrote:
>>
>> As of right now (2014-05-19 11:20 UTC) streams.canonical.com no longer
>> lists 1.17.[1-5] as available. At least if I go here:
>>
>> http://streams.canonical.com/juju/streams/v1/com.ubuntu.j
On 19 March 2014 13:22, John Meinel wrote:
> As of right now (2014-05-19 11:20 UTC) streams.canonical.com no longer
> lists 1.17.[1-5] as available. At least if I go here:
>
> http://streams.canonical.com/juju/streams/v1/com.ubuntu.juju:released:tools.json
> vs going here:
>
> http://juju-dist.s3
As of right now (2014-05-19 11:20 UTC) streams.canonical.com no longer
lists 1.17.[1-5] as available. At least if I go here:
http://streams.canonical.com/juju/streams/v1/com.ubuntu.juju:released:tools.json
vs going here:
http://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju:released:to
On Mon, Mar 17, 2014 at 10:18 PM, John Meinel wrote:
> Thanks for clarifying the process. It does still seem strange that we copy
> to mirrors before the official location, but I understand the build process.
> I'm not sure if we want to slow down dev releases to wait a day to get
> streams update
I think it is the CI groups private bucket. It was a link I followed from
Vincent, and I didn't pay attention to our internal URLs. I wish I had
noticed, since then I could have pointed him at the official location. I
guess I was just thrown off that streams.canonical.com wasn't updated.
Thanks f
On Mon, Mar 17, 2014 at 12:14 PM, Curtis Hovey-Canonical
wrote:
> On Mon, Mar 17, 2014 at 5:01 AM, John Meinel wrote:
>
>> nor are they in HP:
>>
>> https://region-a.geo-1.objects.hpcloudsvc.com/v1/11289530460295/tools/streams/v1/com.ubuntu.juju:released:tools.json
>
> I don't know what 112895
On Mon, Mar 17, 2014 at 5:01 AM, John Meinel wrote:
> nor are they in HP:
>
> https://region-a.geo-1.objects.hpcloudsvc.com/v1/11289530460295/tools/streams/v1/com.ubuntu.juju:released:tools.json
I don't know what 11289530460295 is (The scripts publish to
60502529753910 and since the mirror fi
On Mon, Mar 17, 2014 at 5:01 AM, John Meinel wrote:
>> I'm very happy to see this built, but we have a small problem with our
>> process. Specifically:
>> 1) the juju-1.17.5 client was created and published to the devel ppa
>> 2) before the jujud 1.17.5 tools were published to streams.canonical
Note that I *do* see tools available on EC2 and Canonistack
http://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju:released:tools.json
http://juju-dist.s3.amazonaws.com/tools/releases/juju-1.17.5-precise-amd64.tgz
https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e346458
On Sat, Mar 15, 2014 at 1:11 AM, Curtis Hovey-Canonical
wrote:
> juju-core 1.17.5
>
> A new development release of Juju, juju-core 1.17.5, is now available.
>
>
> Getting Juju
>
> juju-core 1.17.5 is available for trusty and backported to earlier
> series in the following PPA:
> https://launch
Great work everybody! I'm glad to see this release out in the wild, with
such a long list of resolved issues.
--Mark
On Fri, Mar 14, 2014 at 4:11 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:
> juju-core 1.17.5
>
> A new development release of Juju, juju-core 1.17.5, is now availab
juju-core 1.17.5
A new development release of Juju, juju-core 1.17.5, is now available.
Getting Juju
juju-core 1.17.5 is available for trusty and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
Upgrading from stable releases to development rele
12 matches
Mail list logo
