[Group.of.nepali.translators] [Bug 1744079] Re: [SRU] disk over-commit still not correctly calculated during live migration

2018-12-17 Thread Corey Bryant
** Also affects: cloud-archive/ocata
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/pike
   Importance: Undecided
   Status: New

** Changed in: cloud-archive/pike
   Importance: Undecided => High

** Changed in: cloud-archive/pike
   Status: New => Triaged

** Changed in: cloud-archive/ocata
   Importance: Undecided => High

** Changed in: cloud-archive/ocata
   Status: New => Triaged

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

Title:
  [SRU] disk over-commit still not correctly calculated during live
  migration

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive ocata series:
  Triaged
Status in Ubuntu Cloud Archive pike series:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Fix Committed
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  In Progress
Status in OpenStack Compute (nova) rocky series:
  In Progress
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Triaged
Status in nova source package in Bionic:
  Fix Committed
Status in nova source package in Cosmic:
  Fix Committed
Status in nova source package in Disco:
  Fix Released

Bug description:
  [Impact]
  nova compares disk space with disk_available_least field, which is possible 
to be negative, due to overcommit.

  So the migration may fail because of a "Migration pre-check error:
  Unable to migrate dfcd087a-5dff-439d-8875-2f702f081539: Disk of
  instance is too large(available on destination host:-3221225472 <
  need:22806528)" when trying a migration to another compute that has
  plenty of free space in his disk.

  [Test Case]
  Deploy openstack environment. Make sure there is a negative 
disk_available_least and a adequate free_disk_gb in one test compute node, then 
migrate a VM to it with disk-overcommit (openstack server migrate --live 
 --block-migration --disk-overcommit ). You will 
see above migration pre-check error.

  This is the formula to compute disk_available_least and free_disk_gb.

  disk_free_gb = disk_info_dict['free']
  disk_over_committed = self._get_disk_over_committed_size_total()
  available_least = disk_free_gb * units.Gi - disk_over_committed
  data['disk_available_least'] = available_least / units.Gi

  The following command can be used to query the value of
  disk_available_least

  nova hypervisor-show  |grep disk

  Steps to Reproduce:
  1. set disk_allocation_ratio config option > 1.0 
  2. qemu-img resize cirros-0.3.0-x86_64-disk.img +40G
  3. glance image-create --disk-format qcow2 ...
  4. boot VMs based on resized image
  5. we see disk_available_least becomes negative

  [Regression Potential]
  Minimal - we're just changing from the following line:

  disk_available_gb = dst_compute_info['disk_available_least']

  to the following codes:

  if disk_over_commit:
  disk_available_gb = dst_compute_info['free_disk_gb']
  else:
  disk_available_gb = dst_compute_info['disk_available_least']

  When enabling overcommit, disk_available_least is possible to be
  negative, so we should use free_disk_gb instead of it by backporting
  the following two fixes.

  
https://git.openstack.org/cgit/openstack/nova/commit/?id=e097c001c8e0efe8879da57264fcb7bdfdf2
  
https://git.openstack.org/cgit/openstack/nova/commit/?id=e2cc275063658b23ed88824100919a6dfccb760d

  This is the code path for check_can_live_migrate_destination:

  _migrate_live(os-migrateLive API, migrate_server.py) -> migrate_server
  -> _live_migrate -> _build_live_migrate_task ->
  _call_livem_checks_on_host -> check_can_live_migrate_destination

  BTW, redhat also has a same bug -
  https://bugzilla.redhat.com/show_bug.cgi?id=1477706

  
  [Original Bug Report]
  Change I8a705114d47384fcd00955d4a4f204072fed57c2 (written by me... sigh) 
addressed a bug which prevented live migration to a target host with 
overcommitted disk when made with microversion <2.25. It achieved this, but the 
fix is still not correct. We now do:

  if disk_over_commit:
  disk_available_gb = dst_compute_info['local_gb']

  Unfortunately local_gb is *total* disk, not available disk. We
  actually want free_disk_gb. Fun fact: due to the way we calculate this
  for filesystems, without taking into account reserved space, this can
  also be negative.

  The test we're currently running is: could we fit this guest's
  allocated disks on the target if the target disk was empty. This is at
  least better than it was before, as we don't spuriously fail early. In
  fact, we're effectively disabling a test which is disabled for
  microversion >=2.25 anyway. IOW we should fix it, but it's probably
  not a high priority.

To manage notifications about this bug 

[Group.of.nepali.translators] [Bug 1744079] Re: [SRU] disk over-commit still not correctly calculated during live migration

2018-12-17 Thread Corey Bryant
** Also affects: nova (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

Title:
  [SRU] disk over-commit still not correctly calculated during live
  migration

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive queens series:
  Fix Committed
Status in Ubuntu Cloud Archive rocky series:
  Fix Committed
Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  In Progress
Status in OpenStack Compute (nova) rocky series:
  In Progress
Status in nova package in Ubuntu:
  Fix Released
Status in nova source package in Xenial:
  Triaged
Status in nova source package in Bionic:
  Fix Committed
Status in nova source package in Cosmic:
  Fix Committed
Status in nova source package in Disco:
  Fix Released

Bug description:
  [Impact]
  nova compares disk space with disk_available_least field, which is possible 
to be negative, due to overcommit.

  So the migration may fail because of a "Migration pre-check error:
  Unable to migrate dfcd087a-5dff-439d-8875-2f702f081539: Disk of
  instance is too large(available on destination host:-3221225472 <
  need:22806528)" when trying a migration to another compute that has
  plenty of free space in his disk.

  [Test Case]
  Deploy openstack environment. Make sure there is a negative 
disk_available_least and a adequate free_disk_gb in one test compute node, then 
migrate a VM to it with disk-overcommit (openstack server migrate --live 
 --block-migration --disk-overcommit ). You will 
see above migration pre-check error.

  This is the formula to compute disk_available_least and free_disk_gb.

  disk_free_gb = disk_info_dict['free']
  disk_over_committed = self._get_disk_over_committed_size_total()
  available_least = disk_free_gb * units.Gi - disk_over_committed
  data['disk_available_least'] = available_least / units.Gi

  The following command can be used to query the value of
  disk_available_least

  nova hypervisor-show  |grep disk

  Steps to Reproduce:
  1. set disk_allocation_ratio config option > 1.0 
  2. qemu-img resize cirros-0.3.0-x86_64-disk.img +40G
  3. glance image-create --disk-format qcow2 ...
  4. boot VMs based on resized image
  5. we see disk_available_least becomes negative

  [Regression Potential]
  Minimal - we're just changing from the following line:

  disk_available_gb = dst_compute_info['disk_available_least']

  to the following codes:

  if disk_over_commit:
  disk_available_gb = dst_compute_info['free_disk_gb']
  else:
  disk_available_gb = dst_compute_info['disk_available_least']

  When enabling overcommit, disk_available_least is possible to be
  negative, so we should use free_disk_gb instead of it by backporting
  the following two fixes.

  
https://git.openstack.org/cgit/openstack/nova/commit/?id=e097c001c8e0efe8879da57264fcb7bdfdf2
  
https://git.openstack.org/cgit/openstack/nova/commit/?id=e2cc275063658b23ed88824100919a6dfccb760d

  This is the code path for check_can_live_migrate_destination:

  _migrate_live(os-migrateLive API, migrate_server.py) -> migrate_server
  -> _live_migrate -> _build_live_migrate_task ->
  _call_livem_checks_on_host -> check_can_live_migrate_destination

  BTW, redhat also has a same bug -
  https://bugzilla.redhat.com/show_bug.cgi?id=1477706

  
  [Original Bug Report]
  Change I8a705114d47384fcd00955d4a4f204072fed57c2 (written by me... sigh) 
addressed a bug which prevented live migration to a target host with 
overcommitted disk when made with microversion <2.25. It achieved this, but the 
fix is still not correct. We now do:

  if disk_over_commit:
  disk_available_gb = dst_compute_info['local_gb']

  Unfortunately local_gb is *total* disk, not available disk. We
  actually want free_disk_gb. Fun fact: due to the way we calculate this
  for filesystems, without taking into account reserved space, this can
  also be negative.

  The test we're currently running is: could we fit this guest's
  allocated disks on the target if the target disk was empty. This is at
  least better than it was before, as we don't spuriously fail early. In
  fact, we're effectively disabling a test which is disabled for
  microversion >=2.25 anyway. IOW we should fix it, but it's probably
  not a high priority.

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

[Group.of.nepali.translators] [Bug 1807373] Re: /usr/bin/software-properties-gtk:AttributeError:on_driver_selection_changed

2018-12-17 Thread Brian Murray
** Description changed:

+ [Impact]
+ software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.
+ 
+ [Test Case]
+ We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.
+ 
+ [Regression Potential]
+ We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.
+ 
+ [Original Description]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
1.92.36bodhi1, the problem page at 
https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Also affects: software-properties (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_driver_selection_changed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  In Progress
Status in software-properties source package in Cosmic:
  In Progress

Bug description:
  [Impact]
  software-properties-gtk is crashing regularly for users of Ubuntu stable 
releases.

  [Test Case]
  We aren't sure what exactly is causing the crash but we don't need to be 
given that there is a bucket in the Error Tracker with a large number of 
crashes. The fix for this bug can be verified by looking at the bucket in the 
description and confirming that the crash does not occur with the new version 
of the package.

  [Regression Potential]
  We are just adding in a except check for an AttributeError so there is little 
chance of a regression, just make sure the change is typo'ed.

  [Original Description]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
1.92.36bodhi1, the problem page at 
https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1807373/+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 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default

2018-12-17 Thread Adam Collard
** No longer affects: snapstore

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

Title:
  Uninstalled snaps show most recent channel version, not version to be
  installed by default

Status in snapd:
  Won't Fix
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Released
Status in gnome-software source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  GNOME Software can show incorrect version of snap that will be installed on 
details page.

  [Test Case]
  1. Open GNOME Software. Ensure blender or spotify snap is not installed.
  2. Select blender or spotify  snap (tried 28-04-2018, may change if store 
versions are changed)

  Expected result:
  Version label shows version to be installed (stable channel by default)

  Observed result:
  Version label shows most recently uploaded version, i.e. from the edge 
channel. This is not the version that will be installed when clicking install.

  [Regression Potential]
  The logic around choosing which version value to show was changed. Could 
create other bugs with this data.

  Orignial text:

  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 1726856] Re: ufw does not start automatically at boot

2018-12-17 Thread Jamie Strandboge
@Matt you have both ufw and firewalld installed and running. You should
disable/remove firewalld. Marking this as 'Invalid' for now, but please
feel free to report back if you still see a bug in ufw after addressing
firewalld.

** Changed in: ufw
   Status: Incomplete => Invalid

** Changed in: ufw (Ubuntu Disco)
   Status: Incomplete => Invalid

** Changed in: ufw (Ubuntu Cosmic)
   Status: Incomplete => Invalid

** Changed in: ufw (Ubuntu Bionic)
   Status: Incomplete => Invalid

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Invalid
Status in ufw source package in Xenial:
  Invalid
Status in ufw source package in Bionic:
  Invalid
Status in ufw source package in Cosmic:
  Invalid
Status in ufw source package in Disco:
  Invalid

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/1726856/+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 1806674] Re: linux-hwe: 4.15.0-43.46~16.04.1 -proposed tracker

2018-12-17 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 13:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Testing in progress
-   verification-testing: Testing in progress

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

Title:
  linux-hwe: 4.15.0-43.46~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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  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: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 13:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Testing in progress

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

2018-12-17 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 11:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Testing in progress
+   promote-to-security: Master bug not ready for release
+   promote-to-updates: Master bug not ready for release

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

Title:
  linux-hwe-edge: 4.15.0-43.46~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 11:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Master bug not ready for release
promote-to-updates: Master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806675/+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 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker

2018-12-17 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 13:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Testing in progress
+   promote-to-security: Master bug not ready for release
+   promote-to-updates: Master bug not ready for release

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

Title:
  linux-gcp: 4.15.0-1026.27~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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 13:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Master bug not ready for release
promote-to-updates: Master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+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 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

2018-12-17 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the 4.15.0-1007.7~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: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 21:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
-   verification-testing: Testing in progress

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

Title:
  linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.15.0-1007.7~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: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 21:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+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 1806425] Re: linux-azure-edge: 4.18.0-1007.7~16.04.2 -proposed tracker

2018-12-17 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Monday, 10. December 2018 13:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   promote-to-security: Master bug not ready for release
+   promote-to-updates: Master bug not ready for release
stakeholder-signoff: Waiting for signoff
-   verification-testing: Testing in progress

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

Title:
  linux-azure-edge: 4.18.0-1007.7~16.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
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  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: 1806409
  phase: Promoted to proposed
  phase-changed: Monday, 10. December 2018 13:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Master bug not ready for release
promote-to-updates: Master bug not ready for release
stakeholder-signoff: Waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806425/+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 1806671] Re: linux-aws-hwe: 4.15.0-1031.33~16.04.1 -proposed tracker

2018-12-17 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Wednesday, 12. December 2018 10:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Testing in progress
+   promote-to-security: Master bug not ready for release
+   promote-to-updates: Master bug not ready for release

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

Title:
  linux-aws-hwe: 4.15.0-1031.33~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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws-hwe package in Ubuntu:
  Invalid
Status in linux-aws-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: 1806659
  phase: Promoted to proposed
  phase-changed: Wednesday, 12. December 2018 10:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Master bug not ready for release
promote-to-updates: Master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806671/+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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

2018-12-17 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   verification-testing: Testing in progress
+   promote-to-security: Master bug not ready for release
+   promote-to-updates: Master bug not ready for release

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

Title:
  linux-azure: 4.15.0-1036.38~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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Master bug not ready for release
promote-to-updates: Master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+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 1808564] Re: SRU 1.6 tracking bug

2018-12-17 Thread Łukasz Zemczak
** Also affects: ubuntu-image (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: ubuntu-image (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-image (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  SRU 1.6 tracking bug

Status in Ubuntu Image:
  Fix Committed
Status in ubuntu-image package in Ubuntu:
  Fix Released
Status in ubuntu-image source package in Xenial:
  In Progress
Status in ubuntu-image source package in Bionic:
  In Progress
Status in ubuntu-image source package in Cosmic:
  In Progress

Bug description:
  New SRU tracking bug (with exception) for ubuntu-image 1.5 in Cosmic,
  Bionic and Xenial.

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

  [Impact]

  ubuntu-image 1.5 fixes some bugs and pay down some technical debt. It
  includes a bugfix for --with-proposed in classic builds and a change
  to not to copy /etc/cloud if empty.

  [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/1808564/+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 1783252] Re: gcc on ppc64le has bogus r30 register handling, as exposed by greenlet 0.4.14 will not build on ppc64le

2018-12-17 Thread Launchpad Bug Tracker
This bug was fixed in the package gcc-5 - 5.4.0-6ubuntu1~16.04.11

---
gcc-5 (5.4.0-6ubuntu1~16.04.11) xenial; urgency=medium

  * Backport upstream revision r235876 to correct PIC_OFFSET_TABLE_REGNUM
on ppc64el.
LP: #1783252

 -- Dimitri John Ledkov   Wed, 01 Aug 2018 22:22:10
+0100

** Changed in: gcc-5 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  gcc on ppc64le has bogus r30 register handling, as exposed by greenlet
  0.4.14 will not build on ppc64le

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in python-greenlet package in Ubuntu:
  Fix Released
Status in gcc-5 source package in Xenial:
  Fix Released
Status in gcc-5 source package in Bionic:
  Confirmed
Status in gcc-6 source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * GCC has a minor bug w.r.t. clobber r30 register in PIC binaries.
   * A patch to fix this has been upstream in 6+
   * But it is not in gcc-5.4 as used on xenial
   * This prevents compiling future-proof and correct greenlet code, on Ubuntu 
16.04 LTS as used by current and supported Openstack Queens release on ppc64el
   * Whilst backported greenlet is available via the cloud archive for binary 
usage, the toolchain is still technically incorrect, and thus hinders using 
Ubuntu 16.04 LTS as workers in upstream Openstack CI
   * As a wishlist it would be nice to backport this one small gcc patch as an 
SRU

  [Test Case]

   * git clone https://github.com/python-greenlet/greenlet
   * cd greenlet
   * ./setup.py build
  Expect success

  Current result failure:

  creating build/temp.linux-ppc64le-2.7
  powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c greenlet.c -o 
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
  In file included from slp_platformselect.h:16:0,
   from greenlet.c:343:
  platform/switch_ppc64_linux.h: In function 'slp_switch':
  platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30' in 
'asm'
   __asm__ volatile ("" : : : REGS_TO_SAVE);
   ^
  platform/switch_ppc64_linux.h:95:5: error: PIC register clobbered by 'r30' in 
'asm'
   __asm__ volatile ("" : : : REGS_TO_SAVE);
   ^
  error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1

  
  [Regression Potential] 

   * Upstream cherrypick present in later releases including bionic
  
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9213244550335bcb2b8590a0d7d58ac74c932361

  
  [Other Info]
   
   * Original bug report

  
  == Comment: #0 - William M. Edmonds  - 2018-07-23 
16:21:41 ==
  ---Problem Description---
  greenlet 0.4.14 will not build on ppc64le

  Opened https://github.com/python-greenlet/greenlet/issues/136 because
  attempting to build bdist_wheel for greenlet 0.4.14 on ppc64le Ubuntu
  16.04 LTS yields the following error:

  running build
  running build_ext
  building 'greenlet' extension
  creating build
  creating build/temp.linux-ppc64le-2.7
  powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c greenlet.c -o 
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
  In file included from slp_platformselect.h:16:0,
  from greenlet.c:343:
     platform/switch_ppc64_linux.h: In function 'slp_switch':
     platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30' 
in 'asm'
  __asm__ volatile ("" : : : REGS_TO_SAVE);
  ^
     platform/switch_ppc64_linux.h:95:5: error: PIC register clobbered by 'r30' 
in 'asm'
  __asm__ volatile ("" : : : REGS_TO_SAVE);
  ^
     error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1```

  But the greenlet community is saying this is a gcc bug and it would
  not be safe to revert the greenlet change that exposed this issue. I
  have no idea whether that is true or not. Supposedly this should be
  fixed by
  
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9213244550335bcb2b8590a0d7d58ac74c932361
  but that fix is not present in the latest version of gcc (5.4.0)
  available for Ubuntu 16.04 LTS.

  ---uname output---
  unavailable due to lab outage

  Machine Type = unavailable due to lab outage

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  This should be reproducible with `git clone 

[Group.of.nepali.translators] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

2018-12-17 Thread Po-Hsu Lin
4.15.0-1007.9~16.04.1 - oci
Regression test CMPL, RTB.

Issue to note in gcp:
  ubuntu_kvm_unit_tests - 21 failures
  ubuntu_leap_seconds - failed on VM.Standard2.16 only
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) statx05 (bug 1798524) 
fanotify09-2 (bug 1804594) fanotify10 (bug 1802454)
  ubuntu_nbd_smoke_test - failed on VM.Standard1.4 and VM.Standard2.16

Skipped / blacklisted:
 * ubuntu_ltp
 * ubuntu_seccomp

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

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

** Tags added: regression-testing-passed

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

Title:
  linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.15.0-1007.7~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: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 21:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
verification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807982/+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 1783252] Re: gcc on ppc64le has bogus r30 register handling, as exposed by greenlet 0.4.14 will not build on ppc64le

2018-12-17 Thread Launchpad Bug Tracker
This bug was fixed in the package gcc-6 - 6.5.0-2ubuntu1~18.04

---
gcc-6 (6.5.0-2ubuntu1~18.04) bionic-proposed; urgency=medium

  * SRU: LP: #1800197. Update gcc-6 to the last GCC 6.5.0 upstream
release.

gcc-6 (6.5.0-2ubuntu1) disco; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.5.0-2) unstable; urgency=medium

  * Fix PR libstdc++/87822, taken from the bug report.
  * Fix VCS attribute in the control file. Addresses: #912405.

gcc-6 (6.5.0-1) unstable; urgency=medium

  * GCC 6.5.0 release.
  * Refresh patches.

gcc-6 (6.4.0-23) unstable; urgency=medium

  * GCC 6.5.0 release candidate.
  * Update to SVN 20181019 (r265212) from the gcc-6-branch.
- Fix PR middle-end/86542, PR middle-end/86539, PR middle-end/86660,
  PR sanitizer/84761, PR libstdc++/87641, PR libstdc++/86751,
  PR libstdc++/87061, PR libstdc++/70966, PR libstdc++/70966,
  PR libstdc++/77854, PR libstdc++/85098, PR middle-end/87623,
  PR middle-end/87024, PR middle-end/86505, PR target/87550 (x86),
  PR middle-end/87248, PR rtl-optimization/87065, PR middle-end/86627,
  PR middle-end/86542, PR middle-end/86539, PR middle-end/86660,
  PR c++/54278, PR tree-optimization/80032, PR tree-optimization/80032,
  PR target/87517 (x86), PR target/87522 (x86), PR c++/3698, PR c++/86208.
  * Don't configure native builds with --with-sysroot. Apparently this cannot
be completely overridden with the command line option --sysroot.
  * Update VCS attributes in the control file.

gcc-6 (6.4.0-22ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-22) unstable; urgency=medium

  * Update to SVN 20180921 (r264530) from the gcc-6-branch.
- Fix libsanitizer build failure on sparc64.

gcc-6 (6.4.0-21ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-21) unstable; urgency=medium

  * Update to SVN 20180921 (r264459) from the gcc-6-branch.
- Fix PR sanitizer/85835, PR tree-optimization/85859, PR target/87014,
  PR fortran/86116.
- Fix build failure with glibc 2.28.

gcc-6 (6.4.0-20ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-20) unstable; urgency=medium

  * Update to SVN 20180814 (r263539) from the gcc-6-branch.
- Fix PR libstdc++/83982, PR libstdc++/80893, PR libstdc++/80893,
  PR libstdc++/68519, PR libstdc++/86292, PR libstdc++/60555,
  PR libstdc++/86734, PR libstdc++/66145, PR libstdc++/85222,
  PR target/86197 (PPC).
- Fix PR bootstrap/86724. Closes: #905708.
  * Backport r235876 from the trunk (PPC). LP: #1783252.
  * Add some basic autopkg tests for Ada, C, C++, Go, OpenMP and Fortran.
  * Update the src_libgo_Makefile.in patch (Svante Signell). Closes: #905714.

gcc-6 (6.4.0-19ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-19) unstable; urgency=medium

  * Update to SVN 20180727 (r263028) from the gcc-6-branch.
- Fix PR c++/86291, PR libgomp/84096, PR fortran/81304, PR fortran/81841,
  PR libstdc++/86272, PR c++/86210, PR c++/83059, PR c/84873, PR c/84873,
  PR debug/83550, PR c/82340, PR target/84168 (AArch64), PR target/84829,
  PR target/84786 (x86), PR tree-optimization/86231, PR middle-end/85878,
  PR target/85945, PR c++/85659, PR rtl-optimization/85431,
  PR rtl-optimization/85300, PR tree-optimization/85257, PR debug/85252,
  PR rtl-optimization/85167, PR inline-asm/85022, PR inline-asm/85034,
  PR inline-asm/85022, PR inline-asm/84941, PR debug/84875, PR c/84953,
  PR target/84899, PR c++/79085, PR target/84772, PR c++/84767,
  PR tree-optimization/84739, PR target/84700, PR inline-asm/84625,
  PR ipa/84425, PR c/82210, PR sanitizer/83987, PR rtl-optimization/83986,
  PR middle-end/84040, PR target/83930, PR preprocessor/83722,
  PR tree-optimization/83605, PR c++/83553, PR rtl-optimization/80747,
  PR rtl-optimization/83512, PR tree-optimization/83523,
  PR tree-optimization/83521, PR ipa/82801, PR ipa/83346, PR target/81906,
  PR c++/81212, PR target/78643, PR target/80583, PR target/80819,
  PR sanitizer/83014, PR middle-end/82253, PR target/82880, PR c++/82159,
  PR c++/82159, PR rtl-optimization/82192, PR tree-optimization/85989,
  PR tree-optimization/82108, PR tree-optimization/81410,
  PR tree-optimization/79920, PR middle-end/84607, PR middle-end/85588,
  PR middle-end/81884, PR middle-end/85244, PR tree-optimization/85597,
  PR middle-end/83623, PR tree-optimization/82264,
  PR tree-optimization/82285, PR tree-optimization/82402,
  PR tree-optimization/82697, PR middle-end/82765, PR middle-end/83713,
  PR c++/86291, PR c++/85147, PR c++/85140, PR c++/84791, PR c++/85076,
  PR c++/85068, PR 

[Group.of.nepali.translators] [Bug 1783930] Re: go library not found by the go tool

2018-12-17 Thread Launchpad Bug Tracker
This bug was fixed in the package gcc-6 - 6.5.0-2ubuntu1~18.04

---
gcc-6 (6.5.0-2ubuntu1~18.04) bionic-proposed; urgency=medium

  * SRU: LP: #1800197. Update gcc-6 to the last GCC 6.5.0 upstream
release.

gcc-6 (6.5.0-2ubuntu1) disco; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.5.0-2) unstable; urgency=medium

  * Fix PR libstdc++/87822, taken from the bug report.
  * Fix VCS attribute in the control file. Addresses: #912405.

gcc-6 (6.5.0-1) unstable; urgency=medium

  * GCC 6.5.0 release.
  * Refresh patches.

gcc-6 (6.4.0-23) unstable; urgency=medium

  * GCC 6.5.0 release candidate.
  * Update to SVN 20181019 (r265212) from the gcc-6-branch.
- Fix PR middle-end/86542, PR middle-end/86539, PR middle-end/86660,
  PR sanitizer/84761, PR libstdc++/87641, PR libstdc++/86751,
  PR libstdc++/87061, PR libstdc++/70966, PR libstdc++/70966,
  PR libstdc++/77854, PR libstdc++/85098, PR middle-end/87623,
  PR middle-end/87024, PR middle-end/86505, PR target/87550 (x86),
  PR middle-end/87248, PR rtl-optimization/87065, PR middle-end/86627,
  PR middle-end/86542, PR middle-end/86539, PR middle-end/86660,
  PR c++/54278, PR tree-optimization/80032, PR tree-optimization/80032,
  PR target/87517 (x86), PR target/87522 (x86), PR c++/3698, PR c++/86208.
  * Don't configure native builds with --with-sysroot. Apparently this cannot
be completely overridden with the command line option --sysroot.
  * Update VCS attributes in the control file.

gcc-6 (6.4.0-22ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-22) unstable; urgency=medium

  * Update to SVN 20180921 (r264530) from the gcc-6-branch.
- Fix libsanitizer build failure on sparc64.

gcc-6 (6.4.0-21ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-21) unstable; urgency=medium

  * Update to SVN 20180921 (r264459) from the gcc-6-branch.
- Fix PR sanitizer/85835, PR tree-optimization/85859, PR target/87014,
  PR fortran/86116.
- Fix build failure with glibc 2.28.

gcc-6 (6.4.0-20ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-20) unstable; urgency=medium

  * Update to SVN 20180814 (r263539) from the gcc-6-branch.
- Fix PR libstdc++/83982, PR libstdc++/80893, PR libstdc++/80893,
  PR libstdc++/68519, PR libstdc++/86292, PR libstdc++/60555,
  PR libstdc++/86734, PR libstdc++/66145, PR libstdc++/85222,
  PR target/86197 (PPC).
- Fix PR bootstrap/86724. Closes: #905708.
  * Backport r235876 from the trunk (PPC). LP: #1783252.
  * Add some basic autopkg tests for Ada, C, C++, Go, OpenMP and Fortran.
  * Update the src_libgo_Makefile.in patch (Svante Signell). Closes: #905714.

gcc-6 (6.4.0-19ubuntu1) cosmic; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.

gcc-6 (6.4.0-19) unstable; urgency=medium

  * Update to SVN 20180727 (r263028) from the gcc-6-branch.
- Fix PR c++/86291, PR libgomp/84096, PR fortran/81304, PR fortran/81841,
  PR libstdc++/86272, PR c++/86210, PR c++/83059, PR c/84873, PR c/84873,
  PR debug/83550, PR c/82340, PR target/84168 (AArch64), PR target/84829,
  PR target/84786 (x86), PR tree-optimization/86231, PR middle-end/85878,
  PR target/85945, PR c++/85659, PR rtl-optimization/85431,
  PR rtl-optimization/85300, PR tree-optimization/85257, PR debug/85252,
  PR rtl-optimization/85167, PR inline-asm/85022, PR inline-asm/85034,
  PR inline-asm/85022, PR inline-asm/84941, PR debug/84875, PR c/84953,
  PR target/84899, PR c++/79085, PR target/84772, PR c++/84767,
  PR tree-optimization/84739, PR target/84700, PR inline-asm/84625,
  PR ipa/84425, PR c/82210, PR sanitizer/83987, PR rtl-optimization/83986,
  PR middle-end/84040, PR target/83930, PR preprocessor/83722,
  PR tree-optimization/83605, PR c++/83553, PR rtl-optimization/80747,
  PR rtl-optimization/83512, PR tree-optimization/83523,
  PR tree-optimization/83521, PR ipa/82801, PR ipa/83346, PR target/81906,
  PR c++/81212, PR target/78643, PR target/80583, PR target/80819,
  PR sanitizer/83014, PR middle-end/82253, PR target/82880, PR c++/82159,
  PR c++/82159, PR rtl-optimization/82192, PR tree-optimization/85989,
  PR tree-optimization/82108, PR tree-optimization/81410,
  PR tree-optimization/79920, PR middle-end/84607, PR middle-end/85588,
  PR middle-end/81884, PR middle-end/85244, PR tree-optimization/85597,
  PR middle-end/83623, PR tree-optimization/82264,
  PR tree-optimization/82285, PR tree-optimization/82402,
  PR tree-optimization/82697, PR middle-end/82765, PR middle-end/83713,
  PR c++/86291, PR c++/85147, PR c++/85140, PR c++/84791, PR c++/85076,
  PR c++/85068, PR 

[Group.of.nepali.translators] [Bug 1806580] Re: linux-snapdragon: 4.4.0-1106.111 -proposed tracker

2018-12-17 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-1106.111/snapdragon-4.4-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1806580

Title:
  linux-snapdragon: 4.4.0-1106.111 -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:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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: 1806569
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 02:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806580/+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 1806579] Re: linux-raspi2: 4.4.0-1102.110 -proposed tracker

2018-12-17 Thread Taihsiang Ho
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1102.110/raspi2-4.4-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1806579

Title:
  linux-raspi2: 4.4.0-1102.110 -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:
  Fix Released
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:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  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: 1806569
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 15:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Testing in progress

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