[Group.of.nepali.translators] [Bug 1700995] Re: [MIR] vmdk-stream-converter

[Matthias Klose]

still missing bug subscriber

** Changed in: vmdk-stream-converter (Ubuntu)
   Status: Fix Released => Incomplete

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

Title:
  [MIR] vmdk-stream-converter

Status in vmdk-stream-converter package in Ubuntu:
  Incomplete
Status in vmdk-stream-converter source package in Xenial:
  Fix Released
Status in vmdk-stream-converter source package in Zesty:
  Fix Released

Bug description:
  [Availability]
  Currently in universe

  [Rationale]
  vmdk-stream-converter is a runtime dependency of livecd-rootfs

  [Security]
  There are no outstanding nor historical security issues.

  [Quality Assurance]

  There are no outstanding bugs against the package and is well maintained.
  https://bugs.launchpad.net/ubuntu/+source/vmdk-stream-converter
  https://tracker.debian.org/pkg/vmdk-stream-converter

  [Dependencies]
  All in main (python)

  [Standards Compliance]
  FHS and Debian Policy compliant, while the debhelper compat version is a bit 
old, 8.

  [Maintenance]
  Packaging is minimal.

  [Background]
  livecd-rootfs uses the package during generating VMDS image files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vmdk-stream-converter/+bug/1700995/+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 1700995] Re: [MIR] vmdk-stream-converter

[Steve Langasek]

Override component to main
vmdk-stream-converter 0.2-1 in zesty amd64: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in zesty arm64: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in zesty armhf: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in zesty i386: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in zesty ppc64el: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in zesty s390x: universe/misc/extra/100% -> main
Override [y|N]? y
6 publications overridden.


** Changed in: vmdk-stream-converter (Ubuntu Zesty)
   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/1700995

Title:
  [MIR] vmdk-stream-converter

Status in vmdk-stream-converter package in Ubuntu:
  Fix Released
Status in vmdk-stream-converter source package in Xenial:
  Fix Released
Status in vmdk-stream-converter source package in Zesty:
  Fix Released

Bug description:
  [Availability]
  Currently in universe

  [Rationale]
  vmdk-stream-converter is a runtime dependency of livecd-rootfs

  [Security]
  There are no outstanding nor historical security issues.

  [Quality Assurance]

  There are no outstanding bugs against the package and is well maintained.
  https://bugs.launchpad.net/ubuntu/+source/vmdk-stream-converter
  https://tracker.debian.org/pkg/vmdk-stream-converter

  [Dependencies]
  All in main (python)

  [Standards Compliance]
  FHS and Debian Policy compliant, while the debhelper compat version is a bit 
old, 8.

  [Maintenance]
  Packaging is minimal.

  [Background]
  livecd-rootfs uses the package during generating VMDS image files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vmdk-stream-converter/+bug/1700995/+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 1700995] Re: [MIR] vmdk-stream-converter

[Steve Langasek]

Override component to main
vmdk-stream-converter 0.2-1 in xenial amd64: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in xenial arm64: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in xenial armhf: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in xenial i386: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in xenial powerpc: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in xenial ppc64el: universe/misc/extra/100% -> main
vmdk-stream-converter 0.2-1 in xenial s390x: universe/misc/extra/100% -> main
Override [y|N]? y
7 publications overridden.


** Changed in: vmdk-stream-converter (Ubuntu Xenial)
   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/1700995

Title:
  [MIR] vmdk-stream-converter

Status in vmdk-stream-converter package in Ubuntu:
  Fix Released
Status in vmdk-stream-converter source package in Xenial:
  Fix Released
Status in vmdk-stream-converter source package in Zesty:
  Fix Released

Bug description:
  [Availability]
  Currently in universe

  [Rationale]
  vmdk-stream-converter is a runtime dependency of livecd-rootfs

  [Security]
  There are no outstanding nor historical security issues.

  [Quality Assurance]

  There are no outstanding bugs against the package and is well maintained.
  https://bugs.launchpad.net/ubuntu/+source/vmdk-stream-converter
  https://tracker.debian.org/pkg/vmdk-stream-converter

  [Dependencies]
  All in main (python)

  [Standards Compliance]
  FHS and Debian Policy compliant, while the debhelper compat version is a bit 
old, 8.

  [Maintenance]
  Packaging is minimal.

  [Background]
  livecd-rootfs uses the package during generating VMDS image files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vmdk-stream-converter/+bug/1700995/+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 1601998] Re: /usr/bin/dpkg:6:do_internerr:deb_reassemble:process_archive:archivefiles:main

[Launchpad Bug Tracker]

This bug was fixed in the package dpkg - 1.18.4ubuntu1.3

---
dpkg (1.18.4ubuntu1.3) xenial; urgency=medium

  * Use ohshit() instead of internerr() for unhandled dpkg-split exit
codes. (i.e. do not abort). Closes: #812679, LP: #1601998

 -- Brian Murray   Fri, 20 Oct 2017 16:14:06 -0700

** Changed in: dpkg (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/1601998

Title:
  /usr/bin/dpkg:6:do_internerr:deb_reassemble:process_archive:archivefiles:main

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

Bug description:
  [Impact]
  There are a ton of crash reports in the Error Tracker from dpkg about 
dpkg-split which cause dpkg to abort. It'd be good to get this resolved in 
Ubuntu 16.04.

  [Test Case]
  Verify that the new version of dpkg does not appear in the Error Tracker.
  One might also try the following:

  1) dpkg -i /tmp/cats
  2) Observe dpkg-split aborting e.g.

  dpkg-split: error: error reading /tmp/cats: Is a directory
  dpkg:../../src/unpack.c:123:deb_reassemble: internal error: unexpected exit 
status 2 from dpkg-split
  Aborted (core dumped)

  With the version of the package in -proposed that should not happen.

  [Regression Potential]
  Little as we are just changing the error handling mechanism.

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding dpkg.  This problem was most recently seen with version
  1.18.4ubuntu1.1, the problem page at
  https://errors.ubuntu.com/problem/fbab11d5ffef5f64e1affa33c6e5bf0330075104
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1601998/+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 1730642] Re: Support generating a rootfs tree only

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.408.24

---
livecd-rootfs (2.408.24) xenial; urgency=medium

  * For the IMAGEFORMAT=none parts to work for ubuntu-image classic builds, we
need to make sure IMAGEFORMAT is preserved and not overwritten if defined.
Backporting from artful.

livecd-rootfs (2.408.23) xenial; urgency=medium

  [ Gary Wang ]
  * Add the IMAGEFORMAT=none to support generating a single rootfs
(LP: #1730642)

  [ Christopher Glass (Ubuntu) ]
  * Backport "minimized round 2" changes from trunk to Xenial (LP: #1731492)
  * Remove apt, debconf, dpkg cruft files from /var/cache and /var/lib in
all our livefses.
  * Pass --cache false to lb config; otherwise we copy around caches of
.debs that are never used properly, and which prevent us from emptying
/var/cache/apt in images.
  * When building minimized cloud images, remove various packages that we
don't want installed by default.  Some are tools that aren't needed for
non-interactive use; some are libraries whose reverse-dependencies
will have already been removed; and one, open-vm-tools, should only be
included in images that are targeted to VMWare (which is not the case
for any of the current minimal images), rather than being included
directly in the cloud-image seed.

 -- Łukasz 'sil2100' Zemczak   Tue, 21 Nov
2017 17:01:14 +0100

** Changed in: livecd-rootfs (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/1730642

Title:
  Support generating a rootfs tree only

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Zesty:
  Fix Committed
Status in livecd-rootfs source package in Artful:
  Fix Released

Bug description:
  [Impact]

  For the use of ubuntu-image classic image generation, it is required
  that livecd-rootfs supports a way to only generate the rootfs tree for
  a selected set of arguments (project, architecture etc.). By design
  ubuntu-image will use livecd-rootfs for preparation of the rootfs
  contents and then continue with building the image. Since ubuntu-image
  is backported feature-complete into artful, zesty and xenial, we would
  need the same change to be propagated to those stable series.

  [Test Case]

   * Install livecd-rootfs from -proposed
   * Create a temporary directory, cd into it
   * cp -a `dpkg -L livecd-rootfs | grep "auto$"` .
   * sudo PROJECT="ubuntu-cpc" ARCH=amd64 IMAGEFORMAT=none SUITE= lb 
config
   * sudo PROJECT="ubuntu-cpc" ARCH=amd64 IMAGEFORMAT=none SUITE= lb 
build
   * Make sure the build succeeds and that the current directory will have a 
chroot/ with the build rootfs contents
   * Make sure that there config/hooks/ directory has no binary hooks

  [Regression Potential]

  The proposed change should be self-contained and not affecting any
  other code paths, but in the case of a very unlikely situation regular
  image builds could be broken by binary hooks not being executed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1730642/+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 1731492] Re: [SRU] Release "minimized round 2" changes to Xenial

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.408.24

---
livecd-rootfs (2.408.24) xenial; urgency=medium

  * For the IMAGEFORMAT=none parts to work for ubuntu-image classic builds, we
need to make sure IMAGEFORMAT is preserved and not overwritten if defined.
Backporting from artful.

livecd-rootfs (2.408.23) xenial; urgency=medium

  [ Gary Wang ]
  * Add the IMAGEFORMAT=none to support generating a single rootfs
(LP: #1730642)

  [ Christopher Glass (Ubuntu) ]
  * Backport "minimized round 2" changes from trunk to Xenial (LP: #1731492)
  * Remove apt, debconf, dpkg cruft files from /var/cache and /var/lib in
all our livefses.
  * Pass --cache false to lb config; otherwise we copy around caches of
.debs that are never used properly, and which prevent us from emptying
/var/cache/apt in images.
  * When building minimized cloud images, remove various packages that we
don't want installed by default.  Some are tools that aren't needed for
non-interactive use; some are libraries whose reverse-dependencies
will have already been removed; and one, open-vm-tools, should only be
included in images that are targeted to VMWare (which is not the case
for any of the current minimal images), rather than being included
directly in the cloud-image seed.

 -- Łukasz 'sil2100' Zemczak   Tue, 21 Nov
2017 17:01:14 +0100

** Changed in: livecd-rootfs (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/1731492

Title:
  [SRU] Release "minimized round 2" changes to Xenial

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Minimized images have their disk footprint further reduced with these
     changes.
   * Using minimal images can save bandwidth and system resources and we
     would like to make those improvements available for Xenial users,
     especially since most if not all of our minimized images users care
     mostly about LTS releases.

  [Test Case]

   * No new autopkgtest was added, however, an autopkgtest (minimized)
     was previously added to test building minimized images. The test logs show
     the generated image sizes for ubuntu-cpc images with and without
     minimization and the minimized images have to be smaller.

  [Regression Potential]

   * If images rely on the presence of a populated /var/cache/apt, that
     functionality could now break (no such image is known). This is believed 
 to be a functionally "no-op" change.
   * If images rely on /var/cache/debconf/*-old or /var/lib/dpkg/*-old files to
     be present, that functionality cloud now break (no such image is known). 
 This is believed to be a functionally "no-op" change.
   * The package changes should not affect images which are not minimized. The
     minimized images in general may not boot on some systems. This is not a
     regression however, this branch does not make the situation better or
     worse in this regard.

  [Other Info]

  (none)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1731492/+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 1731482] Re: outdated version of libvirt-python 1.3.1 crashes on call to getAllDomainStats

[Launchpad Bug Tracker]

This bug was fixed in the package libvirt-python - 1.3.1-1ubuntu1.1

---
libvirt-python (1.3.1-1ubuntu1.1) xenial; urgency=medium

  * d/p/lp1731482-fix-crash-in-getAllDomainStats.patch: Fix crash when
accessing getAllDomainStats (LP: #1731482).

 -- Christian Ehrhardt   Wed, 15 Nov
2017 16:00:04 +0100

** Changed in: libvirt-python (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/1731482

Title:
  outdated version of libvirt-python 1.3.1 crashes on call to
  getAllDomainStats

Status in libvirt-python package in Ubuntu:
  Fix Released
Status in libvirt-python source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * bad free from libvirt python, getAllDomainStats is unusable

   * mostly python based stat apps like Ceilometer would be affected

   * fix is an upstream backport.

  [Test Case]

   * Execute the test program I wrote in comment #2

  [Regression Potential]

   * it seems that so far any user of getAllDomainStats would have 
 segfaulted. What comes to my mind are solutions that worked before that 
 happened and ignored the latter segfault. By a change in behavior it 
 might now behave different. Still I think that is of very low risk.

  [Other Info]
   
   * n/a

  ---

  The following bug is present in the curent version of libvirt-python
  in Xenial (1.3.1):

  https://bugzilla.redhat.com/show_bug.cgi?id=1326839

  This bug has been resolved in 1.3.4 by the following commit:

  https://gitlab.com/libvirt/libvirt-
  python/commit/e9c4e2abffef007a28112ebb40a9586b0128f10b

  This bug is e.g. triggered when using OpenStack Telemetry (Ceilometer)
  and configuring it to collect "cpu" metering data. This leads to the
  segmentation fault mentioned in the linked bug report.

  The version of libvirt-python in Xenial should be updated to >= 1.3.4
  or at least the linked fix should be backported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt-python/+bug/1731482/+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 1652466] Re: Totem can't play videos on Gallium graphics without mesa-va-drivers

[Launchpad Bug Tracker]

This bug was fixed in the package libva - 1.7.0-1ubuntu0.1

---
libva (1.7.0-1ubuntu0.1) xenial; urgency=medium

  [ Sebastian Ramacher ]
  * debian/control:
- Add mesa-va-drivers as alternative to Depends of va-driver-all
  (LP: #1652466).

 -- Amr Ibrahim   Wed, 30 Aug 2017 04:55:15
-0500

** Changed in: libva (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/1652466

Title:
  Totem can't play videos on Gallium graphics without mesa-va-drivers

Status in One Hundred Papercuts:
  Fix Committed
Status in libva package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid
Status in libva source package in Xenial:
  Fix Released
Status in totem source package in Xenial:
  Invalid

Bug description:
  Impact
  ---
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers)

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  
  Test case
  --
  - Purge va-driver-all and mesa-va-drivers if already installed
  - Install va-driver-all from xenial-proposed
  - Make sure that mesa-va-drivers is pulled in
  - Play videos in Totem with gstreamer1.0-vaapi installed and make sure that 
videos play nicely.

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  
  Regression potential
  -
  Since there are no code changes at all, I cannot think of any regressions.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1652466/+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 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Seth Arnold]

** Also affects: iproute2 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: iproute2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: iproute2 (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/1732032

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  In Progress
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  New
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  New

Bug description:
  [Impact]

   * An explanation of the effects of the bug on users and

   * justification for backporting the fix to the stable release.

   * In addition, it is helpful, but not required, to include an
 explanation of how the upload fixes this bug.

  [Test Case]

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   * discussion of how regressions are most likely to manifest as a
  result of this change.

   * It is assumed that any SRU candidate patch is well-tested before
 upload and has a low overall risk of regression, but it's important
 to make the effort to think about what ''could'' happen in the
 event of a regression.

   * This both shows the SRU team that the risks have been considered,
 and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

  
  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1

  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream already had patches that fix this problem:

  1) https://www.spinics.net/lists/netdev/msg415009.html
  commit 530903dd9003492edb0714e937ad4a5d1219e376
  Author: Petr Vorel 
  Date:   Tue Jan 17 00:25:50 2017 +0100

  ip: fix igmp parsing when iface is long

  Entries with long vhost names in /proc/net/igmp have no whitespace
  between name and colon, so sscanf() adds it to vhost and
  'ip maddr show iface' doesn't include inet result.

  Signed-off-by: Petr Vorel 

  2) https://www.spinics.net/lists/netdev/msg461479.html
  commit 21503ed2af233ffe795926f6641ac84ec1b15bf9
  Author: Michal Kubecek 
  Date:   Thu Oct 19 10:21:08 2017 +0200

  ip maddr: fix filtering by device

  Commit 530903dd9003 ("ip: fix igmp parsing when iface is long") uses
  variable len to keep trailing colon from interface name comparison.  This
  variable is local to loop body but we set it in one pass and use it in
  following one(s) so that we are actually using (pseudo)random length for
  comparison. This became apparent since commit b48a1161f5f9 ("ipmaddr: 
Avoid
  accessing uninitialized data") always initializes len to zero so that the
  name comparison is always true. As a result, "ip maddr show dev eth0" 
shows
  IPv4 multicast addresses for all interfaces.

  Instead of 

[Group.of.nepali.translators] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 235-3ubuntu2

---
systemd (235-3ubuntu2) bionic; urgency=medium

  * systemd-fsckd: Fix ADT tests to work on s390x too.

systemd (235-3ubuntu1) bionic; urgency=medium

  * Merge 235-3 from debian:
- Drop UBUNTU-CVE-2017-15908 included in Debian.

  * Remaining delta from Debian:
- ship dhclient enter hook for dhclient integration with resolved
- ship resolvconf integration via stub-resolv.conf
- ship s390x virtio interface names migration
- do not disable systemd-resolved upon libnss-resolve removal
- do not remote fs in containers, for non-degrated boot
- CVE-2017-15908 in resolved fix loop on packets with pseudo dns types
- Unlink invocation id key, upon chown failure in containers
- Change default to UseDomains by default
- Do not treat failure to set Nice= setting as error in containers
- Add a condition to systemd-journald-audit.socet to not start in
  containers (fails)
- Build without any built-in/fallback DNS server setting
- Enable resolved by default
- Update autopkgtests for reliability/raciness, and testing for typical
  defaults
- Always upgrade udev, when running adt tests
- Skip test-execute on armhf
- Cherry-pick a few testsuite fixes

  * UBUNTU Do not use nested kvm during ADT tests.

systemd (235-3) unstable; urgency=medium

  [ Michael Biebl ]
  * Switch from XC-Package-Type to Package-Type. As of dpkg-dev 1.15.7
Package-Type is recognized as an official field name.
  * Install modprobe configuration file to /lib/modprobe.d.
Otherwise it is not read by kmod. (Closes: #879191)

  [ Felipe Sateler ]
  * Backport upstream (partial) fix for combined DynamicUser= + User=
UID was not allowed to be different to GID, which is normally the case in
debian, due to the group users being allocated the GID 100 without an
equivalent UID 100 being allocated.
  * Backport upstream patches to fully make DynamicUser=yes + static,
pre-existing User= work.

  [ Martin Pitt ]
  * Add missing python3-minimal dependency to systemd-tests
  * Drop long-obsolete systemd-bus-proxy system user
systemd-bus-proxy hasn't been shipped since before stretch and never
created any files. Thus clean up the obsolete system user on upgrades.
(Closes: #878182)
  * Drop static systemd-journal-gateway system user
systemd-journal-gatewayd.service now uses DynamicUser=, so we don't need
to create this statically any more. Don't remove the user on upgrades
though, as there is likely still be a running process. (Closes: #878183)
  * Use DynamicUser= for systemd-journal-upload.service.
  * Add Recommends: libnss-systemd to systemd-sysv.
This is useful to actually be able to resolve dynamically created system
users with DynamicUser=true. This concept is going to be used much more
in future versions and (hopefully) third-party .services, so pulling it
into the default installation seems prudent now.
  * resolved: Fix loop on packets with pseudo dns types.
(CVE-2017-15908, Closes: #880026, LP: #1725351)
  * bpf-firewall: Properly handle kernels without BPF cgroup but with TRIE maps.
Fixes "Detaching egress BPF: Invalid argument" log spam. (Closes: #878965)
  * Fix MemoryDenyWriteExecution= bypass with pkey_mprotect() (LP: #1725348)

 -- Dimitri John Ledkov   Tue, 21 Nov 2017 16:41:15
+

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  
  Sincerely, 
  Thomas IMBERT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725348/+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 1735225] Re: rooturl= should automatically enable 'rc-initrd-dns' feature

[Scott Moser]

** Attachment added: "test script"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1735225/+attachment/5016294/+files/test-lp1714308.sh

** Also affects: resolvconf (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** No longer affects: resolvconf (Ubuntu)

** Changed in: resolvconf (Ubuntu Trusty)
   Status: New => Confirmed

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

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

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

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

Title:
  rooturl= should automatically enable 'rc-initrd-dns' feature

Status in resolvconf source package in Trusty:
  Confirmed
Status in resolvconf source package in Xenial:
  Confirmed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Booting a kernel/initramfs with 'rooturl=http://...' for trusty
  or xenial requires also adding 'rc-initrd-dns' or 'cloud-config-url='
  to the kernel command line in order to get the fix provided by bug
  1711760.

  If a user boots with 'rooturl=', that should imply they want dns
  copied over from the initramfs or otherwise working dns.  They should
  not have to add the additional flag.

  [Test Case]
  Download the test case attached.
  Run it and follow the instructions.
  Login to the guest (ubuntu:password), and inspect /etc/resolv.conf
  without the fix there would be no data in /etc/resolv.conf. With the
  fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com'

  [Regression Potential]
  Regression potential should be very low.
  This could negatively affect a user who was booting with rooturl=
  and had solved the lack of dns in another way.

  [Other Info]
  rooturl was SRU'd to xenial and trusty.  When that happened we were
  not aware of the broken-ness of DNS.  Had we been aware at that time,
  we would have fixed this then, and the regression potential listed above
  would not be present.

  Note, that without a fix for bug 1714308, dns does not work inside
  the initramfs.  So the url in 'rooturl=' has to be an IP address.

  Related bugs:
   * bug 1714308: dns does not work in initramfs after configure_networking 
   * bug 1711760: [2.3] resolv.conf is not set (during commissioning or 
testing) 
  === End SRU Template ===

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu5
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Wed Nov 29 17:33:21 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/trusty/+source/resolvconf/+bug/1735225/+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 1707999] Re: [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's offer

[Launchpad Bug Tracker]

This bug was fixed in the package ipxe - 1.0.0+git-20150424.a25a16d-
1ubuntu1.2

---
ipxe (1.0.0+git-20150424.a25a16d-1ubuntu1.2) xenial-proposed; urgency=medium

  * debian/patches/handle-dhcp-nack.patch: Handle DHCP NAK and send a
re-discover. (LP: #1707999)

 -- Andres Rodriguez   Mon, 20 Nov 2017 13:13:41
-0500

** Changed in: ipxe (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/1707999

Title:
  [SRU] iPXE doesn't handle NAK requests when multiple DHCP server's
  offer

Status in MAAS:
  Invalid
Status in MAAS 2.2 series:
  Invalid
Status in ipxe package in Ubuntu:
  Fix Released
Status in ipxe source package in Xenial:
  Fix Released
Status in ipxe source package in Zesty:
  Fix Committed
Status in ipxe source package in Artful:
  Fix Released
Status in ipxe source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  When there are multiple DHCP servers on the network, iPXE doesn't handle 
NAK's for the DHCP servers. This causes iPXE to get blocked without attempting 
to re-discover, hence, never obtaining an IP address.

  For example, in a MAAS HA environment with a DHCP master/slave
  configuration, the machine fails to PXE boot because at a certain
  point, the DHCP server is not fully in sync, which causes iPXE to get
  a NAK request. This prevents the machine from PXE booting.

  [Test case]
  The easiest way:
  1. Install MAAS with two rack controllers
  2. Configure HA
  3. PXE boot KVM's.

  [Regression Potential]
  Minimal. This only ensures that iPXE attempts to re-discover the network when 
it receives a NACK.

  [Original bug report]
  A VM failed to PXE boot after receiving multiple DHCP offers.

  You can see this here on a log from the secondary controller:
  http://paste.ubuntu.com/25221939/

  The node is offered both 10.245.208.201 and 10.245.208.120, tries to
  get 10.245.208.120, and is refused.

  One strange thing is that it seems like the DHCP server on both the primary 
controller and the secondary controller are responding.  The primary 
controller's log doesn't have the offer for 10.245.208.120 - only the offer for 
10.245.208.201:
  http://paste.ubuntu.com/25221952/

  This is in an HA setup: region API's are at 10.245.208.30,
  10.245.208.31 and 10.245.208.32. We're using hacluster to load
  balance, and a VIP in front at 10.245.208.33. There are rack
  controllers on 10.245.208.30 and 10.245.208.31. For the untagged vlan
  this VM is trying to boot from, 10.245.208.30 is set as the primary
  controller, and 10.245.208.31 is set as the secondary.

  Primary postgres is on 10.245.208.30, it's being replicated to backup
  postgres on 10.245.208.31. It has a VIP at 10.245.208.34.

  We don't hit this everytime - on this deployment only one machine out
  of about 30 hit this.

  We've also seen this on single node MAAS setups - non HA.  So, it's
  not an HA specific issue.

  I've attached logs from the maas servers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1707999/+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 1734744] Re: OOM killer with kernel 4.4.0-92

[Joseph Salisbury]

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.102

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

** Tags added: performing-bisect

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

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

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

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

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

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

Title:
  OOM killer with kernel 4.4.0-92

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

Bug description:
  When putting pressure on a Linux Node in Azure we see OOM killers (similar 
to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842 but not this 
is a different kernel)
  Reverting the kernel to 4.4.0-57 fixes the problem.

  dmesg and kernel.log attached

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

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.29.4.1+18.04

---
snapd (2.29.4.1+18.04) bionic; 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

 -- Michael Vogt   Tue, 28 Nov 2017 07:45:23
+0100

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

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

Title:
  [SRU] 2.29

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

Bug description:
  placeholder

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1726258/+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 1714505] Re: systemd kmod builtin uses out of date kmod context

[Dan Streetman]

** Also affects: debian-installer (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: debian-installer-utils (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: debian-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: Fix Committed

** Also affects: debian-installer-utils (Ubuntu Bionic)
   Importance: Critical
 Assignee: Dimitri John Ledkov (xnox)
   Status: Fix Released

** Also affects: systemd (Ubuntu Bionic)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: Won't Fix

** Changed in: debian-installer-utils (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: debian-installer-utils (Ubuntu Zesty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: debian-installer-utils (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: debian-installer-utils (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  systemd kmod builtin uses out of date kmod context

Status in systemd:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Committed
Status in debian-installer-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in debian-installer source package in Trusty:
  New
Status in debian-installer-utils source package in Trusty:
  New
Status in debian-installer source package in Xenial:
  New
Status in debian-installer-utils source package in Xenial:
  New
Status in debian-installer source package in Zesty:
  New
Status in debian-installer-utils source package in Zesty:
  New
Status in debian-installer source package in Artful:
  New
Status in debian-installer-utils source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  New
Status in debian-installer source package in Bionic:
  Fix Committed
Status in debian-installer-utils source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  udev's rules use a built-in 'kmod' instead of the system
  modprobe/insmod, and this built-in kmod only validates/refreshes its
  kmod 'context' every 3 seconds (or longer) during event processing.

  However, because other parts of the system rely on udev to load
  modules correctly, it is not acceptable for it to use an out of date
  module context.  For example, during a system installation:

  -the system boots with kernel and initrd with a reduced set of modules, not 
including nvme module
  -udevd starts, and creates its kmod module context, which does not include 
nvme module
  -system installer adds 'block-modules' udeb, which adds nvme module to system
  -system installer immediately calls hw-detect->update-dev->udevadm trigger
  -udevd sees its kmod module context is not more than 3 seconds old, and does 
not update it
  -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to 
load matching driver
  -udevd kmod builtin does not find NVMe pci modalias because its context is 
out of date

  this results in the system installer complaining to the user that it
  found no disks, even though there is a NVMe drive in the system, and
  the nvme module is installed in the system.

  [Test Case]

  This is reproducable when trying to install using debian-installer and
  a preseed file that skips all questions, although not on all systems,
  since other events can cause udevd to reload all its builtins, or the
  installer may take longer than 3 seconds to call udevadm trigger after
  installing the nvme module udeb.

  However, the bug is easily reproducable on any system with a nvme
  drive using this script:

  #!/bin/bash
  MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host
  modprobe -rq nvme
  mv $MOD_DIR/nvme.ko .
  depmod -a
  sleep 3
  udevadm trigger
  sleep 1
  mv nvme.ko $MOD_DIR/
  depmod -a
  udevadm trigger
  sleep 3
  grep -q nvme /proc/partitions && echo PASS || echo FAIL

  that script does:
  1) remove nvme module from the system, reproducing situation where nvme 
module had not yet been installed
  2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds
  3) triggers udev, which forces it to reload its kmod context (this could be 
done with udevadm control -R instead)
  4) waits 1 second for the udev trigger to finish, then puts the nvme module 
back into the system, reproducing the initial installation of the deb/udeb 
containing the nvme module
  5) immediately triggers udev, which should load the nvme module when it sees 
the nvme pci device
  6) wait 3 seconds for udev trigger to finish (plenty of time), and check if 
the 

[Group.of.nepali.translators] [Bug 1735183] Re: build-in tests: fail early when preparation steps fail

[Andy Whitcroft]

** Also affects: ubuntu-fan (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-fan (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: ubuntu-fan (Ubuntu Artful)
 Assignee: (unassigned) => Stefan Bader (smb)

** Changed in: ubuntu-fan (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu)
 Assignee: (unassigned) => Stefan Bader (smb)

** Summary changed:

- build-in tests: fail early when preparation steps fail
+ built-in tests: fail early when preparation steps fail

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

Title:
  built-in tests: fail early when preparation steps fail

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  In Progress
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  [SRU justification]

  Impact: Preparing the test environment (shared between host and slave
  side) currently is not checking for errors. This was observed when we
  had issues with docker containers failing to have DNS resolution. This
  lead to required utils not being installed which was not detected and
  then the test was stuck until forcefully terminated.

  Fix: Additional code during the preparation of the test environment
  which checks for errors and returns those to the caller. And
  additional error handling from the callers.

  Testcase: Only regression testing possible without running into other
  issues. But while docker problems were still present the tests were
  failed after a few minutes of runtime instead of timing out.

  Regression potential: Minimal. The modified code is used by the ADT
  tests which are run as part of the release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1735183/+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 1735183] Re: build-in tests: fail early when preparation steps fail

[Stefan Bader]

** Changed in: ubuntu-fan (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: ubuntu-fan (Ubuntu Zesty)
 Assignee: (unassigned) => Stefan Bader (smb)

** Changed in: ubuntu-fan (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-fan (Ubuntu)
   Status: New => Fix Released

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

Title:
  built-in tests: fail early when preparation steps fail

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  In Progress
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  [SRU justification]

  Impact: Preparing the test environment (shared between host and slave
  side) currently is not checking for errors. This was observed when we
  had issues with docker containers failing to have DNS resolution. This
  lead to required utils not being installed which was not detected and
  then the test was stuck until forcefully terminated.

  Fix: Additional code during the preparation of the test environment
  which checks for errors and returns those to the caller. And
  additional error handling from the callers.

  Testcase: Only regression testing possible without running into other
  issues. But while docker problems were still present the tests were
  failed after a few minutes of runtime instead of timing out.

  Regression potential: Minimal. The modified code is used by the ADT
  tests which are run as part of the release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1735183/+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 1735183] Re: build-in tests: fail early when preparation steps fail

[Andy Whitcroft]

** Also affects: ubuntu-fan (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-fan (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/1735183

Title:
  built-in tests: fail early when preparation steps fail

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  In Progress
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  [SRU justification]

  Impact: Preparing the test environment (shared between host and slave
  side) currently is not checking for errors. This was observed when we
  had issues with docker containers failing to have DNS resolution. This
  lead to required utils not being installed which was not detected and
  then the test was stuck until forcefully terminated.

  Fix: Additional code during the preparation of the test environment
  which checks for errors and returns those to the caller. And
  additional error handling from the callers.

  Testcase: Only regression testing possible without running into other
  issues. But while docker problems were still present the tests were
  failed after a few minutes of runtime instead of timing out.

  Regression potential: Minimal. The modified code is used by the ADT
  tests which are run as part of the release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1735183/+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 1733528] Re: linux-hwe: 4.10.0-41.45~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1733524
  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/1733528/+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 1733549] Re: linux-kvm: -proposed tracker

[Stefan Bader]

*** This bug is a duplicate of bug 1734968 ***
https://bugs.launchpad.net/bugs/1734968

** This bug has been marked a duplicate of bug 1734968
   linux-kvm: 4.4.0-1011.16 -proposed tracker

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

Title:
  linux-kvm:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: 1733541
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1733549/+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 1734856] Re: Can't boot VM with more than 16 disks (slof buffer issue)

[ChristianEhrhardt]

Thanks for the bug, I see the patch is under active discussion atm.
Lets take a look to integrate once that discussion concludes.

Since it is packaged in slof I assigned that as the target and opened up
per release tasks.

** Package changed: qemu (Ubuntu) => slof (Ubuntu)

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

** Also affects: slof (Ubuntu Bionic)
   Importance: Critical
 Assignee: David Britton (davidpbritton)
   Status: New

** Also affects: slof (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: slof (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Bug watch added: github.com/qemu/SLOF/issues #3
   https://github.com/qemu/SLOF/issues/3

** Also affects: slof via
   https://github.com/qemu/SLOF/issues/3
   Importance: Unknown
   Status: Unknown

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

Title:
  Can't boot VM with more than 16 disks (slof buffer issue)

Status in SLOF - Slimline Open Firmware:
  Unknown
Status in The Ubuntu-power-systems project:
  New
Status in slof package in Ubuntu:
  New
Status in slof source package in Xenial:
  New
Status in slof source package in Zesty:
  New
Status in slof source package in Artful:
  New
Status in slof source package in Bionic:
  New

Bug description:
  == Comment: #0 - RAHUL CHANDRAKAR  - 2017-11-28 03:40:37 
==
  ---Problem Description---
  Can't boot VM with more than 16 disks.
  It is an issue with qemu/SLOF (Bug: https://github.com/qemu/SLOF/issues/3) 
and it was fixed by Nikunj Amritlal Dadhnia.  He has made a patch available and 
it has been tested by PowerVC team.

  We need this fix in Ubuntu 16.04 and later releases.
   
  Machine Type = 8348-21C (P8 Habanero) 
   
  ---Steps to Reproduce---
   Steps to recreate:
  1. Create a VM
  2. Attach 50 disks
  3. Shutdown from OS
  4. Start again and let it boot
   
  ---uname output---
  Linux neo160.blr.stglabs.ibm.com 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 
18:29:11 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Debugger---
  A debugger is not configured
   

  Patch posted and awaiting response...

  http://patchwork.ozlabs.org/patch/842011/

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