What is happening with the 1.11.2 (nee 1.11.1) release

[David Cheney]

Update 05/07/2013 - I've been trying workarounds to get 1.11.2 going. My
less invasive ones have failed so i'm moving on to more egregious ones now.


On Wed, Jul 3, 2013 at 3:51 PM, David Cheney <david.cheney at canonical.com>wrote:

> Update 03/07/2013 - i've traced the issue to
>
> % dpkg -l | grep golang
> ii  golang-go                                 2:1.0.2-2
>                amd64        Go programming language compiler
> ii  golang-src                                2:1.0.2-2
>                amd64        Go programming language compiler - source files
>
> (modulo the even earlier version in P)
>
> The exact cause of why this version causes issues with Juju talking to EC2
> is not known at this time.
>
>
> On Tue, Jul 2, 2013 at 6:18 PM, David Cheney <david.cheney at canonical.com>wrote:
>
>> +cc: jamespage
>>
>>
>> On Tue, Jul 2, 2013 at 5:30 PM, David Cheney <david.cheney at canonical.com>wrote:
>>
>>> Ok, mystery number one solved. The reason why the go-curl/precise issue
>>> didn't show up in the PPA build is the recipe only builds cmd/juju and
>>> cmd/jujud and gwacl is not part of that build. When it did become a part of
>>> the build this would have failed on precise.
>>>
>>>
>>> On Tue, Jul 2, 2013 at 4:33 PM, David Cheney <david.cheney at canonical.com
>>> > wrote:
>>>
>>>> Hello,
>>>>
>>>> Here is a short status update on the 1.11.2 release.
>>>>
>>>> The release was originally scheduled for the friday, there was a delay
>>>> while a final bug fix was committed, as the 1.11.1 tag was cut by then, the
>>>> release version has been bumped to 1.11.2. Sorry for the confusion.
>>>>
>>>> The next attempt at the release was made this Monday. The code built
>>>> fine and was pushed in to the juju/devel PPA, and tools tarballs were
>>>> pushed up to s3 however during the release validation afterwards this
>>>> release was not able to bootstrap any ec2 environments (status of other
>>>> environments unknown; not attempted).
>>>>
>>>> Building locally from the same source failed to reproduce the problem.
>>>> Searching the archive this issue has happened before,
>>>> https://lists.ubuntu.com/archives/juju-dev/2013-April/000913.html, but
>>>> we failed to investigate at the time.
>>>>
>>>> During diagnosis of this problem a new issue was discovered[1];
>>>> juju-core cannot build on Precise builders due to a bug in the version of
>>>> Go that ships with P.
>>>>
>>>> What is more confusing is on Monday a successful build of 1.11.2 was
>>>> made from a builder that claims to be running Precise. Trying to replicate
>>>> this on a Precise machine showed that 1.11.2 could _not_ be built on
>>>> Precise.
>>>>
>>>> So, we have at least two problems. Both are related to what the
>>>> builders have installed on them and the way it affects the final bits that
>>>> lands the juju/devel PPA.
>>>>
>>>> Dave
>>>>
>>>> [1] https://bugs.launchpad.net/juju-core/+bug/1196811
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130705/94fad21d/attachment.html>