[Group.of.nepali.translators] [Bug 1666570] Re: Post install script has error in RegEx
** No longer affects: tomcat7 (Ubuntu Zesty) -- 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/1666570 Title: Post install script has error in RegEx Status in tomcat7 package in Ubuntu: Invalid Status in tomcat8 package in Ubuntu: Fix Released Status in tomcat7 source package in Trusty: Fix Released Status in tomcat7 source package in Xenial: Fix Committed Status in tomcat8 source package in Xenial: Fix Released Status in tomcat7 source package in Yakkety: Fix Committed Status in tomcat8 source package in Yakkety: Fix Committed Status in tomcat8 source package in Zesty: Fix Released Status in tomcat7 package in Debian: New Status in tomcat8 package in Debian: Fix Released Bug description: == Begin SRU Template == [Impact] * On upgrade of tomcat7 package, if a user has updated their JAVA_OPTS variable to include a '%' an upgrade will fail. The sed command in the postinst uses the '%' character to act as a delimiter, previous versions used '/' however it was updated to '%' in hopes it was far less common. * This SRU updates it to a character that should not be found in the JAVA_ARGS value, namely '\001'. * This is the same solution Debian and tomcat maintainers are now using for Tomcat8. [Test Case] An example to test Tomcat7 on Trusty. The same instructions can apply to Tomcat8 on the other releases. Overview: Install the version from the current release. Modify JAVA_OPTS and then install the version from proposed to validate it upgrades successfully. * lxc launch ubuntu-daily:trusty trusty * lxc exec trusty bash * apt install tomcat7 * Edit /etc/default/tomcat7, set JAVA_OPTS="-Djava.awt.headless=true -XX:ErrorFile=/var/log/tomcat7/java_error%p.log -XX:+DisableExplicitGC -XX:+UseG1GC" * # Enable proposed * apt update * apt install tomcat7 * When asked, 'Keep the local version currently installed' * With the fix, install will complete * Without the fix, the error as described under "Other Info" will appear [Regression Potential] * Users currently experiencing this issue would be expecting a SRU fix to come from us. Working around it would require changing their JAVA_OPTS temporarily, accepting the maintainers version of the defaults script, or modifying the package's postinst script directly. * In either case the proposed fix will over write any changes an end user may have made to the postinst, and all for correctly working expected behavior. * There is the slight, albeit incredibly low chance, that someone actually has the '\001' character in their JAVA_OPTS. In which, case the upgrade would fail as this bug describes. [Other Info] * Using a new delimiter that is far less likely to be in someone's path. This is not the first time the delimiter has changed, as it originally as '/' which is obviously going to show up as soon as someone adds a path. * Upstream change to tomcat8: https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/patch/?id=7664221d66701e2c31a31fe3b4f22e8bea4158dc * Error message on failure: Setting up tomcat7 (7.0.52-1ubuntu0.10) ... sed: -e expression #1, char 97: unknown option to `s' dpkg: error processing package tomcat7 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: tomcat7 E: Sub-process /usr/bin/dpkg returned an error code (1) == End SRU Template == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1666570/+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 1630285] Re: mwifiex_pcie crashes after several bind/unbind
Somehow this appears to have possibly landed in xenial without undergoing the verification expected (which might explain why it was still in New, rather than Fix Committed). I have set this back to Fix Committed for xenial, and re-did the verification. As above, verification was limited to making sure the workaround was present, since there is no hardware available to me to run the test with. ** Changed in: nplan (Ubuntu Xenial) Status: Fix Released => Fix Committed ** Tags added: verification-done-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/1630285 Title: mwifiex_pcie crashes after several bind/unbind Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in nplan package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in nplan source package in Xenial: Fix Committed Status in linux source package in Yakkety: New Status in nplan source package in Yakkety: Fix Committed Bug description: [Impact] netplan-configured systems with mwifiex interfaces crash if netplan attempts to unbind/bind the interface. [Test case] 1) Run 'netplan apply' on a system with mwifiex_pci driver. The system should not crash, and the mwifiex interface should remain untouched. [Regression potential] Interfaces other than those affected by unbind/bind crashes or failures should still be unbound when 'netplan apply' is run. This affects most wireless interfaces, with the notable exception of mwifiex and brcmfmac. Failure to apply netplan configuration for a legitimate mwifiex device (wireless connection driven by NetworkManager renderer using netplan) would also constitute a regression. [Original bug report] # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind Keep doing the bind/unbind actions, it would crash very soon. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630285/+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 1630285] Re: mwifiex_pcie crashes after several bind/unbind
Closing the nplan xenial task as Fix Released since it already have nplan 0.14~16.04; which contains the fix for mwifiex -- this was released in 0.13; backported as 0.13~16.04 (which was landed prior, but also included in 0.14~16.04 in xenial-updates). ** Changed in: nplan (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1630285 Title: mwifiex_pcie crashes after several bind/unbind Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in nplan package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in nplan source package in Xenial: Fix Committed Status in linux source package in Yakkety: New Status in nplan source package in Yakkety: Fix Committed Bug description: [Impact] netplan-configured systems with mwifiex interfaces crash if netplan attempts to unbind/bind the interface. [Test case] 1) Run 'netplan apply' on a system with mwifiex_pci driver. The system should not crash, and the mwifiex interface should remain untouched. [Regression potential] Interfaces other than those affected by unbind/bind crashes or failures should still be unbound when 'netplan apply' is run. This affects most wireless interfaces, with the notable exception of mwifiex and brcmfmac. Failure to apply netplan configuration for a legitimate mwifiex device (wireless connection driven by NetworkManager renderer using netplan) would also constitute a regression. [Original bug report] # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind Keep doing the bind/unbind actions, it would crash very soon. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630285/+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 1665088] Re: netplan bridge config doesn't support stp boolean
Verification done on xenial and yakkety with netplan 0.23~: The parameters are being accepted by netplan parsing network v2 yaml; and appropriately copied on to the resulting configuration for the renderer. STP is not yet supported by systemd however, so further testing could not be done. ** Tags removed: verification-needed ** Tags added: verification-done-xenial verification-done-yakkety ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1665088 Title: netplan bridge config doesn't support stp boolean Status in netplan: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in nplan source package in Yakkety: Fix Committed Status in systemd source package in Yakkety: New Status in nplan source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] Users of netplan may wish to specify a custom MTU value for a device. [Test case] - Run nplan integration tests on the release - Validate that netplan generate && netplan apply alone, without config, behave as expected (no result) - Validate that netplan generate && netplan apply with minimal config writes /run/NetworkManager/conf.d/10-globally-managed-devices.conf - Validate that netplan generate && netplan apply works with any existing configuation. - Use the config below; ensure behavior is as expected (STP value is set on the interface; adjust device names as appropriate). There should be no errors at applying the requested configuration. - Use the config below with the 'stp' key; the device should be brought up and include the default value set for the kernel. [Regression potential] STP default value should continue to be used for the bridge configured using netplan if STP is unset in configuration. --- networkd supports setting STP value in Bridge type netdevs, but netplan does not accept the key. root@ubuntu:/etc/netplan# apt-cache policy nplan nplan: Installed: 0.18 Candidate: 0.18 Version table: *** 0.18 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:/etc/netplan# lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 root@ubuntu:/etc/netplan# cat 52-bridge.yaml network: ethernets: eth0: addresses: - 10.11.12.13/24 match: macaddress: '52:54:00:12:34:00' set-name: foobar0 eth1: match: macaddress: '52:54:00:12:34:02' set-name: eth1 eth2: match: macaddress: '52:54:00:12:34:04' set-name: eth2 bridges: br0: addresses: - 192.168.14.2/24 interfaces: - eth1 - eth2 parameters: ageing-time: 250 priority: 22 forward-delay: 1 hello-time: 1 max-age: 10 path-cost: eth1: 50 eth2: 75 stp: true version: 2 root@ubuntu:/etc/netplan# netplan generate Error in network definition //etc/netplan/52-bridge.yaml line 24 column 16: unknown key stp To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1665088/+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 1698367] Re: Rebase linux-azure to 4.11
** Also affects: linux-azure (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/1698367 Title: Rebase linux-azure to 4.11 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: New Bug description: SRU Justification: Impact: The support for Hyper-V and Azure is under heavy development and due to this reason it's necessary to keep the Azure kernel as closest to upstream as possible in order to get access to the latest features and bug fixes. Fix: Rebase the Azure kernel to the latest 4.11 artful kernel in proposed. Testcase: It's necessary to run a smoke test and check if any performance regression was caused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1698367/+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 1698371] Re: Azure: throughput performance regression after #1690177
** Also affects: linux-azure (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/1698371 Title: Azure: throughput performance regression after #1690177 Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: New Bug description: SRU Justification: Impact: After #1690177, throughput between instances in Azure decreased drastically. The performance dropped from around 10 Gbits/sec to 50 Mbits/sec. Fix: The problem seems to be caused by this commit: 5740cde3743b vmbus: only reschedule tasklet if time limit exceeded Testcase: Use iperf between to Azure instances with the Azure kernel to measure throughput. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1698371/+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 1698372] Re: Azure: remove AF_HYPERV socket
** Also affects: linux-azure (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/1698372 Title: Azure: remove AF_HYPERV socket Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: New Bug description: SRU Justification: Impact: AF_HYPERV wasn't accepted upstream and will be replace by a solution based on AF_VSOCK. Fix: Revert the patches applied by #1690196. Testcase: AF_HYPERV should not be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1698372/+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 1570748] Re: Bug: resize instance after edit flavor with horizon
** Changed in: nova/mitaka 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/1570748 Title: Bug: resize instance after edit flavor with horizon Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive liberty series: Triaged Status in Ubuntu Cloud Archive mitaka series: Triaged Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) kilo series: Fix Released Status in OpenStack Compute (nova) liberty series: Fix Released Status in OpenStack Compute (nova) mitaka series: Fix Released Status in nova-powervm: Fix Released Status in tempest: Fix Released Status in nova package in Ubuntu: Fix Released Status in nova source package in Wily: Triaged Status in nova source package in Xenial: Triaged Status in nova source package in Yakkety: Fix Released Bug description: Error occured when resize instance after edit flavor with horizon (and also delete flavor used by instance) Reproduce step : 1. create flavor A 2. boot instance using flavor A 3. edit flavor with horizon (or delete flavor A) -> the result is same to edit or to delelet flavor because edit flavor means delete/recreate flavor) 4. resize or migrate instance 5. Error occured Log : nova-compute.log File "/opt/openstack/src/nova/nova/conductor/manager.py", line 422, in _object_dispatch return getattr(target, method)(*args, **kwargs) File "/opt/openstack/src/nova/nova/objects/base.py", line 163, in wrapper result = fn(cls, context, *args, **kwargs) File "/opt/openstack/src/nova/nova/objects/flavor.py", line 132, in get_by_id db_flavor = db.flavor_get(context, id) File "/opt/openstack/src/nova/nova/db/api.py", line 1479, in flavor_get return IMPL.flavor_get(context, id) File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 233, in wrapper return f(*args, **kwargs) File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 4732, in flavor_get raise exception.FlavorNotFound(flavor_id=id) FlavorNotFound: Flavor 7 could not be found. This Error is occured because of below code: /opt/openstack/src/nova/nova/compute/manager.py def resize_instance(self, context, instance, image, reservations, migration, instance_type, clean_shutdown=True): if (not instance_type or not isinstance(instance_type, objects.Flavor)): instance_type = objects.Flavor.get_by_id( context, migration['new_instance_type_id']) I think that deleted flavor should be taken when resize instance. I tested this in stable/kilo, but I think stable/liberty and stable/mitaka has same bug because source code is not changed. thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1570748/+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 1570748] Re: Bug: resize instance after edit flavor with horizon
** Changed in: nova/liberty 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/1570748 Title: Bug: resize instance after edit flavor with horizon Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive liberty series: Triaged Status in Ubuntu Cloud Archive mitaka series: Triaged Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) kilo series: Fix Released Status in OpenStack Compute (nova) liberty series: Fix Released Status in OpenStack Compute (nova) mitaka series: Fix Committed Status in nova-powervm: Fix Released Status in tempest: Fix Released Status in nova package in Ubuntu: Fix Released Status in nova source package in Wily: Triaged Status in nova source package in Xenial: Triaged Status in nova source package in Yakkety: Fix Released Bug description: Error occured when resize instance after edit flavor with horizon (and also delete flavor used by instance) Reproduce step : 1. create flavor A 2. boot instance using flavor A 3. edit flavor with horizon (or delete flavor A) -> the result is same to edit or to delelet flavor because edit flavor means delete/recreate flavor) 4. resize or migrate instance 5. Error occured Log : nova-compute.log File "/opt/openstack/src/nova/nova/conductor/manager.py", line 422, in _object_dispatch return getattr(target, method)(*args, **kwargs) File "/opt/openstack/src/nova/nova/objects/base.py", line 163, in wrapper result = fn(cls, context, *args, **kwargs) File "/opt/openstack/src/nova/nova/objects/flavor.py", line 132, in get_by_id db_flavor = db.flavor_get(context, id) File "/opt/openstack/src/nova/nova/db/api.py", line 1479, in flavor_get return IMPL.flavor_get(context, id) File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 233, in wrapper return f(*args, **kwargs) File "/opt/openstack/src/nova/nova/db/sqlalchemy/api.py", line 4732, in flavor_get raise exception.FlavorNotFound(flavor_id=id) FlavorNotFound: Flavor 7 could not be found. This Error is occured because of below code: /opt/openstack/src/nova/nova/compute/manager.py def resize_instance(self, context, instance, image, reservations, migration, instance_type, clean_shutdown=True): if (not instance_type or not isinstance(instance_type, objects.Flavor)): instance_type = objects.Flavor.get_by_id( context, migration['new_instance_type_id']) I think that deleted flavor should be taken when resize instance. I tested this in stable/kilo, but I think stable/liberty and stable/mitaka has same bug because source code is not changed. thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1570748/+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 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::inpu
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released ** Changed in: canonical-devices-system-image Assignee: Stephen M. Webb (bregma) => (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/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Released Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Released Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Invalid Status in mir source package in Xenial: Fix Released Status in unity-system-compositor source package in Xenial: Invalid Status in mir source package in Yakkety: Fix Released Status in mir source package in Zesty: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+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 1696364] Re: linux-joule: 4.4.0-1002.7 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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/1696364 Title: linux-joule: 4.4.0-1002.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-joule package in Ubuntu: Invalid Status in linux-joule 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 -- boot-testing-requested: true kernel-stable-master-bug: 1696357 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1696364/+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
