You can set BB_NO_NETWORK and check what fails to build from local DL_DIR.
On Thu, May 23, 2024 at 11:46 AM gauravpathak129 via
lists.yoctoproject.org
wrote:
>
> Hello Experts,
>
> I am wondering if there is any built in "Yocto way" of listing all the
> recipes/packages which accessed network
/message/2007
* it's fatal error since:
https://git.openembedded.org/openembedded-core/commit/?h=master=32cba1cc916ad530c5e6630a927e74ca6f06289b
Signed-off-by: Martin Jansa
---
recipes-mac/smack/mmap-smack-test_1.0.bb | 4 +++-
recipes-mac/smack/smack-test_1.0.bb | 5 +++--
recipes-mac
-off-by: Martin Jansa
---
recipes-mac/smack/tcp-smack-test/tcp_client.c | 1 +
recipes-mac/smack/udp-smack-test/udp_client.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/recipes-mac/smack/tcp-smack-test/tcp_client.c
b/recipes-mac/smack/tcp-smack-test/tcp_client.c
index 6c0a474..b82b575
Yes, it's also described in:
https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890
echo 0 > /proc/sys/kernel/apparmor_restrict_unprivileged_userns
is bigger hammer, but works as well.
On Sun, May 19, 2024 at 10:34 PM Etienne Cordonnier via
lists.yoctoproject.org
You're most likely missing this fix:
https://git.openembedded.org/openembedded-core/commit/?id=914128f6bd988cde278e087fb9457a0c70c7e5ec
On Fri, May 17, 2024 at 12:47 PM Zoran via lists.yoctoproject.org
wrote:
>
> Hello People,
>
> Thank you very much for helping me with uninative.
>
> This
You probably inherit rm_work somewhere, use bitbake-getvar to find out
where and remove it if you don't want the files to be removed after
the build is finished.
On Thu, May 16, 2024 at 9:28 PM SIMON BABY via lists.yoctoproject.org
wrote:
>
> Hello,
>
> I am building some applications in
Can you show the recipe?
Is the AnalogDevice.h file originally under ${S} variable (which is
excluded with PSEUDO_IGNORE_PATHS by default)?
I think it's not based on
"tmp/work/core2-64-poky-linux/libht2/0.90-r0/AnalogDevice.h" path, so
move it under ${S} like e.g. in:
Try to read log.do_package to see why shlibs code in do_package didn't
automatically add correct runtime dependency.
My guess is that you're incorrectly linking with libsqlite3.so instead
of libsqlite3.so.. Possibly some hardcoded junk in the
component itself.
On Tue, May 14, 2024 at 11:21 AM
PRserv isn't only for incrementing EXTENDPRAUTO, but it should also
increment the LOCALCOUNT (the "0" in "+git0") whenever git sha is
changed to new value not yet recorded in PRserv db.
If this doesn't work, then something isn't configured correctly or
there is a bug.
Cheers,
On Wed, Feb 28,
On Sun, Jan 28, 2024 at 7:59 PM Alexander Kanavin
wrote:
> That said, if the difference between distros is only in specific
> recipe settings, then I think the builds will reuse each other's
> sstate, other than the recipes that differ, and their consumers.
>
Except for example when e.g. icecc
> Backport: new->old override syntax
FWIW: dunfell is forward compatible with new syntax, so this shouldn't be
needed (other than the consistency with other metadata).
On Tue, Jan 2, 2024 at 7:07 PM Yoann Congal wrote:
> Some recipes depend on DISTRO_FEATURES, commercial licensing or compiler
> Am I doing the backport correctly? Maybe config file problems?
You've backported different commit than what Khem asked you to try.
On Fri, Dec 15, 2023 at 10:33 PM Renato Mendes
wrote:
> So Khem, that's what I've done:
>
> *Load from git and backport:*
>
> git clone -b kirkstone
I was experimenting quite a bit with this in:
https://github.com/shr-project/test-oe-build-time/commits/results e.g.:
https://github.com/shr-project/test-oe-build-time/commit/d5111f4472ac397c0f1197eb6366ac7d2e56453f
You need more ram or at least swap to build nodejs, or restrict
PARALLEL_MAKE for nodejs not to trigger OOMK.
On Tue, Nov 14, 2023 at 11:20 AM wrote:
> Hi iam trying to build pionix ti AM62x https://github.com/PionixPublic
> EVSE SDK
> Bitbake builds till 99 percent and last module nodejs runs
I would guess that libdir in your build is set to /usr/lib
while omx-user-module created /usr/lib64.
Check with bitbake-getvar and the files in ${D}, possibly need to pass
libdir value to whatever build system omx-user-module uses (hard to guess
without seeing the whole recipe or sources).
On
I think RUNTIMETARGET is already set correctly when fortran is correctly
enabled as in:
https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/gcc/gcc-runtime.inc#n45
since 2016:
On Wed, Oct 25, 2023 at 11:54 AM Ross Burton wrote:
> On 25 Oct 2023, at 05:17, dspei via lists.yoctoproject.org ambarella@lists.yoctoproject.org> wrote:
> >
> > Hi, community
> >
> > Thanks for your contribution to this great project.
> >
> > The FFmpeg 6.0 was released on 2023-02-27. It
From: Armin Kuster
Signed-off-by: Armin Kuster
---
recipes-mac/smack/smack-test/notroot.py | 12 ++--
.../smack/smack-test/smack_test_file_access.sh | 10 +-
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git
From: Armin Kuster
Signed-off-by: Armin Kuster
---
recipes-mac/smack/smack-test_1.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-mac/smack/smack-test_1.0.bb
b/recipes-mac/smack/smack-test_1.0.bb
index d7824ae..3ab57c6 100644
---
On Thu, Sep 14, 2023 at 2:47 PM Dave Hitchman
wrote:
> Well using that enormous number worked... for the moment, until when it
> next stops. I still would like to know what the devil is being done in my
> system with that one build that is consuming such a crazy number of
> watches, what is
t; that it would need that many things being watched? What is it even watching
> for?
>
It's watching for changes in metadata, which is a lot of files.
------
> *From:* Martin Jansa
> *Sent:* 14 September 2023 14:17
> *To:* Dave Hitchman
> *Cc:* yocto@
On Thu, Sep 14, 2023 at 2:07 PM Dave Hitchman
wrote:
> ERROR: No space left on device or exceeds fs.inotify.max_user_watches?
> ERROR: To check max_user_watches: sysctl -n fs.inotify.max_user_watches.
> ERROR: To modify max_user_watches: sysctl -n -w
> fs.inotify.max_user_watches=.
>
>
* oe-core switched to nanbield in:
https://git.openembedded.org/openembedded-core/commit/?id=f212cb12a0db9c9de5afd3cc89b1331d386e55f6
Signed-off-by: Martin Jansa
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index
* oe-core switched to nanbield in:
https://git.openembedded.org/openembedded-core/commit/?id=f212cb12a0db9c9de5afd3cc89b1331d386e55f6
Signed-off-by: Martin Jansa
---
conf/layer.conf| 2 +-
meta-hardening/conf/layer.conf | 2 +-
meta-integrity/conf/layer.conf | 2 +-
meta
FWIW: I'm mounting my OE drives with barrier=0 and ext4 without journal
(commit=1 cannot be used on ext4 without journal)
BTW: During last OE Happy Hours Khem mentioned using F2FS on NVMEs, anyone
else already played with it?
Not sure how different the effect is from the suggested sysctl
On Fri, Sep 8, 2023 at 9:20 AM Alexandre Belloni <
alexandre.bell...@bootlin.com> wrote:
> On 08/09/2023 09:06:39+0200, Martin Jansa wrote:
> > On Fri, Sep 8, 2023 at 8:42 AM Yoann Congal
> wrote:
> >
> > > Hi!
> > > Le ven. 8 sept. 2023 à 08:01, MOH
On Fri, Sep 8, 2023 at 8:42 AM Yoann Congal wrote:
> Hi!
> Le ven. 8 sept. 2023 à 08:01, MOHAMMED HASSAN
> a écrit :
>
>> Right, you're not the only one!
>> See
>>
>> https://docs.yoctoproject.org/ref-manual/system-requirements.html#minimum-free-disk-space
>> and
> *Phone: *+86-021-60880608-511
>
> *Email: *m...@ambarella.com
>
>
>
>
>
> *From:* yocto@lists.yoctoproject.org *On
> Behalf Of *Martin Jansa
> *Sent:* Friday, August 11, 2023 1:35 AM
> *To:* Ming Wen
> *Cc:* yocto@lists.yoctoproject.org
> *Subject:*
See
https://patchwork.yoctoproject.org/project/oe-core/patch/20230623093323.4058529-1-martin.ja...@gmail.com/
which is easy to backport work around to fix uninative-3.9 and 4.0.
Until uninative-4.1 with more proper fix (
You need to apply
https://patchwork.yoctoproject.org/project/oe-core/patch/20230623093323.4058529-1-martin.ja...@gmail.com/
in your build or wait for new patchelf and new uninative tarball including
that.
On Wed, Jul 5, 2023 at 9:21 AM wrote:
> Hi,
>
> I am trying re-build yocto for one of the
Signed-off-by: Martin Jansa
---
.../files/0001-dram-Fix-build-with-gcc-11.patch | 1 +
1 file changed, 1 insertion(+)
diff --git
a/recipes-bsp/trusted-firmware-a/files/0001-dram-Fix-build-with-gcc-11.patch
b/recipes-bsp/trusted-firmware-a/files/0001-dram-Fix-build-with-gcc-11
armin
>
>
>
> On 6/22/23 10:35 AM, Martin Jansa wrote:
> > * as reported by openembedded-core/scripts/contrib/patchreview.py -v .
> >
> > Malformed Signed-off-by 'Signed-Off-By:'
> (./recipes-mac/AppArmor/files/crosscompile_perl_bindings.patch)
> > Malforme
I've checked the master-next now and somehow I've missed some of the
Upstream-Status issues earlier, so I've sent 4 more changes based on
master-next.
Cheers,
On Wed, Jun 21, 2023 at 3:49 PM Martin Jansa via lists.yoctoproject.org
wrote:
> On Wed, Jun 21, 2023 at 3:42 PM akuster808 wr
$ git grep disable_perl_h_check.patch
Signed-off-by: Martin Jansa
---
.../0001-To-fix-build-error-of-xrang.patch| 29 -
.../Convert-another-vdprintf-to-dprintf.patch | 26
.../Use-format-s-for-call-to-dprintf.patch| 33 -
.../libtpm/files/fix_signed_issue.patch | 48 ---
.
/upgrade_options_processing.patch
Malformed Upstream-Status 'Malformed Upstream-Status in patch
dynamic-layers/meta-perl/recipes-security/nikto/files/location.patch
Signed-off-by: Martin Jansa
---
.../files/check-setuid-use-more-portable-find-args.patch| 1 +
.../bastille/files
-inserting-host-directories-into-co.patch
Malformed Upstream-Status 'Malformed Upstream-Status in patch
meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss/fixup_hosttools.patch
Signed-off-by: Martin Jansa
---
meta-tpm/recipes-tpm2/ibmswtpm2/files/tune-makefile.patch | 2 +-
.../recipes-tpm2/tpm2-tcti-uefi
/krill/files/panic_workaround.patch
Malformed Upstream-Status 'Malformed Upstream-Status in patch
./recipes-security/opendnssec/files/libdns_conf_fix.patch
Malformed Upstream-Status 'Malformed Upstream-Status in patch
./recipes-security/opendnssec/files/libxml2_conf.patch
Signed-off-by: Martin
On Wed, Jun 21, 2023 at 3:42 PM akuster808 wrote:
> Hello Martin,
>
Hello Armin,
On 6/21/23 6:42 AM, Martin Jansa wrote:
> > There is new patch-status QA check in oe-core:
> >
> https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac
%)meta-integrity
15 (68%)meta-tpm
27 (61%)meta-security
Signed-off-by: Martin Jansa
---
...Do-not-get-generation-using-ioctl-when-evm_portable-.patch | 4
.../0001-create-tpm-key-support-well-known-key-option.patch | 2 ++
.../files/0002-libtpm-support-env
The error message says what you should do:
CONNECTIVITY_CHECK_URIS = "https://www.example.com/;
in local.conf (or any other URL which is accessible in China mainland).
On Wed, Jun 14, 2023 at 7:12 AM wrote:
> Hi,
>
> Since yesterday, we can't access
>
TIVEPATH += "python-native"'
>
> I don't know why my EXTRANATIVEPATH doesn't contain python-native when I
> run
> 'bitbake -e '. And this causes my bitbake can not search
> 'python2'.
>
> Martin Jansa 于2023年5月15日周一 16:40写道：
> >
> > Did you add "inherit pythonn
Did you add "inherit pythonnative" or DEPENDS += "python-native"?
You need just the inherit line.
On Mon, May 15, 2023 at 10:23 AM Jiliang Cai wrote:
> I have a bb file abc_1.0.bb:
> DEPENDS += "python3-native"
> And EXTRANATIVEPATH contains "python3-native" as expected, so command
> 'python3'
> I added the directory common/m4
Did you clone common git repo or just created empty directory?
Most gstreamer recipes were fetching common submodule during do_configure
which doesn't work with new kirkstone which prevents network access from
tasks which shouldn't access it, so you need to add
You can add SKIP_RECIPE[rust-native] in your local.conf and bitbake will
tell you all the other parts you need to avoid (e.g. librsvg, ...)
On Wed, Apr 5, 2023 at 2:49 PM Jesus.JimenezSanchez via
lists.yoctoproject.org wrote:
> Hello,
>
> Thank you for your response.
>
> I guess we'll keep
On Sun, Mar 19, 2023 at 3:50 PM Bo YU wrote:
> Hi,
> On Sat, Mar 18, 2023 at 09:29:34AM +, Alexander Kanavin wrote:
> > When the slow download is happening, can you please check (e.g. from a
> > process listing), which server specifically is being accessed and with
> > which command?
On Mon, Mar 13, 2023 at 6:34 PM Alexander Kanavin
wrote:
> There is not a lot of interest in maintaining style guides, and
> associated tooling. My personal feeling is that they don't really help
> with the truly problematic things in recipes that need a human eye (or
> chatgpt level
use SRCPV in PV as the error says
On Fri, Mar 10, 2023 at 10:11 AM Srinuvasan A
wrote:
> Hi All,
>
>
>
> In my downstream layer, one recipe uses the ${AUTOREV} to
> get the very latest commit always, obviously we want the very latest
> changes always to build the recipes often,
/meta-security/commit/?id=da93339112d0a53f0008a72dcacdb55dc3bf95a8
https://git.yoctoproject.org/meta-security/commit/?h=master-next=04a0e35a79d33aadbec79272072dc105830007b7
Cheers,
On Tue, Jan 3, 2023 at 5:36 PM Martin Jansa via lists.yoctoproject.org
wrote:
> * oe-core switched to micked
Yes, it's expected.
native recipes shouldn't be MACHINE specific, so shouldn't use
MACHINEOVERRIDES, see:
meta/classes-recipe/native.bbclass:MACHINEOVERRIDES = ""
meta/classes-recipe/nativesdk.bbclass:MACHINEOVERRIDES = ""
On Fri, Jan 6, 2023 at 9:09 PM wrote:
> MACHINEOVERRIDES which are
Trevor already won this race (I was second, you're third) :)
https://patchwork.yoctoproject.org/project/yocto/list/?seriesmickledore==
On Tue, Jan 3, 2023 at 7:33 PM Khem Raj wrote:
> oe-core switched to mickedore [1]
>
> [1]
>
* oe-core switched to mickedore in:
https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f
Signed-off-by: Martin Jansa
---
conf/layer.conf | 2 +-
meta-hardening/conf/layer.conf | 2 +-
meta-integrity/conf
* oe-core switched to mickedore in:
https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f
Signed-off-by: Martin Jansa
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index
On Tue, Jan 3, 2023 at 3:29 PM Ferry Toth wrote:
> Op 03-01-2023 om 15:18 schreef Alexander Kanavin:
> > I have to note that even the most expensive 16 Gb RAM module is less
> > than 100 Euro, and can be obtained for half that much. Surely you
> > value your time more than that?
>
> Of course.
Hi,
that is intentional, recipes should fetch sources with bitbake fetcher
(which respects MIRROR/PREMIRROR/DL_DIR etc) in do_fetch and network
shouldn't be used in other tasks (unless explicitly enabled in well
explained exceptions).
bitbake can now restrict network access in various tasks
On Thu, Dec 1, 2022 at 12:09 PM Ross Burton wrote:
> On 1 Dec 2022, at 04:27, Zoran via lists.yoctoproject.org
> wrote:
> > I do not understand why we need to explicitly name releases for such
> > simple generic layers?!
>
> The compatibility is because over time things change: override syntax
On Thu, Dec 1, 2022 at 12:05 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Wed, 2022-11-30 at 06:55 -0800, Sven via lists.yoctoproject.org
> wrote:
> > I have intermittent problems with a recipe that creates a user that
> > is member of groups that are created by a different
Agreed with Rudolf.
If the layer maintainer didn't bother to do at least do one build with new
release and adjust LAYERSERIES_COMPAT, then I don't consider that layer
well maintained (it could be someone else who uses the layer, tests it with
new release and sends PR to adjust
You can also chown the files after unpacking them (like in
https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442
)
On Sun, Oct 16, 2022 at 9:13 PM wrote:
> Hi,
> I am working on a project that uses some proprietary layers from a 3rd
> party. These
* the next release 4.2 will be named mickledore
Signed-off-by: Martin Jansa
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index a2661f9..9197c3b 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -14,7 +14,7
On Thu, Sep 22, 2022 at 6:51 PM Benjamin Esquivel <
benjamin.esqui...@gmail.com> wrote:
>
>
> On Sep 21, 2022, at 11:07 PM, Nicolas Dechesne <
> nicolas.deche...@linaro.org> wrote:
>
>
>
> On Thu, Sep 22, 2022 at 5:20 AM Benjamin Esquivel <
> benjamin.esqui...@gmail.com> wrote:
>
>> TL;DR Google
> PARALLEL_MAKE = "-j ${@int(oe.utils.cpu_count() / 4)}"
This won't be optimal in cases where you're rebuilding just one recipe in
incremental build which will be finished much faster if you can unleash
whole potential of dual-epycs. Try to add -l to limit overall load instead
and limit -j only
Cheers,
On Wed, Aug 10, 2022 at 4:16 PM Philippe Midol-Monnet <
philippe.midol-mon...@easymile.com> wrote:
> Hello
>
> Thanks for your answer.
>
> Reading your code, I wonder why you need to do a fetch, it looks very
> resource consuming.
>
> Philippe
>
> On Tu
In webOS we use do_unpack postinst which checks that the SRCREV matches
with the expected tag name and that the tag is annotated, see
https://github.com/webosose/meta-webosose/blob/master/meta-webos/classes/webos_enhanced_submissions.bbclass#L117
Then for our own components (mostly using CMake)
You can use VIRTUAL-RUNTIME_sed variable instead of 'sed' _everywhere_ and
then change the preferred runtime provider in your DISTRO config.
Similar case for "stat" from busybox in webOS OSE:
https://github.com/webosose/meta-webosose/search?q=VIRTUAL-RUNTIME_stat
and much worse case (because too
On Sun, Jul 31, 2022 at 11:56:24PM -0700, Gangadhar N wrote:
> Hi All,
> I made below change in recipes-core/os-release/os-release.bbappend. It
> results in build failure. Please give me pointers to resolve the issue.
> I deleted build/cache and build/sstate-cache. But it didn't resolve the
s as well and it's simple one line patch
(just adding skip_series_check=1 in pop.in), but might be difficult
to upstream, because it's this strange OE specific behavior that we
remove 'patches' directory and then still need quilt pop to work.
Signed-off-by: Martin Jansa
---
meta/lib/oe/patch
On Wed, Mar 30, 2022 at 11:29 PM Trevor Woerner wrote:
> On Wed 2022-03-30 @ 04:08:31 PM, Richard Purdie wrote:
> > On Wed, 2022-03-30 at 09:40 -0400, Trevor Woerner wrote:
> > > Hi Matthias,
> > >
> > > On Wed 2022-03-30 @ 06:32:00 AM, Matthias Klein wrote:
> > > > Yes, you are right, it is
From: Trevor Woerner
Started seeing the following error in my builds:
ERROR: A native program mkfs.ext4 required to build the image was not
found
Please make sure wic-tools have e2fsprogs-native in its DEPENDS
Signed-off-by: Trevor Woerner
---
FWIW: the same is happening now with ubuntu-22.04 where libstdc++6 package
is now built from gcc-12 sources (even when gcc itself still defaults to
gcc-11).
I was trying to add the check in uninative.bbclass, but haven't found easy
portable way to detect the version from libstdc++.so.6 (other
On Wed, Mar 16, 2022 at 8:02 AM Manuel Wagesreither
wrote:
> Poky dunfell contains [1] as 83b827e3d6835ef62cb2db3fc7505679ae727529 and
> [2] as a28d37580a1ae34d6c170490be420c7812d2b3e6 but not [3]. [3] patches
> glibc 2.34, while poky dunfell contains 2.31.
>
It's not about glibc version used
Hi,
can you please create honister branch.
I think 17703ee37b46d15ec369588fbb86dde336df6028 commit (just before this
kirkstone change was applied) would be reasonable branching point.
Now there isn't any branch compatible with Honister release.
Thanks
On Tue, Feb 22, 2022 at 3:16 PM Trevor
I see you have already sent similar patches earlier yesterday, please
ignore this one, but also please merge yours soon as meta-security already
claims kirkstone compatibility, but doesn't parse with kirkstone.
On Tue, Feb 22, 2022 at 12:52 PM Martin Jansa via lists.yoctoproject.org
wrote
* openembedded-core/scripts/contrib/convert-variable-renames.py .
...
All files processed with version 0.1
---
recipes-ids/tripwire/tripwire_2.4.3.7.bb | 2 +-
recipes-mac/smack/smack_1.3.1.bb | 6 +++---
recipes-security/libest/libest_3.2.0.bb | 2 +-
The exception for github.com was implemented in bitbake fetcher and
backported to various versions, e.g. 1.46 used with dunfell with:
https://github.com/openembedded/bitbake/commit/c222eddcebe892ae209aea7776cfc1147ac1df6e
For master branches it's better to change every single recipe which needs
Upgrade bitbake to support new overrides syntax, see
https://github.com/ros/meta-ros/pull/902
On Tue, Dec 28, 2021 at 7:12 PM Kevin Kettinger
wrote:
> Hello,
>
> after including the meta-qt5 and meta-boot2qt layer from
> https://code.qt.io/cgit/yocto, and adding them to my bblayers.conf,
>
https://github.com/agherzan/meta-raspberrypi/pull/946
On Thu, Nov 18, 2021 at 9:01 PM Devendra Tewari
wrote:
> Branch master has been renamed to buster. Also setting protocol to
> https as GitHub is migrating away from unencrypted git protocol
>
> Signed-off-by: Devendra Tewari
> ---
>
see https://github.com/agherzan/meta-raspberrypi/pull/935
On Sun, Nov 7, 2021 at 9:14 PM Tim Orling wrote:
> GitHub has already started "brownouts" for git protocol,
> which will cause random fetcher failures in builds.
>
> Signed-off-by: Tim Orling
> ---
>
Most likely expired Let's Encrypt certificate (which salsa.debian.org where
ca-certificates are hoster is using) on your builder (host OS), see e.g.
for ubuntu:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1928989
So to fix this update ca-certificates on your host distribution and then
Please merge this one.
On Wed, Aug 4, 2021 at 1:20 PM Martin Jansa via lists.yoctoproject.org
wrote:
> Acked-by: Martin Jansa
>
> On Mon, Aug 2, 2021 at 11:02 AM George Liu wrote:
>
>> Fix the variable spelling errors
>> s/SKIP_META_SECUIRTY_SANITY_CHECK/SKIP_ME
Update bitbake to support new overrides syntax.
On Thu, Aug 26, 2021 at 3:28 PM wrote:
> I got this error while trying to build the image after checking out the
> timo/python3-pyinstaller.
> ERROR: ParseError at
> /home/yasmine/yocto/poky/meta-openembedded/meta-oe/conf/layer.conf:106:
>
Hi, read
https://lists.openembedded.org/g/openembedded-architecture/message/1260
https://lists.openembedded.org/g/openembedded-architecture/message/1279
https://lists.openembedded.org/g/openembedded-architecture/message/1291
On Tue, Aug 24, 2021 at 12:33 AM JH wrote:
> Hi,
>
> I updated the
Acked-by: Martin Jansa
On Mon, Aug 2, 2021 at 11:02 AM George Liu wrote:
> Fix the variable spelling errors
> s/SKIP_META_SECUIRTY_SANITY_CHECK/SKIP_META_SECURITY_SANITY_CHECK
>
> Signed-off-by: George Liu
> ---
> classes/sanity-meta-security.bbclass | 2 +-
> 1 file
"_rk3399" also needs to be replaced.
On Tue, Aug 3, 2021 at 7:02 PM Khem Raj wrote:
> Signed-off-by: Khem Raj
> ---
> classes/rockchip-gpt-img.bbclass | 2 +-
> conf/machine/include/rockchip-wic.inc | 2 +-
>
I don't use meta-rockchip, but new syntax doesn't require honister, recent
revisions of 1.50 bitbake are forward compatible with the new syntax.
On Tue, Aug 3, 2021 at 7:02 PM Khem Raj wrote:
> New override syntax requires it
>
> Signed-off-by: Khem Raj
> ---
> conf/layer.conf | 2 +-
> 1
On Fri, Jul 30, 2021 at 3:51 PM akuster808 wrote:
>
>
> On 7/30/21 2:25 AM, Martin Jansa wrote:
> > This is the result of automated script (0.9.0) conversion:
> >
> > oe-core/scripts/contrib/convert-overrides.py .
> >
> > converting the metadata to us
This is the result of automated script (0.9.0) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa
---
README| 2 +-
This marks the layers as compatible with honister now they use the new override
syntax.
Signed-off-by: Martin Jansa
---
conf/layer.conf | 2 +-
meta-hardening/conf/layer.conf | 2 +-
meta-integrity/conf/layer.conf | 2 +-
meta-parsec/conf/layer.conf
1.40 is already in oe-core master you should be able to backport the recipe
from there.
libnml dependency was already added with wireguard PACKAGECONFIG in 1.38
here:
https://git.openembedded.org/openembedded-core/commit/?id=ce2948af5293258a69a9cfefba9e883cefecac87
On Mon, Jul 5, 2021 at 6:55 AM
On Fri, May 14, 2021 at 07:58:02AM -0700, Oliver Westermann wrote:
> Hey,
>
> maybe somebody already has something for this before I reinvent the wheel ;-)
> We've several internal tools that mostly have their own CI and are referenced
> in our yocto layers to be picked up by the nightly build.
On Wed, May 12, 2021 at 05:51:24AM -0700, Chuck Wolber wrote:
> I got a fetcher failure on go-systemd today, which puzzled me. That
> recipe has not changed in ages, and the SRCPV hash is clearly visible
> in the repository.
>
> After looking at it closer, it seems that
On Mon, May 10, 2021 at 12:08:22PM +0300, Thomas Hill via
lists.yoctoproject.org wrote:
> Hi Richard!
>
> On Fri, 7 May 2021, 15:28, Richard Purdie
> > On Fri, 2021-05-07 at 10:10 +0300, Thomas Hill via lists.yoctoproject.org
> > wrote:
> > > On Thu, 6 May 2
On Thu, May 6, 2021 at 10:57 AM Thomas Hill via lists.yoctoproject.org
wrote:
> Hi Martin!
>
> On Mon, Nov 16, 2020 at 02:28 PM, Martin Jansa wrote:
>
>
> https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442
>
> is an e
On Thu, Apr 29, 2021 at 06:05:30PM -0400, Randy MacLeod wrote:
> > > > Most yocto layers have not adopted the tagging perhaps because they
> > > > weren't aware of it so that's why I'm writing this email. Tagging
> > > > will make it easy to find the first commit for a specific release
> > > >
And the variable should be named PREFERRED_VERSION_recipe1 (it's not using
pn as an override).
On Mon, Feb 8, 2021 at 12:10 PM Josef Holzmayr
wrote:
> Howdy!
>
> Am Mo., 8. Feb. 2021 um 11:52 Uhr schrieb Mauro Ziliani <
> ma...@faresoftware.it>:
> > In the image recipe I put
> >
> >
On Thu, Oct 22, 2020 at 11:37 PM Martin Jansa via lists.yoctoproject.org
wrote:
> There were only a few changes needed between dunfell and gatesgarth to
> keep it building and I feel guilty for sending half of them - and pinging
> you on FB :).
>
> I don't have interest in py
Yes, there are significant diffferences in gcc, see:
https://gcc.gnu.org/gcc-5/porting_to.html
https://gcc.gnu.org/gcc-6/porting_to.html
https://gcc.gnu.org/gcc-7/porting_to.html
The recipes in public layers were already fixed at that time, but if you
have a lot of your own C/C++ code in your
You're probably mixing incompatible branches of different layers - always
use the same branch in all layers.
at_least was added in oe-core/dunfell with:
https://git.openembedded.org/openembedded-core/commit/?id=c6dda204e15c5b27559f7617b18a7b3ce604e2f8
On Fri, Dec 11, 2020 at 4:14 PM sateesh m
See QT_DIR_NAME variable in meta-qt5
and b716195f609de6547cfdfadfd4fd25292a6bbf09 commit which changed the
default value.
On Wed, Dec 2, 2020 at 5:03 AM sateesh m wrote:
> Hi Guys,
>
> I am trying to build qt support image to my yocto .I am
> using meta-qt5 master sources,after
https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442
is an example where it triggers this error, but doesn't trigger the more
common host-user-contaminated QA error (unless you happened to use UID 1001
on host for the user running bitbake).
Similarly
If you don't really need 3.8 and 3.7.5 from warrior would be good enough
for you, then backporting it to thud was relatively straightforward as
implemented in:
https://github.com/ros/meta-ros/commits/thud/meta-ros-backports-warrior
and as it's in a separate layer it doesn't make your main distro
1 - 100 of 128 matches
Mail list logo
