On Wed, 14 Sept 2022 at 07:49, ChenQi wrote:
> I'm reluctant to agree that this is like machine and distro, because
> it's a hard requirement that machine and distro definitions be under
> some layer, otherwise how can bitbake get info about it? But
> TEMPLATECONF seems to be a different case, it
From: Mingli Yu
Add devmem 128-bit support [1].
[1]
https://git.busybox.net/busybox/commit/?id=d432049f288c9acdc4a7caa729c68ceba3c5dca1
Signed-off-by: Mingli Yu
---
.../0001-devmem-add-128-bit-width.patch | 128 ++
meta/recipes-core/busybox/busybox/defconfig | 2 +-
On 9/14/22 16:03, Alexander Kanavin wrote:
On Wed, 14 Sept 2022 at 09:42, ChenQi wrote:
Yes. The bblayers.conf.sample is generated dynamically according to
project setup.
Can we step back for a moment, I'd like to know more about how you do
this. Is the code that does dynamic generation of
Hi Etienne,
On 9/13/22 17:25, Etienne Cordonnier via lists.openembedded.org wrote:
editline is a BSD alternative for readline which is GPLv3.
Signed-off-by: Etienne Cordonnier
---
meta/recipes-devtools/python/python3_3.10.6.bb | 1 +
1 file changed, 1 insertion(+)
diff --git
I can only think of patching openssl to pick up a oe-specific
environment variable pointing to staging_libdir_native - making a
wrapper for every native binary that sets those variables doesn't seem
feasible.
Alex
On Wed, 14 Sept 2022 at 10:09, Mikko Rapeli wrote:
>
> Hi,
>
> Found the root
On Wed, 14 Sept 2022 at 11:45, Alexander Kanavin wrote:
> But I'm not asking to make wrappers. I'm asking to patch openssl code
> itself to check for an oe-specific environment variable where it's
> making the decision where these things should be looked for. We
> already do this with native
On Wed, 14 Sept 2022 at 10:17, ChenQi wrote:
> The codes are in: https://github.com/WindRiver-Labs/wrlinux-x
>
> e.g.
>
> ./wrlinux-x/setup.sh --all-layers (this pulls down all supported layers)
>
> ./wrlinux-x/setup.sh --all-layers --dl-layers (this pulls down all
> supported layers, together
On Wed, 2022-09-14 at 11:09 +0300, Mikko Rapeli wrote:
> Hi,
>
> Found the root cause. As suggested on #pyco too maybe native openssl
> was mising legacy support.
> It wasn't but loading the on purpose hidden openssl legacy.so was
> failing. It is located in
>
Hi,
Found the root cause. As suggested on #pyco too maybe native openssl
was mising legacy support.
It wasn't but loading the on purpose hidden openssl legacy.so was
failing. It is located in
recipe-sysroot-native/usr/lib/ossl-modules/legacy.so and only found
via OPENSSL_MODULES
variable which
But I'm not asking to make wrappers. I'm asking to patch openssl code
itself to check for an oe-specific environment variable where it's
making the decision where these things should be looked for. We
already do this with native python.
Alex
On Wed, 14 Sept 2022 at 10:43, Mikko Rapeli wrote:
>
On 9/14/22 14:39, Alexander Kanavin wrote:
On Wed, 14 Sept 2022 at 07:49, ChenQi wrote:
I'm reluctant to agree that this is like machine and distro, because
it's a hard requirement that machine and distro definitions be under
some layer, otherwise how can bitbake get info about it? But
On Wed, 14 Sept 2022 at 09:42, ChenQi wrote:
> Yes. The bblayers.conf.sample is generated dynamically according to
> project setup.
Can we step back for a moment, I'd like to know more about how you do
this. Is the code that does dynamic generation of the list in bblayers
published somewhere?
From: Chee Yang Lee
backport fix for:
CVE-2022-1920
CVE-2022-1921
CVE-2022-1922
CVE-2022-1923
CVE-2022-1924
CVE-2022-1925
CVE-2022-2122
also set ignore at gstreamer1.0_1.16.3.bb
Signed-off-by: Chee Yang Lee
---
.../CVE-2022-1920.patch | 59 +
From: Chee Yang Lee
backport fixes:
CVE-2020-13754, backport patches as debian security tracker notes
https://security-tracker.debian.org/tracker/CVE-2020-13754
CVE-2021-3713
CVE-2021-3748
CVE-2021-3930
CVE-2021-4206
CVE-2021-4207
CVE-2022-0216, does not include qtest in patches, the qtest
On Wed, 14 Sept 2022 at 11:19, Alexander Kanavin wrote:
> I can only think of patching openssl to pick up a oe-specific
> environment variable pointing to staging_libdir_native - making a
> wrapper for every native binary that sets those variables doesn't seem
> feasible.
Hmm. I'm a bit worried
On Wed, 14 Sept 2022 at 10:51, Mikko Rapeli wrote:
> Was there some discussion in the past with openssl upstream about how
> to find config
> files, modules etc, or was there some alignment with e.g. Debian package?
I'm not aware of any such. Please open a ticket, and link to it in any
proposed
ello Everyone
We perform yocto build and do devtool modify for one of package it works
if we perform devtool modify for another package without resetting the
previously modified package we are getting below error in modified package
during parsing bb step
recipefile:
From: Andrei Gherzan
The _exec_shell_cmd function is used by a couple of other functions that
are ultimatelly called from the create_rootfs function. The latter is
used in image bbclass' do_rootfs which is running using the fakeroot
support in bitbake. This makes the fakeroot support in
Note, the following items from meta-oe are still not compatible and
fail as of now:
python3-pycocotools
python3-pybluez
python3-gevent
python3-cchardet
python3-grpcio
python3-wxgtk4
Alex
On Wed, 14 Sept 2022 at 14:04, Alexander Kanavin via
lists.openembedded.org
wrote:
>
> The semaphore fix
I ran a build of core-image-full-cmdline using xz and zstd, using
pre-populated downloads and sstate-cache directories but with empty tmp
directory. Here are the numbers:
zstd:
bitbake core-image-full-cmdline took 2m52.768s (real), the resulting
directory tmp/deploy/ipk is 1.6GB big.
xz:
bitbake
This allows the use of zstd for opkg packages by using OPKGBUILDCMD:
OPKGBUILDCMD = "opkg-build -Z zstd"
Signed-off-by: Alex Feinman
Signed-off-by: Etienne Cordonnier
---
meta/recipes-devtools/opkg/opkg_0.6.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git
Also note that zstd's default compression level is 3 per default (from a 1
to 19 scale). I did not test other compression levels.
On Wed, Sep 14, 2022 at 11:58 AM Etienne Cordonnier <
ecordonn...@snapchat.com> wrote:
> I ran a build of core-image-full-cmdline using xz and zstd, using
>
The semaphore fix has landed and is available from 3.11 onwards:
https://github.com/python/cpython/commit/1ee0f94d16f150356a4b9b0a39d44ba1d2d5b9fc
3.11 release schedule: https://peps.python.org/pep-0664/
Drop 0001-Mitigate-the-race-condition-in-testSockName.patch
as it is merged upstream.
The character '%' is not a valid part of a recipe filename and has been used
here only to suggest a wildcard regarding the recipe's version, see reply [1] in
a companioned thread. Correct that by using the current recipe version instead.
[1] https://lists.yoctoproject.org/g/docs/message/3165
Thanks for checking.
I'd be interested to know if setting a higher compression level for zstd
can get us to a similar compression ratio to xz. If so, then I think it
could be some real value to distro maintainers to be able to *tune*
their compression.
That's not blocking for your new PR
On 2022-09-14 03:20, Yu, Mingli wrote:
From: Mingli Yu
Add devmem 128-bit support [1].
We should merge to master as well but I don't think we need to enable
devmem, especially in kirkstone.
If a user wants to do that, that's fine.
My notes:
I think that back-porting this commit is low
Dear all,
(cross-posting to oe-core and *-architecture)
In the last months, we have worked in Oniro on using the create-spdx
class for both IP compliance and security.
During this work, Alberto Pianon has found that some information is
missing from the SBOM and it does not contain enough for
On Wed, Sep 14, 2022 at 9:16 AM Marta Rybczynska wrote:
>
> Dear all,
> (cross-posting to oe-core and *-architecture)
> In the last months, we have worked in Oniro on using the create-spdx
> class for both IP compliance and security.
>
> During this work, Alberto Pianon has found that some
On Wed, Sep 14, 2022 at 4:08 AM Randy MacLeod
wrote:
>
> On 2022-09-14 03:20, Yu, Mingli wrote:
>
> From: Mingli Yu
>
> Add devmem 128-bit support [1].
>
> We should merge to master as well but I don't think we need to enable devmem,
> especially in kirkstone.
> If a user wants to do that,
From: Chee Yang Lee
backport fixes:
CVE-2021-27918
CVE-2021-36221
CVE-2021-39293
CVE-2021-41771
ignore:
CVE-2022-29526
CVE-2022-30634
Signed-off-by: Chee Yang Lee
---
meta/recipes-devtools/go/go-1.14.inc | 10 +
.../go/go-1.14/CVE-2021-27918.patch | 191 ++
ACK from me.
On 9/14/22 04:59, Etienne Cordonnier via lists.openembedded.org wrote:
This allows the use of zstd for opkg packages by using OPKGBUILDCMD:
OPKGBUILDCMD = "opkg-build -Z zstd"
Signed-off-by: Alex Feinman
Signed-off-by: Etienne Cordonnier
---
On Wed, Sep 14, 2022 at 8:37 AM Alex Stewart wrote:
>
> Thanks for checking.
>
> I'd be interested to know if setting a higher compression level for zstd
> can get us to a similar compression ratio to xz. If so, then I think it
> could be some real value to distro maintainers to be able to *tune*
Hi Paulo
Is it possible to do the transition from unfsd to nfs-ganesha step by
step?
1. Add nfs-ganesha
2. Refactor runqemu-export-rootfs to work with ganesha.nfsd instead
of unfsd.
3. Remove unfs3
My conclusion so far is that just removing the unfs3 recipe would break
On Wed, Sep 14, 2022 at 12:10 PM Alberto Pianon wrote:
>
> Hi Joshua,
>
> nice to meet you!
>
> I'm new to this list, and I've always approached Yocto just from the
> "IP compliance side", so I may miss important pieces of information.
> That
> is why Marta encouraged me and is helping me to ask
From: wangmy
Changelog:
==
* [build] meson: fix typo in variable name
* [build] autoconf: report if building with zstd
* [build] meson -Dlua_version=... to specify lua ver
* [core] avoid CCRandomGenerateBytes on MacOS <10.12 (fixes #3140)
* [core] use diff var name w/
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 3163134b0f58c58aaabe4e957c30109e63b2d60f)
Signed-off-by: Sakib Sajal
Signed-off-by: Steve Sakoman
---
.../lighttpd/{lighttpd_1.4.65.bb =>
From: Richard Purdie
Includes fixes for CVE-2022-3099 and CVE-2022-3134.
Signed-off-by: Richard Purdie
(cherry picked from commit d042923262130b6b96f703b5cd4184f659caeb92)
Signed-off-by: Steve Sakoman
---
meta/recipes-support/vim/vim.inc | 4 ++--
1 file changed, 2 insertions(+), 2
Please review this set of patches for kirkstone and have comments back by end
of day Friday. This should be the final set of patches for the 4.0.4 release.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4225
The following changes since commit
From: "niko.ma...@vaisala.com"
Commit 8089cefed8e83c0348037768c292058f1bcbbbe5 ("systemd: Add
PACKAGECONFIG for sysvinit") decoupled enabling of systemd's sysvinit
handling behavior behind a distinct PACKAGECONFIG feature.
This new option affects among other things the installing of
From: "niko.ma...@vaisala.com"
systemd defines a default set of fallback DNS servers in
https://github.com/systemd/systemd/blob/v251/meson_options.txt#L328-L330
By adding a PACKAGECONFIG knob providing a convenient way to opt out,
and then adding that value to systemd's PACKAGECONFIG, the
Hi Joshua,
nice to meet you!
I'm new to this list, and I've always approached Yocto just from the
"IP compliance side", so I may miss important pieces of information.
That
is why Marta encouraged me and is helping me to ask community feedback.
Il 2022-09-14 16:56 Joshua Watt ha scritto:
On
I am trying to integrate cockpit recipe in my image.
cockpit is a web based linux managment tool.
cockpit is supported mosly in well know distors.
the recipe i am using is based on tag 220.
main problems I am trying to overcome:
1. in first login after image was flashed to emmc. the user is
From: Teoh Jay Shen
Upstream-Status: Backport
[https://github.com/golang/go/commit/5bc9106458fc07851ac324a4157132a91b1f3479]
Signed-off-by: Teoh Jay Shen
---
meta/recipes-devtools/go/go-1.17.13.inc | 1 +
.../go/go-1.18/CVE-2022-27664.patch | 102 ++
2 files
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 14 september 2022 09:42
> To: ChenQi
> Cc: OE-core ; Alexander Kanavin
>
> Subject: Re: [OE-core] [PATCH 1/7] scripts/oe-setup-builddir: add a
These modules outside of perl-modules are necessary to run curl-ptests
Signed-off-by: Khem Raj
---
meta/recipes-support/curl/curl_7.85.0.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-support/curl/curl_7.85.0.bb
b/meta/recipes-support/curl/curl_7.85.0.bb
On 9/14/22 9:56 AM, Joshua Watt wrote:
On Wed, Sep 14, 2022 at 9:16 AM Marta Rybczynska wrote:
Dear all,
(cross-posting to oe-core and *-architecture)
In the last months, we have worked in Oniro on using the create-spdx
class for both IP compliance and security.
During this work, Alberto
46 matches
Mail list logo
