From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW12
Date: Mon, 27 Mar 2023 17:33:01 -0700 [thread overview]
Message-ID: <0f5401d9610c$dadabb50$909031f0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]
All,
YP M+ or high bugs which moved to a new milestone in WW12 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
13533
Devtool finish on _git package with SRCPV in PV points to wrong WORKDIR
randy.macleod@windriver.com
david.reyna@windriver.com
4.2 M3
4.3 M1
14141
devtool modify fails with submodules
randy.macleod@windriver.com
david.reyna@windriver.com
4.2 M3
4.3 M1
14890
create-spdx should parse license strings with and without spaces between license terms
randy.macleod@windriver.com
JPEWhacker@gmail.com
4.2 M3
4.3 M1
15077
AB-INT: unfs couldn't bind to tcp port 3049
randy.macleod@windriver.com
unassigned@yoctoproject.org
0.0.0
4.2 M4
15074
syncfs probe fails with newer compilers
randy.macleod@windriver.com
richard.purdie@linuxfoundation.org
3.1.23
4.3 M1
15075
filemap.py does not handle 64KB block size
randy.macleod@windriver.com
geissonator@yahoo.com
0.0.0
4.3 M1
15078
runqemu error string TypeError: not all arguments converted during string formatting
randy.macleod@windriver.com
JPEWhacker@gmail.com
0.0.0
4.2 M4
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: 21450 bytes --]
next reply other threads:[~2023-03-28 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 0:33 sjolley.yp.pm [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-24 14:04 M+ & H bugs with Milestone Movements WW12 Stephen K Jolley
2025-03-25 6:29 Stephen K Jolley
2024-03-25 20:52 Stephen K Jolley
2022-03-22 0:02 sjolley.yp.pm
2021-03-22 20:50 Stephen Jolley
2020-03-23 17:12 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='0f5401d9610c$dadabb50$909031f0$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=yocto@lists.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