From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW26
Date: Mon, 28 Jun 2021 19:23:24 -0700 [thread overview]
Message-ID: <210901d76c8d$bd81d4f0$38857ed0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3079 bytes --]
All,
YP M+ or high bugs which moved to a new milestone in WW26 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=6428> 6428
Improve the ability to isolate changes that have caused a rebuild
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.99
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=11361> 11361
oe-build-perf-test: monitor system resource utilization
randy.macleod@windriver.com
sakib.sajal@windriver.com
3.99
3.4 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12279> 12279
enhance manifest not found warning
kai.kang@windriver.com
kai.kang@windriver.com
3.4 M1
3.4 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12342> 12342
lib32-core-image-sato -ctestimage failed due to wrong package names
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.4 M4
3.4 M3
kai.kang@windriver.com
unassigned@yoctoproject.org
3.4 M1
3.4 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13025> 13025
WIC image install support
kexin.hao@windriver.com
kexin.hao@windriver.com
3.4 M1
3.5
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14099> 14099
PACKAGE_EXCLUDE not removing packages when PACKAGE_CLASSES = "package_deb"
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.4 M1
3.4 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14125> 14125
busybox wget ssl is exposed to MitM attack due to CVE-2018-1000500
randy.macleod@windriver.com
shachar@vdoo.com
3.4 M1
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14163> 14163
libevent arm ptest intermittent failure
randy.macleod@windriver.com
yf3yu@uwaterloo.ca
3.4 M1
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14244> 14244
util-linux script:_size ptest failure
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.4 M4
3.4 M3
kai.kang@windriver.com
unassigned@yoctoproject.org
3.4 M1
3.4 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14339> 14339
bitbake generates zombie Parser processes (hard to reproduce)
randy.macleod@windriver.com
randy.macleod@windriver.com
3.4 M1
3.4 M3
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14434> 14434
[3.4 M1] dmesg: proc: Bad value for 'hidepid' with poky-altcfg distro
yi.zhao@windriver.com
yi.zhao@windriver.com
3.4 M2
0.0.0
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14444> 14444
[multilib] lib32-core-image-minimal -c populate_sdk failure on dunfell
randy.macleod@windriver.com
raj.khem@gmail.com
3.4
3.4 M2
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
* Cell: (208) 244-4460
* Email: sjolley.yp.pm@gmail.com <mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 36319 bytes --]
next reply other threads:[~2021-06-29 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 2:23 Stephen Jolley [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-01 6:01 M+ & H bugs with Milestone Movements WW26 Stephen K Jolley
2024-07-01 23:29 Stephen K Jolley
2022-06-27 22:52 sjolley.yp.pm
2020-06-30 23:28 Stephen Jolley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='210901d76c8d$bd81d4f0$38857ed0$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox