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 WW21
Date: Mon, 29 May 2023 17:24:10 -0700	[thread overview]
Message-ID: <07ee01d9928d$0e5d2650$2b1772f0$@gmail.com> (raw)

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

All,

YP M+ or high bugs which moved to a new milestone in WW21


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


High

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

cmake-native fails to prepend c++ compiler after pulling the newest kirkstone/master with gcc13 on host

randy.macleod@windriver.com

richard.purdie@linuxfoundation.org

0.0.0

4.3 M1


Medium+

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

packaging debugsrc breaks for recipes with externalsrc and debug-with-srcpkg

randy.macleod@windriver.com

pavel@zhukoff.net

4.0.10

4.0.11

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

file_5.41.bb:do_configure error with GCC 11.3.0 from SDK 4.0.3

randy.macleod@windriver.com

pavel@zhukoff.net

4.0.10

4.0.12

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

AB-INT: gcc 12.3.1 segfault while building ccache

randy.macleod@windriver.com

Yash.Shinde@windriver.com

0.0.0

4.3 M2

are listed below: 

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

             reply	other threads:[~2023-05-30  0:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  0:24 sjolley.yp.pm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-27  6:57 M+ & H bugs with Milestone Movements WW21 Stephen K Jolley
2024-05-28  5:39 Stephen K Jolley
2021-05-25  2:40 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='07ee01d9928d$0e5d2650$2b1772f0$@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.