summaryrefslogtreecommitdiff
path: root/lang/go
AgeCommit message (Collapse)AuthorFilesLines
2019-12-13Update go112 to 1.12.14.bsiegert1-2/+2
go1.12.13 (released 2019/10/31) fixes an issue on macOS 10.15 Catalina where the non-notarized installer and binaries were being rejected by Gatekeeper. Only macOS users who hit this issue need to update. go1.12.14 (released 2019/12/04) includes a fix to the runtime. See the Go 1.12.14 milestone on our issue tracker for details.
2019-12-09go: Split *_SUPPORTED variables out into new go-vars.mk.jperkin2-6/+27
It's not always possible to include go-package.mk earlier than bsd.prefs.mk in a package, for example if the package defines its own do-install target, so move out the *_SUPPORTED variables that need to be included first.
2019-12-08Add go113.bsiegert1-1/+2
I forgot to include this file in the go113 commit, thanks wiz@ for notifying me!
2019-12-07lang/go: add go to the tools directoryrillig1-1/+4
This makes it easier to run the Go compiler from within the build environment created by "bmake build-env".
2019-11-03lang: align variable assignmentsrillig1-12/+12
pkglint -Wall -F --only aligned --only indent -r No manual corrections.
2019-10-18Update go112 to 1.12.12.bsiegert1-2/+2
qo1.12.11 (released 2019/10/17) includes security fixes to the crypto/dsa package. See the Go 1.12.11 milestone on our issue tracker for details. go1.12.12 (released 2019/10/17) includes fixes to the go command, runtime, syscall and net packages. See the Go 1.12.12 milestone on our issue tracker for details.
2019-09-26Update go112 to 1.12.10.bsiegert1-2/+2
Commit ok'd by wiz@ for PMC. Go 1.12.10: net/http (through net/textproto) used to accept and normalize invalid HTTP/1.1 headers with a space before the colon, in violation of RFC 7230. If a Go server is used behind an uncommon reverse proxy that accepts and forwards but doesn't normalize such invalid headers, the reverse proxy and the server can interpret the headers differently. This can lead to filter bypasses or request smuggling, the latter if requests from separate clients are multiplexed onto the same upstream connection by the proxy. Such invalid headers are now rejected by Go servers, and passed without normalization to Go client applications. The issue is CVE-2019-16276 and Go issue golang.org/issue/34540. Go 1.12.9: go1.12.9 (released 2019/08/15) includes fixes to the linker, and the os and math/big packages. See the Go 1.12.9 milestone on our issue tracker for details.
2019-09-17lang/go: on osx 10.9 and earlier, use go110dbj1-1/+6
go 1.11 removed support for osx 10.8 and 10.9 https://github.com/golang/go/issues/23122
2019-09-10lang/go: update _VARGROUPS in go-package.mk, small refactoringrillig1-12/+12
2019-09-10lang/go: extend _VARGROUPS section in go-dep.mkrillig1-1/+13
2019-08-14go112: update to 1.12.8 (security release).bsiegert1-2/+2
net/http: Denial of Service vulnerabilities in the HTTP/2 implementation net/http and golang.org/x/net/http2 servers that accept direct connections from untrusted clients could be remotely made to allocate an unlimited amount of memory, until the program crashes. Servers will now close connections if the send queue accumulates too many control messages. The issues are CVE-2019-9512 and CVE-2019-9514, and Go issue golang.org/issue/33606. Thanks to Jonathan Looney from Netflix for discovering and reporting these issues. This is also fixed in version v0.0.0-20190813141303-74dc4d7220e7 of golang.org/x/net/http2. net/url: parsing validation issue url.Parse would accept URLs with malformed hosts, such that the Host field could have arbitrary suffixes that would appear in neither Hostname() nor Port(), allowing authorization bypasses in certain applications. Note that URLs with invalid, not numeric ports will now return an error from url.Parse. The issue is CVE-2019-14809 and Go issue golang.org/issue/29098. Thanks to Julian Hector and Nikolai Krein from Cure53, and Adi Cohen (adico.me) for discovering and reporting this issue.
2019-08-14go111: update to 1.11.13 (security release).bsiegert1-2/+2
net/http: Denial of Service vulnerabilities in the HTTP/2 implementation net/http and golang.org/x/net/http2 servers that accept direct connections from untrusted clients could be remotely made to allocate an unlimited amount of memory, until the program crashes. Servers will now close connections if the send queue accumulates too many control messages. The issues are CVE-2019-9512 and CVE-2019-9514, and Go issue golang.org/issue/33606. Thanks to Jonathan Looney from Netflix for discovering and reporting these issues. This is also fixed in version v0.0.0-20190813141303-74dc4d7220e7 of golang.org/x/net/http2. net/url: parsing validation issue url.Parse would accept URLs with malformed hosts, such that the Host field could have arbitrary suffixes that would appear in neither Hostname() nor Port(), allowing authorization bypasses in certain applications. Note that URLs with invalid, not numeric ports will now return an error from url.Parse. The issue is CVE-2019-14809 and Go issue golang.org/issue/29098. Thanks to Julian Hector and Nikolai Krein from Cure53, and Adi Cohen (adico.me) for discovering and reporting this issue.
2019-07-14Update go112 to 1.12.7.bsiegert1-2/+2
This fixes a nasty code-generation bug, among other things: go1.12.6 (released 2019/06/11) includes fixes to the compiler, the linker, the go command, and the crypto/x509, net/http, and os packages. See the Go 1.12.6 milestone on our issue tracker for details. go1.12.7 (released 2019/07/08) includes fixes to cgo, the compiler, and the linker. See the Go 1.12.7 milestone on our issue tracker for details.
2019-07-14Update go111 to 1.11.12.bsiegert1-2/+2
go1.11.11 (released 2019/06/11) includes a fix to the crypto/x509 package. See the Go 1.11.11 milestone on our issue tracker for details. go1.11.12 (released 2019/07/08) includes fixes to the compiler and the linker. See the Go 1.11.12 milestone on our issue tracker for details.
2019-05-27Update go112 to 1.12.5.bsiegert1-2/+2
This release includes fixes to the compiler, the linker, the go command, the runtime, and the os package. Same as for go111, remove the pkg/bootstrap tree from the package.
2019-05-27Update go111 to 1.11.10.bsiegert1-2/+2
This release includes fixes to the compiler, the linker, the go command, the runtime, and the os package. While here, remove pkg/bootstrap from the package, as it is only used for bootstrapping.
2019-05-15go: Introduce support for GO_DEPS.jperkin2-1/+133
This supports packages that require a large number of go-based dependencies, treating them as additional distfiles and built inline as part of the package build. The print-go-deps target is helpful to generate the list of GO_DEPS required for each package by parsing the Gopkg.lock file in the extracted sources. Thanks to rillig@ for various suggestions and comments.
2019-04-16Update go112 to 1.12.4.bsiegert1-2/+2
go1.12.2 (released 2019/04/05) includes fixes to the compiler, the go command, the runtime, and the doc, net, net/http/httputil, and os packages. See the Go 1.12.2 milestone on our issue tracker for details. go1.12.3 (released 2019/04/08) was accidentally released without its intended fix. It is identical to go1.12.2, except for its version number. The intended fix is in go1.12.4. go1.12.4 (released 2019/04/11) fixes an issue where using the prebuilt binary releases on older versions of GNU/Linux led to failures when linking programs that used cgo. Only Linux users who hit this issue need to update.
2019-04-16Update go111 to 1.11.9.bsiegert1-2/+2
go1.11.7 (released 2019/04/05) includes fixes to the runtime and the net packages. See the Go 1.11.7 milestone on our issue tracker for details. go1.11.8 (released 2019/04/08) was accidentally released without its intended fix. It is identical to go1.11.7, except for its version number. The intended fix is in go1.11.9. go1.11.9 (released 2019/04/11) fixes an issue where using the prebuilt binary releases on older versions of GNU/Linux led to failures when linking programs that used cgo. Only Linux users who hit this issue need to update.
2019-03-16Update go112 to 1.12.1.bsiegert1-2/+2
go1.12.1 (released 2019/03/14) includes fixes to cgo, the compiler, the go command, and the fmt, net/smtp, os, path/filepath, sync, and text/template packages. See the Go 1.12.1 milestone on our issue tracker for details.
2019-03-16Update go111 to 1.11.6.bsiegert1-2/+2
go1.11.6 (released 2019/03/14) includes fixes to cgo, the compiler, linker, runtime, go command, and the crypto/x509, encoding/json, net, and net/url packages. See the Go 1.11.6 milestone on our issue tracker for details.
2019-03-09go: switch default version to 1.12.bsiegert1-2/+2
This means all builds of packages written in Go use 1.12.
2019-03-09Add a package for Go 1.12.bsiegert1-1/+2
Some of the highlights include opt-in support for TLS 1.3, improved modules support (in preparation for being the default in Go 1.13), support for windows/arm, and improved macOS & iOS forwards compatibility. See https://blog.golang.org/go1.12. In pkgsrc, this is _not_ the default version for Go package builds just yet.
2019-01-24Update go110 to 1.10.8 (security).bsiegert1-2/+2
This release addresses a recently supported security issue. This DoS vulnerability in the crypto/elliptic implementations of the P-521 and P-384 elliptic curves may let an attacker craft inputs that consume excessive amounts of CPU. These inputs might be delivered via TLS handshakes, X.509 certificates, JWT tokens, ECDH shares or ECDSA signatures. In some cases, if an ECDH private key is reused more than once, the attack can also lead to key recovery. The issue is CVE-2019-6486 and Go issue golang.org/issue/29903. See the Go issue for more details.
2019-01-24Update go111 to 1.11.5 (security).bsiegert1-2/+2
This release addresses a recently supported security issue. This DoS vulnerability in the crypto/elliptic implementations of the P-521 and P-384 elliptic curves may let an attacker craft inputs that consume excessive amounts of CPU. These inputs might be delivered via TLS handshakes, X.509 certificates, JWT tokens, ECDH shares or ECDSA signatures. In some cases, if an ECDH private key is reused more than once, the attack can also lead to key recovery. The issue is CVE-2019-6486 and Go issue golang.org/issue/29903. See the Go issue for more details.
2018-12-20go: Actually bump to 1.11.4. Unbreaks build.jperkin1-2/+2
2018-12-15Update go110 to 1.10.7 (security fix).bsiegert1-2/+2
These releases include fixes to cgo, the compiler, linker, runtime, documentation, go command, and the net/http and go/types packages. They include a fix to a bug introduced in Go 1.11.3 and Go 1.10.6 that broke "go get" for import path patterns containing "...". View the release notes for more information: https://golang.org/doc/devel/release.html#go1.10.minor
2018-11-30mk/misc: make configuration for show-all targets more configurablerillig1-1/+13
Up to now, there was a central list of variable name patterns that defined whether a variable was printed as a sorted list, as a list or as a single value. Now each variable group decides on its own which of the variables are printed in which way, using the usual glob patterns. This is more flexible since different files sometimes differ in their naming conventions. Two variable groups are added: license (for everything related to LICENSE) and go (for lang/go).
2018-11-21lang: Re-enable lang/go as a meta package.jperkin2-0/+26
This allows users to simply install a "go" package and pull in the latest version available for their host operating system without having to figure out the name for the correct suffixed package.
2018-11-12*: Add CTF_SUPPORTED/CTF_FILES_SKIP where necessary.jperkin1-1/+2
2018-11-12go: Set STRIP_DEBUG_SUPPORTED=nojperkin1-2/+3
Stripping golang binaries renders them useless.
2018-11-04This file was missing from the previous commit.bsiegert1-2/+2
go111-1.11.2.
2018-11-04Update go110 to 1.10.5.bsiegert1-2/+2
go1.10.5 (released 2018/11/02) includes fixes to the go command, linker, runtime and the database/sql package. See the Go 1.10.5 milestone on our issue tracker for details.
2018-10-26go: Improve PRINT_PLIST_AWK patterns and avoid possible double definitionleot2-7/+6
- Move GO_PLATFORM definition in lang/go/version.mk in order that also lang/go* packages can (re)use it - Change PRINT_PLIST_AWK pattern that replace all ${GO_PLATFORM} and apply it only when ${GO_PLATFORM} is a directory (between two "/"). There are only 3 exceptions to that in lang/go14. Move it to version.mk so lang/go* PLIST can be mostly automatically generated. These changes should help to avoid (most) manual editing of lang/go*/PLIST. Discussed with and thanks to <bsiegert>!
2018-10-14Correct definition of GOTOOLDIR, remove PREFIX.bsiegert1-2/+2
GOTOOLDIR was not updated to use the versioned go directories.
2018-10-02Update go111 to 1.11.1.bsiegert1-2/+2
go1.11.1 (released 2018/10/01) includes fixes to the compiler, documentation, go command, runtime, and the crypto/x509, encoding/json, go/types, net, net/http, and reflect packages. See the Go 1.11.1 milestone on our issue tracker for details. Also correct the PLIST and use ln -sf instead of ln -s.
2018-09-23Remove lang/go.bsiegert14-8321/+0
Replacements: the versioned lang/go19, lang/go110 and lang/go111. Nothing in pkgsrc directly depends on this anymore. There are a few stragglers in wip, which will be fixed.
2018-09-22Move most of the version selection logic into version.mk.bsiegert2-21/+22
Provide a new variable, GO_PACKAGE_DEP, with the correct dependency on the user-selected Go version, to be used for fixing syncthing and friends.
2018-09-21Use lang/go111, not lang/go, for package builds.bsiegert1-2/+13
This moves builds of packages using Go off the unversioned lang/go package and onto Go 1.11 or Go 1.9 (on NetBSD 6) by default. There is a new, user-settable variable GO_VERSION_DEFAULT. NOTE: not all Go packages completely implement this yet. For example, net/syncthing does its own thing. This will be fixed.
2018-09-18Add a versioned Go 1.10 package as lang/go110.bsiegert1-2/+3
This uses a similar approach as go111. Its revision is one higher than the existing lang/go. Next steps: - make builds use this for dependent packages - delete lang/go to complete the move
2018-09-18Add Go 1.11 as lang/go111.bsiegert1-1/+2
This installs the go tool as go111; all the supporting files go under $PREFIX/go111, so it does not conflict with other Go versions. Go packages in pkgsrc do not use it to build yet. Changes: There are many changes and improvements to the toolchain, runtime, and libraries, but two features stand out as being especially exciting: modules and WebAssembly support. This release adds preliminary support for a new concept called "modules," an alternative to GOPATH with integrated support for versioning and package distribution. Module support is considered experimental, and there are still a few rough edges to smooth out, so please make liberal use of the issue tracker. Go 1.11 also adds an experimental port to WebAssembly (js/wasm). This allows programmers to compile Go programs to a binary format compatible with four major web browsers.
2018-09-15lang/go: Improve PRINT_PLIST_AWK for Go packagesminskim1-1/+3
Go packages create ${PREFIX}/bin and ${PREFIX}/gopkg even when they don't install anything in them. This change sets PRINT_PLIST_AWK to ignore such empty directories.
2018-09-14lang/go: Add SYS_IOCTL on SunOS. Bump PKGREVISION.fhajny3-2/+18
2018-08-29lang/go/go-package: Honor MAKE_ENV and set GOCACHE under WRKDIRleot1-3/+6
Previously GOCACHE was not passed as environment variable and hence during the build of packages the cache was stored in `${GO} env GOCACHE' (${XDG_CACHE_HOME} if defined or ${HOME}/.cache). Pass GOCACHE so that all cached file will ends up under ${WRKDIR}. While here also pass both GOPATH and GOCACHE via MAKE_ENV. Thanks to Antonio Huete Jimenez for spotting this problem! Discussed and ok by <bsiegert>, thanks!
2018-08-27Update Go to 1.10.4.bsiegert4-10/+28
go1.10.4 (released 2018/08/24) includes fixes to the go command, linker, and the net/http, mime/multipart, ld/macho, bytes, and strings packages. See the Go 1.10.4 milestone on our issue tracker for details. pkgsrc note: After the import of Go 1.11, this package will be renamed to lang/go110.
2018-08-22Recursive bump for perl5-5.28.0wiz1-2/+2
2018-07-08Update go19 to 1.9.7, latest on that branch.bsiegert1-2/+2
go1.9.5 (released 2018/03/28) includes fixes to the compiler, go command, and net/http/pprof package. See the Go 1.9.5 milestone on our issue tracker for details. go1.9.6 (released 2018/05/01) includes fixes to the compiler and go command. See the Go 1.9.6 milestone on our issue tracker for details. go1.9.7 (released 2018/06/05) includes fixes to the go command, and the crypto/x509, and strings packages. In particular, it adds minimal support to the go command for the vgo transition. See the Go 1.9.7 milestone on our issue tracker for details.
2018-07-08Forgot this in the last commit. Add GO19_VERSION.bsiegert1-1/+2
2018-07-08Move definition of $GO to version.mk.bsiegert2-7/+6
We have some packages, like mongodb-tools, that cannot include go-package.mk but need to call the go tool.
2018-07-08Use the non-symlinked go tool for package builds.bsiegert1-3/+8
Otherwise, you will not be able to build Go code in pkgsrc if you do not have pkg_alternatives installed. Introduce a variable (user-settable for now) GOVERSSUFFIX. $GO is now the Go tool with full path. leot@ convinced me to go full Python (e.g. one directory per major version, GO_VERSION_ACCEPTED etc.) but that will be another series of commits.
generated by cgit v1.2.3 (git 2.39.1) at 2025-03-03 00:12:58 +0000