impish/linux-raspi: <version to be filled> -proposed tracker
Bug #1936495 reported by
Kleber Sacilotto de Souza
This bug report is a duplicate of:
Bug #1941058: impish/linux-raspi: 5.13.0-1006.7 -proposed tracker.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Kernel SRU Workflow |
Fix Released
|
Medium
|
Unassigned | |||
Automated-testing |
New
|
Medium
|
Canonical Kernel Team | |||
Boot-testing |
New
|
Medium
|
Unassigned | |||
Prepare-package |
New
|
Medium
|
Canonical Kernel Team | |||
Prepare-package-meta |
New
|
Medium
|
Canonical Kernel Team | |||
Promote-to-proposed |
New
|
Medium
|
Canonical Kernel Team | |||
Promote-to-release |
New
|
Medium
|
Ubuntu Package Archive Administrators | |||
Regression-testing |
Invalid
|
Medium
|
Unassigned | |||
Sru-review |
New
|
Medium
|
Unassigned | |||
linux-raspi (Ubuntu) | ||||||
Impish |
Confirmed
|
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 --
kernel-
packages:
main: linux-raspi
meta: linux-meta-raspi
phase: Holding before Packaging
phase-changed: Friday, 16. July 2021 09:21 UTC
reason:
:prepare-
prepare-package: Holding -- waiting for master bug
variant: debs
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-2021.07.19-1 |
description: | updated |
tags: | added: kernel-sru-backport-of-1936496 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linux-raspi (Ubuntu Impish): | |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
tags: | removed: kernel-release-tracking-bug-live |
Changed in kernel-sru-workflow: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.