The following packages ended up in the wrong component in the Proposed pocket:
linux-restricted-modules-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-390-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-390-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-418-server-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-418-server-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-435-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-440-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-440-server-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-450-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-450-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-450-server-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-450-server-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-455-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-460-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-460-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-460-server-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-nvidia-460-server-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-objects-nvidia-390-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-objects-nvidia-418-server-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-objects-nvidia-450-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-objects-nvidia-450-server-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-objects-nvidia-460-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-objects-nvidia-460-server-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-restricted-signatures-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-signatures-nvidia-5.11.0-1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
Once this is fixed, set the promote-signing-to-proposed to Fix Released again
The following packages ended up in the wrong component in the Proposed pocket:
linux-restricte d-modules- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 390-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 390-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 418-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 418-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 435-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 440-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 440-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 455-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-server- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 390-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 418-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 450-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-5.11. 0-1003- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse nvidia- 460-server- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse d-signatures- gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse s-nvidia- 5.11.0- 1003-gcp 5.11.0-1003.3+1 - is in restricted instead of multiverse
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-modules-
linux-objects-
linux-objects-
linux-objects-
linux-objects-
linux-objects-
linux-objects-
linux-restricte
linux-signature
Once this is fixed, set the promote- signing- to-proposed to Fix Released again