[Group.of.nepali.translators] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
** Changed in: openssh (Ubuntu) Status: Invalid => Confirmed -- 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/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: Won't Fix Status in pam source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: Won't Fix Status in pam source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: Won't Fix Status in pam source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Won't Fix Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1938183] Re: xenial/linux-kvm: 4.4.0-1096.105 -proposed tracker
** Changed in: kernel-sru-workflow/boot-testing Status: In Progress => 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 -- boot-testing-requested: true built: main: build#1 meta: build#1 delta: sru-review: - meta - main kernel-stable-master-bug: 1938186 packages: main: linux-kvm meta: linux-meta-kvm - phase: Testing - phase-changed: Thursday, 29. July 2021 00:56 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 29. July 2021 01:37 UTC reason: - boot-testing: Ongoing -- testing in progress sru-review: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.4.0-1096.105 meta: 4.4.0.1096.94 source: 4.4.0-1096.105 -- 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/1938183 Title: xenial/linux-kvm: 4.4.0-1096.105 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released 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-signing-to-proposed series: Invalid 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm 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 built: main: build#1 meta: build#1 delta: sru-review: - meta - main kernel-stable-master-bug: 1938186 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Thursday, 29. July 2021 01:37 UTC reason: sru-review: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.4.0-1096.105 meta: 4.4.0.1096.94 source: 4.4.0-1096.105 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938183/+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 1938183] Re: xenial/linux-kvm: 4.4.0-1096.105 -proposed tracker
** 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 ** Changed in: kernel-sru-workflow/boot-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/boot-testing Status: Confirmed => Triaged ** 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 delta: sru-review: - meta - main kernel-stable-master-bug: 1938186 packages: main: linux-kvm meta: linux-meta-kvm - phase: Packaging - phase-changed: Wednesday, 28. July 2021 23:37 UTC + phase: Testing + phase-changed: Thursday, 29. July 2021 00:56 UTC reason: - :prepare-packages: Pending -- building in ppa (main,meta:pending) - prepare-package: Ongoing -- main package not yet fully built - prepare-package-meta: Ongoing -- meta package not yet fully built + boot-testing: Ongoing -- testing in progress sru-review: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.4.0-1096.105 meta: 4.4.0.1096.94 source: 4.4.0-1096.105 -- 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/1938183 Title: xenial/linux-kvm: 4.4.0-1096.105 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Triaged 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-signing-to-proposed series: Invalid 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Confirmed Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm 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 built: main: build#1 meta: build#1 delta: sru-review: - meta - main kernel-stable-master-bug: 1938186 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 29. July 2021 00:56 UTC reason: boot-testing: Ongoing -- testing in progress sru-review: Pending -- ready for review synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.4.0-1096.105 meta: 4.4.0.1096.94 source: 4.4.0-1096.105 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938183/+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 1938183] Re: xenial/linux-kvm: 4.4.0-1096.105 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** 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: 1938186 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Packaging - phase-changed: Wednesday, 28. July 2021 08:18 UTC + phase: Packaging + phase-changed: Wednesday, 28. July 2021 23:37 UTC reason: - :prepare-packages: Pending -b Debs ready to be cranked - prepare-package: Pending -- version not specified + :prepare-packages: 'Ongoing -b Being cranked by: kelsey-skunberg' + prepare-package: Pending -- tag not published and package not + uploaded + prepare-package-meta: Pending -- tag not published and package not + uploaded + synthetic: + :promote-to-as-proposed: Invalid 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/1938183 Title: xenial/linux-kvm: 4.4.0-1096.105 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New 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 promote-signing-to-proposed series: Invalid 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm 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: 1938186 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Wednesday, 28. July 2021 23:37 UTC reason: :prepare-packages: 'Ongoing -b Being cranked by: kelsey-skunberg' prepare-package: Pending -- tag not published and package not uploaded prepare-package-meta: Pending -- tag not published and package not uploaded synthetic: :promote-to-as-proposed: Invalid variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938183/+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 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-oracle (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gke-5.0 (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gke-4.15 (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gcp (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-aws (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 1896638] Re: Path to swapfile doesn't use a static device path
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: hibagent (Ubuntu Groovy) Status: New => Won't Fix -- 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/1896638 Title: Path to swapfile doesn't use a static device path Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in hibagent package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Fix Released Status in hibagent source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in hibagent source package in Bionic: New Status in ec2-hibinit-agent source package in Focal: Fix Released Status in hibagent source package in Focal: New Status in ec2-hibinit-agent source package in Groovy: Fix Released Status in hibagent source package in Groovy: Won't Fix Bug description: [Impact] * Using the device name on the kernel cmdline in the resume= option leads to failure to resume from hibernation when the device name is not stable, which can be the case for nvme drives. [Test Case] * Set up an EC2 instance to allow hibernation * Wait for hibinit-agent.service fully started * /etc/default/grub.d/99-set-swap.cfg should refer to the resume= partition by PARTUUID [Regression Potential] * Failure to discover PARTUUID makes the system unable to resume. A potential crash would cause the system unable to set up hibernation or unable to resume. (On Focal PARTUUID is already in use, even without this fix.) [Original Bug Text] When the agent inserts the resume device path and offset into the kernel cmdline, it uses device names such as the following: `resume_offset=223232 resume=/dev/nvme1n1p1` The issue is that `/dev/nvme1n1p1` is not static. On the reboot, the block device may appear at `/dev/nvme0n1p1` resulting in failure to find the swapfile used to suspend. The solution should be to use a persistent block device naming scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+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 1908264] Re: Disable Atari partition support for cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-aws (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Released Status in linux-gke source package in Focal: Fix Released Status in linux-gkeop source package in Focal: Fix Released Status in linux-oracle source package in Focal: Fix Released Status in linux-aws source package in Groovy: Won't Fix Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+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 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Bug description: Issue found on node grumman, this is not a regression. The kernel_tainted check reports a non-zero flag 2048, this means "workaround for bug in platform firmware applied" log_check reports WARNINGs found in the dmesg: 10. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 7.852005] WARNING: CPU: 0 PID: 179 at /build/linux-0dlxvs/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 11. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 5.387292] WARNING: CPU: 0 PID: 181 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 12. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 6.039705] WARNING: CPU: 0 PID: 4 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+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] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: rustc (Ubuntu Groovy) Status: In Progress => Won't Fix -- 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: Fix Released Status in rustc package in Ubuntu: Fix Released Status in cargo source package in Xenial: In Progress Status in rustc source package in Xenial: In Progress Status in cargo source package in Bionic: In Progress Status in rustc source package in Bionic: In Progress Status in cargo source package in Focal: In Progress Status in rustc source package in Focal: In Progress Status in cargo source package in Groovy: Won't Fix Status in rustc source package in Groovy: Won't Fix 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://gitlab.gnome.org/GNOME/librsvg/-/commit/513a575a839342f46bca713ac4eac37fbab9a7b7. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1692352 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+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] Re: rustc 1.50 and cargo 0.51 will be required by a future version of firefox
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: cargo (Ubuntu Groovy) Status: In Progress => Won't Fix -- 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: Fix Released Status in rustc package in Ubuntu: Fix Released Status in cargo source package in Xenial: In Progress Status in rustc source package in Xenial: In Progress Status in cargo source package in Bionic: In Progress Status in rustc source package in Bionic: In Progress Status in cargo source package in Focal: In Progress Status in rustc source package in Focal: In Progress Status in cargo source package in Groovy: Won't Fix Status in rustc source package in Groovy: Won't Fix 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://gitlab.gnome.org/GNOME/librsvg/-/commit/513a575a839342f46bca713ac4eac37fbab9a7b7. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1692352 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1915722/+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 1916485] Re: test -x fails inside shell scripts in containers
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: docker.io (Ubuntu Groovy) Status: New => Won't Fix -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused
[Group.of.nepali.translators] [Bug 1916485] Re: test -x fails inside shell scripts in containers
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: libseccomp (Ubuntu Groovy) Status: New => Won't Fix -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be
[Group.of.nepali.translators] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: makedumpfile (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
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/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Won't Fix
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Eoan:
Won't Fix
Status in makedumpfile source package in Focal:
Confirmed
Status in makedumpfile source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 1851663] Re: (In)consistent autopkgtest failures on ppc64el/s390x
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: makedumpfile (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1851663 Title: (In)consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Won't Fix Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+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 1898078] Re: FIPS OpenSSL crashes Python2.7 hashlib when using MD5
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: python2.7 (Ubuntu Groovy) Status: New => Won't Fix -- 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/1898078 Title: FIPS OpenSSL crashes Python2.7 hashlib when using MD5 Status in python2.7 package in Ubuntu: New Status in python2.7 source package in Xenial: New Status in python2.7 source package in Bionic: Fix Released Status in python2.7 source package in Focal: New Status in python2.7 source package in Groovy: Won't Fix Bug description: LP #1835135 was fixed in python2.7. However, when python2.7 was updated to current verion, the fix was not included. It needs to be included again into current version of python2.7 to prevent FIPS issues when using fips openssl with python's hashlib. This is only a problem in latest python2.7 versions in xenial, bionic, focal, and groovy. python3 versions do not have this problem in these releases. The fix was a backport of https://github.com/python/cpython/pull/1777/commits/5e3e3568d27b99dabe44b8aa6283dc76d70f2dae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1898078/+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 1903978] Re: New upstream microreleases 9.5.24 10.15, 12.5 and 13.1
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: postgresql-12 (Ubuntu Groovy) Status: Triaged => Won't Fix -- 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/1903978 Title: New upstream microreleases 9.5.24 10.15, 12.5 and 13.1 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: Triaged Status in postgresql-12 source package in Groovy: Won't Fix Status in postgresql-12 source package in Hirsute: Triaged Status in postgresql-13 source package in Hirsute: In Progress Bug description: [Impact] * MRE for latest stable fixes of Postgres release on August 13th. [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 CVEs: CVE-2020-25694 CVE-2020-25695 CVE-2020-25696 --- Current versions in supported releases: postgresql-9.5 | 9.5.23-0ubuntu0.16.04.1 | xenial-updates postgresql-10 | 10.14-0ubuntu0.18.04.1 | bionic-updates postgresql-12 | 12.4-0ubuntu0.20.04.1 | focal-updates postgresql-12 | 12.4-1| groovy postgresql-13 | 13.0-6build1 | hirsute-proposed/universe Special cases: - Hirsute will as usual be synced from Debian. I already see postgresql-13 | 13.1-1| unstable| source, amd64, arm64, armhf, i386, ppc64el, s390x - 21.04 also has a postgresql-12 and while that is on the way to be removed and fulyl replaced by 13 that is too far out. Therefore we will upload 12.5 to Hirsute as well. - I have checked with Debian (they are affected by the same FTFBS and test fails of bug 1903573) but they will just remove postgresql-12 from testing. We can't do that yet on hirsute without breaking too much Last relevant related stable updates: 9.5.23, 10.14 and 12.4 You'll see that the last update was missed, so I'll combined them. 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. --- Interim test state Xenial https://bileto.ubuntu.com/excuses/4331/xenial.html Good except the following which are all masked in hints-ubuntu bareos/14.2.6-3 libreoffice/1:5.1.6~rc2-0ubuntu1~xenial10 pdns/4.0.0~alpha2-3build1: amd64 pgpool2/3.4.3-1: amd64 Bionic https://bileto.ubuntu.com/excuses/4332/bionic.html Good except the following which are all masked in hints-ubuntu pdns/4.1.1-1 pglogical/2.1.1-1 postgresql-multicorn/1.3.4-1 Focal https://bileto.ubuntu.com/excuses/4333/focal.html Many i386 dependency issues - all masked in hints-ubuntu Good except the following which are all masked in hints-ubuntu postgresql-multicorn/1.3.4-31-g9ff7875-3 diaspora-installer/0.7.6.1+debian1 Groovy https://bileto.ubuntu.com/excuses/4334/groovy.html Many i386 dependency issues - all masked in hints-ubuntu The rest are the usual suspects which are ok pdns/4.3.0-4build2 pglogical/2.3.2-1 pglogical-ticker/1.4.0-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/xenial/+source/postgresql-9.5/+bug/1903978/+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 1921902] Re: Security-Fix Xen XSA 371 for Kernel 5.4.0-71
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Won't Fix
--
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/1921902
Title:
Security-Fix Xen XSA 371 for Kernel 5.4.0-71
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
In Progress
Bug description:
[SRU Justification]
See [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html). commit
871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error
handling in xen_blkbk_map()") introduced a security vulnerability.
Original Commit:
871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error handling in
xen_blkbk_map()")
New commit with security fix:
a846738f8c3788d846ed1f587270d2f2e3d32432 ("xen-blkback: don't leak persistent
grants from xen_blkbk_map()")
[Test Plan]
none
[Where problems could occur]
Unknown
[Other Info]
- http://xenbits.xen.org/xsa/advisory-371.html
- http://xenbits.xen.org/xsa/xsa371-linux.patch
- http://xenbits.xen.org/xsa/advisory-365.html
- http://xenbits.xen.org/xsa/xsa365-linux.patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921902/+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 1926183] Re: 'ua fix' tells me to reboot with inaccurate message
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: ubuntu-advantage-tools (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/1926183 Title: 'ua fix' tells me to reboot with inaccurate message Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Committed Status in ubuntu-advantage-tools source package in Focal: Fix Committed Status in ubuntu-advantage-tools source package in Groovy: Won't Fix Status in ubuntu-advantage-tools source package in Hirsute: Fix Committed Status in ubuntu-advantage-tools source package in Impish: Fix Released Bug description: [Impact] When using an affected version of uaclient (any beta of v27) and using the `fix` command, the user could be shown a misleading message. Specifically, if the users machine has the system reboot required flag set, and then they use the `ua fix` command, uaclient will say that a reboot is required to complete the fix, even though uaclient didn't even have to install anything. [Test case] The following example will work on xenial, bionic, focal, and groovy. To reproduce on hirsute, use USN-4913-2 instead of USN-4898-1, and use node-underscore instead of curl in the instructions below. To reproduce: 1. Launch a container: using focal here as an example lxc launch ubuntu-daily:focal dev-f 2. Add the uaclient staging ppa: https://launchpad.net/~ua-client/+archive/ubuntu/staging add-apt-repository ppa:ua-client/staging apt-get update 3. Install version 27 beta 3 apt install ubuntu-advantage-tools=27.0~20.04.1~beta3 4. Make sure you have the latest version of curl installed apt install curl 5. Touch the reboot-required file sudo touch /var/run/reboot-required 6. Attempt to fix https://ubuntu.com/security/notices/USN-4898-1 ua fix USN-4898-1 7. See a message like this USN-4898-1: curl vulnerabilities Found CVEs: https://ubuntu.com/security/CVE-2021-22890 https://ubuntu.com/security/CVE-2021-22876 1 affected package is installed: curl (1/1) curl: A fix is available in Ubuntu standard updates. The update is already installed. A reboot is required to complete fix operation. ✘ USN-4898-1 is not resolved. To see the fixed version: 1. Launch a container: using focal here as an example lxc launch ubuntu-daily:focal dev-f 2. Add this ppa that contains the unreleased fix for this bug: https://launchpad.net/~orndorffgrant/+archive/ubuntu/uaclient-staging-27 add-apt-repository ppa:orndorffgrant/uaclient-staging-27 apt-get update 3. Install version 27 apt install ubuntu-advantage-tools 4. Make sure you have the latest version of curl installed apt install curl 5. Touch the reboot-required file sudo touch /var/run/reboot-required 6. Attempt to fix https://ubuntu.com/security/notices/USN-4898-1 ua fix USN-4898-1 7. See a message like this USN-4898-1: curl vulnerabilities Found CVEs: https://ubuntu.com/security/CVE-2021-22890 https://ubuntu.com/security/CVE-2021-22876 1 affected package is installed: curl (1/1) curl: A fix is available in Ubuntu standard updates. The update is already installed. ✔ USN-4898-1 is resolved. [Where problems could occur] The logic of when to show the reboot required message is still based on the system /var/run/reboot-required flag, and this fix adds additional complexity to our messaging logic after fixing a cve/usn. If this new logic isn't quite right, it may result in uaclient still saying that a reboot is required to complete a fix even when it isn't (for some other situation not in this bug). Or from the opposite direction: if the logic is wrong, it could result in uaclient failing to tell the user that a reboot is required to complete a fix, even when it is. More generally, the changeset is large and carries the risk of other unexpected issues. Any unexpected issues would be limited to uaclient behavior though. [Discussion] This bug doesn't actually exist outside of the v27 betas in the ua- client/staging ppa. The number of users affected by this bug is very low and almost entirely limited to those who were deliberately testing the v27 betas. Because of this, the risk associated with fixing this bug is predicted to be very low. [Original Report] root@malefic:~# ua fix CVE-2021-3410 CVE-2021-3410: libcaca vulnerability https://ubuntu.com/security/CVE-2021-3410 1 affected package is installed: libcaca (1/1) libcaca: A fix is available in Ubuntu standard
[Group.of.nepali.translators] [Bug 1825755] Re: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: apt-mirror (Ubuntu Groovy) Status: Triaged => Won't Fix -- 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/1825755 Title: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files Status in apt-mirror package in Ubuntu: Triaged Status in apt-mirror source package in Xenial: Confirmed Status in apt-mirror source package in Bionic: Triaged Status in apt-mirror source package in Eoan: Won't Fix Status in apt-mirror source package in Focal: Triaged Status in apt-mirror source package in Groovy: Won't Fix Bug description: [Impact] * since ubuntu disco, main repositories contains 'cnf' directory with 'Commands*' files. those files are compressed with xy, whereas apt- mirror 0.5.1 doesn't contain the patch which enable download of .xz compressed files * Without this update, users are not able to mirror newer releases of Ubuntu. [Test Case] * On any release of Ubuntu install apt-mirror and add this line to /etc/apt/mirror.list: deb http://archive.ubuntu.com/ubuntu eoan-updates main restricted universe multiverse * sync the mirror using `apt-mirror` * Attempt to run `apt update` against the mirror. The result will be similar to: ... Err:7 http://10.3.0.41/ubuntu eoan-updates/main amd64 c-n-f Metadata 404 Not Found [IP: 10.3.0.41 80] Ign:14 http://10.3.0.41/ubuntu eoan-updates/multiverse amd64 c-n-f Metadata Ign:15 http://10.3.0.41/ubuntu eoan-updates/universe amd64 c-n-f Metadata Ign:16 http://10.3.0.41/ubuntu eoan-updates/restricted amd64 c-n-f Metadata Reading package lists... Done E: Failed to fetch http://10.3.0.41/ubuntu/dists/eoan-updates/main/cnf/Commands-amd64 404 Not Found [IP: 10.3.0.41 80] E: Some index files failed to download. They have been ignored, or old ones used instead. ... * Updating the apt-mirror package from ppa:slashd/test and then re- running the `apt-mirror` command will then allow a successful `apt update`. [Regression Potential] * The regression potential is low since the package doesn't currently work properly anyway. * It's a patchset from a fork repo, if apt-mirror upstream becomes alive again in the future, it won't necessary mean that the fork will be commited/merged upstream, and Ubuntu package might differ from original upstream until next version bump. [Other informations] Upstream bug: https://github.com/apt-mirror/apt-mirror/issues/118 Not much update has been made since Upstream become inactive as noted from the output of rmadison: Since Bionic, it is a simple copy from release to active devel release and so on directly from debian, no patching whatsoever and nothing new to pull from Debian as well. Ubuntu apt-mirror | 0.5.1-1ubuntu1 | xenial/universe | source, all apt-mirror | 0.5.4-1 | bionic/universe | source, all apt-mirror | 0.5.4-1 | disco/universe | source, all apt-mirror | 0.5.4-1 | eoan/universe| source, all apt-mirror | 0.5.4-1 | focal/universe | source, all apt-mirror | 0.5.4-1 | groovy/universe | source, all Debian apt-mirror 0.5.4-1 is found in sid/unstable --- The required patchset is from a fork of upstream apt-mirror josbraden/apt-mirror (https://github.com/josbraden/apt-mirror) Note that upstream apt-mirror is not active anymore, and is looking for a new maintainer as published in their github page: https://github.com/apt-mirror/apt-mirror That's why we have to rely on the fork atm. The required patchset are (tested by Chris in the form of a test pkg: 0001-Copy-DEP-11-functions-for-editing.patch 0001-Replace-DEP-11-with-cnf-in-DEP-11-code-copy.patch 0001-Fix-Regex.patch 0001-Improve-regex-for-cnf-file-matching.patch 0001-Remove-dev-note.patch 0001-Fix-missing-parenthesis.patch I also talked with sil2100 (SRU verification team member) about the feasibilty of this SRU (from a fork repo): " Yeah, I'd say fixes from forked repositories in this case make sense Since there's no longer any 'one authority' for it. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1825755/+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 1832182] Re: systemd unable to detect running apache if invoked via "apache2ctl graceful"
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: apache2 (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Xenial: Won't Fix Status in apache2 source package in Bionic: Fix Committed Status in apache2 source package in Focal: Fix Committed Status in apache2 source package in Groovy: Won't Fix Status in apache2 source package in Hirsute: Fix Released Status in apache2 package in Debian: New Bug description: [Impact] Unattended upgrade will attempt to gracefully reload the Apache2 httpd service, but it reloads apache directly, not via systemd, so systemctl will mis-report the true status. This can cause unexpected and unnecessary server outages when e.g. upgrading from one LTS to another. [Test Case] root@server:/usr/local/sbin# apache2ctl stop root@server:/usr/local/sbin# apache2ctl graceful httpd not running, trying to start root@server:/usr/local/sbin# systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d +-apache2-systemd.conf Active: inactive (dead) since Mon 2019-06-10 01:04:13 MDT; 17s ago Process: 27370 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS) Process: 11462 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS) Main PID: 1849 (code=exited, status=0/SUCCESS) Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server apachectl[1408]: AH00112: Warning: DocumentRoot [/srv/apache2/www/... Jun 08 19:11:24 server systemd[1]: Started The Apache HTTP Server. Jun 09 06:25:04 server systemd[1]: Reloading The Apache HTTP Server. Jun 09 06:25:04 server systemd[1]: Reloaded The Apache HTTP Server. Jun 10 01:04:13 server apachectl[27370]: httpd (no pid file) not running Output after customizing the apache2ctl script and restarting it: root@server:/usr/local/sbin# apache2ctl_custom graceful Invoking 'systemctl start apache2'. Use 'systemctl status apache2' for more info. root@server:/usr/local/sbin# systemctl status apache2.service ? apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d +-apache2-systemd.conf Active: active (running) since Mon 2019-06-10 01:04:50 MDT; 4s ago Process: 27370 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS) Process: 11462 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS) Process: 27432 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS) Main PID: 27444 (apache2) Tasks: 6 (limit: 2318) CGroup: /system.slice/apache2.service +-27444 /usr/sbin/apache2 -k start +-27448 /usr/sbin/apache2 -k start +-27449 /usr/sbin/apache2 -k start +-27451 /usr/sbin/apache2 -k start +-27454 /usr/sbin/apache2 -k start +-27455 /usr/sbin/apache2 -k start Jun 10 01:04:50 server systemd[1]: Starting The Apache HTTP Server... Jun 10 01:04:50 server systemd[1]: Started The Apache HTTP Server. [Fix] The fix is made somewhat obvious due to the fact that the issue was fixed for "apache2ctl start" in 18.04 LTS by replacing the regular call (which resolves to "/usr/sbin/apache2 -k start") with a check for presence of systemd, followed by an invocation of "systemctl start apache2.service" if that check is affirmative, or falling back to the old start command if that check is negative. Attached to this bug report is a diff of the file before and after I copied the fixed invocation from the "start" subsection to the "graceful" subsection in 18.04 LTS. A fix for 16.04 LTS would require copying that block both into the "start" and "graceful" subsections. [Regression Potential] This alters the behavior of Debian's apache2ctl script for managing the service state. No other Apache2 code is
[Group.of.nepali.translators] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
** Changed in: openssh (Ubuntu) Status: Confirmed => Invalid ** Changed in: openssh (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: Won't Fix Status in pam source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: Won't Fix Status in pam source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: Won't Fix Status in pam source package in Focal: Fix Released Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Won't Fix Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1938179] Re: xenial/linux-aws: 4.4.0-1131.145 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** 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: 1938186 packages: main: linux-aws meta: linux-meta-aws - phase: Ready for Packaging - phase-changed: Wednesday, 28. July 2021 08:18 UTC + phase: Packaging + phase-changed: Wednesday, 28. July 2021 16:58 UTC reason: - :prepare-packages: Pending -b Debs ready to be cranked - prepare-package: Pending -- version not specified + :prepare-packages: 'Ongoing -b Being cranked by: timg-tpi' + prepare-package: Pending -- tag not published and package not + uploaded + prepare-package-meta: Pending -- tag not published and package not + uploaded + synthetic: + :promote-to-as-proposed: Invalid trackers: xenial/linux-aws/aws-kernel: bug 1938178 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/1938179 Title: xenial/linux-aws: 4.4.0-1131.145 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New 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 promote-signing-to-proposed series: Invalid 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: New Status in Kernel SRU Workflow verification-testing series: New 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 -- kernel-stable-master-bug: 1938186 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Wednesday, 28. July 2021 16:58 UTC reason: :prepare-packages: 'Ongoing -b Being cranked by: timg-tpi' prepare-package: Pending -- tag not published and package not uploaded prepare-package-meta: Pending -- tag not published and package not uploaded synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-aws/aws-kernel: bug 1938178 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938179/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Changed in: apport (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Won't Fix Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Bug description: [Impact] apport-unpack crashes when trying to unpack a crash [Test Case] On a system running 20.04 LTS: 1) create an additional user who is only a member of their own group e.g. bdmurray@clean-focal-amd64:~$ id crashy uid=1001(crashy) gid=1001(crashy) groups=1001(crashy) 2) Launch a process as that user 3) kill -11 that process 4) Confirm there is a crash file in /var/crash for that process 5) Run apport-unpack on that .crash file With the version of apport from -proposed you will not get another crash file when unpacking the crash file. [Regression Potential] We are just setting UserGroups to 'N/A' as opposed to having it be completely empty so there isn't any chance for regression. When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: BugDistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1938186] Re: xenial/linux: 4.4.0-213.245 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/boot-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/boot-testing Status: Confirmed => Triaged ** 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 delta: sru-review: - signed - meta - main packages: main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Wednesday, 28. July 2021 07:36 UTC + phase: Testing + phase-changed: Wednesday, 28. July 2021 12:06 UTC reason: - :prepare-packages: Pending -- building in ppa (meta:pending) - prepare-package-meta: Ongoing -- meta package not yet fully built + boot-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: main: 4.4.0-213.245 meta: 4.4.0.213.220 signed: 4.4.0-213.245 source: 4.4.0-213.245 -- 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/1938186 Title: xenial/linux: 4.4.0-213.245 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Triaged Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow kernel-signoff series: New 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: 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released 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 -- boot-testing-requested: true built: main: build#1 meta: build#1 signed: build#1 delta: sru-review: - signed - meta - main packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 28. July 2021 12:06 UTC reason: boot-testing: Ongoing -- testing in progress synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: main: 4.4.0-213.245 meta: 4.4.0.213.220 signed: 4.4.0-213.245 source: 4.4.0-213.245 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938186/+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 1938186] Re: xenial/linux: 4.4.0-213.245 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed 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 -- built: main: build#1 meta: build#1 signed: build#1 delta: sru-review: - signed - meta - main packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 28. July 2021 07:36 UTC reason: - :prepare-packages: Pending -- building in ppa (signed:pending - meta:queued) + :prepare-packages: Pending -- building in ppa (meta:pending) prepare-package-meta: Ongoing -- meta package not yet fully built - prepare-package-signed: Ongoing -- signed package not yet fully - built synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: main: 4.4.0-213.245 meta: 4.4.0.213.220 signed: 4.4.0-213.245 source: 4.4.0-213.245 -- 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/1938186 Title: xenial/linux: 4.4.0-213.245 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow kernel-signoff 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 Released 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released 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 -- built: main: build#1 meta: build#1 signed: build#1 delta: sru-review: - signed - meta - main packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 28. July 2021 07:36 UTC reason: :prepare-packages: Pending -- building in ppa (meta:pending) prepare-package-meta: Ongoing -- meta package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: main: 4.4.0-213.245 meta: 4.4.0.213.220 signed: 4.4.0-213.245 source: 4.4.0-213.245 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938186/+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 1938186] Re: xenial/linux: 4.4.0-213.245 -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 -- built: main: build#1 meta: build#1 signed: build#1 delta: sru-review: - signed - meta - main packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 28. July 2021 07:36 UTC reason: - :prepare-packages: Pending -- building in ppa (meta,signed:depwait - main:pending) - prepare-package: Ongoing -- main package not yet fully built + :prepare-packages: Pending -- building in ppa (meta:building + signed:pending) prepare-package-meta: Ongoing -- meta package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: main: 4.4.0-213.245 meta: 4.4.0.213.220 signed: 4.4.0-213.245 source: 4.4.0-213.245 -- 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/1938186 Title: xenial/linux: 4.4.0-213.245 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow kernel-signoff 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-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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released 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 -- built: main: build#1 meta: build#1 signed: build#1 delta: sru-review: - signed - meta - main packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 28. July 2021 07:36 UTC reason: :prepare-packages: Pending -- building in ppa (meta:building signed:pending) prepare-package-meta: Ongoing -- meta package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: main: 4.4.0-213.245 meta: 4.4.0.213.220 signed: 4.4.0-213.245 source: 4.4.0-213.245 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938186/+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 1938186] Re: xenial/linux: 4.4.0-213.245 -proposed tracker
** Changed in: kernel-sru-workflow/sru-review Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/sru-review Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/sru-review Status: In Progress => 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/1938186 Title: xenial/linux: 4.4.0-213.245 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow kernel-signoff series: New Status in Kernel SRU Workflow prepare-package series: Fix Committed 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-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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released 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 -- built: main: build#1 meta: build#1 signed: build#1 delta: sru-review: - signed - meta - main packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 28. July 2021 07:36 UTC reason: :prepare-packages: Ongoing -- building in ppa (main:building meta,signed:depwait) prepare-package: Ongoing -- main package not yet fully built prepare-package-meta: Ongoing -- meta package not yet fully built prepare-package-signed: Ongoing -- signed package not yet fully built synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: main: 4.4.0-213.245 meta: 4.4.0.213.220 signed: 4.4.0-213.245 source: 4.4.0-213.245 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938186/+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 1938186] Re: xenial/linux: 4.4.0-213.245 -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 -- packages: main: linux meta: linux-meta signed: linux-signed - phase: Ready for Packaging - phase-changed: Tuesday, 27. July 2021 14:53 UTC + phase: Packaging + phase-changed: Wednesday, 28. July 2021 07:36 UTC reason: - :prepare-packages: Pending -b Debs ready to be cranked + :prepare-packages: 'Ongoing -b Being cranked by: smb' derivatives-held: Stalled -- derivative preparation block requested - prepare-package: Pending -- version not specified + prepare-package: Stalled -- tag not published and package not + uploaded + prepare-package-meta: Stalled -- package not uploaded + prepare-package-signed: Stalled -- tag not published and package not + uploaded + synthetic: + :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs + versions: + meta: 4.4.0.213.220 + source: 4.4.0-213.245 -- 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/1938186 Title: xenial/linux: 4.4.0-213.245 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow kernel-signoff series: New 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: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: New 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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 28. July 2021 07:36 UTC reason: :prepare-packages: 'Ongoing -b Being cranked by: smb' derivatives-held: Stalled -- derivative preparation block requested prepare-package: Stalled -- tag not published and package not uploaded prepare-package-meta: Stalled -- package not uploaded prepare-package-signed: Stalled -- tag not published and package not uploaded synthetic: :promote-to-as-proposed: Invalid trackers: trusty/linux-aws: bug 1938184 trusty/linux-lts-xenial: bug 1938185 xenial/linux-aws: bug 1938179 xenial/linux-cascade: bug 1938181 xenial/linux-fips: bug 1938182 xenial/linux-kvm: bug 1938183 xenial/linux/caracalla-kernel: bug 1938175 xenial/linux/pc-kernel: bug 1938176 xenial/linux/stlouis-kernel: bug 1938177 variant: debs versions: meta: 4.4.0.213.220 source: 4.4.0-213.245 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1938186/+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
