jammy/linux-riscv-6.8: 6.8.0-38.38.1~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: fc13a3779d70ec13
  route-entry: 1
delta:
  promote-to-proposed: [main, meta]
  promote-to-security: []
  promote-to-updates: [main, meta]
flag:
  boot-testing-requested: true
  bugs-spammed: true
  proposed-announcement-sent: true
  proposed-testing-requested: true
  stream-from-cycle: true
issue: KSRU-12673
kernel-stable-master-bug: 2068316
packages:
  main: linux-riscv-6.8
  meta: linux-meta-riscv-6.8
phase: Complete
phase-changed: Thursday, 18. July 2024 22:33 UTC
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  main: 6.8.0-38.38.1~22.04.1
  meta: 6.8.0.38.38.1~22.04.1
~~:
  announce:
    swm-transition-crankable: 2024-07-11 07:43:06.088526
    swm-transition-peer-reviewable: 2024-07-11 11:42:40.954745
  clamps:
    new-review: fc13a3779d70ec13
    promote-to-proposed: fc13a3779d70ec13
    self: 6.8.0-38.38.1~22.04.1
    sru-review: fc13a3779d70ec13
  tracker:
    last-message: '2024-07-17 15:32:25.212707+00:00'

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

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

linux-buildinfo-6.8.0-38-generic 6.8.0-38.38.1~22.04.1 - is in main instead of universe
linux-headers-6.8.0-38-generic 6.8.0-38.38.1~22.04.1 - is in main instead of universe
linux-image-6.8.0-38-generic 6.8.0-38.38.1~22.04.1 - is in main instead of universe
linux-image-6.8.0-38-generic-dbgsym 6.8.0-38.38.1~22.04.1 - is in main instead of universe
linux-modules-6.8.0-38-generic 6.8.0-38.38.1~22.04.1 - is in main instead of universe
linux-tools-6.8.0-38-generic 6.8.0-38.38.1~22.04.1 - is in main instead of universe

Once this is fixed, set the promote-to-proposed to Fix Released again

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

All tasks have been completed and the bug is being closed