https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1194022

[David Cheney]

I don't know how to solve the problem with the builders and their no
backports policy, all I can add that if it is _not_ solved, we'll be on our
own with an unsupported version of Go.

To be clear, 1.0.x is a dead end, it will be receiving no new fixes
upstream.

I can speak for the Go project if there is a mechanism to get 1.1 SRU'd
into P.


On Mon, Jun 24, 2013 at 5:18 PM, John Arbash Meinel
<john at arbash-meinel.com>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2013-06-24 11:00, David Cheney wrote:
> > Hello,
> >
> > This is the bug we need resolved for juju on arm. We also need this
> > backported all the way back to P so we can get Juju off the older
> > versions they are using.
> >
> > If you have the ability to make this happen, please do so.
> >
> > Cheers
> >
> > Dave
> >
> >
>
> As I've mentioned before, we can likely get go 1.0.3 SRU'd into
> Precise, and we can get 1.1.1 into a backport. However, the builders
> are set up such that you can only build code with SRU'd packages. So
> even when we have a backport of juju-1.10+ into Precise, it will still
> be built with 1.0.3.
>
> We can do our own build in a PPA or whatever, and we can make sure
> that the tools we upload as 'juju-tool-x.y.tgz' are built with 1.1.1.
> But the stuff that will be in the default archive can only really be
> built with 1.0.3.
>
> (Note that we still need at least 1.0.2 or 1.0.3 SRU'd into precise,
> as it currently only has 1.0)
>
> John
> =:->
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (Cygwin)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlHH8tkACgkQJdeBCYSNAAMkTQCgl6y/XM/cUEM2fdoUltSoBzyL
> DIkAnj0XqXR+hWla7icE7BP91VkE3d6G
> =gImX
> -----END PGP SIGNATURE-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130624/d3fa9403/attachment.html>