wiki: recommended Ubuntu port still does not have security fix release

[kevinburke1]

Per https://github.com/golang/go/wiki/Ubuntu, the recommended Ubuntu 18.04 apt source is longsleep/golang-backports.

As of 5pm Pacific on October 22, that port does not have the Go 1.13.2 or Go 1.13.3 releases.

I'm not sure if this is the right place - if someone on the Go team maintains that package - but it seems bad that a recommended resource is not up to date several days after a security release.

It would be nice to maybe see instructions about what goes into the .deb file so we can reproduce it/upload on our own.

[bradfitz]

I have no clue what that is.

It's a wiki. @RPiAwesomeness added it:

commit 66ed20dd74f17802aa49e84a32a574f173fac314
Author: RPiAwesomeness <[email protected]>
Date:   Sun Mar 26 09:58:13 2017 -0400

    Added information regarding Ubuntu 16.04

diff --git a/Ubuntu.md b/Ubuntu.md
index f5e7313e..336d90d9 100644
--- a/Ubuntu.md
+++ b/Ubuntu.md
@@ -14,5 +14,11 @@ Or use Go's official (non-Deb) downloads:
 
 https://golang.org/dl/
 
+If you're using Ubuntu 16.04 LTS and are unable to install `golang-1.8-go`, then you can also use the `longsleep/golang-backports` PPA:
 
+```
+sudo add-apt-repository ppa:longsleep/golang-backports
+sudo apt-get update
+sudo apt-get install golang-go
+```
 

If you think it's not helpful, remove it. It's a wiki.

The Go team doesn't (and can't) vouch for everything on the wiki.

[kevinburke1]

Oh man, okay. Not much on that page that would make you think it's not an official page - the last update is from Ian Lance Taylor, it's a same place a lot of the go modules stuff is documented, etc.

[kevinburke1]

If anyone is reading this and has suggestions about a more appropriate repository to link to, please let me know and I can update the docs appropriately.

[bradfitz]

The wiki was always an experiment. It was pretty controversial when we started it, and we're still not entirely happy with it. The problem is some good docs are there and then can't migrate to more official (+slightly locked down / peer reviewed) places.

I have some thoughts on what a replacement system should look like (similar low-friction editing/previewing, all changes go through Gerrit, but review is optional for most well-known contributors, bot can +2 non-sensitive pages, must work with GitHub PRs quickly and easily, so people can edit docs from the website... probably need a new "wiki" repo. Go's existing github wiki would be replaced with links to golang.org/wiki/Topic for each page. Then we'd just serve the /wiki/ content directly from golang.org/wiki/Topic probably.)

[dmitshur]

See also #34038 for discussion and proposal for improving the wiki situation.

[ghost]

what is longsleep's approach to a monitoring of new

Golang releases, esp. as pertains to security fixes

a query via Launchpad might return a response

https://launchpad.net/~longsleep

[ghost]

FWIW, running in console mode a recent package generation (different distro) of 1.13.3 took about 1 hour and 42 minutes on the below.

$ uname -mp
i686 Intel(R) Atom(TM) CPU N270   @ 1.60GHz
$ free --giga | perl -lae 'print @F[0,1] if $. == 2'
Mem:1
$ gcc --version | head -n 1
gcc (GCC) 5.5.0
$

[leighmcculloch]

It looks like 1.13.3 has been published now:
https://launchpad.net/~longsleep/+archive/ubuntu/golang-backports

[ghost]

History / Ubuntu

There was a commit by S. Eisenmann on Sept. 4.
Update for Go 1.13

I'd recommend this issue be closed.

[longsleep]

My ppa is updated as soon as I find the time to actually do it. This also means it's not perfectly synced with a new Go release but I always try to get it updated within a few days. This will continue for the foreseeable future.

[longsleep]

For reference the golang Ubuntu packaging for the longsleep ppa is at https://github.com/longsleep/golang-deb - so everyone and the Debian packaging used as base is at https://salsa.debian.org/go-team/compiler/golang - all is open source so if someone actually needs it faster as I can update the ppa it's always possible to build your own.

[dmitshur]

Thanks. I'll close this because the original issue is resolved by now (and so the title has become misleading) and there's nothing left to do here. Moving mature wiki content behind gerrit is already tracked in other issues like #34038.