ssl patch removed ARM section, file no longer exists

It was renamed to root_darwin_ios.go.

Tested and works for me!

@GrahamcOfBorg build direnv

... build direnv

buildGo{Module,Package} is still on go_1_14.

I had a Go test suite test failure on Fedora 31:

--- FAIL: TestChown (0.00s)
    os_unix_test.go:58: gid: 100
    os_unix_test.go:70: groups:  [65534 100]
    os_unix_test.go:73: chown /tmp/_Go_TestChown273750579 -1 65534: chown /tmp/_Go_TestChown273750579: invalid argument
--- FAIL: TestFileChown (0.00s)
    os_unix_test.go:101: gid: 100
    os_unix_test.go:113: groups:  [65534 100]
    os_unix_test.go:116: fchown /tmp/_Go_TestFileChown026046966 -1 65534: chown /tmp/_Go_TestFileChown026046966: invalid argument
--- FAIL: TestLchown (0.00s)
    os_unix_test.go:153: gid: 100
    os_unix_test.go:168: groups:  [65534 100]
    os_unix_test.go:171: lchown /tmp/_Go_TestLchown1881673892 -1 65534: lchown /tmp/_Go_TestLchown1881673892: invalid argument
FAIL
FAIL    os      0.655s

UPDATE: dmesg doesn't show any errors wrt to the presumed EINVAL syscall return value.

@problame I encountered a similar thing on armv7l. The distinction seemed to be sandbox vs no-sandbox

armv7l builds and seems to function.

Should we keep/remove the procps dependency? Removing it on linux doesn't seem to break tests and removes lots of dependencies from the build closure.

@ofborg build go_1_15

@zowoq I'm wondering what the state of this is. Which builds do not work right now?

Can we still move forward without setting go1.15 as the default? go1.14 had a regression and projects like Kubernetes now require 1.15…

Can we still move forward without setting go1.15 as the default?

Yes, we can merge this and switch the default in another PR.

@ofborg build go_1_15