What is happening with the 1.11.2 (nee 1.11.1) release

[David Cheney]

Sounds like a great solution.


On Wed, Jul 3, 2013 at 7:33 PM, James Page <james.page at canonical.com> wrote:

> On 03/07/13 10:24, John Arbash Meinel wrote:
>
>> OK - 1.1.1 is stuck in Debian NEW as the maintainer has enabled a
>>> >load of cross archive compiler packages (not sure if they are
>>> >useful for juju-core or not - they include windows and other
>>> >packages).
>>> >
>>> >I'll pull this direct from the Debian VCS and stick it in a PPA
>>> >for
>>>
>>>> >>= 12.04 so we can get some early exposure to it and use it for
>>>>
>>> >the juju-core build toolchain.
>>> >
>>> >Does that make sense?
>>>
>> Sounds reasonable to me. The big question is whether there will be a
>> chance-in-hell of getting 1.1.1 into P for official "juju" (the
>> client) builds.
>>
>
> Well if we can sort-out backports then maybe.
>
>
>  I could live with "use this stable PPA to run juju-the-client on P,
>> though".
>>
>
> Yeah - thats the short-term/fallback plan anyway.
>
>
>  Once you have it working, I'm pretty sure this:
>> https://launchpad.net/~juju/+**archive/devel<https://launchpad.net/~juju/+archive/devel>
>>
>> Is where we would like to get go-1.1.1 into.
>>
>> Though we might start with:
>> https://launchpad.net/~juju/+**archive/experimental<https://launchpad.net/~juju/+archive/experimental>
>>
>> In PPA builds, can you depend on another PPA for build-time packages,
>> or does it have to be built in the PPA you are building from?
>>
>
> That is possible so we could have a separate toolchain PPA that all the
> other PPA's depend on.
>
>
>
> --
> James Page
> Technical Lead
> Ubuntu Server Team
> james.page at canonical.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130705/d71330a1/attachment.html>