-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Golang 1.9.4 #6326
Update to Golang 1.9.4 #6326
Conversation
waiting for CI before tagging for review. |
9347930
to
3bfa5da
Compare
Since 1.9.4, go restrict the usage of |
Check |
@andrewkroh |
I am thinking about upgrading the psutil lib, they have removed the custom ldflags, I've also notified the issues concerning the compiled with a newer version |
Some core package aren't updated for this issue, see
|
Weird psutil should have worked, the flag is in the whitelist. |
@ph Seeing that you updated some |
I have changed strategy,I won’t update them if possible
On Thu, Feb 8, 2018 at 6:48 PM Nicolas Ruflin ***@***.***> wrote:
@ph <https://github.com/ph> Seeing that you updated some x packages, this
PR is kind of related by @cyrilleverrier
<https://github.com/cyrilleverrier> #6246
<#6246>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6326 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAACgN4fRAYQLF7wZdacYzQ_k3Y5XaqUks5tS4fWgaJpZM4R-06X>
.
--
ph
|
30de83e
to
e889e67
Compare
@@ -52,7 +52,7 @@ NOSETESTS_OPTIONS?=--process-timeout=$(TIMEOUT) --with-timer -v --with-xunit --x | |||
TEST_ENVIRONMENT?=false ## @testing if true, "make testsuite" runs integration tests and system tests in a dockerized test environment | |||
SYSTEM_TESTS?=false ## @testing if true, "make test" and "make testsuite" run unit tests and system tests | |||
STRESS_TESTS?=false ## @testing if true, "make test" and "make testsuite" run also run the stress tests | |||
GOX_OS?=linux darwin windows solaris freebsd netbsd openbsd ## @Building List of all OS to be supported by "make crosscompile". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An "f" is missing from "freebsd".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤕
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed.
e889e67
to
1cb18f8
Compare
@ph Should we open an issue to readd solaris as soon as the above issue is fixed? |
@ph One more question: You have added the backport label. Not sure what the advantage would be to backport this to 6.2? Brew? |
vendor/vendor.json
Outdated
@@ -1025,6 +1025,14 @@ | |||
"revision": "5bf94b69c6b68ee1b541973bb8e1144db23a194b", | |||
"revisionTime": "2017-03-21T23:07:31Z" | |||
}, | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why this is added as I does not seem we use the "top level" gopsutil package anywhere. How did you "update" gopsutil?
Keep up with the latest version of Golang. Version prior to 1.9.4 are affected by security issues on build. `go get` could have been used to do unwanted code execution[1] CVE-2018-6574 during build. The changes in golang now enforce more restrictive pragma declaration when linking and compiling. This commits, disable crosscompiling under solaris which requires an update on the standard library. ``` ../vendor/golang.org/x/sys/unix/zsyscall_solaris_amd64.go:13:3: //go:cgo_import_dynamic libc_pipe pipe "libc.so" only allowed in cgo-generated code ../vendor/golang.org/x/sys/unix/zsyscall_solaris_amd64.go:14:3: //go:cgo_import_dynamic libc_getsockname getsockname "libsocket.so" only allowed in cgo-generated code ``` We also update popsutil, thag was incorrectly defining an ldflags in a previous release making the build fails under the new restriction. [1] golang/go#23672
1cb18f8
to
00cadd7
Compare
@ruflin good catch, I've learned today.
For two reason:
|
@ruflin Is there anything missing in this PR? |
Are we fine with with backporting to 6.2? If so before or after 6.2.2?
On Tue, Feb 13, 2018 at 4:08 PM Nicolas Ruflin ***@***.***> wrote:
Merged #6326 <#6326>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6326 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAACgDElP0xtooXzmROa20O3y9j8B7K6ks5tUfnBgaJpZM4R-06X>
.
--
ph
|
Currently we have decided not to backport it to 6.2. |
Keep up with the latest version of Golang.