ping again
On Fri, Sep 6, 2019 at 1:32 PM Martin Jansa wrote:
> On Mon, Aug 12, 2019 at 07:51:40PM +0000, Martin Jansa wrote:
> > Signed-off-by: Martin Jansa
>
> ping
>
> > ---
> > documentation/ref-manual/ref-classes.xml | 5 -
> > documentati
On Tue, Feb 25, 2020 at 02:10:15PM -0500, Joel A Cohen wrote:
> Hmm, that is a very good suggestion that I hadn't thought of. I guess the
> only disadvantage is that PV doesn't get changed so you end up having to
> keep track of which "recipe_1.0.0.rpm" is the test one and which is the
> good
There is nodejs upgrade to 12.x on oe-devel ML:
http://lists.openembedded.org/pipermail/openembedded-devel/2020-January/204363.html
so we won't be staying on 10.x, but if 12.x isn't enough to build without
meta-python2, then we might need 13.x :/.
On Tue, Jan 21, 2020 at 6:09 PM Konrad Weihmann
> DEPENDS_class-target += "systemd"
You surely meant
DEPENDS_append_class-target = " systemd"
here
On Wed, Feb 19, 2020 at 10:48 PM Mikko Rapeli wrote:
> Hi,
>
> On Wed, Feb 19, 2020 at 01:37:19AM -0800, Armando Hernandez wrote:
> > Hello,
> >
> > I have a recipe that builds a library. The
ll not do `git ls-remote` for the tags more than once. So as
> long as you have built once you can then build again without network.
> (Setting BB_SRCREV_POLICY = "cache" currently breaks ${AUTOREV}, but I sent
> patches for that the other day.)
>
>
>
> //Pe
Both recipes should be updated to use SRCREV like any other recipe, I'll
send patch for that.
The documentation should also mention that using tag names in SRCREV (or
tag parameter) is not recommended, because tags can be moved and bitbake
will always use "git ls-remote" to map the tag name to
or not.. both were already fixed
http://git.openembedded.org/meta-openembedded/commit/?id=2f6c043c0c99ccf71f9eb9088adbe42972b9d8a0
http://git.openembedded.org/meta-openembedded/commit/?id=f61d9b3fd32dede5f2ab2aabbf0a8fb9fa75dd98
On Sat, Feb 15, 2020 at 6:38 PM Martin Jansa wrote:
> Both reci
On Thu, Feb 20, 2020 at 08:14:04AM +, mikko.rap...@bmw.de wrote:
> On Wed, Feb 19, 2020 at 10:57:41PM +0100, Martin Jansa wrote:
> > > DEPENDS_class-target += "systemd"
> >
> > You surely meant
> > DEPENDS_append_class-target = " systemd"
On Thu, Feb 20, 2020 at 11:26:54AM +, Paul Barker wrote:
> In my new CI setup I'm using an sstate mirror which seems to have some
> occasional download issues. This results in the setscene task failing.
> For example:
>
> ERROR: qt3d-5.13.2+gitAUTOINC+93361f1a59-r0
>
> On 30/10/2019 06:25, star at gmx.li wrote:
> > Build of image failed, I got strange and long error messages like:
> >
> > | from distutils.sysconfig import parse_makefile
> > | ModuleNotFoundError: No module named 'distutils.sysconfig'
> > | configure: error: Python failed to run; see above
Signed-off-by: Martin Jansa
---
conf/layer.conf | 2 +-
meta-integrity/conf/layer.conf | 2 +-
meta-security-compliance/conf/layer.conf | 2 +-
meta-security-isafw/conf/layer.conf | 2 +-
meta-tpm/conf/layer.conf | 2 +-
5 files changed, 5
Is Thud EOL now?
Or did someone volunteer off-list and now it waits for Maintainer selection
process to be defined?
https://wiki.yoctoproject.org/wiki/Releases still says Community support.
Thanks
On Tue, Mar 17, 2020 at 10:13 PM akuster wrote:
>
>
> On 3/13/20 11:03 AM, akuster via
<
oliver.westerm...@cognex.com> wrote:
> On Wed, Mar 18, 2020 at 08:38 AM, Martin Jansa wrote:
>
>
> If you want to compare how terrible your current VM compares with some
> other builders, you can use:
> https://github.com/shr-project/test-oe-build-time
>
> Thanks
For uninative you can just use latest dunfell with
https://git.openembedded.org/openembedded-core/commit/?h=dunfell=0f01fb2286335dd0da0c7be3f56c36a0fced3e42
For dpkg you can just try latest, but I'm not seeing it failing with
glibc-2.32 in ubuntu-20.04, something else might be wrong/different in
I was able to reproduce this in one of my build setups and confirm that
backporting this commit helps (and haven't found any other issues while
building our images).
I've sent the backport request now.
On Mon, Sep 28, 2020 at 1:46 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
>
There is no limitation like that, but it's quite easy to break that, you
mentioned some ugly BSP before, I wouldn't be surprised if it's broken
there.
What worked well for me over the years is using this script:
openembedded-core/scripts/sstate-diff-machines.sh
on jenkins which produces the
You can add a layer which will set LAYERSERIES_COMPAT for another layer,
but it needs to be parsed before the layer you want to change, e.g.:
https://github.com/webosose/meta-webosose/blob/thud/meta-qt5-compat/conf/layer.conf
it's useful to use this layer also to implement whatever modifications
I don't use WR, but setting it to empty works fine for me.
Why do you think it shouldn't work? See
https://git.openembedded.org/openembedded-core/tree/meta/classes/blacklist.bbclass#n18
On Mon, May 25, 2020 at 6:38 PM Robert P. J. Day
wrote:
>
> asking what is almost certainly a silly
. J. Day
wrote:
> On Mon, 25 May 2020, Martin Jansa wrote:
>
> > I don't use WR, but setting it to empty works fine for me.
>
> *where* did you set it to empty? in your local.conf?
>
> > Why do you think it shouldn't work? See
> >
> https://git.openembedded.org
Yes, it's worth. Thanks
On Mon, May 25, 2020 at 7:40 PM Robert P. J. Day
wrote:
> On Mon, 25 May 2020, Robert P. J. Day wrote:
>
> > On Mon, 25 May 2020, Martin Jansa wrote:
> >
> > > Yes, in local.conf or distro config, both work fine. Maybe your
> > > PNBL
Are you trying to use it with openssl-1.0.*? Either use openssl-1.1 or
revert the changes from https://github.com/apenwarr/wvstreams/pull/2/commits
.
On Mon, Sep 21, 2020 at 10:55 AM Zoltan Kerenyi Nagy <
kerenyi.nagy.zol...@gmail.com> wrote:
> Hi,
>
> I was messing around with wvdial & wvstream
/opt/yocto_downloads or /opt/downloads?
On Mon, Jul 20, 2020 at 8:15 PM Amrun Nisha.R wrote:
> I have updated the DL_DIR to the current build directory's downloads
> folder using sed command.
>
> sed -i 's/DL_DIR ?= "${BSPDIR}\/downloads/DL_DIR = "\/opt\/yocto_downloads/g'
> conf/local.conf
>
Michael Nazzareno Trimarchi <
mich...@amarulasolutions.com> wrote:
> Hi Martin
>
> On Wed, Jul 8, 2020 at 8:36 AM Martin Jansa
> wrote:
> >
> > Hi,
> >
> > it's know issue already fixed in master, see
> > https://lists.openembedded.org/g/openembed
Hi,
it's know issue already fixed in master, see
https://lists.openembedded.org/g/openembedded-architecture/message/1108
thud is pretty much out of support and probably won't be fixed there, you
should be able to easily fix it from .bbappend in one of your layers.
Regards,
On Wed, Jul 8, 2020
This 0001-mtd-utils-Fix-return-value-of-ubiformat.patch patch was recently
backported to dunfell in
https://git.openembedded.org/openembedded-core/commit/?h=dunfell=3ee98b6c9ddd1dd0825245ca672236b7befb9859
check with "bitbake -e mtd-utils" to see which other layer in your build
adds the same
Add "common" git repo to SRC_URI and set SRCREV + SRCREV_FORMAT for it,
instead of using git submodules to fetch it.
On Thu, Jul 23, 2020 at 2:40 PM wrote:
> Hi,
>
> I have a problem. I am trying to set up development environment that runs
> offline. For this purpose i set up a repository
Are you sure this is the whole SRC_URI and that there aren't some other
parts added through some .bbappend?
Always use "bitbake -e" to see whatever bitbake sees when building the
recipe to make sure.
"common" is git repository gstreamer components use in 1.12 it is git
submodule as you can see:
You can backport
https://git.openembedded.org/openembedded-core/commit/?h=dunfell=2cca75155baec8358939e2aae822e256bed4cfe0
On Tue, Jul 21, 2020 at 9:07 AM Bernd wrote:
> Hello,
>
> we are using the warrior branch for our embedded Linux project. Since
> Ubuntu 20.04 LTS has been released we
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
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
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
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
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
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 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 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.
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 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
> >
> >
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
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
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:
>
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
"_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
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
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
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
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
> ---
>
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
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
> ---
>
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
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
* 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 +-
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
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
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
* 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
* 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
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=.
>
>
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: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
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
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
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_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
---
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
> *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:*
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
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
---
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
> 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
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
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
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)
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
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
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
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.
* 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
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]
>
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: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
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
/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
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,
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
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
> 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
1 - 100 of 128 matches
Mail list logo
