[Group.of.nepali.translators] [Bug 1910067] Re: xenial/linux-hwe: 4.15.0-131.135~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => 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 see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1910068 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Holding before Promote to Proposed phase-changed: Monday, 11. January 2021 08:41 UTC reason: - :prepare-packages: Ongoing -- building in ppa main:building - prepare-package: Ongoing -- main package not yet fully built + :prepare-packages: Pending -- building in ppa meta:depwait + signed:retry-needed prepare-package-meta: Ongoing -- meta package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built trackers: xenial/linux-deeplens: bug 1910066 variant: debs versions: main: 4.15.0-131.135~16.04.1 meta: 4.15.0.131.129 signed: 4.15.0-131.135~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1910067 Title: xenial/linux-hwe: 4.15.0-131.135~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Committed Status in Kernel SRU Workflow prepare-package-signed series: Fix Committed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe source package in Xenial: New 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://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1910068 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Holding before Promote to Proposed phase-changed: Monday, 11. January 2021 08:41 UTC reason: :prepare-packages: Pending -- building in ppa meta:depwait signed:retry-needed prepare-package-meta: Ongoing -- meta package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built trackers: xenial/linux-deeplens: bug 1910066 variant: debs versions: main: 4.15.0-131.135~16.04.1 meta: 4.15.0.131.129 signed: 4.15.0-131.135~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1910067/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1732512] Re: xen hibernation support for linux-aws
This bug was fixed in the package linux-aws - 5.8.0-1018.20+21.04.1 --- linux-aws (5.8.0-1018.20+21.04.1) hirsute; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-1018.20 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Thadeu Lima de Souza Cascardo Thu, 07 Jan 2021 10:47:22 -0300 ** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1732512 Title: xen hibernation support for linux-aws Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Trusty: Fix Released Status in linux-aws source package in Xenial: Fix Released Status in linux-aws source package in Groovy: Fix Released Bug description: linux-aws needs multiple commits from mainline and Amazon Linux to support xen hibernation: UBUNTU: aws: [Config] disable SUSPEND UBUNTU: aws: [Config] disable XEN_FBDEV_FRONTEND, xen: move xen_setup_runstate_info and get_runstate_snapshot to (cherry picked from commit 4ccefbe597392d2914cf7ad904e33c734972681d) xen/time: use READ_ONCE (cherry picked from commit 2dd887e32175b624375570a0361083eb2cd64a07) xen: add steal_clock support on x86 (back-ported from commit ecb23dc6f2eff0ce64dd60351a81f376f13b12cc) xen: support runqueue steal time on xen (cherry picked from commit 6ba286ad845799b135e5af73d1fbc838fa79f709) x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op (cherry picked from commit ad5475f9faf5186b7f59de2c6481ee3e211f1ed7) xen: add static initialization of steal_clock op to xen_time_ops (cherry picked from commit d34c30cc1fa80f509500ff192ea6bc7d30671061) x86/xen: update cpuid.h from Xen-4.7 (cherry picked from commit de2f5537b397249e91cafcbed4de64a24818542e) x86/acpi: store ACPI ids from MADT for future usage (cherry picked from commit 3e9e57fad3d8530aa30787f861c710f598ddc4e7) xen: introduce xen_vcpu_id mapping (back-ported from commit 88e957d6e47f1232ad15b21e54a44f1147ea8c1b) xen: update xen headers (cherry picked from commit 7ba8dba95cb227eb6c270b1aa77f942e45f5e47c) xen: change the type of xen_vcpu_id to uint32_t (cherry picked from commit 55467dea2967259f21f4f854fc99d39cc5fea60e) xen/blkfront: separate per ring information out of device info (cherry picked from commit 81f351615772365d46ceeac3e50c9dd4e8f9dc89) xen/blkfront: pseudo support for multi hardware queues/rings (cherry picked from commit 3df0e5059908b8fdba351c4b5dd77caadd95a949) xen/blkfront: split per device io_lock (cherry picked from commit 11659569f7202d0cb6553e81f9b8aa04dfeb94ce) xen/blkfront: negotiate number of queues/rings to be used with (cherry picked from commit 28d949bcc28bbc2d206f9c3f69b892575e81c040) xen/blkfront: Cleanup of comments, fix unaligned variables, and (cherry picked from commit 6f03a7ff89485f0a7a559bf5c7631d2986c4ecfa) xen/blkfront: Remove duplicate setting of ->xbdev. (cherry picked from commit 75f070b3967b0c3bf0e1bc43411b06bab6c2c2cd) xen/blkfront: make persistent grants pool per-queue (cherry picked from commit 73716df7da4f60dd2d59a9302227d0394f1b8fcc) xen/blkfront: correct setting for xen_blkif_max_ring_order (cherry picked from commit 45fc82642e54018740a25444d1165901501b601b) xen/blkfront: realloc ring info in blkif_resume (cherry picked from commit 3db70a853202c252a8ebefa71ccb088ad149cdd2) blk-mq: dynamic h/w context count (back-ported from commit 868f2f0b72068a097508b6e8870a8950fd8eb7ef) xen-blkfront: save uncompleted reqs in blkfront_resume() (cherry picked from commit 7b427a59538a98161321aa46c13f4ea81b43f4eb) xen-blkfront: fix places not updated after introducing 64KB page (cherry picked from commit 6c647b0eb01cd7326dca093590f5e123e3c68b9c) blk-mq: mark request queue as mq asap (cherry picked from commit 66841672161efb9e3be4a1dbd9755020bb1d86b7) blk-mq: Fix NULL pointer updating nr_requests (cherry picked from commit e9137d4b93078b6a9965acfb18a2a2ad91cf8405) xen-blkfront: fix resume issues after a migration (cherry picked from commit 2a6f71ad99cabe436e70c3f5fcf58072cb3bc07f) xen-blkfront: introduce blkif_set_queue_limits() (back-ported from commit 172335ada40ce26806e514c83a504b45c14a4139) xen/pvhvm: run xen_vcpu_setup()
[Group.of.nepali.translators] [Bug 1899993] Re: EFI: Fails when BootCurrent entry does not exist
This bug was fixed in the package linux - 5.8.0-36.40+21.04.1 --- linux (5.8.0-36.40+21.04.1) hirsute; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kleber Sacilotto de Souza Thu, 07 Jan 2021 11:57:30 +0100 ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/183 Title: EFI: Fails when BootCurrent entry does not exist Status in curtin package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in curtin source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in curtin source package in Bionic: Invalid Status in linux source package in Bionic: Fix Released Status in curtin source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in curtin source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in curtin source package in Hirsute: Invalid Status in linux source package in Hirsute: Fix Released Bug description: [Impact] MAAS installs fail on systems that have EFI Variables that include a "/" in the name. Split out of bug 1894217. [Test Case] Using an OVMF-based VM, create a boot variable with a "/" character. For example: Shell> setvar FOO/BAR -guid 8ed72b3f-ad26-4d5c-aa36-38689635cac3 -rt -nv =foo Then, in Linux: $ ls /sys/firmware/efi/efivars/ ls: reading directory '/sys/firmware/efi/efivars/': Input/output error BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c MTC-eb704011-1402-11d3-8e77-00a0c969723b The Input/output error is the key symptom. See below to see how that percolates up to MAAS install failures. [Regression Risk] There's a very tiny chance that someone has written code that depends on an the -EIO error for some reason. It's hard to guess why such a script would do that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/183/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1902957] Re: Update kernel packaging to support forward porting kernels
This bug was fixed in the package linux - 5.8.0-36.40+21.04.1 --- linux (5.8.0-36.40+21.04.1) hirsute; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kleber Sacilotto de Souza Thu, 07 Jan 2021 11:57:30 +0100 ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1902957 Title: Update kernel packaging to support forward porting kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification Impact: Our kernel packaging currently has support for backporting kernels to older releases. This includes appending ~BACKPORT_SUFFIX to the version string for the backport kernel, where BACKPORT_SUFFIX is defined in update.conf. We need to start doing similar forward ported kernels, but BACKPORT_SUFFIX should be appended using a + rather than a ~. Our kernel packaging cannot easily determine whether a + or a ~ is appropriate. Fix: Move the leading character into BACKPORT_SUFFIX, and do not insert any leading characters from the kernel packaging scripts. Since the script which generates update.conf has access to information from kernel-series, it can more easily determine whether + or ~ is the appropriate leader. Test Case: Run through the normal steps for updating a backport kernel. The version string generated should have ~SERIES for a backport to an older series, and +SERIES for a backport to a newer series. Regression Potential: Backport kernels could end up with an incorrect version strings. Since all kernel uploads undergo review, any such errors should be caught before uploading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902957/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1903293] Re: Avoid double newline when running insertchanges
This bug was fixed in the package linux - 5.8.0-36.40+21.04.1 --- linux (5.8.0-36.40+21.04.1) hirsute; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kleber Sacilotto de Souza Thu, 07 Jan 2021 11:57:30 +0100 ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1903293 Title: Avoid double newline when running insertchanges Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] When preparing derivative kernels and inserting master kernel changes, if the derivative has not changes on its own, we end up with two empty lines, which is caught up by verify-release-ready. [Test case] Run cranky-close with derivative changes and no derivative changes. [Regression Potential] We could break changelogs, or the kernel preparation altogether. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903293/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1907262] Re: raid10: discard leads to corrupted file system
This bug was fixed in the package linux - 5.8.0-36.40+21.04.1 --- linux (5.8.0-36.40+21.04.1) hirsute; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions [ Ubuntu: 5.8.0-36.40 ] * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly [ Ubuntu: 5.8.0-35.39 ] * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-1052 // CVE-2021-1053 - [Packaging] NVIDIA -- Add the NVIDIA 460 driver -- Kleber Sacilotto de Souza Thu, 07 Jan 2021 11:57:30 +0100 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1910082] Re: xenial/linux-aws: 4.4.0-1120.134 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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-testing-requested: true kernel-stable-master-bug: 1910093 packages: main: linux-aws meta: linux-meta-aws - phase: Promote to Proposed - phase-changed: Monday, 11. January 2021 13:27 UTC + phase: Testing + phase-changed: Monday, 11. January 2021 14:58 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for - mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Fix Released trackers: xenial/linux-aws/aws-kernel: bug 1910081 variant: debs versions: main: 4.4.0-1120.134 meta: 4.4.0.1120.125 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1910082 Title: xenial/linux-aws: 4.4.0-1120.134 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws source package in Xenial: New 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://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1910093 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 11. January 2021 14:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Fix Released trackers: xenial/linux-aws/aws-kernel: bug 1910081 variant: debs versions: main: 4.4.0-1120.134 meta: 4.4.0.1120.125 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1910082/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1910084] Re: xenial/linux-cascade: 4.4.0-1029.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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-stable-master-bug: 1910093 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade - phase: Ready for Packaging - phase-changed: Wednesday, 06. January 2021 17:51 UTC + phase: Packaging + phase-changed: Monday, 11. January 2021 08:51 UTC reason: - :prepare-packages: Pending -b Debs ready to be cranked - prepare-package: Pending -- version not specified + :prepare-packages: 'Ongoing -b Being cranked by: shrirang-bagul' + prepare-package: Pending -- tag not published and package not + uploaded + prepare-package-meta: Pending -- tag not published and package not + uploaded + prepare-package-signed: Pending -- tag not published and package not + uploaded synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1910083 variant: debs -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1910084 Title: xenial/linux-cascade: 4.4.0-1029.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux source package in Xenial: New 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://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1910093 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Packaging phase-changed: Monday, 11. January 2021 08:51 UTC reason: :prepare-packages: 'Ongoing -b Being cranked by: shrirang-bagul' prepare-package: Pending -- tag not published and package not uploaded prepare-package-meta: Pending -- tag not published and package not uploaded prepare-package-signed: Pending -- tag not published and package not uploaded synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1910083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1910084/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
