[Group.of.nepali.translators] [Bug 1039701] Re: Wrong RAM memory size

[Launchpad Bug Tracker]

This bug was fixed in the package lshw - 02.17-1.1ubuntu4

---
lshw (02.17-1.1ubuntu4) yakkety; urgency=medium

  * Use upstream solution for avoiding /dev/mem accesses on !x86,
fixing a memory size detection regression (LP: #1039701):
 - Drop: smbios-noscan.patch
 - Add: use-sysfs-for-DMI-info-when-available-696-666-664.patch

 -- dann frazier   Wed, 01 Jun 2016 15:01:29
-0600

** Changed in: lshw (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Wrong RAM memory size

Status in lshw:
  New
Status in MAAS:
  New
Status in landscape-client package in Ubuntu:
  Invalid
Status in lshw package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  New
Status in lshw source package in Xenial:
  In Progress

Bug description:
  [Impact]
  lshw is not using smbios to obtain hardware information. This is causing lshw 
to report incorrect information to user. For example I have a machine which has 
one physical CPU with 8 cores and 32G of RAM. lshw is reporting the machine has 
only one physical CPU with 0 cores and 32162MiB of RAM.

  [Test case]
  Run lshw and compare its reported values with what you know the physical 
system has. To help simplify testing I use this script 
http://paste.ubuntu.com/16900290/ which can be run with the command `sudo lshw 
-xml | ./parse_lshw`

  [Regression Potential]
  smbios-noscan.patch was introduced to prevent ARM systems from locking up 
when lshw is being run. We are replacing this patch with cherry picked 
commit(8237f8ebb92ebf684c0e6715cc6c28a3b2bb93b8) from 
https://ezix.org/src/pkg/lshw which was released with lshw-B.02.18. Potentially 
this could bring back https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 
however upstream considers it fixed with the previously mentioned cherry pick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lshw/+bug/1039701/+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 1039701] Re: Wrong RAM memory size

[dann frazier]

I've tested the proposed fix on two different ARM systems (APM Mustang
and Cavium ThunderX). The output is identical, and there is no system
crash. strace shows that no attempt is made to open /dev/mem, which was
the original issue in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=740034.

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

** Also affects: landscape-client (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: lshw (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: lshw (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: lshw (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

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

Title:
  Wrong RAM memory size

Status in lshw:
  New
Status in MAAS:
  New
Status in landscape-client package in Ubuntu:
  Invalid
Status in lshw package in Ubuntu:
  Confirmed
Status in landscape-client source package in Xenial:
  New
Status in lshw source package in Xenial:
  In Progress

Bug description:
  [Impact]
  lshw is not using smbios to obtain hardware information. This is causing lshw 
to report incorrect information to user. For example I have a machine which has 
one physical CPU with 8 cores and 32G of RAM. lshw is reporting the machine has 
only one physical CPU with 0 cores and 32162MiB of RAM.

  [Test case]
  Run lshw and compare its reported values with what you know the physical 
system has. To help simplify testing I use this script 
http://paste.ubuntu.com/16900290/ which can be run with the command `sudo lshw 
-xml | ./parse_lshw`

  [Regression Potential]
  smbios-noscan.patch was introduced to prevent ARM systems from locking up 
when lshw is being run. We are replacing this patch with cherry picked 
commit(8237f8ebb92ebf684c0e6715cc6c28a3b2bb93b8) from 
https://ezix.org/src/pkg/lshw which was released with lshw-B.02.18. Potentially 
this could bring back https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740034 
however upstream considers it fixed with the previously mentioned cherry pick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lshw/+bug/1039701/+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 1580674] Re: [SRU] mitaka point releases

[Corey Bryant]

** No longer affects: neutron-vpnaas (Ubuntu)

** No longer affects: neutron-fwaas (Ubuntu)

** No longer affects: neutron-lbaas (Ubuntu)

** No longer affects: neutron-fwaas (Ubuntu Xenial)

** No longer affects: neutron-lbaas (Ubuntu Xenial)

** No longer affects: neutron-vpnaas (Ubuntu Xenial)

** Summary changed:

- [SRU] mitaka point releases
+ [SRU] mitaka neutron 8.1.0 point 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/1580674

Title:
  [SRU] mitaka neutron 8.1.0 point release

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Landscape Server:
  Fix Committed
Status in Landscape Server 16.05 series:
  Fix Committed
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  Fix Released
Status in neutron-api package in Juju Charms Collection:
  Fix Released
Status in neutron-gateway package in Juju Charms Collection:
  Fix Released
Status in neutron-openvswitch package in Juju Charms Collection:
  Fix Released

Bug description:
  New point releases for misc openstack components for the mitaka
  release:

  neutron 8.1.0

  The following components have new upstream releases, but don't
  actually contain any new functionality, so we'll skip for Ubuntu:

  neutron-fwaas 8.1.0
  neutron-lbaas 8.1.0
  neutron-vpnaas 8.1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1580674/+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 1576893] Re: console colors are not correctly applied

[Mathieu Trudel-Lapierre]

** Changed in: console-setup (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  console colors are not correctly applied

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  In Progress

Bug description:
  At least on Xenial and onwards, our color scheme for the VTs is not
  being applied, since setvtrgb is not getting run on boot (it's still
  only an upstart job).

  Porting setvtrgb to a systemd unit makes the pretty colors appear, and
  I can get my debconf/newt prompts back with an aubergine background.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1576893/+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 1572697] Re: broken symlink console-setup.service [systemd]

[Mathieu Trudel-Lapierre]

** Changed in: console-setup (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  broken symlink console-setup.service [systemd]

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  In Progress

Bug description:
  keyboard-configuration 1.108ubuntu15 contains console-setup.service in
  /lib/systemd/system/multi-user.target.wants, but as a broken symlink:

  $ dpkg -L keyboard-configuration | grep multi-user.target.wants
  /lib/systemd/system/multi-user.target.wants
  /lib/systemd/system/multi-user.target.wants/console-setup.service

  $ sudo find -L /lib/systemd/system -type l -ls
1315455  0 lrwxrwxrwx   1 root root   22 Apr 20 03:11 
/lib/systemd/system/multi-user.target.wants/console-setup.service -> 
/console-setup.service

  
  Symlink should point to ../console-setup.service instead.

  I originally reported this in
  https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1534121
  against console-setup, which was the wrong package to refer to. My
  apologies for messing that up.

  
  Additional info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy keyboard-configuration
  keyboard-configuration:
Installed: 1.108ubuntu15
Candidate: 1.108ubuntu15
Version table:
   *** 1.108ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1572697/+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 1587988] Re: LDAP ping doesn't prefers site-local DCS

[Chris J Arges]

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

** Also affects: sssd (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

** Also affects: sssd (Ubuntu Yakkety)
   Importance: High
   Status: 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/1587988

Title:
  LDAP ping doesn't prefers site-local DCS

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Trusty:
  New
Status in sssd source package in Wily:
  New
Status in sssd source package in Xenial:
  New
Status in sssd source package in Yakkety:
  Fix Released

Bug description:
  [Description]

  If an active directory domain has any domain controllers defined that are not 
accesible
  from a specific location, then  sssd should prefer site-local DCs in LDAP 
ping.

  This behavior has been fixed on upstream via:
  
https://git.fedorahosted.org/cgit/sssd.git/commit/?id=a1c6869c67fcf4971ac843315b97bf46893ca92d

  [Reproduction]

  
  [Possible regressions]

  * None identified

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1587988/+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 1574090] Re: Brasero not translated at all on ubuntu 16.04

[Mathew Hodson]

** Project changed: brasero => ubuntu-translations

** Changed in: ubuntu-translations
   Importance: High => Undecided

** Changed in: ubuntu-translations
   Status: Unknown => New

** Changed in: ubuntu-translations
 Remote watch: GNOME Bug Tracker #765478 => None

** No longer affects: ubuntu-translations

** Bug watch removed: GNOME Bug Tracker #765478
   https://bugzilla.gnome.org/show_bug.cgi?id=765478

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

Title:
  Brasero not translated at all on ubuntu 16.04

Status in brasero package in Ubuntu:
  Fix Released
Status in brasero source package in Xenial:
  Fix Committed

Bug description:
  To the sponsor: Please use the same patch for Xenial, changing the
  version to 3.12.1-1ubuntu2.1.

  [Impact]

  Translations are not enabled. The attached patch fixes it.

  [Test Case]

  1. Install some other language but english and make it the display
  language.

  2. Start brasero and find that it's still displayed in English.

  [Regression Potential]

  Neglectable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1574090/+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 1580463] Re: Snap blocks access to system input methods (ibus, fctix, ...)

[Jamie Strandboge]

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

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

** Changed in: apparmor (Ubuntu Yakkety)
   Status: New => In Progress

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

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

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: apparmor (Ubuntu Yakkety)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  Snap blocks access to system input methods (ibus, fctix, ...)

Status in apparmor package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged
Status in im-config source package in Xenial:
  In Progress
Status in snapd source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  In Progress
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Confirmed

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in progress. Currently the change should not
  regress snapdsbehavior due to other issues surrounding using ibus
  unrelated to security policy.

  = Original description =
  Currently snaps can't access ibus/fcitx from the system, do we need a 
interface for input methods there?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1580463/+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 1559072] Re: exceptions.from_response with webob 1.6.0 results in "AttributeError: 'unicode' object has no attribute 'get'"

[Scott Moser]

** No longer affects: ubuntu

** No longer affects: Ubuntu Yakkety

** No longer affects: Ubuntu Xenial

** Also affects: python-novaclient (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python-novaclient (Ubuntu)
   Status: New => Confirmed

** Also affects: python-novaclient (Ubuntu Yakkety)
   Importance: Undecided
   Status: Confirmed

** Also affects: python-novaclient (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: python-novaclient (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: python-novaclient (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: python-novaclient (Ubuntu Yakkety)
   Importance: Undecided => High

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

Title:
  exceptions.from_response with webob 1.6.0 results in "AttributeError:
  'unicode' object has no attribute 'get'"

Status in networking-midonet:
  Fix Released
Status in python-cinderclient:
  New
Status in python-novaclient:
  Fix Released
Status in python-openstackclient:
  Invalid
Status in python-novaclient package in Ubuntu:
  Confirmed
Status in python-novaclient source package in Xenial:
  Confirmed
Status in python-novaclient source package in Yakkety:
  Confirmed

Bug description:
  Running on Ubuntu 14.04.
  After installing nova from source in either the Liberty release or Mitaka, 
with WebOb 1.6.0, running any nova command generated this error:
  root@openstack-ubu-controller:~# nova service-list
  ERROR (AttributeError): 'unicode' object has no attribute 'get'

  The equivalent openstack commands work correctly. After downgrading
  WebOb to 1.5.1 AND restarting the nova-api service everything works.

  Detailed output from nova -debug service-list with the error:

  root@openstack-ubu-controller:~# nova --debug service-list
  DEBUG (extension:157) found extension EntryPoint.parse('v2token = 
keystoneauth1.loading._plugins.identity.v2:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('admin_token = 
keystoneauth1.loading._plugins.admin_token:AdminToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
  DEBUG (extension:157) found extension EntryPoint.parse('v2password = 
keystoneauth1.loading._plugins.identity.v2:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3password = 
keystoneauth1.loading._plugins.identity.v3:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
  DEBUG (extension:157) found extension EntryPoint.parse('token = 
keystoneauth1.loading._plugins.identity.generic:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3token = 
keystoneauth1.loading._plugins.identity.v3:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('password = 
keystoneauth1.loading._plugins.identity.generic:Password')
  DEBUG (session:248) REQ: curl -g -i -X GET http://10.0.1.3:5000/v2.0 -H 
"Accept: application/json" -H "User-Agent: keystoneauth1/2.3.0 
python-requests/2.9.1 CPython/2.7.6"
  INFO (connectionpool:207) Starting new HTTP connection (1): 10.0.1.3
  DEBUG (connectionpool:387) "GET /v2.0 HTTP/1.1" 200 334
  DEBUG (session:277) RESP: [200] Content-Length: 334 Vary: X-Auth-Token 
Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection: 
Keep-Alive Date: Fri, 18 Mar 2016 12:41:58 GMT Content-Type: application/json 
x-openstack-request-id: req-a0c68cd5-ea29-4391-942f-130cc69d15f8 
  RESP BODY: {"version": {"status": "stable", "updated": 
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": 
[{"href": "http://10.0.1.3:5000/v2.0/;, "rel": "self"}, {"href": 
"http://docs.openstack.org/;, "type": "text/html", "rel": "describedby"}]}}

  DEBUG (v2:63) Making authentication request to 
http://10.0.1.3:5000/v2.0/tokens
  DEBUG (connectionpool:387) "POST /v2.0/tokens HTTP/1.1" 200 2465
  DEBUG (session:248) REQ: curl -g -i -X GET 
http://10.0.1.3:8774/v1.1/b77d640e127e488fb42a7c0716ba53a5 -H "User-Agent: 
python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: 
{SHA1}381893576ad46c62b587f4963d769b89441b919a"
  INFO (connectionpool:207) Starting new HTTP connection (1): 10.0.1.3
  DEBUG (connectionpool:387) "GET /v1.1/b77d640e127e488fb42a7c0716ba53a5 
HTTP/1.1" 404 112
  DEBUG (session:277) RESP: [404] Date: Fri, 18 Mar 2016 12:41:59 GMT 
Connection: keep-alive Content-Type: application/json; charset=UTF-8 
Content-Length: 112 X-Compute-Request-Id: 
req-f10a2016-9a88-48fd-af1d-5f800fc9e11a 
  RESP BODY: {"message": "The resource could not be found.\n\n\n", 
"code": "404 Not Found", "title": "Not 

[Group.of.nepali.translators] [Bug 1587947] Re: ERROR (AttributeError): 'unicode' object has no attribute 'get'

[Scott Moser]

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

fix seems to be attached.


** Patch added: "seemingly working fix"
   
https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/1587947/+attachment/4674449/+files/fix.diff

** Also affects: python-novaclient (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: python-novaclient (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: python-novaclient (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: python-novaclient (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: python-novaclient (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: python-novaclient (Ubuntu Yakkety)
   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/1587947

Title:
  ERROR (AttributeError): 'unicode' object has no attribute 'get'

Status in python-novaclient package in Ubuntu:
  Confirmed
Status in python-novaclient source package in Xenial:
  Confirmed
Status in python-novaclient source package in Yakkety:
  Confirmed

Bug description:
  $ nova --debug list
  DEBUG (extension:157) found extension EntryPoint.parse('v2token = 
keystoneauth1.loading._plugins.identity.v2:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('admin_token = 
keystoneauth1.loading._plugins.admin_token:AdminToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
  DEBUG (extension:157) found extension EntryPoint.parse('v2password = 
keystoneauth1.loading._plugins.identity.v2:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3password = 
keystoneauth1.loading._plugins.identity.v3:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
  DEBUG (extension:157) found extension EntryPoint.parse('token = 
keystoneauth1.loading._plugins.identity.generic:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3token = 
keystoneauth1.loading._plugins.identity.v3:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('password = 
keystoneauth1.loading._plugins.identity.generic:Password')
  DEBUG (session:248) REQ: curl -g -i -X GET https://iad2.dream.io:5000/v2.0 -H 
"Accept: application/json" -H "User-Agent: keystoneauth1/2.4.0 
python-requests/2.10.0 CPython/2.7.11+"
  INFO (connectionpool:790) Starting new HTTPS connection (1): iad2.dream.io
  DEBUG (connectionpool:395) "GET /v2.0 HTTP/1.1" 200 340
  DEBUG (session:277) RESP: [200] Date: Wed, 01 Jun 2016 15:10:50 GMT Server: 
Apache Vary: X-Auth-Token x-openstack-request-id: 
req-4bde00b2-71da-4330-8b40-7a922f1b8748 Content-Length: 340 Content-Type: 
application/json 
  RESP BODY: {"version": {"status": "stable", "updated": 
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links": 
[{"href": "https://iad2.dream.io:5000/v2.0/;, "rel": "self"}, {"href": 
"http://docs.openstack.org/;, "type": "text/html", "rel": "describedby"}]}}

  DEBUG (v2:63) Making authentication request to 
https://iad2.dream.io:5000/v2.0/tokens
  DEBUG (connectionpool:395) "POST /v2.0/tokens HTTP/1.1" 200 2443
  DEBUG (session:248) REQ: curl -g -i -X GET 
https://iad2.dream.io:8774/v2/5332521f01724d928daf57ebbde20872 -H "User-Agent: 
python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: 
{SHA1}dd45d141aab134bc1500669a82e13733106aa2a7"
  INFO (connectionpool:790) Starting new HTTPS connection (1): iad2.dream.io
  DEBUG (connectionpool:395) "GET /v2/5332521f01724d928daf57ebbde20872 
HTTP/1.1" 404 112
  DEBUG (session:277) RESP: [404] Content-Length: 112 Content-Type: 
application/json; charset=UTF-8 X-Compute-Request-Id: 
req-256881a6-78f7-4870-9923-b5de745afa94 Date: Wed, 01 Jun 2016 15:10:51 GMT 
  RESP BODY: {"message": "The resource could not be found.\n\n\n", 
"code": "404 Not Found", "title": "Not Found"}

  DEBUG (shell:1082) 'unicode' object has no attribute 'get'
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/novaclient/shell.py", line 1080, in 
main
  OpenStackComputeShell().main(argv)
File "/usr/lib/python2.7/dist-packages/novaclient/shell.py", line 914, in 
main
  api_version = api_versions.discover_version(self.cs, api_version)
File "/usr/lib/python2.7/dist-packages/novaclient/api_versions.py", line 
267, in discover_version
  client)
File "/usr/lib/python2.7/dist-packages/novaclient/api_versions.py", line 
248, in _get_server_version_range
  version = client.versions.get_current()
File 

[Group.of.nepali.translators] [Bug 1585156] Re: SRU: update creduce to the final 2.5.0 release

[Launchpad Bug Tracker]

This bug was fixed in the package creduce - 2.5.0-0ubuntu1

---
creduce (2.5.0-0ubuntu1) xenial-proposed; urgency=medium

  * SRU LP: #1585156, backport to 16.04 LTS.

creduce (2.5.0-1) unstable; urgency=medium

  * C-Reduce 2.5.0 release.
  * Remove (build-)dependency on delta.

 -- Matthias Klose   Tue, 24 May 2016 12:57:07 +0200

** Changed in: creduce (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/1585156

Title:
  SRU: update creduce to the final 2.5.0 release

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

Bug description:
  SRU: update creduce (a tool helping to reduce test cases) to the final
  2.5.0 release.  Compared to the snapshot in 16.04 LTS, the final
  release includes two bug fixes (in clang_delta). Everything else in
  the diff are cleanups, including a local patch accepted upstream.

  release summary: http://www.flux.utah.edu/listarchives/creduce-
  dev/msg00273.html

  Acceptence criteria: builds on all architectures and passes the tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/creduce/+bug/1585156/+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 1582982] Re: thermald 1.5-2ubuntu1 failures in ubuntu16.04

[Colin Ian King]

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

** Changed in: thermald (Ubuntu Xenial)
   Status: New => In Progress

** No longer affects: thermald (Ubuntu Trusty)

** Changed in: thermald (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Xenial)
   Importance: Undecided => Low

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

Title:
  thermald 1.5-2ubuntu1 failures in ubuntu16.04

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

Bug description:
  [SRU][XENIAL] Justification:

  thermald is reporting non-critical errors whereas these should be
  downgraded and being reported as warnings so as not to alarm users.

  [FIX]
  Upstream 
commit,https://github.com/01org/thermal_daemon/commit/8280fd7ec6cff6db6463c8a1b01d2e427e418226

  this is already in thermald in Yakkety and working fine.

  [Regression Potential]
  Minimal, this changes the status levels of various error messages, so core 
thermald functional is not touched at all by this fix.

  

  Hi. I am still getting the same failure message despite using the
  latest thermald version. Can you tell me how to solve these failures.

  May 18 10:08:11 Eliot thermald[1012]: failed to open /dev/acpi_thermal_rel
  May 18 10:08:11 Eliot thermald[1012]: failed to open /dev/acpi_thermal_rel
  May 18 10:08:11 Eliot thermald[1012]: TRT/ART read failed
  May 18 10:08:12 Eliot thermald[1012]: sysfs read failed 
constraint_0_max_power_uw
  May 18 10:08:12 Eliot thermald[1012]: sysfs write failed trip_point_0_temp
  May 18 10:08:12 Eliot thermald[1012]: sysfs write failed trip_point_0_temp

  $: dpkg -l thermald
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version Architecture Description
  
+++-=-===-===-===
  ii thermald 1.5-2ubuntu1 amd64 Thermal monitoring and controlling daemon

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy thermald
  thermald:
    Installed: 1.5-2ubuntu1
    Candidate: 1.5-2ubuntu1
    Version table:
   *** 1.5-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.5-2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1582982/+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 1572661] Re: Ubuntu Gnome Bug -evolution translation

[Launchpad Bug Tracker]

This bug was fixed in the package evolution - 3.18.5.2-0ubuntu3

---
evolution (3.18.5.2-0ubuntu3) xenial; urgency=medium

  * debian/control:
- remove the X-Ubuntu-Use-Langpack line rather than commenting it
  due pkgstriptranslations not understanding the # (being fixed,
  but meanwhile let's get that SRU working)

evolution (3.18.5.2-0ubuntu2) xenial; urgency=medium

  * debian/control:
- don't define X-Ubuntu-Use-Langpack, due to a langpack-o-matic bug the
  evolution translations are missing from xenial. The tools are fixed
  but langpack updates are too much work to do one for that specific issue
  so we are going back to include translations until the next export.
  (lp: #1572661)

 -- Sebastien Bacher   Wed, 25 May 2016 08:19:06
+0200

** Changed in: evolution (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/1572661

Title:
  Ubuntu Gnome Bug -evolution translation

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

Bug description:
  * Impact
  evolution is not translated

  * Test case
  start evolution under a non english locale, it should be translated

  * Regression potential
  none, that's a small packaging change to add translations to the deb

  -

  Ubuntu Gnome 16.04 RC

  Evolution is not translated in another language. It is in english
  only.

  Affects at least french (canadian), Norwegian (Bokmål) and german
  (seen on a Google Plus post :

  https://plus.google.com/+UbuntuGNOMEorg/posts/bsFL3SLf6ot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1572661/+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 1538438] Re: apt-helper crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.12~ubuntu16.04.1

---
apt (1.2.12~ubuntu16.04.1) xenial; urgency=medium

  * Upload 1.2.12 micro-release to Xenial (LP: #1538438, #1580952)

apt (1.2.12) unstable; urgency=medium

  [ Patrick Cable ]
  * refactored no_proxy code to work regardless of where https proxy is set

  [ James McCoy ]
  * deb822: Restore support for -{Add,Remove}

  [ David Kalnischkies ]
  * don't show NO_PUBKEY warning if repo is signed by another key
(Closes: 618445)
  * allow redirection for items without a space in the desc again
  * don't sent uninstallable rc-only versions via EDSP
  * respect user pinning in M-A:same version (un)screwing

  [ Julian Andres Klode ]
  * update: Run Post-Invoke-Success if not all sources failed
  * debian/gbp.conf: Set debian-branch to 1.2.y

  [ Frans Spiesschaert ]
  * Dutch program translation update (Closes: 823976)

apt (1.2.11) unstable; urgency=medium

  [ David Kalnischkies ]
  * ensure transaction states are changed only once
  * stop handling items in doomed transactions.
Thanks to Barr Detwix & Vincent Lefevre for log files (Closes: 817240)
  * do not require non-broken systems in 'upgrade'
  * detect compressed status files on extension again
  * recheck Pre-Depends satisfaction in SmartConfigure (LP: #1569099)
  * fix Alt-Filename handling of file method
  * allow uncompressed files to be empty in store again
  * silently skip acquire of empty index files
  * ensure outdated files are dropped without lists-cleanup

  [ Kelemen Gábor ]
  * Hungarian program translation update (Closes: 820638)

 -- Adam Conrad   Thu, 12 May 2016 04:08:00 -0600

** Changed in: apt (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/1538438

Title:
  apt-helper crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

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

Bug description:
  Test Case
  --
  Given that there are thousands of these crashes in the Error Tracker, just 
make sure the new version doesn't appear there.

  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/apt/apt-helper%3A6%3A__gnu_cxx%3A%3A__verbose_terminate_handler%3A__cxxabiv1%3A%3A__terminate%3Astd%3A%3Aterminate%3A__cxxabiv1%3A%3A__cxa_throw%3Astd%3A%3A__throw_out_of_range_fmt

  Original Description
  
  After installing flashplugin-installer I get a prompt noting:
  [START]
  Failure to download extra data files

  The following packages requested additional data downloads after
  package installation, but the data could not be downloaded or could
  not be processed.

  flashplugin-installer

  The download will be attempted again later, or you can try the download again 
now.  Running this command requires an active Internet connection.
  [END]

  Clicking the button Run this action now causes this crash
  consistently.

  Unfortunately, this has the negative outcome of disallowing folks who
  use Firefox from being able to update, or install Flash.

  There are a fair number of these events logged in errors.ubuntu.com.

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: apt 1.1.10
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Wed Jan 27 01:36:34 2016
  ExecutablePath: /usr/lib/apt/apt-helper
  InstallationDate: Installed on 2015-04-25 (276 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/apt/apt-helper download-file 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20151228.1.orig.tar.gz
 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20151228.1.orig.tar.gz
 SHA256:d322547d4542eeed2f57469cc0d3c10e9a55af6632c05be9fe8b6c6a0dbcffdb
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)Signal: 6SourcePackage: apt
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::__throw_out_of_range_fmt(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt-helper crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: Upgraded to xenial on 2016-01-27 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1538438/+subscriptions

[Group.of.nepali.translators] [Bug 1580952] Re: [SRU] Update apt/xenial to 1.2.12

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.2.12~ubuntu16.04.1

---
apt (1.2.12~ubuntu16.04.1) xenial; urgency=medium

  * Upload 1.2.12 micro-release to Xenial (LP: #1538438, #1580952)

apt (1.2.12) unstable; urgency=medium

  [ Patrick Cable ]
  * refactored no_proxy code to work regardless of where https proxy is set

  [ James McCoy ]
  * deb822: Restore support for -{Add,Remove}

  [ David Kalnischkies ]
  * don't show NO_PUBKEY warning if repo is signed by another key
(Closes: 618445)
  * allow redirection for items without a space in the desc again
  * don't sent uninstallable rc-only versions via EDSP
  * respect user pinning in M-A:same version (un)screwing

  [ Julian Andres Klode ]
  * update: Run Post-Invoke-Success if not all sources failed
  * debian/gbp.conf: Set debian-branch to 1.2.y

  [ Frans Spiesschaert ]
  * Dutch program translation update (Closes: 823976)

apt (1.2.11) unstable; urgency=medium

  [ David Kalnischkies ]
  * ensure transaction states are changed only once
  * stop handling items in doomed transactions.
Thanks to Barr Detwix & Vincent Lefevre for log files (Closes: 817240)
  * do not require non-broken systems in 'upgrade'
  * detect compressed status files on extension again
  * recheck Pre-Depends satisfaction in SmartConfigure (LP: #1569099)
  * fix Alt-Filename handling of file method
  * allow uncompressed files to be empty in store again
  * silently skip acquire of empty index files
  * ensure outdated files are dropped without lists-cleanup

  [ Kelemen Gábor ]
  * Hungarian program translation update (Closes: 820638)

 -- Adam Conrad   Thu, 12 May 2016 04:08:00 -0600

** Changed in: apt (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/1580952

Title:
  [SRU] Update apt/xenial to 1.2.12

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

Bug description:
  Since the version in xenial, we released two more new bug fix releases
  upstream. We'd like to get this into xenial under the "New upstream
  microreleases" rule.

  [Impact]
  Most visible for xenial users:
  -> AppStream now updates even if some repositories failed to be fetched (see 
#1562733 for reference)

  -> Third-party repositories will no longer print "Unknown public key"
  type errors when a new key was added (and another key was successfully
  used to verify the repo). This happen(s/ed) on the Chrome
  repositories, for example, and leads users to manually receive keys
  from the key server which weakens their security.

  The rest are other bugfixes. Full changelogs:

  apt (1.2.11) unstable; urgency=medium

    [ David Kalnischkies ]
    * ensure transaction states are changed only once
  -> more sanity checks
    * stop handling items in doomed transactions.
  Thanks to Barr Detwix & Vincent Lefevre for log files (Closes: 817240)
  -> fixes a lot of "E: Unpatched file  doesn't exist (anymore)!" that happen 
sometimes
    * do not require non-broken systems in 'upgrade'
  -> allows people to fix their broken system in upgrade
    * detect compressed status files on extension again
  -> regression from 1.1, single flag changed
    * recheck Pre-Depends satisfaction in SmartConfigure (LP: #1569099)
  -> already in xenial
    * fix Alt-Filename handling of file method
  -> off-by-one error when removing file extensions to get uncompressed filename
    * allow uncompressed files to be empty in store again
  -> this caused failures when fetching empty files
    * silently skip acquire of empty index files
  -> clean up of the above
    * ensure outdated files are dropped without lists-cleanup
  -> ensures proper cleanup

    [ Kelemen Gábor ]
    * Hungarian program translation update (Closes: 820638)

   -- Julian Andres Klode   Mon, 25 Apr 2016 15:23:49
  +0200

  apt (1.2.12) unstable; urgency=medium

    [ Patrick Cable ]
    * refactored no_proxy code to work regardless of where https proxy is set
  -> no_proxy should really work for all ways to set an https proxy (actually 
LP: #1575877)

    [ James McCoy ]
    * deb822: Restore support for -{Add,Remove}
  -> Adds - in front of Add and Remove strings...

    [ David Kalnischkies ]
    * don't show NO_PUBKEY warning if repo is signed by another key
  (Closes: 618445)
  -> this helps the DSA->RSA key transitions, at it gets rid of the unkown 
public key warnings on the Chrome repository
    * allow redirection for items without a space in the desc again
  -> small bug fix
    * don't sent uninstallable rc-only versions via EDSP
  -> Fixes EDSP/CUDF solvers to not try to install package versions in 
config-file state
    * respect user pinning in M-A:same version (un)screwing
  -> used the wrong function get a 

[Group.of.nepali.translators] [Bug 1568790] Re: power applet doesn't update charge unless it is removed/plugging in charger

[Daniel Holbach]

** Also affects: cinnamon-settings-daemon (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cinnamon-settings-daemon (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  power applet doesn't update charge unless it is removed/plugging in
  charger

Status in cinnamon-settings-daemon package in Ubuntu:
  Fix Released
Status in cinnamon-settings-daemon source package in Xenial:
  New

Bug description:
  The cinnamon power applet doesn't update the charge on Ubuntu Xenial.
  It updates when I start/stop charging my laptop and when the battery
  reaches 10%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinnamon-settings-daemon/+bug/1568790/+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 1582340] Re: [SRU] Sync drupal7 7.43-3 (universe) from Debian unstable (main)

[Daniel Holbach]

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

** Changed in: drupal7 (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/1582340

Title:
  [SRU] Sync drupal7 7.43-3 (universe) from Debian unstable (main)

Status in drupal7 package in Ubuntu:
  Fix Released
Status in drupal7 source package in Xenial:
  New

Bug description:
  Drupal7 in 16.04 has been left as broken while we wait on upstream
  Drupal7 to gain PHP7.0 compatibility. This has been achieved in
  Debian's current version, which we should be able to sync as we have
  no delta currently.

  [Impact]

   * drupal7 is currently uninstallable in 16.04.

  [Test Case]

   * There is no test case for this issue, other than attempting to
  install drupal7 itself, which will currently fail due to php5
  dependencies.

  [Regression Potential]

   * As drupal7 is currently uninstallable, there is no possibility of
  regression in 16.04 itself.

  [Other Info]
   
   * To reiterate, the plan for drupal7 in 16.04 was to wait for PHP7 
compatibility to be available and to SRU in the corresponding version.

  Please sync drupal7 7.43-3 (universe) from Debian unstable (main)

  Changelog entries since current xenial version 7.41-1:

  drupal7 (7.43-3) unstable; urgency=medium

    * Moved the farbstatic sources from debian/missing-sources
  todebian/missing-sources/misc, to keep lintian happy
    * The right name for one of our conditional dependencies is no longer
  php-sqlite, but php-sqlite3. Thanks to Nish Aravamudan for pointing
  this out!

   -- Gunnar Wolf   Mon, 09 May 2016 12:25:34 -0500

  drupal7 (7.43-2) unstable; urgency=medium

    * Update dependencies to use PHP 7 instead of 5 (Closes: #821482)
    * Updated debian/watch to work reliably
    * Standards-version 3.9.6.0→3.9.8 (no changes needed)

   -- Gunnar Wolf   Mon, 09 May 2016 10:54:11 -0500

  drupal7 (7.43-1) unstable; urgency=high

    * New upstream version
    * Fixes several security vulnerabilities (SA-CORE-2016-001): File
  upload access bypass and DoS, brute force amplification attack via
  XML-RPC, open redirect via path manipulation, reflected file
  download, wrong modes set on some user accounts setting saves,
  information disclosure of email addresses
    * Several non-security bugfixes from 7.42 included
    * Fix typo in README.Debian
    * Add several needed lintian overrides

   -- Gunnar Wolf   Thu, 25 Feb 2016 22:43:55 -0600

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drupal7/+bug/1582340/+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 1538438] Re: apt-helper crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Julian Andres Klode]

The linked commit was included in 1.3~exp1 in yakkety

** Changed in: apt (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  apt-helper crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  Test Case
  --
  Given that there are thousands of these crashes in the Error Tracker, just 
make sure the new version doesn't appear there.

  Errors Bucket
  -
  
https://errors.ubuntu.com/bucket/?id=/usr/lib/apt/apt-helper%3A6%3A__gnu_cxx%3A%3A__verbose_terminate_handler%3A__cxxabiv1%3A%3A__terminate%3Astd%3A%3Aterminate%3A__cxxabiv1%3A%3A__cxa_throw%3Astd%3A%3A__throw_out_of_range_fmt

  Original Description
  
  After installing flashplugin-installer I get a prompt noting:
  [START]
  Failure to download extra data files

  The following packages requested additional data downloads after
  package installation, but the data could not be downloaded or could
  not be processed.

  flashplugin-installer

  The download will be attempted again later, or you can try the download again 
now.  Running this command requires an active Internet connection.
  [END]

  Clicking the button Run this action now causes this crash
  consistently.

  Unfortunately, this has the negative outcome of disallowing folks who
  use Firefox from being able to update, or install Flash.

  There are a fair number of these events logged in errors.ubuntu.com.

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: apt 1.1.10
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  Date: Wed Jan 27 01:36:34 2016
  ExecutablePath: /usr/lib/apt/apt-helper
  InstallationDate: Installed on 2015-04-25 (276 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/apt/apt-helper download-file 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20151228.1.orig.tar.gz
 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20151228.1.orig.tar.gz
 SHA256:d322547d4542eeed2f57469cc0d3c10e9a55af6632c05be9fe8b6c6a0dbcffdb
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)Signal: 6SourcePackage: apt
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   std::__throw_out_of_range_fmt(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: apt-helper crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: Upgraded to xenial on 2016-01-27 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1538438/+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 1580523] Re: Job rpcbind.service/start deleted to break ordering cycle

[Robie Basak]

** Also affects: rpcbind (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/1580523

Title:
  Job rpcbind.service/start deleted to break ordering cycle

Status in rpcbind package in Ubuntu:
  Fix Released
Status in rpcbind source package in Xenial:
  New

Bug description:
  Here is the error:

  [   12.295037] systemd[1]: remote-fs-pre.target: Found ordering cycle on 
remote-fs-pre.target/start
  [   12.295043] systemd[1]: remote-fs-pre.target: Found dependency on 
rpcbind.service/start
  [   12.295045] systemd[1]: remote-fs-pre.target: Found dependency on 
rpcbind.socket/start
  [   12.295047] systemd[1]: remote-fs-pre.target: Found dependency on 
sysinit.target/start
  [   12.295048] systemd[1]: remote-fs-pre.target: Found dependency on 
zfs-fuse.service/start
  [   12.295050] systemd[1]: remote-fs-pre.target: Found dependency on 
remote-fs.target/start
  [   12.295052] systemd[1]: remote-fs-pre.target: Found dependency on 
remote-fs-pre.target/start
  [   12.295054] systemd[1]: remote-fs-pre.target: Breaking ordering cycle by 
deleting job rpcbind.service/start
  [   12.295056] systemd[1]: rpcbind.service: Job rpcbind.service/start deleted 
to break ordering cycle starting with remote-fs-pre.target/start

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rpcbind 0.2.3-0.2
  Uname: Linux 4.5.3-040503-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed May 11 11:46:51 2016
  JournalErrors:
   -- Logs begin at Wed 2016-05-11 11:46:34 CEST, end at Wed 2016-05-11 
11:46:46 CEST. --
   May 11 11:46:34 hostname /usr/lib/gdm3/gdm-x-session[2998]: QXcbWindow: 
Unhandled client message: "_NET_CURRENT_DESKTOP"
   May 11 11:46:46 hostname /usr/lib/gdm3/gdm-x-session[2998]: QXcbWindow: 
Unhandled client message: "_NET_CURRENT_DESKTOP"
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rpcbind
  UpgradeStatus: Upgraded to xenial on 2016-03-31 (40 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1580523/+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 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind

[Laurent Bigonville]

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

** Also affects: rpcbind (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/1558196

Title:
  ypbind not able to socket activate rpcbind under systemd, fails at
  boot unless something else starts rpcbind

Status in nis package in Ubuntu:
  Triaged
Status in rpcbind package in Ubuntu:
  Fix Released
Status in nis source package in Xenial:
  New
Status in rpcbind source package in Xenial:
  New
Status in nis package in Debian:
  Fix Released

Bug description:
  did apt-get update/upgrade  March 16, 2016 
  Description:Ubuntu Xenial Xerus (development branch)
  Release:16.04

  rpcbind does not start on boot, tried various systemd debugging steps
  with no clues. After boot systemctl start rpcbind works. There is  a
  /etc/init.d/rpcbind and a /lib/systemd/system/rpcbind.service config
  files which is confusing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+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 1581869] Re: CVE-2016-4581

[Steve Beattie]

** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2016-4581

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Committed
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-lts-wily source package in Trusty:
  Fix Committed
Status in linux-lts-xenial source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako 

[Group.of.nepali.translators] [Bug 1566581] Re: CVE-2016-3689

[Steve Beattie]

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

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New => Invalid

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

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

Title:
  CVE-2016-3689

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Released
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status