hirsute/linux-gcp: 5.11.0-1003.3 -proposed tracker
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | |||
Automated-testing |
Invalid
|
Medium
|
Canonical Kernel Team | |||
Prepare-package |
Invalid
|
Medium
|
Andrea Righi | |||
Prepare-package-lrg |
Fix Released
|
Medium
|
Seth Forshee | |||
Prepare-package-lrm |
Fix Released
|
Medium
|
Seth Forshee | |||
Prepare-package-lrs |
Fix Released
|
Medium
|
Seth Forshee | |||
Prepare-package-meta |
Invalid
|
Medium
|
Andrea Righi | |||
Prepare-package-signed |
Invalid
|
Medium
|
Andrea Righi | |||
Promote-signing-to-proposed |
Fix Released
|
Medium
|
Andy Whitcroft | |||
Promote-to-proposed |
Fix Released
|
Medium
|
Andy Whitcroft | |||
Promote-to-release |
Fix Released
|
Medium
|
Ubuntu Package Archive Administrators | |||
Regression-testing |
Fix Released
|
Medium
|
Canonical Kernel Team | |||
linux-gcp (Ubuntu) | ||||||
Hirsute |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
This bug will contain status and test results related to a kernel source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https:/
-- swm properties --
boot-testing-
built:
lrg: build#2
lrm: build#2
lrs: build#2
kernel-
packages:
lrg: linux-restricte
lrm: linux-restricte
lrs: linux-restricte
phase: Complete
phase-changed: Thursday, 01. April 2021 23:23 UTC
promote:
- lrm
- lrs
proposed-
proposed-
reason: {}
synthetic:
:promote-
variant: debs
versions:
lrm: 5.11.0-1003.3+1
source: 5.11.0-1003.3
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-d2021.03.08-2 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1922087 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linux-gcp (Ubuntu Hirsute): | |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → In Progress |
description: | updated |
description: | updated |
description: | updated |
summary: |
- hirsute/linux-gcp: <version to be filled> -proposed tracker + hirsute/linux-gcp: 5.11.0-1003.3 -proposed tracker |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: regression-testing-passed |
description: | updated |
description: | updated |
description: | updated |
The following packages ended up in the wrong component in the Proposed pocket:
linux-restricte d-modules- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 390-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 390-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 418-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 418-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 435-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 440-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 440-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 455-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 390-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 418-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse d-signatures- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse s-nvidia- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-objects-
linux-objects-
linux-objects-
linux-objects-
linux-objects-
linux-objects-
linux-restricte
linux-signature
Once this is fixed, set the promote- signing- to-proposed to Fix Released again