Date   

Re: QA cycle report for 2.2.2 rc2

libertad
 

Ok, I will open a bug for QA to fix this ptest comparison issue, Bug 12094. I guess this ptest bug 12081 cannot be a blocker for the release.

Best Regards
Libertad G.

-----Original Message-----
From: Bystricky, Juro
Sent: Friday, September 15, 2017 3:14 PM
To: akuster808 <akuster808@gmail.com>; Cruz, Libertad <libertad.cruz@intel.com>; Richard Purdie <richard.purdie@linuxfoundation.org>; yocto@yoctoproject.org; Jolley, Stephen K <stephen.k.jolley@intel.com>; Zhang, Jessica <jessica.zhang@intel.com>
Cc: Cruz Alcaraz, Juan M <juan.m.cruz.alcaraz@intel.com>; Jordan, Robin L <robin.l.jordan@intel.com>
Subject: RE: [yocto] QA cycle report for 2.2.2 rc2

I checked out 2.2_M3 2679a347c576f5411fbe802d2f6201c94036ecb2.
The recipes for gzip and slang do not contain any ptest code, so that explains why the tests are missing.
However, flex recipe has a code for ptest. So there is a bit of mystery left.

________________________________________
From: akuster808 [akuster808@gmail.com]
Sent: Friday, September 15, 2017 1:06 PM
To: Bystricky, Juro; Cruz, Libertad; Richard Purdie; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica
Cc: Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: Re: [yocto] QA cycle report for 2.2.2 rc2

On 09/15/2017 01:01 PM, Bystricky, Juro wrote:
The commit is for 2.4 M3 (5f6945f5031e1a4ca116cc1eccf4c2f9dc228547)
2.4 does contain the ptests for gzip, slang and flex. (Although there
are some other mysteries, like sed-ptest is missing) It would seem that 2.2 had never contained (or lost a while ago) those ptests.
Thanks for looking into this. Is there any action I need to follow up on?


Re: QA cycle report for 2.2.2 rc2

Bystricky, Juro
 

I checked out 2.2_M3 2679a347c576f5411fbe802d2f6201c94036ecb2.
The recipes for gzip and slang do not contain any ptest code, so that explains why the tests are
missing.
However, flex recipe has a code for ptest. So there is a bit of mystery left.

________________________________________
From: akuster808 [akuster808@gmail.com]
Sent: Friday, September 15, 2017 1:06 PM
To: Bystricky, Juro; Cruz, Libertad; Richard Purdie; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica
Cc: Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: Re: [yocto] QA cycle report for 2.2.2 rc2

On 09/15/2017 01:01 PM, Bystricky, Juro wrote:
The commit is for 2.4 M3 (5f6945f5031e1a4ca116cc1eccf4c2f9dc228547)
2.4 does contain the ptests for gzip, slang and flex. (Although there are some other mysteries, like sed-ptest is missing)
It would seem that 2.2 had never contained (or lost a while ago) those ptests.
Thanks for looking into this. Is there any action I need to follow up on?


Re: QA cycle report for 2.2.2 rc2

Armin Kuster
 

On 09/15/2017 01:01 PM, Bystricky, Juro wrote:
The commit is for 2.4 M3 (5f6945f5031e1a4ca116cc1eccf4c2f9dc228547)
2.4 does contain the ptests for gzip, slang and flex. (Although there are some other mysteries, like sed-ptest is missing)
It would seem that 2.2 had never contained (or lost a while ago) those ptests.
Thanks for looking into this. Is there any action I need to follow up on?

- armin

Juro
________________________________________
From: Cruz, Libertad
Sent: Friday, September 15, 2017 12:50 PM
To: Bystricky, Juro; Richard Purdie; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica
Cc: Perez Carranza, Jose; Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: RE: QA cycle report for 2.2.2 rc2

Hello,


Regarding 12080: this was a QA documentation error on the test steps, verified it again and changed the bug to not a bug, documented the correct steps for the QA.

Regarding 12081: To open bugs on ptest we make a comparison from the last run in this case the comparison was made with 2.2.2 rc1 Ptest 5f6945f5031e1a4ca116cc1eccf4c2f9dc228547 which in turn was compared with Ptest 9ed748a542b520c1cb763d981969233c0f5efd4e which was compared with Ptest 8e15e9b6e478f6368034519b2a8fd3c7ea71d23b which was compared with Ptest 6bd890d9e011014cf323e61267f8b256949d44aa, they all hold this packages.




Best Regards
Libertad G.

-----Original Message-----
From: Bystricky, Juro
Sent: Friday, September 15, 2017 1:04 PM
To: Richard Purdie <richard.purdie@linuxfoundation.org>; Cruz, Libertad <libertad.cruz@intel.com>; yocto@yoctoproject.org; Jolley, Stephen K <stephen.k.jolley@intel.com>; Zhang, Jessica <jessica.zhang@intel.com>
Cc: Perez Carranza, Jose <jose.perez.carranza@intel.com>; Cruz Alcaraz, Juan M <juan.m.cruz.alcaraz@intel.com>; Jordan, Robin L <robin.l.jordan@intel.com>
Subject: RE: QA cycle report for 2.2.2 rc2


Regarding 12081:
Looking at some previous ptest results in:
https://wiki.yoctoproject.org/wiki/QA_sanity_history
we can see that the offending tests (gzip, flex, slang) were not present in:
https://wiki.yoctoproject.org/wiki/Ptest_62d7d4130202d8ede16abf9e7d779361ca70847e
but started to appear after
https://wiki.yoctoproject.org/wiki/Ptest_6e20b31d5d17133e0fca086e12a0ad06ab5c4cc8 (flex)

Also checking the manifest file, the offending test were also missing in http://downloads.yoctoproject.org/releases/yocto/yocto-2.2.1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.manifest

So this is not a regression issue.

Juro

From: Richard Purdie [richard.purdie@linuxfoundation.org]
Sent: Friday, September 15, 2017 9:50 AM
To: Cruz, Libertad; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica; Bystricky, Juro
Cc: Perez Carranza, Jose; Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: Re: QA cycle report for 2.2.2 rc2

This is a tricky one to evaluate. Going through the bugs in the QA
report:

Bug 12075 - think this is ok to fix on the branch and release note
Bug 12080 - we think minimal eSDK never worked in morty therefore this
is a QA testing error?
Bug 12073 - we continue to see various gpg errors even with master,
propose not to block release on this and only fix master
Bug 12009 - resolved and already fixed in 2.2.2 (I marked it resolved)
Bug 11150 - was a bug with 2.2.1 but should be fixed in 2.2.2?
Bug 11611 - was this found in 2.2.2?
Bug 11064 - marked as resolved as per QA comment, fix was in 2.2.2
Bug 11597 - fix was added to 2.2.2 (marked as resolved)
Bug 10460 - open and unresolved with master but not release blocker IMO
Bug 11797 - can't see any backport but not a release blocker as the
source mirrors work
Bug 11109 - No backport afaict but not release blocker

Which leave us with 12081 to understand before we can decide whether to release this or not.

So the decision to release or not depends on QA agreeing with the resolution of 12080 and figuring out what happened with 12081.

[Thanks to Ross for helping with some of this]

Cheers,

Richard




On Thu, 2017-09-14 at 16:53 -0700, Cruz, Libertad wrote:
Here is the report for the 2.2.2 point release test cycle.
Full Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-
_Full_Point_Release_Test_Cycle_2.2.2_rc2
======= Summary ========
The QA cycle for point release 2.2.2 rc2 is complete. There are 3 new
bugs: bug 12080[2] blocks testing to the eSDK component since eSDK
functionalities cannot be executed. Bugs 12075[1], 12073[3], 12081[4]
don’t block full functionalities.

LPT results are waiting to be updated by Windriver.

Performance
Compared with 2.2.2 rc1 there was a regression of 14.71 while building
rootfs on Ubuntu, there was also a regression on Fedora while building
sato of 7.46% and a regression on kernel of 12.12%.


Ubuntu Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:00:42
1:01:16 0.93
rootfs 2:16
2:36 14.71
rmwork 0:59:29 0:59:51
0.62
kernel 5:01
5:00 -0.33
eSDK 3:22
3:19 -1.49




Fedora Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:01:55
1:06:32 7.46
rootfs 2:49
2:51 1.18
rmwork 0:59:52 1:01:32
2.78
kernel 6:03
6:47 12.12
eSDK 3:44
3:54 4.46


ptest
There was an improvement on the pass rate in the following packages in
comparison with 2.2.2 rc1:
gdk-pixbuf with 5%
libxml2 with 4.20%
lttng-tools with 3.20%

On the other side there was a regression on the pass rate in
comparison with 2.2.2 rc1:
acl with 6.80%
e2fsprogs with 100% regression
gawk with .10%
quilt with 1.80%
valgrind of 53.10%


Compliance
Results are yet to be documented by Windriver.

======= QA-Hints========

There is only one concern on the eSDK component it cannot execute. QA
recommends an 2.2.2 rc3 to only verify the eSDK component.

======= Bugs ========

New Bugs
-12075[1] [morty] testimage quemux86/qemux86-64 lsb
tcgetattr: Input/output error^M
-12080[2] [Morty][Test Case 1605]
TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
-12073[3] selftest: setUpClass failed failing on ubuntu
17.04 (oeqa.selftest.signing.Signing)
-12081[4] [morty] PTEST: Package Name flex, gzip, slang,
do not appear in 2.2.2 rc2

Full Bug Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-1
3_-_Full_Point_Release_Test_Cycle_2.2.2_rc2#Bugs_Found_during_QA_Test


======== Links =========

1. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12075 [1]
2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12080 [2]
3. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12073 [3]
4. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12081 [4]



Regards
Libertad G.


Re: QA cycle report for 2.2.2 rc2

Bystricky, Juro
 

The commit is for 2.4 M3 (5f6945f5031e1a4ca116cc1eccf4c2f9dc228547)
2.4 does contain the ptests for gzip, slang and flex. (Although there are some other mysteries, like sed-ptest is missing)
It would seem that 2.2 had never contained (or lost a while ago) those ptests.

Juro
________________________________________
From: Cruz, Libertad
Sent: Friday, September 15, 2017 12:50 PM
To: Bystricky, Juro; Richard Purdie; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica
Cc: Perez Carranza, Jose; Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: RE: QA cycle report for 2.2.2 rc2

Hello,


Regarding 12080: this was a QA documentation error on the test steps, verified it again and changed the bug to not a bug, documented the correct steps for the QA.

Regarding 12081: To open bugs on ptest we make a comparison from the last run in this case the comparison was made with 2.2.2 rc1 Ptest 5f6945f5031e1a4ca116cc1eccf4c2f9dc228547 which in turn was compared with Ptest 9ed748a542b520c1cb763d981969233c0f5efd4e which was compared with Ptest 8e15e9b6e478f6368034519b2a8fd3c7ea71d23b which was compared with Ptest 6bd890d9e011014cf323e61267f8b256949d44aa, they all hold this packages.




Best Regards
Libertad G.

-----Original Message-----
From: Bystricky, Juro
Sent: Friday, September 15, 2017 1:04 PM
To: Richard Purdie <richard.purdie@linuxfoundation.org>; Cruz, Libertad <libertad.cruz@intel.com>; yocto@yoctoproject.org; Jolley, Stephen K <stephen.k.jolley@intel.com>; Zhang, Jessica <jessica.zhang@intel.com>
Cc: Perez Carranza, Jose <jose.perez.carranza@intel.com>; Cruz Alcaraz, Juan M <juan.m.cruz.alcaraz@intel.com>; Jordan, Robin L <robin.l.jordan@intel.com>
Subject: RE: QA cycle report for 2.2.2 rc2


Regarding 12081:
Looking at some previous ptest results in:
https://wiki.yoctoproject.org/wiki/QA_sanity_history
we can see that the offending tests (gzip, flex, slang) were not present in:
https://wiki.yoctoproject.org/wiki/Ptest_62d7d4130202d8ede16abf9e7d779361ca70847e
but started to appear after
https://wiki.yoctoproject.org/wiki/Ptest_6e20b31d5d17133e0fca086e12a0ad06ab5c4cc8 (flex)

Also checking the manifest file, the offending test were also missing in http://downloads.yoctoproject.org/releases/yocto/yocto-2.2.1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.manifest

So this is not a regression issue.

Juro

From: Richard Purdie [richard.purdie@linuxfoundation.org]
Sent: Friday, September 15, 2017 9:50 AM
To: Cruz, Libertad; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica; Bystricky, Juro
Cc: Perez Carranza, Jose; Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: Re: QA cycle report for 2.2.2 rc2

This is a tricky one to evaluate. Going through the bugs in the QA
report:

Bug 12075 - think this is ok to fix on the branch and release note
Bug 12080 - we think minimal eSDK never worked in morty therefore this
is a QA testing error?
Bug 12073 - we continue to see various gpg errors even with master,
propose not to block release on this and only fix master
Bug 12009 - resolved and already fixed in 2.2.2 (I marked it resolved)
Bug 11150 - was a bug with 2.2.1 but should be fixed in 2.2.2?
Bug 11611 - was this found in 2.2.2?
Bug 11064 - marked as resolved as per QA comment, fix was in 2.2.2
Bug 11597 - fix was added to 2.2.2 (marked as resolved)
Bug 10460 - open and unresolved with master but not release blocker IMO
Bug 11797 - can't see any backport but not a release blocker as the
source mirrors work
Bug 11109 - No backport afaict but not release blocker

Which leave us with 12081 to understand before we can decide whether to release this or not.

So the decision to release or not depends on QA agreeing with the resolution of 12080 and figuring out what happened with 12081.

[Thanks to Ross for helping with some of this]

Cheers,

Richard




On Thu, 2017-09-14 at 16:53 -0700, Cruz, Libertad wrote:
Here is the report for the 2.2.2 point release test cycle.
Full Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-
_Full_Point_Release_Test_Cycle_2.2.2_rc2
======= Summary ========
The QA cycle for point release 2.2.2 rc2 is complete. There are 3 new
bugs: bug 12080[2] blocks testing to the eSDK component since eSDK
functionalities cannot be executed. Bugs 12075[1], 12073[3], 12081[4]
don’t block full functionalities.

LPT results are waiting to be updated by Windriver.

Performance
Compared with 2.2.2 rc1 there was a regression of 14.71 while building
rootfs on Ubuntu, there was also a regression on Fedora while building
sato of 7.46% and a regression on kernel of 12.12%.


Ubuntu Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:00:42
1:01:16 0.93
rootfs 2:16
2:36 14.71
rmwork 0:59:29 0:59:51
0.62
kernel 5:01
5:00 -0.33
eSDK 3:22
3:19 -1.49




Fedora Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:01:55
1:06:32 7.46
rootfs 2:49
2:51 1.18
rmwork 0:59:52 1:01:32
2.78
kernel 6:03
6:47 12.12
eSDK 3:44
3:54 4.46


ptest
There was an improvement on the pass rate in the following packages in
comparison with 2.2.2 rc1:
gdk-pixbuf with 5%
libxml2 with 4.20%
lttng-tools with 3.20%

On the other side there was a regression on the pass rate in
comparison with 2.2.2 rc1:
acl with 6.80%
e2fsprogs with 100% regression
gawk with .10%
quilt with 1.80%
valgrind of 53.10%


Compliance
Results are yet to be documented by Windriver.

======= QA-Hints========

There is only one concern on the eSDK component it cannot execute. QA
recommends an 2.2.2 rc3 to only verify the eSDK component.

======= Bugs ========

New Bugs
-12075[1] [morty] testimage quemux86/qemux86-64 lsb
tcgetattr: Input/output error^M
-12080[2] [Morty][Test Case 1605]
TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
-12073[3] selftest: setUpClass failed failing on ubuntu
17.04 (oeqa.selftest.signing.Signing)
-12081[4] [morty] PTEST: Package Name flex, gzip, slang,
do not appear in 2.2.2 rc2

Full Bug Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-1
3_-_Full_Point_Release_Test_Cycle_2.2.2_rc2#Bugs_Found_during_QA_Test


======== Links =========

1. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12075 [1]
2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12080 [2]
3. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12073 [3]
4. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12081 [4]



Regards
Libertad G.


Re: QA cycle report for 2.2.2 rc2

libertad
 

Hello,


Regarding 12080: this was a QA documentation error on the test steps, verified it again and changed the bug to not a bug, documented the correct steps for the QA.

Regarding 12081: To open bugs on ptest we make a comparison from the last run in this case the comparison was made with 2.2.2 rc1 Ptest 5f6945f5031e1a4ca116cc1eccf4c2f9dc228547 which in turn was compared with Ptest 9ed748a542b520c1cb763d981969233c0f5efd4e which was compared with Ptest 8e15e9b6e478f6368034519b2a8fd3c7ea71d23b which was compared with Ptest 6bd890d9e011014cf323e61267f8b256949d44aa, they all hold this packages.




Best Regards
Libertad G.

-----Original Message-----
From: Bystricky, Juro
Sent: Friday, September 15, 2017 1:04 PM
To: Richard Purdie <richard.purdie@linuxfoundation.org>; Cruz, Libertad <libertad.cruz@intel.com>; yocto@yoctoproject.org; Jolley, Stephen K <stephen.k.jolley@intel.com>; Zhang, Jessica <jessica.zhang@intel.com>
Cc: Perez Carranza, Jose <jose.perez.carranza@intel.com>; Cruz Alcaraz, Juan M <juan.m.cruz.alcaraz@intel.com>; Jordan, Robin L <robin.l.jordan@intel.com>
Subject: RE: QA cycle report for 2.2.2 rc2


Regarding 12081:
Looking at some previous ptest results in:
https://wiki.yoctoproject.org/wiki/QA_sanity_history
we can see that the offending tests (gzip, flex, slang) were not present in:
https://wiki.yoctoproject.org/wiki/Ptest_62d7d4130202d8ede16abf9e7d779361ca70847e
but started to appear after
https://wiki.yoctoproject.org/wiki/Ptest_6e20b31d5d17133e0fca086e12a0ad06ab5c4cc8 (flex)

Also checking the manifest file, the offending test were also missing in http://downloads.yoctoproject.org/releases/yocto/yocto-2.2.1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.manifest

So this is not a regression issue.

Juro

From: Richard Purdie [richard.purdie@linuxfoundation.org]
Sent: Friday, September 15, 2017 9:50 AM
To: Cruz, Libertad; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica; Bystricky, Juro
Cc: Perez Carranza, Jose; Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: Re: QA cycle report for 2.2.2 rc2

This is a tricky one to evaluate. Going through the bugs in the QA
report:

Bug 12075 - think this is ok to fix on the branch and release note
Bug 12080 - we think minimal eSDK never worked in morty therefore this
is a QA testing error?
Bug 12073 - we continue to see various gpg errors even with master,
propose not to block release on this and only fix master
Bug 12009 - resolved and already fixed in 2.2.2 (I marked it resolved)
Bug 11150 - was a bug with 2.2.1 but should be fixed in 2.2.2?
Bug 11611 - was this found in 2.2.2?
Bug 11064 - marked as resolved as per QA comment, fix was in 2.2.2
Bug 11597 - fix was added to 2.2.2 (marked as resolved)
Bug 10460 - open and unresolved with master but not release blocker IMO
Bug 11797 - can't see any backport but not a release blocker as the
source mirrors work
Bug 11109 - No backport afaict but not release blocker

Which leave us with 12081 to understand before we can decide whether to release this or not.

So the decision to release or not depends on QA agreeing with the resolution of 12080 and figuring out what happened with 12081.

[Thanks to Ross for helping with some of this]

Cheers,

Richard




On Thu, 2017-09-14 at 16:53 -0700, Cruz, Libertad wrote:
Here is the report for the 2.2.2 point release test cycle.
Full Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-
_Full_Point_Release_Test_Cycle_2.2.2_rc2
======= Summary ========
The QA cycle for point release 2.2.2 rc2 is complete. There are 3 new
bugs: bug 12080[2] blocks testing to the eSDK component since eSDK
functionalities cannot be executed. Bugs 12075[1], 12073[3], 12081[4]
don't block full functionalities.

LPT results are waiting to be updated by Windriver.

Performance
Compared with 2.2.2 rc1 there was a regression of 14.71 while building
rootfs on Ubuntu, there was also a regression on Fedora while building
sato of 7.46% and a regression on kernel of 12.12%.


Ubuntu Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:00:42
1:01:16 0.93
rootfs 2:16
2:36 14.71
rmwork 0:59:29 0:59:51
0.62
kernel 5:01
5:00 -0.33
eSDK 3:22
3:19 -1.49




Fedora Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:01:55
1:06:32 7.46
rootfs 2:49
2:51 1.18
rmwork 0:59:52 1:01:32
2.78
kernel 6:03
6:47 12.12
eSDK 3:44
3:54 4.46


ptest
There was an improvement on the pass rate in the following packages in
comparison with 2.2.2 rc1:
gdk-pixbuf with 5%
libxml2 with 4.20%
lttng-tools with 3.20%

On the other side there was a regression on the pass rate in
comparison with 2.2.2 rc1:
acl with 6.80%
e2fsprogs with 100% regression
gawk with .10%
quilt with 1.80%
valgrind of 53.10%


Compliance
Results are yet to be documented by Windriver.

======= QA-Hints========

There is only one concern on the eSDK component it cannot execute. QA
recommends an 2.2.2 rc3 to only verify the eSDK component.

======= Bugs ========

New Bugs
-12075[1] [morty] testimage quemux86/qemux86-64 lsb
tcgetattr: Input/output error^M
-12080[2] [Morty][Test Case 1605]
TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
-12073[3] selftest: setUpClass failed failing on ubuntu
17.04 (oeqa.selftest.signing.Signing)
-12081[4] [morty] PTEST: Package Name flex, gzip, slang,
do not appear in 2.2.2 rc2

Full Bug Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-1
3_-_Full_Point_Release_Test_Cycle_2.2.2_rc2#Bugs_Found_during_QA_Test


======== Links =========

1. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12075 [1]
2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12080 [2]
3. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12073 [3]
4. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12081 [4]



Regards
Libertad G.


Re: [meta-cloud-services][PATCH] packagegroups: fix invalid license file

Bruce Ashfield <bruce.ashfield@...>
 

wrong mailing list, but merged anyway.

use the meta-virtualization mailing list for these.

Bruce

On 2017-09-15 5:27 AM, jackie.huang@windriver.com wrote:
From: Jackie Huang <jackie.huang@windriver.com>
Use '${COMMON_LICENSE_DIR}/MIT' for MIT License to fix the warning:
| WARNING: packagegroup-cloud-compute do_populate_lic:
${COREBASE}/LICENSE is not a valid license file, please use
'${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM.
This will become an error in the future
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
---
.../recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-compute.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-controller.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-debug.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-extras.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-network.bb | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb
index 6310b8f..e659c31 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb
@@ -1,7 +1,7 @@
SUMMARY = "Add benchmarking capabilities to cloud images"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb
index 21f8f10..2e9446d 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb
@@ -1,7 +1,7 @@
SUMMARY = "Configuration for OpenStack Compute node"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb
index f172839..1f0a8de 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb
@@ -1,7 +1,7 @@
SUMMARY = "Configuration for OpenStack Controller node"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb
index e5517d2..fecbdc6 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb
@@ -1,7 +1,7 @@
SUMMARY = "Add debugging capabilities to cloud images"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb
index 6fb6045..9273916 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb
@@ -1,7 +1,7 @@
SUMMARY = "Extra packages that improve the usability of compute/control nodes"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb
index f5b07a2..749a99f 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb
@@ -1,7 +1,7 @@
SUMMARY = "Configuration for OpenStack Network node"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
inherit packagegroup


[meta-raspberrypi][PATCH] u-boot: drop upstreamed patches included in v2017.09

Matthew McClintock
 

These are now in upstream, so they are no longer required here.

Signed-off-by: Matthew McClintock <msm-oss@mcclintock.net>
---
...01-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch | 67 --------------------
.../0002-rpi-Enable-USB-keyboard-support.patch | 71 ----------------------
recipes-bsp/u-boot/u-boot_%.bbappend | 7 ---
3 files changed, 145 deletions(-)
delete mode 100644 recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch
delete mode 100644 recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch

diff --git a/recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch b/recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch
deleted file mode 100644
index ffabe89..0000000
--- a/recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch
+++ /dev/null
@@ -1,67 +0,0 @@
-From 46035d84eb75d54e524d068c29a42c4f562f757a Mon Sep 17 00:00:00 2001
-From: Paul Barker <pbarker@toganlabs.com>
-Date: Wed, 2 Aug 2017 11:37:30 +0100
-Subject: [PATCH 1/2] Revert "dm: arm: rpi: Drop CONFIG_OF_EMBED"
-
-This reverts commit 25877d4e4c45451c5398aec3de50e0d5befe0e9f.
-
-Signed-off-by: Paul Barker <pbarker@toganlabs.com>
-Upstream-status: Pending
----
- configs/rpi_2_defconfig | 1 +
- configs/rpi_3_32b_defconfig | 1 +
- configs/rpi_3_defconfig | 1 +
- configs/rpi_defconfig | 1 +
- 4 files changed, 4 insertions(+)
-
-diff --git a/configs/rpi_2_defconfig b/configs/rpi_2_defconfig
-index 862203f..6aa0532 100644
---- a/configs/rpi_2_defconfig
-+++ b/configs/rpi_2_defconfig
-@@ -13,6 +13,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
-diff --git a/configs/rpi_3_32b_defconfig b/configs/rpi_3_32b_defconfig
-index 95b1677..7396925 100644
---- a/configs/rpi_3_32b_defconfig
-+++ b/configs/rpi_3_32b_defconfig
-@@ -14,6 +14,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
-diff --git a/configs/rpi_3_defconfig b/configs/rpi_3_defconfig
-index f91b53d..1b1ee67 100644
---- a/configs/rpi_3_defconfig
-+++ b/configs/rpi_3_defconfig
-@@ -14,6 +14,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
-diff --git a/configs/rpi_defconfig b/configs/rpi_defconfig
-index e2d81ab..c7cf6e0 100644
---- a/configs/rpi_defconfig
-+++ b/configs/rpi_defconfig
-@@ -13,6 +13,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
---
-2.7.4
-
diff --git a/recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch b/recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch
deleted file mode 100644
index 675d7d9..0000000
--- a/recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch
+++ /dev/null
@@ -1,71 +0,0 @@
-From e4ddccdcf2360c104de502db140a2dbb90b63cfe Mon Sep 17 00:00:00 2001
-From: Simon Glass <sjg@chromium.org>
-Date: Thu, 24 Aug 2017 19:45:31 -0600
-Subject: [PATCH 2/2] rpi: Enable USB keyboard support
-
-This is currently disabled, so USB keyboards are not detected in U_Boot.
-Enable this option to fix that.
-
-Backported to v2017.07.
-
-Signed-off-by: Simon Glass <sjg@chromium.org>
-Signed-off-by: Paul Barker <pbarker@toganlabs.com>
-Upstream-status: Backport
----
- configs/rpi_2_defconfig | 1 +
- configs/rpi_3_32b_defconfig | 1 +
- configs/rpi_3_defconfig | 1 +
- configs/rpi_defconfig | 1 +
- 4 files changed, 4 insertions(+)
-
-diff --git a/configs/rpi_2_defconfig b/configs/rpi_2_defconfig
-index 6aa0532..9851836 100644
---- a/configs/rpi_2_defconfig
-+++ b/configs/rpi_2_defconfig
-@@ -22,6 +22,7 @@ CONFIG_USB=y
- CONFIG_DM_USB=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_KEYBOARD=y
-+CONFIG_DM_KEYBOARD=y
- CONFIG_DM_VIDEO=y
- CONFIG_SYS_WHITE_ON_BLACK=y
- CONFIG_CONSOLE_SCROLL_LINES=10
-diff --git a/configs/rpi_3_32b_defconfig b/configs/rpi_3_32b_defconfig
-index 7396925..c9bdcd7 100644
---- a/configs/rpi_3_32b_defconfig
-+++ b/configs/rpi_3_32b_defconfig
-@@ -24,6 +24,7 @@ CONFIG_USB=y
- CONFIG_DM_USB=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_KEYBOARD=y
-+CONFIG_DM_KEYBOARD=y
- CONFIG_DM_VIDEO=y
- CONFIG_SYS_WHITE_ON_BLACK=y
- CONFIG_CONSOLE_SCROLL_LINES=10
-diff --git a/configs/rpi_3_defconfig b/configs/rpi_3_defconfig
-index 1b1ee67..e9c9806 100644
---- a/configs/rpi_3_defconfig
-+++ b/configs/rpi_3_defconfig
-@@ -24,6 +24,7 @@ CONFIG_USB=y
- CONFIG_DM_USB=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_KEYBOARD=y
-+CONFIG_DM_KEYBOARD=y
- CONFIG_DM_VIDEO=y
- CONFIG_SYS_WHITE_ON_BLACK=y
- CONFIG_CONSOLE_SCROLL_LINES=10
-diff --git a/configs/rpi_defconfig b/configs/rpi_defconfig
-index c7cf6e0..59d8c58 100644
---- a/configs/rpi_defconfig
-+++ b/configs/rpi_defconfig
-@@ -22,6 +22,7 @@ CONFIG_USB=y
- CONFIG_DM_USB=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_KEYBOARD=y
-+CONFIG_DM_KEYBOARD=y
- CONFIG_DM_VIDEO=y
- CONFIG_SYS_WHITE_ON_BLACK=y
- CONFIG_CONSOLE_SCROLL_LINES=10
---
-2.7.4
-
diff --git a/recipes-bsp/u-boot/u-boot_%.bbappend b/recipes-bsp/u-boot/u-boot_%.bbappend
index 8d0a531..3781666 100644
--- a/recipes-bsp/u-boot/u-boot_%.bbappend
+++ b/recipes-bsp/u-boot/u-boot_%.bbappend
@@ -1,8 +1 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/u-boot:"
-
-SRC_URI_append_rpi = " \
- file://0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch \
- file://0002-rpi-Enable-USB-keyboard-support.patch \
- "
-
RDEPENDS_${PN}_append_rpi = " rpi-u-boot-scr"
--
2.14.1


Re: QA cycle report for 2.2.2 rc2

Bystricky, Juro
 

Regarding 12081:
Looking at some previous ptest results in:
https://wiki.yoctoproject.org/wiki/QA_sanity_history
we can see that the offending tests (gzip, flex, slang) were not present in:
https://wiki.yoctoproject.org/wiki/Ptest_62d7d4130202d8ede16abf9e7d779361ca70847e
but started to appear after
https://wiki.yoctoproject.org/wiki/Ptest_6e20b31d5d17133e0fca086e12a0ad06ab5c4cc8 (flex)

Also checking the manifest file, the offending test were also missing in
http://downloads.yoctoproject.org/releases/yocto/yocto-2.2.1/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.manifest

So this is not a regression issue.

Juro

From: Richard Purdie [richard.purdie@linuxfoundation.org]
Sent: Friday, September 15, 2017 9:50 AM
To: Cruz, Libertad; yocto@yoctoproject.org; Jolley, Stephen K; Zhang, Jessica; Bystricky, Juro
Cc: Perez Carranza, Jose; Cruz Alcaraz, Juan M; Jordan, Robin L
Subject: Re: QA cycle report for 2.2.2 rc2

This is a tricky one to evaluate. Going through the bugs in the QA
report:

Bug 12075 - think this is ok to fix on the branch and release note
Bug 12080 - we think minimal eSDK never worked in morty therefore this
is a QA testing error?
Bug 12073 - we continue to see various gpg errors even with master,
propose not to block release on this and only fix master
Bug 12009 - resolved and already fixed in 2.2.2 (I marked it resolved)
Bug 11150 - was a bug with 2.2.1 but should be fixed in 2.2.2?
Bug 11611 - was this found in 2.2.2?
Bug 11064 - marked as resolved as per QA comment, fix was in 2.2.2
Bug 11597 - fix was added to 2.2.2 (marked as resolved)
Bug 10460 - open and unresolved with master but not release blocker IMO
Bug 11797 - can't see any backport but not a release blocker as the
source mirrors work
Bug 11109 - No backport afaict but not release blocker

Which leave us with 12081 to understand before we can decide whether to
release this or not.

So the decision to release or not depends on QA agreeing with the resolution of 12080 and figuring out what happened with 12081.

[Thanks to Ross for helping with some of this]

Cheers,

Richard




On Thu, 2017-09-14 at 16:53 -0700, Cruz, Libertad wrote:
Here is the report for the 2.2.2 point release test cycle.
Full Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-
_Full_Point_Release_Test_Cycle_2.2.2_rc2
======= Summary ========
The QA cycle for point release 2.2.2 rc2 is complete. There are 3
new bugs: bug 12080[2] blocks testing to the eSDK component since
eSDK functionalities cannot be executed. Bugs 12075[1], 12073[3],
12081[4] don’t block full functionalities.

LPT results are waiting to be updated by Windriver.

Performance
Compared with 2.2.2 rc1 there was a regression of 14.71 while
building rootfs on Ubuntu, there was also a regression on Fedora
while building sato of 7.46% and a regression on kernel of 12.12%.


Ubuntu Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:00:42
1:01:16 0.93
rootfs 2:16
2:36 14.71
rmwork 0:59:29 0:59:51
0.62
kernel 5:01
5:00 -0.33
eSDK 3:22
3:19 -1.49




Fedora Test 2.2.2_rc1
2.2.2_rc2 %
sato 1:01:55
1:06:32 7.46
rootfs 2:49
2:51 1.18
rmwork 0:59:52 1:01:32
2.78
kernel 6:03
6:47 12.12
eSDK 3:44
3:54 4.46


ptest
There was an improvement on the pass rate in the following packages
in comparison with 2.2.2 rc1:
gdk-pixbuf with 5%
libxml2 with 4.20%
lttng-tools with 3.20%

On the other side there was a regression on the pass rate in
comparison with 2.2.2 rc1:
acl with 6.80%
e2fsprogs with 100% regression
gawk with .10%
quilt with 1.80%
valgrind of 53.10%


Compliance
Results are yet to be documented by Windriver.

======= QA-Hints========

There is only one concern on the eSDK component it cannot execute. QA
recommends an 2.2.2 rc3 to only verify the eSDK component.

======= Bugs ========

New Bugs
-12075[1] [morty] testimage quemux86/qemux86-64 lsb
tcgetattr: Input/output error^M
-12080[2] [Morty][Test Case 1605]
TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
-12073[3] selftest: setUpClass failed failing on ubuntu
17.04 (oeqa.selftest.signing.Signing)
-12081[4] [morty] PTEST: Package Name flex, gzip, slang,
do not appear in 2.2.2 rc2

Full Bug Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-1
3_-_Full_Point_Release_Test_Cycle_2.2.2_rc2#Bugs_Found_during_QA_Test


======== Links =========

1. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12075 [1]
2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12080 [2]
3. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12073 [3]
4. https://bugzilla.yoctoproject.org/show_bug.cgi?id=12081 [4]



Regards
Libertad G.


Re: Morty to Pyro upgrade

Paul D. DeRocco
 

From: Khem Raj [mailto:raj.khem@gmail.com]

On Thu, Sep 14, 2017 at 11:15 PM, Paul D. DeRocco
<pderocco@ix.netcom.com> wrote:
I just upgraded to Pyro, and now I get several Python errors in
sstate_sign_package(), complaining there is no module named
oe.gpg_sign.

I reused the Morty sstate-cache. Is that legal, or do I
need to nuke it and start over?
its too optimistic to use sstate across releases and I dont
think abi is guaranteed
Nuking sstate-cache didn't change anything. I've attached the full console output from my x86 build. My RPi build produces similar errors.

This is on a freshly installed Ubuntu 16.04 system. I installed Pyro from git, added meta-intel pyro branch from git, and added meta-openembedded pyro branch from their git. So everything should be current.

--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com


Re: QA cycle report for 2.2.2 rc2

Richard Purdie
 

This is a tricky one to evaluate. Going through the bugs in the QA
report:

Bug 12075 - think this is ok to fix on the branch and release note
Bug 12080 - we think minimal eSDK never worked in morty therefore this 
            is a QA testing error?
Bug 12073 - we continue to see various gpg errors even with master, 
            propose not to block release on this and only fix master
Bug 12009 - resolved and already fixed in 2.2.2 (I marked it resolved)
Bug 11150 - was a bug with 2.2.1 but should be fixed in 2.2.2?
Bug 11611 - was this found in 2.2.2?
Bug 11064 - marked as resolved as per QA comment, fix was in 2.2.2
Bug 11597 - fix was added to 2.2.2 (marked as resolved)
Bug 10460 - open and unresolved with master but not release blocker IMO
Bug 11797 - can't see any backport but not a release blocker as the 
            source mirrors work
Bug 11109 - No backport afaict but not release blocker

Which leave us with 12081 to understand before we can decide whether to
release this or not.

So the decision to release or not depends on QA agreeing with the resolution of 12080 and figuring out what happened with 12081.

[Thanks to Ross for helping with some of this]

Cheers,

Richard

On Thu, 2017-09-14 at 16:53 -0700, Cruz, Libertad wrote:
Here is the report for the 2.2.2 point release test cycle.
Full Report :  https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-
_Full_Point_Release_Test_Cycle_2.2.2_rc2
======= Summary ========
The QA cycle for point release 2.2.2 rc2 is complete.  There are 3
new bugs: bug 12080[2]  blocks testing to the eSDK component since
eSDK functionalities cannot be executed. Bugs 12075[1], 12073[3],
12081[4] don’t block full functionalities.
 
LPT results are waiting to be updated by Windriver.
 
Performance
Compared with 2.2.2 rc1 there was a regression of 14.71 while
building rootfs on Ubuntu, there was also a regression on Fedora
while building sato of 7.46% and a regression on kernel of 12.12%.
 
 
Ubuntu                 Test       2.2.2_rc1            
2.2.2_rc2             %
                              sato       1:00:42             
1:01:16               0.93
                              rootfs    2:16                   
2:36                     14.71
                              rmwork 0:59:29              0:59:51  
            0.62
                              kernel    5:01                   
5:00                     -0.33
                              eSDK      3:22                   
3:19                     -1.49
                                                                     
     
                                                                     
     
Fedora                 Test       2.2.2_rc1            
2.2.2_rc2             %
                              sato       1:01:55             
1:06:32               7.46
                              rootfs    2:49                   
2:51                     1.18
                              rmwork 0:59:52              1:01:32  
            2.78
                              kernel    6:03                   
6:47                     12.12
                              eSDK      3:44                   
3:54                     4.46
 
 
ptest
There was an improvement on the pass rate in the following packages
in comparison with 2.2.2 rc1:
gdk-pixbuf with 5%
libxml2 with 4.20%
lttng-tools with 3.20%
 
On the other side there was a regression on the pass rate in
comparison with 2.2.2 rc1:
acl with 6.80%
e2fsprogs with 100% regression
gawk with .10%
quilt with 1.80%
valgrind of 53.10%
 
 
Compliance
Results are yet to be documented by Windriver.
 
======= QA-Hints========
 
There is only one concern on the eSDK component it cannot execute. QA
recommends an 2.2.2 rc3 to only verify the eSDK component.
 
======= Bugs ========
 
       New Bugs
            -12075[1]  [morty] testimage quemux86/qemux86-64 lsb
tcgetattr: Input/output error^M
            -12080[2] [Morty][Test Case 1605]
TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
            -12073[3] selftest: setUpClass failed failing on ubuntu
17.04 (oeqa.selftest.signing.Signing)
            -12081[4] [morty] PTEST: Package Name flex, gzip, slang,
do not appear in 2.2.2 rc2
 
Full Bug Report : https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-1
3_-_Full_Point_Release_Test_Cycle_2.2.2_rc2#Bugs_Found_during_QA_Test
 
 
======== Links =========
 
    1.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12075 [1]
    2.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12080 [2]
    3.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12073 [3]
    4.    https://bugzilla.yoctoproject.org/show_bug.cgi?id=12081 [4]
 
   
 
Regards
Libertad G.


Re: [meta-raspberry-pi] needing newer or patched version of g++

Bill J
 

On Sep 15, 2017, at 7:43 AM, Khem Raj <raj.khem@gmail.com> wrote:

On Fri, Sep 15, 2017 at 7:35 AM, Bill Jenkins <bill@korgrd.com> wrote:

On Sep 15, 2017, at 6:54 AM, Khem Raj <raj.khem@gmail.com> wrote:

On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins <bill@korgrd.com> wrote:
After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the following compiler error when
compiling an application using the SDK:

internal compiler error: Max. number of generated reload insns per insn is achieved (90)

It turns out that a patch was submitted for g++ early last year for the above problem,
We need to backport the patch to 6.3.0 and regenerate SDK. If you can
point to patch that will be helpful.
Thanks Khem, here's a link to the commit:

https://github.com/gcc-mirror/gcc/commit/4fe01ba94e99e792ebe9da2ccb3b071aa1bac388#diff-af18d9175d034b2b3726f1ddc05fae55
OK and which release are you on ?
I've been building in the pyro branch. DISTRO_VERSION reports 2.3.2.


but apparently that
patch is not in the 6.3.0 version within the SDK. When I try to specify a newer version,
(by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that only 5.4.0 or 6.3.0
are available. Any suggestions on how to resolve this? (i.e. is there some way to use a newer g++ or to
apply the patch?)

Thanks,
Bill
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


externalsrc: enable sstate for git srctrees based on makefile

Rajendran, Vignesh (RBEI/ECF3; ADITG/SW2) <external.vrajendran@...>
 

Hi Yocto,

 

I am already aware of sstate never works for externalsrc recipes.

 

My environment is using externalsrc in recipes for makefile based sources in git.

 

I am aware that the source is not going to change and only builds one time in my production build.

 

I want to use sstate if nothing has changed in my next build/bitbake.

 

Is it possible to enable setscene tasks if the source is in git and srctree_hash_files reports nothing has been changed in git srctree?

https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/externalsrc.bbclass#n181

 

Do I have to consider some other constraints as well?

 

Thanks in Advance.

 

Best regards

Vignesh Rajendran

 


Re: [meta-raspberry-pi] needing newer or patched version of g++

Khem Raj
 

On Fri, Sep 15, 2017 at 7:35 AM, Bill Jenkins <bill@korgrd.com> wrote:

On Sep 15, 2017, at 6:54 AM, Khem Raj <raj.khem@gmail.com> wrote:

On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins <bill@korgrd.com> wrote:
After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the following compiler error when
compiling an application using the SDK:

internal compiler error: Max. number of generated reload insns per insn is achieved (90)

It turns out that a patch was submitted for g++ early last year for the above problem,
We need to backport the patch to 6.3.0 and regenerate SDK. If you can
point to patch that will be helpful.
Thanks Khem, here's a link to the commit:

https://github.com/gcc-mirror/gcc/commit/4fe01ba94e99e792ebe9da2ccb3b071aa1bac388#diff-af18d9175d034b2b3726f1ddc05fae55
OK and which release are you on ?

but apparently that
patch is not in the 6.3.0 version within the SDK. When I try to specify a newer version,
(by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that only 5.4.0 or 6.3.0
are available. Any suggestions on how to resolve this? (i.e. is there some way to use a newer g++ or to
apply the patch?)

Thanks,
Bill
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [meta-raspberry-pi] needing newer or patched version of g++

Bill J
 

On Sep 15, 2017, at 6:54 AM, Khem Raj <raj.khem@gmail.com> wrote:

On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins <bill@korgrd.com> wrote:
After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the following compiler error when
compiling an application using the SDK:

internal compiler error: Max. number of generated reload insns per insn is achieved (90)

It turns out that a patch was submitted for g++ early last year for the above problem,
We need to backport the patch to 6.3.0 and regenerate SDK. If you can
point to patch that will be helpful.
Thanks Khem, here's a link to the commit:

https://github.com/gcc-mirror/gcc/commit/4fe01ba94e99e792ebe9da2ccb3b071aa1bac388#diff-af18d9175d034b2b3726f1ddc05fae55


but apparently that
patch is not in the 6.3.0 version within the SDK. When I try to specify a newer version,
(by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that only 5.4.0 or 6.3.0
are available. Any suggestions on how to resolve this? (i.e. is there some way to use a newer g++ or to
apply the patch?)

Thanks,
Bill
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


gdk-pixbuf does not install libraries

Pierre-Olivier Huard <pierre-olivier.huard@...>
 

Hello,

I already posted my question on SO, but with no success, so I'll try here.

I'm working on a custom board with iMX6 Quad, on Yocto 2.1.2 (Krogoth branch), I tested on a more recent version, 2.3.1, and the result is the same.
My main goal is to use gdkpixbufoverlay Gstreamer element on my board. This is my error:

gst-launch-1.0 videotestsrc ! gdkpixbufoverlay location=image.png ! fakesink

(gst-launch-1.0:441): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstGdkPixbufOverlay:gdkpixbufoverlay0: Could not load overlay image.
Additional debug info:
../../../gst-plugins-good-1.6.3/ext/gdk_pixbuf/gstgdkpixbufoverlay.c(508): gst_gdk_pixbuf_overlay_start (): /GstPipeline:pipeline0/GstGdkPixbufOverlay:gdkpixbufoverlay0:
Couldn't recognize the image file format for file 'image.png'
Setting pipeline to NULL ...
Freeing pipeline ...

So I tried to run the command advised, but I did not work either. I took a look at the output:

/usr/lib/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders
# GdkPixbuf Image Loader Modules file
# Automatically generated file, do not edit
# Created by gdk-pixbuf-query-loaders from gdk-pixbuf-2.32.3
#
# LoaderDir = /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders
#


And the output is full of comments.

I checked my configuration on yocto:
# bitbake -e gdk-pixbuf | grep ^PACKAGECONFIG=
PACKAGECONFIG="png jpeg"


So the recipe seems to be correctly configured, but I don't have the libraries on the image (eg libpixbufloader-png.so). I've tried to add all gtk recipes to my image, but I don't have the lipixbufloader-*.so libraries.

Did I miss something on my configuration?

Thank you,
Pierre-Olivier


Re: Morty to Pyro upgrade

Khem Raj
 

On Thu, Sep 14, 2017 at 11:15 PM, Paul D. DeRocco
<pderocco@ix.netcom.com> wrote:
I just upgraded to Pyro, and now I get several Python errors in
sstate_sign_package(), complaining there is no module named oe.gpg_sign.

I reused the Morty sstate-cache. Is that legal, or do I need to nuke it
and start over?
its too optimistic to use sstate across releases and I dont think abi is
guaranteed


--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com

--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [meta-raspberry-pi] needing newer or patched version of g++

Khem Raj
 

On Thu, Sep 14, 2017 at 10:14 PM, Bill Jenkins <bill@korgrd.com> wrote:
After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the following compiler error when
compiling an application using the SDK:

internal compiler error: Max. number of generated reload insns per insn is achieved (90)

It turns out that a patch was submitted for g++ early last year for the above problem,
We need to backport the patch to 6.3.0 and regenerate SDK. If you can
point to patch that will be helpful.

but apparently that
patch is not in the 6.3.0 version within the SDK. When I try to specify a newer version,
(by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that only 5.4.0 or 6.3.0
are available. Any suggestions on how to resolve this? (i.e. is there some way to use a newer g++ or to
apply the patch?)

Thanks,
Bill
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [pyro][meta-oracle-java][PATCH 2/2] oracle-java: create directory before creating links

Fabio Berton
 

​Hi Vincent,

I didn't see this error, but I'll look this issue. Without these two commits that I sent to pyro branch I can't build some Java applications because the application can't find java and javac.

On Fri, Sep 15, 2017 at 4:30 AM, Vincent Prince <vincent.prince.fr@...> wrote:
Hi Fabio,

I have a non fatal-error on link creation on pyro:

ERROR: oracle-jse-jdk-x86-64-native-1.8.0-u131r0 do_populate_sysroot:
sstate found an absolute path symlink
/home/build/tmp/work/x86_64-linux/oracle-jse-jdk-x86-64-native/1.8.0-u131r0/sysroot-destdir/home/build/tmp/work/x86_64-linux/oracle-jse-jdk-x86-64-native/1.8.0-u131r0/recipe-sysroot-native/usr/bin/java
pointing at /home/build/tmp/work/x86_64-linux/oracle-jse-jdk-x86-64-native/1.8.0-u131r0/recipe-sysroot-native/usr/lib/jvm/java-8-oracle/bin/java.
Please replace this with a relative link.

I suspect that those lines are concerned:
        ln -sf ${JDK_HOME}/bin/java             ${D}${bindir}
        ln -sf ${JDK_HOME}/bin/javac            ${D}${bindir}

Am I wrong?

Best Regards,
Vincent

2017-09-14 22:21 GMT+02:00 Fabio Berton <fabio.berton@...>:
> From: Jan Remmet <j.remmet@...>
>
> if bindir directory doesn't exists the link is created wrongly:
>
> file -b tmp/work/x86_64-linux/oracle-jse-jdk-x86-64-native/1.8.0-u131r0/image/home/yocto/build/tmp/sysroots/x86_64-linux/usr/bin
> symbolic link to
> `/home/yocto/build/tmp/sysroots/x86_64-linux/usr/lib/jvm/java-8-oracle/bin/javac'
>
> tested on morty
>
> Signed-off-by: Jan Remmet <j.remmet@...>
> Signed-off-by: Maxin B. John <maxin.john@...>
> (cherry picked from commit 731d3d2cf7e7d65954991e79b9918575e06081c8)
> ---
>  recipes-devtools/oracle-java/oracle-jse-jdk.inc | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk.inc b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
> index 935ad9b..a7210d9 100644
> --- a/recipes-devtools/oracle-java/oracle-jse-jdk.inc
> +++ b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
> @@ -12,11 +12,14 @@ JDK_JRE = "jdk"
>  require oracle-jse.inc
>
>  do_install_class-native() {
> -       install -d -m 0755                      ${D}${libdir_jvm}
> +       install -d                              ${D}${libdir_jvm}
>         cp -a ${S}/${JDK_JRE}${PV}_${PV_UPDATE} ${D}${JDK_HOME}
>
> +       install -d                              ${D}${bindir}
>         ln -sf ${JDK_HOME}/bin/java             ${D}${bindir}
>         ln -sf ${JDK_HOME}/bin/javac            ${D}${bindir}
> +
> +       install -d                              ${D}${JDK_HOME}/bin
>         ln -sf javah                            ${D}${JDK_HOME}/bin/gjavah
>         ln -sf jar                              ${D}${JDK_HOME}/bin/fastjar
>  }
> --
> 2.14.1
>
> --
> _______________________________________________
> yocto mailing list
> yocto@...
> https://lists.yoctoproject.org/listinfo/yocto


[meta-cloud-services][PATCH] packagegroups: fix invalid license file

Jackie Huang
 

From: Jackie Huang <jackie.huang@windriver.com>

Use '${COMMON_LICENSE_DIR}/MIT' for MIT License to fix the warning:

| WARNING: packagegroup-cloud-compute do_populate_lic:
${COREBASE}/LICENSE is not a valid license file, please use
'${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM.
This will become an error in the future

Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
---
.../recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-compute.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-controller.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-debug.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-extras.bb | 2 +-
.../recipes-extended/packagegroups/packagegroup-cloud-network.bb | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb
index 6310b8f..e659c31 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-benchmarking.bb
@@ -1,7 +1,7 @@
SUMMARY = "Add benchmarking capabilities to cloud images"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb
index 21f8f10..2e9446d 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-compute.bb
@@ -1,7 +1,7 @@
SUMMARY = "Configuration for OpenStack Compute node"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb
index f172839..1f0a8de 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-controller.bb
@@ -1,7 +1,7 @@
SUMMARY = "Configuration for OpenStack Controller node"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb
index e5517d2..fecbdc6 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-debug.bb
@@ -1,7 +1,7 @@
SUMMARY = "Add debugging capabilities to cloud images"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb
index 6fb6045..9273916 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-extras.bb
@@ -1,7 +1,7 @@
SUMMARY = "Extra packages that improve the usability of compute/control nodes"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb
index f5b07a2..749a99f 100644
--- a/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb
+++ b/meta-openstack/recipes-extended/packagegroups/packagegroup-cloud-network.bb
@@ -1,7 +1,7 @@
SUMMARY = "Configuration for OpenStack Network node"
PR = "r0"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
--
2.9.3


[meta-security][PATCH] packagegroups: fix invalid license file

Jackie Huang
 

From: Jackie Huang <jackie.huang@windriver.com>

Use '${COMMON_LICENSE_DIR}/MIT' for MIT License to fix the warning:

| WARNING: packagegroup-core-security do_populate_lic:
${COREBASE}/LICENSE is not a valid license file, please use
'${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM.
This will become an error in the future

Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
---
meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb | 2 +-
meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb | 2 +-
meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb | 2 +-
meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb | 2 +-
recipes-security/packagegroup/packagegroup-core-security.bb | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb
index 2d93aca..3b9d271 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm-i2c.bb
@@ -1,6 +1,6 @@
DESCRIPTION = "Security packagegroup for TPM i2c support"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb
index 2db8521..25126ef 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb
@@ -1,6 +1,6 @@
DESCRIPTION = "Security packagegroup for Poky"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
index 57b0722..13b505f 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
@@ -1,6 +1,6 @@
DESCRIPTION = "Security packagegroup for Poky"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb b/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb
index f7eee7c..2e9394f 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-vtpm.bb
@@ -1,6 +1,6 @@
DESCRIPTION = "Security packagegroup for Poky"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
diff --git a/recipes-security/packagegroup/packagegroup-core-security.bb b/recipes-security/packagegroup/packagegroup-core-security.bb
index cfd7918..6682d29 100644
--- a/recipes-security/packagegroup/packagegroup-core-security.bb
+++ b/recipes-security/packagegroup/packagegroup-core-security.bb
@@ -1,6 +1,6 @@
DESCRIPTION = "Security packagegroup for Poky"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

inherit packagegroup
--
2.11.0

17141 - 17160 of 55062