[Group.of.nepali.translators] [Bug 1720217] Re: Allow building images with kernels without initrd
This bug was fixed in the package live-build - 3.0~a57-1ubuntu31 --- live-build (3.0~a57-1ubuntu31) artful; urgency=medium * Don't fail when initramfs is not used (LP: #1720217) -- Balint Reczey Thu, 28 Sep 2017 18:01:04 + ** Changed in: live-build (Ubuntu) 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/1720217 Title: Allow building images with kernels without initrd Status in live-build package in Ubuntu: Fix Released Status in live-build source package in Xenial: Triaged Bug description: Lb may fail when creating an image with a kernel not requiring, hence initramfs-tools not building initrd. ... P: Begin installing local package lists... [2017-09-28 15:55:06] lb_binary_linux-image P: Begin install linux-image... cp: cannot stat 'chroot/boot/initrd.img-*': No such file or directory P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1720217/+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 1720217] Re: Allow building images with kernels without initrd
** Changed in: live-build (Ubuntu) Status: Confirmed => In Progress ** Also affects: live-build (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: live-build (Ubuntu Xenial) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: live-build (Ubuntu Xenial) Status: New => Triaged -- 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/1720217 Title: Allow building images with kernels without initrd Status in live-build package in Ubuntu: In Progress Status in live-build source package in Xenial: Triaged Bug description: Lb may fail when creating an image with a kernel not requiring, hence initramfs-tools not building initrd. ... P: Begin installing local package lists... [2017-09-28 15:55:06] lb_binary_linux-image P: Begin install linux-image... cp: cannot stat 'chroot/boot/initrd.img-*': No such file or directory P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree... ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1720217/+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 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install
This bug was fixed in the package python3.5 - 3.5.2-2ubuntu0~16.04.3 --- python3.5 (3.5.2-2ubuntu0~16.04.3) xenial; urgency=medium * Explicitly use the system python for byte compilation in postinst scripts. (LP: #1682934) -- Brian Murray Thu, 14 Sep 2017 15:51:06 -0700 ** Changed in: python3.5 (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/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Fix Released Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Zesty: New Status in python3.5 source package in Zesty: Fix Released Status in python3.5 package in Debian: Fix Released Bug description: [Impact] An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5. [Test Case] 1) Ensure the version of python3.5 from the release pocket is installed 2) Install python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ 3) Confirm that python3.5 from /usr/local/bin/ is being used / the default 4) Upgrade to a newer version of python3.5 from -proposed Observe the following Traceback: Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: python3.5-minimal python3-minimal With the version of python3.5 from -proposed this Traceback will not be encountered. [Regression Potential] It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg. [Original Description] Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+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 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install
This bug was fixed in the package python3.5 - 3.5.3-1ubuntu0~17.04.1 --- python3.5 (3.5.3-1ubuntu0~17.04.1) zesty; urgency=medium * Explicitly use the system python for byte compilation in postinst scripts. (LP: #1682934) -- Brian Murray Thu, 14 Sep 2017 15:58:41 -0700 ** Changed in: python3.5 (Ubuntu Zesty) 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/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Fix Released Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Zesty: New Status in python3.5 source package in Zesty: Fix Released Status in python3.5 package in Debian: Fix Released Bug description: [Impact] An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5. [Test Case] 1) Ensure the version of python3.5 from the release pocket is installed 2) Install python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ 3) Confirm that python3.5 from /usr/local/bin/ is being used / the default 4) Upgrade to a newer version of python3.5 from -proposed Observe the following Traceback: Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: python3.5-minimal python3-minimal With the version of python3.5 from -proposed this Traceback will not be encountered. [Regression Potential] It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg. [Original Description] Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+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 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.4.0-1037.46 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: 1716613 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase:Promoted to updates + kernel-stable-phase-changed:Thursday, 28. September 2017 21:03 UTC ** Description changed: This bug is for tracking the 4.4.0-1037.46 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: 1716613 - phase: Promoted to proposed + phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase:Promoted to updates - kernel-stable-phase-changed:Thursday, 28. September 2017 21:03 UTC -- 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/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-1037.46 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: 1716613 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+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 1715725] Re: linux-aws needs drbd.ko
This bug was fixed in the package linux-aws - 4.4.0-1037.46 --- linux-aws (4.4.0-1037.46) xenial; urgency=low * linux-aws: 4.4.0-1037.46 -proposed tracker (LP: #1719970) * linux-aws needs drbd.ko (LP: #1715725) - [config] AWS: drbd.ko moved to linux-image package -- Thadeu Lima de Souza Cascardo Wed, 27 Sep 2017 15:01:24 -0300 ** Changed in: linux-aws (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/1715725 Title: linux-aws needs drbd.ko Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Xenial: Fix Released Bug description: Please distribute drbd.ko in main linux-image package. [Impact] * This kernel module was inadvertently omitted from linux-aws; requested to be enabled as it is in standard Ubuntu GA kernels. [Test Case] * 'sudo modprobe drbd' fails without it. To test, verify that command returns with no error. (Alternately, verify 'modinfo drbd' describes the module without error). [Regression Potential] * Very low potential for regression: This just makes the module available where it wasn't before, but changes no other functionality. The same module is already included in standard Ubuntu GA kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1715725/+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 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
This bug was fixed in the package linux-aws - 4.4.0-1037.46 --- linux-aws (4.4.0-1037.46) xenial; urgency=low * linux-aws: 4.4.0-1037.46 -proposed tracker (LP: #1719970) * linux-aws needs drbd.ko (LP: #1715725) - [config] AWS: drbd.ko moved to linux-image package -- Thadeu Lima de Souza Cascardo Wed, 27 Sep 2017 15:01:24 -0300 ** Changed in: linux-aws (Ubuntu Xenial) Status: Confirmed => 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/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-1037.46 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: 1716613 phase: Promoted to updates proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+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 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
** Tags added: regression-testing-passed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed -- 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/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-1037.46 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: 1716613 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+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 1719970] Re: linux-aws: 4.4.0-1037.46 -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 ** Description changed: This bug is for tracking the 4.4.0-1037.46 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: 1716613 + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 28. September 2017 20:43 UTC ** Description changed: This bug is for tracking the 4.4.0-1037.46 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: 1716613 - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 28. September 2017 20:43 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-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-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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 4.4.0-1037.46 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: 1716613 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+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 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the 4.4.0-1038.47 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 -- kernel-stable-master-bug: 1718149 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 28. September 2017 20:33 UTC ** Description changed: This bug is for tracking the 4.4.0-1038.47 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 -- kernel-stable-master-bug: 1718149 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 28. September 2017 20:33 UTC + phase: Uploaded -- 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/1720042 Title: linux-aws: 4.4.0-1038.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.4.0-1038.47 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 -- kernel-stable-master-bug: 1718149 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1720042/+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 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing 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/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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 4.4.0-1037.46 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: 1716613 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+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 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
Fix has been verified. ** Changed in: kernel-sru-workflow/verification-testing Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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 4.4.0-1037.46 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: 1716613 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+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 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)
** Changed in: ubuntu-power-systems 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/1696102 Title: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in xfsprogs package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in xfsprogs source package in Xenial: Fix Released Status in linux source package in Zesty: Invalid Status in xfsprogs source package in Zesty: Fix Released Bug description: Impact == When making multiple copies of a V5 filesystem with xfs_copy those copies will be corrupt due to incorrect UUIDs. Test Case = See the detailed steps to create the test environment in comment #20. Regression Potential From the patch "Most of this patch is changing comments and re-ordering tests to match; the functional change is to simply use the *sb rather than the *ag_hdr to identify the proper metadata UUID." So this seems pretty straightforward and given that copy process is currently broken, because the copies are corrupt, this will be an improvement. Original Description Problem Description xfs/073 test fails with Metadata corruption detected on xfs file system. Test fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is inconsistent. # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530 +++ /root/xfstests-dev/results//xfs/073.out.bad 2017-03-27 11:11:43.023059702 +0530 @@ -59,8 +59,7 @@ comparing new image geometry to old unmounting and removing new image checking new image -mounting new image on loopback -comparing new image files to old -comparing new image directories to old -comparing new image geometry to old -unmounting and removing new image +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (c) +(see /root/xfstests-dev/results//xfs/073.full for details) +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (r) +(see /root/xfstests-dev/results//xfs/073.full for details) Metadata corruption detected at xfs_agf block 0x1/0x200 # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.conf for running with created loop device 5.. Run xfstests-dev test : ./check tests/xfs/073 Full log is attached. == Comment: #2 - Harish Sriram - 2017-05-31 01:22:11 == (In reply to comment #1) > Hi Harish, > Can you share the steps used in creating the loop device with xfs filesystem > ? > > Thank you. Create loop device: # mkdir /mnt/loop-device /mnt/test /mnt/scratch # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB /mnt/loop-device/file-$i.img; done # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; done Create File system: # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done # cat local.config export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export SCRATCH_DEV=/dev/loop1 export SCRATCH_MNT=/mnt/scratch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+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 1696102] Re: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs)
This bug was fixed in the package xfsprogs - 4.3.0+nmu1ubuntu4.1 --- xfsprogs (4.3.0+nmu1ubuntu4.1) zesty; urgency=medium * xfs_copy: Fix meta UUID handling on multiple copies upstream fix cbca895541facb. (LP: #1696102) -- Brian Murray Tue, 29 Aug 2017 10:16:48 -0700 ** Changed in: xfsprogs (Ubuntu Zesty) 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/1696102 Title: xfs/073 test fails with Metadata corruption detected on xfs file system (xfsprogs) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Invalid Status in xfsprogs package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in xfsprogs source package in Xenial: Fix Released Status in linux source package in Zesty: Invalid Status in xfsprogs source package in Zesty: Fix Released Bug description: Impact == When making multiple copies of a V5 filesystem with xfs_copy those copies will be corrupt due to incorrect UUIDs. Test Case = See the detailed steps to create the test environment in comment #20. Regression Potential From the patch "Most of this patch is changing comments and re-ordering tests to match; the functional change is to simply use the *sb rather than the *ag_hdr to identify the proper metadata UUID." So this seems pretty straightforward and given that copy process is currently broken, because the copies are corrupt, this will be an improvement. Original Description Problem Description xfs/073 test fails with Metadata corruption detected on xfs file system. Test fails with _check_xfs_filesystem: filesystem on /mnt/test/84004.image2 is inconsistent. # diff -u tests/xfs/073.out /root/xfstests-dev/results//xfs/073.out.bad --- tests/xfs/073.out 2017-03-23 12:13:05.288877197 +0530 +++ /root/xfstests-dev/results//xfs/073.out.bad 2017-03-27 11:11:43.023059702 +0530 @@ -59,8 +59,7 @@ comparing new image geometry to old unmounting and removing new image checking new image -mounting new image on loopback -comparing new image files to old -comparing new image directories to old -comparing new image geometry to old -unmounting and removing new image +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (c) +(see /root/xfstests-dev/results//xfs/073.full for details) +_check_xfs_filesystem: filesystem on /mnt/test/15413.image2 is inconsistent (r) +(see /root/xfstests-dev/results//xfs/073.full for details) Metadata corruption detected at xfs_agf block 0x1/0x200 # uname -a Linux ltc-tuleta12 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Steps to reproduce: 1. Create a loop device with xfs filesystem 2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd xfstests-dev 3. make 4. Create a local.conf for running with created loop device 5.. Run xfstests-dev test : ./check tests/xfs/073 Full log is attached. == Comment: #2 - Harish Sriram - 2017-05-31 01:22:11 == (In reply to comment #1) > Hi Harish, > Can you share the steps used in creating the loop device with xfs filesystem > ? > > Thank you. Create loop device: # mkdir /mnt/loop-device /mnt/test /mnt/scratch # for i in $(seq 0 1); do fallocate -o 0 -l 5GiB /mnt/loop-device/file-$i.img; done # for i in $(seq 0 1); do losetup /dev/loop$i /mnt/loop-device/file-$i.img; done Create File system: # for i in $(seq 0 1); do mkfs.ext4 -F /dev/loop$i; done # cat local.config export TEST_DEV=/dev/loop0 export TEST_DIR=/mnt/test export SCRATCH_DEV=/dev/loop1 export SCRATCH_MNT=/mnt/scratch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696102/+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 1707610] Re: fanctl does not stop setup on first match
This bug was fixed in the package ubuntu-fan - 0.12.4~17.04.1 --- ubuntu-fan (0.12.4~17.04.1) zesty; urgency=medium [ Andy Whitcroft ] * fanctl: only bring up enabled Fan Networks in --auto mode (LP: #1707610) * fanctl: correctly specify local interface specific config (LP: #1707610) * fanatic: recast advanced commands as non-interactive (LP: #1714966) * fanatic: fix spelling in primary help (LP: #1714966) * fanatic: fix references to fanatic manual page (LP: #1714966) [ Stefan Bader ] * fanatic: Fix typo in progress output (LP: #1714966) * README: Refresh documentation (LP: #1714966) * fanctl.8: Refresh documentation (LP: #1714966) * fanatic.8: Refresh documentation (LP: #1714966) * fanatic.8: Reword advanced to non-interactive usage (LP: #1714966) * DEP8: lxd: Suppress stderr on profile list (LP: #1714969) -- Stefan Bader Fri, 18 Aug 2017 14:34:47 +0200 ** Changed in: ubuntu-fan (Ubuntu Zesty) 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/1707610 Title: fanctl does not stop setup on first match Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Triaged Status in ubuntu-fan source package in Zesty: Fix Released Bug description: SRU Justification (Zesty/Xenial) Impact: When /etc/network/fan contains two entries for the same mapping (for example on mapping for the generic network mapping and one for a specific interface) it will try to set up the same Fan bridge twice. Fix: Modify fanctl to only bring up enabled networks in auto mode and to correctly apply the most specific local configuration. Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, and host has for example a 192.168.1.0/24 address. Then trying to use fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8 would show an error now and with the fix applied work ok. Regression Potential: We tested both cases of using an underlay/overlay combination which is in the template section and one that was using a subset for the underlay. The former was working before the latter not. For that reason we anticipate a low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+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 1713059] Re: drop db sync commands from OpenStack packages
This bug was fixed in the package nova - 2:15.0.6-0ubuntu1.1 --- nova (2:15.0.6-0ubuntu1.1) zesty; urgency=medium * d/nova-common.postinst: Don't sync database if connection is not defined in /etc/nova/nova.conf (LP: #1713059). -- Felipe Reyes Tue, 29 Aug 2017 15:40:07 -0300 ** Changed in: nova (Ubuntu Zesty) 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/1713059 Title: drop db sync commands from OpenStack packages Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Committed Status in Ubuntu Cloud Archive newton series: Fix Committed Status in Ubuntu Cloud Archive ocata series: Fix Committed Status in Ubuntu Cloud Archive pike series: Fix Released Status in aodh package in Ubuntu: Fix Released Status in ceilometer package in Ubuntu: Fix Released Status in cinder package in Ubuntu: Fix Released Status in glance package in Ubuntu: Fix Released Status in ironic package in Ubuntu: Fix Released Status in keystone package in Ubuntu: Fix Released Status in manila package in Ubuntu: Fix Released Status in nova package in Ubuntu: Fix Released Status in openstack-trove package in Ubuntu: Fix Released Status in panko package in Ubuntu: Fix Released Status in aodh source package in Xenial: Invalid Status in ceilometer source package in Xenial: Invalid Status in cinder source package in Xenial: Invalid Status in glance source package in Xenial: Invalid Status in ironic source package in Xenial: Invalid Status in keystone source package in Xenial: Invalid Status in manila source package in Xenial: Invalid Status in nova source package in Xenial: Fix Committed Status in openstack-trove source package in Xenial: Invalid Status in panko source package in Xenial: Invalid Status in aodh source package in Zesty: Invalid Status in ceilometer source package in Zesty: Invalid Status in cinder source package in Zesty: Invalid Status in glance source package in Zesty: Invalid Status in ironic source package in Zesty: Invalid Status in keystone source package in Zesty: Invalid Status in manila source package in Zesty: Invalid Status in nova source package in Zesty: Fix Released Status in openstack-trove source package in Zesty: Invalid Status in panko source package in Zesty: Invalid Status in aodh source package in Artful: Fix Released Status in ceilometer source package in Artful: Fix Released Status in cinder source package in Artful: Fix Released Status in glance source package in Artful: Fix Released Status in ironic source package in Artful: Fix Released Status in keystone source package in Artful: Fix Released Status in manila source package in Artful: Fix Released Status in nova source package in Artful: Fix Released Status in openstack-trove source package in Artful: Fix Released Status in panko source package in Artful: Fix Released Bug description: [Impact] nova-compute service does not need access to the database, systems where nova.conf is configured without a database connection the nova- common package will fail to get configured [Test Case] Using this deployer bundle -> http://paste.ubuntu.com/25426891/ juju-deployer -c bundle.yaml -d -v -s 10 xenial-mitaka # once everything is installed git clone https://github.com/openstack-charmers/openstack-charms-tools.git cd openstack-charms-tools/ ./os-upgrade.py -o cloud:xenial-newton Expected result: nova-compute units upgrade their packages to newton without errors Actual result: nova-common fails to configure itself in the nova-compute units [Regression Potential] This change was tested in a staging environment and no regressions were detected, but any possible regression will express itself as a failure running "nova-manage db sync". [Other Info] The original reason this bug was opened is that nova db sync is executed when the 'connection' is not defined. Let's fix that and at the same time drop all db syncs from OpenStack packages in Pike. More on the nova issue: When the 'connection' configuration key is NOT defined in /etc/nova/nova.conf the nova-common.postinst script still tries to run 'nova-manage db sync' root@juju-b24bc9-mno-18:~# grep connection /etc/nova/nova.conf root@juju-b24bc9-mno-18:~# dpkg-reconfigure nova-common Option "logdir" from group "DEFAULT" is deprecated. Use option "log-dir" from group "DEFAULT". Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future. ERROR: could not access cell mapping database - has api db been created? An error has occurred: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/nova/cmd/manage.py", line 1
[Group.of.nepali.translators] [Bug 1714966] Re: Backport documentation and help text rework
This bug was fixed in the package ubuntu-fan - 0.12.4~17.04.1 --- ubuntu-fan (0.12.4~17.04.1) zesty; urgency=medium [ Andy Whitcroft ] * fanctl: only bring up enabled Fan Networks in --auto mode (LP: #1707610) * fanctl: correctly specify local interface specific config (LP: #1707610) * fanatic: recast advanced commands as non-interactive (LP: #1714966) * fanatic: fix spelling in primary help (LP: #1714966) * fanatic: fix references to fanatic manual page (LP: #1714966) [ Stefan Bader ] * fanatic: Fix typo in progress output (LP: #1714966) * README: Refresh documentation (LP: #1714966) * fanctl.8: Refresh documentation (LP: #1714966) * fanatic.8: Refresh documentation (LP: #1714966) * fanatic.8: Reword advanced to non-interactive usage (LP: #1714966) * DEP8: lxd: Suppress stderr on profile list (LP: #1714969) -- Stefan Bader Fri, 18 Aug 2017 14:34:47 +0200 ** Changed in: ubuntu-fan (Ubuntu Zesty) 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/1714966 Title: Backport documentation and help text rework Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: Fix Released Bug description: SRU justification: Impact: After substantially enhancing all of the documentation (README and man pages) as well as the output of built-in help of fanatic, we should backport those changes to Zesty and Xenial. Fixes: * fanatic: recast advanced commands as non-interactive * fanatic: fix spelling in primary help * fanatic: fix references to fanatic manual page * fanatic: Fix typo in progress output * README: Refresh documentation * fanctl.8: Refresh documentation * fanatic.8: Refresh documentation * fanatic.8: Reword advanced to non-interactive usage Test case: Since all changes affect only documentation, there is no test case. Regression risk: Very low (documentation only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714966/+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 1714969] Re: Backport remaining delta
This bug was fixed in the package ubuntu-fan - 0.12.4~17.04.1 --- ubuntu-fan (0.12.4~17.04.1) zesty; urgency=medium [ Andy Whitcroft ] * fanctl: only bring up enabled Fan Networks in --auto mode (LP: #1707610) * fanctl: correctly specify local interface specific config (LP: #1707610) * fanatic: recast advanced commands as non-interactive (LP: #1714966) * fanatic: fix spelling in primary help (LP: #1714966) * fanatic: fix references to fanatic manual page (LP: #1714966) [ Stefan Bader ] * fanatic: Fix typo in progress output (LP: #1714966) * README: Refresh documentation (LP: #1714966) * fanctl.8: Refresh documentation (LP: #1714966) * fanatic.8: Refresh documentation (LP: #1714966) * fanatic.8: Reword advanced to non-interactive usage (LP: #1714966) * DEP8: lxd: Suppress stderr on profile list (LP: #1714969) -- Stefan Bader Fri, 18 Aug 2017 14:34:47 +0200 ** Changed in: ubuntu-fan (Ubuntu Zesty) 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/1714969 Title: Backport remaining delta Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: In Progress Status in ubuntu-fan source package in Zesty: Fix Released Bug description: SRU Justification: Impact: In order to lower maintenance burden we want to use the same code base of ubuntu-fan throughout all releases. Most of the code already is the same. The remaining delta could be split into two classes: documentation (for which there is a separate bug report and changes to build in and/or DEP8 testing (which this report is about). Fixes: [ Xenial SRU only] * debian/control: fix use of obsolete > operator This only changes a package dependency. Not affecting use. * fanatic: fix local testing and improve docker test This fixes up the built-in test for docker and improves it (check for container start failure, potential clean up before start). Executed as part of DEP8 testing. * fanatic: Support nc -N option Strictly only needed in Artful but since the code was written to check for the new option and only use it if present, there is no visible change in previous releases. Covered by DEP8, too. * fanatic: Prevent error message without docker installed Without docker installed there is a message to stderr when disabling fan. This broke the LXD dep8 test. So again, verified by DEP8 as the LXD part gets added. * fanatic: Supply LXD storage if needed At some point the lxd-client started to require providing --storage when creating containers. The LXD dep8 test would break then. Fix checks for option being available and conditionally provides it. Again covered by DEP8 testing. * dep8: Add LXD auto-test Adds DEP8 testing for LXD (currently Xenial only tests docker). [ Xenial and Zesty SRU ] * DEP8: lxd: Suppress stderr on profile list(*) Strictly only needed in Xenial but we want to make the code the same. In Xenial doing a lxc profile list is/was printing a hint about init to stderr even when lxd init was already done. This broke the LXD DEP8 test in Xenial. The fix is to ignore stderr for that call which again is verified by DEP8 passing. Test case: As stated for the individual fixes all the changes will be verified by the DEP8 tests passing. The only exception is the packaging fix and that has no impact on usage at all. Regression Risk: Since all is covered by DEP8, and only modifies tests, the overall risk of regression for normal operation should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714969/+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 1713979] Re: New upstream microreleases 9.3.19, 9.5.9 and 9.6.5
This bug was fixed in the package postgresql-9.5 - 9.5.9-0ubuntu0.16.04 --- postgresql-9.5 (9.5.9-0ubuntu0.16.04) xenial; urgency=medium * New upstream release (LP: #1713979) - fix upgrade regressions of the former security release - Details about other changes at full changelog: https://www.postgresql.org/docs/9.5/static/release-9-5-9.html -- Christian Ehrhardt Wed, 30 Aug 2017 13:01:13 +0200 ** Changed in: postgresql-9.5 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: postgresql-9.3 (Ubuntu Trusty) 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/1713979 Title: New upstream microreleases 9.3.19, 9.5.9 and 9.6.5 Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Invalid Status in postgresql-9.6 package in Ubuntu: Fix Released Status in postgresql-9.3 source package in Trusty: Fix Released Status in postgresql-9.5 source package in Xenial: Fix Released Status in postgresql-9.6 source package in Zesty: Fix Released Status in postgresql-9.6 source package in Artful: Fix Released Bug description: Update to the new set of releases as per the standing micro-release exception these should land in stable Ubuntu releases. Curren versions in releases: postgresql-9.3 | 9.3.18-0ubuntu0.14.04.1 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el postgresql-9.5 | 9.5.8-0ubuntu0.16.04.1 | xenial-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x postgresql-9.6 | 9.6.4-0ubuntu0.17.04.1 | zesty-security | source, amd64, arm64, armhf, i386, ppc64el, s390x postgresql-9.6 | 9.6.4-1| artful | source, amd64, arm64, armhf, i386, ppc64el, s390x This was a double bump within 2 weeks. As the last had upgrade regressions. But the Security Team already did the Bump on the latest so we effectively have the potential upgrade regression in the field and need to bump again. Last stable updates PostgreSQL 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23 So the todo is to pick: MRE: Trusty 9.3.19 from https://www.postgresql.org/ftp/source/v9.3.19/ MRE: Xenial 9.5.9 from https://www.postgresql.org/ftp/source/v9.5.9/ MRE: Zesty 9.6.5 from https://www.postgresql.org/ftp/source/v9.6.5/ Sync: Artful 9.6.5 from https://www.postgresql.org/ftp/source/v9.6.5/ Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.3/+bug/1713979/+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 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.8 --- unattended-upgrades (0.90ubuntu0.8) xenial; urgency=medium * Do not mark packages for deletion / autoremoval if unattended-upgrades is being run in dry-run mode. (LP: #1544942) -- Brian Murray Mon, 18 Sep 2017 13:36:57 -0700 ** Changed in: unattended-upgrades (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/1544942 Title: Marks unneeded packages as manually installed, if --dry-run is used Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: marking linux-headers-4.2.0-16-generic for remove marking linux-headers-4.2.0-16 for remove marking linux-image-4.2.0-16-generic for remove marking linux-image-extra-4.2.0-16-generic for remove Packages that are auto removed: 'linux-headers-4.2.0-16-generic linux-headers-4.2.0-16 linux-image-4.2.0-16-generic linux-image-extra-4.2.0-16-generic' /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64 /usr/bin/dpkg --status-fd 11 --configure --pending Packages were successfully auto-removed InstCount=0 DelCount=4 BrokenCount=0 $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux- headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux- image-4.2.0-16-generic:amd64 $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals Expect the packages to remain automatically installed after each `sudo unattended-upgrade --dry-run -d`. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unattended-upgrades 0.86.2ubuntu1.1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 12 13:58:29 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-24 (18 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2016-02-12T13:53:13.426454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1544942/+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 1706284] Re: sssd fails to Update PTR if any A record update fails.
This bug was fixed in the package sssd - 1.13.4-1ubuntu1.8 --- sssd (1.13.4-1ubuntu1.8) xenial; urgency=medium * d/p/attempt_ptr_update_on_nonzero_return.diff: Continue to send the PTR record update in situations where the nsupdate child forward zone updates are successful but nsupdate returns non-zero. (LP: #1706284) -- Keith Ward Tue, 25 Jul 2017 11:16:18 +0100 ** Changed in: sssd (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/1706284 Title: sssd fails to Update PTR if any A record update fails. Status in sssd package in Ubuntu: Fix Released Status in sssd source package in Xenial: Fix Released Bug description: sssd in both xenial and yakkety fails to update the PTR record of the current host on an active directory controller if any update for an A/AAA record returns a non-fatal error, this results in missing (and/or) mismatched Reverse DNS. This has already been fixed in 1.5.1 (which is present in Zesty and above), as failure to update any of the A/AAA should not affect updating the PTR as well, as not all servers in a given AD cluster may accept an A/AAA record update, especially if it would result in no update being made (NOERROR). See the attached conversation about this issue here: https://pagure.io/SSSD/sssd/issue/3227 for further information. I'll attach a debdiff against the relevant releases shortly, however for now I've attached the original patch which was used to fix the bug in 1.15.1 ### SRU Justification ### [Impact] Currently users find that sssd will not update the reverse (PTR) records of a given host if an AD server returns non-fatal error for an A/AAA update. This causes strange issues to occur where we can end up with hosts with proper functioning forward records but no reverse. I propose we backport the fix from 1.15.1 to both Xenial and Yakkety to resolve the issue so PTR updates get processed (or at least attempted). The patch attached removes the error check that occurs should the return code of the A/AAA nsupdates be non zero, and instead allows the PTR update to occur before checking for errors. This is the same patch taken from the fix for 1.15.1 [Test Case] For the configuration of sssd, a basic configuration of the following should suffice: [sssd] services = nss, pam config_file_version = 2 domains = YOURDOMAIN.TLD [domain/YOURDOMAIN.TLD] id_provider=ad auth_provider=ad access_provider=ad chpass_provider=ad override_homedir=/home/%d/%u cache_credentials = true ad_gpo_access_control=permissive default_shell=/bin/bash ad_hostname = sssd-hostname.YOURDOMAIN.TLD In AD change the properties of the Forward zone Dynamic Updates to "Nonsecure and Secure" Ensure a Reverse Zone is present in the AD DNS MMC. Remove any existing A/ and PTR records from Active Directory DNS for the SSSD system Restart SSSD to trigger the nsupdate call Check the reverse zone in AD for PTR records, they do not get created but the A/ records do. Expected results: Both A and PTR records get updated. [Regression Potential] As this patch is already present in a future release it has been fairly well tested already however back-porting the fix will result in sssd attempting PTR updates whether the A/AAA updates succeeds or not. As per the original bug report where a quick note was made about failed updates; If forward updates fail the result will be inconsistent DNS should the reverse succeed (reverse but no forward), however in that case the admin needs to look into with why the update failed, the code should at least try to record all updates (both A, AAA and PTR) and not just ignore the PTR because the forward update (may or may not have) failed. There is also the possibility that the patch may not resolve the problem completely however as this patch just moves the error handling before the PTR attempt I can see no reason not to backport the patch to the older version for Xenial/Yakkety. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1706284/+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 1713979] Re: New upstream microreleases 9.3.19, 9.5.9 and 9.6.5
This bug was fixed in the package postgresql-9.6 - 9.6.5-0ubuntu0.17.04 --- postgresql-9.6 (9.6.5-0ubuntu0.17.04) zesty; urgency=medium * New upstream release (LP: #1713979) - fix upgrade regressions of the former security release - Details about other changes at full changelog: https://www.postgresql.org/docs/9.6/static/release-9-6-5.html -- Christian Ehrhardt Wed, 30 Aug 2017 13:01:24 +0200 ** Changed in: postgresql-9.6 (Ubuntu Zesty) 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/1713979 Title: New upstream microreleases 9.3.19, 9.5.9 and 9.6.5 Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Invalid Status in postgresql-9.6 package in Ubuntu: Fix Released Status in postgresql-9.3 source package in Trusty: Fix Committed Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.6 source package in Zesty: Fix Released Status in postgresql-9.6 source package in Artful: Fix Released Bug description: Update to the new set of releases as per the standing micro-release exception these should land in stable Ubuntu releases. Curren versions in releases: postgresql-9.3 | 9.3.18-0ubuntu0.14.04.1 | trusty-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el postgresql-9.5 | 9.5.8-0ubuntu0.16.04.1 | xenial-security | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x postgresql-9.6 | 9.6.4-0ubuntu0.17.04.1 | zesty-security | source, amd64, arm64, armhf, i386, ppc64el, s390x postgresql-9.6 | 9.6.4-1| artful | source, amd64, arm64, armhf, i386, ppc64el, s390x This was a double bump within 2 weeks. As the last had upgrade regressions. But the Security Team already did the Bump on the latest so we effectively have the potential upgrade regression in the field and need to bump again. Last stable updates PostgreSQL 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23 So the todo is to pick: MRE: Trusty 9.3.19 from https://www.postgresql.org/ftp/source/v9.3.19/ MRE: Xenial 9.5.9 from https://www.postgresql.org/ftp/source/v9.5.9/ MRE: Zesty 9.6.5 from https://www.postgresql.org/ftp/source/v9.6.5/ Sync: Artful 9.6.5 from https://www.postgresql.org/ftp/source/v9.6.5/ Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.3/+bug/1713979/+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 1610168] Re: error: 'basic_string<_CharT, _Traits, _Allocator>' is missing exception specification
This bug was fixed in the package libc++ - 3.7.0-1ubuntu0.1 --- libc++ (3.7.0-1ubuntu0.1) xenial; urgency=medium * Fix error int the string header in c++11 mode (LP: #1610168). -- Sergey Vidyuk Sat, 24 Jun 2017 18:09:34 +0700 ** Changed in: libc++ (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/1610168 Title: error: 'basic_string<_CharT, _Traits, _Allocator>' is missing exception specification Status in libc++ package in Ubuntu: Fix Released Status in libc++ source package in Xenial: Fix Released Status in libc++ package in Debian: Fix Released Bug description: This is mirroring Debian bug #808086 https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=808086 Compiling any source file that includes with clang 3.8 and -std=c++11 -stdlib=libc++ results in a compile error. While this is a minor bug in Debian (as it doesn't ship 3.8 yet), xenial does, and that's a major problem as it makes libc++ useless. clang: warning: argument unused during compilation: '-stdlib=libc++' In file included from test.cpp:1: In file included from /usr/include/c++/v1/iostream:38: In file included from /usr/include/c++/v1/ios:216: In file included from /usr/include/c++/v1/__locale:15: /usr/include/c++/v1/string:1938:44: error: 'basic_string<_CharT, _Traits, _Allocator>' is missing exception specification 'noexcept(is_nothrow_copy_constructible::value)' basic_string<_CharT, _Traits, _Allocator>::basic_string(const allocator_type& __a) ^ /usr/include/c++/v1/string:1326:76: note: previous declaration is here __attribute__ ((__visibility__("hidden"), __always_inline__)) explicit basic_string(const allocator_type& __a) ^ 1 error generated. -- Update (30 Aug 2017): as per https://wiki.ubuntu.com/StableReleaseUpdates : [Impact] This bug makes it impossible to compile any C++11 source file that includes with clang 3.8 using libc++. Any non-trivial C++11 codebase is affected, making the whole libc++ package useless. [Test Case] See above. Create a C++ file that simply contains #include and compile it with clang++ -std=c++11 -stdlib=libc++ file.cpp. [Regression Potential] The current header simply does not work with clang-3.8 under any condition, so there is no regression potential. The regression potential for GCC is also extremely limited: no package whatsoever uses GCC in combination with libc++, and the fact that GCC 5.4 -- currently in Xenial -- does not detect the error that Clang detects is just showing that GCC is bugged in this regard. [Other Info] The patch/workaround fixes the problem. See also the discussion at the linked Debian bug report as well as https://stackoverflow.com/q/37096062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libc++/+bug/1610168/+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 1716818] Re: Remove obsolete versioned dependency on initramfs-tools
This bug was fixed in the package mdadm - 3.3-2ubuntu7.4 --- mdadm (3.3-2ubuntu7.4) xenial; urgency=medium * Drop versioned dependency on initramfs-tools, which was only needed for upgrades and now keeps initramfs-tools installed on systems that don't need it. LP: #1716818. * Guard calls to update-initramfs -u in the maintainer scripts for a check that the script is present. -- Steve Langasek Wed, 13 Sep 2017 03:52:18 + ** Changed in: mdadm (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/1716818 Title: Remove obsolete versioned dependency on initramfs-tools Status in mdadm package in Ubuntu: Fix Released Status in mdadm source package in Xenial: Fix Released Bug description: [SRU Justification] In xenial and earlier, mdadm declares a versioned dependency on initramfs-tools. This was an Ubuntu-specific dependency only needed for upgrades, and the version referenced is ancient (ca. 2008). In zesty and later, the dependency has been removed. Since this is no longer relevant for upgrades and we would not otherwise have a dependency on initramfs-tools, we should drop this dependency to support building of images with initramfs-tools removed for systems that we know don't require an initramfs. [Test case] 1. On a xenial default cloud image install, try to run 'sudo apt purge initramfs-tools'. 2. Verify that this tries to remove mdadm. 3. Cancel the removal. 4. Install mdadm from xenial-proposed. 5. Run 'sudo apt purge initramfs-tools' again. 6. Verify that mdadm is not removed. 7. Run 'sudo apt install --reinstall mdadm' and confirm that the package can be installed successfully without initramfs-tools installed. [Regression Potential] If a user needs an initramfs in order to mount their root device (whether or not it's on RAID), and mdadm is the only package on their system which depends on initramfs-tools, it is possible that the user may remove initramfs-tools and render their system unbootable. This is unlikely because initramfs-tools is still part of the 'minimal' seed and is therefore a dependency of ubuntu-minimal; and it remains a dependency of the generic kernel image. So long as initramfs-tools is installed, mdadm's initramfs hooks will continue to function as intended when required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1716818/+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 1718155] Re: linux-aws: 4.4.0-1036.45 -proposed tracker
*** This bug is a duplicate of bug 1719970 *** https://bugs.launchpad.net/bugs/1719970 ** This bug is no longer a duplicate of bug 1720042 linux-aws: 4.4.0-1038.47 -proposed tracker ** This bug has been marked a duplicate of bug 1719970 linux-aws: 4.4.0-1037.46 -proposed tracker -- 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/1718155 Title: linux-aws: 4.4.0-1036.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1718149 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718155/+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 1349941] Re: qemu-ppc segfault on simple hello world
Hi, nothing happened since then. I was trying to reproduce but it seems (to me) down to none of us knowing how to correctly resolve libraries. So before here people reported: - static builds work - dynamic builds fail for some with ld.so failing and crashing for others - dynamic builds fail To resolve this a bit one has to follow [1] which also needs [2]. Once you did that the issue of the missing ld.so (of the target arch) is resolved. Doing that I can re-create the issue - even on xenial still with a much newer qemu. I can also confirm that doing the same e.g. with armhf is working - so it must be ppc specific. Given the fact that this is a super rare case to need it and OTOH powerpc is mostly dropped in more recent releases this is still a low prio issue. So even if it is low prio for me, I hope the links help if a community member wants to get onto this. to not let this bug hang-on for another few years I'll mark the tasks incomplete to see if one is still caring and might have a suggestion. If for quite long again nobody volunteers to help or has a suggestion we might end up closing it. Sorry but better honest than faking activity here :-/ [1]: https://wiki.debian.org/QemuUserEmulation [2]: https://wiki.debian.org/Multiarch/HOWTO#Setting_up_apt_sources ** Also affects: qemu (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Xenial) Status: New => Incomplete ** Changed in: qemu (Ubuntu Trusty) Status: Confirmed => Incomplete ** Changed in: qemu (Ubuntu) Status: Fix Released => 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/1349941 Title: qemu-ppc segfault on simple hello world Status in qemu package in Ubuntu: Won't Fix Status in qemu source package in Trusty: Incomplete Status in qemu source package in Xenial: Incomplete Bug description: qemu ppc fails to execute even a simple hello world app. jruble@jruble-linux:~/ppc_qemu_test$ cat test.c #include int main(){ printf("asdf\n"); return 0; } jruble@jruble-linux:~/ppc_qemu_test$ powerpc-linux-gnu-gcc --version powerpc-linux-gnu-gcc (Ubuntu 4.8.2-16ubuntu3) 4.8.2 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. jruble@jruble-linux:~/ppc_qemu_test$ powerpc-linux-gnu-gcc test.c jruble@jruble-linux:~/ppc_qemu_test$ file a.out a.out: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=714f9cfad9e06d0478bcd238ccbcbd10468741fc, not stripped jruble@jruble-linux:~/ppc_qemu_test$ qemu-ppc -version qemu-ppc version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.1), Copyright (c) 2003-2008 Fabrice Bellard jruble@jruble-linux:~/ppc_qemu_test$ qemu-ppc ./a.out Invalid data memory access: 0xfa98c008 NIP f67e2b9c LR f67e2c40 CTR XER MSR 6040 HID0 HF 6000 idx 0 TB GPR00 f67e2c1c f6ffe720 feb6c010 GPR04 f67ec784 000b 0002 GPR08 0030 083c0010 f67ac00a 80808080 GPR12 f67dcfc8 f67fe8c4 GPR16 f67fe900 f6ffe998 f6ffe99c f67feaf0 GPR20 f67fd6c4 000a feb6c010 f67fd320 GPR24 fa98bff4 f7c5ef8d 11f9 041dfff4 GPR28 f67fe900 5604 f67fdff4 2b027fff CR 44284042 [ G G E L G - G E ] RES FPR00 FPR04 FPR08 FPR12 FPR16 FPR20 FPR24 FPR28 FPSCR qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped) jruble@jruble-linux:~/ppc_qemu_test$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-user 2.0.0+dfsg-2ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 2
[Group.of.nepali.translators] [Bug 1595242] Re: mongodb xenial s390x packages are needed (blocks ceilometer)
Seems in artful mongodb | 1:3.4.7-1 | artful/universe | source, amd64, arm64, ppc64el, s390x ** Changed in: mongodb (Ubuntu) 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/1595242 Title: mongodb xenial s390x packages are needed (blocks ceilometer) Status in OpenStack ceilometer charm: Invalid Status in OpenStack ceilometer-agent charm: Invalid Status in MongoDB Charm: Confirmed Status in Ubuntu on IBM z Systems: Fix Released Status in google-perftools package in Ubuntu: Fix Released Status in mongodb package in Ubuntu: Fix Released Status in google-perftools source package in Xenial: New Status in mongodb source package in Xenial: Won't Fix Status in google-perftools source package in Yakkety: New Status in mongodb source package in Yakkety: Won't Fix Status in ceilometer package in Juju Charms Collection: Invalid Status in ceilometer-agent package in Juju Charms Collection: Invalid Status in mongodb package in Juju Charms Collection: Invalid Status in mongodb package in Debian: Fix Released Bug description: The ceilometer and ceilometer-agent charms require the mongodb charm. s390x validation for ceilometer and ceilometer-agent is blocked on the absence of mongodb packages in s390x Xenial, and on the absence of a Xenial mongodb charm in general. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceilometer/+bug/1595242/+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 1719970] Re: linux-aws: 4.4.0-1037.46 -proposed tracker
** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux-aws (Ubuntu) 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/1719970 Title: linux-aws: 4.4.0-1037.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New 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 4.4.0-1037.46 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: 1716613 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1719970/+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 1720042] Re: linux-aws: 4.4.0-1038.47 -proposed tracker
** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1720042 Title: linux-aws: 4.4.0-1038.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-1038.47 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 -- kernel-stable-master-bug: 1718149 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1720042/+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 1718149] Re: linux: 4.4.0-97.120 -proposed tracker
4.4.0-97.120 - generic Regression test CMPL. http://kernel.ubuntu.com/testing/tracker-index.html Issue to note in amd64: monotonic_time - gtod failed ubuntu_kvm_unit_tests - 29 failed on amaura, 11 failed on archytas, 27 failed on onza, 17 failed on michael, 10 failed on daedalus xfstests - btrfs timed out, bug 1718925 Issue to note in arm64: hwclock - issue for HP m400, bug 1716603, or a bug to test case rtc - Update IRQs not supported on starmie ubuntu_fan_smoke_test - network issue ubuntu_kvm_unit_tests - gicv2-ipi, gicv2-active failed on both nodes ubuntu_stress_smoke_test - network issue on starmie ubuntu_zfs_xfs_generic - failed with test 079 Issue to note in i386: monotonic_time - gtod failed on fozzie ubuntu_lxc - Failed to start networking in ubuntu-cloud container Issue to note in ppc64le: rtc - Update IRQs not supported. ubuntu_kvm_unit_tests - spapr_hcall failed, bug 1712803, sprs failed xfstests - btrfs timed out, bug 1718925 Issue to note in s390x (Ubuntu on LPAR): aio_dio_bugs - event res -22, issue seen before libhugetlbfs - 10 failed, 7 killed by signal, 1 bad configuration scrashme - failed to build, bug 168924 ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed) ubuntu_lxc - Failed to start networking in ubuntu-cloud container ubuntu_qrt_apparmor - passed after re-test ubuntu_seccomp - failed to build, bug 1715581 Issue to note in s390x (zKVM): aio_dio_bugs - event res -22, issue seen before libhugetlbfs - 10 failed, 7 killed by signal, 1 bad configuration scrashme - failed to build, bug 168924 ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed) ubuntu_seccomp - failed to build, bug 1715581 Issue to note in s390x (zVM): aio_dio_bugs - event res -22, issue seen before, not regression libhugetlbfs - IOError: [Errno 524] Unknown error 524, issue seen before scrashme - failed to build, bug 168924 ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed) ubuntu_seccomp - failed to build, bug 1715581 4.4.0-97.120 - lowlatency Regression test CMPL. http://kernel.ubuntu.com/testing/tracker-index.html Issue to note in amd64: monotonic_time - gtod failed on onza ubuntu_kvm_unit_tests - 11 failed on archytas, daedalus, 27 failed on onza, 17 failed on michael, 28 failed on amaura xfstests - btrfs timed out, bug 1718925 Issue to note in i386: None ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1718149 Title: linux: 4.4.0-97.120 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux 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 backports: 1718150,1718151 derivatives: 1718153,1718154,1718155,1718156,1718157 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1718149/+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