[Group.of.nepali.translators] [Bug 1639230] Re: reschedule fails with ip already allocated error
** Changed in: nova/newton 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/1639230 Title: reschedule fails with ip already allocated error Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) newton series: Fix Released Status in nova package in Ubuntu: Fix Released Status in nova source package in Xenial: Confirmed Bug description: Tried to create a server in a multi-host environment. The create failed on the first host that was attempted due to a ClientException raised by nova.volume.cinder.API.initialize_connection while trying to attach a volume. When the build was rescheduled on a different host, it should have realized that the network was already allocated by the first attempt and reused that, but the network_allocated=True from instance.system_metadata somehow disappeared, leading to the following exception that causes the reschedule to fail: 2016-10-13 04:48:29.007 16273 WARNING nova.network.neutronv2.api [req-9b343ef7-e8d9-4a61-b86c-a61908afe4df 0688b01e6439ca32d698d20789d52169126fb41fb1a4ddafcebb97d854e836c9 94e1baed634145e0aade858973ae88e8 - - -] [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] Neutron error creating port on network 5038a36b-cb1e-4a61-b26c-a05a80b37ed6 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] Traceback (most recent call last): 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 392, in _create_port_minimal 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] port_response = port_client.create_port(port_req_body) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 98, in wrapper 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] ret = obj(*args, **kwargs) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 750, in create_port 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] return self.post(self.ports_path, body=body) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 98, in wrapper 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] ret = obj(*args, **kwargs) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 365, in post 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] headers=headers, params=params) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 98, in wrapper 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] ret = obj(*args, **kwargs) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 300, in do_request 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] self._handle_fault_response(status_code, replybody, resp) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/nova/network/neutronv2/api.py", line 98, in wrapper 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] ret = obj(*args, **kwargs) 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 275, in _handle_fault_response 2016-10-13 04:48:29.007 16273 ERROR nova.network.neutronv2.api [instance: b85d6c6c-e385-4601-aa47-5c580f893c9b] exception_handler_v20(status_code, error_body) 2016-10-13 04:48:29.007 16273
[Group.of.nepali.translators] [Bug 1690484] Re: pcre2: CVE-2017-7186 and CVE-2016-3191
** Also affects: pcre2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: pcre2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1690484 Title: pcre2: CVE-2017-7186 and CVE-2016-3191 Status in pcre2 package in Ubuntu: Fix Released Status in pcre2 source package in Xenial: New Bug description: CVE-2017-7186 - CVE-2017-7186 is the one known CVE fixed in Debian stretch that still affects Ubuntu 16.04 LTS and 16.10. It was fixed in 17.04 already. CVE-2016-3191 - CVE-2016-3191 is the one known CVE fixed in Debian stretch that still affects Ubuntu 16.04 LTS. It was fixed in 16.10 and newer already. "The compile_branch function in pcre_compile.c in PCRE 8.x before 8.39 and pcre2_compile.c in PCRE2 before 10.22 mishandles patterns containing an (*ACCEPT) substring in conjunction with nested parentheses, which allows remote attackers to execute arbitrary code or cause a denial of service (stack-based buffer overflow) via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror, aka ZDI-CAN-3542." https://security-tracker.debian.org/tracker/CVE-2016-3191 https://bugzilla.redhat.com/show_bug.cgi?id=1311503 Fedora patch: http://pkgs.fedoraproject.org/cgit/rpms/pcre2.git/tree/pcre2-10.21-Fix-workspace-overflow-for-deep-nested-parentheses-w.patch?id=fc9ba26 https://vcs.pcre.org/pcre2?view=revision=489 Testing Done None Packaging Info -- The Debian maintainer uses dgit for the pcre packages. You can run 'dgit clone pcre2' to get the packaging along with the extra metadata that actually describes the changes that were done to the source package. I did this and pushed it to https://git.launchpad.net/~jbicha/ubuntu/+source/pcre2 But the Debian source package itself does not have a patch system which makes it much more difficult for us to see what changes were made and why. I think for maintainability with how Ubuntu packaging generally works, it makes sense here to switch to 3.0 (quilt). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1690484/+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 1890276] Re: inetd does not answer broadcast requests
** Also affects: openbsd-inetd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openbsd-inetd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openbsd-inetd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: openbsd-inetd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: openbsd-inetd (Ubuntu Bionic) Status: New => Fix Released ** Changed in: openbsd-inetd (Ubuntu Xenial) Status: New => Fix Released ** Changed in: openbsd-inetd (Ubuntu) Status: New => Triaged ** Changed in: openbsd-inetd (Ubuntu Eoan) Status: New => Triaged ** Changed in: openbsd-inetd (Ubuntu Focal) 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/1890276 Title: inetd does not answer broadcast requests Status in openbsd-inetd package in Ubuntu: Triaged Status in openbsd-inetd source package in Xenial: Fix Released Status in openbsd-inetd source package in Bionic: Fix Released Status in openbsd-inetd source package in Eoan: Triaged Status in openbsd-inetd source package in Focal: Triaged Bug description: When I call inetd services rup or rusersd in broadcast mode, I get answers from my Ubuntu 18.04 machines only. An Ubuntu 20.04 machine (here rzpc101) answers only when addressed directly: zierke@rzpc100$ rup rzpc100.informatik.un 14:02 up 10 days,8:30, load 0.52 0.38 0.23 rzlinux.informatik.un 14:02 up1 day,3:12, load 0.04 0.09 0.03 rzpc174.informatik.un 14:02 up 4 days, 19:28, load 0.00 0.01 0.00 ^C zierke@rzpc100$ rup rzpc101 rzpc101.informatik.un 14:02 up 3:29, 3 users, load 0.33 0.32 0.15 zierke@rzpc100$ rusers rzpc100.informatik.u zierke zierke rzlinux.informatik.u zierke zierke zierke ^C zierke@rzpc100$ rusers rzpc101 rzpc101.informatik.u zierke zierke zierke zierke@rzpc101$ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 zierke@rzpc100$ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openbsd-inetd 0.20160825-4build1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 14:03:06 2020 InstallationDate: Installed on 2020-07-24 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: openbsd-inetd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbsd-inetd/+bug/1890276/+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 1890265] Re: BUG: Version 3.5.27-1ubuntu1.7 breaks config using icap
** Also affects: squid3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965012 Importance: Unknown Status: Unknown ** Also affects: squid3 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: squid3 (Ubuntu Xenial) Status: New => Confirmed ** Changed in: squid3 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: squid3 (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: squid3 (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- 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/1890265 Title: BUG: Version 3.5.27-1ubuntu1.7 breaks config using icap Status in squid3 package in Ubuntu: Triaged Status in squid3 source package in Xenial: Confirmed Status in squid3 source package in Bionic: Confirmed Status in squid3 package in Debian: Unknown Bug description: Using ubuntu 18.04 I had a squid config using c-icap to scan requests/responses using ClamAV. It was working OK since long time ago. Today, squid has (security)updated to 3.5.27-1ubuntu1.7 and now, connection to icap is broken. That is the error at squid-cache.log 2020/08/04 09:44:08 kid1| essential ICAP service is down after an options fetch failure: icap://127.0.0.1:1344/virus_scan [down,!opt] After downgrading to 3.5.27-1ubuntu1.6 it starts working again. The icap service is working fine, tested with `c-icap-client -i 127.0.0.1 -p 1344 -s virus_scan` Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1890265/+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 1872560] Re: integer overflow in whoopsie 0.2.69
** Tags removed: rls-ff-incoming
** Changed in: whoopsie (Ubuntu Eoan)
Status: Confirmed => Won't Fix
** Changed in: whoopsie (Ubuntu Groovy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1872560
Title:
integer overflow in whoopsie 0.2.69
Status in whoopsie package in Ubuntu:
Fix Committed
Status in whoopsie source package in Xenial:
Fix Released
Status in whoopsie source package in Bionic:
Fix Released
Status in whoopsie source package in Eoan:
Won't Fix
Status in whoopsie source package in Focal:
Fix Released
Status in whoopsie source package in Groovy:
Fix Committed
Bug description:
Hi,
I have found a security issue on whoopsie 0.2.69 and earlier.
## Vulnerability in whoopsie
- whoopsie 0.2.69 and earlier have a heap-based buffer overflow
vulnerability.
- An attacker can cause a denial of service (memory corruption and
application crash) via a crafted .crash file.
## Basic
When a program has been crashed, Linux system tries to create a '.crash' file
on '/var/crash/' directory with python script located in
'/usr/share/apport/apport'.
The file contains a series of system crash information including core dump,
syslog, stack trace, memory map info, etc.
After the creation of '.crash' file, whoopsie extracts the above information
from the '.crash' file and encodes it into binary json (bson) format.
Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error
Report system.
## Vulnerability
Unfortunately, we have found a heap-based buffer overflow vulnerability
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
The data in '.crash' file is stored in key-value form and the whoopsie
separately measures the length of 'key' and 'value' to allocate memory region
during the encoding.
A heap-based buffer overflow can occur when an integer overflow happens on a
variable that contains length of 'key'.
FYI, a issue to that raised by 'value' is well covered by performing
exception handling.
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]
const uint32_t len = strlen( name ) + 1;
- Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value.
- Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]
b->data = bson_realloc( b->data, new_size );
- Unexpected small memory region is allocated due to above integer
overflow.
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]
bson_append( b, name, len );
- Memory corruption happens when unexpected small memory region is
allocated.
## Attack Scenario
1) Create a fake.crash file
- '.crash' file is composed of the following format: 'key : value'.
- To cause the overflow attack, the size of 'key' should be in double amount
of INT32_MAX.
- The size of 'value' doesn’t matter, but not zero length.
$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
$ cat fake.crash
AAA … AA : B
2) Trigger the whoopsie to read the fake.crash file
- Just create 'fake.upload' file by touch command.
- Or launch apport-gtk gui or apport-bug cli application.
3) Check out the result
- After a while, the whoopsie has been killed by segmentation fault.
Sincerely,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1862938] Re: Enable late loading of microcode by default
** Changed in: intel-microcode (Ubuntu) Status: Fix Released => Won't Fix ** Changed in: intel-microcode (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: intel-microcode (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: intel-microcode (Ubuntu Eoan) Status: Fix Committed => Won't Fix ** Changed in: intel-microcode (Ubuntu Focal) Status: Fix Released => 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/1862938 Title: Enable late loading of microcode by default Status in intel-microcode package in Ubuntu: Won't Fix Status in intel-microcode source package in Xenial: Won't Fix Status in intel-microcode source package in Bionic: Won't Fix Status in intel-microcode source package in Eoan: Won't Fix Status in intel-microcode source package in Focal: Won't Fix Bug description: [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. * Normally intel microcode is applied "early" for an uncompressed prepended initramfs archive. However, on systems booting without an initrd, or a missbuilt one, microcode might not get applied. In that case, we need to attempt loading microcode late which may give users security protection against CPU vulnerabilities which they might otherwise be lacking. In an ideal world, everyone would apply their bios/OEM updates with microcode updates in a timely fashion and then we wouldn't need to update CPU microcode from userspace at all. [Test Case] * Install updated package * Reobot * Observe early application of microcode $ journalctl -b | grep microcode Feb 12 12:02:48 ottawa kernel: microcode: microcode updated early to revision 0xd6, date = 2019-10-03 * Remove /usr/share/initramfs-tools/hooks/intel_microcode to prevent correct generation of early microcode updates * Rebuild initrd with update-initramfs -u * Reboot * Observe in dmesg that late loading of microcode is performed $ journalctl -b | grep microcode Feb 12 12:32:54 ottawa kernel: TAA: Vulnerable: Clear CPU buffers attempted, no microcode Feb 12 12:32:54 ottawa kernel: MDS: Vulnerable: Clear CPU buffers attempted, no microcode Feb 12 12:32:54 ottawa kernel: microcode: sig=0x506e3, pf=0x20, revision=0xc6 Feb 12 12:32:54 ottawa kernel: microcode: Microcode Update Driver: v2.2. Feb 12 12:32:57 ottawa kernel: microcode: updated to revision 0xd6, date = 2019-10-03 Feb 12 12:32:57 ottawa kernel: x86/CPU: CPU features have changed after loading microcode, but might not take effect. Feb 12 12:32:57 ottawa kernel: microcode: Reload completed, microcode revision: 0xd6 (Note the lack of "early" in above messages) [Regression Potential] * Application of microcode is a risky operation, especially if the cores are busy. Hence we prefer bios updates & early microcode updates, and those will remain the place. The late loading of microcode is really here for the cases were the previous two update strategies have failed. For example, from time to time, certain microcode updates are pulled or get blacklisted from late loading. [Other Info] * The majority of our users on bare-metal machines boot correctly with early microcode updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1862938/+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 1888268] Re: xenial/linux-raspi2: 4.4.0-1137.146 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1888274 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 23. July 2020 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1888267 variant: debs versions: main: 4.4.0-1137.146 meta: 4.4.0.1137.137 -- 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/1888268 Title: xenial/linux-raspi2: 4.4.0-1137.146 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1888274 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 23. July 2020 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1888267 variant: debs versions: main: 4.4.0-1137.146 meta: 4.4.0.1137.137 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1888268/+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 1888274] Re: xenial/linux: 4.4.0-187.217 -proposed tracker
No outstanding ADT issues ** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1888274 Title: xenial/linux: 4.4.0-187.217 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 22. July 2020 11:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1888272 trusty/linux-lts-xenial: bug 1888273 xenial/linux-aws: bug 1888263 xenial/linux-cascade: bug 1888265 xenial/linux-fips: bug 1888271 xenial/linux-kvm: bug 1888266 xenial/linux-raspi2: bug 1888268 xenial/linux-snapdragon: bug 1888270 xenial/linux/caracalla-kernel: bug 1888259 xenial/linux/pc-kernel: bug 1888260 xenial/linux/stlouis-kernel: bug 1888261 variant: debs versions: main: 4.4.0-187.217 meta: 4.4.0.187.193 signed: 4.4.0-187.217 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1888274/+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 1888270] Re: xenial/linux-snapdragon: 4.4.0-1141.149 -proposed tracker
No outstanding ADT issues ** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1888270 Title: xenial/linux-snapdragon: 4.4.0-1141.149 -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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1888274 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 24. July 2020 10:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1888269 variant: debs versions: main: 4.4.0-1141.149 meta: 4.4.0.1141.133 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1888270/+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
