[Group.of.nepali.translators] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 - phase: Promote to Proposed - phase-changed: Thursday, 14. February 2019 12:34 UTC + phase: Testing + phase-changed: Monday, 18. February 2019 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress -- 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/1814651 Title: linux-aws: 4.4.0-1076.86 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814647 phase: Testing phase-changed: Monday, 18. February 2019 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814651/+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 1814744] Re: linux-gcp: 4.15.0-1028.29~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 - phase: Promote to Proposed - phase-changed: Friday, 15. February 2019 10:09 UTC + phase: Testing + phase-changed: Monday, 18. February 2019 17:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: Pending -- snap not in beta channel - snap-release-to-edge: Pending -- snap not in edge channel + snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress -- 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/1814744 Title: linux-gcp: 4.15.0-1028.29~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1814726 phase: Testing phase-changed: Monday, 18. February 2019 17:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1028 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814744/+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 1815212] Re: [Xenial][Bionic][SRU] Update pci.ids to version 2018.07.21
This bug was fixed in the package pciutils - 1:3.5.2-1ubuntu1.1 --- pciutils (1:3.5.2-1ubuntu1.1) bionic; urgency=medium * d/p/08-update-2018-07-21-pciids.patch: - Update pci.ids to version 2018-07-21. (LP: #1815212) -- Eric Sun, 10 Feb 2019 18:25:12 + ** Changed in: pciutils (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815212 Title: [Xenial][Bionic][SRU] Update pci.ids to version 2018.07.21 Status in pciutils package in Ubuntu: Fix Released Status in pciutils source package in Xenial: Fix Released Status in pciutils source package in Bionic: Fix Released Bug description: [Impact] pci.ids table in Xenial seems a little bit behind in term of new device id added since last time it was updated. Some user are observing that their new device doesn't show up because they don't exist in the pci.ids file yet. User or troubleshooter may get a wrong impression that, for instance, the correct raid controller is not present, if the user doesn't read the PCI bus address. While we are here, I will update Xenial and Bionic to be at the same version level (Version: 2018.07.21) of current devel release (Disco) which isn't too far behind current upstream (github) one in master branch. x/pciutils-3.3.1/pci.ids:#Version: 2016.01.02 b/pciutils-3.5.2/pci.ids:#Version: 2017.03.16 c/pciutils-3.5.2/pci.ids:#Version: 2018.07.21 d/pciutils-3.5.2/pci.ids:#Version: 2018.07.21 upstream/pciutils/pci.ids:# Version: 2018.08.12 [Test case] * Deploy Xenial and/or Bionic system. * Run 'lspci' command took from the pciutils package found in the Ubuntu archive * Look all listed devices are recognised with the proper device name/vendor/... Here's an example took by a user using a device id (0014) not in the Xenial pci.ids table: lspci on Xenial: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 0014 (rev 01) lspci on Bionic: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID Tri-Mode SAS3516 (rev 01) [Pending SRU status] * XENIAL - Regression in autopkgtest for linux-oracle https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-oracle/20190211_192705_fa550@/log.gz ERROR: running version does not match source package Source Package Version: 4.15.0-1008.10~16.04.1 Running Kernel Version: 4.4.0-142.168 ==> https://launchpad.net/bugs/1723223 - Regression in autopkgtest for linux (i386): test log Recurrent failure from various trigger (not introduced by this ongoing SRU) http://autopkgtest.ubuntu.com/packages/l/linux/xenial/i386 * BIONIC - Regression in autopkgtest for linux-oracle (amd64): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-oracle/20190211_163710_b6f0a@/log.gz Source Package Version: 4.15.0-1008.10 Running Kernel Version: 4.15.0-45.48 ERROR: running version does not match source package ==> https://launchpad.net/bugs/1723223 - Regression in autopkgtest for linux-gcp-edge (amd64): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-gcp-edge/20190211_163830_8dce2@/log.gz Source Package Version: 4.15.0-1008.10 Running Kernel Version: 4.15.0-45.48 ERROR: running version does not match source package ==> https://launchpad.net/bugs/1723223 - Regression in autopkgtest for linux (ppc64el): test log - Regression in autopkgtest for linux (i386): test log Recurrent failure from various trigger (not introduced by this ongoing SRU) http://autopkgtest.ubuntu.com/packages/l/linux/bionic/ppc64el http://autopkgtest.ubuntu.com/packages/l/linux/bionic/i386 [Regression Potential] Low, no core functionality change. The intention is to only update pci.ids table list to recognise new PCI vendor/product list, by updating it to the same version level as Cosmic and Disco has as of today. The only thing I can think of ... In some cases there is some device id renaming, which I guess can "possibly" impact some user script and/or HW inventory solution. If this happens to certain users, I don't expect it to have a major impact and this should can be consider low and easy to fix by the user or admin of the HW inventory solution ... IMHO. Example: - 67df Ellesmere [Polaris10] + 67df Ellesmere [Radeon RX 470/480] [Other information] Confirmed w/ vorlon (SRU verification team) on #ubuntu-release https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases For Long Term Support releases we regularly want to enable new hardware. Such
[Group.of.nepali.translators] [Bug 1815212] Re: [Xenial][Bionic][SRU] Update pci.ids to version 2018.07.21
This bug was fixed in the package pciutils - 1:3.3.1-1.1ubuntu1.3 --- pciutils (1:3.3.1-1.1ubuntu1.3) xenial; urgency=medium * d/p/09-update-2018-07-21-pciids.patch: - Update pci.ids to version 2018-07-21. (LP: #1815212) -- Eric Sun, 10 Feb 2019 18:27:49 + ** Changed in: pciutils (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1815212 Title: [Xenial][Bionic][SRU] Update pci.ids to version 2018.07.21 Status in pciutils package in Ubuntu: Fix Released Status in pciutils source package in Xenial: Fix Released Status in pciutils source package in Bionic: Fix Released Bug description: [Impact] pci.ids table in Xenial seems a little bit behind in term of new device id added since last time it was updated. Some user are observing that their new device doesn't show up because they don't exist in the pci.ids file yet. User or troubleshooter may get a wrong impression that, for instance, the correct raid controller is not present, if the user doesn't read the PCI bus address. While we are here, I will update Xenial and Bionic to be at the same version level (Version: 2018.07.21) of current devel release (Disco) which isn't too far behind current upstream (github) one in master branch. x/pciutils-3.3.1/pci.ids:#Version: 2016.01.02 b/pciutils-3.5.2/pci.ids:#Version: 2017.03.16 c/pciutils-3.5.2/pci.ids:#Version: 2018.07.21 d/pciutils-3.5.2/pci.ids:#Version: 2018.07.21 upstream/pciutils/pci.ids:# Version: 2018.08.12 [Test case] * Deploy Xenial and/or Bionic system. * Run 'lspci' command took from the pciutils package found in the Ubuntu archive * Look all listed devices are recognised with the proper device name/vendor/... Here's an example took by a user using a device id (0014) not in the Xenial pci.ids table: lspci on Xenial: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic Device 0014 (rev 01) lspci on Bionic: 60:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID Tri-Mode SAS3516 (rev 01) [Pending SRU status] * XENIAL - Regression in autopkgtest for linux-oracle https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-oracle/20190211_192705_fa550@/log.gz ERROR: running version does not match source package Source Package Version: 4.15.0-1008.10~16.04.1 Running Kernel Version: 4.4.0-142.168 ==> https://launchpad.net/bugs/1723223 - Regression in autopkgtest for linux (i386): test log Recurrent failure from various trigger (not introduced by this ongoing SRU) http://autopkgtest.ubuntu.com/packages/l/linux/xenial/i386 * BIONIC - Regression in autopkgtest for linux-oracle (amd64): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-oracle/20190211_163710_b6f0a@/log.gz Source Package Version: 4.15.0-1008.10 Running Kernel Version: 4.15.0-45.48 ERROR: running version does not match source package ==> https://launchpad.net/bugs/1723223 - Regression in autopkgtest for linux-gcp-edge (amd64): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-gcp-edge/20190211_163830_8dce2@/log.gz Source Package Version: 4.15.0-1008.10 Running Kernel Version: 4.15.0-45.48 ERROR: running version does not match source package ==> https://launchpad.net/bugs/1723223 - Regression in autopkgtest for linux (ppc64el): test log - Regression in autopkgtest for linux (i386): test log Recurrent failure from various trigger (not introduced by this ongoing SRU) http://autopkgtest.ubuntu.com/packages/l/linux/bionic/ppc64el http://autopkgtest.ubuntu.com/packages/l/linux/bionic/i386 [Regression Potential] Low, no core functionality change. The intention is to only update pci.ids table list to recognise new PCI vendor/product list, by updating it to the same version level as Cosmic and Disco has as of today. The only thing I can think of ... In some cases there is some device id renaming, which I guess can "possibly" impact some user script and/or HW inventory solution. If this happens to certain users, I don't expect it to have a major impact and this should can be consider low and easy to fix by the user or admin of the HW inventory solution ... IMHO. Example: - 67df Ellesmere [Polaris10] + 67df Ellesmere [Radeon RX 470/480] [Other information] Confirmed w/ vorlon (SRU verification team) on #ubuntu-release https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases For Long Term Support releases we regularly want to enable new hardware.
[Group.of.nepali.translators] [Bug 1813873] Re: Userspace break as a result of missing patch backport
Hi Edgar, I've changed it back =) It should be Fix Committed if the patch is present/merged in the kernel, but kernel wasn't released yet. Once it gets released, it'll get changed to Fix Released. Cheers, Guilherme ** Changed in: linux (Ubuntu Bionic) Status: Fix Released => Fix Committed -- 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/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1813873] Re: Userspace break as a result of missing patch backport
Hello, I mistakenly change the status of Bionic to Fix released, I didn't know that I could change something like this since I'm not a maitainer of some sort, I'm just an end user. I tried to cancel the change but I don't have the right to do so. ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1813873 Title: Userspace break as a result of missing patch backport Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: Hi, The most recent set of Ubuntu kernels applied a variety of tty patches including: https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b But have not applied the more recent https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0 patch. This second patch is required to prevent a rather serious regression where userspace applications reading from stdin can receive EAGAIN when they should not. I will try to link correspondence from the mailing list archives once they are available, but for now if you have access to the linux- console mailing list you can find discussion under the thread "Userspace break? read from STDIN returns EAGAIN if tty is "touched"". I would appreciate it if this could be examined soon as it is a regression on userspace. Thanks Michael Good: 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 Bad: 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+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 1816388] [NEW] FTBFS on s390x on xenial
Public bug reported: [Impact] libguestfs doesn't build on s390x architecture * Pending SRU (xenial) libguestfs s390x: Failed to build https://launchpad.net/ubuntu/+source/libguestfs/1:1.32.2-4ubuntu2.1/+build/16379018 * Build log ... checking for qemu-system-s390x... no configure: error: qemu must be installed ... [Test Case] * Build libguestfs for s390x in Launchpad (PPA) [Regression Potential] None, the package doesn't build. The fix is already in other releases. The package will no longer relies on qemu-system-misc in favor of qemu-system-s390x now. [Other informations] * git-ubuntu (libguestfs) commit 3928bd5f1458d199cd93e415c9a8081d28048500) * debdiff The following should help the build for that particular FTBFS situation (if no other build problem found after) diff -Nru libguestfs-1.32.2/debian/control libguestfs-1.32.2/debian/control --- libguestfs-1.32.2/debian/control2016-03-13 16:04:12.0 + +++ libguestfs-1.32.2/debian/control2019-02-15 14:24:56.0 + @@ -18,7 +18,7 @@ gperf, libxml2-utils, qemu-system-arm [armel armhf arm64], qemu-system-mips [mips mipsel mips64 mips64el], - qemu-system-misc [s390x], + qemu-system-s390x [s390x], qemu-system-ppc [powerpc ppc64 ppc64el], qemu-system-aarch64 [arm64], qemu-system-sparc [sparc], @@ -154,7 +154,7 @@ supermin (>= 5), qemu-system-arm [armel armhf arm64], qemu-system-mips [mips mipsel mips64 mips64el], - qemu-system-misc [s390x], + qemu-system-s390x [s390x], qemu-system-aarch64 [arm64], qemu-system-ppc [powerpc pc64 ppc64el], qemu-system-sparc [sparc], ** Affects: libguestfs (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libguestfs (Ubuntu Xenial) Importance: Medium Assignee: Ioanna Alifieraki (joalif) Status: In Progress ** Tags: sts ** Also affects: libguestfs (Ubuntu Xenial) Importance: Undecided Status: New ** Summary changed: - FTBFS on s390x + FTBFS on s390x on xenial ** Changed in: libguestfs (Ubuntu) Status: New => Fix Released ** Changed in: libguestfs (Ubuntu Xenial) Status: New => In Progress ** Changed in: libguestfs (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: libguestfs (Ubuntu Xenial) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- 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/1816388 Title: FTBFS on s390x on xenial Status in libguestfs package in Ubuntu: Fix Released Status in libguestfs source package in Xenial: In Progress Bug description: [Impact] libguestfs doesn't build on s390x architecture * Pending SRU (xenial) libguestfs s390x: Failed to build https://launchpad.net/ubuntu/+source/libguestfs/1:1.32.2-4ubuntu2.1/+build/16379018 * Build log ... checking for qemu-system-s390x... no configure: error: qemu must be installed ... [Test Case] * Build libguestfs for s390x in Launchpad (PPA) [Regression Potential] None, the package doesn't build. The fix is already in other releases. The package will no longer relies on qemu-system-misc in favor of qemu-system-s390x now. [Other informations] * git-ubuntu (libguestfs) commit 3928bd5f1458d199cd93e415c9a8081d28048500) * debdiff The following should help the build for that particular FTBFS situation (if no other build problem found after) diff -Nru libguestfs-1.32.2/debian/control libguestfs-1.32.2/debian/control --- libguestfs-1.32.2/debian/control 2016-03-13 16:04:12.0 + +++ libguestfs-1.32.2/debian/control 2019-02-15 14:24:56.0 + @@ -18,7 +18,7 @@ gperf, libxml2-utils, qemu-system-arm [armel armhf arm64], qemu-system-mips [mips mipsel mips64 mips64el], - qemu-system-misc [s390x], + qemu-system-s390x [s390x], qemu-system-ppc [powerpc ppc64 ppc64el], qemu-system-aarch64 [arm64], qemu-system-sparc [sparc], @@ -154,7 +154,7 @@ supermin (>= 5), qemu-system-arm [armel armhf arm64], qemu-system-mips [mips mipsel mips64 mips64el], - qemu-system-misc [s390x], + qemu-system-s390x [s390x], qemu-system-aarch64 [arm64], qemu-system-ppc [powerpc pc64 ppc64el], qemu-system-sparc [sparc], To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1816388/+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 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
Since the required fix is in makedumpfile, marking the linux track as invalid. ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid -- 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/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in makedumpfile source package in Xenial: New Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: In Progress Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Fix Released Bug description: == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
Required fix is to makedumpfile package therefore marking the linux track as invalid. ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid -- 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/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in makedumpfile source package in Xenial: New Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: In Progress Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Fix Released Bug description: == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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 1813059] Re: fwts 19.01.00-0ubuntu1 ADT test failure with linux 5.0.0-1.2
This bug was fixed in the package fwts - 18.03.00-0ubuntu4 --- fwts (18.03.00-0ubuntu4) bionic; urgency=medium [Colin Ian King] * efi_runtime: fix access_ok build issues on 5.0 kernels (LP: #1813059) - add Linux 5.0 compat fix to access_ok to fix dkms build issue -- Colin Ian King Thu, 24 Jan 2019 09:25:11 + ** Changed in: fwts (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: fwts (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1813059 Title: fwts 19.01.00-0ubuntu1 ADT test failure with linux 5.0.0-1.2 Status in fwts package in Ubuntu: Fix Released Status in fwts source package in Xenial: Fix Released Status in fwts source package in Bionic: Fix Released Status in fwts source package in Cosmic: Fix Released Status in fwts source package in Disco: Fix Released Bug description: == SRU Justification, Xenial, Bionic, Cosmic == The DKMS kernel module fails to build if new 5.0 kernels are used because of an API change in access_ok(). == Fix == Add a kernel version detection and a macro compat fix to paper over the API differences between the two version: +#if LINUX_VERSION_CODE >= KERNEL_VERSION(5, 0, 0) +#define ACCESS_OK(type, addr, size)access_ok(addr, size) +#else +#define ACCESS_OK(type, addr, size)access_ok(type, addr, size) +#endif and use ACCESS_OK instead of access_ok. == Regression Potential == Minimal - this build time change will select the appropriate API, so the final resultant compiled code will be identical to the original before the patch for current kernels, and only different for 5.0+ kernels. == How To test == Install fwts with a 5.0 kernel. Without the fix the dkms build of the efi driver will fail. With the fix it will succeed. -- Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/amd64/f/fwts/20190123_163310_2b561@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/arm64/f/fwts/20190123_164249_2b561@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/armhf/f/fwts/20190123_164402_2b561@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/i386/f/fwts/20190123_163518_2b561@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/ppc64el/f/fwts/20190123_163508_2b561@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1813059/+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 1816093] Re: linux-azure: 4.15.0-1039.43 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Promote to Proposed phase-changed: Friday, 15. February 2019 21:32 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + snap-release-to-beta: Pending -- snap not in beta channel + snap-release-to-edge: Pending -- snap not in edge channel + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Pending -- Ready -- 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/1816093 Title: linux-azure: 4.15.0-1039.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1813779 phase: Promote to Proposed phase-changed: Friday, 15. February 2019 21:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Pending -- Ready To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1816093/+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
