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 WW28
Date: Mon, 13 Jul 2020 15:14:11 -0700	[thread overview]
Message-ID: <03cc01d65962$efb79020$cf26b060$@gmail.com> (raw)

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

All,

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


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

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

nobody group added by systemd sysusers.d

yi.zhao@windriver.com

yi.zhao@windriver.com

3.2 M1

3.2 M2


 

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

Consistent naming scheme for deployed artifacts

randy.macleod@windriver.com

Martin.Jansa@gmail.com

3.2 M1

3.2 M2


 

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

nativesdk-opkg prefixes all internal paths with $SDKPATH and won't work

randy.macleod@windriver.com

unassigned@yoctoproject.org

3.2 M1

3.2 M2


 

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

How to run our test suites for boards like beaglebone remotely on a LAVA
board farm?

randy.macleod@windriver.com

limon.anibal@gmail.com

3.2 M1

3.99


 

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

Multiconfig builds may try to execute events that don't exist for them

randy.macleod@windriver.com

alejandro@enedino.org

3.2 M1

3.2 M2


 

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

ttm_bo_vm_open kernel warning

randy.macleod@windriver.com

jon.mason@arm.com

3.2 M1

3.2 M2


 

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

Switch qemuarm (another others) to virtio graphics

randy.macleod@windriver.com

jon.mason@arm.com

3.2 M1

3.2 M2


 

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

Determine 32bit guest support on arm64

randy.macleod@windriver.com

jon.mason@arm.com

3.2 M1

3.2 M2


 

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

Devtool finish on _git package with SRCPV in PV points to wrong WORKDIR

randy.macleod@windriver.com

jaewon@xilinx.com

3.2 M1

3.2 M2


 

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

Add SPDX license headers to all source files for layerindex-web

randy.macleod@windriver.com

amber.n.elliot@intel.com

3.2 M1

3.2 M2


 

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

Add SPDX license headers to all source files for prelink-cross

randy.macleod@windriver.com

newcomer@yoctoproject.org

3.2 M1

3.2 M2

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*    Cell:                (208) 244-4460

* Email:               <mailto:sjolley.yp.pm@gmail.com>
sjolley.yp.pm@gmail.com

 


[-- Attachment #2: Type: text/html, Size: 30071 bytes --]

             reply	other threads:[~2020-07-13 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 22:14 Stephen Jolley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-17 21:49 M+ & H bugs with Milestone Movements WW28 sjolley.yp.pm
2023-07-24 20:03 sjolley.yp.pm
2024-07-22 23:22 Stephen K Jolley
2025-07-14 23:52 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='03cc01d65962$efb79020$cf26b060$@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.