jammy/linux-lowlatency-hwe-5.19: 5.19.0-1017.18~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: 2f09ecda49db2136
  route-entry: 1
delta:
  promote-to-proposed: [main, meta, lrs, lrm, signed, lrg, generate]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-6265
kernel-stable-master-bug: 2003420
packages:
  generate: linux-generate-lowlatency-hwe-5.19
  lrg: linux-restricted-generate-lowlatency-hwe-5.19
  lrm: linux-restricted-modules-lowlatency-hwe-5.19
  lrs: linux-restricted-signatures-lowlatency-hwe-5.19
  main: linux-lowlatency-hwe-5.19
  meta: linux-meta-lowlatency-hwe-5.19
  signed: linux-signed-lowlatency-hwe-5.19
phase: Testing
phase-changed: Monday, 06. February 2023 12:01 UTC
reason:
  automated-testing: Ongoing -s testing in progress
  verification-testing: Ongoing -s testing in progress
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  lrm: 5.19.0-1017.18~22.04.1
  main: 5.19.0-1017.18~22.04.1
  meta: 5.19.0.1017.18~22.04.3
  signed: 5.19.0-1017.18~22.04.1
~~:
  clamps:
    new-review: 2f09ecda49db2136
    promote-to-proposed: 2f09ecda49db2136
    self: 5.19.0-1017.18~22.04.1
    sru-review: 2f09ecda49db2136

[Launchpad Janitor (janitor)]

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

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

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

linux-restricted-modules-lowlatency-hwe-5.19 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-390-5.19.0-1017-lowlatency 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-390-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-435-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-440-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-440-server-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-450-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-450-server-5.19.0-1017-lowlatency 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-450-server-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-455-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-460-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-460-server-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-465-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-470-5.19.0-1017-lowlatency 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-470-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-470-server-5.19.0-1017-lowlatency 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-470-server-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-495-lowlatency-64k-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-495-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-495-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-510-5.19.0-1017-lowlatency 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-510-5.19.0-1017-lowlatency 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-510-5.19.0-1017-lowlatency-64k 5.19.0-1017.18~22.04.1 - is in universe instead of multiverse
linux-modules-nvidia-510-lowlatency-64k-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-510-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-510-lowlatency-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of multiverse
linux-modules-nvidia-510-server-lowlatency-64k-hwe-22.04-edge 5.19.0-1017.18~22.04.1 - is in restricted instead of mult...

[Stefan Bader (smb)]

Checking the RT logs I see no issues.

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for linux-lowlatency-hwe-5.19 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.