jammy/linux-intel-iotg: 5.15.0-1012.16 -proposed tracker
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:
from: 7bba80cd497ecd19
route-entry: 1
delta:
promote-
flag:
boot-
issue: KSRU-4373
kernel-
packages:
lrg: linux-restricte
lrm: linux-restricte
lrs: linux-restricte
main: linux-intel-iotg
meta: linux-meta-
signed: linux-signed-
phase: Holding before Promote to Proposed
phase-changed: Wednesday, 27. July 2022 21:16 UTC
reason:
sru-review: Stalled -- review FAILED
trackers:
focal/
variant: debs
versions:
lrm: 5.15.0-1012.16
main: 5.15.0-1012.16
meta: 5.15.0.1012.12
signed: 5.15.0-1012.16
~~:
clamps:
new-review: 7bba80cd497ecd19
self: 5.15.0-1012.16
sru-review: 7bba80cd497ecd19
CVE References
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-2022.07.11-1 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1981243 |
Changed in kernel-sru-workflow: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in linux-intel-iotg (Ubuntu Jammy): | |
importance: | Undecided → Medium |
Changed in kernel-sru-workflow: | |
status: | Confirmed → Triaged |
description: | updated |
Changed in kernel-sru-workflow: | |
status: | Triaged → In Progress |
tags: | added: kernel-jira-issue-ksru-4373 |
description: | updated |
description: | updated |
summary: |
- jammy/linux-intel-iotg: <version to be filled> -proposed tracker + jammy/linux-intel-iotg: 5.15.0-1012.16 -proposed tracker |
description: | updated |
tags: | added: kernel-jira-in-review |
description: | updated |
tags: | removed: kernel-jira-in-review |
description: | updated |
tags: | added: kernel-jira-in-review |
description: | updated |
tags: | removed: kernel-jira-in-review |
description: | updated |
tags: | added: kernel-jira-in-review |
description: | updated |
tags: | removed: kernel-jira-in-review |
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: | removed: kernel-release-tracking-bug-live |
Changed in kernel-sru-workflow: | |
status: | In Progress → Invalid |
Changed in linux-intel-iotg (Ubuntu Jammy): | |
status: | New → Invalid |
This kernel was not rebased against the parents kernel latest tag but against master-next. How it that possible using cranky rebase? Also maybe before cranking again, check whether this would want to be done against the -45 ABI version.