From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW12
Date: Mon, 23 Mar 2020 10:12:32 -0700 [thread overview]
Message-ID: <0eac01d60136$3d9ba2c0$b8d2e840$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2970 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+
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13181> 13181
persist_data sqlite database mixed with forking is irreparably broken
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13319> 13319
Add SPDX license headers to all source files for matchbox/sato
randy.macleod@windriver.com
matthew.zeng@windriver.com
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13411> 13411
ptest-perl.bbclass run-ptest is too greedy for SKIP
timothy.t.orling@intel.com
timothy.t.orling@intel.com
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13425> 13425
Add bblock and bbunlock helper tools
randy.macleod@windriver.com
newcomer@yoctoproject.org
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13508> 13508
Meson detects googletest installed on system
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13670> 13670
python3: missing standard library module 'pathlib'
timothy.t.orling@intel.com
timothy.t.orling@intel.com
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13681> 13681
testimage does not log qemu errors to main console; only says do_testimage: runqemu exited with code 1
timothy.t.orling@intel.com
timothy.t.orling@intel.com
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13690> 13690
runqemu with slirp, forwarded host ports are not available on host
timothy.t.orling@intel.com
timothy.t.orling@intel.com
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13705> 13705
master] bitbake and hashserve.sock left behind when ^C a build
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13706> 13706
dnf parslogs failure (mips/systemd)
randy.macleod@windriver.com
unassigned@yoctoproject.org
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13709> 13709
Buildhistory race when building sdk and eSDK in parallel
randy.macleod@windriver.com
newcomer@yoctoproject.org
3.1 M3
3.1 M4
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13804> 13804
do_package_qa race generating warning
randy.macleod@windriver.com
newcomer@yoctoproject.org
3.1 M3
3.1 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: 32373 bytes --]
next reply other threads:[~2020-03-23 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 17:12 Stephen Jolley [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-22 20:50 M+ & H bugs with Milestone Movements WW12 Stephen Jolley
2022-03-22 0:02 sjolley.yp.pm
2023-03-28 0:33 sjolley.yp.pm
2024-03-25 20:52 Stephen K Jolley
2025-03-25 6:29 Stephen K Jolley
2026-03-24 14:04 Stephen K 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='0eac01d60136$3d9ba2c0$b8d2e840$@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.