All of lore.kernel.org
 help / color / mirror / Atom feed
From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW45
Date: Mon, 7 Nov 2022 17:45:41 -0700	[thread overview]
Message-ID: <189c01d8f30b$6dd6c090$498441b0$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2723 bytes --]

All,

YP M+ or high bugs which moved to a new milestone in WW45 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


High

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14787> 14787

AB-INT: systemd.SystemdServiceTests.test_systemd_status failure

randy.macleod@windriver.com

ross.burton@arm.com

4.1 M4

4.2 M1


Medium+

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=10731> 10731

bitbake --observe-only doesn't work with memres

randy.macleod@windriver.com

pavel@zhukoff.net

4.2

4.2 M2


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=11781> 11781

bitbake --observe-only may get KeyError

randy.macleod@windriver.com

richard.purdie@linuxfoundation.org

4.1 M3

4.2 M1


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=11899> 11899

broken 'bitbake --status-only' and 'bitbake -m'

randy.macleod@windriver.com

richard.purdie@linuxfoundation.org

4.1 M3

4.2 M1


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=12937> 12937

Consistent naming scheme for deployed artifacts

randy.macleod@windriver.com

Martin.Jansa@gmail.com

4.1 M3

4.99


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=13808> 13808

do_task[noexec] = "" marks task noexec, which is inconsistent with docs

randy.macleod@windriver.com

richard.purdie@linuxfoundation.org

4.1

4.2 M1


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14045> 14045

git fetcher deadlock with self-referencing sub-modules

randy.macleod@windriver.com

richard.purdie@linuxfoundation.org

4.1 M4

4.2 M1


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14121> 14121

Implement sphinx switchers.js for bitbake

randy.macleod@windriver.com

michael.opdenacker@bootlin.com

4.1 M3

4.2 M1


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14717> 14717

OEToolchainConfig.cmake sets wrong and unsuitable compiler flags

randy.macleod@windriver.com

martin.beeger@online.de

4.1 M2

4.2 M1


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14745> 14745

cve-checker update to support NVD json 5.0 format

randy.macleod@windriver.com

akuster808@gmail.com

4.1 M3

4.2 M1


 

 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14905> 14905

Error in compiling rustfmt does not cause do_compile to fail

randy.macleod@windriver.com

Naveen.Gowda@windriver.com

4.1 M4

4.2 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: 30256 bytes --]

             reply	other threads:[~2022-11-08  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  0:45 sjolley.yp.pm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-11 14:57 M+ & H bugs with Milestone Movements WW45 Stephen K Jolley
2024-11-12  6:22 Stephen K Jolley
2023-11-13 11:27 Stephen K Jolley
2021-11-08 23:35 sjolley.yp.pm
2020-11-10  0:24 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='189c01d8f30b$6dd6c090$498441b0$@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 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.