** Description changed:
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 --
boot-testi
** Description changed:
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 --
boot-testi
** Changed in: linux (Ubuntu Cosmic)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834499
Title:
[linux-azure] Block Layer Commits Requested in
** Description changed:
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 --
boot-testi
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Description changed:
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
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Description changed:
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
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Description changed:
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
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Description changed:
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
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Description changed:
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
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
** Description changed:
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
** Description changed:
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 --
boot-testi
Result of 'journalctl -b -1 -k'
Specifying boot ID has no effect, no persistent journal was found
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846271
Title:
Full video freeze kernel
** Description changed:
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 --
boot-testi
>IIUC linux-oem-osp1 has more DMIC support from intel-sof driver.
Not only does the oem-osp1 kernel not recognize the mic in this laptop,
it also doesn't recognize the speakers.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1845861
Title:
package grub-efi-amd64 2.02-2ubuntu8.13 failed to install/upgrade:
instal
Verification test completed successfully.
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
** Description changed:
Description
This task is to identify what new device IDs are required for CML.
CML PCH-LP: CML-U
CML PCH-V:
ControllerKernel Version Commit Approved to be
published Comments
SMBus 0x02a3 v5.1-rc35cd1c56c42be
I²C 0x0
Same problem with the kernel v. 4.15.0-55... it does not work properly,
whistling is always present.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1841485
Title:
Unbearable whistling in
** Description changed:
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 --
boot-testi
** Description changed:
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 --
boot-testi
** Description changed:
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 --
kernel-sta
Per attachment on previous comment, the issue seems to be fixed. I'll
flag it as verification-done.
Thanks!
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: Christian Brauner (cbrauner)
Status: In Progress
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed
** Description changed:
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 --
boot-testi
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
** Description changed:
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 --
boot-testi
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Description changed:
This bug will contain status and test results related to a kernel source
Public bug reported:
split from bug 1843774
Description
This task is to identify what new device IDs are required for CML PCH-H.
Controller Kernel Version Commit Approved to be published Comments
USB device/xDCI 0x02ee v5.2 7ae622c978db6b2
I²C (CMP-H) 0x06c5 0x06c6 0x60e8? 0x60e9? 0x06ea 0x06eb
quanxian: Any idea when the missing id's will be added?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1846335
Title:
[CML] New device id's for CMP-H
Status in intel:
New
Status in li
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
** Description changed:
Description
This task is to identify what new device IDs are required for CML.
CML PCH-LP: CML-U
CML PCH-V:
ControllerKernel Version Commit Approved to be
published Comments
SMBus 0x02a3 v5.1-rc35cd1c56c42be
I²C 0x0
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1846007
Title:
bionic/linux-azure: 5.0.0
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Tags removed: kernel-release-tracking-bug-live
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Ch
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
Your build works very well. The noise floor is even lower than before
the regression, and my audio quality is now the best I've heard it.
Thank you!
For clarity:
Medium noise: linux-image-4.15.0-58-generic 4.15.0-58.64
High noise (initial regression): linux-image-4.15.0-60-generic 4.15.0-60.67
Hi
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
** Description changed:
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 --
+ boot-testi
** Description changed:
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 --
boot-testi
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1846007
Title:
bionic/linux-azure: 5.0.0-1022.23
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
*** This bug is a duplicate of bug 1846204 ***
https://bugs.launchpad.net/bugs/1846204
** This bug has been marked a duplicate of bug 1846204
eoan/linux: 5.3.0-16.17 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844378
Title:
bionic/linux-aws-f
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
*** This bug is a duplicate of bug 1846204 ***
https://bugs.launchpad.net/bugs/1846204
** This bug is no longer a duplicate of bug 1845987
eoan/linux: 5.3.0-15.16 -proposed tracker
** This bug has been marked a duplicate of bug 1846204
eoan/linux: 5.3.0-16.17 -proposed tracker
--
You r
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Fix Committed => Incomplete
** Description changed:
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
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844378
Title:
bionic/linux-aws-f
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
all of the remaining ones are in eoan (5.3)
** Description changed:
Description
This task is to identify what new device IDs are required for CML.
CML PCH-LP: CML-U
- CML PCH-H: CML-S
- CML PCH-V:
+ CML PCH-V:
ControllerKernel Version Commit Approved to be
publishe
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844378
Title:
bionic/linux-aws-f
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
The following packages ended up in the wrong component in the -proposed
pocket:
linux-restricted-modules-aws-fips 4.15.0-2001.1 - is in main instead of
restricted
linux-modules-nvidia-390-4.15.0-2001-aws-fips 4.15.0-2001.1 - is in main
instead of restricted
linux-modules-nvidia-390-aws-fips 4.15
201 - 300 of 587 matches
Mail list logo
