Commit graph

258 commits

Author SHA1 Message Date
John Ericson
4ccb74011f Merge commit '18aa59b0f26fc707e7313f8467e67159e61600c2' from master into staging
There was one conflict in the NixOS manual; I checked that it still
built after resolving it.
2019-04-01 00:40:03 -04:00
John Ericson
655a29ff9c ghc, go, guile: Use new pkgs*
`pkgsBuildTarget` allows us to avoid repeated and confusing conditions.
The others merely provide clarity for one the foreign package set's
target platform matters.
2019-03-24 22:12:15 -04:00
Wael M. Nasreddine
276d8c97bb
go_1_12: 1.12 -> 1.12.1 2019-03-21 22:33:43 -07:00
Wael M. Nasreddine
2d9d054bce
go_1_11: 1.11.5 -> 1.11.6 2019-03-21 22:33:42 -07:00
Wael Nasreddine
37d2f71e2f
go_1_12: set meta.branch to 1.12 (#56852) 2019-03-04 23:18:12 -08:00
Wael M. Nasreddine
252376c617
go_1_12: switch to fetchurl for sha256 consistency on Darwin
fetchFromGitHub and thus fetchzip hashes the contents of the archive and
not the archive itself. Unicode file names lead to different checksums
on HFS+ vs. other file systems because of Unicode normalisation
2019-03-03 16:32:04 -08:00
Wael M. Nasreddine
6ef04cabd4
go_1_12: init at go 1.12 2019-03-02 14:24:17 -08:00
Jörg Thalheim
dadc7eb329
treewide: use runtimeShell instead of stdenv.shell whenever possible
Whenever we create scripts that are installed to $out, we must use runtimeShell
in order to get the shell that can be executed on the machine we create the
package for. This is relevant for cross-compiling. The only use case for
stdenv.shell are scripts that are executed as part of the build system.
Usages in checkPhase are borderline however to decrease the likelyhood
of people copying the wrong examples, I decided to use runtimeShell as well.
2019-02-26 14:10:49 +00:00
Vladimír Čunát
4851a04deb
go_1_10: fix tests after binutils update 2019-02-19 11:35:54 +01:00
adisbladis
affee8aa47
go_1_9: Drop go 1.9
Unsupported by upstream
2019-02-01 06:19:14 +00:00
Vladimír Čunát
a687ef9739
go_1_9: mark as insecure (see the parent commit)
Upstream only supports two latest releases.
https://github.com/golang/go/issues/29903#issuecomment-457307356
2019-01-27 11:33:57 +01:00
Vladimír Čunát
d32e779ae8
go_1_10: 1.10.7 -> 1.10.8 (security)
https://groups.google.com/forum/#!topic/golang-announce/mVeX35iXuSw
https://github.com/NixOS/nixpkgs/pull/54658
2019-01-27 11:29:13 +01:00
allowthere
d803da845f
go: 1.11.4 -> 1.11.5
https://groups.google.com/forum/#!msg/golang-announce/mVeX35iXuSw/Flp8FX7QEAAJ

We have just released Go 1.11.5 and Go 1.10.8 to address a recently reported security issue. We recommend that all users update to one of these releases (if you’re not sure which, choose Go 1.11.5).

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-27 02:59:44 +00:00
Jörg Thalheim
b5c1deca8a
treewide: remove wkennington as maintainer
He prefers to contribute to his own nixpkgs fork triton.
Since he is still marked as maintainer in many packages
this leaves the wrong impression he still maintains those.
2019-01-26 10:05:32 +00:00
rnhmjoj
ba7266c629
go: patch missing mimetype database 2019-01-20 00:58:57 +01:00
Benjamin Herr
ce2d980be8 go: 1.11.2 -> 1.11.4 2018-12-15 06:54:12 -08:00
Benjamin Herr
3cb3a24ce9 go_1_10: 1.10.3 -> 1.10.7 2018-12-15 06:53:50 -08:00
Jörg Thalheim
7b63cdcc07
go_1_11: remove build artifacts 2018-11-26 07:22:50 +00:00
Jörg Thalheim
79b9462468
go_1_11: fix cross compilation 2018-11-24 10:36:57 +00:00
Frederik Rietdijk
2219e2578e Merge staging-next into staging 2018-11-22 10:10:40 +01:00
Frederik Rietdijk
c31cb577ae Merge master into staging-next 2018-11-22 09:57:08 +01:00
Jörg Thalheim
416d8928b2 go_1_11: split into install/check phase
For cross compilation we want to skip installCheckPhase.
2018-11-22 04:17:43 +01:00
Jörg Thalheim
60c6dc3f5e go_1_11: remove unused postConfigure
Since it was overriding configurePhase postConfigure has not be used in a while.
2018-11-22 04:17:43 +01:00
Jörg Thalheim
ebe6575b43
go_1_10: update outdated meta.branch 2018-11-21 17:55:21 +00:00
Jörg Thalheim
a4f37346e7
go_1_11: update outdated meta.branch 2018-11-21 17:53:28 +00:00
Frederik Rietdijk
3b052406ea Merge staging-next into staging 2018-11-12 19:01:36 +01:00
ryan4729
b46f5e1277 go: organize GOARCH and GOOS 2018-11-11 14:37:12 -08:00
ryan4729
5302222337 go: make compiler usable for cross compiles 2018-11-10 22:41:46 -08:00
Jaka Hudoklin
734bd4ca54
go_1_11: 1.11 -> 1.11.2f
fixes #50180
2018-11-10 21:59:58 +00:00
Yegor Timoshenko
f969e6e474
go: do not wrap with go get tools
See: https://github.com/NixOS/nixpkgs/issues/46603

These tools are not required for `buildGoPackage`, while
significantly affecting closure size and build time.

This essentially reverts 458895db33.
2018-10-12 19:36:34 +00:00
Colin Rice
cdeb26ee76 go: Remove pkg/obj directory from the build outputs.
This appears to be causing the go package to be roughly 900MB in size.
2018-09-24 03:37:43 +00:00
Jörg Thalheim
51a6c88394 go_1_11: add url to flaky test 2018-09-16 11:08:53 +01:00
Bob van der Linden
0bf6b440d9
go: skip flaky os/exec TestExtraFiles
This seems to only happen on i686 on go 1.11. It also happens on
Debian. For more information:

https://github.com/golang/go/issues/25628
2018-09-15 18:46:18 +02:00
Sarah Brofeldt
17b6efaf3d go_1_11: Only allow one of GOARM=5, 6 or 7 2018-09-04 11:46:35 +02:00
John Ericson
2c2f1e37d4 reewide: Purge all uses stdenv.system and top-level system
It is deprecated and will be removed after 18.09.
2018-08-30 17:20:32 -04:00
adisbladis
90d3ed0096
go_1_11: init at 1.11 2018-08-26 23:11:10 +08:00
Jörg Thalheim
218298b30f
Merge branch 'master' into unused5 2018-07-21 15:41:22 +01:00
volth
52f53c69ce pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
volth
6d2857a311 [bot] treewide: remove unused 'inherit' in let blocks 2018-07-20 19:38:19 +00:00
Jörg Thalheim
b0f2233917 go_1_10: remove cache artifacts from package
fixes #42465
2018-07-13 20:02:36 -04:00
R. RyanTM
fce5759f24 go: 1.10.2 -> 1.10.3
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/go/versions.

These checks were done:

- built on NixOS
- Warning: no invocation of /nix/store/sz746n0jm0n8dnv47d7cqvwny8ncfbi4-go-1.10.3/bin/gofmt had a zero exit code or showed the expected version
- /nix/store/sz746n0jm0n8dnv47d7cqvwny8ncfbi4-go-1.10.3/bin/.go-wrapped passed the binary check.
- /nix/store/sz746n0jm0n8dnv47d7cqvwny8ncfbi4-go-1.10.3/bin/go passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 0 of 3 passed binary check by having the new version present in output.
- found 1.10.3 with grep in /nix/store/sz746n0jm0n8dnv47d7cqvwny8ncfbi4-go-1.10.3
- directory tree listing: https://gist.github.com/499abd38cfb9318ba6bbcd885951c6b8
- du listing: https://gist.github.com/04fbe15eac23c814fa6b313c8e543e4c
2018-06-14 07:59:05 -07:00
Matthew Bauer
6748534d83 Merge remote-tracking branch 'upstream/master' into staging 2018-05-08 09:36:00 -05:00
xeji
a958d80051
Merge pull request #38309 from volth/fix37704
go_1_{9,10}: disable problematic tests in net module
2018-05-03 22:39:05 +02:00
R. RyanTM
59c22bf3a1 go: 1.10.1 -> 1.10.2
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.

This update was made based on information from https://repology.org/metapackage/go/versions.

These checks were done:

- built on NixOS
- ran ‘/nix/store/w2wgdl5ljbx1fq6iwlavrl4nzbchq954-go-1.10.2/bin/.go-wrapped help’ got 0 exit code
- ran ‘/nix/store/w2wgdl5ljbx1fq6iwlavrl4nzbchq954-go-1.10.2/bin/go help’ got 0 exit code
- found 1.10.2 with grep in /nix/store/w2wgdl5ljbx1fq6iwlavrl4nzbchq954-go-1.10.2
- directory tree listing: https://gist.github.com/249bfa4dc4d10281576f20de902e501a
2018-05-02 16:04:31 -07:00
John Ericson
ba52ae5048 treewide: isArm -> isAarch32
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.

The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:

```
ISA:             ARMv8   {-A, -R, -M}
                 /    \
Mode:     Aarch32     Aarch64
             |         /   \
Encoding:   A64      A32   T32
```

At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.

The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.

[1]: https://developer.arm.com/products/architecture/a-profile
2018-04-25 15:28:55 -04:00
volth
9e11e4ba64 go_1_{9,10}: disable TestVariousDeadlines test 2018-04-01 20:39:12 +00:00
volth
8a77a0ae0e go_1_{9,10}: disable TestWritevError test 2018-04-01 20:32:33 +00:00
Will Dietz
266cd103f1
Merge pull request #38076 from dtzWill/update/go-1.10.1
go: 1.10 -> 1.10.1
2018-03-29 18:06:24 -05:00
Will Dietz
1661c0b2c6 go: 1.10 -> 1.10.1 2018-03-29 17:17:12 -05:00
Will Dietz
166a632124 go: 1.9.4 -> 1.9.5 2018-03-29 17:15:57 -05:00