date:20171219

4.13.0-1002.3 - azure
Regression test CMPL.

Issue to note in x86_64 (azure):
  ebizzy - failed on one instance (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 - test disabled
  ubuntu_ltp - test disabled
  ubuntu_lttng_smoke_test - some instances (Standard_A0) failed with dpkg 
issue, 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


** 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)

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

Title:
  linux-azure: 4.13.0-1002.3 -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:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 4.13.0-1002.3 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
  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/1737951/+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 1737945] Re: linux-hwe: 4.10.0-43.47~16.04.1 -proposed tracker

No bug was tagged with verification-needed for this kernel.


** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/verification-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-hwe: 4.10.0-43.47~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe 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: 1737942
  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/1737945/+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 1737920] Re: linux-aws: 4.4.0-1045.54 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu 
Lin (cypressyew)

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

Title:
  linux-aws: 4.4.0-1045.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1737916
  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/1737920/+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 1737925] Re: linux-raspi2: 4.4.0-1081.89 -proposed tracker

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  linux-raspi2: 4.4.0-1081.89 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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: 1737916
  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/1737925/+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 1738206] Re: linux-azure-edge: 4.14.0-1002.2 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu 
Lin (cypressyew)

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

Title:
  linux-azure-edge: 4.14.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure-edge package in Ubuntu:
  Invalid
Status in linux-azure-edge source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-1002.2 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
  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/1738206/+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 1713004] Re: Temporary files left under /var/tmp by mkinitramfs

This bug was fixed in the package initramfs-tools - 0.122ubuntu8.10

---
initramfs-tools (0.122ubuntu8.10) xenial; urgency=medium

  * mkinitramfs: Delete or report temporary files in /var/tmp/ on failure.
(LP: #1713004)

 -- Brian Murray   Tue, 05 Dec 2017 11:17:43 -0800

** Changed in: 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/1713004

Title:
  Temporary files left under /var/tmp by mkinitramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  Test Case
  -
  1) confirm there are no mkinitramfs junk files in /var/tmp
  2) run 'sudo update-initramfs -k all -u -v'
  3) interrupt update-initramfs with Ctrl-C
  4) observe junk files in /var/tmp e.g. /var/tmp/mkinitramfs*

  With the version of initramfs-tools in -proposed you should see not
  have any leftovers in /var/tmp.

  I recently ran out of disk space on my / mount.  While looking for
  what consumed the disk I noticed a large number (130) of directories
  with names / paths beginning /var/tmp/mkinitramfs.  These directories
  seem to be either ~103 MB or ~927 MB in size.  Many of these files are
  months old, some are almost a year.

  Having had a quick look about for an explanation as to why these files
  are here and found Debian Bug #814345.  That explains that temporary
  files are left behind by the initramfs-tools if something fails in the
  process.  If this is the cause of my files then updating the Ubuntu
  package to version 0.123 should resolve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 25 09:40:41 2017
  InstallationDate: Installed on 2015-03-12 (896 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1713004/+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 1723198] Re: [SRU] upgrade from 14.04 to 16.04 fails with: ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned

This bug was fixed in the package ca-certificates-java - 20160321ubuntu1

---
ca-certificates-java (20160321ubuntu1) xenial; urgency=medium

  * Depend on openjdk-8 instead of openjdk-7. (LP: #1723198)

 -- Eric Desrochers   Thu, 14 Dec 2017
15:38:26 -0500

** Changed in: ca-certificates-java (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/1723198

Title:
  [SRU] upgrade from 14.04 to 16.04 fails with: ca-certificates
  20170717~16.04.1 failed to install/upgrade: triggers looping,
  abandoned

Status in ca-certificates-java package in Ubuntu:
  Fix Released
Status in ca-certificates-java source package in Xenial:
  Fix Released
Status in ca-certificates-java source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  ca-certificates-java currently depend on openjdk-7 which no longer
  exist after Trusty. It triggers failures while doing release upgrade,
  due to triggers loop.

  [Test Case]

  # Install Ubuntu server 14.04.5 + all the updates.
  (I used "uvt-kvm create trustylp1723198 release=trusty")

  sudo apt-get update
  sudo apt-get dist-upgrade

  # Install ca-certificates-java and man-db.
  sudo apt-get install ca-certificates-java man-db

  # Upgrade to 16.04 LTS.
  sudo do-release-upgrade

  # Error:
  ..
  Removing ca-certificates-java (20130815ubuntu1) ...
  Removing openjdk-7-jre-headless:amd64 (7u151-2.6.11-2ubuntu0.14.04.1) ...
  dpkg: cycle found while processing triggers:
  chain of packages whose triggers are or may be responsible:
  man-db -> ca-certificates
  packages' pending triggers which are or may be unresolvable:
  ca-certificates: update-ca-certificates
  man-db: /usr/share/man
  dpkg: error processing package ca-certificates (--remove):
  triggers looping, abandoned

  [Regression Potential]

   * Regression is low risk. Xenial and late doesn't have openjdk-7
  available in the archive. It has openjdk-8. This will have the effect
  to make the release upgrade to work correctly when ca-certificates-
  java is installed. This patch has been already proven to work in
  Artful, Bionic and Debian upstream.

  * The current "ca-certificates-java" installs openjdk-9 (universe),
  with this fix the new package will install openjdk-8 (main).  This is
  a change in behaviour, but ca-certificates-java's dependency on
  openjdk-7-jre-headless | java-runtime-headless means the package
  manager handling of the dependency is inconsistent anyway. For more
  detail: See Comment #16, #17 & #18.

  [Other Info]

   * Debian bug :
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863803

   * Debian commit:
   
https://anonscm.debian.org/cgit/pkg-java/ca-certificates-java.git/commit/?id=0ddf3c9

  [Original Description]
  Test Case:
  1. Install Ubuntu server 14.04.5 + all the updates
  2. Install ca-certificates-java and man-db
  3. Reboot
  4. Upgrade to 16.04 LTS with do-release-upgrade and proceed with the upgrade

  Actual Result
  Upgrade fails with
  Removing ca-certificates-java (20130815ubuntu1) ...
  Removing openjdk-7-jre-headless:amd64 (7u151-2.6.11-2ubuntu0.14.04.1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    man-db -> ca-certificates
   packages' pending triggers which are or may be unresolvable:
    ca-certificates: update-ca-certificates
    man-db: /usr/share/man
  dpkg: error processing package ca-certificates (--remove):
   triggers looping, abandoned

  I have no further information to give at this time except to say that
  there were several errors during the upgrade process from 14.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Oct 12 17:52:19 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2013-11-16 (1425 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1723198/+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 1723198] Re: [SRU] upgrade from 14.04 to 16.04 fails with: ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned

This bug was fixed in the package ca-certificates-java - 20161107ubuntu1

---
ca-certificates-java (20161107ubuntu1) zesty; urgency=medium

  * Depend on openjdk-8 instead of openjdk-7. (LP: #1723198)

 -- Eric Desrochers   Fri, 15 Dec 2017
00:12:19 -0500

** Changed in: ca-certificates-java (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] upgrade from 14.04 to 16.04 fails with: ca-certificates
  20170717~16.04.1 failed to install/upgrade: triggers looping,
  abandoned

Status in ca-certificates-java package in Ubuntu:
  Fix Released
Status in ca-certificates-java source package in Xenial:
  Fix Released
Status in ca-certificates-java source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  ca-certificates-java currently depend on openjdk-7 which no longer
  exist after Trusty. It triggers failures while doing release upgrade,
  due to triggers loop.

  [Test Case]

  # Install Ubuntu server 14.04.5 + all the updates.
  (I used "uvt-kvm create trustylp1723198 release=trusty")

  sudo apt-get update
  sudo apt-get dist-upgrade

  # Install ca-certificates-java and man-db.
  sudo apt-get install ca-certificates-java man-db

  # Upgrade to 16.04 LTS.
  sudo do-release-upgrade

  # Error:
  ..
  Removing ca-certificates-java (20130815ubuntu1) ...
  Removing openjdk-7-jre-headless:amd64 (7u151-2.6.11-2ubuntu0.14.04.1) ...
  dpkg: cycle found while processing triggers:
  chain of packages whose triggers are or may be responsible:
  man-db -> ca-certificates
  packages' pending triggers which are or may be unresolvable:
  ca-certificates: update-ca-certificates
  man-db: /usr/share/man
  dpkg: error processing package ca-certificates (--remove):
  triggers looping, abandoned

  [Regression Potential]

   * Regression is low risk. Xenial and late doesn't have openjdk-7
  available in the archive. It has openjdk-8. This will have the effect
  to make the release upgrade to work correctly when ca-certificates-
  java is installed. This patch has been already proven to work in
  Artful, Bionic and Debian upstream.

  * The current "ca-certificates-java" installs openjdk-9 (universe),
  with this fix the new package will install openjdk-8 (main).  This is
  a change in behaviour, but ca-certificates-java's dependency on
  openjdk-7-jre-headless | java-runtime-headless means the package
  manager handling of the dependency is inconsistent anyway. For more
  detail: See Comment #16, #17 & #18.

  [Other Info]

   * Debian bug :
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863803

   * Debian commit:
   
https://anonscm.debian.org/cgit/pkg-java/ca-certificates-java.git/commit/?id=0ddf3c9

  [Original Description]
  Test Case:
  1. Install Ubuntu server 14.04.5 + all the updates
  2. Install ca-certificates-java and man-db
  3. Reboot
  4. Upgrade to 16.04 LTS with do-release-upgrade and proceed with the upgrade

  Actual Result
  Upgrade fails with
  Removing ca-certificates-java (20130815ubuntu1) ...
  Removing openjdk-7-jre-headless:amd64 (7u151-2.6.11-2ubuntu0.14.04.1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    man-db -> ca-certificates
   packages' pending triggers which are or may be unresolvable:
    ca-certificates: update-ca-certificates
    man-db: /usr/share/man
  dpkg: error processing package ca-certificates (--remove):
   triggers looping, abandoned

  I have no further information to give at this time except to say that
  there were several errors during the upgrade process from 14.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Oct 12 17:52:19 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2013-11-16 (1425 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1723198/+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 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

This bug was fixed in the package unattended-upgrades - 0.98ubuntu2

---
unattended-upgrades (0.98ubuntu2) bionic; urgency=medium

  * unattended-upgrades: Do not reboot during a dry-run. (LP: #1269177)

 -- Brian Murray   Tue, 19 Dec 2017 11:04:52 -0800

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  New
Status in unattended-upgrades source package in Zesty:
  New
Status in unattended-upgrades source package in Artful:
  New
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  Much to my surprise, when I did a dry-run test of unattended-upgrades
  my server was forcibly rebooted. I must have had the file '/var/run
  /reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages: 
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1269177/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot

2017-12-19 Thread Steve Langasek

** Changed in: systemd (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Zesty)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Artful)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Bionic)
   Status: Incomplete => 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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in systemd source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Won't Fix

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax

[Group.of.nepali.translators] [Bug 1734038] Re: snap-confine profile uses 'include' instead of '#include' which breaks apparmor-utils python tools

2017-12-19 Thread Matthew Mercaldi

** Changed in: snapd (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: snapd (Ubuntu Zesty)
   Status: New => Invalid

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

Title:
  snap-confine profile uses 'include' instead of '#include' which breaks
  apparmor-utils python tools

Status in snapd package in Ubuntu:
  In Progress
Status in snapd source package in Trusty:
  New
Status in snapd source package in Xenial:
  Fix Released
Status in snapd source package in Zesty:
  Invalid
Status in snapd source package in Artful:
  New
Status in snapd source package in Bionic:
  In Progress

Bug description:
  Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41,
  across different architectures

  Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error 
message:
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,

  (BTW the include and this ld.so.cache are not in the same line, please
  refer to comment #3 for attachment)

  This issue will gone if you downgrade the snapd and ubuntu-core-launcher 
package:
  sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5

  Debug information:
  ubuntu@kernel01:~$ snap version
  snap2.29.3
  snapd   2.29.3
  series  16
  ubuntu  16.04
  kernel  4.4.0-102-generic

  ubuntu@kernel01:~$ apt list snapd
  Listing... Done
  snapd/xenial-proposed,now 2.29.3 s390x [installed]
  N: There are 2 additional versions. Please use the '-a' switch to see them.

  ubuntu@kernel01:~$ apt list apparmor -a
  Listing... Done
  apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed]
  apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x
  apparmor/xenial 2.10.95-0ubuntu2 s390x

  Steps to run the Apparmor test from QA Regression testing suite:
1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing
2. sudo ./qa-regression-testing/scripts/test-apparmor.py

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-102-generic 4.4.0-102.125
  ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98
  Uname: Linux 4.4.0-102-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Nov 23 01:36:31 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-102-generic N/A
   linux-backports-modules-4.4.0-102-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1734038/+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 1729531] Re: SRU 1.2 and 1.3 tracking bug

This bug was fixed in the package ubuntu-image - 1.3+17.04ubuntu1

---
ubuntu-image (1.3+17.04ubuntu1) zesty; urgency=medium

  * Remove the snapcraft dependency by moving the gadget tree priming step away
from ubuntu-image.  (LP:1734655)
  * Add support for defining the livecd-rootfs configuration path through
an environment variable.  (LP:1734949)
  * SRU tracking number LP: #1729531

ubuntu-image (1.2+17.04ubuntu1) zesty; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * SRU tracking number LP: #1729531
  * Add a generic hook mechanism and add our first supported snap-image hook:
post-populate-rootfs.  (LP:1672436)
  * Document the newly added hook API in the ubuntu-image manpage.
(LP:1715849)
  * Make sure ubuntu-image has 100% code-coverage after getting the classic
image support added.

  [ Gary Wang ]
  * Add classic image creation support.  (LP:1726391)

 -- Łukasz 'sil2100' Zemczak   Mon, 27 Nov
2017 11:12:08 +0100

** Changed in: ubuntu-image (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-image (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/1729531

Title:
  SRU 1.2 and 1.3 tracking bug

Status in Ubuntu Image:
  In Progress
Status in ubuntu-image package in Ubuntu:
  Fix Released
Status in ubuntu-image source package in Xenial:
  Fix Released
Status in ubuntu-image source package in Zesty:
  Fix Released
Status in ubuntu-image source package in Artful:
  Fix Released

Bug description:
  New SRU tracking bug (with exception) for ubuntu-image 1.2 in Artful,
  Zesty and Xenial.

  See https://wiki.ubuntu.com/UbuntuImageUpdates

  [Impact]

  ubuntu-image 1.2 and 1.3 fix some bugs and pay down some technical
  debt. It includes a new hook mechanism, support for building classic
  Ubuntu preinstalled images and updates the documentation. For the
  classic image support to work correctly, the corresponding livecd-
  rootfs changes need to be released as well.

  [Test Case]

  Create an image using the official amd64 model assertion. Ensure that
  the resulting image boots to 'press enter to configure' phase. Create
  an ubuntu-cpc project classic image using a modified amd64 gadget tree
  [1] and make sure it boots.

  [Regression Potential]

  * ubuntu-image may not produce a bootable image

  [1] For example: https://github.com/sil2100/pc-amd64-gadget

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-image/+bug/1729531/+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 1729531] Re: SRU 1.2 and 1.3 tracking bug

This bug was fixed in the package ubuntu-image - 1.3+17.10ubuntu1

---
ubuntu-image (1.3+17.10ubuntu1) artful; urgency=medium

  * Remove the snapcraft dependency by moving the gadget tree priming step away
from ubuntu-image.  (LP:1734655)
  * Add support for defining the livecd-rootfs configuration path through
an environment variable.  (LP:1734949)
  * SRU tracking number LP: #1729531

ubuntu-image (1.2+17.10ubuntu1) artful; urgency=medium

  [ Łukasz 'sil2100' Zemczak ]
  * SRU tracking number LP: #1729531
  * Add a generic hook mechanism and add our first supported snap-image hook:
post-populate-rootfs.  (LP:1672436)
  * Document the newly added hook API in the ubuntu-image manpage.
(LP:1715849)
  * Make sure ubuntu-image has 100% code-coverage after getting the classic
image support added.

  [ Gary Wang ]
  * Add classic image creation support.  (LP:1726391)

 -- Łukasz 'sil2100' Zemczak   Mon, 27 Nov
2017 11:12:08 +0100

** Changed in: ubuntu-image (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/1729531

Title:
  SRU 1.2 and 1.3 tracking bug

Status in Ubuntu Image:
  In Progress
Status in ubuntu-image package in Ubuntu:
  Fix Released
Status in ubuntu-image source package in Xenial:
  Fix Released
Status in ubuntu-image source package in Zesty:
  Fix Released
Status in ubuntu-image source package in Artful:
  Fix Released

Bug description:
  New SRU tracking bug (with exception) for ubuntu-image 1.2 in Artful,
  Zesty and Xenial.

  See https://wiki.ubuntu.com/UbuntuImageUpdates

  [Impact]

  ubuntu-image 1.2 and 1.3 fix some bugs and pay down some technical
  debt. It includes a new hook mechanism, support for building classic
  Ubuntu preinstalled images and updates the documentation. For the
  classic image support to work correctly, the corresponding livecd-
  rootfs changes need to be released as well.

  [Test Case]

  Create an image using the official amd64 model assertion. Ensure that
  the resulting image boots to 'press enter to configure' phase. Create
  an ubuntu-cpc project classic image using a modified amd64 gadget tree
  [1] and make sure it boots.

  [Regression Potential]

  * ubuntu-image may not produce a bootable image

  [1] For example: https://github.com/sil2100/pc-amd64-gadget

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-image/+bug/1729531/+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 1727355] Re: Juju attempts to bootstrap bionic by default

This bug was fixed in the package juju-core - 2.3.1-0ubuntu0.17.04.1

---
juju-core (2.3.1-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream release. (LP: #1718213)

juju-core (2.2.6-0ubuntu0.17.04.3) zesty; urgency=medium

  * Only juju 2.3+ supports cidr expansion for no proxy, fix for 2.2

juju-core (2.2.6-0ubuntu0.17.04.2) zesty; urgency=medium

  * Add no_proxy for lxd subnet in support of adt tests

juju-core (2.2.6-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream release. (LP: #1718213)
  * Simplify use of embedded dependencies
  * Remove DH_VERBOSE=1
  * Ensure juju bootstrap succeeds with bionic in distro-info-data (LP: 
#1727355)

juju-core (2.2.4-0ubuntu0.17.04.2) zesty; urgency=medium

  * Fix installation of bash completion scripts.

juju-core (2.2.4-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream release. (LP: #1718213)
  * Remove debian/patches/CVE-2017-9232.patch, included upstream.
  * Improved support for mixing vendored and archive dependencies.
  * Killed old code for building on saucy, precise and with gccgo.
  * Embed Go 1.8.3 as upstream no longer builds with Go 1.6. (Note that
golang-go is still a build dependency as it is required to build the
embedded go 1.8.3).
  * Switch golang.org/x/crypto dependency to vendorized.

 -- Nicholas Skaggs   Wed, 13 Dec 2017
17:38:04 -0500

** Changed in: juju-core (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9232

** Changed in: juju-core (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/1727355

Title:
  Juju attempts to bootstrap bionic by default

Status in juju:
  Fix Released
Status in distro-info-data package in Ubuntu:
  Won't Fix
Status in juju-core package in Ubuntu:
  Invalid
Status in distro-info-data source package in Trusty:
  Won't Fix
Status in juju-core source package in Trusty:
  Invalid
Status in distro-info-data source package in Xenial:
  Fix Released
Status in juju-core source package in Xenial:
  Fix Released
Status in distro-info-data source package in Zesty:
  Fix Released
Status in juju-core source package in Zesty:
  Fix Released
Status in distro-info-data source package in Artful:
  Won't Fix
Status in juju-core source package in Artful:
  Invalid

Bug description:
  This is with 2.2.5 on xenial, with x86 hosts:

  I'm hitting this everytime I try to bootstrap:

  14:01:42 DEBUG juju.cmd.juju.commands bootstrap.go:497 (error details:
  [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:588: failed to
  bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching
  agent binaries available}])

  Full error:
  http://paste.ubuntu.com/25817026/

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1727355/+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 1718213] Re: [SRU] Juju 2.3.1

This bug was fixed in the package juju-core - 2.3.1-0ubuntu0.16.04.1

---
juju-core (2.3.1-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release. (LP: #1718213)

juju-core (2.2.6-0ubuntu0.16.04.3) xenial; urgency=medium

  * Only juju 2.3+ supports cidr expansion for no proxy, fix for 2.2

juju-core (2.2.6-0ubuntu0.16.04.2) xenial; urgency=medium

  * Add no_proxy for lxd subnet in support of adt tests

juju-core (2.2.6-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release. (LP: #1718213)
  * Simplify use of embedded dependencies
  * Remove DH_VERBOSE=1
  * Ensure juju bootstrap succeeds with bionic in distro-info-data (LP: 
#1727355)

juju-core (2.2.4-0ubuntu0.16.04.2) xenial; urgency=medium

  * Fix installation of bash completion scripts.

juju-core (2.2.4-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release. (LP: #1718213)
  * Remove debian/patches/CVE-2017-9232.patch, included upstream.
  * Improved support for mixing vendored and archive dependencies.
  * Killed old code for building on saucy, precise and with gccgo.
  * Embed Go 1.8.3 as upstream no longer builds with Go 1.6.
  * Switch golang.org/x/crypto dependency to vendorized.

 -- Nicholas Skaggs   Tue, 12 Dec 2017
14:41:40 -0500

** Changed in: juju-core (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/1718213

Title:
  [SRU] Juju 2.3.1

Status in juju-core package in Ubuntu:
  Invalid
Status in juju-core source package in Xenial:
  Fix Released
Status in juju-core source package in Zesty:
  Fix Released

Bug description:
  This syncs juju with the upstream release bringing the latest bugfixes
  and enhancements.

  [SRU Information]
  juju-core has a stable release exception, including for major version 
updates, https://wiki.ubuntu.com/JujuUpdates.

  [Impact]
  A full list of targeted bugs can be seen against the milestone, and the 
intervening milestones:

  https://launchpad.net/juju/+milestone/2.0.3
  https://launchpad.net/juju/+milestone/2.0.4
  https://launchpad.net/juju/+milestone/2.1.0
  https://launchpad.net/juju/+milestone/2.1.1
  https://launchpad.net/juju/+milestone/2.1.2
  https://launchpad.net/juju/+milestone/2.1.3
  https://launchpad.net/juju/+milestone/2.2.0
  https://launchpad.net/juju/+milestone/2.2.1
  https://launchpad.net/juju/+milestone/2.2.2
  https://launchpad.net/juju/+milestone/2.2.3
  https://launchpad.net/juju/+milestone/2.2.4
  https://launchpad.net/juju/+milestone/2.2.5
  https://launchpad.net/juju/+milestone/2.2.6
  https://launchpad.net/juju/+milestone/2.3.0
  https://launchpad.net/juju/+milestone/2.3.1

  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here:

  http://qa.jujucharms.com/releases/6058

  In addition, juju has adt test coverage for all supported archs,
  http://autopkgtest.ubuntu.com/packages/j/juju-core/.

  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+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 1718213] Re: [SRU] Juju 2.3.1

This bug was fixed in the package juju-core - 2.3.1-0ubuntu0.17.04.1

---
juju-core (2.3.1-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream release. (LP: #1718213)

juju-core (2.2.6-0ubuntu0.17.04.3) zesty; urgency=medium

  * Only juju 2.3+ supports cidr expansion for no proxy, fix for 2.2

juju-core (2.2.6-0ubuntu0.17.04.2) zesty; urgency=medium

  * Add no_proxy for lxd subnet in support of adt tests

juju-core (2.2.6-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream release. (LP: #1718213)
  * Simplify use of embedded dependencies
  * Remove DH_VERBOSE=1
  * Ensure juju bootstrap succeeds with bionic in distro-info-data (LP: 
#1727355)

juju-core (2.2.4-0ubuntu0.17.04.2) zesty; urgency=medium

  * Fix installation of bash completion scripts.

juju-core (2.2.4-0ubuntu0.17.04.1) zesty; urgency=medium

  * New upstream release. (LP: #1718213)
  * Remove debian/patches/CVE-2017-9232.patch, included upstream.
  * Improved support for mixing vendored and archive dependencies.
  * Killed old code for building on saucy, precise and with gccgo.
  * Embed Go 1.8.3 as upstream no longer builds with Go 1.6. (Note that
golang-go is still a build dependency as it is required to build the
embedded go 1.8.3).
  * Switch golang.org/x/crypto dependency to vendorized.

 -- Nicholas Skaggs   Wed, 13 Dec 2017
17:38:04 -0500

** Changed in: juju-core (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9232

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

Title:
  [SRU] Juju 2.3.1

Status in juju-core package in Ubuntu:
  Invalid
Status in juju-core source package in Xenial:
  Fix Released
Status in juju-core source package in Zesty:
  Fix Released

Bug description:
  This syncs juju with the upstream release bringing the latest bugfixes
  and enhancements.

  [SRU Information]
  juju-core has a stable release exception, including for major version 
updates, https://wiki.ubuntu.com/JujuUpdates.

  [Impact]
  A full list of targeted bugs can be seen against the milestone, and the 
intervening milestones:

  https://launchpad.net/juju/+milestone/2.0.3
  https://launchpad.net/juju/+milestone/2.0.4
  https://launchpad.net/juju/+milestone/2.1.0
  https://launchpad.net/juju/+milestone/2.1.1
  https://launchpad.net/juju/+milestone/2.1.2
  https://launchpad.net/juju/+milestone/2.1.3
  https://launchpad.net/juju/+milestone/2.2.0
  https://launchpad.net/juju/+milestone/2.2.1
  https://launchpad.net/juju/+milestone/2.2.2
  https://launchpad.net/juju/+milestone/2.2.3
  https://launchpad.net/juju/+milestone/2.2.4
  https://launchpad.net/juju/+milestone/2.2.5
  https://launchpad.net/juju/+milestone/2.2.6
  https://launchpad.net/juju/+milestone/2.3.0
  https://launchpad.net/juju/+milestone/2.3.1

  [QA/Testing]
  Juju practices continuous integration and testing of the juju source tree. 
The results for this release can be seen here:

  http://qa.jujucharms.com/releases/6058

  In addition, juju has adt test coverage for all supported archs,
  http://autopkgtest.ubuntu.com/packages/j/juju-core/.

  Finally, manual verification and testing of the package has been done
  per https://wiki.ubuntu.com/JujuUpdates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1718213/+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 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

2017-12-19 Thread Brian Murray

Let's go ahead and reuse this bug although this only happens when there
are no updates available and the previous fix was for when updates were
available.

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Fix Released => 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/1269177

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Xenial:
  New
Status in unattended-upgrades source package in Zesty:
  New
Status in unattended-upgrades source package in Artful:
  New
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  Much to my surprise, when I did a dry-run test of unattended-upgrades
  my server was forcibly rebooted. I must have had the file '/var/run
  /reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages: 
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1269177/+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 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

2017-12-19 Thread Brian Murray

Okay, I've sorted out what's wrong. Thanks!

** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: High
 Assignee: Brian Murray (brian-murray)
   Status: Fix Released

** Also affects: unattended-upgrades (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Xenial:
  New
Status in unattended-upgrades source package in Zesty:
  New
Status in unattended-upgrades source package in Artful:
  New
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  Much to my surprise, when I did a dry-run test of unattended-upgrades
  my server was forcibly rebooted. I must have had the file '/var/run
  /reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages: 
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1269177/+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 1712921] Re: enabling networkd appears to eat up entropy

This bug was fixed in the package nplan - 0.32~17.10.1

---
nplan (0.32~17.10.1) artful; urgency=medium

  * Backport 0.32 to Ubuntu 17.10. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

 -- Mathieu Trudel-Lapierre   Thu, 23 Nov 2017
12:30:51 -0500

** Changed in: nplan (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/1712921

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in nplan source package in Xenial:
  Fix Committed
Status in openssh source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in nplan source package in Zesty:
  Fix Committed
Status in openssh source package in Zesty:
  New
Status in systemd source package in Zesty:
  New
Status in nplan source package in Artful:
  Fix Released
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged
Status in nplan source package in Bionic:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.

  [Test cases]

  == netplan ==
  1) Boot system with netplan config; using networkd renderer
  2) Validate that it starts and does not cause undue delay.
  2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
  3) Validate that config with NetworkManager renderer generates UUIDs.

  [Regression potential]
  Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.

  ---

  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1712921/+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 1713142] Re: Backport netplan 0.32

This bug was fixed in the package nplan - 0.32~17.10.1

---
nplan (0.32~17.10.1) artful; urgency=medium

  * Backport 0.32 to Ubuntu 17.10. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

 -- Mathieu Trudel-Lapierre   Thu, 23 Nov 2017
12:30:51 -0500

** Changed in: nplan (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/1713142

Title:
  Backport netplan 0.32

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Backport features in upstream netplan / netplan in bionic to zesty, xenial.

  [Test cases]

  == Autopkgtests ==
  Run autopkgtests, they should all pass.

  == MTU settings ==
  1) Set a MTU for a device managed by NetworkManager:

  ethernet:
    eth0:
  renderer: NetworkManager
  mtu: 1400
  dhcp4: yes

  2) Verify that the MTU is properly applied to the device.

  [Regression potential]Failure to properly configure existing
  interfaces for MTU settings, IPv6 settings would be regressions; for
  example, if existing network devices were to all get the same MTU, or
  the same MTU as another interface configured in netplan although the
  configuration is not set to apply to them (ie. the config bleeds to
  other devices); then this would be a regression. Any new failures in
  autopkgtests would also be regressions to be investigated as possibly
  caused by the update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1713142/+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 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

This bug was fixed in the package nplan - 0.32~17.10.1

---
nplan (0.32~17.10.1) artful; urgency=medium

  * Backport 0.32 to Ubuntu 17.10. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

 -- Mathieu Trudel-Lapierre   Thu, 23 Nov 2017
12:30:51 -0500

** Changed in: nplan (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/1669564

Title:
  udevadm trigger subsystem-match=net doesn't always run rules because
  of reconfiguration rate-limiting

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Proper udev trigger behavior following a 'netplan apply' is essential to 
having all the configuration applied for an interface.

  [Test case]
  1- Write a netplan configuration file that sets MTU for a device, or renames 
a device.
  2- Run 'netplan apply'
  Validate that all the changes were correctly applied: netplan apply will run 
'udevadm trigger' for the user, and udev should apply all low-level link 
changes (MTU and renames).
  Make sure to watch out for device renames on devices that are blacklisted for 
replugging such as mwifiex, XEN VIF, etc.

  [Regression potential]
  Verification should watch out for a MTU being set, but set to the wrong 
value, or MTUs being applied to all interfaces rather than just the interface 
for which it was set. Users should also watch out for the network device to be 
renamed correctly, and then seen as the correct name and state in both networkd 
and the ip command.

  ---

  1. root@ubuntu:~# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:~# apt-cache policy udev
  udev:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. udevadm trigger --verbose --subsystem-match=net --action=add will run and 
read .link files from /run/systemd/network/10-netplan-interface1.link
  and apply MTU settings

  4. during system boot running (3) does not set the MTU; running (3)
  after boot has completed MTU is set correctly.

  Here'a log during boot where cloud-init generates a netplan config,
  invokes `netplan generate` which writes the networkd config out
  and then udevadm trigger (3).  Upon logging in interface1 has an MTU of 1500. 
 Re-running udevadm trigger now runs the rules/link files and updates the MTU.

  Note that, if you run udevadm test /sys/class/net/interface1; this also will
  apply the MTU (test probably shouldn't change the interface, I'll file a
  bug for that as well).

  # journalctl -o short-precise --no-pager -b | grep WARK
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 
'generate']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', 
'--no-block', 'systemd-udev-trigger.service']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', 
'--verbose', '--subsystem-match=net', '--action=add']:

  root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link
  [Match]
  MACAddress=52:54:00:12:34:02

  [Link]
  Name=interface1
  WakeOnLan=off
  MTUBytes=1492

  root@ubuntu:~# ifconfig interface1

[Group.of.nepali.translators] [Bug 1699371] Re: nplan autopkgtests are failing in artful (NM 1.8?)

This bug was fixed in the package nplan - 0.32~17.10.1

---
nplan (0.32~17.10.1) artful; urgency=medium

  * Backport 0.32 to Ubuntu 17.10. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

 -- Mathieu Trudel-Lapierre   Thu, 23 Nov 2017
12:30:51 -0500

** Changed in: nplan (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/1699371

Title:
  nplan autopkgtests are failing in artful (NM 1.8?)

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released

Bug description:
  [Impact]
  New versions of NetworkManager require more precise handling of the network 
interfaces. If not already configured to be ignored, bridges may be managed if 
no previous configuration exists, even if NetworkManager has not created the 
bridge.

  [Test case]
  Run autopkgtests for netplan:
  autopkgtest -U --apt-pocket=proposed -s nplan -- qemu 

  [Regression Potential]
  Given that this only affects autopkgtests, regressions would be limited to 
the tests themselves. If the tests regularly fail to pass, or fail more than 
previously, this would be a regression caused by the update.

  ---

  nplan's autopkgtests are failing in artful which is preventing
  network-manager 1.8 from migrating in to artful.

  Maybe something changed in the new version of NetworkManager?

  Tests are passing for armhf and s390x but failing for amd64, i386 and
  ppc64el.

  http://autopkgtest.ubuntu.com/packages/n/nplan/artful/amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1699371/+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 1729573] Re: netplan breaks Xen VIF driver

This bug was fixed in the package nplan - 0.32~17.10.1

---
nplan (0.32~17.10.1) artful; urgency=medium

  * Backport 0.32 to Ubuntu 17.10. (LP: #1713142)

nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

nplan (0.31) bionic; urgency=medium

  [ Mathieu Trudel-Lapierre ]
  * src/nm.c: generate a UUID for a connection only as needed; when we're
dealing with NM VLANs. (LP: #1712921)
  * debian/tests/autostart: Make the autostart test more verbose and avoid
failing right from the start when systemd-networkd is disabled.
(LP: #1699371)
  * tests/integration.py: bump the NetworkManager timeout for settling to
120 seconds, autopkgtest infrastructure tends to be a little slow for the
network device configuration to be applied and noticed by NM.
(LP: #1699371)

  [ Dimitri John Ledkov ]
  * Reload udevd to invalidate configuration cache of .rules/.link files
as generate step may have changed them. LP: #1669564

  [ Dan Streetman ]
  * Add another interface driver exception to netplan replug to prevent unbind
of the Xen VIF interfaces. (LP: #1729573)

 -- Mathieu Trudel-Lapierre   Thu, 23 Nov 2017
12:30:51 -0500

** Changed in: nplan (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/1729573

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never complete startup.

  [Fix]

  No fix yet.  Upstream kernel does not appear fixed.

  [Test Case]

  Create a guest instance under a Xen hypervisor (e.g. an AWS instance)
  that has Ubuntu Artful 17.10 installed.  Use only a single interface
  at first when creating it.  Then once it is ready, attach a second
  network interface to the instance.  From inside the instance,
  configure the new interface in netplan (i.e. add a /etc/netplan/
  config for it).  Make sure the new interface is down (netplan does not
  appear to unbind/bind interfaces that are up), and then run:

  $ sudo netplan apply

  or for debug,

  $ sudo netplan --debug apply

  this will unbind and re-bind the second interface, which will then
  have all-0 mac, and will be unusable, as described above.

  [Regression Potential]

  Changes to the Xen VIF driver can result in unusable network
  interfaces, or problems while using Xen VIF interfaces.

  [Other Info]

  Problem appears to exist upstream also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729573/+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 1734278] Re: Grub2 cannot boot up when 8254 time function disable

2017-12-19 Thread Mathieu Trudel-Lapierre

Marking bionic Fix Released; Steve uploaded a debian-installer, which
was built against the new grub.

** Changed in: debian-installer (Ubuntu Bionic)
   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/1734278

Title:
  Grub2 cannot boot up when 8254 time function disable

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in debian-installer package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released
Status in debian-installer source package in Xenial:
  New
Status in grub2 source package in Xenial:
  Fix Committed
Status in debian-installer source package in Bionic:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Released
Status in grub2 package in Debian:
  New
Status in grub2 package in Fedora:
  Confirmed

Bug description:
  [Impact]
  Some Intel SoC-based systems.

  [Test cases]
  1) Boot an affected system.

  [Regression potential]
  Some systems may rely on the current state of the timer selection in order to 
be able to boot successfully, or to catch key presses before the end of a 
timeout in the menu.
  These systems may then fail to boot correctly, stuck in a timeout of crashing 
in grub. The new default, pmtimer, should be available on all ACPI-capable 
systems without being power-gated such as for the PIT, so the impact of this 
possible regression is minimal.

  ---

  Fail to boot into Ubuntu GRUB on the platforms which legacy(8254) timer 
function is disabled.
  "8254 clock gating" is provided to disable 8254 timer to get rid of legacy 
and save power. The platforms with the firmware which disable the 8254 timer 
will fail to boot up and block on grub2 which uses the 8254 timer to calibrate 
the TSC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1734278/+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 1726258] Re: [SRU] 2.29

This bug was fixed in the package snapd - 2.29.4.2+17.10

---
snapd (2.29.4.2+17.10) artful; urgency=medium

  * New upstream release, LP: #1726258
- snap-confine: use #include in snap-confine.apparmor.in

snapd (2.29.4.1) xenial; urgency=medium

  * New upstream release, LP: #1726258
- tests: more debug info for classic-ubuntu-core-transition
- packaging: fix typo that causes error in the misspell test

snapd (2.29.4) xenial; urgency=medium

  * New upstream release, LP: #1726258
- snap-confine: fix snap-confine under lxd
- tests: disable classic-ubuntu-core-transition on i386 temporarily
- many: reject bad plugs/slots
- interfaces,tests: skip unknown plug/slot interfaces
- store: enable "base" field from the store
- packaging/fedora: Merge changes from Fedora Dist-Git

snapd (2.29.3) xenial; urgency=medium

  * New upstream release, LP: #1726258
- daemon: cherry-picked /v2/logs fixes
- cmd/snap-confine: Respect biarch nature of libdirs
- cmd/snap-confine: Ensure snap-confine is allowed to access os-
  release
- interfaces: fix udev tagging for hooks
- cmd: fix re-exec bug with classic confinement for host snapd
- tests: disable xdg-open-compat test
- cmd/snap-confine: add slave PTYs and let devpts newinstance
  perform mediation
- interfaces/many: misc policy updates for browser-support, cups-
  control and network-status
- interfaces/raw-usb: match on SUBSYSTEM, not SUBSYSTEMS
- tests: fix security-device-cgroup* tests on devices with
  framebuffer

snapd (2.29.2) xenial; urgency=medium

  * New upstream release, LP: #1726258
- snapctl: disable stop/start/restart (2.29)
- cmd/snap-update-ns: fix collection of changes made

snapd (2.29.1) xenial; urgency=medium

  * New upstream release, LP: #1726258
- interfaces: fix incorrect signature of ofono DBusPermanentSlot
- interfaces/serial-port: udev tag plugged slots that have just
  'path' via KERNEL
- interfaces/hidraw: udev tag plugged slots that have just 'path'
  via KERNEL
- interfaces/uhid: unconditionally add existing uhid device to the
  device cgroup
- cmd/snap-update-ns: fix mount rules for font sharing
- tests: disable refresh-undo test on trusty for now
- tests: use `snap change --last=install` in snapd-reexec test
- Revert " wrappers: fail install if exec-line cannot be re-written
- interfaces: don't udev tag devmode or classic snaps
- many: make ignore-validation sticky and send the flag with refresh
  requests

snapd (2.29) xenial; urgency=medium

  * New upstream release, LP: #1726258
- interfaces/many: miscellaneous updates based on feedback from the
  field
- snap-confine: allow reading uevents from any where in /sys
- spread: add bionic beaver
- debian: make packaging/ubuntu-14.04/copyright a real file again
- tests: cherry pick the fix for services test into 2.29
- cmd/snap-update-ns: initialize logger
- hooks/configure: queue service restarts
- snap-{confine,seccomp}: make @unrestricted fully unrestricted
- interfaces: clean system apparmor cache on core device
- debian: do not build static snap-exec on powerpc
- snap-confine: increase sanity_timeout to 6s
- snapctl: cherry pick service commands changes
- cmd/snap: tell translators about arg names and descs req's
- systemd: run all mount units before snapd.service to avoid race
- store: add a test to show auth failures are forwarded by doRequest
- daemon: convert ErrInvalidCredentials to a 401 Unauthorized error.
- store: forward on INVALID_CREDENTIALS error as
  ErrInvalidCredentials
- daemon: generate a forbidden response message if polkit dialog is
  dismissed
- daemon: Allow Polkit authorization to cancel changes.
- travis: switch to container based test runs
- interfaces: reduce duplicated code in interface tests mocks
- tests: improve revert related testing
- interfaces: sanitize plugs and slots early in ReadInfo
- store: add download caching
- preserve TMPDIR and HOSTALIASES across snap-confine invocation
- snap-confine: init all arrays with `= {0,}`
- tests: adding test for network-manager interface
- interfaces/mount: don't generate legacy per-hook/per-app mount
  profiles
- snap: introduce structured epochs
- tests: fix interfaces-cups-control test for cups-2.2.5
- snap-confine: cleanup incorrectly created nvidia udev tags
- cmd/snap-confine: update valid security tag regexp
- cmd/libsnap: enable two stranded tests
- cmd,packaging: enable apparmor on openSUSE
- overlord/ifacestate: refresh all security backends on startup
- interfaces/dbus: drop unneeded check for
  release.ReleaseInfo.ForceDevMode
- dbus: ensure io.snapcraft.Launcher.service is created on re-
  exec
- overlord/auth: continue for now supporting UBUNTU_STORE_ID if the

[Group.of.nepali.translators] [Bug 1726258] Re: [SRU] 2.29

This bug was fixed in the package snapd - 2.29.4.2+17.04

---
snapd (2.29.4.2+17.04) zesty; urgency=medium

  * New upstream release, LP: #1726258
- snap-confine: use #include in snap-confine.apparmor.in

snapd (2.29.4.1) xenial; urgency=medium

  * New upstream release, LP: #1726258
- tests: more debug info for classic-ubuntu-core-transition
- packaging: fix typo that causes error in the misspell test

snapd (2.29.4) xenial; urgency=medium

  * New upstream release, LP: #1726258
- snap-confine: fix snap-confine under lxd
- tests: disable classic-ubuntu-core-transition on i386 temporarily
- many: reject bad plugs/slots
- interfaces,tests: skip unknown plug/slot interfaces
- store: enable "base" field from the store
- packaging/fedora: Merge changes from Fedora Dist-Git

snapd (2.29.3) xenial; urgency=medium

  * New upstream release, LP: #1726258
- daemon: cherry-picked /v2/logs fixes
- cmd/snap-confine: Respect biarch nature of libdirs
- cmd/snap-confine: Ensure snap-confine is allowed to access os-
  release
- interfaces: fix udev tagging for hooks
- cmd: fix re-exec bug with classic confinement for host snapd
- tests: disable xdg-open-compat test
- cmd/snap-confine: add slave PTYs and let devpts newinstance
  perform mediation
- interfaces/many: misc policy updates for browser-support, cups-
  control and network-status
- interfaces/raw-usb: match on SUBSYSTEM, not SUBSYSTEMS
- tests: fix security-device-cgroup* tests on devices with
  framebuffer

snapd (2.29.2) xenial; urgency=medium

  * New upstream release, LP: #1726258
- snapctl: disable stop/start/restart (2.29)
- cmd/snap-update-ns: fix collection of changes made

snapd (2.29.1) xenial; urgency=medium

  * New upstream release, LP: #1726258
- interfaces: fix incorrect signature of ofono DBusPermanentSlot
- interfaces/serial-port: udev tag plugged slots that have just
  'path' via KERNEL
- interfaces/hidraw: udev tag plugged slots that have just 'path'
  via KERNEL
- interfaces/uhid: unconditionally add existing uhid device to the
  device cgroup
- cmd/snap-update-ns: fix mount rules for font sharing
- tests: disable refresh-undo test on trusty for now
- tests: use `snap change --last=install` in snapd-reexec test
- Revert " wrappers: fail install if exec-line cannot be re-written
- interfaces: don't udev tag devmode or classic snaps
- many: make ignore-validation sticky and send the flag with refresh
  requests

snapd (2.29) xenial; urgency=medium

  * New upstream release, LP: #1726258
- interfaces/many: miscellaneous updates based on feedback from the
  field
- snap-confine: allow reading uevents from any where in /sys
- spread: add bionic beaver
- debian: make packaging/ubuntu-14.04/copyright a real file again
- tests: cherry pick the fix for services test into 2.29
- cmd/snap-update-ns: initialize logger
- hooks/configure: queue service restarts
- snap-{confine,seccomp}: make @unrestricted fully unrestricted
- interfaces: clean system apparmor cache on core device
- debian: do not build static snap-exec on powerpc
- snap-confine: increase sanity_timeout to 6s
- snapctl: cherry pick service commands changes
- cmd/snap: tell translators about arg names and descs req's
- systemd: run all mount units before snapd.service to avoid race
- store: add a test to show auth failures are forwarded by doRequest
- daemon: convert ErrInvalidCredentials to a 401 Unauthorized error.
- store: forward on INVALID_CREDENTIALS error as
  ErrInvalidCredentials
- daemon: generate a forbidden response message if polkit dialog is
  dismissed
- daemon: Allow Polkit authorization to cancel changes.
- travis: switch to container based test runs
- interfaces: reduce duplicated code in interface tests mocks
- tests: improve revert related testing
- interfaces: sanitize plugs and slots early in ReadInfo
- store: add download caching
- preserve TMPDIR and HOSTALIASES across snap-confine invocation
- snap-confine: init all arrays with `= {0,}`
- tests: adding test for network-manager interface
- interfaces/mount: don't generate legacy per-hook/per-app mount
  profiles
- snap: introduce structured epochs
- tests: fix interfaces-cups-control test for cups-2.2.5
- snap-confine: cleanup incorrectly created nvidia udev tags
- cmd/snap-confine: update valid security tag regexp
- cmd/libsnap: enable two stranded tests
- cmd,packaging: enable apparmor on openSUSE
- overlord/ifacestate: refresh all security backends on startup
- interfaces/dbus: drop unneeded check for
  release.ReleaseInfo.ForceDevMode
- dbus: ensure io.snapcraft.Launcher.service is created on re-
  exec
- overlord/auth: continue for now supporting UBUNTU_STORE_ID if the

[Group.of.nepali.translators] [Bug 1726258] Re: [SRU] 2.29

This bug was fixed in the package snapd - 2.29.4.2

---
snapd (2.29.4.2) xenial; urgency=medium

  * New upstream release, LP: #1726258
- snap-confine: use #include in snap-confine.apparmor.in

snapd (2.29.4.1) xenial; urgency=medium

  * New upstream release, LP: #1726258
- tests: more debug info for classic-ubuntu-core-transition
- packaging: fix typo that causes error in the misspell test

snapd (2.29.4) xenial; urgency=medium

  * New upstream release, LP: #1726258
- snap-confine: fix snap-confine under lxd
- tests: disable classic-ubuntu-core-transition on i386 temporarily
- many: reject bad plugs/slots
- interfaces,tests: skip unknown plug/slot interfaces
- store: enable "base" field from the store
- packaging/fedora: Merge changes from Fedora Dist-Git

snapd (2.29.3) xenial; urgency=medium

  * New upstream release, LP: #1726258
- daemon: cherry-picked /v2/logs fixes
- cmd/snap-confine: Respect biarch nature of libdirs
- cmd/snap-confine: Ensure snap-confine is allowed to access os-
  release
- interfaces: fix udev tagging for hooks
- cmd: fix re-exec bug with classic confinement for host snapd
- tests: disable xdg-open-compat test
- cmd/snap-confine: add slave PTYs and let devpts newinstance
  perform mediation
- interfaces/many: misc policy updates for browser-support, cups-
  control and network-status
- interfaces/raw-usb: match on SUBSYSTEM, not SUBSYSTEMS
- tests: fix security-device-cgroup* tests on devices with
  framebuffer

snapd (2.29.2) xenial; urgency=medium

  * New upstream release, LP: #1726258
- snapctl: disable stop/start/restart (2.29)
- cmd/snap-update-ns: fix collection of changes made

snapd (2.29.1) xenial; urgency=medium

  * New upstream release, LP: #1726258
- interfaces: fix incorrect signature of ofono DBusPermanentSlot
- interfaces/serial-port: udev tag plugged slots that have just
  'path' via KERNEL
- interfaces/hidraw: udev tag plugged slots that have just 'path'
  via KERNEL
- interfaces/uhid: unconditionally add existing uhid device to the
  device cgroup
- cmd/snap-update-ns: fix mount rules for font sharing
- tests: disable refresh-undo test on trusty for now
- tests: use `snap change --last=install` in snapd-reexec test
- Revert " wrappers: fail install if exec-line cannot be re-written
- interfaces: don't udev tag devmode or classic snaps
- many: make ignore-validation sticky and send the flag with refresh
  requests

snapd (2.29) xenial; urgency=medium

  * New upstream release, LP: #1726258
- interfaces/many: miscellaneous updates based on feedback from the
  field
- snap-confine: allow reading uevents from any where in /sys
- spread: add bionic beaver
- debian: make packaging/ubuntu-14.04/copyright a real file again
- tests: cherry pick the fix for services test into 2.29
- cmd/snap-update-ns: initialize logger
- hooks/configure: queue service restarts
- snap-{confine,seccomp}: make @unrestricted fully unrestricted
- interfaces: clean system apparmor cache on core device
- debian: do not build static snap-exec on powerpc
- snap-confine: increase sanity_timeout to 6s
- snapctl: cherry pick service commands changes
- cmd/snap: tell translators about arg names and descs req's
- systemd: run all mount units before snapd.service to avoid race
- store: add a test to show auth failures are forwarded by doRequest
- daemon: convert ErrInvalidCredentials to a 401 Unauthorized error.
- store: forward on INVALID_CREDENTIALS error as
  ErrInvalidCredentials
- daemon: generate a forbidden response message if polkit dialog is
  dismissed
- daemon: Allow Polkit authorization to cancel changes.
- travis: switch to container based test runs
- interfaces: reduce duplicated code in interface tests mocks
- tests: improve revert related testing
- interfaces: sanitize plugs and slots early in ReadInfo
- store: add download caching
- preserve TMPDIR and HOSTALIASES across snap-confine invocation
- snap-confine: init all arrays with `= {0,}`
- tests: adding test for network-manager interface
- interfaces/mount: don't generate legacy per-hook/per-app mount
  profiles
- snap: introduce structured epochs
- tests: fix interfaces-cups-control test for cups-2.2.5
- snap-confine: cleanup incorrectly created nvidia udev tags
- cmd/snap-confine: update valid security tag regexp
- cmd/libsnap: enable two stranded tests
- cmd,packaging: enable apparmor on openSUSE
- overlord/ifacestate: refresh all security backends on startup
- interfaces/dbus: drop unneeded check for
  release.ReleaseInfo.ForceDevMode
- dbus: ensure io.snapcraft.Launcher.service is created on re-
  exec
- overlord/auth: continue for now supporting UBUNTU_STORE_ID if the
  model is

[Group.of.nepali.translators] [Bug 1738797] Re: linux-oem: 4.13.0-1013.14 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

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

Title:
  linux-oem: 4.13.0-1013.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  kernel-stable-master-bug: 1738791
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1738797/+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 1738797] Re: linux-oem: 4.13.0-1013.14 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1738791
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 19. December 2017 16:32 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1738791
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 19. December 2017 16:32 UTC
+ phase: Uploaded

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

Title:
  linux-oem: 4.13.0-1013.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem 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 --
  kernel-stable-master-bug: 1738791
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1738797/+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 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2017-12-19 Thread Łukasz Zemczak

I have pushed the 3 packages to the xenial UNAPPROVED queue. Now we need
to wait for those to get reviewed by someone from the SRU team. It's a
big SRU so the reviewers might raise some issues during the review
process - let's keep track of any comments from them on this bug.

** Changed in: modemmanager (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: libqmi (Ubuntu)
   Status: New => Fix Released

** Changed in: libmbim (Ubuntu)
   Status: New => Fix Released

** Changed in: libqmi (Ubuntu)
   Importance: Undecided => Critical

** Changed in: libmbim (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1738864] Re: libvirt updates all iSCSI targets from host each time a pool is started

2017-12-19 Thread ChristianEhrhardt

You'd add [2] and always take packages from there non selectively.
So normal add-apt-repository and after that just update/upgrade as usual
according to your maintenance policies.

I'd say that while libvirt/qemu can break things I'd have very rarely seen
those to manifest as system instabilities - so I'd assume other changes would
have caused this.
In general I'd recommend to do the change on a few systems only to begin with
and see if they behave up to your expectation for a while.
Also maybe do not change the week before Christmas, but more in January :-)

On the SRU I think we agree that we will not change the version as in
Xenial for the reasons outlined before - thanks for your understanding.
I'm marking the bug task accordingly.

I'll stay subscribed here to help you with the general discussion.

** Changed in: libvirt (Ubuntu Xenial)
Status: Confirmed => Won't Fix

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

Title:
libvirt updates all iSCSI targets from host each time a pool is
started

Status in libvirt package in Ubuntu:
Fix Released
Status in libvirt source package in Trusty:
Won't Fix
Status in libvirt source package in Xenial:
Won't Fix

Bug description:
Hello everyone, I'm a little confused about the behavior of libvirt in
Ubuntu 16.04.3.

We have up to 140 iSCSI targets on a single storage host, and all of
these are made available to our VM hosts. If I stop one of the iSCSI
pools through virsh ("virsh pool-destroy iscsipool1") and start it
back up again while running libvirt in debug, I see that it runs a
discovery and proceeds to go through and update every single target
available on that host -- even targets that we do not use, instead of
simply connecting to that target.

This turns a <1 second process into a minimum of 30 seconds, and I
just ran it with the stopwatch and clocked it at 64 seconds. So if we
are doing maintenance on these hosts and go for a reboot, it takes
90-120+ minutes to finish auto starting all of the iSCSI pools. And of
course, during this period of time, the server is completely worthless
as a VM host. Libvirt is just stuck until it finishes connecting
everything. Manually connecting to the targets using iscsiadm without
doing all the same hubbub that libvirt is doing connects these targets
immediately, as I would expect from libvirt.

And for each of the 140 iSCSI targets, it goes through and runs an
iscsiadm sendtargets and then updates every single target before
finally connecting the respective pool.

We also noticed that libvirt in Ubuntu 17.10 does not have this
behavior. Well maybe it does, but it connects the iSCSI targets
immediately. It is a much different process than Ubuntu 16.04.3.

Any help would be greatly appreciated. Thank you so much.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1738864/+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 1738911] Re: Support realtek new codec alc257 in the alsa hda driver

2017-12-19 Thread Timo Aaltonen

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

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

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

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

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

Title:
  Support realtek new codec alc257 in the alsa hda driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  New

Bug description:
  Otherwise, the kernel will load generic codec driver, this will
  introduce lots of problem like mute/micmute hotkey can't work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1738911/+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 1738796] Re: linux-hwe-edge: 4.13.0-22.25~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1738791
+ kernel-stable-phase-changed:Tuesday, 19. December 2017 15:02 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1738791
- kernel-stable-phase-changed:Tuesday, 19. December 2017 15:02 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-hwe-edge: 4.13.0-22.25~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge 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 --
  kernel-stable-master-bug: 1738791
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1738796/+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 1738842] Re: linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.13.0-21.24~16.04.1 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: 1738823
  phase: Uploaded
+ kernel-stable-phase-changed:Tuesday, 19. December 2017 13:32 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.13.0-21.24~16.04.1 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: 1738823
- phase: Uploaded
- kernel-stable-phase-changed:Tuesday, 19. December 2017 13:32 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-hwe-edge: 4.13.0-21.24~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.13.0-21.24~16.04.1 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: 1738823
  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/1738842/+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 1738862] Re: linux-oem: 4.13.0-1012.13 -proposed tracker