Yocto Project Discussions
 help / color / mirror / Atom feed
From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW10
Date: Mon, 13 Mar 2023 15:40:08 -0700	[thread overview]
Message-ID: <0b7a01d955fc$c4793e60$4d6bbb20$@gmail.com> (raw)

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

All,

 

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

11781

bitbake --observe-only may get KeyError

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

11899

broken 'bitbake --status-only' and 'bitbake -m' for multiple connections

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

13424

devupstream doesn't work with mutilib

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

13599

Enhancement: Detect variables that shouldn't be defined in image scope, but in global (distro) scope

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

13808

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

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

14385

mode of sstate files created under pseudo

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

14620

QA error not seen when reusing SSTATE

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

14717

OEToolchainConfig.cmake sets wrong and unsuitable compiler flags

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

14811

Incorrect path matching in pseudo cause package failure in yocto

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

14870

Dangling bbappend behaviour can lead to unexpected surprises (error vs warn)

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.3 M1


 

14896

Current autobuilder code incompatible with buildbot 3.5.0

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

14918

Devtool fails if SRCREV is set to ${AUTOREV}

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

15010

native.bbclass is unable to clear unconditional overrides during dependency rewriting

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

4.2 M4


 

15008

'BitBakeXMLRPCServer' object has no attribute 'set_async_cmd'

richard.purdie@linuxfoundation.org

richard.purdie@linuxfoundation.org

4.2 M3

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: 37187 bytes --]

             reply	other threads:[~2023-03-13 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 22:40 sjolley.yp.pm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-10 15:10 M+ & H bugs with Milestone Movements WW10 Stephen K Jolley
2024-03-11 22:34 Stephen K Jolley
2022-10-11  6:42 sjolley.yp.pm
2022-03-08 16:25 sjolley.yp.pm
2021-03-08 16:23 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='0b7a01d955fc$c4793e60$4d6bbb20$@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