date:20211104

[OE-core] [V3][PATCH] ruby: workaround ptest hang problem

2021-11-04 Thread Changqing Li

From: Changqing Li 

since openssl 3 not compatible problem, ruby have disable openssl
extention. But disable openssl extention make test_smtp.rs hang at
test case "test_start".

Net::TestSMTP#test_start:
NameError: uninitialized constant Net::SMTP::OpenSSL
Did you mean? Open3
/usr/lib64/ruby/3.0.0/net/smtp.rb:195:in `default_ssl_context'
/usr/lib64/ruby/3.0.0/net/smtp.rb:552:in `start'
/usr/lib64/ruby/3.0.0/net/smtp.rb:475:in `start'
/usr/lib64/ruby/ptest/test/net/smtp/test_smtp.rb:199:in `test_start'

temporarily remove the hang case to make other testcases can be run.

Meantime, move ruby-ptest out of the PTESTS_PROBLEMS list.
On 48 core host, run ruby ptest in qemux86-64:
root@qemux86-64:/usr/lib64/ruby/ptest# time ./run-ptest
PASS: test/test_set.rb
PASS: test/stringio/test_stringio.rb
...
PASS: test/did_you_mean/test_tree_spell_checker.rb
PASS: test/test_mutex_m.rb

real5m42.872s
user3m50.923s
sys 0m44.136s

Signed-off-by: Changqing Li 
---
 meta/conf/distro/include/ptest-packagelists.inc | 3 +--
 meta/recipes-devtools/ruby/ruby.inc | 4 
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/meta/conf/distro/include/ptest-packagelists.inc 
b/meta/conf/distro/include/ptest-packagelists.inc
index 2e324f8da4..f1c40ac813 100644
--- a/meta/conf/distro/include/ptest-packagelists.inc
+++ b/meta/conf/distro/include/ptest-packagelists.inc
@@ -81,6 +81,7 @@ PTESTS_SLOW = "\
 openssl-ptest \
 perl-ptest \
 python3-ptest \
+ruby-ptest \
 strace-ptest \
 tcl-ptest \
 util-linux-ptest \
@@ -90,7 +91,6 @@ PTESTS_SLOW = "\
 PTESTS_SLOW:remove:riscv64 = "valgrind-ptest"
 PTESTS_PROBLEMS:append:riscv64 = "valgrind-ptest"
 
-#ruby-ptest \ # Timeout
 #lz4-ptest \ # Needs a rewrite
 #rt-tests-ptest \ # Needs to be checked whether it runs at all
 #bash-ptest \ # Test outcomes are non-deterministic by design
@@ -103,7 +103,6 @@ PTESTS_PROBLEMS:append:riscv64 = "valgrind-ptest"
 #python3-numpy-ptest \ # requires even more RAM and (possibly) disk space; 
multiple failures
 
 PTESTS_PROBLEMS = "\
-ruby-ptest \
 lz4-ptest \
 rt-tests-ptest \
 bash-ptest \
diff --git a/meta/recipes-devtools/ruby/ruby.inc 
b/meta/recipes-devtools/ruby/ruby.inc
index 2b5caf35f5..776c409f6c 100644
--- a/meta/recipes-devtools/ruby/ruby.inc
+++ b/meta/recipes-devtools/ruby/ruby.inc
@@ -42,3 +42,7 @@ do_configure:prepend() {
 do_configure:prepend() {
 rm -rf ${S}/ext/openssl/extconf.rb
 }
+# Remove this test temporarily until it compatible with openssl 3
+do_install_ptest:append() {
+rm -rf ${D}${PTEST_PATH}/test/net/smtp/test_smtp.rb
+}
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157881): 
https://lists.openembedded.org/g/openembedded-core/message/157881
Mute This Topic: https://lists.openembedded.org/mt/86832482/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 0/6] kernel: consolidated pull request

2021-11-04 Thread Bruce Ashfield

On Thu, Nov 4, 2021 at 4:57 PM Khem Raj  wrote:

>
>
> On 11/4/21 12:48 PM, Bruce Ashfield wrote:
> > From: Bruce Ashfield 
> >
> > Richard,
> >
> > Here's a broad set of kernel updates:
> >
> >   - stable for 5.14
> >   - stable for 5.10
> >
> > And then the bigger, a way earlier than normal:
> >
> >   - libc-headers bump to 5.15
> >   - 5.15 reference kernel recipes
> >
> > As everyone has probably heard, 5.15 is the next kernel LTS, so I
> > wanted to establish it for the next release earlier than normal. Due
> > to the -dev testing, things like lttng, perf and devsrc are already
> > ready to go, so this is a smaller pull request than normal.
> >
> > I had to fixup strace, and the vboxguest drivers (patch sent to
> > meta-oe)
> >
> > I've run it through the AB and everything came back green, as well
> > as my local testing.
> >
> > This isn't the default for any of the machines yet (but I have
> > local patches for that as well). The h/w reference boards
> > stil use 5.14 and need to be updated, but the plan is to remove 5.14,
> > and eventually 5.10 from master, and we'll go with 5.15, and 5.16+
> > in the spring 2022 release.
>
> also 5.10 ? I think there perhaps will be enough folks needing 5.10
> Since next YP release is also LTS, I wonder if we should keep kernel
> UAPIs as a LTS kernel too.
>

While we have to wait a bit longer to hear, it is very likely that 5.15
will outlast 5.10 in terms of support .. since almost every other LTS has
picked up extended support. As for 5.10 (I state the obvious), that's what
the release branches are for :)

We've never kept more than 2 released + 1 dev kernels active at once (in
master) .. one can always find a consumer of any particular version or
subversion, and they are convinced they need it.  5.15 is a definite, as is
something newer than it (because we absolutely need newer for
feature/platform/bleeding edge), which leaves 5.10 on the bubble.

Just because the recipe isn't in master, doesn't mean I'm not updating and
maintaining it .. it just means that we aren't doing a matrix of tests on
it, since that would be 4x (if you count -dev) active kernels in master and
that's a significant overhead.

That all being said, I'm not removing anything yet, and we'll see where the
chips fall on that front!

I've taken note, it can all be mixed into the consideration. The fact that
you read my yammering closely enough to comment, gives weight to
the request :)

Bruce



>
> >
> > Cheers,
> >
> > Bruce
> >
> > The following changes since commit
> 3e9c4801216111496acffdfdccf1deae3b3d6b96:
> >
> >insane.bbclass: Add a check for directories that are expected to be
> empty (2021-11-03 11:12:26 +)
> >
> > are available in the Git repository at:
> >
> >git://git.yoctoproject.org/poky-contrib zedd/kernel
> >http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
> >
> > Bruce Ashfield (6):
> >linux-yocto/5.14: update to v5.14.15
> >linux-yocto/5.10: update to v5.10.76
> >linux-libc-headers: update to v5.15
> >linux-yocto-rt/5.10: update to -rt54
> >linux-yocto/5.15: introduce recipes
> >strace: fix build against 5.15 kernel/kernel-headers
> >
> >   meta/conf/distro/include/tcmode-default.inc   |   2 +-
> >   ...1-Avoid-relying-on-presence-of-ipx.h.patch | 151 ++
> >   meta/recipes-devtools/strace/strace_5.14.bb   |   1 +
> >   ...ers_5.14.bb => linux-libc-headers_5.15.bb} |   4 +-
> >   .../linux/linux-yocto-rt_5.10.bb  |   6 +-
> >   .../linux/linux-yocto-rt_5.14.bb  |   6 +-
> >   .../linux/linux-yocto-rt_5.15.bb  |  45 ++
> >   .../linux/linux-yocto-tiny_5.10.bb|   8 +-
> >   .../linux/linux-yocto-tiny_5.14.bb|   8 +-
> >   .../linux/linux-yocto-tiny_5.15.bb|  32 
> >   meta/recipes-kernel/linux/linux-yocto_5.10.bb |  24 +--
> >   meta/recipes-kernel/linux/linux-yocto_5.14.bb |  26 +--
> >   meta/recipes-kernel/linux/linux-yocto_5.15.bb |  68 
> >   13 files changed, 339 insertions(+), 42 deletions(-)
> >   create mode 100644
> meta/recipes-devtools/strace/strace/0001-Avoid-relying-on-presence-of-ipx.h.patch
> >   rename meta/recipes-kernel/linux-libc-headers/{
> linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} (81%)
> >   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
> >   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
> >   create mode 100644 meta/recipes-kernel/linux/linux-yocto_5.15.bb
> >
> >
> >
> > 
> >
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157880): 
https://lists.openembedded.org/g/openembedded-core/message/157880
Mute This Topic: https://lists.openembedded.org/mt/86824892/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe:

Re: [OE-core] [V2][PATCH] ruby: workaround ptest hang problem

2021-11-04 Thread Changqing Li



On 11/4/21 5:17 PM, Alexander Kanavin wrote:


**[Please note: This e-mail is from an EXTERNAL e-mail address]

On Thu, 4 Nov 2021 at 02:42, Changqing Li > wrote:


@@ -85,12 +85,12 @@ PTESTS_SLOW = "\
     tcl-ptest \
     util-linux-ptest \
     valgrind-ptest \
+    ruby-ptest \
 "


Thanks, can you insert this in alphabetical order? Also please add to 
the commit message how long does the test take.


Alex

OK,  Thanks.  I will send V3

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157879): 
https://lists.openembedded.org/g/openembedded-core/message/157879
Mute This Topic: https://lists.openembedded.org/mt/86807541/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] opkg: Fix poor operator combination choice

2021-11-04 Thread Richard Purdie

On Thu, 2021-11-04 at 17:05 -0500, Alex Stewart wrote:
> On 11/4/21 09:35, Mikko Rapeli wrote:
> > On Thu, Nov 04, 2021 at 02:02:57PM +, Richard Purdie wrote:
> > > Combining :append with += rarely makes sense. Improve it to use the 
> > > standard
> > > format (and tweak the implied spacing).
> > Maybe I'm silly but I find :append with += safer to do than manually 
> > remembring
> > to add the space character.
> 
> I tend to agree; hence why I wrote it that way in the original patch. 
> But I'm not going to defend the practice in this case, so ACK from me 
> either way.

There is a patch on the bitbake list which would make this usage a warning. It
certainly isn't obvious to most new users that:

YYY:append += "XXX"

really means

YYY:append = " XXX"

so I tend to prefer the later as being much clearer about what is happening.
Part of what we need to to improve usability is to remove some of these
confusions so standardising on things like this seems to make sense.

> I'm intending to drop this recipe warning after the opkg_0.5.0 release 
> in December. So the recipe-as-written will only exist in the mainline 
> for another few months.

Sounds good.

Cheers,

Richard




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157878): 
https://lists.openembedded.org/g/openembedded-core/message/157878
Mute This Topic: https://lists.openembedded.org/mt/86816265/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] opkg: Fix poor operator combination choice

2021-11-04 Thread Alex Stewart



On 11/4/21 09:35, Mikko Rapeli wrote:

On Thu, Nov 04, 2021 at 02:02:57PM +, Richard Purdie wrote:

Combining :append with += rarely makes sense. Improve it to use the standard
format (and tweak the implied spacing).

Maybe I'm silly but I find :append with += safer to do than manually remembring
to add the space character.


I tend to agree; hence why I wrote it that way in the original patch. 
But I'm not going to defend the practice in this case, so ACK from me 
either way.


I'm intending to drop this recipe warning after the opkg_0.5.0 release 
in December. So the recipe-as-written will only exist in the mainline 
for another few months.



Signed-off-by: Richard Purdie 
---
  meta/recipes-devtools/opkg/opkg_0.4.5.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/opkg/opkg_0.4.5.bb 
b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
index 2760fc58786..8af047a51ff 100644
--- a/meta/recipes-devtools/opkg/opkg_0.4.5.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
@@ -60,7 +60,7 @@ do_install_ptest () {
sed -i -e '/@PYTHONPATH=. $(PYTHON) $^/a\\t@if [ "$$?" != "0" ];then echo 
"FAIL:"$^;else echo "PASS:"$^;fi' ${D}${PTEST_PATH}/tests/Makefile
  }
  
-WARN_QA:append += "openssl-deprecation"

+WARN_QA:append = " openssl-deprecation"
  QAPKGTEST[openssl-deprecation] = "package_qa_check_openssl_deprecation"
  def package_qa_check_openssl_deprecation (package, d, messages):
  sane = True
--
2.32.0





Thanks,

--
Alex Stewart
Software Engineer - NI Real-Time OS
NI (National Instruments)

alex.stew...@ni.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157877): 
https://lists.openembedded.org/g/openembedded-core/message/157877
Mute This Topic: https://lists.openembedded.org/mt/86816265/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 0/3] SPDX: Add annotations to relationship

2021-11-04 Thread Joshua Watt



On 11/4/21 3:50 PM, Richard Purdie wrote:

On Thu, 2021-11-04 at 15:45 -0500, Joshua Watt wrote:

On 11/4/21 3:43 PM, Richard Purdie wrote:

On Thu, 2021-11-04 at 20:00 +, Jose Quaresma wrote:

Richard Purdie  escreveu no dia quinta,
28/10/2021 à(s) 21:58:

On Thu, 2021-10-28 at 08:47 -1000, Steve Sakoman wrote:

On Tue, Oct 26, 2021 at 10:41 PM Jose Quaresma 

wrote:

Hi all,

There are any plans or is it possible to backport the SBOM/SPDX to the

dunfell branch?

I'm going to yield to Saul as to whether he thinks this is
desirable/possible or not.

The packagedata changes are pretty invasive unfortunately and likely not
something you're going to want in dunfell sadly.


Thanks for the clarification.


I have been thinking a bit more about this. I did wonder if we should consider a
mixin layer of some kind for it that could work with dunfell?

We could host it, it is just a question of writing the mixin layer and
maintaining it.

I don't think it's going to be possible with a pure mixin layer, since
it relies on the extended package data?

I suspect that could perhaps be patched in through a layer though? You might
choose to drop the compression piece or do it differently for the backport?



I'm not sure if a layer could hook in well enough to get the data 
needed...  maybe worth an experiment though



With a backport, I would probably either use GZip compression or no 
compression. The zstd compression was designed as a drop in replacement 
for Gzip if we wanted to go that route.




Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157876): 
https://lists.openembedded.org/g/openembedded-core/message/157876
Mute This Topic: https://lists.openembedded.org/mt/86616599/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 0/6] kernel: consolidated pull request

2021-11-04 Thread Khem Raj




On 11/4/21 12:48 PM, Bruce Ashfield wrote:

From: Bruce Ashfield 

Richard,

Here's a broad set of kernel updates:

  - stable for 5.14
  - stable for 5.10

And then the bigger, a way earlier than normal:

  - libc-headers bump to 5.15
  - 5.15 reference kernel recipes

As everyone has probably heard, 5.15 is the next kernel LTS, so I
wanted to establish it for the next release earlier than normal. Due
to the -dev testing, things like lttng, perf and devsrc are already
ready to go, so this is a smaller pull request than normal.

I had to fixup strace, and the vboxguest drivers (patch sent to
meta-oe)

I've run it through the AB and everything came back green, as well
as my local testing.

This isn't the default for any of the machines yet (but I have
local patches for that as well). The h/w reference boards
stil use 5.14 and need to be updated, but the plan is to remove 5.14,
and eventually 5.10 from master, and we'll go with 5.15, and 5.16+
in the spring 2022 release.


also 5.10 ? I think there perhaps will be enough folks needing 5.10 
Since next YP release is also LTS, I wonder if we should keep kernel 
UAPIs as a LTS kernel too.




Cheers,

Bruce

The following changes since commit 3e9c4801216111496acffdfdccf1deae3b3d6b96:

   insane.bbclass: Add a check for directories that are expected to be empty 
(2021-11-03 11:12:26 +)

are available in the Git repository at:

   git://git.yoctoproject.org/poky-contrib zedd/kernel
   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (6):
   linux-yocto/5.14: update to v5.14.15
   linux-yocto/5.10: update to v5.10.76
   linux-libc-headers: update to v5.15
   linux-yocto-rt/5.10: update to -rt54
   linux-yocto/5.15: introduce recipes
   strace: fix build against 5.15 kernel/kernel-headers

  meta/conf/distro/include/tcmode-default.inc   |   2 +-
  ...1-Avoid-relying-on-presence-of-ipx.h.patch | 151 ++
  meta/recipes-devtools/strace/strace_5.14.bb   |   1 +
  ...ers_5.14.bb => linux-libc-headers_5.15.bb} |   4 +-
  .../linux/linux-yocto-rt_5.10.bb  |   6 +-
  .../linux/linux-yocto-rt_5.14.bb  |   6 +-
  .../linux/linux-yocto-rt_5.15.bb  |  45 ++
  .../linux/linux-yocto-tiny_5.10.bb|   8 +-
  .../linux/linux-yocto-tiny_5.14.bb|   8 +-
  .../linux/linux-yocto-tiny_5.15.bb|  32 
  meta/recipes-kernel/linux/linux-yocto_5.10.bb |  24 +--
  meta/recipes-kernel/linux/linux-yocto_5.14.bb |  26 +--
  meta/recipes-kernel/linux/linux-yocto_5.15.bb |  68 
  13 files changed, 339 insertions(+), 42 deletions(-)
  create mode 100644 
meta/recipes-devtools/strace/strace/0001-Avoid-relying-on-presence-of-ipx.h.patch
  rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb => 
linux-libc-headers_5.15.bb} (81%)
  create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
  create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
  create mode 100644 meta/recipes-kernel/linux/linux-yocto_5.15.bb






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157875): 
https://lists.openembedded.org/g/openembedded-core/message/157875
Mute This Topic: https://lists.openembedded.org/mt/86824892/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 0/3] SPDX: Add annotations to relationship

2021-11-04 Thread Richard Purdie

On Thu, 2021-11-04 at 15:45 -0500, Joshua Watt wrote:
> On 11/4/21 3:43 PM, Richard Purdie wrote:
> > On Thu, 2021-11-04 at 20:00 +, Jose Quaresma wrote:
> > > 
> > > Richard Purdie  escreveu no dia 
> > > quinta,
> > > 28/10/2021 à(s) 21:58:
> > > > On Thu, 2021-10-28 at 08:47 -1000, Steve Sakoman wrote:
> > > > > On Tue, Oct 26, 2021 at 10:41 PM Jose Quaresma 
> > > > > 
> > > > wrote:
> > > > > > Hi all,
> > > > > > 
> > > > > > There are any plans or is it possible to backport the SBOM/SPDX to 
> > > > > > the
> > > > dunfell branch?
> > > > > I'm going to yield to Saul as to whether he thinks this is
> > > > > desirable/possible or not.
> > > > The packagedata changes are pretty invasive unfortunately and likely not
> > > > something you're going to want in dunfell sadly.
> > > > 
> > > 
> > > Thanks for the clarification.
> > > 
> > I have been thinking a bit more about this. I did wonder if we should 
> > consider a
> > mixin layer of some kind for it that could work with dunfell?
> > 
> > We could host it, it is just a question of writing the mixin layer and
> > maintaining it.
> 
> I don't think it's going to be possible with a pure mixin layer, since 
> it relies on the extended package data?

I suspect that could perhaps be patched in through a layer though? You might
choose to drop the compression piece or do it differently for the backport?

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157874): 
https://lists.openembedded.org/g/openembedded-core/message/157874
Mute This Topic: https://lists.openembedded.org/mt/86616599/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 0/3] SPDX: Add annotations to relationship

2021-11-04 Thread Joshua Watt



On 11/4/21 3:43 PM, Richard Purdie wrote:

On Thu, 2021-11-04 at 20:00 +, Jose Quaresma wrote:


Richard Purdie  escreveu no dia quinta,
28/10/2021 à(s) 21:58:

On Thu, 2021-10-28 at 08:47 -1000, Steve Sakoman wrote:

On Tue, Oct 26, 2021 at 10:41 PM Jose Quaresma 

wrote:

Hi all,

There are any plans or is it possible to backport the SBOM/SPDX to the

dunfell branch?

I'm going to yield to Saul as to whether he thinks this is
desirable/possible or not.

The packagedata changes are pretty invasive unfortunately and likely not
something you're going to want in dunfell sadly.



Thanks for the clarification.


I have been thinking a bit more about this. I did wonder if we should consider a
mixin layer of some kind for it that could work with dunfell?

We could host it, it is just a question of writing the mixin layer and
maintaining it.


I don't think it's going to be possible with a pure mixin layer, since 
it relies on the extended package data?





Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157873): 
https://lists.openembedded.org/g/openembedded-core/message/157873
Mute This Topic: https://lists.openembedded.org/mt/86616599/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 0/3] SPDX: Add annotations to relationship

2021-11-04 Thread Richard Purdie

On Thu, 2021-11-04 at 20:00 +, Jose Quaresma wrote:
> 
> 
> Richard Purdie  escreveu no dia quinta,
> 28/10/2021 à(s) 21:58:
> > On Thu, 2021-10-28 at 08:47 -1000, Steve Sakoman wrote:
> > > On Tue, Oct 26, 2021 at 10:41 PM Jose Quaresma 
> > wrote:
> > > > 
> > > > Hi all,
> > > > 
> > > > There are any plans or is it possible to backport the SBOM/SPDX to the
> > dunfell branch?
> > > 
> > > I'm going to yield to Saul as to whether he thinks this is
> > > desirable/possible or not.
> > 
> > The packagedata changes are pretty invasive unfortunately and likely not
> > something you're going to want in dunfell sadly.
> > 
> 
> 
> Thanks for the clarification.
> 

I have been thinking a bit more about this. I did wonder if we should consider a
mixin layer of some kind for it that could work with dunfell?

We could host it, it is just a question of writing the mixin layer and
maintaining it.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157872): 
https://lists.openembedded.org/g/openembedded-core/message/157872
Mute This Topic: https://lists.openembedded.org/mt/86616599/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] patch.bbclass: don't repr() the exception, use str()

2021-11-04 Thread Jose Quaresma

Richard Purdie  escreveu no dia terça,
2/11/2021 à(s) 12:36:

> On Tue, 2021-11-02 at 12:26 +, Ross Burton wrote:
> > repr() results in formatting characters such as extra quotation marks
> > which are pointless.
> >
> > Signed-off-by: Ross Burton 
> > ---
> >  meta/classes/patch.bbclass | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/patch.bbclass b/meta/classes/patch.bbclass
> > index 8de7025491..079ee33e3c 100644
> > --- a/meta/classes/patch.bbclass
> > +++ b/meta/classes/patch.bbclass
> > @@ -155,7 +155,7 @@ python patch_do_patch() {
> >  resolver.Resolve()
> >  except bb.BBHandledException as e:
> >  bb.utils.remove(process_tmpdir, True)
> > -bb.fatal("Applying patch '%s' on target directory '%s'\n%s"
> % (parm['patchname'], patchdir, repr(e).replace("\\n", "\n")))
>

Replace the "str(e)" with "repr(e).replace("\\n", "\n")" is a bit ugly, can
this be moved to bb.utils or something like that?

> +bb.fatal("Applying patch '%s' on target directory '%s'\n%s"
> % (parm['patchname'], patchdir, str(e).replace("\\n", "\n")))
> >
> >  bb.utils.remove(process_tmpdir, True)
> >  del os.environ['TMPDIR']
>
> Full circle:
>
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=ec6edfc27f2cfa990dd0f8b2bbc6f9472a50a839
>
> :(
>
> (the original issue being that str(e) on exceptions can hide a lot of
> useful
> info)
>
> Cheers,
>
> Richard
>
>
> 
>
>

-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157871): 
https://lists.openembedded.org/g/openembedded-core/message/157871
Mute This Topic: https://lists.openembedded.org/mt/86764324/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 0/3] SPDX: Add annotations to relationship

2021-11-04 Thread Jose Quaresma

Richard Purdie  escreveu no dia quinta,
28/10/2021 à(s) 21:58:

> On Thu, 2021-10-28 at 08:47 -1000, Steve Sakoman wrote:
> > On Tue, Oct 26, 2021 at 10:41 PM Jose Quaresma 
> wrote:
> > >
> > > Hi all,
> > >
> > > There are any plans or is it possible to backport the SBOM/SPDX to the
> dunfell branch?
> >
> > I'm going to yield to Saul as to whether he thinks this is
> > desirable/possible or not.
>
> The packagedata changes are pretty invasive unfortunately and likely not
> something you're going to want in dunfell sadly.
>

Thanks for the clarification.


>
> Cheers,
>
> Richard
>
>

-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157870): 
https://lists.openembedded.org/g/openembedded-core/message/157870
Mute This Topic: https://lists.openembedded.org/mt/86616599/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 1/2] sstate.bbclass: exceptions on mirror fetcher is not fatal

2021-11-04 Thread Jose Quaresma

Richard Purdie  escreveu no dia sábado,
30/10/2021 à(s) 22:34:

> On Sat, 2021-10-30 at 00:13 +0100, Jose Quaresma wrote:
> > An exceptions in sstate_checkhashes sstate mirror fetcher
> > is not fatal for the build and it can be a warning.
> >
> > If we can't check status in the fetcher we can assume that sstate
> > file don't exist on the mirror and build it from sources, ignoring
> > the sstate cache.
> >
> > Signed-off-by: Jose Quaresma 
> > ---
> >  meta/classes/sstate.bbclass | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
> > index 6e4eb09f8e..54d38ed42d 100644
> > --- a/meta/classes/sstate.bbclass
> > +++ b/meta/classes/sstate.bbclass
> > @@ -995,7 +995,7 @@ def sstate_checkhashes(sq_data, d, siginfo=False,
> currentcount=0, summary=True,
> >  missed.add(tid)
> >  bb.debug(2, "SState: Unsuccessful fetch test for %s
> (%s)" % (srcuri, e))
> >  except Exception as e:
> > -bb.error("SState: cannot test %s: %s" % (srcuri, e))
> > +bb.warn("SState: cannot test file %s from mirrors '%s':
> (%s)" % (srcuri, mirrors, e))
> >  if len(tasklist) >= min_tasks:
> >  bb.event.fire(bb.event.ProcessProgress(msg,
> len(tasklist) - thread_worker.tasks.qsize()), d)
> >
>
> This has been discussed a bit before. Whilst the issue isn't fatal to the
> build
> I do think this should be an error and have bitbake return an exit code
> that
> there was an issue as there is something wrong somewhere if we're hitting
> this
> code path.
>
> As an example:
>
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/4230/steps/15/logs/stdio
>
> which might have not shown up if it wasn't an error.
>
>
I was not aware that this subject had already been discussed.
But it makes sense that when we have the sstate mirrors, if we can't
communicate with the server we have a problem.

My assumption in this patch can hide these issues as it will always build
from the sources and the warning can go unnoticed.

Cheers,
>
> Richard
>
>
>
>

-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157869): 
https://lists.openembedded.org/g/openembedded-core/message/157869
Mute This Topic: https://lists.openembedded.org/mt/86689304/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 6/6] strace: fix build against 5.15 kernel/kernel-headers

2021-11-04 Thread Bruce Ashfield

From: Bruce Ashfield 

kernel 5.15 removed ipx.h from the uapi, but strace hasn't adjusted
its tests to the removal.

There is a WIP patch on the esyr/5.15 branch that solves the problem,
so we grab it here, adjust for context and fix our build problem.

When strace updates to 5.15, and we can bump our version and drop
this patch.

Upstream-Status: Backport [commit cca828197c0e16c2599129114]

Signed-off-by: Bruce Ashfield 
---
 ...1-Avoid-relying-on-presence-of-ipx.h.patch | 151 ++
 meta/recipes-devtools/strace/strace_5.14.bb   |   1 +
 2 files changed, 152 insertions(+)
 create mode 100644 
meta/recipes-devtools/strace/strace/0001-Avoid-relying-on-presence-of-ipx.h.patch

diff --git 
a/meta/recipes-devtools/strace/strace/0001-Avoid-relying-on-presence-of-ipx.h.patch
 
b/meta/recipes-devtools/strace/strace/0001-Avoid-relying-on-presence-of-ipx.h.patch
new file mode 100644
index 00..6df673fa95
--- /dev/null
+++ 
b/meta/recipes-devtools/strace/strace/0001-Avoid-relying-on-presence-of-ipx.h.patch
@@ -0,0 +1,151 @@
+From 197f712ea96c12dcabc9fe98889a425d61ad6a60 Mon Sep 17 00:00:00 2001
+From: Eugene Syromyatnikov 
+Date: Wed, 3 Nov 2021 00:48:59 +0100
+Subject: [PATCH] Avoid relying on presence of ipx.h
+
+After Linux has broken UAPI in commit v5.15-rc1~157^2~207, it is well
+possible that neither kernel nor libc (such as musl, for example)
+provide IPX-related header.  Avoid relying on its presence
+in the strace's code and conditionalise the relevant checks in the tests.
+
+* configure.ac (AC_CHECK_HEADERS): Add linux/ipx.h.
+* src/net.c: Remove / includes.
+* src/sockaddr.c: Likewise.
+(IPX_NODE_LEN): New macro constant.
+(struct sockaddr_ipx): New type definition.
+* src/xlat/sock_ipx_options.in (IPX_TYPE): Provide a fallback value.
+* tests/net-sockaddr.c [!HAVE_LINUX_IPX_H]: Do not include
+.
+[!HAVE_LINUX_IPX_H && HAVE_NETIPX_IPX_H]: Include .
+[!(HAVE_LINUX_IPX_H || defined HAVE_NETIPX_IPX_H)]: Do not define
+check_ipx.
+[!(HAVE_LINUX_IPX_H || defined HAVE_NETIPX_IPX_H)] (main): Do not call
+check_ipx.
+
+Closes: https://github.com/strace/strace/issues/201
+
+Upstream-Status: backport [commit cca828197c0e1 branch esyr/5.15]
+
+[bva: changed context to apply to a released strace 5.14 tarball]
+Signed-off-by: Bruce Ashfield 
+
+---
+ configure.ac |  1 +
+ src/net.c|  5 -
+ src/sockaddr.c   | 16 ++--
+ src/xlat/sock_ipx_options.in |  2 +-
+ tests/net-sockaddr.c | 10 +-
+ 5 files changed, 21 insertions(+), 13 deletions(-)
+
+Index: strace-5.14/configure.ac
+===
+--- strace-5.14.orig/configure.ac
 strace-5.14/configure.ac
+@@ -423,6 +423,7 @@
+   elf.h
+   gcov.h
+   iconv.h
++  linux/ipx.h
+   mqueue.h
+   netinet/sctp.h
+   netipx/ipx.h
+Index: strace-5.14/src/net.c
+===
+--- strace-5.14.orig/src/net.c
 strace-5.14/src/net.c
+@@ -28,11 +28,6 @@
+ #include 
+ #include 
+ #include 
+-#ifdef HAVE_NETIPX_IPX_H
+-# include 
+-#else
+-# include 
+-#endif
+ 
+ #include 
+ #include "netlink.h"
+Index: strace-5.14/src/sockaddr.c
+===
+--- strace-5.14.orig/src/sockaddr.c
 strace-5.14/src/sockaddr.c
+@@ -24,12 +24,6 @@
+ #include 
+ #include 
+ 
+-#ifdef HAVE_NETIPX_IPX_H
+-# include 
+-#else
+-# include 
+-#endif
+-
+ #include "xlat/addrfams.h"
+ #include "xlat/arp_hardware_types.h"
+ #include "xlat/ethernet_protocols.h"
+@@ -45,6 +39,16 @@
+ const size_t arp_hardware_types_size = ARRAY_SIZE(arp_hardware_types) - 1;
+ const size_t ethernet_protocols_size = ARRAY_SIZE(ethernet_protocols) - 1;
+ 
++#define IPX_NODE_LEN  6
++struct sockaddr_ipx {
++  uint16_t sipx_family;
++  uint16_t sipx_port;
++  uint32_t sipx_network;
++  unsigned char sipx_node[IPX_NODE_LEN];
++  uint8_t sipx_type;
++  unsigned char sipx_zero;
++};
++
+ static void
+ print_sockaddr_data_un(struct tcb *tcp, const void *const buf, const int 
addrlen)
+ {
+Index: strace-5.14/src/xlat/sock_ipx_options.in
+===
+--- strace-5.14.orig/src/xlat/sock_ipx_options.in
 strace-5.14/src/xlat/sock_ipx_options.in
+@@ -1 +1 @@
+-IPX_TYPE
++IPX_TYPE  1
+Index: strace-5.14/tests/net-sockaddr.c
+===
+--- strace-5.14.orig/tests/net-sockaddr.c
 strace-5.14/tests/net-sockaddr.c
+@@ -24,7 +24,11 @@
+ #include 
+ #include 
+ #include 
+-#include 
++#if defined HAVE_LINUX_IPX_H
++# include 
++#elif defined HAVE_NETIPX_IPX_H
++# include 
++#endif
+ #ifdef HAVE_BLUETOOTH_BLUETOOTH_H
+ # include 
+ # include 
+@@ -269,6 +273,7 @@
+   printf("connect(-1, %p, %u) = %d EBADF (%m)\n", in6, len, ret);
+ }
+ 
++#if defined HAVE_LINUX_IPX_H || defined HAVE_NETIPX_IPX_H
+ static void
+

[OE-core] [PATCH 5/6] linux-yocto/5.15: introduce recipes

2021-11-04 Thread Bruce Ashfield

From: Bruce Ashfield 

The 5.15 kernel will be a LTS release, so we introduce our reference
recipes to track the release.

We have some configuration tweaks for the final 5.15 release, but this
is otherwise the same as the kernel that was tested in linux-yocto-dev.

Signed-off-by: Bruce Ashfield 
---
 .../linux/linux-yocto-rt_5.15.bb  | 45 
 .../linux/linux-yocto-tiny_5.15.bb| 32 +
 meta/recipes-kernel/linux/linux-yocto_5.15.bb | 68 +++
 3 files changed, 145 insertions(+)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_5.15.bb

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
new file mode 100644
index 00..81440b65fa
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
@@ -0,0 +1,45 @@
+KBRANCH ?= "v5.15/standard/preempt-rt/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# Skip processing of this recipe if it is not explicitly specified as the
+# PREFERRED_PROVIDER for virtual/kernel. This avoids errors when trying
+# to build multiple virtual/kernel providers, e.g. as dependency of
+# core-image-rt-sdk, core-image-rt.
+python () {
+if d.getVar("KERNEL_PACKAGE_NAME") == "kernel" and 
d.getVar("PREFERRED_PROVIDER_virtual/kernel") != "linux-yocto-rt":
+raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
+}
+
+SRCREV_machine ?= "a4b3abf4d96d765bea92af652d8ae020c365d46a"
+SRCREV_meta ?= "177a773f3c223d057e34cd341268d2656b89ea01"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}"
+
+LINUX_VERSION ?= "5.15"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
+
+DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
+DEPENDS += "openssl-native util-linux-native"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "1"
+
+LINUX_KERNEL_TYPE = "preempt-rt"
+
+COMPATIBLE_MACHINE = 
"(qemux86|qemux86-64|qemuarm|qemuarmv5|qemuarm64|qemuppc|qemumips)"
+
+KERNEL_DEVICETREE:qemuarmv5 = "versatile-pb.dtb"
+
+# Functionality flags
+KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
features/taskstats/taskstats.scc"
+KERNEL_FEATURES:append = " ${KERNEL_EXTRA_FEATURES}"
+KERNEL_FEATURES:append:qemuall=" cfg/virtio.scc 
features/drm-bochs/drm-bochs.scc"
+KERNEL_FEATURES:append:qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES:append:qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
+KERNEL_FEATURES:append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/scsi/scsi-debug.scc", "", d)}"
+KERNEL_FEATURES:append = "${@bb.utils.contains("DISTRO_FEATURES", "ptest", " 
features/gpio/mockup.scc", "", d)}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
new file mode 100644
index 00..b2bd8e070c
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
@@ -0,0 +1,32 @@
+KBRANCH ?= "v5.15/standard/tiny/base"
+KBRANCH:qemuarm  ?= "v5.15/standard/tiny/arm-versatile-926ejs"
+
+LINUX_KERNEL_TYPE = "tiny"
+KCONFIG_MODE = "--allnoconfig"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+LINUX_VERSION ?= "5.15"
+LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
+
+DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
+DEPENDS += "openssl-native util-linux-native"
+
+KMETA = "kernel-meta"
+KCONF_BSP_AUDIT_LEVEL = "2"
+
+SRCREV_machine:qemuarm ?= "5fbef884c98a51679ab4ab566568b1e89123c011"
+SRCREV_machine ?= "a4b3abf4d96d765bea92af652d8ae020c365d46a"
+SRCREV_meta ?= "177a773f3c223d057e34cd341268d2656b89ea01"
+
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
+   
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}"
+
+COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm|qemuarmv5"
+
+# Functionality flags
+KERNEL_FEATURES = ""
+
+KERNEL_DEVICETREE:qemuarmv5 = "versatile-pb.dtb"
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
new file mode 100644
index 00..e45208e436
--- /dev/null
+++ b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
@@ -0,0 +1,68 @@
+KBRANCH ?= "v5.15/standard/base"
+
+require recipes-kernel/linux/linux-yocto.inc
+
+# board specific branches
+KBRANCH:qemuarm  ?= "v5.15/standard/arm-versatile-926ejs"
+KBRANCH:qemuarm64 ?= "v5.15/standard/qemuarm64"
+KBRANCH:qemumips ?= "v5.15/standard/mti-malta32"
+KBRANCH:qemuppc  ?= "v5.15/standard/qemuppc"
+KBRANCH:qemuriscv64  ?=

[OE-core] [PATCH 4/6] linux-yocto-rt/5.10: update to -rt54

2021-11-04 Thread Bruce Ashfield

From: Bruce Ashfield 

Integrating the following commit(s) to linux-yocto-rt/5.10:

f01089784fd6 Linux 5.10.73-rt54
f34df8f3c666 Linux 5.10.65-rt53
271c5e6e4064 Linux 5.10.59-rt52
1a4bba4bc32c locking/rwsem-rt: Remove might_sleep() in __up_read()
ff591a2bdcfb Linux 5.10.59-rt51
8d185ac23c11 Linux 5.10.58-rt50
2c0fd44153f5 Linux 5.10.56-rt49
8b083d3c993c printk: Enhance the condition check of msleep in pr_flush()
448cd29e3bc9 Linux 5.10.56-rt48

Signed-off-by: Bruce Ashfield 
---
 meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
index 34bb95e4fc..c210667350 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.10.bb
@@ -11,7 +11,7 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "f7d2419be110c618b74cbaddaafbabf4a886b91b"
+SRCREV_machine ?= "f01089784fd6234111851aad756297e0f258276c"
 SRCREV_meta ?= "e1979ceb171bc91ef2cb71cfcde548a101dab687"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157866): 
https://lists.openembedded.org/g/openembedded-core/message/157866
Mute This Topic: https://lists.openembedded.org/mt/86824896/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/6] linux-yocto/5.10: update to v5.10.76

2021-11-04 Thread Bruce Ashfield

From: Bruce Ashfield 

Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:

378e85d1aeb5 Linux 5.10.76
cfa79faf7e1f pinctrl: stm32: use valid pin identifier in 
stm32_pinctrl_resume()
c56c801391c3 ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
d088db8637bb selftests: bpf: fix backported ASSERT_FALSE
3a845fa00fd7 e1000e: Separate TGP board type from SPT
021b6d11e590 tracing: Have all levels of checks prevent recursion
3a0dc2e35a5d net: mdiobus: Fix memory leak in __mdiobus_register
cfe9266213c4 bpf, test, cgroup: Use sk_{alloc,free} for test cases
188907c25218 s390/pci: fix zpci_zdev_put() on reserve
f18b90e9366f can: isotp: isotp_sendmsg(): fix TX buffer concurrent access 
in isotp_sendmsg()
2304dfb548a4 scsi: core: Fix shost->cmd_per_lun calculation in 
scsi_add_host_with_dma()
c58654f344dd net: hns3: fix for miscalculation of rx unused desc
96fe5061291d sched/scs: Reset the shadow stack when idle_task_exit
96f0aebf29be scsi: qla2xxx: Fix a memory leak in an error path of 
qla2x00_process_els()
90c8e8c0829b scsi: iscsi: Fix set_param() handling
0eb254479685 Input: snvs_pwrkey - add clk handling
ea9c1f5d8a3a perf/x86/msr: Add Sapphire Rapids CPU support
7a5a1f09c8b4 libperf tests: Fix test_stat_cpu
e56a3e7ae353 ALSA: hda: avoid write to STATESTS if controller is in reset
85c8d8c1609d platform/x86: intel_scu_ipc: Update timeout value in comment
9f591cbdbed3 isdn: mISDN: Fix sleeping function called from invalid context
ab4f542b515b ARM: dts: spear3xx: Fix gmac node
15d3ad79885b net: stmmac: add support for dwmac 3.40a
f9d16a428489 btrfs: deal with errors when checking if a dir entry exists 
during log replay
369db2a91d5c ALSA: hda: intel: Allow repeatedly probing on codec 
configuration errors
81d8e70cdce4 gcc-plugins/structleak: add makefile var for disabling 
structleak
69078a94365a net: hns3: fix the max tx size according to user manual
f40c2281d2c0 drm: mxsfb: Fix NULL pointer dereference crash on unload
96835b68d7b3 net: bridge: mcast: use multicast_membership_interval for 
IGMPv3
0e033cb40761 selftests: netfilter: remove stray bash debug line
f8a6541345c2 netfilter: Kconfig: use 'default y' instead of 'm' for bool 
config option
7f221ccbee4e isdn: cpai: check ctr->cnr to avoid array index out of bound
77c0ef979e32 nfc: nci: fix the UAF of rf_conn_info object
8f042315fcc4 KVM: nVMX: promptly process interrupts delivered while in 
guest mode
b41fd8f5d2ad mm, slub: fix incorrect memcg slab count for bulk free
568f906340b4 mm, slub: fix potential memoryleak in kmem_cache_open()
48843dd23c7b mm, slub: fix mismatch between reconstructed freelist depth 
and cnt
c5c2a80368e9 powerpc/idle: Don't corrupt back chain when going idle
197ec50b2df1 KVM: PPC: Book3S HV: Make idle_kvm_start_guest() return 0 if 
it went to guest
fbd724c49bea KVM: PPC: Book3S HV: Fix stack handling in 
idle_kvm_start_guest()
9258f58432c5 powerpc64/idle: Fix SP offsets when saving GPRs
3e16d9d525a7 net: dsa: mt7530: correct ds->num_ports
16802fa4c33e audit: fix possible null-pointer dereference in 
audit_filter_rules
0d867a359979 ASoC: DAPM: Fix missing kctl change notifications
a2606acf418e ALSA: hda/realtek: Add quirk for Clevo PC50HS
6411397b6d7a ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
b721500c979b vfs: check fd has read access in kernel_read_file_from_fd()
895ceeff31b1 elfcore: correct reference to CONFIG_UML
3cda4bfffd4f userfaultfd: fix a race between writeprotect and exit_mmap()
93be0eeea14c ocfs2: mount fails with buffer overflow in strlen
f1b98569e81c ocfs2: fix data corruption after conversion from inline format
1727e8688d2e ceph: fix handling of "meta" errors
603d4bcc0fcd ceph: skip existing superblocks that are blocklisted or shut 
down when mounting
d48db508f911 can: j1939: j1939_xtp_rx_rts_session_new(): abort TP less than 
9 bytes
5abc9b9d3ca5 can: j1939: j1939_xtp_rx_dat_one(): cancel session if receive 
TP.DT with error length
864e1a24 can: j1939: j1939_netdev_start(): fix UAF for rx_kref of 
j1939_priv
ecfccb1c58c9 can: j1939: j1939_tp_rxtimer(): fix errant alert in 
j1939_tp_rxtimer
053bc12df0d6 can: isotp: isotp_sendmsg(): add result check for 
wait_event_interruptible()
0917fb04069a can: isotp: isotp_sendmsg(): fix return error on FC timeout on 
TX path
28f28e4bc3a5 can: peak_pci: peak_pci_remove(): fix UAF
9697ad6395f9 can: peak_usb: pcan_usb_fd_decode_status(): fix back to 
ERROR_ACTIVE state notification
4758e92e75ca can: rcar_can: fix suspend/resume
4a0928c3ebca net: enetc: fix ethtool counter name for PM0_TERR
00ad7a015409 drm/panel: ilitek-ili9881c: Fix sync for Feixin K101-IM2BYL02 
panel
eccd00728b1a ice: Add missing E810 device ids
6418508a3ac2 e1000e: Fix packet loss on Tiger Lake and

[OE-core] [PATCH 3/6] linux-libc-headers: update to v5.15

2021-11-04 Thread Bruce Ashfield

From: Bruce Ashfield 

No patches needed refreshing or removal, so we just update the
SRC_URI and pick up the latest uapi / kernel headers.

Signed-off-by: Bruce Ashfield 
---
 meta/conf/distro/include/tcmode-default.inc   | 2 +-
 ...{linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb => 
linux-libc-headers_5.15.bb} (81%)

diff --git a/meta/conf/distro/include/tcmode-default.inc 
b/meta/conf/distro/include/tcmode-default.inc
index 58f49800c4..86a6b50433 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -21,7 +21,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
 BINUVERSION ?= "2.37%"
 GDBVERSION ?= "10.%"
 GLIBCVERSION ?= "2.34"
-LINUXLIBCVERSION ?= "5.14%"
+LINUXLIBCVERSION ?= "5.15%"
 QEMUVERSION ?= "6.1%"
 GOVERSION ?= "1.16%"
 # This can not use wildcards like 8.0.% since it is also used in mesa to denote
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb 
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
similarity index 81%
rename from meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
rename to meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
index 282c04d79c..588cc3acd1 100644
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
@@ -14,7 +14,7 @@ SRC_URI:append = "\
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
 
-SRC_URI[md5sum] = "a082ef5748b813abca0649dab8be5f52"
-SRC_URI[sha256sum] = 
"7e068b5e0d26a62b10e5320b25dce57588cbbc6f781c090442138c9c9c3271b2"
+SRC_URI[md5sum] = "071d49ff4e020d58c04f9f3f76d3b594"
+SRC_URI[sha256sum] = 
"57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8"
 
 
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157865): 
https://lists.openembedded.org/g/openembedded-core/message/157865
Mute This Topic: https://lists.openembedded.org/mt/86824895/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 1/6] linux-yocto/5.14: update to v5.14.15

2021-11-04 Thread Bruce Ashfield

From: Bruce Ashfield 

Updating linux-yocto/5.14 to the latest korg -stable release that comprises
the following commits:

b46092c7497e Linux 5.14.15
96e4ea34f6d7 pinctrl: stm32: use valid pin identifier in 
stm32_pinctrl_resume()
4850e9e3c6a3 ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
80344938e468 e1000e: Separate TGP board type from SPT
0c4e87ba11eb net: mdiobus: Fix memory leak in __mdiobus_register
2f4356963624 bpf, test, cgroup: Use sk_{alloc,free} for test cases
4e5d794a2743 s390/pci: fix zpci_zdev_put() on reserve
e27170d5f2fc s390/pci: cleanup resources only if necessary
2be38f02ec89 scsi: core: Fix shost->cmd_per_lun calculation in 
scsi_add_host_with_dma()
ff261f9aa654 autofs: fix wait name hash calculation in autofs_wait()
1009f098dfbe drm/kmb: Limit supported mode to 1080p
217d42e8b835 drm/kmb: Enable alpha blended second plane
c1ad040dbea8 net/mlx5: Lag, change multipath and bonding to be mutually 
exclusive
d2ec7d208d8e net/mlx5: Lag, move lag destruction to a workqueue
42b6431f1c17 net: hns3: fix for miscalculation of rx unused desc
f1972f14f16e sched/scs: Reset the shadow stack when idle_task_exit
c4813d308517 mm/thp: decrease nr_thps in file's mapping on THP split
a7fbb56e6c94 scsi: qla2xxx: Fix a memory leak in an error path of 
qla2x00_process_els()
c8c1b2183fb8 scsi: mpi3mr: Fix duplicate device entries when scanning 
through sysfs
ce527668277c scsi: storvsc: Fix validation for unsolicited incoming packets
08d82a9b65e7 scsi: iscsi: Fix set_param() handling
6408a4c8da2f ASoC: codec: wcd938x: Add irq config support
9eb2aaede632 Input: snvs_pwrkey - add clk handling
9dd0389d77b9 perf/x86/msr: Add Sapphire Rapids CPU support
11d6811cbde0 libperf tests: Fix test_stat_cpu
65eec1fb58c1 libperf test evsel: Fix build error on !x86 architectures
b6062308c510 spi-mux: Fix false-positive lockdep splats
722ef19a161c spi: Fix deadlock when adding SPI controllers on SPI buses
785d69099ef4 ALSA: hda: avoid write to STATESTS if controller is in reset
3972b03ed085 platform/x86: intel_scu_ipc: Update timeout value in comment
6659008140b4 platform/x86: intel_scu_ipc: Increase virtual timeout to 10s
f5966ba53013 isdn: mISDN: Fix sleeping function called from invalid context
ef24577a52ba ARM: dts: spear3xx: Fix gmac node
834cc3fc2b99 net: stmmac: add support for dwmac 3.40a
0c878175dd2f btrfs: deal with errors when checking if a dir entry exists 
during log replay
051995bd0f42 ALSA: hda: intel: Allow repeatedly probing on codec 
configuration errors
9906da162dc8 objtool: Update section header before relocations
e73e72be194e objtool: Check for gelf_update_rel[a] failures
515e03331255 bitfield: build kunit tests without structleak plugin
3f66b6e01c82 thunderbolt: build kunit tests without structleak plugin
d9f94a8ec35a device property: build kunit tests without structleak plugin
2c793a67d71b iio/test-format: build kunit tests without structleak plugin
930f561aae28 gcc-plugins/structleak: add makefile var for disabling 
structleak
1d1af4da1c44 drm/msm/a6xx: Serialize GMU communication
bbdd158b40b6 kunit: fix reference count leak in kfree_at_end
dfcc47a1fe36 KVM: MMU: Reset mmu->pkru_mask to avoid stale data
e647d75565ab net: hns3: fix the max tx size according to user manual
b0e6db0656dd drm: mxsfb: Fix NULL pointer dereference crash on unload
56a3d9637b77 KVM: SEV-ES: Set guest_state_protected after VMSA update
d469678d6b50 net: bridge: mcast: use multicast_membership_interval for 
IGMPv3
8f20259f186e selftests: netfilter: remove stray bash debug line
057aef8df940 netfilter: Kconfig: use 'default y' instead of 'm' for bool 
config option
cc20226e218a isdn: cpai: check ctr->cnr to avoid array index out of bound
6197eb050cfa nfc: nci: fix the UAF of rf_conn_info object
fb82d4dbee95 KVM: x86: remove unnecessary arguments from 
complete_emulator_pio_in
66e46fe3f276 KVM: x86: split the two parts of emulator_pio_in
9887c1668ada KVM: x86: check for interrupts before deciding whether to exit 
the fast path
169577c8840e KVM: x86: leave vcpu->arch.pio.count alone in 
emulator_pio_in_out
62a1a254ed83 KVM: SEV-ES: reduce ghcb_sa_len to 32 bits
3f54362dc7d7 KVM: SEV-ES: go over the sev_pio_data buffer in multiple 
passes if needed
4988e000b3a8 KVM: SEV-ES: fix length of string I/O
727286b23f93 KVM: SEV-ES: keep INS functions together
98c55c508df0 KVM: SEV-ES: clean up kvm_sev_es_ins/outs
abcae3cd6272 KVM: SEV-ES: rename guest_ins_data to sev_pio_data
6697ceb9f6cd KVM: SEV: Flush cache on non-coherent systems before 
RECEIVE_UPDATE_DATA
495bd03b6ba5 KVM: nVMX: promptly process interrupts delivered while in 
guest mode
dc94b8b3f28a mm, slub: fix incorrect memcg slab count for bulk free
159d8cfbd042 mm, slub: fix potential use-after-free in slab_debugfs_fops

[OE-core] [PATCH 0/6] kernel: consolidated pull request

2021-11-04 Thread Bruce Ashfield

From: Bruce Ashfield 

Richard,

Here's a broad set of kernel updates:

 - stable for 5.14
 - stable for 5.10

And then the bigger, a way earlier than normal:

 - libc-headers bump to 5.15
 - 5.15 reference kernel recipes

As everyone has probably heard, 5.15 is the next kernel LTS, so I
wanted to establish it for the next release earlier than normal. Due
to the -dev testing, things like lttng, perf and devsrc are already
ready to go, so this is a smaller pull request than normal.

I had to fixup strace, and the vboxguest drivers (patch sent to
meta-oe)

I've run it through the AB and everything came back green, as well
as my local testing.

This isn't the default for any of the machines yet (but I have
local patches for that as well). The h/w reference boards
stil use 5.14 and need to be updated, but the plan is to remove 5.14,
and eventually 5.10 from master, and we'll go with 5.15, and 5.16+
in the spring 2022 release.

Cheers,

Bruce

The following changes since commit 3e9c4801216111496acffdfdccf1deae3b3d6b96:

  insane.bbclass: Add a check for directories that are expected to be empty 
(2021-11-03 11:12:26 +)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (6):
  linux-yocto/5.14: update to v5.14.15
  linux-yocto/5.10: update to v5.10.76
  linux-libc-headers: update to v5.15
  linux-yocto-rt/5.10: update to -rt54
  linux-yocto/5.15: introduce recipes
  strace: fix build against 5.15 kernel/kernel-headers

 meta/conf/distro/include/tcmode-default.inc   |   2 +-
 ...1-Avoid-relying-on-presence-of-ipx.h.patch | 151 ++
 meta/recipes-devtools/strace/strace_5.14.bb   |   1 +
 ...ers_5.14.bb => linux-libc-headers_5.15.bb} |   4 +-
 .../linux/linux-yocto-rt_5.10.bb  |   6 +-
 .../linux/linux-yocto-rt_5.14.bb  |   6 +-
 .../linux/linux-yocto-rt_5.15.bb  |  45 ++
 .../linux/linux-yocto-tiny_5.10.bb|   8 +-
 .../linux/linux-yocto-tiny_5.14.bb|   8 +-
 .../linux/linux-yocto-tiny_5.15.bb|  32 
 meta/recipes-kernel/linux/linux-yocto_5.10.bb |  24 +--
 meta/recipes-kernel/linux/linux-yocto_5.14.bb |  26 +--
 meta/recipes-kernel/linux/linux-yocto_5.15.bb |  68 
 13 files changed, 339 insertions(+), 42 deletions(-)
 create mode 100644 
meta/recipes-devtools/strace/strace/0001-Avoid-relying-on-presence-of-ipx.h.patch
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb => 
linux-libc-headers_5.15.bb} (81%)
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
 create mode 100644 meta/recipes-kernel/linux/linux-yocto_5.15.bb

-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157862): 
https://lists.openembedded.org/g/openembedded-core/message/157862
Mute This Topic: https://lists.openembedded.org/mt/86824892/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] bitbake: cooker: check if upstream hash equivalence server is available

2021-11-04 Thread Jose Quaresma

To reproduce we can set:

# the real port is 8687 and with the 18687 we can simulate a firewall block
BB_HASHSERVE_UPSTREAM = "typhoon.yocto.io:18687"

With the V2 patch and we get on the log:

WARNING: BB_HASHSERVE_UPSTREAM is not valid, unable to connect hash
equivalence server at 'typhoon.yocto.io:18687': timeout('timed out')

and bitbake deadlock in Initialising tasks:

Initialising tasks:  44%
|
  | ETA:
 0:00:00

on bitbake-cookerdaemon.log we have:

3 19:32:26.434306 Running command ['buildTargets', ['core-image-minimal'],
'build']
63 19:32:26.434386 Command Completed
Error talking to server: [Errno 110] Connect call failed ('35.233.185.178',
18687)
Error talking to server: [Errno 110] Connect call failed ('35.233.185.178',
18687)
Error talking to server: [Errno 110] Connect call failed ('35.233.185.178',
18687)
Error talking to server: [Errno 110] Connect call failed ('35.233.185.178',
18687)
Error from client: [Errno 110] Connect call failed ('35.233.185.178',
18687)
Traceback (most recent call last):
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 57, in
_send_wrapper
   await self.connect()
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 43, in connect
   (self.reader, self.writer) = await self._connect_sock()
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 26, in
connect_sock
   return await asyncio.open_connection(address, port)
 File "/usr/lib/python3.7/asyncio/streams.py", line 77, in open_connection
   lambda: protocol, host, port, **kwds)
 File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in
create_connection
   raise exceptions[0]
 File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in
create_connection
   await self.sock_connect(sock, address)
 File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in
sock_connect
   return await fut
 File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in
_sock_connect_cb
   raise OSError(err, f'Connect call failed {address}')
TimeoutError: [Errno 110] Connect call failed ('35.233.185.178', 18687)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
 File "/work/poky/bitbake/lib/bb/asyncrpc/serv.py", line 192, in
handle_client
   await client.process_requests()
 File "/work/poky/bitbake/lib/hashserv/server.py", line 200, in
process_requests
   await super().process_requests()
 File "/work/poky/bitbake/lib/bb/asyncrpc/serv.py", line 72, in
process_requests
   await self.dispatch_message(d)
 File "/work/poky/bitbake/lib/hashserv/server.py", line 210, in
dispatch_message
   await self.handlers[k](msg[k])
 File "/work/poky/bitbake/lib/hashserv/server.py", line 355, in
handle_get_stream
   upstream = await self.upstream_client.get_unihash(method, taskhash)
 File "/work/poky/bitbake/lib/hashserv/client.py", line 57, in get_unihash
   await self._set_mode(self.MODE_GET_STREAM)
 File "/work/poky/bitbake/lib/hashserv/client.py", line 46, in _set_mode
   r = await self.send_message({"get-stream": None})
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 110, in
send_message
   return await self._send_wrapper(proc)
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 68, in
_send_wrapper
   raise ConnectionError(str(e))
ConnectionError: [Errno 110] Connect call failed ('35.233.185.178', 18687)
Error talking to server: Connection closed
Traceback (most recent call last):
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 57, in
_send_wrapper
   await self.connect()
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 43, in connect
   (self.reader, self.writer) = await self._connect_sock()
 File "/work/poky/bitbake/lib/bb/asyncrpc/client.py", line 26, in
connect_sock
   return await asyncio.open_connection(address, port)
 File "/usr/lib/python3.7/asyncio/streams.py", line 77, in open_connection
   lambda: protocol, host, port, **kwds)
 File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in
create_connection
   raise exceptions[0]
 File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in
create_connection
   await self.sock_connect(sock, address)
 File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in
sock_connect
   return await fut
 File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in
_sock_connect_cb
   raise OSError(err, f'Connect call failed {address}')
TimeoutError: [Errno 110] Connect call failed ('35.233.185.178', 18687)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
 File "/work/poky/bitbake/lib/bb/asyncrpc/serv.py", line 192, in
handle_client
   await client.process_requests()
 File "/work/poky/bitbake/lib/hashserv/server.py", line 200, in
process_requests
   await super().process_requests()
 File "/work/poky/bitbake/lib/bb/asyncrpc/serv.py", line 72, in
process_requests
   await

Re: [OE-core] [PATCH] bitbake: cooker: check if upstream hash equivalence server is available

2021-11-04 Thread Jose Quaresma

Jose Quaresma via lists.openembedded.org  escreveu no dia domingo, 17/10/2021 à(s)
22:14:

>
>
> Joshua Watt  escreveu no dia sábado, 16/10/2021
> à(s) 20:15:
>
>>
>>
>> On Fri, Oct 15, 2021, 6:47 PM Jose Quaresma 
>> wrote:
>>
>>> When the user specify an upstream hash equivalence server in
>>> BB_HASHSERVE_UPSTREAM abort if we can't connect otherwise the
>>> user will never be notified about the problem.
>>>
>>> Signed-off-by: Jose Quaresma 
>>> ---
>>>  bitbake/lib/bb/cooker.py | 12 +++-
>>>  1 file changed, 11 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
>>> index af794b4c42..34603c5ea2 100644
>>> --- a/bitbake/lib/bb/cooker.py
>>> +++ b/bitbake/lib/bb/cooker.py
>>> @@ -388,12 +388,22 @@ class BBCooker:
>>>  # Create a new hash server bound to a unix domain socket
>>>  if not self.hashserv:
>>>  dbfile = (self.data.getVar("PERSISTENT_DIR") or
>>> self.data.getVar("CACHE")) + "/hashserv.db"
>>> +upstream = self.data.getVar("BB_HASHSERVE_UPSTREAM") or
>>> None
>>> +if upstream:
>>> +import socket
>>> +try:
>>> +sock =
>>> socket.create_connection(upstream.split(":"), 5)
>>> +sock.close()
>>> +except socket.error as e:
>>> +bb.fatal("BB_HASHSERVE_UPSTREAM is not valid,
>>> unable to connect hash equivalence server at '%s': %s"
>>> + % (upstream, repr(e)))
>>> +
>>>
>>
>> Perhaps this should just be a warning? The upstream missing should not be
>> fatal for a given server, if it is we probably need to fix that
>>
>
I have changed it to be a warning in V2


> In my opinion this needs to be fatal or fixed with a different approach.
>
> If we launch bitbake in a clean build without build/cache with an invalid
> server it will deadlock printing the follow message after several minutes:
> WARNING: Error contacting Hash Equivalence Server
> unix:///build/hashserve.sock: Connection closed
>
> The build/bitbake-cookerdaemon.log have all the connections errors as well
> as exceptions.
> This cooker log is a bit ugly imho and I will try to improved it in a
> follow up patch.
>
>
>>  self.hashservaddr = "unix://%s/hashserve.sock" %
>>> self.data.getVar("TOPDIR")
>>>  self.hashserv = hashserv.create_server(
>>>  self.hashservaddr,
>>>  dbfile,
>>>  sync=False,
>>> -upstream=self.data.getVar("BB_HASHSERVE_UPSTREAM")
>>> or None,
>>> +upstream=upstream,
>>>  )
>>>  self.hashserv.serve_as_process()
>>>  self.data.setVar("BB_HASHSERVE", self.hashservaddr)
>>> --
>>> 2.33.1
>>>
>>>
>>>
>>>
>>>
>
> --
> Best regards,
>
> José Quaresma
>
> 
>
>

-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157860): 
https://lists.openembedded.org/g/openembedded-core/message/157860
Mute This Topic: https://lists.openembedded.org/mt/86362510/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v2] bitbake: cooker: check if upstream hash equivalence server is available

2021-11-04 Thread Jose Quaresma

When the user specify an invalid upstream hash equivalence server in
BB_HASHSERVE_UPSTREAM notify the user that we can't connect the server.

Signed-off-by: Jose Quaresma 
---

v2: make it a warning instaed of fatal

 bitbake/lib/bb/cooker.py | 12 +++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
index 194595ce8b..2b92744998 100644
--- a/bitbake/lib/bb/cooker.py
+++ b/bitbake/lib/bb/cooker.py
@@ -388,12 +388,22 @@ class BBCooker:
 # Create a new hash server bound to a unix domain socket
 if not self.hashserv:
 dbfile = (self.data.getVar("PERSISTENT_DIR") or 
self.data.getVar("CACHE")) + "/hashserv.db"
+upstream = self.data.getVar("BB_HASHSERVE_UPSTREAM") or None
+if upstream:
+import socket
+try:
+sock = socket.create_connection(upstream.split(":"), 5)
+sock.close()
+except socket.error as e:
+bb.warn("BB_HASHSERVE_UPSTREAM is not valid, unable to 
connect hash equivalence server at '%s': %s" 
+ % (upstream, repr(e)))
+
 self.hashservaddr = "unix://%s/hashserve.sock" % 
self.data.getVar("TOPDIR")
 self.hashserv = hashserv.create_server(
 self.hashservaddr,
 dbfile,
 sync=False,
-upstream=self.data.getVar("BB_HASHSERVE_UPSTREAM") or None,
+upstream=upstream,
 )
 self.hashserv.serve_as_process()
 self.data.setVar("BB_HASHSERVE", self.hashservaddr)
-- 
2.33.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157859): 
https://lists.openembedded.org/g/openembedded-core/message/157859
Mute This Topic: https://lists.openembedded.org/mt/86824483/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH v2] sstate: another fix for touching files inside pseudo

2021-11-04 Thread Jose Quaresma

This patch is a fixup for 676757f "sstate: fix touching files inside pseudo"

running the 'id' command inside the sstate_unpack_package
function shows that this funcion run inside the pseudo:

 uid=0(root) gid=0(root) groups=0(root)

The check for [ -w ${SSTATE_PKG} ] and [ -O ${SSTATE_PKG}.siginfo ]
will always return true and the touch can fail when the real user
don't have permission or in readonly filesystem.

As the documentation refers:
- the file test operator "-w" check if the file has write permission
(for the user running the test).
- the file test operator "-O" check if you are owner of file

We can avoid this test running the touch and mask any return errors
that we have.

Signed-off-by: Jose Quaresma 
---

V2: match the original code

 meta/classes/sstate.bbclass | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 8182010047..849723d4dc 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -900,12 +900,12 @@ sstate_unpack_package () {
fi
 
tar -I "$ZSTD" -xvf ${SSTATE_PKG}
-   # update .siginfo atime on local/NFS mirror
-   [ -O ${SSTATE_PKG}.siginfo ] && [ -w ${SSTATE_PKG}.siginfo ] && [ -h 
${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
-   # Use "! -w ||" to return true for read only files
-   [ ! -w ${SSTATE_PKG} ] || touch --no-dereference ${SSTATE_PKG}
-   [ ! -w ${SSTATE_PKG}.sig ] || [ ! -e ${SSTATE_PKG}.sig ] || touch 
--no-dereference ${SSTATE_PKG}.sig
-   [ ! -w ${SSTATE_PKG}.siginfo ] || [ ! -e ${SSTATE_PKG}.siginfo ] || 
touch --no-dereference ${SSTATE_PKG}.siginfo
+   # update .siginfo atime on local/NFS mirror if it is a symbolic link
+   [ ! -h ${SSTATE_PKG}.siginfo ] || touch -a ${SSTATE_PKG}.siginfo 
2>/dev/null || true
+   # update each symbolic link instead of any referenced file
+   touch --no-dereference ${SSTATE_PKG} 2>/dev/null || true
+   [ ! -e ${SSTATE_PKG}.sig ] || touch --no-dereference ${SSTATE_PKG}.sig 
2>/dev/null || true
+   [ ! -e ${SSTATE_PKG}.siginfo ] || touch --no-dereference 
${SSTATE_PKG}.siginfo 2>/dev/null || true
 }
 
 BB_HASHCHECK_FUNCTION = "sstate_checkhashes"
-- 
2.33.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157858): 
https://lists.openembedded.org/g/openembedded-core/message/157858
Mute This Topic: https://lists.openembedded.org/mt/86824160/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] sstate: another fix for touching files inside pseudo

2021-11-04 Thread Jose Quaresma

Peter Kjellerstedt  escreveu no dia quinta,
4/11/2021 à(s) 17:01:

> > -Original Message-
> > From: openembedded-core@lists.openembedded.org  > c...@lists.openembedded.org> On Behalf Of Jose Quaresma
> > Sent: den 4 november 2021 16:42
> > To: openembedded-core@lists.openembedded.org
> > Cc: Jose Quaresma 
> > Subject: [OE-core] [PATCH] sstate: another fix for touching files inside
> > pseudo
> >
> > This patch is a fixup for 676757f "sstate: fix touching files inside
> > pseudo"
> >
> > running the 'id' command inside the sstate_unpack_package
> > function shows that this funcion run inside the pseudo:
> >
> >  uid=0(root) gid=0(root) groups=0(root)
> >
> > The check for [ -w ${SSTATE_PKG} ] and [ -O ${SSTATE_PKG}.siginfo ]
> > will always return true and the touch can fail when the real user
> > don't have permission or in readonly filesystem.
> >
> > As the documentation refers:
> > - the file test operator "-w" check if the file has write permission
> > (for the user running the test).
> > - the file test operator "-O" check if you are owner of file
> >
> > We can avoid this test running the touch and mask any return errors
> > that we have.
> >
> > Signed-off-by: Jose Quaresma 
> > ---
> >  meta/classes/sstate.bbclass | 12 ++--
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
> > index 8182010047..e4d58639f3 100644
> > --- a/meta/classes/sstate.bbclass
> > +++ b/meta/classes/sstate.bbclass
> > @@ -900,12 +900,12 @@ sstate_unpack_package () {
> >   fi
> >
> >   tar -I "$ZSTD" -xvf ${SSTATE_PKG}
> > - # update .siginfo atime on local/NFS mirror
> > - [ -O ${SSTATE_PKG}.siginfo ] && [ -w ${SSTATE_PKG}.siginfo ] && [
> -h ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
> > - # Use "! -w ||" to return true for read only files
> > - [ ! -w ${SSTATE_PKG} ] || touch --no-dereference ${SSTATE_PKG}
> > - [ ! -w ${SSTATE_PKG}.sig ] || [ ! -e ${SSTATE_PKG}.sig ] || touch
> --no-dereference ${SSTATE_PKG}.sig
> > - [ ! -w ${SSTATE_PKG}.siginfo ] || [ ! -e ${SSTATE_PKG}.siginfo ]
> || touch --no-dereference ${SSTATE_PKG}.siginfo
> > + # update .siginfo atime on local/NFS mirror if it is a symbolic
> link
> > + [ ! -h ${SSTATE_PKG}.siginfo ] || touch -a ${SSTATE_PKG}.siginfo
> 2>/dev/null || true
> > + # update each symbolic link instead of any referenced file
> > + touch --no-dereference ${SSTATE_PKG} 2>/dev/null || true
> > + touch --no-dereference ${SSTATE_PKG}.siginfo 2>/dev/null || true
>
> To match the original code this should be:
>
> [ ! -e ${SSTATE_PKG}.siginfo ] || touch --no-dereference
> ${SSTATE_PKG}.siginfo 2>/dev/null || true
>
> Or was there some reason you removed the test for if the siginfo
> file exists before touching it? If so, then the commit message
> should state this.
>

I assumed that when ${SSTATE_PKG} exists the ${SSTATE_PKG}.siginfo also
exists.
You are true in your observation that this doesn't match the original code.
I will send a v2.


>
> > + [ ! -e ${SSTATE_PKG}.sig ] || touch --no-dereference
> ${SSTATE_PKG}.sig 2>/dev/null || true
> >  }
> >
> >  BB_HASHCHECK_FUNCTION = "sstate_checkhashes"
> > --
> > 2.33.1
>
> //Peter
>
>

-- 
Best regards,

José Quaresma

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157857): 
https://lists.openembedded.org/g/openembedded-core/message/157857
Mute This Topic: https://lists.openembedded.org/mt/86819016/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] create-spdx: Set the Organization field via a variable

2021-11-04 Thread Joshua Watt

On Thu, Nov 4, 2021 at 11:49 AM Andres Beltran
 wrote:
>
> Currently, the "Organization" field for SBOMs is hard-coded in
> create-spdx. Create a new variable SPDX_ORG to make this field more
> generic.
>
> Signed-off-by: Andres Beltran 

LGTM

Reviewed-By: Joshua Watt 

> ---
>  meta/classes/create-spdx.bbclass | 10 ++
>  1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/meta/classes/create-spdx.bbclass 
> b/meta/classes/create-spdx.bbclass
> index c35dbe11849..eb1d446f3fb 100644
> --- a/meta/classes/create-spdx.bbclass
> +++ b/meta/classes/create-spdx.bbclass
> @@ -28,6 +28,8 @@ SPDX_NAMESPACE_PREFIX ??= "http://spdx.org/spdxdoc;
>
>  SPDX_LICENSES ??= "${COREBASE}/meta/files/spdx-licenses.json"
>
> +SPDX_ORG ??= "OpenEmbedded ()"
> +
>  do_image_complete[depends] = "virtual/kernel:do_create_spdx"
>
>  def get_doc_namespace(d, doc):
> @@ -415,7 +417,7 @@ python do_create_spdx() {
>  doc.creationInfo.comment = "This document was created by analyzing 
> recipe files during the build."
>  doc.creationInfo.licenseListVersion = 
> d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
>  doc.creationInfo.creators.append("Tool: OpenEmbedded Core 
> create-spdx.bbclass")
> -doc.creationInfo.creators.append("Organization: OpenEmbedded ()")
> +doc.creationInfo.creators.append("Organization: %s" % 
> d.getVar("SPDX_ORG"))
>  doc.creationInfo.creators.append("Person: N/A ()")
>
>  recipe = oe.spdx.SPDXPackage()
> @@ -519,7 +521,7 @@ python do_create_spdx() {
>  package_doc.creationInfo.comment = "This document was created by 
> analyzing packages created during the build."
>  package_doc.creationInfo.licenseListVersion = 
> d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
>  package_doc.creationInfo.creators.append("Tool: OpenEmbedded 
> Core create-spdx.bbclass")
> -package_doc.creationInfo.creators.append("Organization: 
> OpenEmbedded ()")
> +package_doc.creationInfo.creators.append("Organization: %s" % 
> d.getVar("SPDX_ORG"))
>  package_doc.creationInfo.creators.append("Person: N/A ()")
>  package_doc.externalDocumentRefs.append(recipe_ref)
>
> @@ -653,7 +655,7 @@ python do_create_runtime_spdx() {
>  runtime_doc.creationInfo.comment = "This document was created by 
> analyzing package runtime dependencies."
>  runtime_doc.creationInfo.licenseListVersion = 
> d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
>  runtime_doc.creationInfo.creators.append("Tool: OpenEmbedded 
> Core create-spdx.bbclass")
> -runtime_doc.creationInfo.creators.append("Organization: 
> OpenEmbedded ()")
> +runtime_doc.creationInfo.creators.append("Organization: %s" % 
> d.getVar("SPDX_ORG"))
>  runtime_doc.creationInfo.creators.append("Person: N/A ()")
>
>  package_ref = oe.spdx.SPDXExternalDocumentRef()
> @@ -813,7 +815,7 @@ python image_combine_spdx() {
>  doc.creationInfo.comment = "This document was created by analyzing the 
> source of the Yocto recipe during the build."
>  doc.creationInfo.licenseListVersion = 
> d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
>  doc.creationInfo.creators.append("Tool: OpenEmbedded Core 
> create-spdx.bbclass")
> -doc.creationInfo.creators.append("Organization: OpenEmbedded ()")
> +doc.creationInfo.creators.append("Organization: %s" % 
> d.getVar("SPDX_ORG"))
>  doc.creationInfo.creators.append("Person: N/A ()")
>
>  image = oe.spdx.SPDXPackage()
> --
> 2.17.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157856): 
https://lists.openembedded.org/g/openembedded-core/message/157856
Mute This Topic: https://lists.openembedded.org/mt/86820747/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] sstate: another fix for touching files inside pseudo

2021-11-04 Thread Peter Kjellerstedt

> -Original Message-
> From: openembedded-core@lists.openembedded.org  c...@lists.openembedded.org> On Behalf Of Jose Quaresma
> Sent: den 4 november 2021 16:42
> To: openembedded-core@lists.openembedded.org
> Cc: Jose Quaresma 
> Subject: [OE-core] [PATCH] sstate: another fix for touching files inside
> pseudo
> 
> This patch is a fixup for 676757f "sstate: fix touching files inside
> pseudo"
> 
> running the 'id' command inside the sstate_unpack_package
> function shows that this funcion run inside the pseudo:
> 
>  uid=0(root) gid=0(root) groups=0(root)
> 
> The check for [ -w ${SSTATE_PKG} ] and [ -O ${SSTATE_PKG}.siginfo ]
> will always return true and the touch can fail when the real user
> don't have permission or in readonly filesystem.
> 
> As the documentation refers:
> - the file test operator "-w" check if the file has write permission
> (for the user running the test).
> - the file test operator "-O" check if you are owner of file
> 
> We can avoid this test running the touch and mask any return errors
> that we have.
> 
> Signed-off-by: Jose Quaresma 
> ---
>  meta/classes/sstate.bbclass | 12 ++--
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
> index 8182010047..e4d58639f3 100644
> --- a/meta/classes/sstate.bbclass
> +++ b/meta/classes/sstate.bbclass
> @@ -900,12 +900,12 @@ sstate_unpack_package () {
>   fi
> 
>   tar -I "$ZSTD" -xvf ${SSTATE_PKG}
> - # update .siginfo atime on local/NFS mirror
> - [ -O ${SSTATE_PKG}.siginfo ] && [ -w ${SSTATE_PKG}.siginfo ] && [ -h 
> ${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
> - # Use "! -w ||" to return true for read only files
> - [ ! -w ${SSTATE_PKG} ] || touch --no-dereference ${SSTATE_PKG}
> - [ ! -w ${SSTATE_PKG}.sig ] || [ ! -e ${SSTATE_PKG}.sig ] || touch 
> --no-dereference ${SSTATE_PKG}.sig
> - [ ! -w ${SSTATE_PKG}.siginfo ] || [ ! -e ${SSTATE_PKG}.siginfo ] || 
> touch --no-dereference ${SSTATE_PKG}.siginfo
> + # update .siginfo atime on local/NFS mirror if it is a symbolic link
> + [ ! -h ${SSTATE_PKG}.siginfo ] || touch -a ${SSTATE_PKG}.siginfo 
> 2>/dev/null || true
> + # update each symbolic link instead of any referenced file
> + touch --no-dereference ${SSTATE_PKG} 2>/dev/null || true
> + touch --no-dereference ${SSTATE_PKG}.siginfo 2>/dev/null || true

To match the original code this should be:

[ ! -e ${SSTATE_PKG}.siginfo ] || touch --no-dereference 
${SSTATE_PKG}.siginfo 2>/dev/null || true

Or was there some reason you removed the test for if the siginfo 
file exists before touching it? If so, then the commit message 
should state this.

> + [ ! -e ${SSTATE_PKG}.sig ] || touch --no-dereference ${SSTATE_PKG}.sig 
> 2>/dev/null || true
>  }
> 
>  BB_HASHCHECK_FUNCTION = "sstate_checkhashes"
> --
> 2.33.1

//Peter


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157855): 
https://lists.openembedded.org/g/openembedded-core/message/157855
Mute This Topic: https://lists.openembedded.org/mt/86819016/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] create-spdx: Set the Organization field via a variable

2021-11-04 Thread Andres Beltran

Currently, the "Organization" field for SBOMs is hard-coded in
create-spdx. Create a new variable SPDX_ORG to make this field more
generic.

Signed-off-by: Andres Beltran 
---
 meta/classes/create-spdx.bbclass | 10 ++
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/meta/classes/create-spdx.bbclass b/meta/classes/create-spdx.bbclass
index c35dbe11849..eb1d446f3fb 100644
--- a/meta/classes/create-spdx.bbclass
+++ b/meta/classes/create-spdx.bbclass
@@ -28,6 +28,8 @@ SPDX_NAMESPACE_PREFIX ??= "http://spdx.org/spdxdoc;
 
 SPDX_LICENSES ??= "${COREBASE}/meta/files/spdx-licenses.json"
 
+SPDX_ORG ??= "OpenEmbedded ()"
+
 do_image_complete[depends] = "virtual/kernel:do_create_spdx"
 
 def get_doc_namespace(d, doc):
@@ -415,7 +417,7 @@ python do_create_spdx() {
 doc.creationInfo.comment = "This document was created by analyzing recipe 
files during the build."
 doc.creationInfo.licenseListVersion = 
d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
 doc.creationInfo.creators.append("Tool: OpenEmbedded Core 
create-spdx.bbclass")
-doc.creationInfo.creators.append("Organization: OpenEmbedded ()")
+doc.creationInfo.creators.append("Organization: %s" % d.getVar("SPDX_ORG"))
 doc.creationInfo.creators.append("Person: N/A ()")
 
 recipe = oe.spdx.SPDXPackage()
@@ -519,7 +521,7 @@ python do_create_spdx() {
 package_doc.creationInfo.comment = "This document was created by 
analyzing packages created during the build."
 package_doc.creationInfo.licenseListVersion = 
d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
 package_doc.creationInfo.creators.append("Tool: OpenEmbedded Core 
create-spdx.bbclass")
-package_doc.creationInfo.creators.append("Organization: 
OpenEmbedded ()")
+package_doc.creationInfo.creators.append("Organization: %s" % 
d.getVar("SPDX_ORG"))
 package_doc.creationInfo.creators.append("Person: N/A ()")
 package_doc.externalDocumentRefs.append(recipe_ref)
 
@@ -653,7 +655,7 @@ python do_create_runtime_spdx() {
 runtime_doc.creationInfo.comment = "This document was created by 
analyzing package runtime dependencies."
 runtime_doc.creationInfo.licenseListVersion = 
d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
 runtime_doc.creationInfo.creators.append("Tool: OpenEmbedded Core 
create-spdx.bbclass")
-runtime_doc.creationInfo.creators.append("Organization: 
OpenEmbedded ()")
+runtime_doc.creationInfo.creators.append("Organization: %s" % 
d.getVar("SPDX_ORG"))
 runtime_doc.creationInfo.creators.append("Person: N/A ()")
 
 package_ref = oe.spdx.SPDXExternalDocumentRef()
@@ -813,7 +815,7 @@ python image_combine_spdx() {
 doc.creationInfo.comment = "This document was created by analyzing the 
source of the Yocto recipe during the build."
 doc.creationInfo.licenseListVersion = 
d.getVar("SPDX_LICENSE_DATA")["licenseListVersion"]
 doc.creationInfo.creators.append("Tool: OpenEmbedded Core 
create-spdx.bbclass")
-doc.creationInfo.creators.append("Organization: OpenEmbedded ()")
+doc.creationInfo.creators.append("Organization: %s" % d.getVar("SPDX_ORG"))
 doc.creationInfo.creators.append("Person: N/A ()")
 
 image = oe.spdx.SPDXPackage()
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157854): 
https://lists.openembedded.org/g/openembedded-core/message/157854
Mute This Topic: https://lists.openembedded.org/mt/86820747/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [dunfell][PATCH] sstate: another fix for touching files inside pseudo

2021-11-04 Thread Jose Quaresma

This patch is a fixup for 676757f "sstate: fix touching files inside pseudo"

running the 'id' command inside the sstate_unpack_package
function shows that this funcion run inside the pseudo:

 uid=0(root) gid=0(root) groups=0(root)

The check for [ -w ${SSTATE_PKG} ] and [ -O ${SSTATE_PKG}.siginfo ]
will always return true and the touch can fail when the real user
don't have permission or in readonly filesystem.

As the documentation refers:
- the file test operator "-w" check if the file has write permission
(for the user running the test).
- the file test operator "-O" check if you are owner of file

We can avoid this test running the touch and mask any return errors
that we have.

Signed-off-by: Jose Quaresma 
---

The patch sent to master branch don't apply on dunfell branch
because of the ZSTD changes.

 meta/classes/sstate.bbclass | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 38dc3bff30..c42bd7ab77 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -859,12 +859,12 @@ python sstate_report_unihash() {
 #
 sstate_unpack_package () {
tar -xvzf ${SSTATE_PKG}
-   # update .siginfo atime on local/NFS mirror
-   [ -O ${SSTATE_PKG}.siginfo ] && [ -w ${SSTATE_PKG}.siginfo ] && [ -h 
${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
-   # Use "! -w ||" to return true for read only files
-   [ ! -w ${SSTATE_PKG} ] || touch --no-dereference ${SSTATE_PKG}
-   [ ! -w ${SSTATE_PKG}.sig ] || [ ! -e ${SSTATE_PKG}.sig ] || touch 
--no-dereference ${SSTATE_PKG}.sig
-   [ ! -w ${SSTATE_PKG}.siginfo ] || [ ! -e ${SSTATE_PKG}.siginfo ] || 
touch --no-dereference ${SSTATE_PKG}.siginfo
+   # update .siginfo atime on local/NFS mirror if it is a symbolic link
+   [ ! -h ${SSTATE_PKG}.siginfo ] || touch -a ${SSTATE_PKG}.siginfo 
2>/dev/null || true
+   # update each symbolic link instead of any referenced file
+   touch --no-dereference ${SSTATE_PKG} 2>/dev/null || true
+   touch --no-dereference ${SSTATE_PKG}.siginfo 2>/dev/null || true
+   [ ! -e ${SSTATE_PKG}.sig ] || touch --no-dereference ${SSTATE_PKG}.sig 
2>/dev/null || true
 }
 
 BB_HASHCHECK_FUNCTION = "sstate_checkhashes"
-- 
2.33.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157853): 
https://lists.openembedded.org/g/openembedded-core/message/157853
Mute This Topic: https://lists.openembedded.org/mt/86820412/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] mesa: Broadcom v3d Vulkan driver

2021-11-04 Thread Joel Winarske

Enables building the Vulkan 1.1 compliant v3d driver.

Signed-off-by: Joel Winarske 
---
 meta/recipes-graphics/mesa/mesa.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-graphics/mesa/mesa.inc 
b/meta/recipes-graphics/mesa/mesa.inc
index cc71114992..b687f8e4ab 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -112,6 +112,7 @@ VULKAN_DRIVERS = ""
 VULKAN_DRIVERS:append:x86:class-target = ",intel"
 VULKAN_DRIVERS:append:x86-64:class-target = ",intel"
 VULKAN_DRIVERS:append ="${@bb.utils.contains('PACKAGECONFIG', 'freedreno', 
',freedreno', '', d)}"
+VULKAN_DRIVERS:append ="${@bb.utils.contains('PACKAGECONFIG', 'broadcom', 
',broadcom', '', d)}"
 PACKAGECONFIG[vulkan] = 
"-Dvulkan-drivers=${@strip_comma('${VULKAN_DRIVERS}')}, -Dvulkan-drivers='',"
 
 PACKAGECONFIG[opengl] = "-Dopengl=true, -Dopengl=false"
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157852): 
https://lists.openembedded.org/g/openembedded-core/message/157852
Mute This Topic: https://lists.openembedded.org/mt/86819839/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] sstate: another fix for touching files inside pseudo

2021-11-04 Thread Jose Quaresma

This patch is a fixup for 676757f "sstate: fix touching files inside pseudo"

running the 'id' command inside the sstate_unpack_package
function shows that this funcion run inside the pseudo:

 uid=0(root) gid=0(root) groups=0(root)

The check for [ -w ${SSTATE_PKG} ] and [ -O ${SSTATE_PKG}.siginfo ]
will always return true and the touch can fail when the real user
don't have permission or in readonly filesystem.

As the documentation refers:
- the file test operator "-w" check if the file has write permission
(for the user running the test).
- the file test operator "-O" check if you are owner of file

We can avoid this test running the touch and mask any return errors
that we have.

Signed-off-by: Jose Quaresma 
---
 meta/classes/sstate.bbclass | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 8182010047..e4d58639f3 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -900,12 +900,12 @@ sstate_unpack_package () {
fi
 
tar -I "$ZSTD" -xvf ${SSTATE_PKG}
-   # update .siginfo atime on local/NFS mirror
-   [ -O ${SSTATE_PKG}.siginfo ] && [ -w ${SSTATE_PKG}.siginfo ] && [ -h 
${SSTATE_PKG}.siginfo ] && touch -a ${SSTATE_PKG}.siginfo
-   # Use "! -w ||" to return true for read only files
-   [ ! -w ${SSTATE_PKG} ] || touch --no-dereference ${SSTATE_PKG}
-   [ ! -w ${SSTATE_PKG}.sig ] || [ ! -e ${SSTATE_PKG}.sig ] || touch 
--no-dereference ${SSTATE_PKG}.sig
-   [ ! -w ${SSTATE_PKG}.siginfo ] || [ ! -e ${SSTATE_PKG}.siginfo ] || 
touch --no-dereference ${SSTATE_PKG}.siginfo
+   # update .siginfo atime on local/NFS mirror if it is a symbolic link
+   [ ! -h ${SSTATE_PKG}.siginfo ] || touch -a ${SSTATE_PKG}.siginfo 
2>/dev/null || true
+   # update each symbolic link instead of any referenced file
+   touch --no-dereference ${SSTATE_PKG} 2>/dev/null || true
+   touch --no-dereference ${SSTATE_PKG}.siginfo 2>/dev/null || true
+   [ ! -e ${SSTATE_PKG}.sig ] || touch --no-dereference ${SSTATE_PKG}.sig 
2>/dev/null || true
 }
 
 BB_HASHCHECK_FUNCTION = "sstate_checkhashes"
-- 
2.33.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157851): 
https://lists.openembedded.org/g/openembedded-core/message/157851
Mute This Topic: https://lists.openembedded.org/mt/86819016/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD license

2021-11-04 Thread Joshua Watt

On Thu, Nov 4, 2021 at 6:33 AM Ross Burton  wrote:
>
> Sorry, missed this email.
>
> I copied the license from libx11, as it is the same tarball.  It was
> Joshua Watt who introduced the expanded licenses in
> 44fd2aa731956fe0a0f74d36959c88b0b87adab5.

I don't recall the reasoning for BSD-4-Clause in that specific recipe.
I can go back and look again. It's also possible I just got it wrong;
if you have a better idea what it should be, that would save me the
trouble :)

>
> Ross
>
> On Thu, 4 Nov 2021 at 11:19, Peter Kjellerstedt
>  wrote:
> >
> > Ross: any comment to my question below?
> >
> > > -Original Message-
> > > From: openembedded-core@lists.openembedded.org  > > c...@lists.openembedded.org> On Behalf Of Peter Kjellerstedt
> > > Sent: den 28 oktober 2021 17:44
> > > To: Ross Burton 
> > > Cc: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> > > license
> > >
> > > > -Original Message-
> > > > From: openembedded-core@lists.openembedded.org  > > > c...@lists.openembedded.org> On Behalf Of Ross Burton
> > > > Sent: den 2 september 2021 18:25
> > > > To: openembedded-core@lists.openembedded.org
> > > > Subject: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> > > > license
> > > >
> > > > "BSD" is ambiguous, use the precise licenses BSD-2-Clause BSD-4-Clause.
> > > >
> > > > Signed-off-by: Ross Burton 
> > > > ---
> > > >  meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > > b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > > index 7519b4c018d..e53ccc6aea8 100644
> > > > --- a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > > +++ b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > > @@ -8,7 +8,7 @@ python () {
> > > >
> > > >  require xorg-lib-common.inc
> > > >
> > > > -LICENSE = "MIT & MIT-style & BSD"
> > > > +LICENSE = "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
> > >
> > > Why is this marked as BSD-4-Clause? Looking at the COPYING file and
> > > searching the code I can find no trace of any license text with the
> > > advertising clause from BSD-4-Clause. What am I missing?
> > >
> > > >  LIC_FILES_CHKSUM =
> > > "file://COPYING;md5=172255dee66bb0151435b2d5d709fcf7"
> > > >
> > > >  SRC_URI[md5sum] = "c5fa5a86a20e3591bed6c046498d4b8f"
> > > > --
> > > > 2.25.1
> > >
> > > //Peter
> >
> > //Peter
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157850): 
https://lists.openembedded.org/g/openembedded-core/message/157850
Mute This Topic: https://lists.openembedded.org/mt/85331681/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] opkg: Fix poor operator combination choice

2021-11-04 Thread Mikko Rapeli

On Thu, Nov 04, 2021 at 02:02:57PM +, Richard Purdie wrote:
> Combining :append with += rarely makes sense. Improve it to use the standard
> format (and tweak the implied spacing).

Maybe I'm silly but I find :append with += safer to do than manually remembring
to add the space character.

-Mikko

> Signed-off-by: Richard Purdie 
> ---
>  meta/recipes-devtools/opkg/opkg_0.4.5.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/opkg/opkg_0.4.5.bb 
> b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
> index 2760fc58786..8af047a51ff 100644
> --- a/meta/recipes-devtools/opkg/opkg_0.4.5.bb
> +++ b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
> @@ -60,7 +60,7 @@ do_install_ptest () {
>   sed -i -e '/@PYTHONPATH=. $(PYTHON) $^/a\\t@if [ "$$?" != "0" ];then 
> echo "FAIL:"$^;else echo "PASS:"$^;fi' ${D}${PTEST_PATH}/tests/Makefile
>  }
>  
> -WARN_QA:append += "openssl-deprecation"
> +WARN_QA:append = " openssl-deprecation"
>  QAPKGTEST[openssl-deprecation] = "package_qa_check_openssl_deprecation"
>  def package_qa_check_openssl_deprecation (package, d, messages):
>  sane = True
> -- 
> 2.32.0
> 

> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157849): 
https://lists.openembedded.org/g/openembedded-core/message/157849
Mute This Topic: https://lists.openembedded.org/mt/86816265/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 3/3] meta/scripts: Manual git url branch additions

2021-11-04 Thread Steve Sakoman

From: Richard Purdie 

Following the scripted conversion adding branches to git://
SRC_URI entries, add the remaining references, mainly in the selftests
and recipetool.

Signed-off-by: Richard Purdie 
(cherry picked from commit 5340c0d688036c1be6c938f05d8a8c1e3b49ec38)
Signed-off-by: Steve Sakoman 
---
 meta/conf/distro/include/default-distrovars.inc | 2 +-
 meta/lib/oeqa/selftest/cases/devtool.py | 4 ++--
 meta/lib/oeqa/selftest/cases/recipetool.py  | 6 +++---
 meta/lib/oeqa/selftest/cases/sstatetests.py | 2 +-
 scripts/lib/recipetool/create.py| 3 +++
 5 files changed, 10 insertions(+), 7 deletions(-)

diff --git a/meta/conf/distro/include/default-distrovars.inc 
b/meta/conf/distro/include/default-distrovars.inc
index 433d4b6651..0240589c81 100644
--- a/meta/conf/distro/include/default-distrovars.inc
+++ b/meta/conf/distro/include/default-distrovars.inc
@@ -47,5 +47,5 @@ KERNEL_IMAGETYPES ??= "${KERNEL_IMAGETYPE}"
 # The CONNECTIVITY_CHECK_URIS are used to test whether we can succesfully
 # fetch from the network (and warn you if not). To disable the test set
 # the variable to be empty.
-# Git example url: 
git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=master
+# Git example url: 
git://git.yoctoproject.org/yocto-firewall-test;protocol=git;rev=master;branch=master
 CONNECTIVITY_CHECK_URIS ?= "https://www.example.com/;
diff --git a/meta/lib/oeqa/selftest/cases/devtool.py 
b/meta/lib/oeqa/selftest/cases/devtool.py
index 0985434238..713efd71bd 100644
--- a/meta/lib/oeqa/selftest/cases/devtool.py
+++ b/meta/lib/oeqa/selftest/cases/devtool.py
@@ -340,7 +340,7 @@ class DevtoolAddTests(DevtoolBase):
 checkvars['LIC_FILES_CHKSUM'] = 
'file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263'
 checkvars['S'] = '${WORKDIR}/git'
 checkvars['PV'] = '0.1+git${SRCPV}'
-checkvars['SRC_URI'] = 
'git://git.yoctoproject.org/git/dbus-wait;protocol=https'
+checkvars['SRC_URI'] = 
'git://git.yoctoproject.org/git/dbus-wait;protocol=https;branch=master'
 checkvars['SRCREV'] = srcrev
 checkvars['DEPENDS'] = set(['dbus'])
 self._test_recipe_contents(recipefile, checkvars, [])
@@ -880,7 +880,7 @@ class DevtoolUpdateTests(DevtoolBase):
 self._check_repo_status(os.path.dirname(recipefile), expected_status)
 
 result = runCmd('git diff %s' % os.path.basename(recipefile), 
cwd=os.path.dirname(recipefile))
-addlines = ['SRCREV = ".*"', 'SRC_URI = 
"git://git.infradead.org/mtd-utils.git"']
+addlines = ['SRCREV = ".*"', 'SRC_URI = 
"git://git.infradead.org/mtd-utils.git;branch=master"']
 srcurilines = src_uri.split()
 srcurilines[0] = 'SRC_URI = "' + srcurilines[0]
 srcurilines.append('"')
diff --git a/meta/lib/oeqa/selftest/cases/recipetool.py 
b/meta/lib/oeqa/selftest/cases/recipetool.py
index c2ade2543a..e8aeea3023 100644
--- a/meta/lib/oeqa/selftest/cases/recipetool.py
+++ b/meta/lib/oeqa/selftest/cases/recipetool.py
@@ -370,7 +370,7 @@ class RecipetoolTests(RecipetoolBase):
 tempsrc = os.path.join(self.tempdir, 'srctree')
 os.makedirs(tempsrc)
 recipefile = os.path.join(self.tempdir, 'libmatchbox.bb')
-srcuri = 'git://git.yoctoproject.org/libmatchbox'
+srcuri = 'git://git.yoctoproject.org/libmatchbox;branch=master'
 result = runCmd(['recipetool', 'create', '-o', recipefile, srcuri + 
";rev=9f7cf8895ae2d39c465c04cc78e918c157420269", '-x', tempsrc])
 self.assertTrue(os.path.isfile(recipefile), 'recipetool did not create 
recipe file; output:\n%s' % result.output)
 checkvars = {}
@@ -456,7 +456,7 @@ class RecipetoolTests(RecipetoolBase):
 self.assertTrue(os.path.isfile(recipefile))
 checkvars = {}
 checkvars['LICENSE'] = set(['Apache-2.0'])
-checkvars['SRC_URI'] = 
'git://github.com/mesonbuild/meson;protocol=https'
+checkvars['SRC_URI'] = 
'git://github.com/mesonbuild/meson;protocol=https;branch=master'
 inherits = ['setuptools3']
 self._test_recipe_contents(recipefile, checkvars, inherits)
 
@@ -523,7 +523,7 @@ class RecipetoolTests(RecipetoolBase):
 self.assertTrue(os.path.isfile(recipefile))
 checkvars = {}
 checkvars['LICENSE'] = set(['GPLv2'])
-checkvars['SRC_URI'] = 
'git://git.yoctoproject.org/git/matchbox-terminal;protocol=http'
+checkvars['SRC_URI'] = 
'git://git.yoctoproject.org/git/matchbox-terminal;protocol=http;branch=master'
 inherits = ['pkgconfig', 'autotools']
 self._test_recipe_contents(recipefile, checkvars, inherits)
 
diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py 
b/meta/lib/oeqa/selftest/cases/sstatetests.py
index f0c94c8422..1bfe88c87d 100644
--- a/meta/lib/oeqa/selftest/cases/sstatetests.py
+++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
@@ -39,7 +39,7 @@ class SStateTests(SStateBase):
 
 recipefile = os.path.join(tempdir, "recipes-test",

[OE-core][dunfell 2/3] meta: Add explict branch to git SRC_URIs, handle github url changes

2021-11-04 Thread Steve Sakoman

This update was made with the convert-scruri.py script in scripts/contrib

This script handles two emerging issues:

1. There is uncertainty about the default branch name in git going forward.
To try and cover the different possible outcomes, add branch names to all
git:// and gitsm:// SRC_URI entries.

2. Github are dropping support for git:// protocol fetching, so remap github
 urls as needed. For more details see:

https://github.blog/2021-09-01-improving-git-protocol-security-github/

Signed-off-by: Steve Sakoman 
---
 .../recipes-test/devtool/devtool-upgrade-test2_git.bb   | 2 +-
 .../devtool/devtool-upgrade-test2_git.bb.upgraded   | 2 +-
 meta/classes/devupstream.bbclass| 2 +-
 meta/recipes-bsp/efibootmgr/efibootmgr_17.bb| 2 +-
 meta/recipes-bsp/efivar/efivar_37.bb| 2 +-
 meta/recipes-bsp/opensbi/opensbi_0.6.bb | 2 +-
 meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb| 2 +-
 meta/recipes-bsp/u-boot/u-boot-common.inc   | 2 +-
 meta/recipes-connectivity/connman/connman-gnome_0.7.bb  | 2 +-
 meta/recipes-connectivity/libnss-mdns/libnss-mdns_0.14.1.bb | 2 +-
 .../mobile-broadband-provider-info_git.bb   | 2 +-
 meta/recipes-connectivity/resolvconf/resolvconf_1.82.bb | 2 +-
 meta/recipes-core/dbus-wait/dbus-wait_git.bb| 2 +-
 meta/recipes-core/expat/expat_2.2.9.bb  | 2 +-
 meta/recipes-core/fts/fts_1.2.7.bb  | 2 +-
 meta/recipes-core/glibc/cross-localedef-native_2.31.bb  | 2 +-
 meta/recipes-core/glibc/glibc-version.inc   | 2 +-
 meta/recipes-core/ifupdown/ifupdown_0.8.35.bb   | 2 +-
 meta/recipes-core/libxcrypt/libxcrypt.inc   | 2 +-
 meta/recipes-core/musl/libucontext_git.bb   | 2 +-
 meta/recipes-core/musl/musl-obstack.bb  | 2 +-
 meta/recipes-core/musl/musl-utils.bb| 2 +-
 meta/recipes-core/musl/musl_git.bb  | 2 +-
 meta/recipes-core/ncurses/ncurses.inc   | 2 +-
 meta/recipes-core/psplash/psplash_git.bb| 2 +-
 meta/recipes-core/systemd/systemd.inc   | 2 +-
 meta/recipes-core/update-rc.d/update-rc.d_0.8.bb| 2 +-
 meta/recipes-devtools/bootchart2/bootchart2_0.14.9.bb   | 2 +-
 meta/recipes-devtools/btrfs-tools/btrfs-tools_5.4.1.bb  | 2 +-
 meta/recipes-devtools/build-compare/build-compare_git.bb| 2 +-
 meta/recipes-devtools/createrepo-c/createrepo-c_0.15.7.bb   | 2 +-
 meta/recipes-devtools/distcc/distcc_3.3.3.bb| 2 +-
 meta/recipes-devtools/dnf/dnf_4.2.2.bb  | 2 +-
 meta/recipes-devtools/e2fsprogs/e2fsprogs.inc   | 2 +-
 meta/recipes-devtools/file/file_5.38.bb | 2 +-
 meta/recipes-devtools/glide/glide_0.13.3.bb | 2 +-
 meta/recipes-devtools/gnu-config/gnu-config_git.bb  | 2 +-
 meta/recipes-devtools/go/go-dep_0.5.4.bb| 2 +-
 meta/recipes-devtools/libcomps/libcomps_0.1.15.bb   | 2 +-
 meta/recipes-devtools/libdnf/libdnf_0.28.1.bb   | 2 +-
 meta/recipes-devtools/librepo/librepo_1.11.2.bb | 2 +-
 meta/recipes-devtools/llvm/llvm_git.bb  | 2 +-
 meta/recipes-devtools/mtd/mtd-utils_git.bb  | 2 +-
 meta/recipes-devtools/ninja/ninja_1.10.0.bb | 2 +-
 meta/recipes-devtools/patchelf/patchelf_0.10.bb | 2 +-
 meta/recipes-devtools/rpm/rpm_4.14.2.1.bb   | 2 +-
 meta/recipes-devtools/squashfs-tools/squashfs-tools_git.bb  | 2 +-
 .../systemd-bootchart/systemd-bootchart_233.bb  | 2 +-
 meta/recipes-devtools/tcf-agent/tcf-agent_git.bb| 2 +-
 meta/recipes-devtools/unfs3/unfs3_git.bb| 2 +-
 meta/recipes-extended/go-examples/go-helloworld_0.1.bb  | 2 +-
 meta/recipes-extended/iputils/iputils_s20190709.bb  | 2 +-
 meta/recipes-extended/libaio/libaio_0.3.111.bb  | 2 +-
 meta/recipes-extended/libnsl/libnsl2_git.bb | 2 +-
 meta/recipes-extended/libnss-nis/libnss-nis.bb  | 2 +-
 meta/recipes-extended/libsolv/libsolv_0.7.10.bb | 2 +-
 meta/recipes-extended/ltp/ltp_20200120.bb   | 2 +-
 meta/recipes-extended/procps/procps_3.3.16.bb   | 2 +-
 meta/recipes-extended/psmisc/psmisc_23.3.bb | 2 +-
 meta/recipes-extended/rpcsvc-proto/rpcsvc-proto.bb  | 2 +-
 meta/recipes-extended/stress-ng/stress-ng_0.11.17.bb| 2 +-
 meta/recipes-extended/sysklogd/sysklogd.inc | 2 +-
 meta/recipes-extended/xinetd/xinetd_2.3.15.bb   | 2 +-
 meta/recipes-graphics/libfakekey/libfakekey_git.bb  | 2 +-
 meta/recipes-graphics/libmatchbox/libmatchbox_1.12.bb   | 2 +-

[OE-core][dunfell 1/3] scripts/convert-srcuri: Backport SRC_URI conversion script from master branch

2021-11-04 Thread Steve Sakoman

From: Richard Purdie 

This script handles two emerging issues:

1. There is uncertainty about the default branch name in git going forward.
To try and cover the different possible outcomes, add branch names to all
git:// and gitsm:// SRC_URI entries.

2. Github are dropping support for git:// protocol fetching, so remap github
 urls as needed. For more details see:

https://github.blog/2021-09-01-improving-git-protocol-security-github/

Signed-off-by: Steve Sakoman 
---
 scripts/contrib/convert-srcuri.py | 77 +++
 1 file changed, 77 insertions(+)
 create mode 100755 scripts/contrib/convert-srcuri.py

diff --git a/scripts/contrib/convert-srcuri.py 
b/scripts/contrib/convert-srcuri.py
new file mode 100755
index 00..5b362ea2e8
--- /dev/null
+++ b/scripts/contrib/convert-srcuri.py
@@ -0,0 +1,77 @@
+#!/usr/bin/env python3
+#
+# Conversion script to update SRC_URI to add branch to git urls
+#
+# Copyright (C) 2021 Richard Purdie
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+
+import re
+import os
+import sys
+import tempfile
+import shutil
+import mimetypes
+
+if len(sys.argv) < 2:
+print("Please specify a directory to run the conversion script against.")
+sys.exit(1)
+
+def processfile(fn):
+def matchline(line):
+if "MIRROR" in line or ".*" in line or "GNOME_GIT" in line:
+return False
+return True
+print("processing file '%s'" % fn)
+try:
+if "distro_alias.inc" in fn or "linux-yocto-custom.bb" in fn:
+return
+fh, abs_path = tempfile.mkstemp()
+modified = False
+with os.fdopen(fh, 'w') as new_file:
+with open(fn, "r") as old_file:
+for line in old_file:
+if ("git://" in line or "gitsm://" in line) and "branch=" 
not in line and matchline(line):
+if line.endswith('"\n'):
+line = line.replace('"\n', ';branch=master"\n')
+elif line.endswith(" \\\n"):
+line = line.replace(' \\\n', ';branch=master \\\n')
+modified = True
+if ("git://" in line or "gitsm://" in line) and 
"github.com" in line and "protocol=https" not in line and matchline(line):
+if "protocol=git" in line:
+line = line.replace('protocol=git', 
'protocol=https')
+elif line.endswith('"\n'):
+line = line.replace('"\n', ';protocol=https"\n')
+elif line.endswith(" \\\n"):
+line = line.replace(' \\\n', ';protocol=https 
\\\n')
+modified = True
+new_file.write(line)
+if modified:
+shutil.copymode(fn, abs_path)
+os.remove(fn)
+shutil.move(abs_path, fn)
+except UnicodeDecodeError:
+pass
+
+ourname = os.path.basename(sys.argv[0])
+ourversion = "0.1"
+
+if os.path.isfile(sys.argv[1]):
+processfile(sys.argv[1])
+sys.exit(0)
+
+for targetdir in sys.argv[1:]:
+print("processing directory '%s'" % targetdir)
+for root, dirs, files in os.walk(targetdir):
+for name in files:
+if name == ourname:
+continue
+fn = os.path.join(root, name)
+if os.path.islink(fn):
+continue
+if "/.git/" in fn or fn.endswith(".html") or fn.endswith(".patch") 
or fn.endswith(".m4") or fn.endswith(".diff"):
+continue
+processfile(fn)
+
+print("All files processed with version %s" % ourversion)
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157846): 
https://lists.openembedded.org/g/openembedded-core/message/157846
Mute This Topic: https://lists.openembedded.org/mt/86816372/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell 0/3] Patch review

2021-11-04 Thread Steve Sakoman

Please review these patches for dunfell and have comments back by end of day
Monday.

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2876

The following changes since commit 6cd21ddc6f998eec4d9be05f080e32072fddd2bd:

  tzdata: update 2021d -> 2021e (2021-11-03 11:17:55 +)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Richard Purdie (2):
  scripts/convert-srcuri: Backport SRC_URI conversion script from master
branch
  meta/scripts: Manual git url branch additions

Steve Sakoman (1):
  meta: Add explict branch to git SRC_URIs, handle github url changes

 .../devtool/devtool-upgrade-test2_git.bb  |  2 +-
 .../devtool-upgrade-test2_git.bb.upgraded |  2 +-
 meta/classes/devupstream.bbclass  |  2 +-
 .../distro/include/default-distrovars.inc |  2 +-
 meta/lib/oeqa/selftest/cases/devtool.py   |  4 +-
 meta/lib/oeqa/selftest/cases/recipetool.py|  6 +-
 meta/lib/oeqa/selftest/cases/sstatetests.py   |  2 +-
 meta/recipes-bsp/efibootmgr/efibootmgr_17.bb  |  2 +-
 meta/recipes-bsp/efivar/efivar_37.bb  |  2 +-
 meta/recipes-bsp/opensbi/opensbi_0.6.bb   |  2 +-
 meta/recipes-bsp/u-boot/libubootenv_0.3.1.bb  |  2 +-
 meta/recipes-bsp/u-boot/u-boot-common.inc |  2 +-
 .../connman/connman-gnome_0.7.bb  |  2 +-
 .../libnss-mdns/libnss-mdns_0.14.1.bb |  2 +-
 .../mobile-broadband-provider-info_git.bb |  2 +-
 .../resolvconf/resolvconf_1.82.bb |  2 +-
 meta/recipes-core/dbus-wait/dbus-wait_git.bb  |  2 +-
 meta/recipes-core/expat/expat_2.2.9.bb|  2 +-
 meta/recipes-core/fts/fts_1.2.7.bb|  2 +-
 .../glibc/cross-localedef-native_2.31.bb  |  2 +-
 meta/recipes-core/glibc/glibc-version.inc |  2 +-
 meta/recipes-core/ifupdown/ifupdown_0.8.35.bb |  2 +-
 meta/recipes-core/libxcrypt/libxcrypt.inc |  2 +-
 meta/recipes-core/musl/libucontext_git.bb |  2 +-
 meta/recipes-core/musl/musl-obstack.bb|  2 +-
 meta/recipes-core/musl/musl-utils.bb  |  2 +-
 meta/recipes-core/musl/musl_git.bb|  2 +-
 meta/recipes-core/ncurses/ncurses.inc |  2 +-
 meta/recipes-core/psplash/psplash_git.bb  |  2 +-
 meta/recipes-core/systemd/systemd.inc |  2 +-
 .../update-rc.d/update-rc.d_0.8.bb|  2 +-
 .../bootchart2/bootchart2_0.14.9.bb   |  2 +-
 .../btrfs-tools/btrfs-tools_5.4.1.bb  |  2 +-
 .../build-compare/build-compare_git.bb|  2 +-
 .../createrepo-c/createrepo-c_0.15.7.bb   |  2 +-
 meta/recipes-devtools/distcc/distcc_3.3.3.bb  |  2 +-
 meta/recipes-devtools/dnf/dnf_4.2.2.bb|  2 +-
 meta/recipes-devtools/e2fsprogs/e2fsprogs.inc |  2 +-
 meta/recipes-devtools/file/file_5.38.bb   |  2 +-
 meta/recipes-devtools/glide/glide_0.13.3.bb   |  2 +-
 .../gnu-config/gnu-config_git.bb  |  2 +-
 meta/recipes-devtools/go/go-dep_0.5.4.bb  |  2 +-
 .../libcomps/libcomps_0.1.15.bb   |  2 +-
 meta/recipes-devtools/libdnf/libdnf_0.28.1.bb |  2 +-
 .../librepo/librepo_1.11.2.bb |  2 +-
 meta/recipes-devtools/llvm/llvm_git.bb|  2 +-
 meta/recipes-devtools/mtd/mtd-utils_git.bb|  2 +-
 meta/recipes-devtools/ninja/ninja_1.10.0.bb   |  2 +-
 .../patchelf/patchelf_0.10.bb |  2 +-
 meta/recipes-devtools/rpm/rpm_4.14.2.1.bb |  2 +-
 .../squashfs-tools/squashfs-tools_git.bb  |  2 +-
 .../systemd-bootchart_233.bb  |  2 +-
 .../tcf-agent/tcf-agent_git.bb|  2 +-
 meta/recipes-devtools/unfs3/unfs3_git.bb  |  2 +-
 .../go-examples/go-helloworld_0.1.bb  |  2 +-
 .../iputils/iputils_s20190709.bb  |  2 +-
 .../recipes-extended/libaio/libaio_0.3.111.bb |  2 +-
 meta/recipes-extended/libnsl/libnsl2_git.bb   |  2 +-
 .../recipes-extended/libnss-nis/libnss-nis.bb |  2 +-
 .../libsolv/libsolv_0.7.10.bb |  2 +-
 meta/recipes-extended/ltp/ltp_20200120.bb |  2 +-
 meta/recipes-extended/procps/procps_3.3.16.bb |  2 +-
 meta/recipes-extended/psmisc/psmisc_23.3.bb   |  2 +-
 .../rpcsvc-proto/rpcsvc-proto.bb  |  2 +-
 .../stress-ng/stress-ng_0.11.17.bb|  2 +-
 meta/recipes-extended/sysklogd/sysklogd.inc   |  2 +-
 meta/recipes-extended/xinetd/xinetd_2.3.15.bb |  2 +-
 .../libfakekey/libfakekey_git.bb  |  2 +-
 .../libmatchbox/libmatchbox_1.12.bb   |  2 +-
 .../libva/libva-utils_2.6.0.bb|  2 +-
 .../matchbox-wm/matchbox-wm_1.2.2.bb  |  2 +-
 meta/recipes-graphics/mx/mx-1.0_1.4.7.bb  |  2 +-
 meta/recipes-graphics/piglit/piglit_git.bb|  2 +-
 .../virglrenderer/virglrenderer_0.8.2.bb  |  2 +-
 meta/recipes-graphics/vulkan/assimp_5.0.1.bb  |  2 +-
 .../vulkan/vulkan-demos_git.bb|  6 +-
 .../vulkan/vulkan-headers_1.1.126.0.bb

[OE-core] [PATCH] opkg: Fix poor operator combination choice

2021-11-04 Thread Richard Purdie

Combining :append with += rarely makes sense. Improve it to use the standard
format (and tweak the implied spacing).

Signed-off-by: Richard Purdie 
---
 meta/recipes-devtools/opkg/opkg_0.4.5.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/opkg/opkg_0.4.5.bb 
b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
index 2760fc58786..8af047a51ff 100644
--- a/meta/recipes-devtools/opkg/opkg_0.4.5.bb
+++ b/meta/recipes-devtools/opkg/opkg_0.4.5.bb
@@ -60,7 +60,7 @@ do_install_ptest () {
sed -i -e '/@PYTHONPATH=. $(PYTHON) $^/a\\t@if [ "$$?" != "0" ];then 
echo "FAIL:"$^;else echo "PASS:"$^;fi' ${D}${PTEST_PATH}/tests/Makefile
 }
 
-WARN_QA:append += "openssl-deprecation"
+WARN_QA:append = " openssl-deprecation"
 QAPKGTEST[openssl-deprecation] = "package_qa_check_openssl_deprecation"
 def package_qa_check_openssl_deprecation (package, d, messages):
 sane = True
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157844): 
https://lists.openembedded.org/g/openembedded-core/message/157844
Mute This Topic: https://lists.openembedded.org/mt/86816265/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] meson: set objcopy in the cross and native toolchain files

2021-11-04 Thread Ross Burton

Signed-off-by: Ross Burton 
---
 meta/classes/meson.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
index da58cb4bec..4ba70de3dc 100644
--- a/meta/classes/meson.bbclass
+++ b/meta/classes/meson.bbclass
@@ -48,6 +48,7 @@ ar = ${@meson_array('AR', d)}
 nm = ${@meson_array('NM', d)}
 strip = ${@meson_array('STRIP', d)}
 readelf = ${@meson_array('READELF', d)}
+objcopy = ${@meson_array('OBJCOPY', d)}
 pkgconfig = 'pkg-config'
 llvm-config = 'llvm-config${LLVMVERSION}'
 cups-config = 'cups-config'
@@ -85,6 +86,7 @@ ar = ${@meson_array('BUILD_AR', d)}
 nm = ${@meson_array('BUILD_NM', d)}
 strip = ${@meson_array('BUILD_STRIP', d)}
 readelf = ${@meson_array('BUILD_READELF', d)}
+objcopy = ${@meson_array('BUILD_OBJCOPY', d)}
 pkgconfig = 'pkg-config-native'
 
 [built-in options]
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157843): 
https://lists.openembedded.org/g/openembedded-core/message/157843
Mute This Topic: https://lists.openembedded.org/mt/86815859/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD license

2021-11-04 Thread Ross Burton

Sorry, missed this email.

I copied the license from libx11, as it is the same tarball.  It was
Joshua Watt who introduced the expanded licenses in
44fd2aa731956fe0a0f74d36959c88b0b87adab5.

Ross

On Thu, 4 Nov 2021 at 11:19, Peter Kjellerstedt
 wrote:
>
> Ross: any comment to my question below?
>
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org  > c...@lists.openembedded.org> On Behalf Of Peter Kjellerstedt
> > Sent: den 28 oktober 2021 17:44
> > To: Ross Burton 
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> > license
> >
> > > -Original Message-
> > > From: openembedded-core@lists.openembedded.org  > > c...@lists.openembedded.org> On Behalf Of Ross Burton
> > > Sent: den 2 september 2021 18:25
> > > To: openembedded-core@lists.openembedded.org
> > > Subject: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> > > license
> > >
> > > "BSD" is ambiguous, use the precise licenses BSD-2-Clause BSD-4-Clause.
> > >
> > > Signed-off-by: Ross Burton 
> > > ---
> > >  meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > index 7519b4c018d..e53ccc6aea8 100644
> > > --- a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > +++ b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > > @@ -8,7 +8,7 @@ python () {
> > >
> > >  require xorg-lib-common.inc
> > >
> > > -LICENSE = "MIT & MIT-style & BSD"
> > > +LICENSE = "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
> >
> > Why is this marked as BSD-4-Clause? Looking at the COPYING file and
> > searching the code I can find no trace of any license text with the
> > advertising clause from BSD-4-Clause. What am I missing?
> >
> > >  LIC_FILES_CHKSUM =
> > "file://COPYING;md5=172255dee66bb0151435b2d5d709fcf7"
> > >
> > >  SRC_URI[md5sum] = "c5fa5a86a20e3591bed6c046498d4b8f"
> > > --
> > > 2.25.1
> >
> > //Peter
>
> //Peter
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157842): 
https://lists.openembedded.org/g/openembedded-core/message/157842
Mute This Topic: https://lists.openembedded.org/mt/85331681/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD license

2021-11-04 Thread Peter Kjellerstedt

Ross: any comment to my question below?

> -Original Message-
> From: openembedded-core@lists.openembedded.org  c...@lists.openembedded.org> On Behalf Of Peter Kjellerstedt
> Sent: den 28 oktober 2021 17:44
> To: Ross Burton 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> license
> 
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org  > c...@lists.openembedded.org> On Behalf Of Ross Burton
> > Sent: den 2 september 2021 18:25
> > To: openembedded-core@lists.openembedded.org
> > Subject: [OE-core] [PATCH 11/14] libx11-compose-data: set precise BSD
> > license
> >
> > "BSD" is ambiguous, use the precise licenses BSD-2-Clause BSD-4-Clause.
> >
> > Signed-off-by: Ross Burton 
> > ---
> >  meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > index 7519b4c018d..e53ccc6aea8 100644
> > --- a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > +++ b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
> > @@ -8,7 +8,7 @@ python () {
> >
> >  require xorg-lib-common.inc
> >
> > -LICENSE = "MIT & MIT-style & BSD"
> > +LICENSE = "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
> 
> Why is this marked as BSD-4-Clause? Looking at the COPYING file and
> searching the code I can find no trace of any license text with the
> advertising clause from BSD-4-Clause. What am I missing?
> 
> >  LIC_FILES_CHKSUM =
> "file://COPYING;md5=172255dee66bb0151435b2d5d709fcf7"
> >
> >  SRC_URI[md5sum] = "c5fa5a86a20e3591bed6c046498d4b8f"
> > --
> > 2.25.1
> 
> //Peter

//Peter


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157841): 
https://lists.openembedded.org/g/openembedded-core/message/157841
Mute This Topic: https://lists.openembedded.org/mt/85331681/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH RFC 1/2] package: Introduce PACKAGE_GLOBAL_RENAMES

2021-11-04 Thread Richard Purdie

Allow renaming of packages on a global basis to work, e.g.:

PACKAGE_GLOBAL_RENAMES[bash] = "busybox"

Note this happens at package creation time and build time dependencies
remain as written.

This does have the potential to replace the horrific VIRTUAL-RUNTIME*
variables, see the follow up patch.

Signed-off-by: Richard Purdie 
---
 meta/classes/image.bbclass |  7 ---
 meta/classes/package.bbclass   | 16 ++--
 meta/classes/populate_sdk_base.bbclass |  9 +
 3 files changed, 19 insertions(+), 13 deletions(-)

diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 2fa69a40d10..b3f5421697d 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -236,9 +236,10 @@ fakeroot python do_rootfs () {
 # otherwise, the multilib renaming could step in and squash any fixups that
 # may have occurred.
 pn = d.getVar('PN')
-runtime_mapping_rename("PACKAGE_INSTALL", pn, d)
-runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", pn, d)
-runtime_mapping_rename("BAD_RECOMMENDATIONS", pn, d)
+remaps = d.getVarFlags("PACKAGE_GLOBAL_RENAMES")
+runtime_mapping_rename("PACKAGE_INSTALL", pn, remaps, d)
+runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", pn, remaps, d)
+runtime_mapping_rename("BAD_RECOMMENDATIONS", pn, remaps, d)
 
 # Generate the initial manifest
 create_manifest(d)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 92eba988929..aad58ead977 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -612,9 +612,12 @@ def copydebugsources(debugsrcdir, sources, d):
 # Package data handling routines
 #
 
-def get_package_mapping (pkg, basepkg, d, depversions=None):
+def get_package_mapping(pkg, basepkg, remaps, d, depversions=None):
 import oe.packagedata
 
+if pkg in remaps:
+pkg = remaps[pkg]
+
 data = oe.packagedata.read_subpkgdata(pkg, d)
 key = "PKG:%s" % pkg
 
@@ -646,13 +649,13 @@ def get_package_additional_metadata (pkg_type, d):
 metadata_fields = [field.strip() for field in oe.data.typed_value(key, 
d)]
 return "\n".join(metadata_fields).strip()
 
-def runtime_mapping_rename (varname, pkg, d):
+def runtime_mapping_rename(varname, pkg, remaps, d):
 #bb.note("%s before: %s" % (varname, d.getVar(varname)))
 
 new_depends = {}
 deps = bb.utils.explode_dep_versions2(d.getVar(varname) or "")
 for depend, depversions in deps.items():
-new_depend = get_package_mapping(depend, pkg, d, depversions)
+new_depend = get_package_mapping(depend, pkg, remaps, d, depversions)
 if depend != new_depend:
 bb.note("package name mapping done: %s -> %s" % (depend, 
new_depend))
 new_depends[new_depend] = deps[depend]
@@ -2512,6 +2515,7 @@ def mapping_rename_hook(d):
 like debian.bbclass or manual PKG variable name changes
 """
 pkg = d.getVar("PKG")
-runtime_mapping_rename("RDEPENDS", pkg, d)
-runtime_mapping_rename("RRECOMMENDS", pkg, d)
-runtime_mapping_rename("RSUGGESTS", pkg, d)
+remaps = d.getVarFlags("PACKAGE_GLOBAL_RENAMES")
+runtime_mapping_rename("RDEPENDS", pkg, remaps, d)
+runtime_mapping_rename("RRECOMMENDS", pkg, remaps, d)
+runtime_mapping_rename("RSUGGESTS", pkg, remaps, d)
diff --git a/meta/classes/populate_sdk_base.bbclass 
b/meta/classes/populate_sdk_base.bbclass
index fafdd96749c..55c36e1108d 100644
--- a/meta/classes/populate_sdk_base.bbclass
+++ b/meta/classes/populate_sdk_base.bbclass
@@ -152,13 +152,14 @@ def populate_sdk_common(d):
 d.setVar("PACKAGE_INSTALL_ATTEMPTONLY", ' '.join(inst_attempt_pkgs))
 
 pn = d.getVar('PN')
-runtime_mapping_rename("TOOLCHAIN_TARGET_TASK", pn, d)
-runtime_mapping_rename("TOOLCHAIN_TARGET_TASK_ATTEMPTONLY", pn, d)
+remaps = d.getVarFlags("PACKAGE_GLOBAL_RENAMES")
+runtime_mapping_rename("TOOLCHAIN_TARGET_TASK", pn, remaps, d)
+runtime_mapping_rename("TOOLCHAIN_TARGET_TASK_ATTEMPTONLY", pn, remaps, d)
 
 ld = bb.data.createCopy(d)
 ld.setVar("PKGDATA_DIR", 
"${STAGING_DIR}/${SDK_ARCH}-${SDKPKGSUFFIX}${SDK_VENDOR}-${SDK_OS}/pkgdata")
-runtime_mapping_rename("TOOLCHAIN_HOST_TASK", pn, ld)
-runtime_mapping_rename("TOOLCHAIN_HOST_TASK_ATTEMPTONLY", pn, ld)
+runtime_mapping_rename("TOOLCHAIN_HOST_TASK", pn, remaps, ld)
+runtime_mapping_rename("TOOLCHAIN_HOST_TASK_ATTEMPTONLY", pn, remaps, ld)
 d.setVar("TOOLCHAIN_HOST_TASK", ld.getVar("TOOLCHAIN_HOST_TASK"))
 d.setVar("TOOLCHAIN_HOST_TASK_ATTEMPTONLY", 
ld.getVar("TOOLCHAIN_HOST_TASK_ATTEMPTONLY"))
 
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157840): 
https://lists.openembedded.org/g/openembedded-core/message/157840
Mute This Topic: https://lists.openembedded.org/mt/86813103/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe:

[OE-core] [PATCH RFC 2/2] conf/recipes: Replace VIRTUAL-RUNTIME with PACKAGE_GLOBAL_RENAMES

2021-11-04 Thread Richard Purdie

I don't think anyone has ever liked VIRTUAL-RUNTIME as a solution. This patch
replaces it with PACKAGE_GLOBAL_RENAME.

There are two types of VIRTUAL-RUNTIME. Direct package replacements like
getopt or keymaps and "namespaces" for things like "device-manager" or
"login-manager". The later are different in that one recipe may provide
several but they need to be configured individually. If they were all
"systemd", we couldn't replace the correct ones.

As such this patch introduces the "virtual-XXX" namespace where the
system is expected to resolve these into final values as per the configuration.

The advantage of this approach is that we no longer need to have specific
VIRTUAL-RUNTIME parameterisation for a user to change a particular dependency,
they can just do things like:

PACKAGE_GLOBAL_RENAME[keymaps] = "mykeymaps"

or simply:

PACKAGE_GLOBAL_RENAME[keymaps] = ""

to remove it. You can see examples of the virtual-* mappings in the init 
manager includes.

This patch uses the PACKAGE_GLOBAL_RENAMES variable and mechanism from the
previous patch to function but to be clear, this only works at package
creation time, not at build time. As such we have to inject the virtual
namespace into RPROVIDES. Filtering all package variables at parse time
isn't really viable at present (the multilib classes show the work involved).

Known issues:
a) The changes apply at final image build time which means that the original
provider would be built and the alternate only swapped in at do_rootfs.
b) The patch throwns build-rdeps QA warnings (probably as a result of a).
c) As a result of b) there are probably missing build dependencies
d) The tests are unconverted.

As such I suspect this patch won't quite work but I want to share it and
see what people think and if a better solution could rise from this as a
result. Adding "filter" support to variables as JPEW and I once discussed
may be a different way of handling this which would also handle some multilib
issues.

Signed-off-by: Richard Purdie 
---
 meta/classes/base.bbclass |  6 +
 meta/classes/image.bbclass|  3 ++-
 meta/classes/multilib_global.bbclass  |  5 +
 meta/classes/package.bbclass  |  4 +++-
 meta/classes/packagegroup.bbclass |  4 ++--
 meta/classes/update-alternatives.bbclass  |  5 +
 .../conf/distro/include/default-providers.inc | 13 +--
 .../include/init-manager-mdev-busybox.inc |  9 
 .../conf/distro/include/init-manager-none.inc |  7 +++---
 .../distro/include/init-manager-systemd.inc   |  9 
 .../distro/include/init-manager-sysvinit.inc  |  7 +++---
 meta/conf/layer.conf  |  2 +-
 meta/lib/oe/rootfs.py |  2 +-
 meta/recipes-core/busybox/busybox.inc |  4 ++--
 meta/recipes-core/busybox/busybox_1.34.1.bb   |  6 ++---
 .../images/core-image-minimal-initramfs.bb|  2 +-
 .../images/core-image-tiny-initramfs.bb   |  4 +---
 .../initrdscripts/initramfs-framework_1.0.bb  |  4 ++--
 .../initramfs-live-install-efi_1.0.bb |  4 ++--
 .../initramfs-live-install_1.0.bb |  4 ++--
 .../initramfs-module-install-efi_1.0.bb   |  4 ++--
 .../initramfs-module-install_1.0.bb   |  4 ++--
 .../packagegroups/packagegroup-base.bb|  9 +++-
 .../packagegroups/packagegroup-core-boot.bb   | 22 ---
 meta/recipes-devtools/dpkg/dpkg.inc   |  2 +-
 meta/recipes-devtools/opkg/opkg_0.4.5.bb  |  2 +-
 meta/recipes-extended/lsb/lsb-release_1.4.bb  |  2 +-
 .../packagegroup-core-base-utils.bb   |  4 +---
 .../packagegroup-core-full-cmdline.bb |  9 
 .../packagegroups/packagegroup-core-weston.bb |  2 +-
 .../packagegroups/packagegroup-core-x11.bb|  9 +---
 meta/recipes-graphics/wayland/weston-init.bb  |  6 ++---
 meta/recipes-graphics/wayland/weston_9.0.0.bb |  2 +-
 .../gstreamer/gstreamer1.0-omx_1.18.5.bb  |  3 +--
 34 files changed, 88 insertions(+), 96 deletions(-)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index a65fcc6c1db..1395df4a02c 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -334,6 +334,12 @@ python base_eventhandler() {
 profprov = d.getVar("PREFERRED_PROVIDER_" + p)
 if profprov and pn != profprov:
 raise bb.parse.SkipRecipe("PREFERRED_PROVIDER_%s set 
to %s, not %s" % (p, profprov, pn))
+
+
+remaps = d.getVarFlags("PACKAGE_GLOBAL_RENAMES")
+for m in remaps:
+if m.startswith("virtual-"):
+d.setVar("RPROVIDES:" + remaps[m] + ":append", " " + m)
 }
 
 CONFIGURESTAMPFILE = "${WORKDIR}/configure.sstate"
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index b3f5421697d..605dcc9eee2 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -43,7 +43,7 @@ IMAGE_INSTALL_DEBUGFS ?= ""
 
 # These

[OE-core] [PATCH RFC 0/2] Replace VIRTUAL-RUNTIME variables

2021-11-04 Thread Richard Purdie

The VIRTUAL-RUNTIME variables are a hack and not fit for purpose.
These patches replace it with something different. There are some
issues listed in the second patch which probably rule out the 
implmentation as is but I liked it enough to get it this far and
maybe some better solution can rise from the ideas here.

Richard Purdie (2):
  package: Introduce PACKAGE_GLOBAL_RENAMES
  conf/recipes: Replace VIRTUAL-RUNTIME with PACKAGE_GLOBAL_RENAMES

 meta/classes/base.bbclass |  6 +
 meta/classes/image.bbclass| 10 +
 meta/classes/multilib_global.bbclass  |  5 +
 meta/classes/package.bbclass  | 18 ++-
 meta/classes/packagegroup.bbclass |  4 ++--
 meta/classes/populate_sdk_base.bbclass|  9 
 meta/classes/update-alternatives.bbclass  |  5 +
 .../conf/distro/include/default-providers.inc | 13 +--
 .../include/init-manager-mdev-busybox.inc |  9 
 .../conf/distro/include/init-manager-none.inc |  7 +++---
 .../distro/include/init-manager-systemd.inc   |  9 
 .../distro/include/init-manager-sysvinit.inc  |  7 +++---
 meta/conf/layer.conf  |  2 +-
 meta/lib/oe/rootfs.py |  2 +-
 meta/recipes-core/busybox/busybox.inc |  4 ++--
 meta/recipes-core/busybox/busybox_1.34.1.bb   |  6 ++---
 .../images/core-image-minimal-initramfs.bb|  2 +-
 .../images/core-image-tiny-initramfs.bb   |  4 +---
 .../initrdscripts/initramfs-framework_1.0.bb  |  4 ++--
 .../initramfs-live-install-efi_1.0.bb |  4 ++--
 .../initramfs-live-install_1.0.bb |  4 ++--
 .../initramfs-module-install-efi_1.0.bb   |  4 ++--
 .../initramfs-module-install_1.0.bb   |  4 ++--
 .../packagegroups/packagegroup-base.bb|  9 +++-
 .../packagegroups/packagegroup-core-boot.bb   | 22 ---
 meta/recipes-devtools/dpkg/dpkg.inc   |  2 +-
 meta/recipes-devtools/opkg/opkg_0.4.5.bb  |  2 +-
 meta/recipes-extended/lsb/lsb-release_1.4.bb  |  2 +-
 .../packagegroup-core-base-utils.bb   |  4 +---
 .../packagegroup-core-full-cmdline.bb |  9 
 .../packagegroups/packagegroup-core-weston.bb |  2 +-
 .../packagegroups/packagegroup-core-x11.bb|  9 +---
 meta/recipes-graphics/wayland/weston-init.bb  |  6 ++---
 meta/recipes-graphics/wayland/weston_9.0.0.bb |  2 +-
 .../gstreamer/gstreamer1.0-omx_1.18.5.bb  |  3 +--
 35 files changed, 106 insertions(+), 108 deletions(-)

-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157838): 
https://lists.openembedded.org/g/openembedded-core/message/157838
Mute This Topic: https://lists.openembedded.org/mt/86813100/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [V2][PATCH] ruby: workaround ptest hang problem

2021-11-04 Thread Alexander Kanavin

On Thu, 4 Nov 2021 at 02:42, Changqing Li 
wrote:

> @@ -85,12 +85,12 @@ PTESTS_SLOW = "\
>  tcl-ptest \
>  util-linux-ptest \
>  valgrind-ptest \
> +ruby-ptest \
>  "
>

Thanks, can you insert this in alphabetical order? Also please add to the
commit message how long does the test take.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157837): 
https://lists.openembedded.org/g/openembedded-core/message/157837
Mute This Topic: https://lists.openembedded.org/mt/86807541/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

45 matches

Mail list logo