jammy/linux-lowlatency-hwe-6.2: 6.2.0-1008.8~22.04.1 -proposed tracker

[Stefan Bader]

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://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
built:
  from: d35453424f709ee1
  route-entry: 1
delta:
  promote-to-proposed: []
  promote-to-security: []
  promote-to-updates: [lrm, lrs, main, meta, signed]
flag:
  boot-testing-requested: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-8094
kernel-stable-master-bug: 2024537
packages:
  generate: linux-generate-lowlatency-hwe-6.2
  lrg: linux-restricted-generate-lowlatency-hwe-6.2
  lrm: linux-restricted-modules-lowlatency-hwe-6.2
  lrs: linux-restricted-signatures-lowlatency-hwe-6.2
  main: linux-lowlatency-hwe-6.2
  meta: linux-meta-lowlatency-hwe-6.2
  signed: linux-signed-lowlatency-hwe-6.2
phase: Complete
phase-changed: Wednesday, 12. July 2023 09:02 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  lrm: 6.2.0-1008.8~22.04.1+1
  main: 6.2.0-1008.8~22.04.1
  meta: 6.2.0.1008.8~22.04.5
  signed: 6.2.0-1008.8~22.04.1
~~:
  clamps:
    new-review: d35453424f709ee1
    promote-to-proposed: d35453424f709ee1
    self: 6.2.0-1008.8~22.04.1
    sru-review: d35453424f709ee1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

New kernel with signed kernels; signing-review required.

[Kleber Sacilotto de Souza (kleber-souza)]

Marking signing-sigoff as invalid as the verification has already been done for the previous version (6.2.0-1005.5~22.04.4 - bug 2024016) which is currently the version in -proposed.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

The following packages ended up in the wrong component in the Proposed pocket:

linux-restricted-modules-lowlatency-hwe-6.2 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-390-6.2.0-1008-lowlatency 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-390-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-435-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-440-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-440-server-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-450-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-450-server-6.2.0-1008-lowlatency 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-450-server-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-455-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-460-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-460-server-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-465-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-470-6.2.0-1008-lowlatency 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-470-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-470-server-6.2.0-1008-lowlatency 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-470-server-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-510-lowlatency-64k-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-510-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-510-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-510-server-lowlatency-64k-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-510-server-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-510-server-lowlatency-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead of multiverse
linux-modules-nvidia-515-6.2.0-1008-lowlatency 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-515-6.2.0-1008-lowlatency 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-515-6.2.0-1008-lowlatency-64k 6.2.0-1008.8~22.04.1+1 - is in universe instead of multiverse
linux-modules-nvidia-515-lowlatency-64k-hwe-22.04-edge 6.2.0-1008.8~22.04.1+1 - is in restricted instead o...

[Stefan Bader (smb)]

With pending proposed ADT looks good.

[Stefan Bader (smb)]

Glancing over the RT results I see no signs of regression.

[Stefan Bader (smb)]

The jammy:linux-lowlatency-hwe-6.2 kernel does not contain any additional patches compared to lunar:linux. But since it is one of the first builds does contain multiple iterations of uploads in the changelog. Those cause incorrect verification requests.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being closed