eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kernel SRU Workflow |
Medium
|
Unassigned | |||
Automated-testing |
Medium
|
Canonical Kernel Team | |||
Prepare-package |
Medium
|
Seth Forshee | |||
Prepare-package-meta |
Medium
|
Seth Forshee | |||
Prepare-package-signed |
Medium
|
Seth Forshee | |||
Promote-to-proposed |
Medium
|
Canonical Kernel Team | |||
Promote-to-release |
Medium
|
Ubuntu Package Archive Administrators | |||
Regression-testing |
Medium
|
Canonical Kernel Team | |||
linux-gcp (Ubuntu) |
Medium
|
Unassigned | |||
Eoan |
Medium
|
Unassigned |
Bug Description
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:/
-- swm properties --
boot-testing-
kernel-
packages:
lrm: linux-restricte
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
phase: Complete
phase-changed: Sunday, 13. October 2019 03:26 UTC
proposed-
proposed-
variant: debs
CVE References
tags: | added: eoan kernel-release-tracking-bug |
Changed in linux-gcp (Ubuntu Eoan): | |
status: | New → Confirmed |
Changed in linux-gcp (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: kernel-release-tracking-bug-live |
description: | updated |
tags: | added: kernel-sru-cycle-d2019.10.08-1 |
description: | updated |
tags: | added: kernel-sru-derivative-of-1847298 |
Changed in kernel-sru-workflow: | |
status: | New → In Progress |
importance: | Undecided → Medium |
summary: |
- linux-gcp: <version to be filled> -proposed tracker + eoan/linux-gcp: <version to be filled> -proposed tracker |
description: | updated |
description: | updated |
summary: |
- eoan/linux-gcp: <version to be filled> -proposed tracker + eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: block-proposed-eoan |
tags: | added: block-proposed |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: regression-testing-passed |
tags: | removed: block-proposed-eoan |
tags: | removed: block-proposed |
description: | updated |
Launchpad Janitor (janitor) wrote : | #2 |
This bug was fixed in the package linux-gcp - 5.3.0-1004.4
---------------
linux-gcp (5.3.0-1004.4) eoan; urgency=medium
* eoan/linux-gcp: 5.3.0-1004.4 -proposed tracker (LP: #1847293)
* Use pyhon3-sphinx instead of python-sphinx for building html docs
(LP: #1845808)
- [Packaging] Update sphinx build dependencies to python3 packages
[ Ubuntu: 5.3.0-18.19 ]
* eoan/linux: 5.3.0-18.19 -proposed tracker (LP: #1847298)
* Enable the Dragonboards out of Eoan/master arm64 kernel (LP: #1846704)
- [Packaging] arm64: snapdragon: introduce a snapdragon flavour
- [Packaging] arm64: snapdragon: switch kernel format to Image
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA=y
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_QCOM_SMEM=y
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_QCOM_SMP2P=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMSM=y
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_QCOM_TSENS=y
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI=y
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
- [Config] arm64: snapdragon: CONFIG_
Changed in linux-gcp (Ubuntu Eoan): | |
status: | Confirmed → Fix Released |
description: | updated |
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 |
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1) | #4 |
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-
The following regressions have been reported in tests triggered by the package:
linux-gcp-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
[1] https:/
Thank you!
The following packages ended up in the wrong component in the Proposed pocket:
linux-restricte d-modules- gcp 5.3.0-1004.4 - is in universe instead of restricted nvidia- 390-5.3. 0-1004- gcp 5.3.0-1004.4 - is in universe instead of restricted nvidia- 430-5.3. 0-1004- gcp 5.3.0-1004.4 - is in universe instead of restricted
linux-modules-
linux-modules-
Once this is fixed, set the promote-to-proposed to Fix Released again