From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW22
Date: Mon, 31 May 2021 16:51:48 -0700 [thread overview]
Message-ID: <168d01d75677$ebe4b410$c3ae1c30$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2992 bytes --]
All,
YP M+ or high bugs which moved to a new milestone in WW22 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=12465> 12465
test case test_check_rpm_install_removal_log_file_size failed
randy.macleod@windriver.com
richard.purdie@linuxfoundation.org
3.99
3.4 M1
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13768> 13768
base-files do_package fatal error in subprocess
randy.macleod@windriver.com
mingli.yu@windriver.com
3.3 M4
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=13819> 13819
No clue when CONNECTIVITY_CHECK_URIS is unaccessible
randy.macleod@windriver.com
mingli.yu@windriver.com
3.3 M4
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14020> 14020
environment-setup script in multilib eSDK doesn't work for multilib variant
randy.macleod@windriver.com
liezhi.yang@windriver.com
3.3 M4
3.4 M1
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14047> 14047
eSDK: python3.5.real: No such file or directory
randy.macleod@windriver.com
bluelightning@bluelightning.org
3.3 M3
3.4 M1
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14060> 14060
devtool modify fails when applied on recipes using patches
randy.macleod@windriver.com
bluelightning@bluelightning.org
3.3 M3
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14100> 14100
SDKPATH should not reference SDK_VERSION
randy.macleod@windriver.com
ydirson@free.fr
3.3 M3
3.4 M1
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14120> 14120
pkg_postinst_ontarget_${PN}
randy.macleod@windriver.com
pokylinux@reliableembeddedsystems.com
3.3 M3
3.4 M1
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14146> 14146
Post-patch hook fails with submodules and PATCHTOOL=git and PATCH_COMMIT_FUNCTIONS=1
randy.macleod@windriver.com
bluelightning@bluelightning.org
3.3 M3
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14168> 14168
#new-recipe-makefile-based-package does not exist anymore
randy.macleod@windriver.com
michael.opdenacker@bootlin.com
3.3 M3
3.4 M2
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14192> 14192
gcc/kernel: crypto/aegis128-neon-inner.c can not be built anymore
randy.macleod@windriver.com
raj.khem@gmail.com
3.3 M3
3.4 M1
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=14254> 14254
oe-selftest-centos: gotoolchain.oeGoToolchainSelfTest.test_go_dep_build failed
randy.macleod@windriver.com
raj.khem@gmail.com
3.3 M3
3.4 M1
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: 32459 bytes --]
next reply other threads:[~2021-05-31 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 23:51 Stephen Jolley [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-03 4:48 M+ & H bugs with Milestone Movements WW22 Stephen K Jolley
2023-06-06 3:27 sjolley.yp.pm
2022-05-30 23:06 sjolley.yp.pm
2020-06-01 16:54 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='168d01d75677$ebe4b410$c3ae1c30$@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.