[Bug 1977860] Re: Backport 1.18.3 to 20.04 and 22.04 LTS

[Didier Roche]

@Steve: this doesn’t change golang-defaults though, does it?

This is similar to the same process that happened in the past when snapd
or any other tool needed a new golang version: add a new source package,
don’t change the default for existing source that will still rebuild
with the exact same version.

So, basically, no impact on the 2000 packages in jammy which build-
depend on golang-defaults. Only new packages, that explicitely build-dep
on golang-1.18 will use it.

Do you mind considering a rereview?

@Yuan-Chen: this brings the version in line with the one we have in
jammy, for the ubuntu upgrade policy being respected.

** Changed in: golang-1.18 (Ubuntu Jammy)
       Status: Incomplete => Fix Committed

** Changed in: golang-1.18 (Ubuntu Jammy)
       Status: Fix Committed => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to golang-1.18 in Ubuntu.
https://bugs.launchpad.net/bugs/1977860

Title:
  Backport 1.18.3 to 20.04 and 22.04 LTS

Status in golang-1.18 package in Ubuntu:
  Fix Released
Status in golang-1.18 source package in Focal:
  Fix Committed
Status in golang-1.18 source package in Jammy:
  New

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.

  [Test Plan]

   1. Ensure Golang 1.16 is published in -proposed
   2. Start a build with a package, requiring Golang 1.18 (dependency + PATH set to Golang 1.18 go binary).
   3. Ensure the package builds successfully.
   4. Run go version <your binary> which should display: "go1.18.x" (x being the version uploaded).

  [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://launchpad.net/~didrocks/+archive/ubuntu/ppa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.18/+bug/1977860/+subscriptions