[Group.of.nepali.translators] [Bug 1770532] Re: DKIM signing not working in bionic
Hi Neustradamus,
the initial bug was reported as "Upon upgrading to bionic, amavisd-new DKIM
signing no longer works." so no one thought about former releases.
This also matches that there were no bugs about that issue, prior to Bionic
being released.
Also there is an increased risk the further changes are backported.
In this case all >=Bionic was on 2.11, but Xenial is 2.10 and Trusty even on
2.7.
So even if it happens in older versions the tradeoff between regressions for
current users vs the benefit of the fix for others might be different.
Especially with a somewhat dead upstream and a patch that existed in three
variants - also the test instructions are ok'ish but not totally complete to
try it in different variants. Therefore the risk is too high to apply it
further back (IMHO).
The old patch applies, but with a 788 line offset in a 34k line perl
file - oO
For now - for me personally - this is Won't Fix, but I'm open to be
convinced if we get enough confirmation and confidence in it. So if you
really think the very same issue affects Xenial, please share some
details about why you think so. Do the testing steps above trigger it
for you, if you can add extra details about testing if needed for
Xenial.
** Also affects: amavisd-new (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: amavisd-new (Ubuntu Xenial)
Status: New => 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/1770532
Title:
DKIM signing not working in bionic
Status in amavisd-new package in Ubuntu:
Fix Released
Status in amavisd-new source package in Xenial:
Won't Fix
Status in amavisd-new source package in Bionic:
Fix Released
Status in amavisd-new source package in Cosmic:
Fix Released
Status in amavisd-new package in Debian:
Confirmed
Bug description:
[Impact]
* There is a known upstream issue in 2.0.11 breaking DKIM signing.
- https://bugzilla.redhat.com/show_bug.cgi?id=1364730
- https://lists.amavis.org/pipermail/amavis-users/2018-February/005292.html
* given the activity on the report it seems plenty of people set this up
pre-Bionic and are now running into these failures on upgrade to the
current LTS.
* Add a fix to avoid more people being hit by this on upgrade and forced
to deploy workarounds (or drop the functionality)
[Test Case]
* Setup amavisd for DKIM signing, see
https://www.ijs.si/software/amavisd/amavisd-new-docs.html#dkim
or any of
https://www.faqforge.com/linux/how-to-enable-dkim-email-signatures-in-amavisd-new-and-ispconfig-3/
https://nwgat.ninja/setting-up-dkim-and-spf-with-amavis-on-ubuntu-16-04-2/
...
There seem to be a lot all doing the same essential steps.
TL;DR would be:
$ apt install amavisd-new
$ mkdir -p /var/db/dkim/
$ amavisd-new genrsa /var/db/dkim/example-foo.key.pem
Add in /etc/amavis/conf.d/21-ubuntu_defaults
$enable_dkim_signing = 1;
dkim_key('example.com', 'foo', '/var/db/dkim/example-foo.key.pem');
@dkim_signature_options_bysender_maps = (
{ '.' => { ttl => 21*24*3600, c => 'relaxed/simple' } } );
@mynetworks = qw(0.0.0.0/8 127.0.0.0/8 10.0.0.0/8 172.16.0.0/12
192.168.0.0/16); # list your internal networks
- Now showkeys will report your key including the pblic key you'll need
- amavisd-new showkeys
- add the public key (as displayed) to your DNS zone, increment SOA sequence
number and reload DNS;
- then test signing and a published key
- amavisd-new testkeys
Never the less you'd need to setup a lot of details and it feels
unclear if you test the right thing, therefor my preference is with so
many users reporting about the issue to rely on them to test their
real setups.
[Regression Potential]
* Lacking upstream being active there is always a chance things are
missed, but multiple people came up with very similar solutions and
multiple people tested these successfully.
The actual change sets the originating flag where it is needed on the
creation of dkim signatures.
Due to that setups not triggering dkim_make_signatures should be not
affected at all. And those that use dkim_make_signatures are those
failing now due to the issue.
[Other Info]
* Upstream seems essentially dead atm, so it is on the community (users
reporting patches on the ML) and the Distributions (e.g. Fedora have
taken a very similar change) alone for now.
* For some extra confidence I'd ask for some extra time in proposed for
this update.
Upon upgrading to bionic, amavisd-new DKIM signing no longer works.
A quick google search reveals that this is a known bug in amavisd
2.11.0:
https://bugzilla.redhat.com/show_bug.cgi?id=1364730
[Group.of.nepali.translators] [Bug 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Testing in progress verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806673 Title: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1783252] Re: gcc on ppc64le has bogus r30 register handling, as exposed by greenlet 0.4.14 will not build on ppc64le
Do we have a gcc-5 upload for bionic? As far as I can tell that's not
been done.
** Also affects: gcc-6 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcc-5 (Ubuntu Bionic)
Status: Fix Committed => Confirmed
** Changed in: gcc-6 (Ubuntu)
Status: New => Fix Committed
** Also affects: python-greenlet (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: gcc-5 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: gcc-6 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: python-greenlet (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gcc-5 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gcc-6 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** No longer affects: gcc-6 (Ubuntu Trusty)
** No longer affects: gcc-5 (Ubuntu Trusty)
** No longer affects: python-greenlet (Ubuntu Trusty)
** No longer affects: python-greenlet (Ubuntu Cosmic)
** No longer affects: gcc-5 (Ubuntu Cosmic)
** Changed in: gcc-6 (Ubuntu Cosmic)
Status: New => Fix Committed
** Changed in: gcc-6 (Ubuntu)
Status: Fix Committed => 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/1783252
Title:
gcc on ppc64le has bogus r30 register handling, as exposed by greenlet
0.4.14 will not build on ppc64le
Status in The Ubuntu-power-systems project:
Fix Committed
Status in gcc-5 package in Ubuntu:
Fix Released
Status in gcc-6 package in Ubuntu:
Confirmed
Status in python-greenlet package in Ubuntu:
Fix Released
Status in gcc-5 source package in Xenial:
Fix Committed
Status in gcc-5 source package in Bionic:
Confirmed
Status in gcc-6 source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* GCC has a minor bug w.r.t. clobber r30 register in PIC binaries.
* A patch to fix this has been upstream in 6+
* But it is not in gcc-5.4 as used on xenial
* This prevents compiling future-proof and correct greenlet code, on Ubuntu
16.04 LTS as used by current and supported Openstack Queens release on ppc64el
* Whilst backported greenlet is available via the cloud archive for binary
usage, the toolchain is still technically incorrect, and thus hinders using
Ubuntu 16.04 LTS as workers in upstream Openstack CI
* As a wishlist it would be nice to backport this one small gcc patch as an
SRU
[Test Case]
* git clone https://github.com/python-greenlet/greenlet
* cd greenlet
* ./setup.py build
Expect success
Current result failure:
creating build/temp.linux-ppc64le-2.7
powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c greenlet.c -o
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
In file included from slp_platformselect.h:16:0,
from greenlet.c:343:
platform/switch_ppc64_linux.h: In function 'slp_switch':
platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30' in
'asm'
__asm__ volatile ("" : : : REGS_TO_SAVE);
^
platform/switch_ppc64_linux.h:95:5: error: PIC register clobbered by 'r30' in
'asm'
__asm__ volatile ("" : : : REGS_TO_SAVE);
^
error: command 'powerpc64le-linux-gnu-gcc' failed with exit status 1
[Regression Potential]
* Upstream cherrypick present in later releases including bionic
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9213244550335bcb2b8590a0d7d58ac74c932361
[Other Info]
* Original bug report
== Comment: #0 - William M. Edmonds - 2018-07-23
16:21:41 ==
---Problem Description---
greenlet 0.4.14 will not build on ppc64le
Opened https://github.com/python-greenlet/greenlet/issues/136 because
attempting to build bdist_wheel for greenlet 0.4.14 on ppc64le Ubuntu
16.04 LTS yields the following error:
running build
running build_ext
building 'greenlet' extension
creating build
creating build/temp.linux-ppc64le-2.7
powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c greenlet.c -o
build/temp.linux-ppc64le-2.7/greenlet.o -fno-tree-dominator-opts
In file included from slp_platformselect.h:16:0,
from greenlet.c:343:
platform/switch_ppc64_linux.h: In function 'slp_switch':
platform/switch_ppc64_linux.h:80:5: error: PIC register clobbered by 'r30'
in 'asm'
__asm__ volatile ("" : : : REGS_TO_SAVE);
^
platform/switch_ppc64_linux.h:95:5: error: PIC register
[Group.of.nepali.translators] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
This bug was fixed in the package gnome-desktop3 - 3.8.4-0ubuntu3.3 --- gnome-desktop3 (3.8.4-0ubuntu3.3) trusty; urgency=medium * libgnome-desktop/display-name.c - some vendors encode the screen ratio (e.g 16/9) in the EDID instead of including the screen size, detect those cases and display the product name instead of the screen diagonal. (lp: #1755490) -- Dariusz Gadomski Fri, 30 Nov 2018 08:27:43 +0100 ** Changed in: gnome-desktop3 (Ubuntu Trusty) Status: Fix Committed => Fix Released ** Changed in: hwdata (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/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Released Status in hwdata source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Released Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Released Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+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 1792575] Re: Boot failure with efi shims from 20180913.0
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.20 --- grub2 (2.02~beta2-36ubuntu3.20) xenial; urgency=medium * debian/patches/linuxefi_fix_relocate_coff.patch: fix typo in relocate_coff() causing issues with relocation of code in chainload. (LP: #1792575) * debian/patches/linuxefi_truncate_overlong_reloc_section.patch: The Windows 7 bootloader has inconsistent headers; truncate to the smaller, correct size to fix chainloading Windows 7. (LP: #1792575) grub2 (2.02~beta2-36ubuntu3.19) xenial; urgency=medium * debian/patches/0001-i386-linux-Add-support-for-ext_lfb_base.patch: Add support for ext_lfb_base. (LP: #1785033) -- Mathieu Trudel-Lapierre Fri, 02 Nov 2018 13:08:47 -0400 ** Changed in: grub2 (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: grub2-signed (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/1792575 Title: Boot failure with efi shims from 20180913.0 Status in MAAS: Invalid Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in shim package in Ubuntu: Invalid Status in shim-signed package in Ubuntu: Invalid Status in grub2 source package in Xenial: Fix Released Status in grub2-signed source package in Xenial: Fix Released Status in shim source package in Xenial: Invalid Status in shim-signed source package in Xenial: Confirmed Status in grub2 source package in Bionic: Fix Released Status in grub2-signed source package in Bionic: Fix Released Status in shim source package in Bionic: Invalid Status in shim-signed source package in Bionic: Fix Released Bug description: [Impact] Chainloading grub via grub in a netboot context using MAAS's Boot to local disk feature. [Test cases] 1) Deploy UEFI system using MAAS 2) After deployment, have the system reboot to local disk (via netboot). [Regression potential] It is possible that the changes to chainloading logic that evaluates the sizes for various sections of code that gets copied to memory to load the next bootloader might fail to correctly evaluate the sections, or otherwise copy sections incorrectly, but this regression scenario is indistinguishable from the current case, there the system fails to load the next bootloader anyway. Error messages may vary, but the net result for a regression would be an incorrectly loaded bootloader, and thus error messages at boot from grub. --- We have had several nodes that had been deployed on Sept. 12 and were booting correctly fail to boot. On the console and during tracing we could see they were getting dhcp and pxe information, but then errored out with "relocation failed", dropping into a fallback grub menu with a Local boot option. After copying over bootx64.efi grubx64.efi from https://images.maas.io/ephemeral-v3/daily/bootloaders/uefi/amd64/20180906.0/ instead of 20180913.0/ and rebooting, boot would commence successfully. Hardware: Dell R640 maas 2.3.5-6511-gf466fdb-0ubuntu1~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1792575/+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 1798228] Re: Snap search results not in the same order as command line
This bug was fixed in the package gnome-software - 3.28.1-0ubuntu4.18.04.8 --- gnome-software (3.28.1-0ubuntu4.18.04.8) bionic; urgency=medium * Re-released to generate correct .changes file gnome-software (3.28.1-0ubuntu4.18.04.7) bionic; urgency=medium * debian/rules: * debian/patches/0001-packagekit-Add-configure-option-to-use-autoremove-fe.patch: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: * debian/patches/0023-snap-Don-t-treat-auth-cancellation-as-an-error.patch: - Stop cancelling snapd authorization triggers error notification (LP: #1785240) gnome-software (3.28.1-0ubuntu4.18.04.6) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Disable the Flatpak changes - SRU testing showed they broke downgrades gnome-software (3.28.1-0ubuntu4.18.04.5) bionic; urgency=medium * debian/patches/0023-Revert-Revert-flatpak-Use-list-of-related-apps-for-i.patch: * debian/patches/0024-flatpak-Check-if-a-related-app-is-installed-even-whe.patch: * debian/patches/0025-flatpak-Include-related-refs-to-the-app-s-runtime-on.patch: - Pull related flatpak refs (LP: #1754864) * debian/patches/0003-Sort-snaps-before-other-apps.patch: - Fix snap search result ordering (LP: #1798228) * debian/patches/0001-Set-reboot-notifications-as-urgent-to-avoid-them-tim.patch: - Stop reboot notification from timing out (LP: #1719797) * debian/patches/0001-lib-Allow-opening-CAB-files-that-resolve-more-than-o.patch: - Support composite CAB files (LP: #1798470) -- Robert Ancell Wed, 21 Nov 2018 12:29:27 +1300 ** Changed in: gnome-software (Ubuntu Bionic) 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/1798228 Title: Snap search results not in the same order as command line Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Won't Fix Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] When searching in GNOME Software, the Snap results are not returned in the same order as the command line. This is due to classic snaps being considered a lower quality than strict snaps. [Test Case] 1. Open GNOME Software 2. Search for "sky" Expected result: Snaps matching "sky" are returned, with the same order as the command line (Skype is first) Observed result: While mostly in the same order, some snaps are not (Skype is the last snap in the list, in eighth position). [Regression Potential] The fix is to set the "match value" of each Snap GsApp to be the order the results are returned in. This field is checked before the "kudo" field which is populated based on the confinement used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798228/+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 1804445] Re: Update rax-nova-agent to 2.1.18
This bug was fixed in the package rax-nova-agent - 2.1.18-0ubuntu1~16.04.0 --- rax-nova-agent (2.1.18-0ubuntu1~16.04.0) xenial; urgency=medium * Rebuild for Xenial. * Use compat level 9 build-depending on debhelper (>= 9) and dh-systemd rax-nova-agent (2.1.18-0ubuntu1) disco; urgency=medium * New upstream version 2.1.18 (LP: #1804445) - Update _setup_hostname to write to /etc/hostname file when failing on hostnamectl. Move function to base class since function is the same for all operating systems - Update tests to ensure changes to _setup_hostname are covered * Clean up after rax-openstack-guest-agents in postinst * Refresh patches rax-nova-agent (2.1.15-0ubuntu2) cosmic; urgency=medium * Drop dependency on python3-systemd, it is not needed with latest upstream * Use DefaultDependencies=no to prevent forming service ordering cycles (LP: #1788716) -- Balint Reczey Wed, 21 Nov 2018 15:22:22 +0100 ** Changed in: rax-nova-agent (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/1804445 Title: Update rax-nova-agent to 2.1.18 Status in rax-nova-agent package in Ubuntu: Fix Released Status in rax-nova-agent source package in Xenial: Fix Released Status in rax-nova-agent source package in Bionic: Fix Released Status in rax-nova-agent source package in Cosmic: Fix Released Bug description: [Impact] Nova-agent is provided by Rackspace for installation within guests that run on Rackspace Cloud. It is a collection of tools and daemons, packaged as rax-nova-agent, that ensure that the Ubuntu images published to Rackspace run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating rax-nova-agent to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. See https://wiki.ubuntu.com/rax-nova-agent-Updates for more details. [Test Case] * Ensure that upgrading from the previous version works in Rackspace's cloud including rebooting the instance * Ensure that images created with the updated rax-nova-agent boot and operate properly in Rackspace's cloud including rebooting the instance. * Additional tests may be performed by the CPC team, please contact them before marking the package verified. [Regression Potential] Latest changes included changing system initialization and networking setup which may break instance booting and setting up network connectivity potentially making the instance unreachable. The testing aims at revealing problems in those areas if there are regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rax-nova-agent/+bug/1804445/+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 1804445] Re: Update rax-nova-agent to 2.1.18
This bug was fixed in the package rax-nova-agent - 2.1.18-0ubuntu1~18.04.0 --- rax-nova-agent (2.1.18-0ubuntu1~18.04.0) bionic; urgency=medium * Bionic rax-nova-agent (2.1.18-0ubuntu1) disco; urgency=medium * New upstream version 2.1.18 (LP: #1804445) - Update _setup_hostname to write to /etc/hostname file when failing on hostnamectl. Move function to base class since function is the same for all operating systems - Update tests to ensure changes to _setup_hostname are covered * Clean up after rax-openstack-guest-agents in postinst * Refresh patches rax-nova-agent (2.1.15-0ubuntu2) cosmic; urgency=medium * Drop dependency on python3-systemd, it is not needed with latest upstream * Use DefaultDependencies=no to prevent forming service ordering cycles (LP: #1788716) -- Balint Reczey Wed, 21 Nov 2018 14:56:50 +0100 ** Changed in: rax-nova-agent (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: rax-nova-agent (Ubuntu Cosmic) 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/1804445 Title: Update rax-nova-agent to 2.1.18 Status in rax-nova-agent package in Ubuntu: Fix Released Status in rax-nova-agent source package in Xenial: Fix Released Status in rax-nova-agent source package in Bionic: Fix Released Status in rax-nova-agent source package in Cosmic: Fix Released Bug description: [Impact] Nova-agent is provided by Rackspace for installation within guests that run on Rackspace Cloud. It is a collection of tools and daemons, packaged as rax-nova-agent, that ensure that the Ubuntu images published to Rackspace run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating rax-nova-agent to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. See https://wiki.ubuntu.com/rax-nova-agent-Updates for more details. [Test Case] * Ensure that upgrading from the previous version works in Rackspace's cloud including rebooting the instance * Ensure that images created with the updated rax-nova-agent boot and operate properly in Rackspace's cloud including rebooting the instance. * Additional tests may be performed by the CPC team, please contact them before marking the package verified. [Regression Potential] Latest changes included changing system initialization and networking setup which may break instance booting and setting up network connectivity potentially making the instance unreachable. The testing aims at revealing problems in those areas if there are regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rax-nova-agent/+bug/1804445/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806579] Re: linux-raspi2: 4.4.0-1102.110 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress - snap-release-to-candidate: Snap not in candidate channel -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806579 Title: linux-raspi2: 4.4.0-1102.110 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806579/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806579] Re: linux-raspi2: 4.4.0-1102.110 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/RRpBVYwM/544-pi2-kernel-440-1102110-81 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806579 Title: linux-raspi2: 4.4.0-1102.110 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress snap-certification-testing: Ready To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806579/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806578] Re: linux-kvm: 4.4.0-1039.45 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806578 Title: linux-kvm: 4.4.0-1039.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806578/+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 1806573] Re: linux-aws: 4.4.0-1074.84 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - verification-testing: Testing in progress + promote-to-security: Master bug not ready for release + promote-to-updates: Master bug not ready for release -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806573 Title: linux-aws: 4.4.0-1074.84 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806573/+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 1806580] Re: linux-snapdragon: 4.4.0-1106.111 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 02:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress - verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806580 Title: linux-snapdragon: 4.4.0-1106.111 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 02:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806580/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806672 Title: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806579] Re: linux-raspi2: 4.4.0-1102.110 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress snap-certification-testing: Ready - verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806579 Title: linux-raspi2: 4.4.0-1102.110 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806569 phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 15:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress snap-certification-testing: Ready To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806579/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806673 Title: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806569] Re: linux: 4.4.0-141.167 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806569 Title: linux: 4.4.0-141.167 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the 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: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial) derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 (linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed phase-changed: Thursday, 06. December 2018 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Testing in progress regression-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806569/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806673 Title: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Saturday, 08. December 2018 13:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress snap-release-to-candidate: Snap not in candidate channel verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress - snap-release-to-beta: Snap not in beta channel - snap-release-to-edge: Snap not in edge channel + snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806672 Title: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Promoted to proposed phase-changed: Friday, 07. December 2018 15:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress snap-release-to-candidate: Snap not in candidate channel stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806672/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1805920] Re: iPXE ignores vlan 0 traffic
To keep potential regressions even lower I'd for now only consider that for >=Bionic. That also helps as if someone intentionally spawns an old type KVM machine (pre Bionic) on a >=Bionic host we don#t have to care about this too much (machine type, not release runnin IN the guest). That makes us able to ignore ipxe-qemu-256k-compat-efi-roms in regard to this issue. ** Also affects: ipxe-qemu-256k-compat (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Invalid ** Also affects: ipxe (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Also affects: ipxe-qemu-256k-compat (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ipxe (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ipxe-qemu-256k-compat (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Trusty) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) ** Changed in: ipxe-qemu-256k-compat (Ubuntu Trusty) Status: New => Invalid ** Changed in: ipxe-qemu-256k-compat (Ubuntu Xenial) Status: New => Invalid ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Trusty) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Xenial) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Bionic) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Cosmic) ** No longer affects: ipxe-qemu-256k-compat (Ubuntu Disco) ** Changed in: ipxe-qemu-256k-compat (Ubuntu) Status: New => Won't Fix ** Changed in: ipxe (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: ipxe (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: ipxe-qemu-256k-compat (Ubuntu) Status: Won't Fix => Invalid ** Changed in: ipxe (Ubuntu Bionic) Status: New => Triaged ** Changed in: ipxe (Ubuntu Cosmic) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1805920 Title: iPXE ignores vlan 0 traffic Status in MAAS: Invalid Status in ipxe package in Ubuntu: Fix Released Status in ipxe-qemu-256k-compat package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in ipxe source package in Trusty: Won't Fix Status in ipxe source package in Xenial: Won't Fix Status in ipxe source package in Bionic: Triaged Status in ipxe source package in Cosmic: Triaged Status in ipxe source package in Disco: Fix Released Bug description: I have three MAAS rack/region nodes which are blades in a Cisco UCS chassis. This is an FCE deployment where MAAS has two DHCP servers, infra1 is the primary and infra3 is the secondary. The pod VMs on infra1 and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If I reconfigure the subnet to provide DHCP on infra2 (either as primary or secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on the demoted infra node (that no longer serves DHCP) now fail to PXE boot. While commissioning a pod VM on infra2 I captured network traffic with tcpdump on the vnet interface. Here is the dump when the PXE boot fails (no dhcp server on infra2): https://pastebin.canonical.com/p/THW2gTSv4S/ Here is the dump when PXE boot succeeds (when infra2 is serving dhcp): https://pastebin.canonical.com/p/HH3XvZtTGG/ The only difference I can see is that in the unsuccessful scenario, the reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally vlan 0 traffic is passed as if it is not tagged and indeed, I can ping between the blades with no problem. Outgoing packets are untagged but incoming packets are tagged vlan 0 -- but the ping works. It seems vlan 0 is used as a part of 802.1p to set priority
[Group.of.nepali.translators] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
** Changed in: network-manager (Ubuntu Yakkety) Status: Triaged => 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1807743] Re: QEMU timerfd_create support on PowerPC
I agree to the case, but not fully to the fix.
The old syscall definitions came in in 2007 via [1] "Update Linux kernel
syscall list" (v0.10.0)
The feature adding the timerfd was added in 2014 with [2] "linux-user: support
timerfd_{create, gettime, settime} syscalls" (v2.2.0) using the wrong
definitions.
Later this was fixed 2015 for arm [3] "linux-user/arm: Correct
TARGET_NR_timerfd to TARGET_NR_timerfd_create" (v2.4.0) and for the rest
2016 in [4] "linux-user: correct timerfd_create syscall numbers"
(2.6.0).
No follow on fixes after that seen in upstream/master
That said things are fixed in Yakkety and later.
And the feature didn't exist in Trusty.
So only Xenial is affected.
The changes seem doable, and even if one used the old header on a
backport it became the number which still is the same number. Also those
headers are not meant for external use (no one links on that, and even
if one would - again - it is the same number now).
Old value only used in the defines:
$ grep -Hrn 'TARGET_NR_timerfd\s'
linux-user/sparc/syscall_nr.h:281:#define TARGET_NR_timerfd 312
linux-user/unicore32/syscall_nr.h:361:#define TARGET_NR_timerfd
350
linux-user/ppc/syscall_nr.h:322:#define TARGET_NR_timerfd 306
linux-user/sparc64/syscall_nr.h:313:#define TARGET_NR_timerfd 312
linux-user/mips/syscall_nr.h:323:#define TARGET_NR_timerfd
(TARGET_NR_Linux + 318)
linux-user/sh4/syscall_nr.h:326:#define TARGET_NR_timerfd 322
linux-user/m68k/syscall_nr.h:320:#define TARGET_NR_timerfd 318
linux-user/x86_64/syscall_nr.h:284:#define TARGET_NR_timerfd283
linux-user/s390x/syscall_nr.h:246:#define TARGET_NR_timerfd 317
linux-user/i386/syscall_nr.h:327:#define TARGET_NR_timerfd 322
linux-user/mips64/syscall_nr.h:287:#define TARGET_NR_timerfd
(TARGET_NR_Linux + 281)
linux-user/mips64/syscall_nr.h:601:#define TARGET_NR_timerfd
(TARGET_NR_Linux + 277)
linux-user/alpha/syscall_nr.h:416:#define TARGET_NR_timerfd
477
That said, that LGTM - except I'd backport the official upstream fixes [3] and
[4].
@Wes - would you mind outlining steps to reproduce as that is an integral part
of any SRU [5]
[1]:
https://git.qemu.org/?p=qemu.git;a=commit;h=8dd77cca03ac6325bda61dbdb8b8a2021fe524c3
[2]:
https://git.qemu.org/?p=qemu.git;a=commit;h=518343413fd311a3d95798b2c1d51853fd8d3c85
[3]:
https://git.qemu.org/?p=qemu.git;a=commit;h=d82322e175d58c0c8951cbc905da1ca9ee2e008c
[4]:
https://git.qemu.org/?p=qemu.git;a=commit;h=93a92d3bd649cd315db47b9fb5dcb6af657cc22c
[5]: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Precise)
Status: New => Invalid
** Changed in: qemu (Ubuntu Trusty)
Status: New => Invalid
** Changed in: qemu (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: qemu (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
** Description changed:
+ [Impact]
+
+ * A bad named define made timerfd_create be in the code but not
+ available
+
+ * two smaller fixes to be backported from upstream that change the define
+names; This will enable the timerfd_create in qemu-user
+
+ [Test Case]
+
+ * TODO @WES
+
+ [Regression Potential]
+
+ * The headers are only used internally so no outside regression should
+happen.
+ * Even then only the names changed but the number stayed, that means even
+if it would be an external ABI (it isn't) the number would be the same
+ * Internally the old define was only used when defining it, but not used
+(see grep in comment #1)
+ * The one regression I could think of is software running in qemu-user
+today and working by having a path like "does this have timerfd create
+-> no, ok then do A", with the change this might become "-> yes, so do
+B" and if that B is broken there would be a regression, but I'd
+consider it unlikely since all versions after Xenials 2.5 had the new
+variant and I have seen no complaints about it.
+
+ [Other Info]
+
+ * n/a
+
+
+ ---
+
QEMU erroneously fails to detect support for the timerfd_create syscall
when running user-mode emulation of PowerPC targets. QEMU supports the
timerfd_create syscall, but because the PowerPC target syscall header
has it named "timerfd" instead of "timerfd_create", support is
[Group.of.nepali.translators] [Bug 1806425] Re: linux-azure-edge: 4.18.0-1007.7~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806409 phase: Promoted to proposed phase-changed: Monday, 10. December 2018 13:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing in progress regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1806425 Title: linux-azure-edge: 4.18.0-1007.7~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806409 phase: Promoted to proposed phase-changed: Monday, 10. December 2018 13:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806425/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
