All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>
Subject: M+ & H bugs with Milestone Movements WW44
Date: Mon, 2 Nov 2020 14:37:38 -0800	[thread overview]
Message-ID: <132601d6b168$c4ebc830$4ec35890$@gmail.com> (raw)

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

All,

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

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

Global DNS fallback mechanism not present in poky distro

kai.kang@windriver.com

kai.kang@windriver.com

3.2 M4

3.3 M1


 

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

nobody group added by systemd sysusers.d

randy.macleod@windriver.com

yi.zhao@windriver.com

3.3

3.3 M1


 

	 

yi.zhao@windriver.com

yi.zhao@windriver.com

3.2 M4

3.3


 

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

rpmbuild: Can not build packages on qemu target

hongxu.jia@windriver.com

hongxu.jia@windriver.com

3.2 M4

3.3 M3


 

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

enhance manifest not found warning

kai.kang@windriver.com

kai.kang@windriver.com

3.2 M4

3.3 M2


 

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

lib32-core-image-sato -ctestimage failed due to wrong package names

kai.kang@windriver.com

kai.kang@windriver.com

3.2 M4

3.3 M1


 

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

Warnings from nightly-multilib builds (build-deps)

kai.kang@windriver.com

kai.kang@windriver.com

3.2 M4

3.3 M1


 

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

Meson detects googletest installed on system

randy.macleod@windriver.com

hongxu.jia@windriver.com

3.3 M4

3.3 M2


 

	 

hongxu.jia@windriver.com

hongxu.jia@windriver.com

3.2 M4

3.3 M4


 

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

core-image-full-cmdline qemumips systemd boot failure

kai.kang@windriver.com

kai.kang@windriver.com

3.2 M4

3.3 M2


 

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

quilt ptest intermittent failure

randy.macleod@windriver.com

joe.slater@windriver.com

3.3

3.3 M2


 

	 

joe.slater@windriver.com

joe.slater@windriver.com

3.2 M4

3.3


 

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

environment-setup script in multilib eSDK doesn't work for multilib variant

liezhi.yang@windriver.com

liezhi.yang@windriver.com

3.2 M4

3.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: 33664 bytes --]

             reply	other threads:[~2020-11-02 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 22:37 Stephen Jolley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-01 20:45 M+ & H bugs with Milestone Movements WW44 sjolley.yp.pm
2022-10-31 21:24 sjolley.yp.pm
2023-11-06 12:06 Stephen K Jolley
2024-11-05  6:10 Stephen K Jolley
2025-11-04  6:50 Stephen K 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='132601d6b168$c4ebc830$4ec35890$@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.