Go 1.10.8 and 1.11.5

[rvolosatovs]

Motivation for this change

Upstream update

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Assured whether relevant documentation is up to date
• Fits CONTRIBUTING.md.

---

[rvolosatovs]

@GrahamcOfBorg build go_1_10 go_1_11

[Mic92]

@GrahamcOfBorg eval

[Mic92]

@GrahamcOfBorg build go_1_10 go_1_11

[rvolosatovs]

@grahamc NixOS/ofborg#299 was merged 10 days ago, but it seems that still no automated builds get executed by @GrahamcOfBorg and neither can I manually trigger builds(as I tried in e.g. #54535 (comment)). Am I doing something wrong or is the configuration simply still not updated?

[rvolosatovs]

Any update? This is taking too long for what it is, especially considering that having outdated go versions in nixpkgs represent a security issue

[vcunat]

Well, just for the record, we already had the new versions in master and thus this merge made no difference on the files ;-) The relevant PR: #54658, I didn't notice this one until now.

[grahamc]

@rvolosatovs looks like the builds did work? https://github.com/NixOS/nixpkgs/pull/54535/checks

[rvolosatovs]

@grahamc yes, but they were triggered by #54535 (comment)
Not #54535 (comment) or #54535 (comment)