On 17/03/15 16:20 -0400, Michael P. McGrath wrote:
----- Original Message -----From: "Vincent Batts" <vbatts redhat com> To: atomic-devel projectatomic io, "Eric Paris" <eparis redhat com> Sent: Tuesday, March 17, 2015 12:50:13 PM Subject: [atomic-devel] go1.4 requirement I see that upstream etcd is now requiring go1.4 https://github.com/coreos/etcd/issues/2524 Docker has churned on this for a while, but I have staved them off since upgrading f20, f21 and epel6 to go1.4 would deprecate a few packages (bash completion, emacs and vim editor files, etc) and this is not something I care to push mid stream. The `net/http` BasicAuth is pretty small https://golang.org/src/net/http/request.go?s=16575:16641#L518 and seems like it _could_ be easily backported, though there are other nice improvements to move forward to go1.4 for. And I'm not keen on backporting things where an upgrade of version would be easier... Thoughts?When should we decide WRT Fedora 22 requirements?
f22 and rawhide are already on go1.4.2 http://koji.fedoraproject.org/koji/packageinfo?packageID=16224 vb
Attachment:
pgpC3QqOx3U8U.pgp
Description: PGP signature