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 WW16
Date: Mon, 24 Apr 2023 13:59:42 -0700	[thread overview]
Message-ID: <104d01d976ef$b1b1a150$1514e3f0$@gmail.com> (raw)

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

All,

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

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

native programs from RSS that alias hosttools can cause non-reproducible builds

randy.macleod@windriver.com

JPEWhacker@gmail.com

4.2

4.3

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

Buildtools tarball python performance degraded by reproducibile builds

randy.macleod@windriver.com

JPEWhacker@gmail.com

4.2

4.3

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

yocto-check-layer can fail if a layer adds new licenses

randy.macleod@windriver.com

JPEWhacker@gmail.com

4.2

4.3

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

Remove debug_domain logic

randy.macleod@windriver.com

JPEWhacker@gmail.com

4.2

4.3

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

[meta-mingw] nativesdk-openssl: Configure failed

randy.macleod@windriver.com

JPEWhacker@gmail.com

4.2

4.3

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

Using overrides on security flags may produce an incorrect meta-environment for the generated SDK

randy.macleod@windriver.com

mark.hatle@kernel.crashing.org

0.0.0

4.3 M2

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

patching path for cargo based recipe don't work with virtual manifest

randy.macleod@windriver.com

randy.macleod@windriver.com

0.0.0

4.3 M2

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

Move ptest doc to Testing manual

randy.macleod@windriver.com

michael.opdenacker@bootlin.com

0.0.0

4.3 M1

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

Add package specification for ptest (upstream test suite, ...)

randy.macleod@windriver.com

michael.opdenacker@bootlin.com

0.0.0

4.3 M1

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

python3targetconfig.bbclass: PYTHONPATH is overwritten instead of extended

randy.macleod@windriver.com

johannes.schrimpf@blueye.no

0.0.0

4.3 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: 23393 bytes --]

             reply	other threads:[~2023-04-24 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 20:59 sjolley.yp.pm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-21 14:54 M+ & H bugs with Milestone Movements WW16 Stephen K Jolley
2025-04-22  6:57 Stephen K Jolley
2024-04-23  5:14 Stephen K Jolley
2022-04-18 20:02 sjolley.yp.pm
2021-04-20  0:59 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='104d01d976ef$b1b1a150$1514e3f0$@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