[Group.of.nepali.translators] [Bug 1915370] Re: xenial/linux-azure: 4.15.0-1108.120~16.04.1 -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/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 built: main: build#1 meta: build#1 signed: build#1 kernel-stable-master-bug: 1915371 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Thursday, 11. February 2021 11:56 UTC + phase: Testing + phase-changed: Monday, 15. February 2021 16:17 UTC promote: - main - meta - signed + proposed-announcement-sent: true + proposed-testing-requested: true reason: - :promote-to-as-proposed: Ongoing -- packages not yet published - promote-to-proposed: Ongoing -- waiting for packages to publish to - as-proposed + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress synthetic: - :promote-to-as-proposed: Fix Committed + :promote-to-as-proposed: Fix Released trackers: xenial/linux-azure/azure-kernel: bug 1915369 variant: debs versions: main: 4.15.0-1108.120~16.04.1 meta: 4.15.0.1108.99 signed: 4.15.0-1108.120~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/1915370 Title: xenial/linux-azure: 4.15.0-1108.120~16.04.1 -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 prepare-package-signed 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: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure source package in Xenial: Confirmed 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 built: main: build#1 meta: build#1 signed: build#1 kernel-stable-master-bug: 1915371 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 15. February 2021 16:17 UTC promote: - main - meta - signed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Fix Released trackers: xenial/linux-azure/azure-kernel: bug 1915369 variant: debs versions: main: 4.15.0-1108.120~16.04.1 meta: 4.15.0.1108.99 signed: 4.15.0-1108.120~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1915370/+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 1915722] [NEW] rustc 1.50 and cargo 0.51 will be required by a future version of firefox
Public bug reported: This is not yet a hard requirement, but builders in the Mozilla infrastructure have already been upgraded to rustc 1.50¹, so we should start preparing this update for hirsute and all supported releases (xenial, bionic, focal, and groovy). This will also benefit other projects that are packaged in Ubuntu and are bumping their build dependency on rustc, see e.g. https://gitlab.gnome.org/GNOME/librsvg/-/commit/513a575a839342f46bca713ac4eac37fbab9a7b7. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1692352 ** Affects: cargo (Ubuntu) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: rustc (Ubuntu) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: cargo (Ubuntu Xenial) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: rustc (Ubuntu Xenial) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: cargo (Ubuntu Bionic) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: rustc (Ubuntu Bionic) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: cargo (Ubuntu Focal) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: rustc (Ubuntu Focal) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: cargo (Ubuntu Groovy) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: rustc (Ubuntu Groovy) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Also affects: cargo (Ubuntu) Importance: Undecided Status: New ** Changed in: cargo (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Also affects: cargo (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cargo (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cargo (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: cargo (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: rustc (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: cargo (Ubuntu Xenial) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: cargo (Ubuntu Bionic) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: cargo (Ubuntu Focal) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: cargo (Ubuntu Groovy) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: rustc (Ubuntu Xenial) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: rustc (Ubuntu Bionic) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: rustc (Ubuntu Focal) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: rustc (Ubuntu Groovy) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- 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/1915722 Title: rustc 1.50 and cargo 0.51 will be required by a future version of firefox Status in cargo package in Ubuntu: New Status in rustc package in Ubuntu: New Status in cargo source package in Xenial: New Status in rustc source package in Xenial: New Status in cargo source package in Bionic: New Status in rustc source package in Bionic: New Status in cargo source package in Focal: New Status in rustc source package in Focal: New Status in cargo source package in Groovy: New Status in rustc source package in Groovy: New Bug description: This is not yet a hard requirement, but builders in the Mozilla infrastructure have already been upgraded to rustc 1.50¹, so we should start preparing this update for hirsute and all supported releases (xenial, bionic, focal, and groovy). This will also benefit other projects that are packaged in Ubuntu and are bumping their build dependency on rustc, see e.g. https
[Group.of.nepali.translators] [Bug 1902260] Re: systemd-detect-virt is missing on Groovy EC2 AMI
This bug was fixed in the package livecd-rootfs - 2.525.51 --- livecd-rootfs (2.525.51) bionic; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.525.50) bionic; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:59:37 + ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1902260 Title: systemd-detect-virt is missing on Groovy EC2 AMI Status in cloud-images: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * On some image types, systemd-detect-virt might be missing [Test Case] * $ sudo systemd-detect-virt Should print a word. If it prints "no such file or directory" it is buggy. Best reproduced on initrdless boot, public cloud, where kernel flavour is switched, such as GCP groovy or AWS EC2 groovy. However other image types might be affected too. Backporting the change to all series, in case there are other places which invoke undivert_grub multiple times in a row. [Where problems could occur] * Hopefully, systemd-detect-virt undivert is now correct. Issues might happen in case systemd is not meant to be installed and yet the file remains on disk; or if the diversion is not removed still. Resulting in incorrect runtime behaviour. * For the images where this is fixed, systemd-detect-virt will now start working correctly. Thus may trigger automation to run that relied on missing systemd-detect-virt and thus previously did not execute. [Other Info] * Original bug report ubuntu/images/hvm-ssd/ubuntu-groovy-20.10-arm64-server-20201022.1 ubuntu@ip-172-31-30-199:~$ dpkg -S systemd-detect-virt systemd: /usr/bin/systemd-detect-virt systemd: /usr/share/bash-completion/completions/systemd-detect-virt systemd: /usr/share/man/man1/systemd-detect-virt.1.gz ubuntu@ip-172-31-30-199:~$ ls /usr/bin/systemd-detect-virt ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory Since livecd-rootfs plays with diversions of this file it looks suspicious, but I have not fully triaged the problem. LXD image for amd64 seems to be ok: ubuntu 20.10 amd64 (release) (20201022.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902260/+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 1910557] Re: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
This bug was fixed in the package livecd-rootfs - 2.525.51 --- livecd-rootfs (2.525.51) bionic; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.525.50) bionic; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:59:37 + ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in livecd-rootfs source package in Hirsute: Fix Released Bug description: livecd-rootfs v2.700 in hirsute introduced a fix to produce unpacked artifacts for use by multipass on macOS hosts. These hosts require direct access to a kernel and initrd to boot the buildd images. See: https://git.launchpad.net/livecd- rootfs/commit/?id=065c82314464fa78337d5122e1d4826a7d6edbb0 This change needs to be backported to all suites. [Impact] * Without this change, users are unable to use the buildd images with multipass on macOS hosts. Snapcraft utilizes multipass to build snaps, so this blocks macOS users from building snaps. As a workaround, the CPC team is manually extracting these artifacts and publishing them to cloud-images.ubuntu.com. This is not ideal for the long-term, and could result in breakage in the event that the CPC team forgets to manually publish these artifacts. [Test Case] * After this change lands, a user should be able to build images with the ubuntu-base project and buildd subproject, and the resulting build should produce extracted kernel and initrd artifacts. [Where problems could occur] * These changes are minor, but a mistake could result in broken buildd image hooks (where the build fails) or broken buildd image artifacts (where the images don't work as expected). * Since all buildd images are manually tested by the launchpad team, multipass team, and snapcraft team before they enter production, the risk of introducing breakage for end users is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+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 1912835] Re: ESP should be fscked
This bug was fixed in the package livecd-rootfs - 2.525.51 --- livecd-rootfs (2.525.51) bionic; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.525.50) bionic; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:59:37 + ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1912835 Title: ESP should be fscked Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * ESP can be not clean, thus failing to mount on boot. * fsck should be enabled for ESP partition. [Test Case] * $ systemctl status systemd-fsck*.service On boot, that should produce status for two drives, the one with short uuid should be the one mounted as /ESP [Where problems could occur] * The change will affect only newly deployed instances. Old instances will have to correct this in fstab themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912835/+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 1912830] Re: Use non-removable uefi bootloader in cloud-images by default
This bug was fixed in the package livecd-rootfs - 2.525.51 --- livecd-rootfs (2.525.51) bionic; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.525.50) bionic; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:59:37 + ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1912830 Title: Use non-removable uefi bootloader in cloud-images by default Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Won't Fix Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * use non --removable uefi installation for cloud-images * Currently cloud-images use --removable grub installation, which makes the disk images look at lot more like our installer .isos, than installed systems. This causes many issues: * ubuntu efiboot entry is not created by the fallback manager from shim * one cannot reorder ubuntu boot entry, and/or boot and apply fwupdate updates (if possible) * measurements are unstable, and change if one call grub-install and or upgrades things * often grub & shim upgrades are not applied at all as \EFI\ubuntu does not exist on the ESP * We should switch to only shipping shim/fallback/mm in \ESP\Boot and ship \ESP\ubuntu on the cloud-image ESPs such that we regain stable measurements; ubuntu boot entry; and upgrades of grub and shim. [Test Case] * After UEFI firstboot $ efibootmgr --verbose => should contain `ubuntu` entry pointing at ESP\ubuntu\shim*.efi binary, which should be added to the bootorder [Where problems could occur] * Existing systems which were booted from previous style images, will not upgrade shim|grub on the ESP, and must call `grub-install` or `grub-multi-install` to correct that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912830/+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 1902260] Re: systemd-detect-virt is missing on Groovy EC2 AMI
This bug was fixed in the package livecd-rootfs - 2.664.17 --- livecd-rootfs (2.664.17) focal; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.664.16) focal; urgency=medium [ Cody Shepherd ] * Produce manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:52:00 + ** Changed in: livecd-rootfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1902260 Title: systemd-detect-virt is missing on Groovy EC2 AMI Status in cloud-images: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * On some image types, systemd-detect-virt might be missing [Test Case] * $ sudo systemd-detect-virt Should print a word. If it prints "no such file or directory" it is buggy. Best reproduced on initrdless boot, public cloud, where kernel flavour is switched, such as GCP groovy or AWS EC2 groovy. However other image types might be affected too. Backporting the change to all series, in case there are other places which invoke undivert_grub multiple times in a row. [Where problems could occur] * Hopefully, systemd-detect-virt undivert is now correct. Issues might happen in case systemd is not meant to be installed and yet the file remains on disk; or if the diversion is not removed still. Resulting in incorrect runtime behaviour. * For the images where this is fixed, systemd-detect-virt will now start working correctly. Thus may trigger automation to run that relied on missing systemd-detect-virt and thus previously did not execute. [Other Info] * Original bug report ubuntu/images/hvm-ssd/ubuntu-groovy-20.10-arm64-server-20201022.1 ubuntu@ip-172-31-30-199:~$ dpkg -S systemd-detect-virt systemd: /usr/bin/systemd-detect-virt systemd: /usr/share/bash-completion/completions/systemd-detect-virt systemd: /usr/share/man/man1/systemd-detect-virt.1.gz ubuntu@ip-172-31-30-199:~$ ls /usr/bin/systemd-detect-virt ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory Since livecd-rootfs plays with diversions of this file it looks suspicious, but I have not fully triaged the problem. LXD image for amd64 seems to be ok: ubuntu 20.10 amd64 (release) (20201022.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902260/+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 1910557] Re: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
This bug was fixed in the package livecd-rootfs - 2.664.17 --- livecd-rootfs (2.664.17) focal; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.664.16) focal; urgency=medium [ Cody Shepherd ] * Produce manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:52:00 + ** Changed in: livecd-rootfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in livecd-rootfs source package in Hirsute: Fix Released Bug description: livecd-rootfs v2.700 in hirsute introduced a fix to produce unpacked artifacts for use by multipass on macOS hosts. These hosts require direct access to a kernel and initrd to boot the buildd images. See: https://git.launchpad.net/livecd- rootfs/commit/?id=065c82314464fa78337d5122e1d4826a7d6edbb0 This change needs to be backported to all suites. [Impact] * Without this change, users are unable to use the buildd images with multipass on macOS hosts. Snapcraft utilizes multipass to build snaps, so this blocks macOS users from building snaps. As a workaround, the CPC team is manually extracting these artifacts and publishing them to cloud-images.ubuntu.com. This is not ideal for the long-term, and could result in breakage in the event that the CPC team forgets to manually publish these artifacts. [Test Case] * After this change lands, a user should be able to build images with the ubuntu-base project and buildd subproject, and the resulting build should produce extracted kernel and initrd artifacts. [Where problems could occur] * These changes are minor, but a mistake could result in broken buildd image hooks (where the build fails) or broken buildd image artifacts (where the images don't work as expected). * Since all buildd images are manually tested by the launchpad team, multipass team, and snapcraft team before they enter production, the risk of introducing breakage for end users is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+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 1912830] Re: Use non-removable uefi bootloader in cloud-images by default
This bug was fixed in the package livecd-rootfs - 2.664.17 --- livecd-rootfs (2.664.17) focal; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.664.16) focal; urgency=medium [ Cody Shepherd ] * Produce manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:52:00 + ** Changed in: livecd-rootfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1912830 Title: Use non-removable uefi bootloader in cloud-images by default Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Won't Fix Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * use non --removable uefi installation for cloud-images * Currently cloud-images use --removable grub installation, which makes the disk images look at lot more like our installer .isos, than installed systems. This causes many issues: * ubuntu efiboot entry is not created by the fallback manager from shim * one cannot reorder ubuntu boot entry, and/or boot and apply fwupdate updates (if possible) * measurements are unstable, and change if one call grub-install and or upgrades things * often grub & shim upgrades are not applied at all as \EFI\ubuntu does not exist on the ESP * We should switch to only shipping shim/fallback/mm in \ESP\Boot and ship \ESP\ubuntu on the cloud-image ESPs such that we regain stable measurements; ubuntu boot entry; and upgrades of grub and shim. [Test Case] * After UEFI firstboot $ efibootmgr --verbose => should contain `ubuntu` entry pointing at ESP\ubuntu\shim*.efi binary, which should be added to the bootorder [Where problems could occur] * Existing systems which were booted from previous style images, will not upgrade shim|grub on the ESP, and must call `grub-install` or `grub-multi-install` to correct that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912830/+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 1912835] Re: ESP should be fscked
This bug was fixed in the package livecd-rootfs - 2.664.17 --- livecd-rootfs (2.664.17) focal; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.664.16) focal; urgency=medium [ Cody Shepherd ] * Produce manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:52:00 + ** Changed in: livecd-rootfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1912835 Title: ESP should be fscked Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * ESP can be not clean, thus failing to mount on boot. * fsck should be enabled for ESP partition. [Test Case] * $ systemctl status systemd-fsck*.service On boot, that should produce status for two drives, the one with short uuid should be the one mounted as /ESP [Where problems could occur] * The change will affect only newly deployed instances. Old instances will have to correct this in fstab themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912835/+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 1902260] Re: systemd-detect-virt is missing on Groovy EC2 AMI
This bug was fixed in the package livecd-rootfs - 2.694.3 --- livecd-rootfs (2.694.3) groovy; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.694.2) groovy; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:40:38 + ** Changed in: livecd-rootfs (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1902260 Title: systemd-detect-virt is missing on Groovy EC2 AMI Status in cloud-images: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in livecd-rootfs source package in Bionic: Fix Committed Status in livecd-rootfs source package in Focal: Fix Committed Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * On some image types, systemd-detect-virt might be missing [Test Case] * $ sudo systemd-detect-virt Should print a word. If it prints "no such file or directory" it is buggy. Best reproduced on initrdless boot, public cloud, where kernel flavour is switched, such as GCP groovy or AWS EC2 groovy. However other image types might be affected too. Backporting the change to all series, in case there are other places which invoke undivert_grub multiple times in a row. [Where problems could occur] * Hopefully, systemd-detect-virt undivert is now correct. Issues might happen in case systemd is not meant to be installed and yet the file remains on disk; or if the diversion is not removed still. Resulting in incorrect runtime behaviour. * For the images where this is fixed, systemd-detect-virt will now start working correctly. Thus may trigger automation to run that relied on missing systemd-detect-virt and thus previously did not execute. [Other Info] * Original bug report ubuntu/images/hvm-ssd/ubuntu-groovy-20.10-arm64-server-20201022.1 ubuntu@ip-172-31-30-199:~$ dpkg -S systemd-detect-virt systemd: /usr/bin/systemd-detect-virt systemd: /usr/share/bash-completion/completions/systemd-detect-virt systemd: /usr/share/man/man1/systemd-detect-virt.1.gz ubuntu@ip-172-31-30-199:~$ ls /usr/bin/systemd-detect-virt ls: cannot access '/usr/bin/systemd-detect-virt': No such file or directory Since livecd-rootfs plays with diversions of this file it looks suspicious, but I have not fully triaged the problem. LXD image for amd64 seems to be ok: ubuntu 20.10 amd64 (release) (20201022.1) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902260/+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 1910557] Re: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
This bug was fixed in the package livecd-rootfs - 2.694.3 --- livecd-rootfs (2.694.3) groovy; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.694.2) groovy; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:40:38 + ** Changed in: livecd-rootfs (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in livecd-rootfs source package in Bionic: Fix Committed Status in livecd-rootfs source package in Focal: Fix Committed Status in livecd-rootfs source package in Groovy: Fix Released Status in livecd-rootfs source package in Hirsute: Fix Released Bug description: livecd-rootfs v2.700 in hirsute introduced a fix to produce unpacked artifacts for use by multipass on macOS hosts. These hosts require direct access to a kernel and initrd to boot the buildd images. See: https://git.launchpad.net/livecd- rootfs/commit/?id=065c82314464fa78337d5122e1d4826a7d6edbb0 This change needs to be backported to all suites. [Impact] * Without this change, users are unable to use the buildd images with multipass on macOS hosts. Snapcraft utilizes multipass to build snaps, so this blocks macOS users from building snaps. As a workaround, the CPC team is manually extracting these artifacts and publishing them to cloud-images.ubuntu.com. This is not ideal for the long-term, and could result in breakage in the event that the CPC team forgets to manually publish these artifacts. [Test Case] * After this change lands, a user should be able to build images with the ubuntu-base project and buildd subproject, and the resulting build should produce extracted kernel and initrd artifacts. [Where problems could occur] * These changes are minor, but a mistake could result in broken buildd image hooks (where the build fails) or broken buildd image artifacts (where the images don't work as expected). * Since all buildd images are manually tested by the launchpad team, multipass team, and snapcraft team before they enter production, the risk of introducing breakage for end users is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+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 1912830] Re: Use non-removable uefi bootloader in cloud-images by default
This bug was fixed in the package livecd-rootfs - 2.694.3 --- livecd-rootfs (2.694.3) groovy; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.694.2) groovy; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:40:38 + ** Changed in: livecd-rootfs (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1912830 Title: Use non-removable uefi bootloader in cloud-images by default Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Won't Fix Status in livecd-rootfs source package in Bionic: Fix Committed Status in livecd-rootfs source package in Focal: Fix Committed Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * use non --removable uefi installation for cloud-images * Currently cloud-images use --removable grub installation, which makes the disk images look at lot more like our installer .isos, than installed systems. This causes many issues: * ubuntu efiboot entry is not created by the fallback manager from shim * one cannot reorder ubuntu boot entry, and/or boot and apply fwupdate updates (if possible) * measurements are unstable, and change if one call grub-install and or upgrades things * often grub & shim upgrades are not applied at all as \EFI\ubuntu does not exist on the ESP * We should switch to only shipping shim/fallback/mm in \ESP\Boot and ship \ESP\ubuntu on the cloud-image ESPs such that we regain stable measurements; ubuntu boot entry; and upgrades of grub and shim. [Test Case] * After UEFI firstboot $ efibootmgr --verbose => should contain `ubuntu` entry pointing at ESP\ubuntu\shim*.efi binary, which should be added to the bootorder [Where problems could occur] * Existing systems which were booted from previous style images, will not upgrade shim|grub on the ESP, and must call `grub-install` or `grub-multi-install` to correct that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912830/+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 1912835] Re: ESP should be fscked
This bug was fixed in the package livecd-rootfs - 2.694.3 --- livecd-rootfs (2.694.3) groovy; urgency=medium [ David Krauser ] * buildd: produce kernel and initrd as separate artifacts LP: #1910557 * buildd: call update-initramfs for all installed kernels We only have one kernel installed, so we don't need to specify an explicit version. LP: #1910557 [ Dimitri John Ledkov ] * esp: install grub in ubuntu bootloader id path, instead of removable. (LP: #1912830) * esp: perform fsck. (LP: #1912835) * Perform fsck on all rootfs. (LP: #1912835) * functions: stop removing systemd-detect-virt unconditionally in undivert_grub (LP: #1902260) livecd-rootfs (2.694.2) groovy; urgency=medium [ Cody Shepherd ] * Create manifests for buildd tarball images (LP: #1914445) -- Dimitri John Ledkov Tue, 09 Feb 2021 00:40:38 + ** Changed in: livecd-rootfs (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1912835 Title: ESP should be fscked Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in livecd-rootfs source package in Bionic: Fix Committed Status in livecd-rootfs source package in Focal: Fix Committed Status in livecd-rootfs source package in Groovy: Fix Released Bug description: [Impact] * ESP can be not clean, thus failing to mount on boot. * fsck should be enabled for ESP partition. [Test Case] * $ systemctl status systemd-fsck*.service On boot, that should produce status for two drives, the one with short uuid should be the one mounted as /ESP [Where problems could occur] * The change will affect only newly deployed instances. Old instances will have to correct this in fstab themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912835/+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 1915254] Re: New upstream microreleases 9.5.25 10.16 12.6 13.2
This bug was fixed in the package postgresql-12 - 12.6-0ubuntu0.20.10.1 --- postgresql-12 (12.6-0ubuntu0.20.10.1) groovy-security; urgency=medium * New upstream version (LP: #1915254) + Fix incorrect detection of concurrent page splits while inserting into a GiST index (Heikki Linnakangas) Concurrent insertions could lead to a corrupt index with entries placed in the wrong pages. It's recommended to reindex any GiST index that's been subject to concurrent insertions. + Fix CREATE INDEX CONCURRENTLY to wait for concurrent prepared transactions (Andrey Borodin) At the point where CREATE INDEX CONCURRENTLY waits for all concurrent transactions to complete so that it can see rows they inserted, it must also wait for all prepared transactions to complete, for the same reason. Its failure to do so meant that rows inserted by prepared transactions might be omitted from the new index, causing queries relying on the index to miss such rows. In installations that have enabled prepared transactions (max_prepared_transactions > 0), it's recommended to reindex any concurrently-built indexes in case this problem occurred when they were built. + Fix information leakage in constraint-violation error messages (Heikki Linnakangas) If an UPDATE command attempts to move a row to a different partition but finds that it violates some constraint on the new partition, and the columns in that partition are in different physical positions than in the parent table, the error message could reveal the contents of columns that the user does not have SELECT privilege on. (CVE-2021-3393) + Details about these and many further changes can be found at: https://www.postgresql.org/docs/10/static/release-12-6.html -- Christian Ehrhardt Wed, 10 Feb 2021 11:47:33 +0100 ** Changed in: postgresql-12 (Ubuntu Groovy) Status: Triaged => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3393 ** Changed in: postgresql-12 (Ubuntu Focal) Status: Triaged => Fix Released -- 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/1915254 Title: New upstream microreleases 9.5.25 10.16 12.6 13.2 Status in postgresql-9.5 source package in Xenial: Triaged Status in postgresql-10 source package in Bionic: Triaged Status in postgresql-12 source package in Focal: Fix Released Status in postgresql-12 source package in Groovy: Fix Released Status in postgresql-13 source package in Hirsute: Incomplete Bug description: [Impact] * MRE for latest stable fixes of Postgres released on February 11th [Test Case] * The Postgres MREs traditionally rely on the large set of autopkgtests to run for verification. In a PPA those are all already pre-checked to be good for this upload. [Regression Potential] * Upstreams tests are usually great and in additon in the Archive there are plenty of autopkgtests that in the past catched issues before being released. But never the less there always is a risk for something to break. Since these are general stable releases I can't pinpoint them to a most-likely area. - usually this works smoothly except a few test hickups (flaky) that need to be clarified to be sure. Pre-checks will catch those to be discussed upfront (as last time) [Other Info] * This is a reoccurring MRE, see below and all the references * This includes a fix for one CVE: CVE-2021-3393 - only v12 for on Focal/Groovy --- Current versions in supported releases: postgresql-12 | 12.5-0ubuntu0.20.10.1 | groovy-security | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x postgresql-12 | 12.5-0ubuntu0.20.04.1 | focal-security | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x postgresql-10 | 10.15-0ubuntu0.18.04.1 | bionic-security | source, amd64, arm64, armhf, i386, ppc64el, s390x postgresql-9.5 | 9.5.24-0ubuntu0.16.04.1 | xenial-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x Special cases: - Hirsute will as usual be synced from Debian. Currently on 13.1 still postgresql-13 | 13.1-1build1 | hirsute | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x Standing MRE - Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 - pad.lv/1713979 - pad.lv/1730661 - pad.lv/1747676 - pad.lv/1752271 - pad.lv/1786938 - pad.lv/1815665 - pad.lv/1828012 - pad.lv/1833211 - pad.lv/1839058 - pad.lv/1863108 - pad.lv/1892335 As usual we test and prep from the PPA and then push through SRU/Security as applicable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/x
[Group.of.nepali.translators] [Bug 1914131] Re: xenial/linux-cascade: 4.4.0-1031.34 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** 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 built: main: build#1 meta: build#1 signed: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade - phase: Promote to Proposed - phase-changed: Friday, 12. February 2021 10:36 UTC + phase: Testing + phase-changed: Monday, 15. February 2021 09:31 UTC promote: - signed - main - meta + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Stalled -- review in progress + verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 -- 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/1914131 Title: xenial/linux-cascade: 4.4.0-1031.34 -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: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released 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: In Progress Status in linux source package in Xenial: Confirmed 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 built: main: build#1 meta: build#1 signed: build#1 kernel-stable-master-bug: 1914140 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Testing phase-changed: Monday, 15. February 2021 09:31 UTC promote: - signed - main - meta proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-cascade/cascade-kernel: bug 1914130 variant: debs versions: main: 4.4.0-1031.34 meta: 4.4.0.1031.34 signed: 4.4.0-1031.34 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1914131/+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
