-
Notifications
You must be signed in to change notification settings - Fork 66
Switch go builds from epel-testing to epel stable #4618
Comments
@alexeykazakov maybe it would be nice to move to goa 1.4 to be able to use golangv1.11, see comment fabric8-services/build-tool-detector#28 (comment) |
@corinnekrych absolutely. We are planning to investigate goa 1.4 move in our cluster service - fabric8-services/fabric8-cluster#13 |
This patch is to use go library from epel-release in spite of epel-testing Fix related to openshiftio/openshift.io#4618
This patch is to use go library from epel-release in spite of epel-testing Fix related to openshiftio/openshift.io#4618
This patch is to use go library from epel-release in spite of epel-testing Fix related to openshiftio/openshift.io#4618
This patch is to use go library from epel-release in spite of epel-testing Fix related to openshiftio/openshift.io#4618
This patch is to use go library from epel-release in spite of epel-testing Fix related to openshiftio/openshift.io#4618
@sbose78 I see that f8-wit also would face same issue with http/proxy and reverseproxy which f8-auth faced in last week. Issue: fabric8-services/fabric8-auth#734 cc: @alexeykazakov |
Right. This is why I’ve created a PR to update WIT a week ago - fabric8-services/fabric8-wit#2377 |
We need to switch all our go repos from using go from epel-testing to epel (stable)
The text was updated successfully, but these errors were encountered: