[Group.of.nepali.translators] [Bug 1744166] Re: East-Saskatchewan timezone removed in latest tzdata

[Nish Aravamudan]

Fixed in bionic: 3.5.2-1ubuntu1

** Summary changed:

- East/Saskatchewan timezone removed in latest tzdata
+ East-Saskatchewan timezone removed in latest tzdata

** Description changed:

- This leads to autopkgtest failures.
+ [Impact]
+ 
+ * DEP8 tests for php-sabre-vobject-3 currently fail in 16.04 because the
+ 2017c version of tzdata dropped the East-Saskatchewan timezone, which is
+ hardcoded in the package.
+ 
+ * This in turn blocks SRUs of new PHP7.0 microreleases.
+ 
+ [Test Case]
+ 
+ * Run the autopkgtests for this source package before and after the
+ change. They should pass after.
+ 
+ [Regression Potential]
+ 
+ * None, this timezone is no longer valid in 16.04.

** Changed in: php-sabre-vobject-3 (Ubuntu)
   Status: New => Fix Released

** Changed in: php-sabre-vobject-3 (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: php-sabre-vobject-3 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1744166

Title:
  East-Saskatchewan timezone removed in latest tzdata

Status in php-sabre-vobject-3 package in Ubuntu:
  Fix Released
Status in php-sabre-vobject-3 source package in Xenial:
  Fix Committed
Status in php-sabre-vobject-3 package in Debian:
  Fix Committed

Bug description:
  [Impact]

  * DEP8 tests for php-sabre-vobject-3 currently fail in 16.04 because
  the 2017c version of tzdata dropped the East-Saskatchewan timezone,
  which is hardcoded in the package.

  * This in turn blocks SRUs of new PHP7.0 microreleases.

  [Test Case]

  * Run the autopkgtests for this source package before and after the
  change. They should pass after.

  [Regression Potential]

  * None, this timezone is no longer valid in 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-sabre-vobject-3/+bug/1744166/+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 1532608] Re: Files moved around in clamav without appropriate Breaks/Replaces, causing upgrade failures

[Brian Murray]

Hello Andreu, or anyone else affected,

Accepted clamav into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/clamav/0.99.2+dfsg-
0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: clamav (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: clamav (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
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/1532608

Title:
  Files moved around in clamav without appropriate Breaks/Replaces,
  causing upgrade failures

Status in clamav package in Ubuntu:
  In Progress
Status in clamav source package in Xenial:
  Fix Committed

Bug description:
  
  [Impact] 

   * Upgrades can fail due to file collisions since SRUs that bumped the 
 version in trusty. Due to that the formerly breaks/replaces no more 
 applies correctly.

  [Test Case]

   * The following upgrade paths leads to an error without the fix (ok to be 
 run in a container)
 # install trusty
 $ apt install clamav-daemon
 # upgrade to Xenial repo
 $ apt update && apt upgrade

  [Regression Potential]

   * Since we "just" bump the breaks/replaces this should be fairly safe.
 The only case that comes to my mind is when old custom versions with 
 odd versions were installed, but even then it either does just trigger 
 the same issues. OTOH most likely even in that rare (and unsupported 
 case) they should be fine.

  [Other Info]
   
   * n/a


  ---

  This bug appeared updating from Ubuntu 14.04 to Ubuntu 15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: clamav-daemon 0.98.7+dfsg-0ubuntu0.15.04.1
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Sun Jan 10 21:18:16 2016
  DuplicateSignature: 
package:clamav-daemon:0.98.7+dfsg-0ubuntu0.15.04.1:intentando sobreescribir 
`/usr/share/man/man5/clamd.conf.5.gz', que está también en el paquete 
clamav-base 0.98.7+dfsg-0ubuntu0.14.04.1
  ErrorMessage: intentando sobreescribir `/usr/share/man/man5/clamd.conf.5.gz', 
que está también en el paquete clamav-base 0.98.7+dfsg-0ubuntu0.14.04.1
  InstallationDate: Installed on 2015-07-25 (168 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic 
root=UUID=b406f381-7240-484e-88db-5b321e59568d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: clamav
  Title: package clamav-daemon 0.98.7+dfsg-0ubuntu0.15.04.1 failed to 
install/upgrade: intentando sobreescribir 
`/usr/share/man/man5/clamd.conf.5.gz', que está también en el paquete 
clamav-base 0.98.7+dfsg-0ubuntu0.14.04.1
  UpgradeStatus: Upgraded to vivid on 2016-01-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1532608/+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 1744166] [NEW] East/Saskatchewan timezone removed in latest tzdata

[Nish Aravamudan]

Public bug reported:

This leads to autopkgtest failures.

** Affects: php-sabre-vobject-3 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: php-sabre-vobject-3 (Ubuntu Xenial)
 Importance: Medium
 Assignee: Nish Aravamudan (nacc)
 Status: Confirmed

** Affects: php-sabre-vobject-3 (Debian)
 Importance: Unknown
 Status: Unknown

** Also affects: php-sabre-vobject-3 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: php-sabre-vobject-3 (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: php-sabre-vobject-3 (Ubuntu Xenial)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: php-sabre-vobject-3 (Ubuntu Xenial)
   Importance: Undecided => Medium

** Bug watch added: Debian Bug tracker #880337
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880337

** Also affects: php-sabre-vobject-3 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880337
   Importance: Unknown
   Status: Unknown

-- 
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/1744166

Title:
  East/Saskatchewan timezone removed in latest tzdata

Status in php-sabre-vobject-3 package in Ubuntu:
  New
Status in php-sabre-vobject-3 source package in Xenial:
  Confirmed
Status in php-sabre-vobject-3 package in Debian:
  Unknown

Bug description:
  This leads to autopkgtest failures.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-sabre-vobject-3/+bug/1744166/+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 1744148] Re: [MRE] Please update to latest upstream release 7.0.27

[Nish Aravamudan]

** Changed in: php7.0 (Ubuntu)
   Status: New => Confirmed

** Also affects: php7.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: php7.0 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: php7.0 (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: php7.0 (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: php7.0 (Ubuntu Xenial)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

-- 
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/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.27

Status in php7.0 package in Ubuntu:
  Invalid
Status in php7.0 source package in Xenial:
  Confirmed

Bug description:
  PHP 7.0.25 was tentatively SRU'ed to Xenial (LP: #1724896). During the
  process, upstream put out 2 more microversions addressing security
  issues and other bug fixes. Here is a list of the CVEs addressed by
  those:

  PHP 7.0.26 (23 Nov 2017):

  * No CVE addressed

  PHP 7.0.27 (04 Jan 2018):

  * https://bugs.php.net/bug.php?id=64938 / 
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-8866
  * https://bugs.php.net/bug.php?id=75571 / 
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5711
  * https://bugs.php.net/bug.php?id=74782 / 
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5712

  Changelog: https://secure.php.net/ChangeLog-7.php

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1744148/+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 1727337] Re: lime-forensics 1.7.2-1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Launchpad Bug Tracker]

This bug was fixed in the package lime-forensics - 1.7.2-1ubuntu1

---
lime-forensics (1.7.2-1ubuntu1) xenial; urgency=medium

  * Add support for 4.11 kernels. (LP: #1727337)
- 0001-Fixed-issue-with-compiling-on-kernels-4.11.patch

 -- Marcelo Henrique Cerri   Fri, 27 Oct
2017 12:15:19 -0200

** Changed in: lime-forensics (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/1727337

Title:
  lime-forensics 1.7.2-1 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in lime-forensics package in Ubuntu:
  In Progress
Status in lime-forensics source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lime-forensics/20171018_120534_aec4e@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/l/lime-forensics/20171018_120630_aec4e@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lime-forensics/20171018_121419_aec4e@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lime-forensics/20171018_120611_aec4e@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lime-forensics/20171018_115927_aec4e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1727337/+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 1727334] Re: dm-writeboost 2.2.6-1~16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Launchpad Bug Tracker]

This bug was fixed in the package dm-writeboost - 2.2.6-1~16.04.2

---
dm-writeboost (2.2.6-1~16.04.2) xenial; urgency=medium

  * Backport to xenial to support 4.11 and 4.13 kernels. (LP: #1727334)
- 0001-ubuntu-compat-4.13.patch

 -- Marcelo Henrique Cerri   Fri, 27 Oct
2017 15:16:55 -0200

** Changed in: dm-writeboost (Ubuntu Xenial)
   Status: Incomplete => 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/1727334

Title:
  dm-writeboost 2.2.6-1~16.04.1 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in dm-writeboost source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20171018_120546_4e791@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20171018_120710_4e791@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20171018_121235_4e791@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20171018_120813_4e791@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20171018_115927_4e791@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dm-writeboost/+bug/1727334/+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 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.135-0ubuntu0.16.04.2

---
nvidia-graphics-drivers-304 (304.135-0ubuntu0.16.04.2) xenial; urgency=medium

  * Support for kernel 4.11 and 4.12. (LP: #1724871)
- debian/dkms/patches/buildfix_kernel_4.11.patch
- debian/dkms/patches/buildfix_kernel_4.12.patch

 -- Marcelo Henrique Cerri   Wed, 01 Nov
2017 16:57:45 -0200

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: Incomplete => 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/1724871

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1724871/+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 1724867] Re: langford 0.0.20130228-5 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Launchpad Bug Tracker]

This bug was fixed in the package langford -
0.0.20130228-5ubuntu1~16.04.1

---
langford (0.0.20130228-5ubuntu1~16.04.1) xenial; urgency=medium

  * Fix module build with Linux 4.12 (LP: #1724867)
- debian/patches/fix-uaccess-include.patch

 -- Marcelo Henrique Cerri   Tue, 31 Oct
2017 14:21:48 -0200

** Changed in: langford (Ubuntu Xenial)
   Status: Incomplete => 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/1724867

Title:
  langford 0.0.20130228-5 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in langford package in Ubuntu:
  Fix Released
Status in langford source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/langford/20171018_120558_d9a48@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/l/langford/20171018_121613_d9a48@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/langford/20171018_121338_d9a48@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/langford/20171018_120515_d9a48@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langford/+bug/1724867/+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 1724865] Re: broadcom-sta 6.30.223.271-3~16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Launchpad Bug Tracker]

This bug was fixed in the package broadcom-sta - 6.30.223.271-3~16.04.2

---
broadcom-sta (6.30.223.271-3~16.04.2) xenial; urgency=medium

  * Backport to xenial for kernel 4.10, 4.11 and 4.13 support. (LP: #1724865)
- 16-linux48.patch
- 17-fix-kernel-warnings.patch
- 18-linux411.patch
- 19-linux412.patch

 -- Marcelo Henrique Cerri   Thu, 26 Oct
2017 16:40:15 -0200

** Changed in: broadcom-sta (Ubuntu Xenial)
   Status: Incomplete => 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/1724865

Title:
  broadcom-sta 6.30.223.271-3~16.04.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

Status in broadcom-sta package in Ubuntu:
  In Progress
Status in broadcom-sta source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package broadcom-sta fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11 
hwe-edge
  and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud 
kernels
  as well.

  [Test Case]

  Install the broadcom-sta package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since the new
  changes are conditionally compiled based on the kernel version.

  Besides that the new package was tested with the following kernels in an amd64
  environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/broadcom-sta/20171018_120722_62eb1@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/broadcom-sta/20171018_121214_62eb1@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1724865/+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 1727343] Re: rt-tests 0.93-1ubuntu1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Launchpad Bug Tracker]

This bug was fixed in the package rt-tests - 0.93-1ubuntu2

---
rt-tests (0.93-1ubuntu2) xenial; urgency=medium

  * Add support to backfire for 4.11 kernels. (LP: #1727343)
- debian/patches/backfire-fix-build-failure-for-4.11-kernels.patch

 -- Marcelo Henrique Cerri   Wed, 01 Nov
2017 14:50:01 -0200

** Changed in: rt-tests (Ubuntu Xenial)
   Status: Incomplete => 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/1727343

Title:
  rt-tests 0.93-1ubuntu1 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in rt-tests package in Ubuntu:
  In Progress
Status in rt-tests source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/r/rt-tests/20171018_120348_f6c62@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/r/rt-tests/20171018_120711_f6c62@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/r/rt-tests/20171018_121506_f6c62@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/r/rt-tests/20171018_121632_f6c62@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/r/rt-tests/20171018_120217_f6c62@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rt-tests/+bug/1727343/+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 1724875] Re: xtables-addons 2.12-0.1~16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Launchpad Bug Tracker]

This bug was fixed in the package xtables-addons - 2.12-0.1~16.04.2

---
xtables-addons (2.12-0.1~16.04.2) xenial; urgency=medium

  * Fix module build error with Linux 4.12+ (LP: #1724875)
- debian/patches/buildfix-4.12.patch

 -- Marcelo Henrique Cerri   Tue, 31 Oct
2017 15:09:28 -0200

** Changed in: xtables-addons (Ubuntu Xenial)
   Status: Incomplete => 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/1724875

Title:
  xtables-addons 2.12-0.1~16.04.1 ADT test failure with linux-hwe-edge
  4.13.0-16.19~16.04.3

Status in xtables-addons package in Ubuntu:
  Invalid
Status in xtables-addons source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/x/xtables-addons/20171018_120630_098c1@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/x/xtables-addons/20171018_120653_098c1@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/x/xtables-addons/20171018_121609_098c1@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/x/xtables-addons/20171018_121705_098c1@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/x/xtables-addons/20171018_120523_098c1@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1724875/+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 1744078] Re: linux < 4.8: x-netns vti is broken

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: linux (Ubuntu)
   Status: Confirmed => Triaged

** Tags added: kernel-da-key xenial

-- 
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/1744078

Title:
  linux < 4.8: x-netns vti is broken

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  The following upstream patch is missing:

  11d7a0bb95ea xfrm: Only add l3mdev oif to dst lookups 
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=11d7a0bb95ea

  There are several ways to reproduce this problem. Here an example:

  # Prepare netns
  ip netns add test
  ip netns exec test sysctl -q -w net.ipv4.conf.all.forwarding=1
  ip netns exec test ip link set lo up
  ip netns exec test ip addr add 172.16.1.1/24 dev lo

  # Create VTI iface and move it in netns test
  ip addr add 1.1.1.1/32 dev lo
  ip link add name vti_test type vti local 1.1.1.1 remote 2.2.2.2 key 0x1
  ip link set dev vti_test netns test

  # Configure IPsec
  ip xfrm state add src 1.1.1.1 dst 2.2.2.2 proto esp spi 1 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm state add src 2.2.2.2 dst 1.1.1.1 proto esp spi 2 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm policy add dir out tmpl src 1.1.1.1 dst 2.2.2.2 proto esp mode tunnel 
mark 0x1
  ip xfrm policy add dir in tmpl src 2.2.2.2 dst 1.1.1.1 proto esp mode tunnel 
mark 0x1

  # Configure SVTI
  ip netns exec test ip link set dev vti_test up

  # Add route
  ip netns exec test ip route add 172.16.2.0/24 dev vti_test

  # Run a tcpdump on the output interface (given by "ip route get 2.2.2.2")
  tcpdump -nei eth0 &

  # Ping from the netns
  ip netns exec test ping 172.16.2.1 -I 172.16.1.1 -c 4

  --

  On 4.4.0-109-generic:
  (ping) From 172.16.1.1 icmp_seq=1 Destination Host Unreachable
  (tcpdump) no IPsec packet

  => Problem

  On 4.8.0-58-generic:
  (ping): no error raised
  (tcpdump) 15:09:45.109776 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x2), 
length 132
  (tcpdump) 15:10:05.422243 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x3), 
length 132

  => No problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744078/+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 1744117] Re: [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel

[Eric Desrochers]

** Changed in: linux (Ubuntu)
   Status: New => 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/1744117

Title:
  [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table
  to Ubuntu 16.04 LTS Kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  Add support for 4/6/8 channel sound in 16.04 LTS kernel for future
  GPUs. This commit should be what is needed:

  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f

  ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

  Add codec IDs for several recently released, pending, and historical
  NVIDIA GPU audio controllers to the patch table, to allow the correct
  patch functions to be selected for them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744117/+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 1744117] Re: [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel

[Eric Desrochers]

Patch is already found in v4.13 (ubuntu-artful)

$ git describe --contains  74ec118152ea494a25ebb677cbc83a75c982ac5f
v4.13~13^2~22


v4.4 (ubuntu-xenial) doesn't have the patch.

Since this seems trivial, and apply cleanly, and I'll proceed with the
SRU (after verification) and see what kernel-team says.

- Eric


** Tags added: sts

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1744117

Title:
  [SRU][HWE] ALSA backport missing NVIDIA GPU codec IDs to patch table
  to Ubuntu 16.04 LTS Kernel

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress

Bug description:
  Add support for 4/6/8 channel sound in 16.04 LTS kernel for future
  GPUs. This commit should be what is needed:

  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f

  ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

  Add codec IDs for several recently released, pending, and historical
  NVIDIA GPU audio controllers to the patch table, to allow the correct
  patch functions to be selected for them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744117/+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 1722162] Re: gold: Fix internal error when applying TLSDESC relocations with no TLS segment.

[Launchpad Bug Tracker]

This bug was fixed in the package binutils - 2.26.1-1ubuntu1~16.04.6

---
binutils (2.26.1-1ubuntu1~16.04.6) xenial; urgency=medium

  * pr19353.diff: Fix internal error when applying TLSDESC relocations with no 
TLS
segment. (LP: #1722162)

 -- Timo Aaltonen   Wed, 08 Nov 2017 18:06:03 +0200

** Changed in: binutils (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/1722162

Title:
  gold: Fix internal error when applying TLSDESC relocations with no TLS
  segment.

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  llvm-5.0 fails to build on arm64/xenial because of gold/19353.

  [Test case]

  backport the upstream commit, test llvm-5 build ond arm64

  [Regression potential]
  Unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1722162/+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 1744062] [NEW] L3 HA: multiple agents are active at the same time

[Corey Bryant]

Public bug reported:

This is the same issue reported in
https://bugs.launchpad.net/neutron/+bug/1731595, however that is marked
as 'Fix Released' and the issue is still occurring and I can't change
back to 'New' so it seems best to just open a new bug.

It seems as if this bug surfaces due to load issues. While the fix
provided by Venkata (https://review.openstack.org/#/c/522641/) should
help clean things up at the time of l3 agent restart, issues seem to
come back later down the line in some circumstances. xavpaice mentioned
he saw multiple routers active at the same time when they had 464
routers configured on 3 neutron gateway hosts using L3HA, and each
router was scheduled to all 3 hosts. However, jhebden mentions that
things seem stable at the 400 L3HA router mark, and it's worth noting
this is the same deployment that xavpaice was referring to.

It seems to me that something is being pushed to it's limit, and
possibly once that limit is hit, master router advertisements aren't
being received, causing a new master to be elected. If this is the case
it would be great to get to the bottom of what resource is getting
constrained.

** Affects: cloud-archive
 Importance: High
 Status: Triaged

** Affects: cloud-archive/mitaka
 Importance: High
 Status: Triaged

** Affects: cloud-archive/newton
 Importance: High
 Status: Triaged

** Affects: cloud-archive/ocata
 Importance: High
 Status: Triaged

** Affects: cloud-archive/pike
 Importance: High
 Status: Triaged

** Affects: cloud-archive/queens
 Importance: High
 Status: Triaged

** Affects: neutron
 Importance: Undecided
 Status: New

** Affects: neutron (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: neutron (Ubuntu Xenial)
 Importance: High
 Status: Triaged

** Affects: neutron (Ubuntu Artful)
 Importance: High
 Status: Triaged

** Affects: neutron (Ubuntu Bionic)
 Importance: High
 Status: Triaged

** Description changed:

  This is the same issue as
  https://bugs.launchpad.net/neutron/+bug/1731595 however that bug is 'Fix
  Released' and the issue is still occurring. There are a lot of details
- in the linked bug so I won't add them here unless it's useful.
+ in the linked bug so I won't add too many here.
+ 
+ It seems as if this bug surfaces due to load issues. While the fix
+ provided by Venkata (https://review.openstack.org/#/c/522641/) should
+ help clean things up at the time of l3 agent restart, issues seem to
+ come back later down the line in some circumstances. xavpaice mentioned
+ he saw multiple routers active at the same time when they had 464
+ routers configured on 3 neutron gateway hosts using L3HA, and each
+ router was scheduled to all 3 hosts. However, jhebden mentions that
+ things seem stable at the 400 L3HA router mark, and it's worth noting
+ this is the same deployment that xavpaice was referring to.
+ 
+ It seems to me that something is being pushed to it's limit, and
+ possibly once that limit is hit, master router advertisements aren't
+ being received, causing a new master to be elected. If this is the case
+ it would be great to get to the bottom of what resource is getting
+ constrained.

** Also affects: neutron (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- This is the same issue as
- https://bugs.launchpad.net/neutron/+bug/1731595 however that bug is 'Fix
- Released' and the issue is still occurring. There are a lot of details
- in the linked bug so I won't add too many here.
- 
- It seems as if this bug surfaces due to load issues. While the fix
- provided by Venkata (https://review.openstack.org/#/c/522641/) should
- help clean things up at the time of l3 agent restart, issues seem to
- come back later down the line in some circumstances. xavpaice mentioned
- he saw multiple routers active at the same time when they had 464
- routers configured on 3 neutron gateway hosts using L3HA, and each
- router was scheduled to all 3 hosts. However, jhebden mentions that
- things seem stable at the 400 L3HA router mark, and it's worth noting
- this is the same deployment that xavpaice was referring to.
- 
- It seems to me that something is being pushed to it's limit, and
- possibly once that limit is hit, master router advertisements aren't
- being received, causing a new master to be elected. If this is the case
- it would be great to get to the bottom of what resource is getting
- constrained.
+ -

** No longer affects: neutron

** Summary changed:

-  L3 HA: multiple agents are active at the same time
+ -

** Changed in: neutron (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- -
+ L3 HA: multiple agents are active at the same time

** Description changed:

- -
+ This is the same issue reported in
+ https://bugs.launchpad.net/neutron/+bug/1731595, however that is marked
+ as 'Fix Released' and the issue is still occurring.
+ 
+ It 

[Group.of.nepali.translators] [Bug 1743001] Re: linux-aws: 4.4.0-1049.58 -proposed tracker

[Po-Hsu Lin]

4.4.0-1049.58 - aws
Regression test CMPL.

Issue to note in x86_64 (aws):
  libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3
  ubuntu_kvm_unit_tests - test disabled
  ubuntu_ltp - test disabled
  ubuntu_lxc - lxc-test-ubunut failed (Failed to start networking in 
ubuntu-cloud container)


** 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/1743001

Title:
  linux-aws: 4.4.0-1049.58 -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 snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
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: 1743362
  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/1743001/+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 1742723] Re: linux-azure: 4.13.0-1006.8 -proposed tracker

[Po-Hsu Lin]

4.13.0-1006.8 - azure
Regression test CMPL.

Issue to note in x86_64 (azure):
  ebizzy - failed on Standard_A0, passed on the rest
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad 
config 3, passed on the rest
  monotonic_time - all three tests (or just tsc test) failed on some instances, 
passed on the rest
  ubuntu_kvm_unit_tests - 15 test failed (apic, ioapic, vmexit_vmcall, 
emulator, hypercall, idt_test, realmode, s3, sieve, syscall, svm, 
kvmclock_test, pcid, debug, hyperv_clock), some node will have sieve test passed
  ubuntu_ltp - test disabled
  ubuntu_lttng_smoke_test - failed on Standard_B1s only, passed on the rest
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in 
ubuntu-cloud container, Failed creating ubuntu-cloud container due to too many 
open files), passed on the rest
  ubuntu_unionmount_overlayfs_suite - bug 1727290

Note that the ubuntu_kvm_unit_tests will be marked as passed even it
have some tests failed.


** 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/1742723

Title:
  linux-azure: 4.13.0-1006.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  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:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1742722
  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/1742723/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1727401

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1512068] Re: Python ctypes.util , Shell Injection in find_library()

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.3

---
python2.7 (2.7.12-1ubuntu0~16.04.3) xenial-proposed; urgency=medium

  * Some performance improvements: LP: #1638695.
- Build the _math.o object file without -fPIC for static builds.
  * Rename md5_* functions to _Py_md5_*. Closes: #868366. LP: #1734109.
  * Explicitly use the system python for byte compilation in postinst scripts.
LP: #1682934.
  * Fix issue #22636: Avoid shell injection problems with
ctypes.util.find_library(). LP: #1512068.

 -- Matthias Klose   Mon, 04 Dec 2017 15:50:18 +0100

** Changed in: python2.7 (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/1512068

Title:
  Python ctypes.util , Shell Injection in find_library()

Status in Python:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Released

Bug description:
  https://github.com/Legrandin/ctypes/issues/1

  The find_library() function can execute code when special chars like ;|`<>$ 
are in the name.
  The "os.popen()" calls in the util.py script should be replaced with 
"subprocess.Popen()".

  Demo Exploits for Linux :
  

  >>> from ctypes.util import find_library
  >>> find_library(";xeyes")# runs  xeyes 
  >>> find_library("|xterm")# runs terminal
  >>> find_library("")# runs gimp
  >>> find_library("$(nautilus)")  # runs filemanager
  >>> find_library(">test")   # creates, and if exists, 
erases a file "test"

   Traceback 

  >>> find_library("`xmessage hello`")# shows a message, press ctrl+c for 
Traceback
  ^CTraceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3.4/ctypes/util.py", line 244, in find_library
  return _findSoname_ldconfig(name) or _get_soname(_findLib_gcc(name))
File "/usr/lib/python3.4/ctypes/util.py", line 99, in _findLib_gcc
  trace = f.read()
  KeyboardInterrupt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libpython2.7-stdlib 2.7.10-4ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov  1 10:34:38 2015
  InstallationDate: Installed on 2015-10-09 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151009)
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1512068/+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 1638695] Re: Python 2.7.12 performance regression

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.3

---
python2.7 (2.7.12-1ubuntu0~16.04.3) xenial-proposed; urgency=medium

  * Some performance improvements: LP: #1638695.
- Build the _math.o object file without -fPIC for static builds.
  * Rename md5_* functions to _Py_md5_*. Closes: #868366. LP: #1734109.
  * Explicitly use the system python for byte compilation in postinst scripts.
LP: #1682934.
  * Fix issue #22636: Avoid shell injection problems with
ctypes.util.find_library(). LP: #1512068.

 -- Matthias Klose   Mon, 04 Dec 2017 15:50:18 +0100

** Changed in: python2.7 (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/1638695

Title:
  Python 2.7.12 performance regression

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Released
Status in python2.7 source package in Zesty:
  Fix Committed

Bug description:
  SRU: Looks like only the math.o build without -fPIC makes it into the
  SRU. There shouldn't be any regression potential when building without
  -fPIC for the static interpreter.  Acceptance criteria is running the
  benchmarks and not showing any performance regressions.

  I work on the OpenStack-Ansible project and we've noticed that testing
  jobs on 16.04 take quite a bit longer to complete than on 14.04.  They
  complete within an hour on 14.04 but they normally take 90 minutes or
  more on 16.04.  We use the same version of Ansible with both versions
  of Ubuntu.

  After more digging, I tested python performance (using the
  'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12).  There
  is a significant performance difference between each version of
  python.  That is detailed in a spreadsheet[0].

  I began using perf to dig into the differences when running the python
  performance module and when using Ansible playbooks.  CPU migrations
  (as measured by perf) are doubled in Ubuntu 16.04 when running the
  same python workloads.

  I tried changing some of the kerne.sched sysctl configurables but they
  had very little effect on the results.

  I compiled python 2.7.12 from source on 14.04 and found the
  performance to be unchanged there.  I'm not entirely sure where the
  problem might be now.

  We also have a bug open in OpenStack-Ansible[1] that provides
  additional detail. Thanks in advance for any help you can provide!

  [0] 
https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing
  [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.3

---
python2.7 (2.7.12-1ubuntu0~16.04.3) xenial-proposed; urgency=medium

  * Some performance improvements: LP: #1638695.
- Build the _math.o object file without -fPIC for static builds.
  * Rename md5_* functions to _Py_md5_*. Closes: #868366. LP: #1734109.
  * Explicitly use the system python for byte compilation in postinst scripts.
LP: #1682934.
  * Fix issue #22636: Avoid shell injection problems with
ctypes.util.find_library(). LP: #1512068.

 -- Matthias Klose   Mon, 04 Dec 2017 15:50:18 +0100

** Changed in: python2.7 (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:
  Fix Released
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Zesty:
  Fix Committed
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 : 

[Group.of.nepali.translators] [Bug 1734109] Re: Avoid symbol conflicts with `md5_*' symbols in third party extensions

[Launchpad Bug Tracker]

This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.3

---
python2.7 (2.7.12-1ubuntu0~16.04.3) xenial-proposed; urgency=medium

  * Some performance improvements: LP: #1638695.
- Build the _math.o object file without -fPIC for static builds.
  * Rename md5_* functions to _Py_md5_*. Closes: #868366. LP: #1734109.
  * Explicitly use the system python for byte compilation in postinst scripts.
LP: #1682934.
  * Fix issue #22636: Avoid shell injection problems with
ctypes.util.find_library(). LP: #1512068.

 -- Matthias Klose   Mon, 04 Dec 2017 15:50:18 +0100

** Changed in: python2.7 (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/1734109

Title:
  Avoid symbol conflicts with `md5_*' symbols in third party extensions

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  Fix Released
Status in python2.7 source package in Zesty:
  Fix Committed
Status in python2.7 source package in Artful:
  Fix Released

Bug description:
  SRU

  We link most extensions as built-ins into the python binary. the md5_*
  symbols cause a conflict with external libs/extensions.  So just use
  the _Py-* namespace for these. See the Debian report for details.

  These are internal functions for the md5 module. Renaming them to the
  _Py_* namespace avoids the conflict.  There should not be any case
  where these are intentionally referenced. At least in the archive
  there are no known references, so the regression potential is limited
  to external binaries, and there it should be minimal to non-existing
  as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1734109/+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 1728048] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for cloud-initramfs-tools
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

** Changed in: cloud-initramfs-tools (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1728048

Title:
  squashfs url matching is too strict

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Zesty:
  Won't Fix
Status in cloud-initramfs-tools source package in Artful:
  Fix Released

Bug description:
   Begin SRU Template ===
  [Impact]
  Squashfs images published by Ubuntu on http://cloud-images.ubuntu.com
  end in '.squashfs' and on http://images.maas.io/ephemeral-v3/
  the files are named 'squashfs'.

  When you boot an initramfs with rooturl it would automatically
  determine/assume that content is squashfs if it ended in
  '.squash' or '.squashfs'.

  The filter was just too strict and would thus not match
    http://images.maas.io/ephemeral-v3//squashfs

  That meant a usage would have to re-publish the url.

  [Test Case]
  ## setup system to build maas images
  $ sudo apt-get install -qy --no-install-recommends bzr
  $ bzr branch lp:maas-images
  $ cd maas-images
  $ ./system-setup

  ## download the reference squashfs images.
  $ arch=amd64
  $ burl=http://cloud-images.ubuntu.com/server
  # download reference squashfs images
  $ for rel in xenial zesty artful; do
file=../$rel-server-cloudimg-$arch.squashfs;
[ -f "$file" ] && continue;
wget "$burl/$rel/current/${file#*/}" -O "$file.tmp" &&
  mv "$file.tmp" "$file"
  done

  ## build maas image output.  This creates a squashfs image and 
kernel/initramfs
  ## files that have the updated packages inside.
  ## It does take a while to run, and lots of cpu and IO.
  ## You can reduce the kernels built by commenting out 'lowlatency' and 'edge'
  ## kernels:
  ##  sed -i -e '/^[ ].*\(lowlatency\|edge\)/s/^/#/' conf/meph-v3.yaml
  # either set 'proposed' or add the repo via M2E_ADD_REPOS
  $ proposed="--proposed"
  $ export M2E_ADD_REPOS=ppa:smoser/cloud-initramfs-tools
  $ for rel in xenial zesty artful; do
    img=../$rel-server-cloudimg-$arch.squashfs
    PATH=$PWD/bin:$PATH ./bin/meph2-build $proposed --config=conf/meph-v3.yaml \
  $arch $rel $(date +"%Y%m%d") $img ../$rel.d/ 2>&1 |
  tee ../$rel.log
    done

  ## After running, you will have files like:
  $ find xenial.d/xenial -type f | sort
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/squashfs
  xenial.d/xenial/amd64/20171221/squashfs.manifest

  ## You can verify in the $rel.log files you have 'Setting up cloud-initramfs-'
  $ grep '^Setting up overlayroot' xenial.log
  Setting up overlayroot (0.27ubuntu1.5~ppa16.04.1) ...

  ## Now download the test-boot script, provide it a directory and
  ## the squashfs, kernel, initramfs

  $ ./test-boot test-x xenial.d/xenial/amd64/20171221/squashfs \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd

  $ r=zesty; ./test-boot work.d $r.d/*/amd64/*/squashfs 
$r.d/*/amd64/*/ga-*/generic/boot-kernel $r.d/*/amd64/*/ga-*/generic/boot-initrd
  Now, do:
    cd work.d
    ./boot

  ## Running ./boot will serve the squashfs image over http, and then
  ## boot the kernel and initrd with a kernel command line of
  ##root=http:///squashfs
  ## and
  ##ds=nocloud-net;seedfrom=http://10.0.2.2:/
  ## which will the read the 'user-data' and 'meta-data' files in that dir.
  ##
  ## The result is that you can log in with 'ubuntu' and 'passw0rd'

  ## Then collect some information
  # you'll see the 'LABEL=' entry is commented out.
  $ cat /etc/fstab
  # local-fs.target should be fine
  $ systemctl status local-fs.target --no-pager
  # just for record
  $ cat /proc/cmdline

  [Regression Potential]
  Very low.
  If a url does not match, rooturl would just complain and do nothing.
  This just extends the things that match.

  [Other Info]
  This does seem to be low importance.  In fact it is, but its jsut part
  of syncing cloud-initramfs-tools 

[Group.of.nepali.translators] [Bug 1723183] Re: transient systemd ordering issue when using overlayroot

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.5

---
cloud-initramfs-tools (0.27ubuntu1.5) xenial; urgency=medium

  * sync with upstream at 0.40ubuntu1
- whitespace changes.
- rooturl: adjust squashfs url matching to not require '.'.
  Previously it would match *.squashfs or *.squash
  Now it will match *squashfs or *squash.  (LP: #1728048)
- updateroot/*, debian/control: new package 'cloud-initramfs-updateroot'
- debian/README.source: update upstream information for move to git.
- overlayroot: change from storing password in
  /run/initramfs/overlayroot.passwd rather than randomly generated
  /run/initramfs/overlayroot.XX
- overlayroot: avoid confusing systemd (LP: #1723183)
   + Mark / as 'noauto' in the newly written /etc/fstab
   + Comment out the read-only line for /.

 -- Scott Moser   Fri, 15 Dec 2017 15:57:35 -0500

** Changed in: cloud-initramfs-tools (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/1723183

Title:
  transient systemd ordering issue when using overlayroot

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Zesty:
  Won't Fix
Status in cloud-initramfs-tools source package in Artful:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  Overlayfs allows a user to mount the root filesystem read-only
  and put an overlay over it.
  It handles mounting of the root filesystem in the initramfs, and updates
  /etc/fstab to account for non-root filesystems and generally make
  /etc/fstab "correct".

  systemd can get confused by a /etc/fstab that looks like this:

     LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
     /media/root-ro/ / overlay lowerdir=...

  It would not recognize that the LABEL=cloudimg-rootfs image *was* mounted.
  This would lead to boot ordering cycles.  The fix that was ultimately
  applied was just to comment out the line for /media/root-ro.

  That way systemd wouldnt try to ensure that /media/root-ro got
  mounted.

  The fix that was put in place was just to comment out the '/' (/media/root-ro)
  line in /etc/fstab.  So essentially:
   - LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
   + #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0

  Since that happens in the initramfs before systemd ever generates mount
  options, it has the desired affect.  And /media/root-ro is already mounted
  before systemd starts.

  [Test Case]
  ## setup system to build maas images
  $ sudo apt-get install -qy --no-install-recommends bzr
  $ bzr branch lp:maas-images
  $ cd maas-images
  $ ./system-setup

  ## download the reference squashfs images.
  $ arch=amd64
  $ burl=http://cloud-images.ubuntu.com/
  # download reference squashfs images
  $ for rel in xenial zesty artful; do
   file=../$rel-server-cloudimg-$arch.squashfs
   [ -f "$file" ] && continue
   wget "$burl/$rel/current/$file" -O "$file.tmp" && mv "$file.tmp" "$file";
    done

  ## build maas image output.  This creates a squashfs image and 
kernel/initramfs
  ## files that have the updated packages inside.
  ## It does take a while to run, and lots of cpu and IO.
  ## You can reduce the kernels built by commenting out 'lowlatency' and 'edge'
  ## kernels:
  ##  sed -i -e '/^[ ].*\(lowlatency\|edge\)/s/^/#/' conf/meph-v3.yaml
  # either set 'proposed' or add the repo via M2E_ADD_REPOS
  $ proposed="--proposed"
  $ export M2E_ADD_REPOS=ppa:smoser/cloud-initramfs-tools
  $ for rel in xenial zesty artful; do
    img=../$rel-server-cloudimg-$arch.squashfs
    PATH=$PWD/bin:$PATH ./bin/meph2-build $proposed --config=conf/meph-v3.yaml \
  $arch $rel $(date +"%Y%m%d") $img ../$rel.d/ 2>&1 |
  tee ../$rel.log
    done

  ## After running, you will have files like:
  $ find xenial.d/xenial -type f | sort
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/squashfs
  xenial.d/xenial/amd64/20171221/squashfs.manifest

  ## You can verify in the $rel.log files you have 'Setting up cloud-initramfs-'
  $ grep '^Setting up overlayroot' xenial.log
  Setting up overlayroot (0.27ubuntu1.5~ppa16.04.1) ...

  ## Now download the test-boot script, provide it a directory and
  ## the squashfs, kernel, initramfs

  $ ./test-boot test-x xenial.d/xenial/amd64/20171221/squashfs \
  

[Group.of.nepali.translators] [Bug 1723183] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for cloud-initramfs-tools
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

** Changed in: cloud-initramfs-tools (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1723183

Title:
  transient systemd ordering issue when using overlayroot

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Zesty:
  Won't Fix
Status in cloud-initramfs-tools source package in Artful:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  Overlayfs allows a user to mount the root filesystem read-only
  and put an overlay over it.
  It handles mounting of the root filesystem in the initramfs, and updates
  /etc/fstab to account for non-root filesystems and generally make
  /etc/fstab "correct".

  systemd can get confused by a /etc/fstab that looks like this:

     LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
     /media/root-ro/ / overlay lowerdir=...

  It would not recognize that the LABEL=cloudimg-rootfs image *was* mounted.
  This would lead to boot ordering cycles.  The fix that was ultimately
  applied was just to comment out the line for /media/root-ro.

  That way systemd wouldnt try to ensure that /media/root-ro got
  mounted.

  The fix that was put in place was just to comment out the '/' (/media/root-ro)
  line in /etc/fstab.  So essentially:
   - LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
   + #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0

  Since that happens in the initramfs before systemd ever generates mount
  options, it has the desired affect.  And /media/root-ro is already mounted
  before systemd starts.

  [Test Case]
  ## setup system to build maas images
  $ sudo apt-get install -qy --no-install-recommends bzr
  $ bzr branch lp:maas-images
  $ cd maas-images
  $ ./system-setup

  ## download the reference squashfs images.
  $ arch=amd64
  $ burl=http://cloud-images.ubuntu.com/
  # download reference squashfs images
  $ for rel in xenial zesty artful; do
   file=../$rel-server-cloudimg-$arch.squashfs
   [ -f "$file" ] && continue
   wget "$burl/$rel/current/$file" -O "$file.tmp" && mv "$file.tmp" "$file";
    done

  ## build maas image output.  This creates a squashfs image and 
kernel/initramfs
  ## files that have the updated packages inside.
  ## It does take a while to run, and lots of cpu and IO.
  ## You can reduce the kernels built by commenting out 'lowlatency' and 'edge'
  ## kernels:
  ##  sed -i -e '/^[ ].*\(lowlatency\|edge\)/s/^/#/' conf/meph-v3.yaml
  # either set 'proposed' or add the repo via M2E_ADD_REPOS
  $ proposed="--proposed"
  $ export M2E_ADD_REPOS=ppa:smoser/cloud-initramfs-tools
  $ for rel in xenial zesty artful; do
    img=../$rel-server-cloudimg-$arch.squashfs
    PATH=$PWD/bin:$PATH ./bin/meph2-build $proposed --config=conf/meph-v3.yaml \
  $arch $rel $(date +"%Y%m%d") $img ../$rel.d/ 2>&1 |
  tee ../$rel.log
    done

  ## After running, you will have files like:
  $ find xenial.d/xenial -type f | sort
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/squashfs
  xenial.d/xenial/amd64/20171221/squashfs.manifest

  ## You can verify in the $rel.log files you have 'Setting up cloud-initramfs-'
  $ grep '^Setting up overlayroot' xenial.log
  Setting up overlayroot (0.27ubuntu1.5~ppa16.04.1) ...

  ## Now download the test-boot script, provide it a directory and
  ## the squashfs, kernel, initramfs

  $ ./test-boot test-x xenial.d/xenial/amd64/20171221/squashfs \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd

  $ r=zesty; ./test-boot work.d $r.d/*/amd64/*/squashfs 
$r.d/*/amd64/*/ga-*/generic/boot-kernel $r.d/*/amd64/*/ga-*/generic/boot-initrd
  Now, do:
    cd work.d
    ./boot

  ## Running ./boot will serve the squashfs image over http, and then
  ## boot the kernel and initrd with a kernel command line of
  ##root=http:///squashfs
  ## and
  ##

[Group.of.nepali.translators] [Bug 1728048] Re: squashfs url matching is too strict

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.5

---
cloud-initramfs-tools (0.27ubuntu1.5) xenial; urgency=medium

  * sync with upstream at 0.40ubuntu1
- whitespace changes.
- rooturl: adjust squashfs url matching to not require '.'.
  Previously it would match *.squashfs or *.squash
  Now it will match *squashfs or *squash.  (LP: #1728048)
- updateroot/*, debian/control: new package 'cloud-initramfs-updateroot'
- debian/README.source: update upstream information for move to git.
- overlayroot: change from storing password in
  /run/initramfs/overlayroot.passwd rather than randomly generated
  /run/initramfs/overlayroot.XX
- overlayroot: avoid confusing systemd (LP: #1723183)
   + Mark / as 'noauto' in the newly written /etc/fstab
   + Comment out the read-only line for /.

 -- Scott Moser   Fri, 15 Dec 2017 15:57:35 -0500

** Changed in: cloud-initramfs-tools (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/1728048

Title:
  squashfs url matching is too strict

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Zesty:
  Won't Fix
Status in cloud-initramfs-tools source package in Artful:
  Fix Released

Bug description:
   Begin SRU Template ===
  [Impact]
  Squashfs images published by Ubuntu on http://cloud-images.ubuntu.com
  end in '.squashfs' and on http://images.maas.io/ephemeral-v3/
  the files are named 'squashfs'.

  When you boot an initramfs with rooturl it would automatically
  determine/assume that content is squashfs if it ended in
  '.squash' or '.squashfs'.

  The filter was just too strict and would thus not match
    http://images.maas.io/ephemeral-v3//squashfs

  That meant a usage would have to re-publish the url.

  [Test Case]
  ## setup system to build maas images
  $ sudo apt-get install -qy --no-install-recommends bzr
  $ bzr branch lp:maas-images
  $ cd maas-images
  $ ./system-setup

  ## download the reference squashfs images.
  $ arch=amd64
  $ burl=http://cloud-images.ubuntu.com/server
  # download reference squashfs images
  $ for rel in xenial zesty artful; do
file=../$rel-server-cloudimg-$arch.squashfs;
[ -f "$file" ] && continue;
wget "$burl/$rel/current/${file#*/}" -O "$file.tmp" &&
  mv "$file.tmp" "$file"
  done

  ## build maas image output.  This creates a squashfs image and 
kernel/initramfs
  ## files that have the updated packages inside.
  ## It does take a while to run, and lots of cpu and IO.
  ## You can reduce the kernels built by commenting out 'lowlatency' and 'edge'
  ## kernels:
  ##  sed -i -e '/^[ ].*\(lowlatency\|edge\)/s/^/#/' conf/meph-v3.yaml
  # either set 'proposed' or add the repo via M2E_ADD_REPOS
  $ proposed="--proposed"
  $ export M2E_ADD_REPOS=ppa:smoser/cloud-initramfs-tools
  $ for rel in xenial zesty artful; do
    img=../$rel-server-cloudimg-$arch.squashfs
    PATH=$PWD/bin:$PATH ./bin/meph2-build $proposed --config=conf/meph-v3.yaml \
  $arch $rel $(date +"%Y%m%d") $img ../$rel.d/ 2>&1 |
  tee ../$rel.log
    done

  ## After running, you will have files like:
  $ find xenial.d/xenial -type f | sort
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/squashfs
  xenial.d/xenial/amd64/20171221/squashfs.manifest

  ## You can verify in the $rel.log files you have 'Setting up cloud-initramfs-'
  $ grep '^Setting up overlayroot' xenial.log
  Setting up overlayroot (0.27ubuntu1.5~ppa16.04.1) ...

  ## Now download the test-boot script, provide it a directory and
  ## the squashfs, kernel, initramfs

  $ ./test-boot test-x xenial.d/xenial/amd64/20171221/squashfs \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd

  $ r=zesty; ./test-boot work.d $r.d/*/amd64/*/squashfs 
$r.d/*/amd64/*/ga-*/generic/boot-kernel $r.d/*/amd64/*/ga-*/generic/boot-initrd
  Now, do:
    cd work.d
    ./boot

  ## Running ./boot will serve the squashfs image over http, and then
  ## boot the kernel and initrd with a kernel command line of
  ##root=http:///squashfs
  ## and
  ##ds=nocloud-net;seedfrom=http://10.0.2.2:/
  ## which will the read the 'user-data' and 'meta-data' files in that dir.
  ##
  ## The result is that you can log in with 'ubuntu' and 'passw0rd'

  ## Then collect some information
  # 

[Group.of.nepali.translators] [Bug 1723183] Re: transient systemd ordering issue when using overlayroot

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.39ubuntu1.1

---
cloud-initramfs-tools (0.39ubuntu1.1) artful; urgency=medium

  * sync with upstream at 0.40ubuntu1
- rooturl: adjust squashfs url matching to not require '.'.
  Previously it would match *.squashfs or *.squash
  Now it will match *squashfs or *.squash.  (LP: #1728048)
- overlayroot: avoid confusing systemd by commenting out read-only
  line for /. (LP: #1723183)
- overlayroot: remove unused variable 'rel_root'.

 -- Scott Moser   Fri, 15 Dec 2017 15:54:28 -0500

** Changed in: cloud-initramfs-tools (Ubuntu Artful)
   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/1723183

Title:
  transient systemd ordering issue when using overlayroot

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Zesty:
  Won't Fix
Status in cloud-initramfs-tools source package in Artful:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  Overlayfs allows a user to mount the root filesystem read-only
  and put an overlay over it.
  It handles mounting of the root filesystem in the initramfs, and updates
  /etc/fstab to account for non-root filesystems and generally make
  /etc/fstab "correct".

  systemd can get confused by a /etc/fstab that looks like this:

     LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
     /media/root-ro/ / overlay lowerdir=...

  It would not recognize that the LABEL=cloudimg-rootfs image *was* mounted.
  This would lead to boot ordering cycles.  The fix that was ultimately
  applied was just to comment out the line for /media/root-ro.

  That way systemd wouldnt try to ensure that /media/root-ro got
  mounted.

  The fix that was put in place was just to comment out the '/' (/media/root-ro)
  line in /etc/fstab.  So essentially:
   - LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
   + #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0

  Since that happens in the initramfs before systemd ever generates mount
  options, it has the desired affect.  And /media/root-ro is already mounted
  before systemd starts.

  [Test Case]
  ## setup system to build maas images
  $ sudo apt-get install -qy --no-install-recommends bzr
  $ bzr branch lp:maas-images
  $ cd maas-images
  $ ./system-setup

  ## download the reference squashfs images.
  $ arch=amd64
  $ burl=http://cloud-images.ubuntu.com/
  # download reference squashfs images
  $ for rel in xenial zesty artful; do
   file=../$rel-server-cloudimg-$arch.squashfs
   [ -f "$file" ] && continue
   wget "$burl/$rel/current/$file" -O "$file.tmp" && mv "$file.tmp" "$file";
    done

  ## build maas image output.  This creates a squashfs image and 
kernel/initramfs
  ## files that have the updated packages inside.
  ## It does take a while to run, and lots of cpu and IO.
  ## You can reduce the kernels built by commenting out 'lowlatency' and 'edge'
  ## kernels:
  ##  sed -i -e '/^[ ].*\(lowlatency\|edge\)/s/^/#/' conf/meph-v3.yaml
  # either set 'proposed' or add the repo via M2E_ADD_REPOS
  $ proposed="--proposed"
  $ export M2E_ADD_REPOS=ppa:smoser/cloud-initramfs-tools
  $ for rel in xenial zesty artful; do
    img=../$rel-server-cloudimg-$arch.squashfs
    PATH=$PWD/bin:$PATH ./bin/meph2-build $proposed --config=conf/meph-v3.yaml \
  $arch $rel $(date +"%Y%m%d") $img ../$rel.d/ 2>&1 |
  tee ../$rel.log
    done

  ## After running, you will have files like:
  $ find xenial.d/xenial -type f | sort
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/squashfs
  xenial.d/xenial/amd64/20171221/squashfs.manifest

  ## You can verify in the $rel.log files you have 'Setting up cloud-initramfs-'
  $ grep '^Setting up overlayroot' xenial.log
  Setting up overlayroot (0.27ubuntu1.5~ppa16.04.1) ...

  ## Now download the test-boot script, provide it a directory and
  ## the squashfs, kernel, initramfs

  $ ./test-boot test-x xenial.d/xenial/amd64/20171221/squashfs \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd

  $ r=zesty; ./test-boot work.d $r.d/*/amd64/*/squashfs 
$r.d/*/amd64/*/ga-*/generic/boot-kernel $r.d/*/amd64/*/ga-*/generic/boot-initrd
  Now, do:
    cd work.d
    ./boot

  ## Running ./boot will serve the squashfs image over http, and 

[Group.of.nepali.translators] [Bug 1728048] Re: squashfs url matching is too strict

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-initramfs-tools - 0.39ubuntu1.1

---
cloud-initramfs-tools (0.39ubuntu1.1) artful; urgency=medium

  * sync with upstream at 0.40ubuntu1
- rooturl: adjust squashfs url matching to not require '.'.
  Previously it would match *.squashfs or *.squash
  Now it will match *squashfs or *.squash.  (LP: #1728048)
- overlayroot: avoid confusing systemd by commenting out read-only
  line for /. (LP: #1723183)
- overlayroot: remove unused variable 'rel_root'.

 -- Scott Moser   Fri, 15 Dec 2017 15:54:28 -0500

** Changed in: cloud-initramfs-tools (Ubuntu Artful)
   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/1728048

Title:
  squashfs url matching is too strict

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Fix Released
Status in cloud-initramfs-tools source package in Zesty:
  Won't Fix
Status in cloud-initramfs-tools source package in Artful:
  Fix Released

Bug description:
   Begin SRU Template ===
  [Impact]
  Squashfs images published by Ubuntu on http://cloud-images.ubuntu.com
  end in '.squashfs' and on http://images.maas.io/ephemeral-v3/
  the files are named 'squashfs'.

  When you boot an initramfs with rooturl it would automatically
  determine/assume that content is squashfs if it ended in
  '.squash' or '.squashfs'.

  The filter was just too strict and would thus not match
    http://images.maas.io/ephemeral-v3//squashfs

  That meant a usage would have to re-publish the url.

  [Test Case]
  ## setup system to build maas images
  $ sudo apt-get install -qy --no-install-recommends bzr
  $ bzr branch lp:maas-images
  $ cd maas-images
  $ ./system-setup

  ## download the reference squashfs images.
  $ arch=amd64
  $ burl=http://cloud-images.ubuntu.com/server
  # download reference squashfs images
  $ for rel in xenial zesty artful; do
file=../$rel-server-cloudimg-$arch.squashfs;
[ -f "$file" ] && continue;
wget "$burl/$rel/current/${file#*/}" -O "$file.tmp" &&
  mv "$file.tmp" "$file"
  done

  ## build maas image output.  This creates a squashfs image and 
kernel/initramfs
  ## files that have the updated packages inside.
  ## It does take a while to run, and lots of cpu and IO.
  ## You can reduce the kernels built by commenting out 'lowlatency' and 'edge'
  ## kernels:
  ##  sed -i -e '/^[ ].*\(lowlatency\|edge\)/s/^/#/' conf/meph-v3.yaml
  # either set 'proposed' or add the repo via M2E_ADD_REPOS
  $ proposed="--proposed"
  $ export M2E_ADD_REPOS=ppa:smoser/cloud-initramfs-tools
  $ for rel in xenial zesty artful; do
    img=../$rel-server-cloudimg-$arch.squashfs
    PATH=$PWD/bin:$PATH ./bin/meph2-build $proposed --config=conf/meph-v3.yaml \
  $arch $rel $(date +"%Y%m%d") $img ../$rel.d/ 2>&1 |
  tee ../$rel.log
    done

  ## After running, you will have files like:
  $ find xenial.d/xenial -type f | sort
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-initrd
  xenial.d/xenial/amd64/20171221/hwe-16.04/generic/boot-kernel
  xenial.d/xenial/amd64/20171221/squashfs
  xenial.d/xenial/amd64/20171221/squashfs.manifest

  ## You can verify in the $rel.log files you have 'Setting up cloud-initramfs-'
  $ grep '^Setting up overlayroot' xenial.log
  Setting up overlayroot (0.27ubuntu1.5~ppa16.04.1) ...

  ## Now download the test-boot script, provide it a directory and
  ## the squashfs, kernel, initramfs

  $ ./test-boot test-x xenial.d/xenial/amd64/20171221/squashfs \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-kernel \
  xenial.d/xenial/amd64/20171221/ga-16.04/generic/boot-initrd

  $ r=zesty; ./test-boot work.d $r.d/*/amd64/*/squashfs 
$r.d/*/amd64/*/ga-*/generic/boot-kernel $r.d/*/amd64/*/ga-*/generic/boot-initrd
  Now, do:
    cd work.d
    ./boot

  ## Running ./boot will serve the squashfs image over http, and then
  ## boot the kernel and initrd with a kernel command line of
  ##root=http:///squashfs
  ## and
  ##ds=nocloud-net;seedfrom=http://10.0.2.2:/
  ## which will the read the 'user-data' and 'meta-data' files in that dir.
  ##
  ## The result is that you can log in with 'ubuntu' and 'passw0rd'

  ## Then collect some information
  # you'll see the 'LABEL=' entry is commented out.
  $ cat /etc/fstab
  # local-fs.target should be fine
  $ systemctl status local-fs.target --no-pager
  # just for record
  $ cat /proc/cmdline

  [Regression Potential]
  Very low.
  If a url does not match, rooturl would just complain and do nothing.
  This just extends the things that match.

  

[Group.of.nepali.translators] [Bug 1730343] Re: firmware update breaks Ubuntu

[Łukasz Zemczak]

The latest upload consists of a very high number of patches which might
quickly get hard to maintain. For the future maybe it would make sense
to backport the whole 9 version to xenial instead of patching just one
component with the code from the 9-codebase.

** Changed in: fwupdate-signed (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

** Changed in: fwupdate (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1730343

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  Fix Released
Status in fwupd package in Ubuntu:
  Invalid
Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupd source package in Xenial:
  Invalid
Status in fwupdate source package in Xenial:
  Fix Committed
Status in fwupdate-signed source package in Xenial:
  Fix Committed
Status in fwupd source package in Zesty:
  Invalid
Status in fwupdate source package in Zesty:
  Won't Fix
Status in fwupdate-signed source package in Zesty:
  Won't Fix
Status in fwupd source package in Artful:
  Invalid
Status in fwupdate source package in Artful:
  Fix Released
Status in fwupdate-signed source package in Artful:
  Fix Released
Status in fwupd source package in Bionic:
  Invalid
Status in fwupdate source package in Bionic:
  Fix Released
Status in fwupdate-signed source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * A few users have reported instances of not being able to boot into Ubuntu 
after a firmware update.  This is suspected to be caused by a missing Ubuntu 
boot entry.
   * fwupdate adds an entry for doing the update to the BootOrder, but doesn't 
remove it.  BIOS auto-creation for making boot entries typically depends on the 
BootOrder being empty.

  
  * This affects all releases of fwupdate since the code to add to BootOrder was
  also backported into the Ubuntu 16.04 release of fwupdate (0.5-2ubuntu5)

  [Test Case]

  * Perform a UEFI BIOS update after installing this package.
  * Ensure the system boots and there is no longer a "Linux Firmware Updater" 
entry
  present in the efibootmgr -v output.

  
  [Regression Potential] 

  * Regressions are possible to manifest if any BIOS depends on the
  previous behavior.

  * The fixes that were backported have been upstream for a few months and no
  concerns have been raised upstream from them.

  [Other Info]
  Two users have reported that fwupd breaks their Ubuntu installation because 
the "Ubuntu" EFI boot option disappears after an update.
  Upstream issue: https://github.com/rhboot/fwupdate/issues/86

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1730343/+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