Backport 1.18.1 to 18.04, 20.04 and 22.04 LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
golang-1.18 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Lucas Kanashiro | ||
Focal |
Fix Released
|
Undecided
|
Lucas Kanashiro | ||
Jammy |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
[Rationale for update in 22.04]
As requested by sil2100, we don’t want upgrade from 20.04 LTS downgrading the Golang 1.18 version. Hence updating this package too to 1.18.3 which includes multile security fixes compared to 1.18.1:
- go1.18.2 (released 2022-05-10) includes security fixes to the syscall package, as well as bug fixes to the compiler, runtime, the go command, and the crypto/x509, go/types, net/http/httptest, reflect, and sync/atomic packages. See the Go 1.18.2 milestone on our issue tracker for details.
- go1.18.3 (released 2022-06-01) includes security fixes to the crypto/rand, crypto/tls, os/exec, and path/filepath packages, as well as bug fixes to the compiler, and the crypto/tls and text/template/parse packages. See the Go 1.18.3 milestone on our issue tracker for details.
[Rationale for new package in 20.04]
As part of our entreprise desktop offering, we need to backport a recent version of ADSys to 20.04 LTS.
This version depends on a recent Go version for embedding and more (golang 1.18), thus we need to backport Go 1.18 as a new separate binary package, as it’s already the case for current adsys and the backport of 1.16.
The latest docker.io version in Lunar requires Golang 1.18 to be backported to Focal.
[Rationale for new package in 18.04]
The latest docker.io version in Lunar requires Golang 1.18 to be backported to Bionic.
[Test Plan]
A smoke test, like this:
$ apt install golang-1.16-go
$ PATH=/usr/
$ go version
< check it's 1.16 >
$ cat > trivial.go
package main
func main() {}
$ go run trivial.go
$ cat > trivialcgo.go
package main
import "C"
func main() {}
$ go run trivialcgo.go
Then we should verify if docker.
[Where problems could occur]
* Package depending on this Go version would not be able to compile.
* As this is a separate, versionned, new package, no impact on existing ones.
* FYI, we already built ADSys against this Go version in our ppa: https:/
It's a new package so should not impact any existing behavior. I'm not at all proposing to update the default version of Go in a stable release. FWIW golang-1.18 is already co-installable with other golang versions in other releases.
Changed in golang-1.18 (Ubuntu): | |
status: | New → Fix Released |
summary: |
- Backport to 20.04 LTS + Backport 1.18.3 to 20.04 and 22.04 LTS |
description: | updated |
Changed in golang-1.18 (Ubuntu Bionic): | |
assignee: | nobody → Lucas Kanashiro (lucaskanashiro) |
description: | updated |
Changed in golang-1.18 (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in golang-1.18 (Ubuntu Focal): | |
status: | Fix Committed → In Progress |
Hello Didier, or anyone else affected,
Accepted golang-1.18 into focal-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ golang- 1.18/1. 18.3-1ubuntu1~ 20.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification- needed- focal to verification- done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- focal. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.