[Group.of.nepali.translators] [Bug 1691911] [NEW] SRU of LXC 2.0.8
Public bug reported: LXC upstream released LXC 2.0.8 as a bugfix release with following changelog: - Security fix for CVE-2017-5985 (previously fixed in Ubuntu) - All templates have been updated to not set default passwords anymore, instead requiring lxc-attach be used to configure users. This may affect some automated environments that were relying on our default (very much insecure) users. - Make lxc-start-ephemeral Python 3.2-compatible - Fix typo - Allow build without sys/capability.h - lxc-opensuse: fix default value for release code - util: always malloc for setproctitle - util: update setproctitle comments - confile: clear lxc.network..ipv{4,6} when empty - lxc_setup_tios(): Ignore SIGTTOU and SIGTTIN signals - Make lxc-net return non-zero on failure - seccomp: allow x32 guests on amd64 hosts. - Add HAVE_LIBCAP - c/r: only supply --ext-mount-map for bind mounts - Added 'mkdir -p' functionality in create_or_remove_cgroup - Use LXC_ROOTFS_MOUNT in clonehostname hook - squeeze is not a supported release anymore, drop the key - start: dumb down SIGCHLD from WARN() to NOTICE() - log: fix lxc_unix_epoch_to_utc() - cgfsng: make trim() safer - seccomp: set SCMP_FLTATR_ATL_TSKIP if available - lxc-user-nic: re-order #includes - lxc-user-nic: improve + bugfix - lxc-user-nic: delete link on failure - conf: only try to delete veth when privileged - Fix lxc-containers to support multiple bridges - Fix mixed tab/spaces in previous patch - lxc-alpine: use dl-cdn.a.o as default mirror instead of random one - lxc-checkconfig: verify new[ug]idmap are setuid-root - [templates] archlinux: resolve conflicting files - [templates] archlinux: noneed default_timezone variable - python3: Deal with potential NULL char* - lxc-download.in / allow setting keyserver from env - lxc-download.in / Document keyserver change in help - Change variable check to match existing style - tree-wide: include directly - conf/ile: make sure buffer is large enough - tree-wide: include directly - tests: Support running on IPv6 networks - tests: Kill containers (don't wait for shutdown) - Fix opening wrong file in suggest_default_idmap - do not set the root password in the debian template - do not set insecure passwords - don't set a default password for altlinux, gentoo, openmandriva and pld - tools: exit with return code of lxc_execute() - Keep veth.pair.name on network shutdown - Makefile: fix static clang init.lxc build - Avoid waiting for bridge interface if disabled in sysconfig/lxc - Increased buffer length in print_stats() - avoid assigning to a variable which is not POSIX shell proof (bug #1498) - remove obsolete note about api stability - conf: less error prone pointer access - conf: lxc_map_ids() non-functional changes - caps: add lxc_{proc,file}_cap_is_set() - conf: check for {filecaps,setuid} on new{g,u}idmap - conf: improve log when mounting rootfs - ls: simplify the judgment condition when list active containers - fix typo introduced in #1509 - attach|unshare: fix the wrong comment - caps: skip file capability checks on android - autotools: check for cap_get_file - caps: return false if caps are not supported - conf: non-functional changes to setup_pts() - conf: use bind-mount for /dev/ptmx - conf: non-functional changes - utils: use loop device helpers from LXD - create ISSUE_TEMPLATE.md - cgroups: improve cgfsng debugging - issue template: fix typo - conf: close fd in lxc_setup_devpts() - conf: non-functional changes - utils: tweak lxc_mount_proc_if_needed() - Change sshd template to work with Ubuntu 17.04 - conf: order mount options - conf: add MS_LAZYTIME to mount options - monitor: report errno on exec() error - af unix: allow for maximum socket name - commands: avoid NULL pointer dereference - commands: non-functional changes - lxccontainer: avoid NULL pointer dereference - monitor: simplify abstract socket logic - precise is not the latest LTS, let's use xenial instead - fix the wrong exit status - conf: non-functional changes lxc_fill_autodev() - conf: remove /dev/console from lxc_fill_autodev() - conf: non-functional changes lxc_setup() - conf: non-functional changes to console functions - conf: improve lxc_setup_dev_console() - conf: lxc_setup_ttydir_console() - config: remove /dev/console bind mount - doc: document console behavior - utils: add lxc_unstack_mountpoint() - conf: unstack all mounts atop /dev/console - console: fail when we cannot allocate peer tty - start: remove umount2() - conf: non-functional changes - utils: handle > 2^31 in lxc_unstack_mountpoint() - Install systemd units for CentOS - Merge
[Group.of.nepali.translators] [Bug 1686648] Re: linux-raspi2: 4.4.0-1055.62 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Thursday, 18. May 2017 21:50 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Thursday, 18. May 2017 21:50 UTC - kernel-stable-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/1686648 Title: linux-raspi2: 4.4.0-1055.62 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686648/+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 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Thursday, 18. May 2017 21:51 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Thursday, 18. May 2017 21:51 UTC - kernel-stable-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/1686651 Title: linux-aws: 4.4.0-1017.26 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686651/+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 1686649] Re: linux-snapdragon: 4.4.0-1058.62 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Thursday, 18. May 2017 21:51 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Thursday, 18. May 2017 21:51 UTC - kernel-stable-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/1686649 Title: linux-snapdragon: 4.4.0-1058.62 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux-snapdragon source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686649/+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 1686652] Re: linux-gke: 4.4.0-1013.13 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true + kernel-stable-phase-changed:Thursday, 18. May 2017 21:52 UTC + kernel-stable-phase:Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 - phase: Promoted to proposed + phase: Released proposed-announcement-sent: true proposed-testing-requested: true - kernel-stable-phase-changed:Thursday, 18. May 2017 21:52 UTC - kernel-stable-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/1686652 Title: linux-gke: 4.4.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gke package in Ubuntu: Invalid Status in linux-gke source package in Xenial: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 phase: Released proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686652/+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 1691182] Re: linux-raspi2: 4.4.0-1056.63 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1691180 + kernel-stable-phase-changed:Thursday, 18. May 2017 21:47 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1691180 - kernel-stable-phase-changed:Thursday, 18. May 2017 21:47 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1691182 Title: linux-raspi2: 4.4.0-1056.63 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1691180 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691182/+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 1691247] Re: linux-azure: 4.10.0-1005.5 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-azure 4.10.0-1005.5 - is in main instead of universe linux-azure-cloud-tools-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-cloud-tools-4.10.0-1005-dbgsym 4.10.0-1005.5 - is in main instead of universe linux-azure-headers-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-headers-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-headers-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-headers-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-headers-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-headers-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-headers-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-tools-4.10.0-1005 4.10.0-1005.5 - is in main instead of universe linux-azure-tools-4.10.0-1005-dbgsym 4.10.0-1005.5 - is in main instead of universe linux-cloud-tools-4.10.0-1005-azure 4.10.0-1005.5 - is in main instead of universe linux-headers-4.10.0-1005-azure 4.10.0-1005.5 - is in main instead of universe linux-image-4.10.0-1005-azure 4.10.0-1005.5 - is in main instead of universe linux-image-4.10.0-1005-azure-dbgsym 4.10.0-1005.5 - is in main instead of universe linux-tools-4.10.0-1005-azure 4.10.0-1005.5 - is in main instead of universe linux-meta-azure 4.10.0.1005.5 - is in main instead of universe linux-azure 4.10.0.1005.5 - is in main instead of universe linux-headers-azure 4.10.0.1005.5 - is in main instead of universe linux-image-azure 4.10.0.1005.5 - is in main instead of universe linux-tools-azure 4.10.0.1005.5 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** 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/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the 4.10.0-1005.5 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 + kernel-stable-phase-changed:Thursday, 18. May 2017 21:40 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the 4.10.0-1005.5 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1686645 - kernel-stable-phase-changed:Thursday, 18. May 2017 21:40 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1691247 Title: linux-azure: 4.10.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete 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:
[Group.of.nepali.translators] [Bug 1690730] Re: New upstream microreleases 9.3.17, 9.5.7 and 9.6.3
This needs a postrgresql-9.6, since that is a different source package, for Zesty. ** Also affects: postgresql-9.6 (Ubuntu) Importance: Undecided Status: New ** Changed in: postgresql-9.6 (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1690730 Title: New upstream microreleases 9.3.17, 9.5.7 and 9.6.3 Status in postgresql-9.5 package in Ubuntu: Triaged Status in postgresql-9.6 package in Ubuntu: New Status in postgresql-9.5 source package in Trusty: Fix Committed Status in postgresql-9.6 source package in Trusty: New Status in postgresql-9.5 source package in Xenial: Fix Committed Status in postgresql-9.6 source package in Xenial: New Status in postgresql-9.5 source package in Yakkety: Fix Committed Status in postgresql-9.6 source package in Yakkety: New Status in postgresql-9.5 source package in Zesty: Fix Committed Status in postgresql-9.6 source package in Zesty: Fix Committed Bug description: https://www.postgresql.org/about/news/1746/ As per the standing micro-release exception these should land in stable Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.5/+bug/1690730/+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 1687129] Re: Needs to allow updates from the ESM archive
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.6 --- unattended-upgrades (0.90ubuntu0.6) xenial; urgency=medium * Add UbuntuESM to the list of sources automatically upgraded from by default. LP: #1687129. -- Steve LangasekTue, 02 May 2017 21:41:25 -0400 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1687129 Title: Needs to allow updates from the ESM archive Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Precise: Fix Released Status in unattended-upgrades source package in Trusty: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Status in unattended-upgrades source package in Zesty: Fix Released Bug description: [SRU Justification] When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match. [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both. [Test case] 1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates' 2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to enable the ESM archive 3. run 'sudo apt-get update' 4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 5. run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease' 6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed. 7. install unattended-upgrades from -proposed. 8. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 9. again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease' 10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package. [Regression potential] Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+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 1687129] Re: Needs to allow updates from the ESM archive
This bug was fixed in the package unattended-upgrades - 0.92ubuntu1.5 --- unattended-upgrades (0.92ubuntu1.5) yakkety; urgency=medium * Add UbuntuESM to the list of sources automatically upgraded from by default. LP: #1687129. -- Steve LangasekTue, 02 May 2017 21:43:24 -0400 ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: unattended-upgrades (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1687129 Title: Needs to allow updates from the ESM archive Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Precise: Fix Released Status in unattended-upgrades source package in Trusty: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Yakkety: Fix Released Status in unattended-upgrades source package in Zesty: Fix Released Bug description: [SRU Justification] When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match. [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 Since the ESM archive contains packages updated by the Ubuntu Security team, we should ensure the behavior of unattended-upgrades applies the same default policy to both. [Test case] 1. run 'sudo apt-get install ubuntu-advantage-tools unattended-upgrades ca-certificates' 2. run 'sudo ubuntu-advantage enable-esm ' with your private creds to enable the ESM archive 3. run 'sudo apt-get update' 4. create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 5. run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease' 6. run 'sudo unattended-upgrades --debug --dry-run' and verify that no unattended-upgrades package is installed. 7. install unattended-upgrades from -proposed. 8. again create a faked-up entry in /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_main_binary-amd64_Packages for the unattended-upgrades package with a higher version number 9. again run 'sudo sed -i -e"s/precise/$(lsb_release -c | cut -f2)/" /var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_precise_InRelease' 10. run 'sudo unattended-upgrades --debug --dry-run' and verify that it offers to install a new unattended-upgrades package. [Regression potential] Worst-case scenario is a bug that prevents future security updates from being applied correctly. This is not a concern for precise because there will be no further security updates /except/ those enabled by this SRU, but this SRU should also be included in all later stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+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 1674892] Re: zend_print_flat_zval_r doesn't consider reference
This bug was fixed in the package php7.0 - 7.0.18-0ubuntu0.16.10.1 --- php7.0 (7.0.18-0ubuntu0.16.10.1) yakkety; urgency=medium * New upstream release 7.0.18 - LP: #1686237 - LP: #1674892 - Refresh patches for new upstream release * Drop: - debian/patches/0048-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester. Closes LP #1658289. [ Fixed upstream in 7.0.16 ] - SECURITY REGRESSION: large mysql requests broken (LP #1668017) + debian/patches/fix_74021.patch: fix fetch_array with more than MEDIUMBLOB in ext/mysqlnd/mysqlnd_wireprotocol.c, added tests to ext/mysqli/tests/bug73800.phpt, ext/mysqli/tests/bug74021.phpt. [ Fixed upstream in 7.0.17 ] -- Nishanth Aravamudan Wed, 26 Apr 2017 16:55:19 -0700 ** Changed in: php7.0 (Ubuntu Yakkety) 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/1674892 Title: zend_print_flat_zval_r doesn't consider reference Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: Fix Committed Status in php7.0 source package in Yakkety: Fix Released Status in php7.0 source package in Zesty: Fix Released Status in php7.0 source package in Artful: Fix Released Bug description: [Impact] * Users hit an error with PHP7.0 when zend_print_flat_zval_r doesn't consider a reference. The following error may be triggered: PHP Notice: Array to string conversion; Catchable fatal error: Object could not be converted to string. [Test Case] * From the upstream bug: $a = array('a'); class b{}; $b = new b; $test[] =& $a; $test[] =& $b; test($test); function test() { debug_print_backtrace(); } Expected result: #0 test(Array ([0] => Array ([0] => a),[1] => b Object ())) called at [/Users/playcrab/Documents/code/php/test/test7.php:7] Actual result: -- #0 test(Array ([0] => PHP Notice: Array to string conversion in /Users/playcrab/Documents/code/php/test/test7.php on line 9 PHP Stack trace: PHP 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 PHP 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 PHP 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 PHP Catchable fatal error: Object of class b could not be converted to string in /Users/playcrab/Documents/code/php/test/test7.php on line 9 PHP Stack trace: PHP 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 PHP 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 PHP 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 Notice: Array to string conversion in /Users/playcrab/Documents/code/php/test/test7.php on line 9 Call Stack: 0.0068 353088 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 0.0080 353928 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 0.0080 353928 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 Array,[1] => Catchable fatal error: Object of class b could not be converted to string in /Users/playcrab/Documents/code/php/test/test7.php on line 9 Call Stack: 0.0068 353088 1. {main}() /Users/playcrab/Documents/code/php/test/test7.php:0 0.0080 353928 2. test() /Users/playcrab/Documents/code/php/test/test7.php:7 0.0080 353928 3. debug_print_backtrace() /Users/playcrab/Documents/code/php/test/test7.php:9 [Regression Potential] * I believe the regression potential is low to zero for this fix (via 7.0.18 upstream). The reason is that the code as-is in 16.04 does not work and leads to backtraces. The fix introduce upstream resolves the issue. --- https://bugs.php.net/bug.php?id=73916 We've hit this bug in 7.0.15, the current/latest version for Xenial. It was fixed in 7.0.16 by php.net, Feb 16 2017. It would be nice if Xenials packages would be updated to reflect this fix. Patch: http://git.php.net/?p=php- src.git;a=blobdiff;f=Zend/zend.c;h=2a47e9244ba787a2ad35e9220171b04d1a5de634;hp=3f3ca75e382b1dec98fd138307d812f36f02251e;hb=04379bcb1df25a9f9cc1d440f5c12105b9fbaf97;hpb=bd75f9e61375c7632bb55b0d49b470ecd94e8ec7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1674892/+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 :
[Group.of.nepali.translators] [Bug 1686237] Re: [SRU] microrelease update of src:php7.0 (7.0.18)
This bug was fixed in the package php7.0 - 7.0.18-0ubuntu0.16.10.1 --- php7.0 (7.0.18-0ubuntu0.16.10.1) yakkety; urgency=medium * New upstream release 7.0.18 - LP: #1686237 - LP: #1674892 - Refresh patches for new upstream release * Drop: - debian/patches/0048-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester. Closes LP #1658289. [ Fixed upstream in 7.0.16 ] - SECURITY REGRESSION: large mysql requests broken (LP #1668017) + debian/patches/fix_74021.patch: fix fetch_array with more than MEDIUMBLOB in ext/mysqlnd/mysqlnd_wireprotocol.c, added tests to ext/mysqli/tests/bug73800.phpt, ext/mysqli/tests/bug74021.phpt. [ Fixed upstream in 7.0.17 ] -- Nishanth Aravamudan Wed, 26 Apr 2017 16:55:19 -0700 ** Changed in: php7.0 (Ubuntu Yakkety) 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/1686237 Title: [SRU] microrelease update of src:php7.0 (7.0.18) Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: Fix Committed Status in php7.0 source package in Yakkety: Fix Released Status in php7.0 source package in Zesty: Fix Released Bug description: There have been a number of microreleases of PHP 7.0 upstream since the last update to Xenial (which corresponded to the merge in Zesty). As we have re-merged again in Artful, it feels appropriate to provide another MRE update to php7.0. A number of critical security and bug- fixes are present in each 7.0.x. Rather than backporting individual patches (e.g., Bug # 1569509), I believe it makes significantly more sense to follow the upstream 7.0.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.0.x: - 7.0.18: http://php.net/ChangeLog-7.php#7.0.18 The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly. Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packing to run the source tests during the build itself. I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.1.0. Additionally for this SRU, there is (at least) one bug fixed upstream which will be fixed by updating to a newer upstream version: LP: #1674892. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1686237/+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 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
This bug was fixed in the package iproute2 - 4.3.0-1ubuntu3.16.04.1 --- iproute2 (4.3.0-1ubuntu3.16.04.1) xenial; urgency=medium * debian/patches/1004-tc.8-Fix-reference-to-tc-tcindex.8.patch: [PATCH] tc.8: Fix reference to tc-tcindex.8. Thanks to Phil Sutter. LP: #1668813 -- Jon Grimm Fri, 10 Mar 2017 16:59:26 -0600 ** Changed in: iproute2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: Fix Released Status in iproute2 source package in Yakkety: Fix Released Bug description: [Impact] * The man pages for tc make reference to a non-existent tc-index man page. Purely a typo that should have been tc-tcindex. * Purely a documentation fix, but nice to fix for an LTS release that has many years left to it. [Test Case] * To see this issue, fire up a 16,04 image (I did so via lxd) and type: root@xi386# man tc | grep tc-index Filter packets based on traffic control index. See tc-index(8). , HOWEVER: root@xi386:~# man tc-index No manual entry for tc-index * on a fixed system you should only see refereces to tc-tcindex, not tc-index: root@x1:~# man tc | grep tc-index root@x1:~# man tc | grep tc-tcindex Filter packets based on traffic control index. See tc-tcindex(8). red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), tc-tcindex(8), tc-u32(8), [Regression Potential] * This is only a change to man pages, so any regression would be non- functional, but this fix is trivial to fix and verify, and the fix is exactly from the upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+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 1668813] Re: The tc man page references tc-index man page but tc-index man page does not exist
This bug was fixed in the package iproute2 - 4.3.0-1ubuntu3.16.10.1 --- iproute2 (4.3.0-1ubuntu3.16.10.1) yakkety; urgency=medium * debian/patches/1004-tc.8-Fix-reference-to-tc-tcindex.8.patch: [PATCH] tc.8: Fix reference to tc-tcindex.8. Thanks to Phil Sutter. LP: #1668813 -- Jon Grimm Fri, 10 Mar 2017 16:59:26 -0600 ** Changed in: iproute2 (Ubuntu Yakkety) 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/1668813 Title: The tc man page references tc-index man page but tc-index man page does not exist Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Xenial: Fix Released Status in iproute2 source package in Yakkety: Fix Released Bug description: [Impact] * The man pages for tc make reference to a non-existent tc-index man page. Purely a typo that should have been tc-tcindex. * Purely a documentation fix, but nice to fix for an LTS release that has many years left to it. [Test Case] * To see this issue, fire up a 16,04 image (I did so via lxd) and type: root@xi386# man tc | grep tc-index Filter packets based on traffic control index. See tc-index(8). , HOWEVER: root@xi386:~# man tc-index No manual entry for tc-index * on a fixed system you should only see refereces to tc-tcindex, not tc-index: root@x1:~# man tc | grep tc-index root@x1:~# man tc | grep tc-tcindex Filter packets based on traffic control index. See tc-tcindex(8). red(8), tc-route(8), tc-sfb(8), tc-sfq(8), tc-stab(8), tc-tbf(8), tc-tcindex(8), tc-u32(8), [Regression Potential] * This is only a change to man pages, so any regression would be non- functional, but this fix is trivial to fix and verify, and the fix is exactly from the upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1668813/+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 1690147] Re: Missing versioned dependency against python3-google-compute-engine
This bug was fixed in the package gce-compute-image-packages - 20170426-0ubuntu2~16.04.0 --- gce-compute-image-packages (20170426-0ubuntu2~16.04.0) xenial; urgency=medium * Backport to xenial. * debian/control: - Make the python3-google-compute-engine dependency versioned for gce-compute-image-packages always on the most current version (LP: #1690147). gce-compute-image-packages (20170426-0ubuntu1) artful; urgency=medium * New upstream release (LP: #1689205). -- Łukasz 'sil2100' ZemczakThu, 11 May 2017 14:25:24 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1690147 Title: Missing versioned dependency against python3-google-compute-engine Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: [Impact] With the latest upstream release of gce-compute-image-packages, it was now required that along with upgrading of the gce-compute-image- packages package the python3-google-compute-engine had to be upgraded as well for everything to work. Both come from the same source package and the dep was unversioned previously. To make sure that both get upgraded at the same time and not cause any breakages in the future, a = ${source:Version} dep is recommended. [Test Case] On a system that has the previous version of gce-compute-image- packages do an upgrade of only gce-compute-image-packages (sudo apt install gce-compute-image-packages) and make sure that python3-google- compute-engine is upgraded with it as well. [Regression Potential] None. This is a dependency-only change - the dependency was always there so for all cases other than upgrades no differences will be visible. I cannot think of any other parts that could be affected by this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1690147/+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 1689205] Re: [SRU] Update google compute-image-packages to 20170426
This bug was fixed in the package gce-compute-image-packages - 20170426-0ubuntu2~16.10.0 --- gce-compute-image-packages (20170426-0ubuntu2~16.10.0) yakkety; urgency=medium * Backport to yakkety. * debian/control: - Make the python3-google-compute-engine dependency versioned for gce-compute-image-packages always on the most current version (LP: #1690147). gce-compute-image-packages (20170426-0ubuntu1) artful; urgency=medium * New upstream release (LP: #1689205). -- Łukasz 'sil2100' ZemczakThu, 11 May 2017 14:25:24 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: gce-compute-image-packages (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1689205 Title: [SRU] Update google compute-image-packages to 20170426 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1689205/+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 1689205] Re: [SRU] Update google compute-image-packages to 20170426
This bug was fixed in the package gce-compute-image-packages - 20170426-0ubuntu2~16.04.0 --- gce-compute-image-packages (20170426-0ubuntu2~16.04.0) xenial; urgency=medium * Backport to xenial. * debian/control: - Make the python3-google-compute-engine dependency versioned for gce-compute-image-packages always on the most current version (LP: #1690147). gce-compute-image-packages (20170426-0ubuntu1) artful; urgency=medium * New upstream release (LP: #1689205). -- Łukasz 'sil2100' ZemczakThu, 11 May 2017 14:25:24 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1689205 Title: [SRU] Update google compute-image-packages to 20170426 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1689205/+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 1690147] Re: Missing versioned dependency against python3-google-compute-engine
This bug was fixed in the package gce-compute-image-packages - 20170426-0ubuntu2~16.10.0 --- gce-compute-image-packages (20170426-0ubuntu2~16.10.0) yakkety; urgency=medium * Backport to yakkety. * debian/control: - Make the python3-google-compute-engine dependency versioned for gce-compute-image-packages always on the most current version (LP: #1690147). gce-compute-image-packages (20170426-0ubuntu1) artful; urgency=medium * New upstream release (LP: #1689205). -- Łukasz 'sil2100' ZemczakThu, 11 May 2017 14:25:24 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: gce-compute-image-packages (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1690147 Title: Missing versioned dependency against python3-google-compute-engine Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: [Impact] With the latest upstream release of gce-compute-image-packages, it was now required that along with upgrading of the gce-compute-image- packages package the python3-google-compute-engine had to be upgraded as well for everything to work. Both come from the same source package and the dep was unversioned previously. To make sure that both get upgraded at the same time and not cause any breakages in the future, a = ${source:Version} dep is recommended. [Test Case] On a system that has the previous version of gce-compute-image- packages do an upgrade of only gce-compute-image-packages (sudo apt install gce-compute-image-packages) and make sure that python3-google- compute-engine is upgraded with it as well. [Regression Potential] None. This is a dependency-only change - the dependency was always there so for all cases other than upgrades no differences will be visible. I cannot think of any other parts that could be affected by this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1690147/+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 1689205] Re: [SRU] Update google compute-image-packages to 20170426
This bug was fixed in the package gce-compute-image-packages - 20170426-0ubuntu2~17.04.0 --- gce-compute-image-packages (20170426-0ubuntu2~17.04.0) zesty; urgency=medium * Backport to zesty. * debian/control: - Make the python3-google-compute-engine dependency versioned for gce-compute-image-packages always on the most current version (LP: #1690147). gce-compute-image-packages (20170426-0ubuntu1) artful; urgency=medium * New upstream release (LP: #1689205). -- Łukasz 'sil2100' ZemczakThu, 11 May 2017 14:25:24 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1689205 Title: [SRU] Update google compute-image-packages to 20170426 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1689205/+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 1690147] Re: Missing versioned dependency against python3-google-compute-engine
This bug was fixed in the package gce-compute-image-packages - 20170426-0ubuntu2~17.04.0 --- gce-compute-image-packages (20170426-0ubuntu2~17.04.0) zesty; urgency=medium * Backport to zesty. * debian/control: - Make the python3-google-compute-engine dependency versioned for gce-compute-image-packages always on the most current version (LP: #1690147). gce-compute-image-packages (20170426-0ubuntu1) artful; urgency=medium * New upstream release (LP: #1689205). -- Łukasz 'sil2100' ZemczakThu, 11 May 2017 14:25:24 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1690147 Title: Missing versioned dependency against python3-google-compute-engine Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: [Impact] With the latest upstream release of gce-compute-image-packages, it was now required that along with upgrading of the gce-compute-image- packages package the python3-google-compute-engine had to be upgraded as well for everything to work. Both come from the same source package and the dep was unversioned previously. To make sure that both get upgraded at the same time and not cause any breakages in the future, a = ${source:Version} dep is recommended. [Test Case] On a system that has the previous version of gce-compute-image- packages do an upgrade of only gce-compute-image-packages (sudo apt install gce-compute-image-packages) and make sure that python3-google- compute-engine is upgraded with it as well. [Regression Potential] None. This is a dependency-only change - the dependency was always there so for all cases other than upgrades no differences will be visible. I cannot think of any other parts that could be affected by this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1690147/+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 1610500] Re: package pptpd 1.4.0-7ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I am nominating this for Xenial. As previously suggested this should be fixed there and has been reported in other bugs in Xenial to help ease upgrade. ** Also affects: pptpd (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/1610500 Title: package pptpd 1.4.0-7ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in pptpd package in Ubuntu: Fix Released Status in pptpd source package in Xenial: Confirmed Bug description: This is one of the crashed that happened during upgrade to 16.04 LTS. The install routine was exited with a script error. Try to figure stuff of since pptpd seems to be outdated ProblemType: Package DistroRelease: Ubuntu 16.04 Package: pptpd 1.4.0-7ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Fri Aug 5 21:40:28 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-02-25 (1988 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pptpd Title: package pptpd 1.4.0-7ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1610500/+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 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding
** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667531 Title: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding Status in linux package in Ubuntu: Won't Fix Status in linux source package in Xenial: Won't Fix Status in linux source package in Yakkety: Won't Fix Bug description: Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin commit fd7aabb062fa1a8331a786d617744de220eaf002 Author: Haiyang ZhangDate: Fri Dec 2 15:55:38 2016 -0800 tools: hv: Enable network manager for bonding scripts on RHEL We found network manager is necessary on RHEL to make the synthetic NIC, VF NIC bonding operations handled automatically. So, enabling network manager here. Signed-off-by: Haiyang Zhang Reviewed-by: K. Y. Srinivasan Signed-off-by: David S. Miller commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6 Author: Haiyang Zhang Date: Mon Jul 11 17:06:42 2016 -0700 tools: hv: Add a script to help bonding synthetic and VF NICs This script helps to create bonding network devices based on synthetic NIC (the virtual network adapter usually provided by Hyper-V) and the matching VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can function as one network device, and fail over to the synthetic NIC if VF is down. Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by this script. Signed-off-by: Haiyang Zhang Reviewed-by: K. Y. Srinivasan Signed-off-by: David S. Miller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667531/+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 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image
** Changed in: linux (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/1650058 Title: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: In order to have the correct VF driver to support SR-IOV in Azure, the Mellanox OFED distribution needs to be included in the kernel and the image. Mellanox's drivers are not upstream, but they are available from here: https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487 While this configuration is not explicitly listed as supported in the release notes, Microsoft and Mellanox engineers are working on the corresponding Windows Server 2016 PF driver to support this VF driver in operation in Ubuntu guests. I file file a corresponding rebase request to pick up the PCI passthrough and other SR-IOV work done for the Hyper-V capabilities in the upstream 4.9 kernel. Only 64-bit support for Ubuntu 16.04's HWE kernel is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650058/+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 1632786] Re: [Hyper-V] do not lose pending heartbeat vmbus packets
** Changed in: linux (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/1632786 Title: [Hyper-V] do not lose pending heartbeat vmbus packets Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: Hyper-V hosts can continue sending heartbeat packets to guests independent of whether earlier packets have responses, which led to a potential issue of these packets being dropped when responses took too long to process. Lost heartbeats will lead to the host diagnosing that the guest is dead and should be shut down and restarted. The following patch was submitted upstream but has not yet been accepted. I will add the upstream commit ID once the patch goes into linux-next: From: Long LiThe host keeps sending heartbeat packets independent of the guest responding to them. Even though we respond to the heartbeat messages at interrupt level, we can have situations where there maybe multiple heartbeat messages pending that have not been responded to. For instance this occurs when the VM is paused and the host continues to send the heartbeat messages. Address this issue by draining and responding to all the heartbeat messages that maybe pending. Signed-off-by: Long Li Signed-off-by: K. Y. Srinivasan CC: Stable --- V2: Submit the patch to stable as well - Joshua R. Poulson drivers/hv/hv_util.c | 10 +++--- 1 files changed, 7 insertions(+), 3 deletions(-) diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c index 4aa3cb6..bcd0630 100644 --- a/drivers/hv/hv_util.c +++ b/drivers/hv/hv_util.c @@ -314,10 +314,14 @@ static void heartbeat_onchannelcallback(void *context) u8 *hbeat_txf_buf = util_heartbeat.recv_buffer; struct icmsg_negotiate *negop = NULL; - vmbus_recvpacket(channel, hbeat_txf_buf, -PAGE_SIZE, , ); + while (1) { + + vmbus_recvpacket(channel, hbeat_txf_buf, +PAGE_SIZE, , ); + + if (!recvlen) + break; - if (recvlen > 0) { icmsghdrp = (struct icmsg_hdr *)_txf_buf[ sizeof(struct vmbuspipe_hdr)]; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632786/+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 1677958] Re: no SSL certificate verify
** Also affects: nghttp2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nghttp2 (Ubuntu) Status: New => Fix Released ** Changed in: nghttp2 (Ubuntu Xenial) Status: New => Confirmed -- 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/1677958 Title: no SSL certificate verify Status in nghttp2 package in Ubuntu: Fix Released Status in nghttp2 source package in Xenial: Confirmed Bug description: Hi developers: We made a large scale security static analysis on several open source projects, and found some mistakes in nghttp2 1.7.1. In the @example/client.c:539: static void fetch_uri(const struct URI *uri) { { [...] ssl_ctx = SSL_CTX_new(SSLv23_client_method()); if (ssl_ctx == NULL) { dief("SSL_CTX_new", ERR_error_string(ERR_get_error(), NULL)); } init_ssl_ctx(ssl_ctx); ssl = SSL_new(ssl_ctx); if (ssl == NULL) { dief("SSL_new", ERR_error_string(ERR_get_error(), NULL)); } /* To simplify the program, we perform SSL/TLS handshake in blocking I/O. */ ssl_handshake(ssl, fd); [...] } The function ssl_handshake(ssl, fd) achieve SSL_connect(ssl). When finish the SSL connect, you immedicately start to execute read/write operation without verify certificate,which can lead to MITM attack and cause leakage of sensitive data.We recommand you add verify operation such as SSL_CTX_set_verify or SSL_get_peer_certificate to guarantee the security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nghttp2/+bug/1677958/+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 1691600] Re: oops on 4.4.0-66-generic
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Tags added: kernel-da-key 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/1691600 Title: oops on 4.4.0-66-generic Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: My long running (year old) Ubuntu 16.04 AWS instance got wedged sometime yesterday. I was able to (barely) log in, but I found a system load of 248 (on a single core system), and it was basically unusable. After a reboot, I inspected the logs around the time at which it stopped reporting to Landscape and I found a kernel trace (attached). Note, that I am running canonical-livepatch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1691600/+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 1691180] Re: linux: 4.4.0-79.100 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: true + kernel-stable-phase-changed:Thursday, 18. May 2017 11:43 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: true - kernel-stable-phase-changed:Thursday, 18. May 2017 11:43 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1691180 Title: linux: 4.4.0-79.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New 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 backports: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691180/+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 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1672819 Title: exec'ing a setuid binary from a threaded program sometimes fails to setuid Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: New Status in linux source package in Zesty: New Bug description: == SRU REQUEST XENIAL, YAKKETY, ZESTY == Due to two race conditions in check_unsafe_exec(), exec'ing a setuid binary from a threaded program sometimes fails to setuid. == Fix == Sauce patch for Xenial, Yakkety + Zesty: https://lists.ubuntu.com/archives/kernel-team/2017-May/084102.html This fix re-executes the unsafe check if there is a discrepancy between the expected fs count and the found count during the racy window during thread exec or exit. This re-check occurs very infrequently and saves a lot of addition locking on per thread structures that would make performance of fork/exec/exit prohibitively expensive. == Test case == See the example C code in the patch, https://lists.ubuntu.com/archives /kernel-team/2017-May/084102.html Run the test code as follows: for i in $(seq 1000); do ./a; done With the patch, no messages are emitted, without the patch, one sees a message: "Failed, got euid 1000 (expecting 0)" ..which shows the setuid program failed the check_unsafe_exec() because of the race. == Regression potential == breaking existing safe exec semantics. This can be reproduced with https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813 With that, and go 1.8, if you run “make” and then for i in `seq 99`; do ./a_go; done you'll see a variable number of ”GOT 1000” (or whatever your user id is). If you don't, add one or two more 9s on there. That's a simple go reproducer. You can also use “a_p” instead of “a_go” to see one that only uses pthreads. “a_c” is a C version that does *not* reproduce the issue. But it's not pthreads: if in a_go.go you comment out the “import "C"”, you'll still see the “GOT 1000” messages, in a static binary that uses no pthreads, just clone(2). You'll also see a bunch of warnings because it's not properly handling an EAGAIN from clone, but that's unrelated. If you pin the process to a single thread using taskset, you don't get the issue from a_go; a_p continues to reproduce the issue. In some virtualized environments we haven't been able to reproduce the issue either (e.g. some aws instances), but kvm works (you need -smp to see the issue from a_go). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: john 2354 F...m pulseaudio /dev/snd/controlC0: john 2354 F pulseaudio CurrentDesktop: Unity Date: Tue Mar 14 17:17:23 2017 HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf InstallationDate: Installed on 2014-04-27 (1051 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude E6510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1672819/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net
[Group.of.nepali.translators] [Bug 1690362] Re: Exar usb-serial doesn't restore baud rate after resume from S3/S4
** Also affects: linux (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/1690362 Title: Exar usb-serial doesn't restore baud rate after resume from S3/S4 Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: Resume from suspend-to-ram and suspend-to-disk should restore data send/receive over Exar usb-serial ports. The XR21V1412 ports were using the hardware power-on default of 9600bps after resume from S3/S4. This patch re-initializes the baud rate and fixes the re-connection issues after resume from S3/S4. This bug is to track the integration of the driver released by the vendor to fix this issue. Changelog: Version 1B, 11/6/2015 Fixed Bug: The conditional logic to support kernel 3.9 was incorrect(line 396 in xr_usb_serial_common.c). Version 1A, 1/9/2015 This driver will work with any USB UART function in these Exar devices: XR21V1410/1412/1414 XR21B1411 XR21B1420/1422/1424 XR22801/802/804 Exar serial devices are typically enuremated as /dev/ttyXRUSB[0-3] This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1690362/+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 1690310] Re: st_pressure, st_accel IIO drivers fail to detect sensors after reloading kernel modules
** Also affects: linux (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/1690310 Title: st_pressure, st_accel IIO drivers fail to detect sensors after reloading kernel modules Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: Fails to register the sensors when the user unloads and re-loads the driver module. 1. Unload the kernel modules for st_pressure $ sudo rmmod st_pressure_i2c $ sudo rmmod st_pressure 2. Re-load the driver $ sudo insmod st_pressure $ sudo insmod st_pressure_i2c --- OR --- $ sudo modprobe st_pressure_i2c dmesg errors: [ 160.935707] iio iio:device2: DRDY on pdata not valid. [ 160.941505] st-press-i2c: probe of i2c-SMO9210:00 failed with error -22 The driver fails to register the pressure sensor device. Devices supported by st_accel driver also suffer from the same bug. This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1690310/+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 1690498] Re: Upgrade Redpine WLAN/BT driver to ver. 1.2.RC9
** Also affects: linux (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/1690498 Title: Upgrade Redpine WLAN/BT driver to ver. 1.2.RC9 Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: Upgrade the Redpine WLAN/BT RS9113 driver in Ubuntu Xenial kernel to ver. 1.2.RC9. This is the latest version of the driver provided by Redpine. For now, this driver is enabled only on x86, x86_64 architectures. The impact is restricted to { SDIO_DEVICE(0x041B, 0x9330) } for SDIO based WiFi-BT modules and on USB bus, this driver binds only to RS9113, lets upstream kernel driver handle other RSI chipsets. Fixes since previous release(see lp: #1669672) Changelog: 1.2.RC9 - WLAN Bug Fixes: --- 1) BT reset added before going to S3/S4/S5 sleep when WoWLAN is enabled. 2) Station connection check before going to S3/S4/S5 sleep removed. WLAN Limitations/Features NOT Supported: 1) S5 with WoWLAN does not work. 2) For GTK rekey, wakeup trigger send to host. BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC8 - WLAN Bug Fixes: --- 1) Added power leak fixes for S4. 2) S5 WoLAN issue resolved. 3) Wakeup short pulse issue resolved. WLAN Limitations/Features NOT Supported: 1) S5 with WoWLAN does not work. 2) For GTK rekey, wakeup trigger send to host. BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC7 - WLAN Bug Fixes: --- 1) Configured host wakeup pin as active low from driver. WLAN Limitations/Features NOT Supported: 1) S5 with WoWLAN does not work. 2) For GTK rekey, wakeup trigger send to host. BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. 1.2.RC6 - WLAN Bug Fixes: --- 1) AP data throughput issue resolved. 2) Scan results issue resolved. WLAN Limitations/Features NOT Supported: 1) S5 with WoWLAN does not work. 2) For GTK rekey, wakeup trigger send to host. BT Limitations/Features NOT Supported: 1) To connect multiple BT slaves, connection should be initiated from rsi module. 2) In coex mode, BT file transfer fails at times with certain mobiles. This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1690498/+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 1690321] Re: Fix CVE-2017-7294
** Changed in: linux (Ubuntu Precise) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Precise) Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- 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/1690321 Title: Fix CVE-2017-7294 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Precise: Won't Fix Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: Tracking bug for fixing CVE-2017-7294 Affected file: drivers/gpu/drm/vmwgfx/vmwgfx_surface.c Fix: e7e11f99564222d82f0ce84bd521e57d78a6b678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690321/+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 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
> Anything else needed on src:systemd side of things? Hi xnox, Well, in a perfect world and with a time machine to help you could look what in zesty's systemd fixed it to work reliably even with the suboptimal service file. But then you have more important tasks all around you and it is fixed where it was broken. Until then I think "opinion" is more appropriate than "incomplete" - yet at whatever state it is ok to just let it hang around for now. If similar issues come up for other services we might reconsider. ** Changed in: systemd (Ubuntu) Status: Incomplete => Opinion ** Changed in: systemd (Ubuntu Xenial) Status: Incomplete => Opinion -- 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/1644530 Title: keepalived fails to restart cleanly due to the wrong systemd settings Status in keepalived package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Opinion Status in keepalived source package in Xenial: Fix Released Status in systemd source package in Xenial: Opinion Status in keepalived package in Debian: New Bug description: [Impact] * Restarts of keepalived can leave stale processes with the old configuration around. * The systemd detection of the MainPID is suboptimal, and combined with not waiting on signals being handled it can fail on second restart killing the (still) remaining process of the first start. * Upstream has a PIDFile statement, this has proven to avoid the issue in the MainPID guessing code of systemd. [Test Case] * Set up keepalived, the more complex the config is the "bigger" is the reace window, below in the description is a trivial sample config that works well. * As a test run the loop restarting the service head-to-head while staying under the max-restart limit $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo systemctl restart keepalived; sudo systemctl status keepalived | egrep 'Main.*exited'; done; done Expectation: no output other than timing Without fix: sometimes MainPIDs do no more exist, in these cases the child processes are the "old" ones from last execution with the old config. [Regression Potential] * Low because * A PIDFile statement is recommended by systemd for type=forking services anyway. * Upstream keepalived has this statement in their service file * By the kind of change, it should have no functional impact to other parts of the service other than for the PID detection of the job by Systemd. * Yet regression potential is never zero. There might be the unlikely case, which were considered working before due to a new config not properly being picked up. After the fix they will behave correctly and might show up as false-positives then if e.g. config was bad. [Other Info] * Usually a fix has to be in at least the latest Development release before SRUing it. But as I outlined below in later Releases than Xenial systemd seems to have improved making this change not-required. We haven't identified the bits for this (there is a bug task here), and they might as well be very complex. I think it is correct to fix Xenial in this regard with the simple change to the service file for now. * To eventually match I created a Debian bug task to ask them for the inclusion of the PIDFile so it can slowly tickle back down to newer Ubuntu Releases - also there more often people run backports where the issue might occur on older systemd versions (just as it does for us on Xenial) --- Because "PIDFile=" directive is missing in the systemd unit file, keepalived sometimes fails to kill all old processes. The old processes remain with old settings and cause unexpected behaviors. The detail of this bug is described in this ticket in upstream: https://github.com/acassen/keepalived/issues/443. The official systemd unit file is available since version 1.2.24 by this commit: https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15 This includes "PIDFile" directive correctly: PIDFile=/var/run/keepalived.pid We should go the same way. I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic. Package: keepalived Version: 1.2.19-1 === How to reproduce: I used the two instances of Ubuntu 16.04.2 on DigitalOcean: Configurations -- MASTER server's /etc/keepalived/keepalived.conf: vrrp_script chk_nothing { script "/bin/true" interval 2 } vrrp_instance G1 { interface eth1 state BACKUP priority 100 virtual_router_id 123 unicast_src_ip unicast_peer { } track_script { chk_nothing } } BACKUP server's