Date   

What .c/.h etc files were used to compile?

FLoraVLogs <eripflo@...>
 

Hi,

Is there a way to find out what .c/.h files were used to compile?

I am baking and tried using -D --no-setscene options and piped data into the file but don't see the .c/.h that were used to compile.

Regards,

Ripu


Yocto Project Status WW12'20

Stephen Jolley
 

Current Dev Position: YP 3.1 M4 - Stabilization

Next Deadline: YP 3.1 M4 build date  3/30/2020

 

Next Team Meetings:

 

Key Status/Updates:

  • M3 is through QA and due to be released.
  • The first M4 rc candidate is due to be built on Monday.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We’ve uncovered significant issues with the datastore connector approach in tinfoil. There is a proposed fix which effectively rewrites it which is not something undertaken lightly at this point in release but reluctantly, is probably necessary.
  • The focus is now on stabilizing and bug fixing for the final release

 

YP 3.1 Milestone Dates:

  • YP 3.1 M3 being reviewed for release
  • YP 3.1 M4 build date  3/30/2020
  • YP 3.1 M4 release date  4/24/2020

 

Planned upcoming dot releases:

  • YP 3.0.3 build date  5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date  5/18/2020
  • YP 2.7.4 release date 5/29/2020

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Building FIT images with different initramfs images

Stefano Babic
 

Hi Vladimir,

On 24.03.20 11:00, Vladimir Motyka wrote:
Hello,

I want to ask if there is some best practice or recommendation on how to build multiple FIT images with different initramfs image. We need more FIT images with a different set of packages to support different use cases(development image, production test image, etc.).

As the INITRAMFS_IMAGE variable is set in the machine configuration, we defined more machines with different INITRAMFS_IMAGE value. I think this is abusing of machine configuration.

I found a similar question here on the mailing list (https://www.yoctoproject.org/pipermail/yocto/2017-August/037676.html), where Christian describes his solution - adjusting kernel.bbclass and kernel-fitimage.bbclass and creating a new variable INITRAMFS_IMAGES. However, it wasn't integrated into YP.

To summarize, is there a better/recommended solution for building multiple FIT images with different initramfs image, then abusing the MACHINE configuration, or adjusting kernel.bbclass and kernel-fitimage.bbclass by myself?
I do not know if there is a best practise - but I do not like to extend
kernel classes as described above. IMHO the ramdisk does not belong to
MACHINE. I can build several images, and I would like that some of them
are put into a fit container. The kernel-fitimage class fits a very
common use case and generates the .its file (the description of fitIMage
used by mkimage), too, but it cannot fit all possible use cases: I have
often to put into a fitImage other components, like FPGA bitstreams,
splash images, multiple DTs and further configuration.

I see and I use fitImage as a container for an image class, that means
not bound to MACHINE. So in my image recipe (where I generate the
Ramdisk), I add a task that uses a fetched "its" file to generate the
resulting fitImage.

Somethink like:


SRC_URI = " my-fit.its"

do_prepareitb() {
< further compression, and so on>

mkimage -f ${WORKDIR}/my-fit.its ${WORKDIR}/${PN}-${MACHINE}.itb

}

addtask prepareitb before do_build after do_image_complete

Maybe someone else has solved in a different way..

Best regards,
Stefano Babic




--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@...
=====================================================================


Adding library headers in SDK (libsdnfile)

Guy Morand <guy@...>
 

Hi everyone,

I'm trying to add the libsdnfile development library in my SDK. I added a packagegroup-core-standalone-sdk-target.bbappend file in my meta-layer with the following:

RDEPENDS_${PN} += " \
  libsndfile-dev \
  "

Unfurtnately this fails:

ERROR: Nothing RPROVIDES 'libsndfile-dev'

It works when using libsndfile1-dev but I don't have the .pc file neither the headers in my SDK. Extracting the resulted ipk, it seems that the libsndfile-dev_1.0.28-r0.2_ARCH.ipk is the package I need but I can't get it installed!

I have the same issue with alsa library. Other packages work great using this approach.

Any pointers?

Best regards,

Guy Morand


Building FIT images with different initramfs images

Vladimir Motyka
 

Hello,

I want to ask if there is some best practice or recommendation on how to build multiple FIT images with different initramfs image. We need more FIT images with a different set of packages to support different use cases(development image, production test image, etc.).

As the INITRAMFS_IMAGE variable is set in the machine configuration, we defined more machines with different INITRAMFS_IMAGE value. I think this is abusing of machine configuration.

I found a similar question here on the mailing list (https://www.yoctoproject.org/pipermail/yocto/2017-August/037676.html), where Christian describes his solution - adjusting kernel.bbclass and kernel-fitimage.bbclass and creating a new variable INITRAMFS_IMAGES. However, it wasn't integrated into YP.

To summarize, is there a better/recommended solution for building multiple FIT images with different initramfs image, then abusing the MACHINE configuration, or adjusting kernel.bbclass and kernel-fitimage.bbclass by myself?

Thank You and Best Regards,
Vlado Motyka

Confidentiality Notice: This e-mail is privileged and confidential and for the use of the addressee only. Should you have received this e-mail in error please notify us by replying directly to the sender or by sending a message to info@.... Unauthorised dissemination, disclosure or copying of the contents of this e-mail, or any similar action, is prohibited.


Re: "Yocto Project Linux Kernel Development Manual" is gone

Nicolas Dechesne
 

thanks Vineela

On Tue, Mar 24, 2020 at 2:36 AM Tummalapalli, Vineela <vineela.tummalapalli@...> wrote:

Hello,

 

During the release process, I update the docs for the release in old.yoctoproject.org and publish those.

For 3.0.2 looks like “yocto project kernel development” manual was not added and “yocto project development tasks” manual was added twice. Sorry. I corrected it now.

In old.yoctoproject.org, I did add “”yocto project kernel development “Manual and deleted the duplicate “Development tasks Manual” entry.

 

I see it being added properly in https://old.yoctoproject.org/documentation but I see it is not yet updated in https://www.yoctoproject.org/docs/

Does it take some time to update https://www.yoctoproject.org/docs/


it looks good on the website now.

 

Thanks,

Vineela

 

From: yocto@... <yocto@...> On Behalf Of Nicolas Dechesne
Sent: Monday, March 23, 2020 12:38 AM
To: Vasyl Vavrychuk <vvavrychuk@...>
Cc: yocto@...
Subject: Re: [yocto] "Yocto Project Linux Kernel Development Manual" is gone

 

hi,

 

thanks for reporting, you're right.. and the Development tasks manual entry is listed twice.. We will investigate and fix that!

 

cheers

 

 

On Sun, Mar 22, 2020 at 11:57 PM Vasyl Vavrychuk <vvavrychuk@...> wrote:

Latest "Docs Overview" webpage https://www.yoctoproject.org/docs/ has no link to "Yocto Project Linux Kernel Development Manual".

Instead it shows link to "Yocto Project Development Tasks Manual" two times.

 


Re: "Yocto Project Linux Kernel Development Manual" is gone

Vineela
 

Hello,

 

During the release process, I update the docs for the release in old.yoctoproject.org and publish those.

For 3.0.2 looks like “yocto project kernel development” manual was not added and “yocto project development tasks” manual was added twice. Sorry. I corrected it now.

In old.yoctoproject.org, I did add “”yocto project kernel development “Manual and deleted the duplicate “Development tasks Manual” entry.

 

I see it being added properly in https://old.yoctoproject.org/documentation but I see it is not yet updated in https://www.yoctoproject.org/docs/

Does it take some time to update https://www.yoctoproject.org/docs/

 

Thanks,

Vineela

 

From: yocto@... <yocto@...> On Behalf Of Nicolas Dechesne
Sent: Monday, March 23, 2020 12:38 AM
To: Vasyl Vavrychuk <vvavrychuk@...>
Cc: yocto@...
Subject: Re: [yocto] "Yocto Project Linux Kernel Development Manual" is gone

 

hi,

 

thanks for reporting, you're right.. and the Development tasks manual entry is listed twice.. We will investigate and fix that!

 

cheers

 

 

On Sun, Mar 22, 2020 at 11:57 PM Vasyl Vavrychuk <vvavrychuk@...> wrote:

Latest "Docs Overview" webpage https://www.yoctoproject.org/docs/ has no link to "Yocto Project Linux Kernel Development Manual".

Instead it shows link to "Yocto Project Development Tasks Manual" two times.

 


[yocto-autobuilder-helper][PATCH 2/2] setup-config: Add multiconfig setup support

Aaron Chan
 

From: Aaron Chan <aaron.chun.yew.chan@...>

Signed-off-by: Aaron Chan <aaron.chun.yew.chan@...>
---
scripts/setup-config | 17 +++++++++++++++++
1 file changed, 17 insertions(+)

diff --git a/scripts/setup-config b/scripts/setup-config
index 3c8862a..c006297 100755
--- a/scripts/setup-config
+++ b/scripts/setup-config
@@ -9,6 +9,7 @@ import sys
import subprocess
import errno
import copy
+import re

import utils

@@ -119,3 +120,19 @@ with open(sdkextraconf, "w") as f:
print(" " + v)
f.write(v + "\n")

+# Add multiconfig setup support
+multivars=utils.getconfigexpr("multi-(.*)", ourconfig, args.target, stepnum)
+if multivars:
+ for conf in multivars:
+ mvars=utils.getconfiglistfilter(conf, ourconfig, args.target, stepnum)
+ m=re.search("multi-(.*)", conf)
+ mpath=os.path.join(args.builddir, "conf", "multiconfig")
+ mfile=os.path.join(mpath, "%s.conf" % m.group(1))
+ os.makedirs(mpath, exist_ok=True)
+ if os.path.exists(mfile):
+ os.remove(mfile)
+ utils.printheader("Writing %s with contents:" % mfile)
+ with open(mfile, 'w') as f:
+ for v in mvars:
+ print(" " + v)
+ f.write(v + "\n")
--
2.21.0.windows.1


[yocto-autobuilder-helper][PATCH 1/2] utils: Add getconfiglistfilter() to return config based on regexpr

Aaron Chan
 

From: Aaron Chan <aaron.chun.yew.chan@...>

Signed-off-by: Aaron Chan <aaron.chun.yew.chan@...>
---
scripts/utils.py | 10 ++++++++++
1 file changed, 10 insertions(+)

diff --git a/scripts/utils.py b/scripts/utils.py
index 68652d9..204360d 100644
--- a/scripts/utils.py
+++ b/scripts/utils.py
@@ -119,6 +119,16 @@ def getconfiglistfilter(name, config, target, stepnum):
merge(ret, config['defaults'][name])
return expandresult(ret, config)

+# Return a list of configuration keys based on regular expressions
+def getconfigexpr(name, config, target, stepnum):
+ ret = []
+ step = "step" + str(stepnum)
+ if target in config['overrides'] and step in config['overrides'][target]:
+ for i in config['overrides'][target][step].keys():
+ if re.search(name, i):
+ ret.append(i)
+ return ret
+
#
# Expand 'templates' with the configuration
#
--
2.21.0.windows.1


Re: yocto on tinkerbaord using meta-rockchip

Karthik Poduval
 

Thanks for the tip Joshua,

Like you suggested it was power supply related, I am able to boot the
board now with a 3A power supply.

Hi Tever,

Yes I have my console connected to UART2 and it seems to work fine for
the yocto build. For the tinkerOS image neither UART1 or UART2 had a
console output but the board booted successfully over HDMI (I didn't
test it any further).

Appreciate all the help everyone.

--
Regards,
Karthik Poduval

On Mon, Mar 23, 2020 at 2:48 PM Michael Nazzareno Trimarchi
<michael@...> wrote:

Hi

On Mon, Mar 23, 2020 at 10:45 PM Trevor Woerner <twoerner@...> wrote:

On Mon 2020-03-23 @ 10:31:05 PM, Michael Nazzareno Trimarchi wrote:
What about the status of qt layer using panfrost? and mainline
Thanks to JPEW, mesa with panfrost is enabled/working with relevant boards.
I've tested it, running, on both the rock-pi-4 and tinkerboard (so it *should*
be working with your vyasa-rk3288 board too, although I haven't run-tested it
lately). Therefore most anything sitting on top of mesa *should* work.

Of course... the panfrost project is a "work-in-progress", so there are
probably some cases that might not work.
Technically I can include meta-qt and build on top of mesa using
wayland and some
mainline kernel. I'm working right now on tinker-s board and figure
out to move legacy
project on mainline solution. I will try to compile it and give a try

Michael


Best regards,
Trevor


--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


--
Regards,
Karthik Poduval


Re: yocto on tinkerbaord using meta-rockchip

Michael Nazzareno Trimarchi
 

Hi

On Mon, Mar 23, 2020 at 10:45 PM Trevor Woerner <twoerner@...> wrote:

On Mon 2020-03-23 @ 10:31:05 PM, Michael Nazzareno Trimarchi wrote:
What about the status of qt layer using panfrost? and mainline
Thanks to JPEW, mesa with panfrost is enabled/working with relevant boards.
I've tested it, running, on both the rock-pi-4 and tinkerboard (so it *should*
be working with your vyasa-rk3288 board too, although I haven't run-tested it
lately). Therefore most anything sitting on top of mesa *should* work.

Of course... the panfrost project is a "work-in-progress", so there are
probably some cases that might not work.
Technically I can include meta-qt and build on top of mesa using
wayland and some
mainline kernel. I'm working right now on tinker-s board and figure
out to move legacy
project on mainline solution. I will try to compile it and give a try

Michael


Best regards,
Trevor


--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


Re: yocto on tinkerbaord using meta-rockchip

Trevor Woerner
 

On Mon 2020-03-23 @ 10:31:05 PM, Michael Nazzareno Trimarchi wrote:
What about the status of qt layer using panfrost? and mainline
Thanks to JPEW, mesa with panfrost is enabled/working with relevant boards.
I've tested it, running, on both the rock-pi-4 and tinkerboard (so it *should*
be working with your vyasa-rk3288 board too, although I haven't run-tested it
lately). Therefore most anything sitting on top of mesa *should* work.

Of course... the panfrost project is a "work-in-progress", so there are
probably some cases that might not work.

Best regards,
Trevor


Re: yocto on tinkerbaord using meta-rockchip

Michael Nazzareno Trimarchi
 

Hi all

On Mon, Mar 23, 2020 at 7:15 PM Sergey Bostandzhyan <jin@...> wrote:

Hi everyone,

On Mon, Mar 23, 2020 at 01:59:11PM -0400, Trevor Woerner wrote:
Testing a different image was a good idea, and the fact it didn't work
either suggests it might possibly be hardware related. To me this
suggests, perhaps, a power supply issue (i.e. the fact it boots up
partway then stops). Can you try with other sources of power?
this is indeed a good suggestion, I ran into such an issue myself, actually
had it with Armbian and was pointed here by the Armbian devs:

https://forum.armbian.com/topic/4767-powering-through-micro-usb

Apparently even picking a different USB cable can make a difference.

What I observed was that LEDs went off at some point during kernel
startup and the board went dead. After being pointed to the above link I
tried a much stronger USB power suppy (from an Acer netbook) and then
it suddenly worked without any modifications to the software.

Also, although the Tinkerboard has the same pin layout as the
Raspberry Pi, unlike the Raspberry Pi the Rockchip people like to use
UART2 for the console rather than UART1. Is your console cable
connected to UART2 (pins 32 and 33)?

https://tinkerboarding.co.uk/wiki/index.php/GPIO
I have a tinker-board-s, I am using it with meta-rockhip and I can confirm that
it works for me (also using UART2 on the pins described by Trevor), so the
layer as such should work...
What about the status of qt layer using panfrost? and mainline

Michael

Kind regards,
Jin


--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |


Re: yocto on tinkerbaord using meta-rockchip

Sergey Bostandzhyan
 

Hi everyone,

On Mon, Mar 23, 2020 at 01:59:11PM -0400, Trevor Woerner wrote:
Testing a different image was a good idea, and the fact it didn't work
either suggests it might possibly be hardware related. To me this
suggests, perhaps, a power supply issue (i.e. the fact it boots up
partway then stops). Can you try with other sources of power?
this is indeed a good suggestion, I ran into such an issue myself, actually
had it with Armbian and was pointed here by the Armbian devs:

https://forum.armbian.com/topic/4767-powering-through-micro-usb

Apparently even picking a different USB cable can make a difference.

What I observed was that LEDs went off at some point during kernel
startup and the board went dead. After being pointed to the above link I
tried a much stronger USB power suppy (from an Acer netbook) and then
it suddenly worked without any modifications to the software.

Also, although the Tinkerboard has the same pin layout as the
Raspberry Pi, unlike the Raspberry Pi the Rockchip people like to use
UART2 for the console rather than UART1. Is your console cable
connected to UART2 (pins 32 and 33)?

https://tinkerboarding.co.uk/wiki/index.php/GPIO
I have a tinker-board-s, I am using it with meta-rockhip and I can confirm that
it works for me (also using UART2 on the pins described by Trevor), so the
layer as such should work...

Kind regards,
Jin


Re: yocto on tinkerbaord using meta-rockchip

Trevor Woerner
 

On Sat, Mar 21, 2020 at 3:09 AM karthik poduval
<karthik.poduval@...> wrote:
Thanks for getting back, I tried with tinker-board-s machine type but same result. I also tried flashing Asus Debian image on sdcard but that too didn't work (no console logs with this image). I am suspecting it's a hardware issue at this point. Any other suggestions or insights would be appreciated.
Testing a different image was a good idea, and the fact it didn't work
either suggests it might possibly be hardware related. To me this
suggests, perhaps, a power supply issue (i.e. the fact it boots up
partway then stops). Can you try with other sources of power?

Also, although the Tinkerboard has the same pin layout as the
Raspberry Pi, unlike the Raspberry Pi the Rockchip people like to use
UART2 for the console rather than UART1. Is your console cable
connected to UART2 (pins 32 and 33)?

https://tinkerboarding.co.uk/wiki/index.php/GPIO


M+ & H bugs with Milestone Movements WW12

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

13181

persist_data sqlite database mixed with forking is irreparably broken

randy.macleod@...

unassigned@...

3.1 M3

3.1 M4

 

13319

Add SPDX license headers to all source files for matchbox/sato

randy.macleod@...

matthew.zeng@...

3.1 M3

3.1 M4

 

13411

ptest-perl.bbclass run-ptest is too greedy for SKIP

timothy.t.orling@...

timothy.t.orling@...

3.1 M3

3.1 M4

 

13425

Add bblock and bbunlock helper tools

randy.macleod@...

newcomer@...

3.1 M3

3.1 M4

 

13508

Meson detects googletest installed on system

randy.macleod@...

unassigned@...

3.1 M3

3.1 M4

 

13670

python3: missing standard library module 'pathlib'

timothy.t.orling@...

timothy.t.orling@...

3.1 M3

3.1 M4

 

13681

testimage does not log qemu errors to main console; only says do_testimage: runqemu exited with code 1

timothy.t.orling@...

timothy.t.orling@...

3.1 M3

3.1 M4

 

13690

runqemu with slirp, forwarded host ports are not available on host

timothy.t.orling@...

timothy.t.orling@...

3.1 M3

3.1 M4

 

13705

master] bitbake and hashserve.sock left behind when ^C a build

randy.macleod@...

unassigned@...

3.1 M3

3.1 M4

 

13706

dnf parslogs failure (mips/systemd)

randy.macleod@...

unassigned@...

3.1 M3

3.1 M4

 

13709

Buildhistory race when building sdk and eSDK in parallel

randy.macleod@...

newcomer@...

3.1 M3

3.1 M4

 

13804

do_package_qa race generating warning

randy.macleod@...

newcomer@...

3.1 M3

3.1 M4

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW12!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

ee.peng.yeoh@...

3

raj.khem@...

2

chee.yang.lee@...

2

kexin.hao@...

2

randy.macleod@...

2

mostthingsweb@...

1

JPEWhacker@...

1

jpuhlman@...

1

Grand Total

14

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current Top developers on Yocto Project 3.1

Stephen Jolley
 

All,

Below is the list as of top 50 developers as of the end of WW12 of who have open medium or higher bugs and enhancements against YP 3.1.   There are 23 possible work days left until the final release candidates for YP 3.1 needs to be released.

Who

Count

richard.purdie@...

34

liezhi.yang@...

27

david.reyna@...

25

bluelightning@...

14

akuster808@...

13

timothy.t.orling@...

12

bruce.ashfield@...

11

mark.morton@...

11

Qi.Chen@...

11

kai.kang@...

10

randy.macleod@...

10

ross@...

7

michael@...

6

jon.mason@...

5

trevor.gamblin@...

5

changqing.li@...

5

hongxu.jia@...

4

pbarker@...

4

srifenbark@...

4

alejandro@...

4

mingli.yu@...

4

yang.wang@...

3

kexin.hao@...

3

alex.kanavin@...

3

anuj.mittal@...

2

seebs@...

2

ycnakajsph@...

2

mark.hatle@...

2

kergoth@...

2

matthew.zeng@...

2

raj.khem@...

2

JPEWhacker@...

2

jaewon@...

2

chee.yang.lee@...

2

joe.slater@...

1

anon2313@...

1

yi.zhao@...

1

maxime.roussinbelanger@...

1

jonathan.yong@...

1

mshah@...

1

ee.peng.yeoh@...

1

georgi.georgiev@...

1

denis@...

1

kai.ruhnau@...

1

zhe.he@...

1

bunk@...

1

scott.branden@...

1

amber.n.elliot@...

1

dl9pf@...

1

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 299 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then “3.2”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


[matchbox-desktop-2][PATCH] Add SPDX-License-Identifier: GPL-2.0-or-later

Matthew
 

Fixes [YOCTO #13319]

Signed-off-by: Mingde (Matthew) Zeng <matthew.zeng@...>
---
libtaku/inotify/inotify-diag.c | 2 ++
libtaku/inotify/inotify-diag.h | 2 ++
libtaku/inotify/inotify-kernel.c | 2 ++
libtaku/inotify/inotify-kernel.h | 2 ++
libtaku/inotify/inotify-missing.c | 2 ++
libtaku/inotify/inotify-missing.h | 2 ++
libtaku/inotify/inotify-path.c | 2 ++
libtaku/inotify/inotify-path.h | 2 ++
libtaku/inotify/inotify-sub.c | 2 ++
libtaku/inotify/inotify-sub.h | 2 ++
libtaku/launcher-util.c | 2 ++
libtaku/launcher-util.h | 2 ++
libtaku/taku-icon-tile.c | 2 ++
libtaku/taku-icon-tile.h | 2 ++
libtaku/taku-launcher-tile.c | 2 ++
libtaku/taku-launcher-tile.h | 2 ++
libtaku/taku-menu-desktop.c | 2 ++
libtaku/taku-menu.h | 2 ++
libtaku/taku-queue-source.c | 2 ++
libtaku/taku-queue-source.h | 2 ++
libtaku/taku-tile.c | 2 ++
libtaku/taku-tile.h | 2 ++
libtaku/xutil.c | 2 ++
libtaku/xutil.h | 2 ++
src/desktop.c | 2 ++
src/desktop.h | 2 ++
src/main.c | 2 ++
src/taku-category-bar.c | 2 ++
src/taku-category-bar.h | 2 ++
29 files changed, 58 insertions(+)

diff --git a/libtaku/inotify/inotify-diag.c b/libtaku/inotify/inotify-diag.c
index 937ebd7..95aa725 100644
--- a/libtaku/inotify/inotify-diag.c
+++ b/libtaku/inotify/inotify-diag.c
@@ -4,6 +4,8 @@

Copyright (C) 2005 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-diag.h b/libtaku/inotify/inotify-diag.h
index f818f16..f74fca6 100644
--- a/libtaku/inotify/inotify-diag.h
+++ b/libtaku/inotify/inotify-diag.h
@@ -2,6 +2,8 @@

Copyright (C) 2006 John McCutchan <john@...>

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-kernel.c b/libtaku/inotify/inotify-kernel.c
index 9cce03d..4969f53 100644
--- a/libtaku/inotify/inotify-kernel.c
+++ b/libtaku/inotify/inotify-kernel.c
@@ -1,6 +1,8 @@
/*
Copyright (C) 2005 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-kernel.h b/libtaku/inotify/inotify-kernel.h
index b406d71..490fca3 100644
--- a/libtaku/inotify/inotify-kernel.h
+++ b/libtaku/inotify/inotify-kernel.h
@@ -1,6 +1,8 @@
/*
Copyright (C) 2005 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-missing.c b/libtaku/inotify/inotify-missing.c
index 96126b3..40d81b0 100644
--- a/libtaku/inotify/inotify-missing.c
+++ b/libtaku/inotify/inotify-missing.c
@@ -4,6 +4,8 @@

Copyright (C) 2005 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-missing.h b/libtaku/inotify/inotify-missing.h
index b67b595..af4a4bb 100644
--- a/libtaku/inotify/inotify-missing.h
+++ b/libtaku/inotify/inotify-missing.h
@@ -2,6 +2,8 @@

Copyright (C) 2006 John McCutchan <john@...>

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-path.c b/libtaku/inotify/inotify-path.c
index c5cfbb8..4a57609 100644
--- a/libtaku/inotify/inotify-path.c
+++ b/libtaku/inotify/inotify-path.c
@@ -4,6 +4,8 @@

Copyright (C) 2006 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-path.h b/libtaku/inotify/inotify-path.h
index c613b9f..9645935 100644
--- a/libtaku/inotify/inotify-path.h
+++ b/libtaku/inotify/inotify-path.h
@@ -1,6 +1,8 @@
/*
Copyright (C) 2005 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-sub.c b/libtaku/inotify/inotify-sub.c
index 404dc20..04be968 100644
--- a/libtaku/inotify/inotify-sub.c
+++ b/libtaku/inotify/inotify-sub.c
@@ -4,6 +4,8 @@

Copyright (C) 2006 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/inotify/inotify-sub.h b/libtaku/inotify/inotify-sub.h
index 36561e7..697c633 100644
--- a/libtaku/inotify/inotify-sub.h
+++ b/libtaku/inotify/inotify-sub.h
@@ -2,6 +2,8 @@

Copyright (C) 2006 John McCutchan

+ SPDX-License-Identifier: GPL-2.0-or-later
+
The Gnome Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public License as
published by the Free Software Foundation; either version 2 of the
diff --git a/libtaku/launcher-util.c b/libtaku/launcher-util.c
index 89333f9..8a36838 100644
--- a/libtaku/launcher-util.c
+++ b/libtaku/launcher-util.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/launcher-util.h b/libtaku/launcher-util.h
index d059d84..d6cb256 100644
--- a/libtaku/launcher-util.h
+++ b/libtaku/launcher-util.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-icon-tile.c b/libtaku/taku-icon-tile.c
index 110db6b..d62636d 100644
--- a/libtaku/taku-icon-tile.c
+++ b/libtaku/taku-icon-tile.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-icon-tile.h b/libtaku/taku-icon-tile.h
index 4475ca4..ad98e20 100644
--- a/libtaku/taku-icon-tile.h
+++ b/libtaku/taku-icon-tile.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-launcher-tile.c b/libtaku/taku-launcher-tile.c
index e7f58f3..0025983 100644
--- a/libtaku/taku-launcher-tile.c
+++ b/libtaku/taku-launcher-tile.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-launcher-tile.h b/libtaku/taku-launcher-tile.h
index c1b8cf9..9b13107 100644
--- a/libtaku/taku-launcher-tile.h
+++ b/libtaku/taku-launcher-tile.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-menu-desktop.c b/libtaku/taku-menu-desktop.c
index 93c8a56..8ca8d00 100644
--- a/libtaku/taku-menu-desktop.c
+++ b/libtaku/taku-menu-desktop.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-menu.h b/libtaku/taku-menu.h
index 9f78064..6d4d5c4 100644
--- a/libtaku/taku-menu.h
+++ b/libtaku/taku-menu.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-queue-source.c b/libtaku/taku-queue-source.c
index d17be14..1d743ab 100644
--- a/libtaku/taku-queue-source.c
+++ b/libtaku/taku-queue-source.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-queue-source.h b/libtaku/taku-queue-source.h
index 00ad959..26b14c4 100644
--- a/libtaku/taku-queue-source.h
+++ b/libtaku/taku-queue-source.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-tile.c b/libtaku/taku-tile.c
index 64dd3d7..3d43bda 100644
--- a/libtaku/taku-tile.c
+++ b/libtaku/taku-tile.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/taku-tile.h b/libtaku/taku-tile.h
index 5c03089..1299e61 100644
--- a/libtaku/taku-tile.h
+++ b/libtaku/taku-tile.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/xutil.c b/libtaku/xutil.c
index 3cd36bb..184d06d 100644
--- a/libtaku/xutil.c
+++ b/libtaku/xutil.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/libtaku/xutil.h b/libtaku/xutil.h
index 9ecb805..0b0685d 100644
--- a/libtaku/xutil.h
+++ b/libtaku/xutil.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/src/desktop.c b/src/desktop.c
index a1943eb..e37c8c1 100644
--- a/src/desktop.c
+++ b/src/desktop.c
@@ -2,6 +2,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/src/desktop.h b/src/desktop.h
index 5c6900b..d938870 100644
--- a/src/desktop.h
+++ b/src/desktop.h
@@ -2,6 +2,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/src/main.c b/src/main.c
index b2794c4..53a3b0d 100644
--- a/src/main.c
+++ b/src/main.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/src/taku-category-bar.c b/src/taku-category-bar.c
index 5900d54..9b77f8b 100644
--- a/src/taku-category-bar.c
+++ b/src/taku-category-bar.c
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
diff --git a/src/taku-category-bar.h b/src/taku-category-bar.h
index ff93e86..1885abe 100644
--- a/src/taku-category-bar.h
+++ b/src/taku-category-bar.h
@@ -1,6 +1,8 @@
/*
* Copyright (C) 2007 OpenedHand Ltd
*
+ * SPDX-License-Identifier: GPL-2.0-or-later
+ *
* This program is free software; you can redistribute it and/or modify it under
* the terms of the GNU General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option) any later
--
Mingde (Matthew) Zeng

8881 - 8900 of 57789