[almighty] Upgrading to go 1.7.3

[Aslak Knutsen]

Upgrade postponed until further notice.

-aslak-

On Fri, Nov 4, 2016 at 12:47 PM, Aslak Knutsen <aslak at redhat.com> wrote:

>
> On Fri, Nov 4, 2016 at 12:35 PM, Karanbir Singh <kbsingh at redhat.com>
> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 04/11/16 08:25, Konrad Kleine wrote:
>> > Go for it! :)
>> >
>> > On Fri, Nov 4, 2016 at 1:35 AM, Aslak Knutsen <aslak at redhat.com
>> > <mailto:aslak at redhat.com>> wrote:
>> >
>> > https://github.com/almighty/almighty-core/pull/433
>> > <https://github.com/almighty/almighty-core/pull/433>
>> >
>> > When that is pulled, almighty-core will no longer compile under go
>> > 1.6.
>> >
>> > -aslak-
>> >
>>
>> we dont have system support for go-1.7 as yet,
>>
>>
> This only effects Build time. Runtime we only have a binary blob.
>
>
>
>> what is the driving req for this upgrade ?
>>
>>
> The cause of the update is described here:
> https://github.com/almighty/almighty-core/issues/427
>
>
>>
>> - --
>> Karanbir Singh, Project Lead, The CentOS Project, London, UK
>> Red Hat Ext. 8274455 | DID: 0044 207 009 4455
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.22 (GNU/Linux)
>>
>> iQEcBAEBAgAGBQJYHHJ5AAoJEI3Oi2Mx7xbt29oH/2qXeL/ix/RbrdTsxea7jucA
>> gRWqvETDO/iOTYMbhk/0tafSJVrpw5X2Ukr+eV19Cs5Akc/MvjGQgQnt0lAl9+yN
>> rK6xw1WAykvf9bfeOONTDR5Wh26JZdEnDY3jUCWImUx6MS9fIUGN7e+X/5BriChR
>> rPJ7hA7aVTdhNQ96D4UkVMyBya4KLyua6TGv/0t6YAHmifyOBODvpvefdwQMoYlc
>> kJq472BfdNI1FmbkoeW74+bUhJzYhoYfgDBqfRCAKFJGm5kYZDKOTAA3LtvrpO5L
>> hKuDoU+FOXe7J9NDwJNgd7oVk+dyhVDduTmR8Zf/jZkJOTt87kwAnN/Okc3lf94=
>> =4Fax
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> almighty-public mailing list
>> almighty-public at redhat.com
>> https://www.redhat.com/mailman/listinfo/almighty-public
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20161104/5b411b70/attachment.htm>