[Group.of.nepali.translators] [Bug 1647017] [NEW] [SRU] Update xenial and yakkety to match zesty version

[Stéphane Graber]

Public bug reported:

go-lxc is used by LXD as the way to interact with liblxc.
As a result, upstream changes for it are usually restricted to bugfixes or 
minor improvements (for things like CRIU support). To make our lives easier, we 
like to keep go-lxc in sync in all supported Ubuntu releases to match the LXC 
version that we also keep in sync there.

To do so, we need to SRU a new version of go-lxc to xenial and yakkety, with 
the following upstream changelog:
 - bindings C: check for LXC_DEVEL in version.h file
 - bindings go: check for LXC_DEVEL in version.h
 - lxc-binding: add binding for c->attach()
 - container: add RunCommandNoWait()
 - lxc_test: add test for RunCommandNoWait()
 - Move LXC_DEVEL define to after version.h include
 - c/r: make sure container is running before doing a dump
 - container, error: return correct error
 - Fix TestRunCommandNoWait failure
 - tests: Skip architecture test on !x86
 - tests: Make skip messages consistent
 - Run "go fmt"

The xenial SRU will not require any extra work. The next LXD upload will
simply pick up the new go-lxc at build time.

For the yakkety SRU, we will need to upload a no change rebuild of LXD
to build against the new go-lxc and we'll need them both to be released
at the same time. That's because of the addition of the "attach()"
function which changes the Go shared library hash.

** Affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: lxd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Affects: lxd (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: Triaged

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu)
   Status: New => Fix Released

** Also affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** No longer affects: lxd (Ubuntu Xenial)

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

** Changed in: lxd (Ubuntu)
   Status: Invalid => Fix Released

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

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: lxd (Ubuntu Yakkety)
   Status: In Progress => Triaged

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Yakkety)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxd (Ubuntu Yakkety)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

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

Title:
  [SRU] Update xenial and yakkety to match zesty version

Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial:
  In Progress
Status in golang-gopkg-lxc-go-lxc.v2 source package in Yakkety:
  In Progress
Status in lxd source package in Yakkety:
  Triaged

Bug description:
  go-lxc is used by LXD as the way to interact with liblxc.
  As a result, upstream changes for it are usually restricted to bugfixes or 
minor improvements (for things like CRIU support). To make our lives easier, we 
like to keep go-lxc in sync in all supported Ubuntu releases to match the LXC 
version that we also keep in sync there.

  To do so, we need to SRU a new version of go-lxc to xenial and yakkety, with 
the following upstream changelog:
   - bindings C: check for LXC_DEVEL in version.h file
   - bindings go: check for LXC_DEVEL in version.h
   - lxc-binding: add binding for c->attach()
   - container: add RunCommandNoWait()
   - lxc_test: add test for RunCommandNoWait()
   - Move LXC_DEVEL define to after version.h include
   - c/r: make sure container is running before doing a dump
   - container, error: return correct error
   - Fix TestRunCommandNoWait failure
   - tests: Skip architecture test on !x86
   - tests: Make skip messages consistent
   - Run "go fmt"

  The xenial SRU will not require any extra work. The next LXD upload
  will simply pick up the new go-lxc at build time.

  For the yakkety SRU, we will need to upload a no change 

[Group.of.nepali.translators] [Bug 1647012] [NEW] SRU of LXCFS 2.0.5 (upstream bugfix release)

[Stéphane Graber]

Public bug reported:

LXCFS upstream released LXCFS 2.0.5 as a bugfix release with following 
changelog:
  - Add Documentation key to systemd unit
  - bindings: allow getattr on O_WRONLY files
  - bindings: remove noop check
  - fix Active/Inactive /proc/meminfo
  - macro: add header for shared macros
  - pam_cgfs: reimplement and add cgroupfs v2 support
  - pam_cgfs: re-use cgroups that already belong to us
  - pam_cgfs: handle cgroupfs v1 cpuset controller
  - pam_cgfs: improve logging
  - cgroups: handle non-existent isolcpus file

Just like Ubuntu itself, upstream releases long term support releases,
as is 2.0 and then periodic point releases including all the accumulated
bugfixes.

Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.

This bugfix release has already been uploaded to Zesty and automatically
backported in the upstream PPAs for all Ubuntu releases. So far without
any reported regression.

This should qualify under the minor upstream bugfix release allowance of
the SRU policy, letting us SRU this without paperwork for every single
change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to trusty-
backports as well, making sure we have the same version everywhere.

** Affects: lxcfs (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: lxcfs (Ubuntu Trusty)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Affects: lxcfs (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Affects: lxcfs (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Stéphane Graber (stgraber)
 Status: In Progress

** Also affects: lxcfs (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

** Changed in: lxcfs (Ubuntu Trusty)
   Status: New => In Progress

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

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

** Changed in: lxcfs (Ubuntu Trusty)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxcfs (Ubuntu Xenial)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: lxcfs (Ubuntu Yakkety)
 Assignee: (unassigned) => Stéphane Graber (stgraber)

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

Title:
  SRU of LXCFS 2.0.5 (upstream bugfix release)

Status in lxcfs package in Ubuntu:
  Fix Released
Status in lxcfs source package in Trusty:
  In Progress
Status in lxcfs source package in Xenial:
  In Progress
Status in lxcfs source package in Yakkety:
  In Progress

Bug description:
  LXCFS upstream released LXCFS 2.0.5 as a bugfix release with following 
changelog:
- Add Documentation key to systemd unit
- bindings: allow getattr on O_WRONLY files
- bindings: remove noop check
- fix Active/Inactive /proc/meminfo
- macro: add header for shared macros
- pam_cgfs: reimplement and add cgroupfs v2 support
- pam_cgfs: re-use cgroups that already belong to us
- pam_cgfs: handle cgroupfs v1 cpuset controller
- pam_cgfs: improve logging
- cgroups: handle non-existent isolcpus file

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Zesty and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1647012/+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 1647010] [NEW] SRU of LXC 2.0.6 (upstream bugfix release)

[Stéphane Graber]

Public bug reported:

LXC upstream released LXC 2.0.5 as a bugfix release with following changelog:
- Security fix for CVE-2016-8649
- utils: make detect_ramfs_rootfs() return bool
- tests: add test for detect_ramfs_rootfs()
- add Documentation entries to lxc and lxc@ units
- mark the python examples as having utf-8 encoding
- log: sanity check the returned value from snprintf()
- lxc-alpine: mount /dev/shm as tmpfs
- archlinux: Do DHCP on eth0
- archlinux: Fix resolving
- Drop leftover references to lxc_strerror()
- tests: fix image download for s390x
- tools: fix coding style in lxc_attach
- tools: make overlay valid backend
- tools: better error reporting for lxc-start
- alpine: Fix installing extra packages
- lxc-alpine: do not drop setfcap
- s390x: Fix seccomp handling of personalities
- tools: correct the argument typo in lxc_copy
- Use libtool for liblxc.so
- c/r: use --external instead of --veth-pair
- c/r: remember to increment netnr
- c/r: add checkpoint/restore support for macvlan interfaces
- ubuntu: Fix package upgrades requiring proc
- c/r: drop duplicate hunk from macvlan case
- c/r: use snprintf to compute device name
- Tweak libtool handling to work with Android
- tests: add lxc_error() and lxc_debug()
- container start: clone newcgroup immediately
- use python3_sitearch for including the python code
- fix rpm build, include all built files, but only once
- cgfs: fix invalid free()
- find OpenSUSE's build also as obs-build
- improve help text for --fancy and --fancy-format
- improve wording of the help page for lxc-ls
- cgfs: add print_cgfs_init_debuginfo()
- cgfs: skip empty entries under /proc/self/cgroup
- cgfs: explicitly check for NULL
- tools: use correct exit code for lxc-stop
- c/r: explicitly emit bind mounts as criu arguments
- log: bump LXC_LOG_BUFFER_SIZE to 4096
- conf: merge network namespace move & rename on shutdown
- c/r: save criu's stdout during dump too
- c/r: remove extra \ns from logs
- c/r: fix off-by-one error
- c/r: check state before doing a checkpoint/restore
- start: CLONE_NEWCGROUP after we have setup cgroups
- create symlink for /var/run
- utils: add lxc_append_string()
- cgroups: remove isolated cpus from cpuset.cpus
- Update Ubuntu release name: add zesty and remove wily
- templates: add squashfs support to lxc-ubuntu-cloud.in
- cgroups: skip v2 hierarchy entry
- also stop lxc-net in runlevels 0 and 6
- add lxc.egg-info to gitignore
- install bash completion where pkg-config tells us to
- conf: do not use %m format specifier
- debian: Don't depend on libui-dialog-perl
- cgroups: use %zu format specifier to print size_t
- lxc-checkpoint: automatically detect if --external or --veth-pair
- cgroups: prevent segfault in cgfsng
- utils: add lxc_preserve_ns()
- start: add netnsfd to lxc_handler
- conf: use lxc_preserve_ns()
- attach: use lxc_preserve_ns()
- lxc_user_nic: use lxc_preserve_ns()
- conf, start: improve log output
- conf: explicitly remove veth device from host
- conf, start: be smarter when deleting networks
- start, utils: improve preserve_ns()
- start, error: improve log + non-functional changes
- start, namespace: move ns_info to namespace.{c,h}
- attach, utils: bugfixes
- attach: use ns_info[LXC_NS_MAX] struct
- namespace: always attach to user namespace first
- cgroup: improve isolcpus handling
- cgroups: handle non-existent isolcpus file
- utils: add lxc_safe_uint()
- tests: add unit tests for lxc_safe_uint()
- utils: add lxc_safe_int()
- tests: add unit tests for lxc_safe_int()
- conf/ile: get ip prefix via lxc_safe_uint()
- confile: use lxc_safe_u/int in config_init_{u,g}id
- conf/ile: use lxc_safe_uint() in config_pts()
- conf/ile: use lxc_safe_u/int() in config_start()
- conf/ile: use lxc_safe_uint() in config_monitor()
- conf/ile: use lxc_safe_uint() in config_tty()
- conf/ile: use lxc_safe_uint() in config_kmsg()
- conf/ile: avoid atoi in config_lsm_aa_incomplete()
- conf/ile: use lxc_safe_uint() in config_autodev()
- conf/ile: avoid atoi() in config_ephemeral()
- utils: use lxc_safe_int()
- lxc_monitord: use lxc_safe_int() && use exit()
- start: use lxc_safe_int()
- conf: use lxc_safe_{u}int()
- tools/lxc_execute: use lxc_safe_uint()
- tools/lxc_stop: use lxc_safe_uint()
- utils: add lxc_safe_long()
- tests: add unit tests for lxc_safe_long()
- tools/lxc_stop: use lxc_safe_long()
- tools/lxc_top: use lxc_safe_int()
- tools/lxc_ls: use lxc_safe_uint()
- tools/lxc_autostart: use lxc_safe_{int,long}()
- tools/lxc_console: use lxc_safe_uint()
- tools: replace non-standard namespace identifiers
- Configure a static MAC address on 

[Group.of.nepali.translators] [Bug 1285850] Re: interuppting lxc-clone can destroy source container

[Launchpad Bug Tracker]

[Expired for lxc (Ubuntu Xenial) because there has been no activity for
60 days.]

** Changed in: lxc (Ubuntu Xenial)
   Status: Incomplete => Expired

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

Title:
  interuppting lxc-clone can destroy source container

Status in lxc package in Ubuntu:
  Expired
Status in lxc source package in Vivid:
  Won't Fix
Status in lxc source package in Wily:
  Won't Fix
Status in lxc source package in Xenial:
  Expired

Bug description:
  ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen
  containers on demand, but if i ctrl-c interuppt the operation, i've
  seen a few cases where it will destroy the source container (using
  snapshots and btrfs)

  $ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
  ctrl-c

  the source container's rootfs directory goes missing, and only a
  rootfs.hold file remains in place.

  btrfs subvolume list shows nothing for the missing container rootfs as
  well.

  lxc-version -> 1.0.0.alpha1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1285850/+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 1285850] Re: interuppting lxc-clone can destroy source container

[Launchpad Bug Tracker]

[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]

** Changed in: lxc (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  interuppting lxc-clone can destroy source container

Status in lxc package in Ubuntu:
  Expired
Status in lxc source package in Vivid:
  Won't Fix
Status in lxc source package in Wily:
  Won't Fix
Status in lxc source package in Xenial:
  Expired

Bug description:
  ubuntu 13.10, i'm currently scripting lxc-clone to create a dozen
  containers on demand, but if i ctrl-c interuppt the operation, i've
  seen a few cases where it will destroy the source container (using
  snapshots and btrfs)

  $ lxc-clone -s precise-subvolume target-1 -- -S ~/.ssh/id_dsa.pub
  ctrl-c

  the source container's rootfs directory goes missing, and only a
  rootfs.hold file remains in place.

  btrfs subvolume list shows nothing for the missing container rootfs as
  well.

  lxc-version -> 1.0.0.alpha1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1285850/+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 1632144] Re: SRU of LXC 2.0.5 (upstream bugfix release)

[Stéphane Graber]

** Changed in: lxc (Ubuntu Trusty)
   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/1632144

Title:
  SRU of LXC 2.0.5 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  LXC upstream released LXC 2.0.5 as a bugfix release with following changelog:
- Fix .gitignore after /tools/ split
- Add lxc-test-utils to .gitignore
- bdev: use correct overlay module name
- cleanup: tools: remove --name from lxc-top usage message
- cleanup: whitespaces in option alignment for lxc-execute
- Use full GPG fingerprint instead of long IDs.
- tools: move --rcfile to the common options list
- tools: set configfile after load_config
- doc: add --rcfile to common opts
- doc: Update Korean lxc-attach(1)
- doc: Add --rcfile to Korean common opts
- doc: Add --rcfile to Japanese common opts
- tools: use exit(EXIT_*) everywhere
- tools: unify exit() calls outside of main()
- utils: Add mips signalfd syscall numbers
- seccomp: Implement MIPS seccomp handling
- seccomp: Add mips and mips64 entries to lxc_config_parse_arch
- seccomp: fix strerror()
- confile: add more archs to lxc_config_parse_arch()
- seccomp: add support for s390x
- seccomp: remove double include and order includes
- seccomp: non functional changes
- templates: use fd 9 instead of 200
- templates: fedora requires openssl binary
- tools: use boolean for ret in lxc_device.c
- c/r: use /proc/self/tid/children instead of pidfile
- c/r: Fix pid_t on some arches
- templates: Add mips hostarch detection to debian
- cleanup: replace tabs wth spaces in usage strings
- remove extra 'ret'
- c/r: write status only after trying to parse the pid
- set FULL_PATH_NAMES=NO in doc/api/Doxyfile
- templates: rm halt.target -> sigpwr.target symlink
- templates: remove creation of bogus directory
- console: use correct log name
- configure: add --disable-werror
- tests: fix get_item tests
- templates: use correct cron version in alpine template
- c/r: zero a smaller than known migrate_opts struct
- lxczfs: small fixes
- c/r: free valid_opts if necessary
- make rsync deal with sparse files efficiently
- lxc-create -t debian fails on ppc64el arch
- c/r: fix typo in comment
- cgroup: add new functions for interacting with hierachies
- utils: add lxc_deslashify
- c/r: pass --cgroup-roots on checkpoint
- cgroup: get rid of weird hack in cgfsng_escape
- cgroup: drop cgroup_canonical_path
- c/r: check that cgroup_num_hierarchies > 0
- tools: do not add trailing spaces on lxc-ls -1
- conf: retrieve mtu from netdev->link
- conf: try to retrieve mtu from veth
- c/r: detatch from controlling tty on restore
- Fix null derefence if attach is called without access to any tty
- utils: fix lxc_string_split()
- tools: lxc_deslashify() handle special cases
- tests: add unit tests for lxc_deslashify()
- Fix for ALTLinux container creation in all branches
- utils: lxc_deslashify() free memory
- Fix spelling of CentOS in the templates
- Define LXC_DEVEL to detect development releases
- tools: lxc-checkconfig conditionalize devpts check

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Yakkety and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1632144/+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 1508284] Re: netperf: FTBFS with GCC 5: undefined reference to `demo_interval_tick'

[Logan Rosen]

** Also affects: netperf (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: netperf (Ubuntu Zesty)
   Importance: High
   Status: 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/1508284

Title:
  netperf: FTBFS with GCC 5: undefined reference to `demo_interval_tick'

Status in netperf package in Ubuntu:
  Triaged
Status in netperf source package in Wily:
  New
Status in netperf source package in Xenial:
  Triaged
Status in netperf source package in Yakkety:
  New
Status in netperf source package in Zesty:
  Triaged
Status in netperf package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/798789:

  Package: netperf
  Version: 2.6.0-2
  Severity: serious
  Tags: sid stretch
  Justification: fails to build from source (but built successfully in the past)

  Hi,

  netperf FTBFS in sid with GCC5:

  [...]
  gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c netlib.c
  netlib.c: In function 'bind_to_specific_processor':
  netlib.c:2292:9: warning: implicit declaration of function 
'sched_setaffinity' [-Wimplicit-function-declaration]
   if (sched_setaffinity(getpid(), len, _cpu_set)) {
   ^
  netlib.c: At top level:
  netlib.c:4080:20: warning: 'temp_demo_ptr' is static but used in inline 
function 'demo_interval_tick' which is not static
   demo_two_ptr = temp_demo_ptr;
  ^
  netlib.c:4080:5: warning: 'demo_two_ptr' is static but used in inline 
function 'demo_interval_tick' which is not static
   demo_two_ptr = temp_demo_ptr;
   ^
  netlib.c:4079:20: warning: 'demo_two_ptr' is static but used in inline 
function 'demo_interval_tick' which is not static
   demo_one_ptr = demo_two_ptr;
  ^
  [...]
  gcc  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall  
-Wl,-z,relro -o netperf netperf.o netlib.o netsh.o nettest_bsd.o nettest_dlpi.o 
nettest_unix.o nettest_xti.o nettest_sctp.o nettest_sdp.o nettest_omni.o 
net_uuid.o dscp.o netcpu_procstat.o netrt_rtnetlink.o netdrv_ethtool.o 
netslot_linux.o netsys_linux.o netsec_linux.o  -ldl -lm 
  nettest_omni.o: In function `send_omni_inner':
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4366: undefined reference to 
`demo_interval_tick'
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4359: undefined reference to 
`demo_interval_tick'
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4363: undefined reference to 
`demo_interval_tick'
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4356: undefined reference to 
`demo_interval_tick'
  collect2: error: ld returned 1 exit status
  [...]

  
  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netperf/+bug/1508284/+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 1508284] Re: netperf: FTBFS with GCC 5: undefined reference to `demo_interval_tick'

[Bug Watch Updater]

** Changed in: netperf (Debian)
   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/1508284

Title:
  netperf: FTBFS with GCC 5: undefined reference to `demo_interval_tick'

Status in netperf package in Ubuntu:
  Triaged
Status in netperf source package in Wily:
  New
Status in netperf source package in Xenial:
  Triaged
Status in netperf package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/798789:

  Package: netperf
  Version: 2.6.0-2
  Severity: serious
  Tags: sid stretch
  Justification: fails to build from source (but built successfully in the past)

  Hi,

  netperf FTBFS in sid with GCC5:

  [...]
  gcc -DHAVE_CONFIG_H -I. -I..   -D_FORTIFY_SOURCE=2  -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c netlib.c
  netlib.c: In function 'bind_to_specific_processor':
  netlib.c:2292:9: warning: implicit declaration of function 
'sched_setaffinity' [-Wimplicit-function-declaration]
   if (sched_setaffinity(getpid(), len, _cpu_set)) {
   ^
  netlib.c: At top level:
  netlib.c:4080:20: warning: 'temp_demo_ptr' is static but used in inline 
function 'demo_interval_tick' which is not static
   demo_two_ptr = temp_demo_ptr;
  ^
  netlib.c:4080:5: warning: 'demo_two_ptr' is static but used in inline 
function 'demo_interval_tick' which is not static
   demo_two_ptr = temp_demo_ptr;
   ^
  netlib.c:4079:20: warning: 'demo_two_ptr' is static but used in inline 
function 'demo_interval_tick' which is not static
   demo_one_ptr = demo_two_ptr;
  ^
  [...]
  gcc  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall  
-Wl,-z,relro -o netperf netperf.o netlib.o netsh.o nettest_bsd.o nettest_dlpi.o 
nettest_unix.o nettest_xti.o nettest_sctp.o nettest_sdp.o nettest_omni.o 
net_uuid.o dscp.o netcpu_procstat.o netrt_rtnetlink.o netdrv_ethtool.o 
netslot_linux.o netsys_linux.o netsec_linux.o  -ldl -lm 
  nettest_omni.o: In function `send_omni_inner':
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4366: undefined reference to 
`demo_interval_tick'
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4359: undefined reference to 
`demo_interval_tick'
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4363: undefined reference to 
`demo_interval_tick'
  /tmp/buildd/netperf-2.6.0/src/nettest_omni.c:4356: undefined reference to 
`demo_interval_tick'
  collect2: error: ld returned 1 exit status
  [...]

  
  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netperf/+bug/1508284/+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 1646993] Re: [SRU] New stable micro release 2.23

[Launchpad Bug Tracker]

This bug was fixed in the package snapcraft - 2.23+17.04

---
snapcraft (2.23+17.04) zesty; urgency=medium

  [ Sergio Schvezov ]
  * indicators: work with Content-Encoding set (#896)
  * store: download without login (#903)
  * readme: rocket instead of irc (#907)
  * indicators: support TERM=dumb (#906)
  * Update HACKING.md (#910)
  * help: update stage-packages and build-packages (#913)
  * meta: icon is now dedeprecated (#914)
  * cache: cleanup logic to pass project name (#915)
  * sources: missing command instead of package (#916)
  * docs: update GUI related integrations (#919)
  * pluginhandler: source management moved to the core (#923)
  * store: return specific error when already owned (#942)
  * nodejs plugin: install during pull to support npm run (#936)
  * New upstream release 2.22.1 (LP: #1646993)

  [ Parameswaran Sivatharman ]
  * store: login with option to agree to terms of service and human friendly 
errors (#866)

  [ Bayard Randel ]
  * cache: snap revision caching on 'push'. (#889)
  * deltas: migrate from xdelta to xdelta3. (#934)

  [ Leo Arias ]
  * tools: new script to retry autopktests (#893)
  * tests: remove the outdated all snaps image set up for snaps tests (#911)
  * plugin: add a gradle demo and test (#912)
  * tests: unset the proxies for gradle unit testing (#922)
  * tests: use the connectivity check page to test the downloader snap (#925)
  * tests: add a script to build external snaps (#927)
  * tests: replace coveralls with codecov (#939)
  * tests: replace subTests with TestScenarios (#943)

  [ Marco Trevisan ]
  * repo: apt-mark new build-packages as automatically installed (#891)
  * sources: add ftp support (#900)
  * parser: support remote dependencies (#930)
  * sources: add current dir to ignore list if we're iterating on parent (#926)

  [ Kelvin Li ]
  * cache: enable prune for snap cache. (#905)
  * deltas: initial implementation (#918)

  [ Celso Providelo ]
  * cli: basic 'enable-ci' implementation. (#901)
  * cli: implement `enable-ci travis --refresh` command (#932)

  [ John Lenton ]
  * cli: _filedir takes an extension, not a glob (#933)

  [ Larry Price ]
  * cmake plugin: utilize MakePlugin build logic within CMakePlugin (#935)

  [ Kyle Fazzari ]
  * pluginhandler: incorporate all part properties into state tracking. (#937)

 -- Sergio Schvezov   Fri, 02 Dec 2016
23:44:19 +

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

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

Title:
  [SRU] New stable micro release 2.23

Status in snapcraft package in Ubuntu:
  Fix Released
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  New
Status in snapcraft source package in Zesty:
  Fix Released

Bug description:
  This is an SRU bug to release 2.23 of snapcraft which follows the
  guidelines defined in the wiki over at
  https://wiki.ubuntu.com/SnapcraftUpdates

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.23 and
  https://launchpad.net/snapcraft/+milestone/2.23

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1646993/+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 1646993] [NEW] [SRU] New stable micro release 2.23

[Sergio Schvezov]

Public bug reported:

This is an SRU bug to release 2.23 of snapcraft which follows the
guidelines defined in the wiki over at
https://wiki.ubuntu.com/SnapcraftUpdates

The list of bugs and features in this release are defined at
https://launchpad.net/snapcraft/+milestone/2.23 and
https://launchpad.net/snapcraft/+milestone/2.23

** Affects: snapcraft (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: snapcraft (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: snapcraft (Ubuntu Yakkety)
 Importance: Undecided
 Status: New

** Affects: snapcraft (Ubuntu Zesty)
 Importance: Undecided
 Status: New

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

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

** Also affects: snapcraft (Ubuntu Yakkety)
   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/1646993

Title:
  [SRU] New stable micro release 2.23

Status in snapcraft package in Ubuntu:
  New
Status in snapcraft source package in Xenial:
  New
Status in snapcraft source package in Yakkety:
  New
Status in snapcraft source package in Zesty:
  New

Bug description:
  This is an SRU bug to release 2.23 of snapcraft which follows the
  guidelines defined in the wiki over at
  https://wiki.ubuntu.com/SnapcraftUpdates

  The list of bugs and features in this release are defined at
  https://launchpad.net/snapcraft/+milestone/2.23 and
  https://launchpad.net/snapcraft/+milestone/2.23

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1646993/+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 1637215] Re: [SRU] 2.17.1

[Mathew Hodson]

** No longer affects: snapd (Ubuntu Vivid)

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

Title:
  [SRU] 2.17.1

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Fix Committed
Status in snapd source package in Yakkety:
  Fix Committed

Bug description:
  This is a new version of snapd.

  The changelog for 2.17 is available here
  https://github.com/snapcore/snapd/blob/2.17/debian/changelog, the raw
  git changelog is available here:
  https://github.com/snapcore/snapd/commits/2.17 (note that the debian
  changelog is auto-generated from the merges of the git commits so
  there is usually no need to look at the raw git commits).

  The snappy team released a new 2.17 micro release that we want SRU
  into xenial. The new process described in
  https://wiki.ubuntu.com/SnapdUpdates was used and we have done
  integration-tests on the snappy images, autopkgtests on classic and
  unit tests.

  The following automatic tests are run:
  - travis unit tests https://travis-ci.org/snapcore/snapd/branches (check for 
2.17 here)
  - travis/spread based integration/system tests: 
https://travis-ci.org/snapcore/snapd/branches (check for 2.17 here under 
"spread")

  The following additional tests were performed:
  """
  $ adt-run -s -U snapd_2.17.dsc --- qemu ~/VM/adt-xenial-amd64-cloud.img
  [lots of output, wait 45min]
  2016/09/28 11:51:57 Restoring autopkgtest:ubuntu-16.04-64:tests/upgrade/...
  2016/09/28 11:52:00 Discarding autopkgtest:ubuntu-16.04-64...
  2016/09/28 11:52:01 Successful tasks: 88
  2016/09/28 11:52:01 Aborted tasks: 0
  adt-run [11:52:01]: test integrationtests: ---]
  adt-run [11:52:02]: test integrationtests: - - - - - - - - - - results - - - 
- - - - - - -
  integrationtests PASS
  adt-run [11:52:03]:  summary
  integrationtests PASS

  $ adt-run -s -U snapd_2.17.dsc --- qemu ~/VM/adt-yakkety-amd64-cloud.img
  [lots of output, wait 45min]
  2016/09/28 12:09:09 Restoring autopkgtest:ubuntu-16.04-64:tests/upgrade/...
  2016/09/28 12:09:12 Discarding autopkgtest:ubuntu-16.04-64...
  2016/09/28 12:09:12 Successful tasks: 88
  2016/09/28 12:09:12 Aborted tasks: 0
  adt-run [12:09:13]: test integrationtests: ---]
  adt-run [12:09:14]: test integrationtests: - - - - - - - - - - results - - - 
- - - - - - -
  integrationtests PASS
  adt-run [12:09:14]:  summary
  integrationtests PASS

  """
  Almost all of our spread integration tests are now run as part of the 
autopkgtest run.

  After installing the new snapd it was ensured that apt is unaffected by doing:
  """
  - sudo apt install -y hello && sudo apt remove -y hello
  """

  After installing the new snapd gnome-software was used:
  """
  - install "http" (snap) and remove it again
  """
  All worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1637215/+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 1645906] Re: new dist-upgrader tarballs necessary so they are signed with 4k key

[Mathew Hodson]

** No longer affects: ubuntu-release-upgrader (Ubuntu Precise)

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

Title:
  new dist-upgrader tarballs necessary so they are signed with 4k key

Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  Invalid
Status in update-manager source package in Precise:
  Fix Committed
Status in ubuntu-release-upgrader source package in Trusty:
  Fix Committed
Status in update-manager source package in Trusty:
  Invalid
Status in ubuntu-release-upgrader source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Invalid
Status in ubuntu-release-upgrader source package in Yakkety:
  Fix Committed
Status in update-manager source package in Yakkety:
  Invalid

Bug description:
  With the ubuntu-archive-publishing change in
  https://code.launchpad.net/~xnox/ubuntu-archive-publishing/migrate-
  dist-upgrade-to-4k/+merge/311181 the signing process for the dist-
  upgrader tarball has been changed.  This change should be tested now,
  rather than doing an ubuntu-release-upgrader change months from now
  and wondering why things aren't working (if they are broken).

  Due to the way the gpg signature is generated we can't just remove it
  and have it regenerated as the timestamp for the signature will not
  change, so the change will not propogate to the mirrors.  Hence the
  need for a mostly no change (mirrors and demotions may change) upload
  of ubuntu-release-upgrader.

  Test Case
  -
  1) run do-release-upgrade -p --frontend DistUpgradeViewText
  2) ensure the tarball for the next release e.g. xenial.tar.gz is downloaded 
and the signature verification passes

  Regression Potential
  
  It's possible the signing is wrong and the verification of the signature will 
fail thereby causing release upgrades to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1645906/+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 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

[Matthias Klose]

** Also affects: gcc-6 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gcc-6 (Ubuntu Xenial)

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

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  New
Status in gcc-5 package in Ubuntu:
  New
Status in gcc-6 package in Ubuntu:
  New
Status in binutils source package in Xenial:
  New
Status in gcc-5 source package in Xenial:
  New

Bug description:
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed". 

  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1623418/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists

[Michael Terry]

** Description changed:

  when doing a backup for the first time, dejadup verifies your passphrase
  by having you enter it twice.
  
  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.
  
  with the periodic 'full' backups that happen from time to time, however,
  any password will be accepted.
  
  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what you
  typed and have no way to get your files (or do another incremental
  backup on top of it).
  
  i think this is what happened to me recently.
  
  clearly, the fix is to explicitly verify the passphrase is correct when
  doing a new full backup.  this may be a duplicity bug.
+ 
+ === Ubuntu deja-dup SRU information ===
+ 
+ [impact]
+ Users may unwittingly re-set their backup password and not be able to restore 
their data.
+ 
+ [test case]
+ - $ deja-dup-preferences # set up a dummy backup
+ - $ deja-dup --backup # complete first encrypted full backup
+ - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
+ - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
+ - $ deja-dup --backup # second backup, enter the wrong password
+ - $ deja-dup --restore # try to restore with original password
+ 
+ [regression potential]
+ Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

** Also affects: deja-dup (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/918489

Title:
  duplicity allows bad passphrase on full backup if archive cache exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Xenial:
  New

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+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 1596629] Re: Support snap configuration

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.18+17.04ubuntu3

---
snapd (2.18+17.04ubuntu3) zesty; urgency=medium

  * disable ppc64el autopkgtest for now, it never worked but for
some reason autopkgtest thinks it did at some point and asking
for correction of the DB was not successful so far

 -- Michael Vogt   Fri, 02 Dec 2016 16:27:34
+0100

** Changed in: snapd (Ubuntu)
   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/1596629

Title:
  Support snap configuration

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  Fix Committed
Status in snapd source package in Yakkety:
  Fix Committed

Bug description:
  Two commands will be supported: `snap set key=value` and `snap get
  key`. `snap set` will cause the `configure` hook to be run within the
  snap in question, which gives it an opportunity to respond to those
  changes (including vetoing them). `snap get` will obtain the config
  values directly from snapd (no hooks involved).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1596629/+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 1644625] Re: [SRU] 2.18

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.18+17.04ubuntu3

---
snapd (2.18+17.04ubuntu3) zesty; urgency=medium

  * disable ppc64el autopkgtest for now, it never worked but for
some reason autopkgtest thinks it did at some point and asking
for correction of the DB was not successful so far

 -- Michael Vogt   Fri, 02 Dec 2016 16:27:34
+0100

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

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

Title:
  [SRU] 2.18

Status in snapd package in Ubuntu:
  Fix Released
Status in snapd source package in Xenial:
  New
Status in snapd source package in Yakkety:
  New

Bug description:
  This is a new version of snapd.

  The changelog for 2.18 is available here
  https://github.com/snapcore/snapd/blob/2.18/debian/changelog, the raw
  git changelog is available here:
  https://github.com/snapcore/snapd/commits/2.18 (note that the debian
  changelog is auto-generated from the merges of the git commits so
  there is usually no need to look at the raw git commits).

  The snappy team released a new 2.18 micro release that we want SRU
  into xenial. The new process described in
  https://wiki.ubuntu.com/SnapdUpdates was used and we have done
  integration-tests on the snappy images, autopkgtests on classic and
  unit tests.

  The following automatic tests are run:
  - travis unit tests https://travis-ci.org/snapcore/snapd/branches (check for 
2.18 here)
  - travis/spread based integration/system tests: 
https://travis-ci.org/snapcore/snapd/branches (check for 2.18 here under 
"spread")

  The following additional tests were performed:
  """
  $ adt-run -s -U snapd_2.18.dsc --- qemu ~/VM/adt-xenial-amd64-cloud.img
  [lots of output, wait 45min]
  2016/11/24 21:42:53 Restoring project on autopkgtest:ubuntu-16.04-64...
  2016/11/24 21:42:53 Discarding autopkgtest:ubuntu-16.04-64...
  2016/11/24 21:42:53 Successful tasks: 101
  2016/11/24 21:42:53 Aborted tasks: 0
  adt-run [21:42:54]: test integrationtests: ---]
  adt-run [21:42:55]: test integrationtests:  - - - - - - - - - - results - - - 
- - - - - - -
  integrationtests PASS
  adt-run [21:42:55]:  summary
  integrationtests PASS

  $ adt-run -s -U snapd_2.18.dsc --- qemu ~/VM/adt-yakkety-amd64-cloud.img
  [lots of output, wait 45min]
  2016/11/24 22:15:06 Restoring 
autopkgtest:ubuntu-16.04-64:tests/main/snap-run-symlink-error...
  2016/11/24 22:15:09 Restoring autopkgtest:ubuntu-16.04-64:tests/main/...
  2016/11/24 22:15:13 Restoring project on autopkgtest:ubuntu-16.04-64...
  2016/11/24 22:15:13 Discarding autopkgtest:ubuntu-16.04-64...
  2016/11/24 22:15:13 Successful tasks: 101
  2016/11/24 22:15:13 Aborted tasks: 0
  adt-run [22:15:14]: test integrationtests: ---]
  adt-run [22:15:15]: test integrationtests:  - - - - - - - - - - results - - - 
- - - - - - -
  integrationtests PASS
  adt-run [22:15:16]:  summary
  integrationtests PASS

  
  """
  Almost all of our spread integration tests are now run as part of the 
autopkgtest run.

  After installing the new snapd it was ensured that apt is unaffected by doing:
  """
  - sudo apt install -y hello && sudo apt remove -y hello
  """

  After installing the new snapd gnome-software was used:
  """
  - install "http" (snap) and remove it again
  """
  All worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1644625/+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 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%

[Mario Limonciello]

This is actually a kernel bug where the PWM isn't saved.  It affects the
specific display type in this machine.  It's been fixed upstream
already, and was brought into Ubuntu 16.04 (See SRU
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625932).

The Precision 5510 however ships with Ubuntu 14.04 + vivid HWE stack.
The vivid HWE stack does not contain the fix, which is why this issue is
happening.

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

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

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

** Also affects: xorg (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: xorg (Ubuntu Vivid)
   Status: Incomplete => Invalid

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

Title:
  Backlight sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New
Status in xorg source package in Vivid:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in xorg source package in Xenial:
  Invalid

Bug description:
  Back-light sometimes fails to resume from suspend & screen brightness
  sometimes will not dim below 100%

  Issue is interment in occurrence. Will be reproducible with the
  command "sudo pm-suspend" & or close/reopen laptop lid for a period of
  time days or hours, then go a period of time, days or hours without
  being able to trigger it again.

  This is irrespective of running "apt-get update && apt-get upgrade -y"
  and has continued to be intermittent on last 3 versions of 3.19
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-74-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec  1 10:06:43 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150721-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06e5]
  InstallationDate: Installed on 2016-11-22 (8 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150721-23:28
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed 
root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.14
  dmi.board.name: 0W7V82
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: 

[Group.of.nepali.translators] [Bug 1518430] Re: liberty: ~busy loop on epoll_wait being called with zero timeout

[Corey Bryant]

This has been uploaded to ubuntu zesty, yakkety, xenial and is awaiting
sru team review for yakkety and xenial.  This has also been uploaded to
kilo-staging and liberty-staging for the ubuntu cloud archive.  These
should all be available in -proposed soon for testing.

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

** Changed in: cloud-archive/kilo
   Status: New => Fix Committed

** Changed in: cloud-archive/liberty
   Status: New => Fix Committed

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

Title:
  liberty: ~busy loop on epoll_wait being called with zero timeout

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive kilo series:
  Fix Committed
Status in Ubuntu Cloud Archive liberty series:
  Fix Committed
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Committed
Status in OpenStack Compute (nova):
  Invalid
Status in oslo.messaging:
  Fix Released
Status in nova package in Ubuntu:
  Invalid
Status in python-oslo.messaging package in Ubuntu:
  Fix Released
Status in python-oslo.messaging source package in Xenial:
  New
Status in python-oslo.messaging source package in Yakkety:
  New
Status in python-oslo.messaging source package in Zesty:
  Fix Released

Bug description:
  Context: openstack juju/maas deploy using 1510 charms release
  on trusty, with:
    openstack-origin: "cloud:trusty-liberty"
    source: "cloud:trusty-updates/liberty

  * Several openstack nova- and neutron- services, at least:
  nova-compute, neutron-server, nova-conductor,
  neutron-openvswitch-agent,neutron-vpn-agent
  show almost busy looping on epoll_wait() calls, with zero timeout set
  most frequently.
  - nova-compute (chose it b/cos single proc'd) strace and ltrace captures:
    http://paste.ubuntu.com/13371248/ (ltrace, strace)

  As comparison, this is how it looks on a kilo deploy:
  - http://paste.ubuntu.com/13371635/

  * 'top' sample from a nova-cloud-controller unit from
     this completely idle stack:
    http://paste.ubuntu.com/13371809/

  FYI *not* seeing this behavior on keystone, glance, cinder,
  ceilometer-api.

  As this issue is present on several components, it likely comes
  from common libraries (oslo concurrency?), fyi filed the bug to
  nova itself as a starting point for debugging.

  Note: The description in the following bug gives a good overview of
  the issue and points to a possible fix for oslo.messaging:
  https://bugs.launchpad.net/mos/+bug/1380220

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1518430/+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 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC

[Matthias Klose]

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

** Also affects: gcc-5 (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/1623418

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  New
Status in gcc-5 package in Ubuntu:
  New
Status in binutils source package in Xenial:
  New
Status in gcc-5 source package in Xenial:
  New

Bug description:
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed". 

  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1623418/+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 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Mathew Hodson]

** Also affects: zfs-linux (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839645
   Importance: Unknown
   Status: Unknown

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in zfs-linux package in Debian:
  Unknown

Bug description:
  [Impact]

  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  * dbufstat.py : Print out statistics for all cached dmu buffers

  should be renamed according to Policy 10.4 :
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

  [Test Case]

   * Install zfsutils-linux
   * List files

   $ dpkg -L zfsutils-linux | egrep "arc|dbufstat"
     /usr/sbin/arc_summary.py
     /usr/sbin/arcstat.py
     /usr/sbin/dbufstat.py

  [Regression Potential]

   * none expected, this is a trivial change that simply rename the
  scripts to remove the extension (.py) with a simple 'mv' before the
  dh_install invocation in order to get this expected result :

  $ dpkg -L zfsutils-linux | egrep -i "arc|dbuf"
    /usr/sbin/arc_summary
    /usr/sbin/arcstat
    /usr/sbin/dbufstat

  Yakkety include the renaming as shown above.

  Xenial will have a symlink to not break user experience until next release 
upgrade:
  
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1628279/comments/19

  So user will be able to use both for instance : arcstat.py or arcstat

  
  [Other Info]

   * Justification/argument for Xenial
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/13
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/14

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

   * Upstream (ZoL) is reluctant to change it at upstream code level.
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/comments/2

   * This has been flag by Adam Conrad
  https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1574342/comments/19

   * Debian policy
  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1628279/+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 1640645] Re: free space check doesn't take into account kernel upgrades

[Brian Murray]

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

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: ubuntu-release-upgrader (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  free space check doesn't take into account kernel upgrades

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  In Progress

Bug description:
  Could not install 'linux-image-4.4.0-45-generic'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.17
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Wed Nov  9 20:11:19 2016
  InstallationDate: Installed on 2015-05-24 (535 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-11-10 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: Error creating textual authentication agent: Error opening current 
controlling terminal for the process (`/dev/tty'): No such device or address
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1640645/+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 1518430] Re: liberty: ~busy loop on epoll_wait being called with zero timeout

[Corey Bryant]

I can't see where this bug exists on base Trusty/Icehouse so I've
dropped those targets for Ubuntu.

** No longer affects: cloud-archive/icehouse

** No longer affects: python-oslo.messaging (Ubuntu Trusty)

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

Title:
  liberty: ~busy loop on epoll_wait being called with zero timeout

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive liberty series:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Committed
Status in OpenStack Compute (nova):
  Invalid
Status in oslo.messaging:
  Fix Released
Status in nova package in Ubuntu:
  Invalid
Status in python-oslo.messaging package in Ubuntu:
  Fix Released
Status in python-oslo.messaging source package in Xenial:
  New
Status in python-oslo.messaging source package in Yakkety:
  New
Status in python-oslo.messaging source package in Zesty:
  Fix Released

Bug description:
  Context: openstack juju/maas deploy using 1510 charms release
  on trusty, with:
    openstack-origin: "cloud:trusty-liberty"
    source: "cloud:trusty-updates/liberty

  * Several openstack nova- and neutron- services, at least:
  nova-compute, neutron-server, nova-conductor,
  neutron-openvswitch-agent,neutron-vpn-agent
  show almost busy looping on epoll_wait() calls, with zero timeout set
  most frequently.
  - nova-compute (chose it b/cos single proc'd) strace and ltrace captures:
    http://paste.ubuntu.com/13371248/ (ltrace, strace)

  As comparison, this is how it looks on a kilo deploy:
  - http://paste.ubuntu.com/13371635/

  * 'top' sample from a nova-cloud-controller unit from
     this completely idle stack:
    http://paste.ubuntu.com/13371809/

  FYI *not* seeing this behavior on keystone, glance, cinder,
  ceilometer-api.

  As this issue is present on several components, it likely comes
  from common libraries (oslo concurrency?), fyi filed the bug to
  nova itself as a starting point for debugging.

  Note: The description in the following bug gives a good overview of
  the issue and points to a possible fix for oslo.messaging:
  https://bugs.launchpad.net/mos/+bug/1380220

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1518430/+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 1518430] Re: liberty: ~busy loop on epoll_wait being called with zero timeout

[Corey Bryant]

** Changed in: python-oslo.messaging (Ubuntu Zesty)
   Status: New => Fix Released

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

Title:
  liberty: ~busy loop on epoll_wait being called with zero timeout

Status in Ubuntu Cloud Archive:
  Fix Committed
Status in Ubuntu Cloud Archive icehouse series:
  New
Status in Ubuntu Cloud Archive liberty series:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Fix Committed
Status in Ubuntu Cloud Archive newton series:
  Fix Committed
Status in OpenStack Compute (nova):
  Invalid
Status in oslo.messaging:
  Fix Released
Status in nova package in Ubuntu:
  Invalid
Status in python-oslo.messaging package in Ubuntu:
  Fix Released
Status in python-oslo.messaging source package in Trusty:
  New
Status in python-oslo.messaging source package in Xenial:
  New
Status in python-oslo.messaging source package in Yakkety:
  New
Status in python-oslo.messaging source package in Zesty:
  Fix Released

Bug description:
  Context: openstack juju/maas deploy using 1510 charms release
  on trusty, with:
    openstack-origin: "cloud:trusty-liberty"
    source: "cloud:trusty-updates/liberty

  * Several openstack nova- and neutron- services, at least:
  nova-compute, neutron-server, nova-conductor,
  neutron-openvswitch-agent,neutron-vpn-agent
  show almost busy looping on epoll_wait() calls, with zero timeout set
  most frequently.
  - nova-compute (chose it b/cos single proc'd) strace and ltrace captures:
    http://paste.ubuntu.com/13371248/ (ltrace, strace)

  As comparison, this is how it looks on a kilo deploy:
  - http://paste.ubuntu.com/13371635/

  * 'top' sample from a nova-cloud-controller unit from
     this completely idle stack:
    http://paste.ubuntu.com/13371809/

  FYI *not* seeing this behavior on keystone, glance, cinder,
  ceilometer-api.

  As this issue is present on several components, it likely comes
  from common libraries (oslo concurrency?), fyi filed the bug to
  nova itself as a starting point for debugging.

  Note: The description in the following bug gives a good overview of
  the issue and points to a possible fix for oslo.messaging:
  https://bugs.launchpad.net/mos/+bug/1380220

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1518430/+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 1643990] Re: cloud-init-local.service messages not written to /var/log/cloud-init.log in systemd

[Scott Moser]

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   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/1643990

Title:
  cloud-init-local.service messages not written to /var/log/cloud-
  init.log in systemd

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  In Progress

Bug description:
  output of cloud-init-local.service can get lost in systemd.
  The result is that there is no output in /var/log/cloud-init.log from 
cloud-init-local.service.

  There is some information in 
https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+merge/301729
  about how this occurrs and how it used to work.
  copying part of that here:

  
  Cloud-init's logging basically employed a "try syslog and fallback to direct 
log to file".
  The proposed "just log to a file" is definitely dramatically simpler and 
advantageous in some cases.

  The way the "try syslog and fallback" works (or worked) on Ubuntu up
  until systemd was:

  a.) cloud-init init --local
  1. read logging config,
  2. attempt to log to syslog ([ *log_base, *log_syslog ])
  3. that fail, so it log to file directly

  b.) cloud-init init
 1.) rsyslog would have /dev/log up functional at this point
 2.) cloud-init logging config read and ends up logging to syslog

  Systemd changed some things in teh way /dev/log was handled, and the
  above no longer worked well.

  Additionally, cloud-init installs a file
  /etc/rsyslog.d/21-cloudinit.conf which tells rsyslog to redirect
  messages generated by cloud-init to /var/log/cloud-init.log

  The value of doing this in this way was that we use syslog, so if the
  user had configured the system to log remotely, cloud-init's logs
  would go to that remote system as they desired.

  If we directly log to a file, then cloud-init's log messages will not
  without further configuration go to syslog.

  One other thing to be aware of is that cloud-init can itself configure
  rsyslog through cloudinit/config/cc_rsyslog.py . So, the user could
  provide in user-data some rsyslog configuration, and then the system's
  syslog (including cloud-init messages) would start goign to that
  remote server as soon as they realistically could.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643990/+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 1646248] Re: Injecting DHCP configuration from Hyper-V host fails

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

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

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

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

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

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

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

Title:
  Injecting DHCP configuration from Hyper-V host fails

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

Bug description:
  When injecting a DHCP configuration from a Hyper-V host using WMI, the IP 
address does not change, and the syslog contains the following line:
  Failed to execute cmd 'hv_set_ifconfig /var/lib/hyperv/ifcfg-eth0'; error: 2 
No such file or directory
  the ifcfg-eth0 exists with a modification time identical to the log line's.
  Switching the scheduler to noop did not resolve this issue.
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Dec  1 10:06 seq
   crw-rw+ 1 root audio 116, 33 Dec  1 10:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a3b32a0b-59a9-4b50-8d31-a06477933916
  InstallationDate: Installed on 2016-11-22 (8 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=31af956a-1342-4e8d-9c74-af0308e00111 ro
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Dec  1 10:06 seq
   crw-rw+ 1 root audio 116, 33 Dec  1 10:06 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a3b32a0b-59a9-4b50-8d31-a06477933916
  InstallationDate: Installed on 2016-11-22 (8 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   

[Group.of.nepali.translators] [Bug 1643524] Re: linux-hwe-edge: 4.8.0-28.30~16.04.1 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

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

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

** Description changed:

  This bug is for tracking the 4.8.0-28.30~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 --
  kernel-stable-master-bug: 1641083
+ kernel-stable-phase-changed:Friday, 02. December 2016 15:31 UTC
+ kernel-stable-phase:Released

** Description changed:

  This bug is for tracking the 4.8.0-28.30~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 --
  kernel-stable-master-bug: 1641083
- kernel-stable-phase-changed:Friday, 02. December 2016 15:31 UTC
- kernel-stable-phase:Released
+ phase: 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/1643524

Title:
  linux-hwe-edge: 4.8.0-28.30~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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:
  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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
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:
  Invalid
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:
  Fix Released

Bug description:
  This bug is for tracking the 4.8.0-28.30~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 --
  kernel-stable-master-bug: 1641083
  phase: Released

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux-hwe-edge - 4.8.0-28.30~16.04.1

---
linux-hwe-edge (4.8.0-28.30~16.04.1) xenial; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1643524

  * lxc-attach to malicious container allows access to host (LP: #1639345)
- Revert "UBUNTU: SAUCE: (noup) ptrace: being capable wrt a process requires
  mapped uids/gids"
- (upstream) mm: Add a user_ns owner to mm_struct and fix ptrace permission
  checks

  * [Feature] AVX-512 new instruction sets (avx512_4vnniw, avx512_4fmaps)
(LP: #1637526)
- x86/cpufeature: Add AVX512_4VNNIW and AVX512_4FMAPS features

  * zfs: importing zpool with vdev on zvol hangs kernel (LP: #1636517)
- SAUCE: (noup) Update zfs to 0.6.5.8-0ubuntu4.1

  * Move some device drivers build from kernel built-in to modules
(LP: #1637303)
- [Config] CONFIG_TIGON3=m for all arches
- [Config] CONFIG_VIRTIO_BLK=m, CONFIG_VIRTIO_NET=m

  * I2C touchpad does not work on AMD platform (LP: #1612006)
- pinctrl/amd: Configure GPIO register using BIOS settings

  * guest experiencing Transmit Timeouts on CX4 (LP: #1636330)
- powerpc/64: Re-fix race condition between going idle and entering guest
- powerpc/64: Fix race condition in setting lock bit in idle/wakeup code

  * QEMU throws failure msg while booting guest with SRIOV VF (LP: #1630554)
- KVM: PPC: Always select KVM_VFIO, plus Makefile cleanup

  * [Feature] KBL - New device ID for Kabypoint(KbP) (LP: #1591618)
- SAUCE: mfd: lpss: Fix Intel Kaby Lake PCH-H properties

  * hio: SSD data corruption under stress test (LP: #1638700)
- SAUCE: hio: set bi_error field to signal an I/O error on a BIO
- SAUCE: hio: splitting bio in the entry of .make_request_fn

  * cleanup primary tree for linux-hwe layering issues (LP: #1637473)
- [Config] switch Vcs-Git: to yakkety repository
- [Packaging] handle both linux-lts* and linux-hwe* as backports
- [Config] linux-tools-common and linux-cloud-tools-common are one per 
series
- [Config] linux-source-* is in the primary linux namespace
- [Config] linux-tools -- always suggest the base package

  * SRU: sync zfsutils-linux and spl-linux changes to linux (LP: #1635656)
- SAUCE: (noup) Update spl to 0.6.5.8-2, zfs to 0.6.5.8-0ubuntu4 (LP:
  #1635656)

  * [Feature] SKX: perf uncore PMU support (LP: #1591810)
- perf/x86/intel/uncore: Add Skylake server uncore support
- perf/x86/intel/uncore: Remove hard-coded implementation for Node ID 
mapping
  location
- perf/x86/intel/uncore: Handle non-standard counter offset

  * [Feature] Purley: Memory Protection Keys (LP: #1591804)
- x86/pkeys: Add fault handling for PF_PK page fault bit
- mm: Implement new pkey_mprotect() system call
- x86/pkeys: Make mprotect_key() mask off additional vm_flags
- x86/pkeys: Allocation/free syscalls
- x86: Wire up protection keys system calls
- generic syscalls: Wire up memory protection keys syscalls
- pkeys: Add details of system call use to Documentation/
- x86/pkeys: Default to a restrictive init PKRU
- x86/pkeys: Allow configuration of init_pkru
- x86/pkeys: Add self-tests

  * kernel invalid opcode in intel_powerclamp (LP: #1630774)
- SAUCE: (no-up) thermal/powerclamp: correct cpu support check

  * please include mlx5_core modules in linux-image-generic package
(LP: #1635223)
- [Config] Include mlx5 in main package

  * [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default (LP: #1636733)
- [Config] CONFIG_VFIO_PCI=y for ppc64el

  * Yakkety update to v4.8.6 stable release (LP: #1638748)
- drm/vc4: Fix races when the CS reads from render targets.
- drm/prime: Pass the right module owner through to dma_buf_export()
- drm/i915/backlight: setup and cache pwm alternate increment value
- drm/i915/backlight: setup backlight pwm alternate increment on backlight
  enable
- drm/amdgpu: fix IB alignment for UVD
- drm/amdgpu/dce10: disable hpd on local panels
- drm/amdgpu/dce8: disable hpd on local panels
- drm/amdgpu/dce11: disable hpd on local panels
- drm/amdgpu/dce11: add missing drm_mode_config_cleanup call
- drm/amdgpu: initialize the context reset_counter in amdgpu_ctx_init
- drm/amdgpu: change vblank_time's calculation method to reduce 
computational
  error.
- drm/radeon: narrow asic_init for virtualization
- drm/radeon/si/dpm: fix phase shedding setup
- drm/radeon: change vblank_time's calculation method to reduce 
computational
  error.
- drm/vmwgfx: Limit the user-space command buffer size
- drm/fsl-dcu: fix endian issue when using clk_register_divider
- drm/amd/powerplay: fix mclk not switching back after multi-head was 
disabled
- HID: add quirk for Akai MIDImix.
- drm/i915/skl: Update plane watermarks atomically during plane updates
- drm/i915: Move CRTC updating in atomic_commit into it's own hook
- 

[Group.of.nepali.translators] [Bug 1642679] Re: The OpenStack network_config.json implementation fails on Hyper-V compute nodes

[Scott Moser]

** Also affects: cloud-init (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Wily)
   Importance: Undecided
   Status: New

** No longer affects: cloud-init (Ubuntu Vivid)

** No longer affects: cloud-init (Ubuntu Wily)

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

Title:
  The OpenStack network_config.json implementation fails on Hyper-V
  compute nodes

Status in cloud-init:
  Confirmed
Status in OpenStack Compute (nova):
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  We have discovered an issue when booting Xenial instances on OpenStack
  environments (Liberty or newer) and Hyper-V compute nodes using config
  drive as metadata source.

  When applying the network_config.json, cloud-init fails with this error:
  http://paste.openstack.org/show/RvHZJqn48JBb0TO9QznL/

  The fix would be to add 'hyperv' as a link type here:
  /usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py, line 
587

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1642679/+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 1644615] Re: linux-snapdragon: 4.4.0-1038.42 -proposed tracker

[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-1038.42
/snapdragon-xenial-proposed.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/1644615

Title:
  linux-snapdragon: 4.4.0-1038.42 -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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1644611
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1644615/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 232-7

---
systemd (232-7) unstable; urgency=medium

  [ Michael Biebl ]
  * Mark liblz4-tool build dependency as 
  * udev: Try mount -n -o move first
initramfs-tools is not actually using util-linux mount (yet), so making
mount -n --move the first alternative would trigger an error message if
users have built their initramfs without busybox support.

  [ Alexander Kurtz ]
  * debian/extra/kernel-install.d/85-initrd.install: Remove an unnecessary
variable. (Closes: #845977)

  [ Martin Pitt ]
  * Drop systemd-networkd's "After=dbus.service" ordering, so that it can
start during early boot (for cloud-init.service). It will auto-connect to
D-Bus once it becomes available later, and transient (from DHCP) hostname
and timezone setting do not currently work anyway. (LP: #1636912)
  * Run hwdb/parse_hwdb.py during package build.
  * Package libnss-systemd
  * Make libnss-* depend on the same systemd package version.

 -- Martin Pitt   Wed, 30 Nov 2016 14:38:36 +0100

** Changed in: systemd (Ubuntu)
   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/1636912

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  Fix Committed

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11

[Group.of.nepali.translators] [Bug 1646150] Re: linux: 4.4.0-52.73 -proposed tracker

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-51.72-generic/s2lp3__4.4.0-51.72__2016-12-02_09-04-00/results-index.html

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

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

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

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

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the 4.4.0-52.73 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
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 02. December 2016 09:03 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.4.0-52.73 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
  derivative-trackers-created: true
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 02. December 2016 09:03 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-52.73 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
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.4.0-52.73 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
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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