On 3/15/21 10:31 PM, Steve Sakoman wrote:
On Sun, Mar 14, 2021 at 3:10 PM kai wrote:
On 3/10/21 11:09 AM, kai wrote:
From: Chen Qi
/var/run has been deprecated by systemd, so use /run instead,
as suggested by systemd.
Ping.
This is in the group of patches sent for review on 3/13:
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_M3.rc1.
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC
It appears that inherit of the kernel_do_install routine is called which causes
the linux
image to be installed in /boot. I added a quick and dirty hack to inhibit this
behaviour.
Could someone please comment on a proper solution:
diff --git a/meta/classes/kernel.bbclass
Hello,
There seems to be a problem when a kernel module is added to an initramfs image.
As soon as I add a recipe which installs an external kernel module into an
initramfs image it automatically installs the linux kernel image in a /boot
directory.
This is really bad as it increases the size
On Mon, Mar 15, 2021 at 4:40 PM Scott Branden via
lists.openembedded.org
wrote:
>
> Hello,
>
> There seems to be a problem when a kernel module is added to an initramfs
> image.
>
> As soon as I add a recipe which installs an external kernel module into an
> initramfs image it automatically
The meson determinism issue is the same frozenset issue we encountered with
python itself. Remove the problematic pyc file until upstream work out the
best way to address the issue (as with core python).
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/reproducible.py | 1 -
On Mon, Mar 15, 2021 at 04:49:34PM -0700, Khem Raj wrote:
> On Mon, Mar 15, 2021 at 4:40 PM Scott Branden via
> lists.openembedded.org
> wrote:
> >
> > Hello,
> >
> > There seems to be a problem when a kernel module is added to an initramfs
> > image.
> >
> > As soon as I add a recipe which
On Mon, Mar 15, 2021 at 04:39:56PM -0700, Scott Branden via
lists.openembedded.org wrote:
> Hello,
>
> There seems to be a problem when a kernel module is added to an initramfs
> image.
>
> As soon as I add a recipe which installs an external kernel module into an
> initramfs image it
Hi Mike,
On 15.03.21 14:13, Mike Looijmans wrote:
For software updates, I want to have what would have gone into the boot
partition of the WIC image as a separate file.
If I want to have the contents of the rootfs as an ext4 image, I can
just specify IMAGE_TYPES="ext4" in my image recipe.
The upstream patches are only in glib >= 2.66.6 and >= 2.67.3 and won't
be backported. This patch is developed based on the upstream patch set
and consulting teh backports recently made by Ubuntu for the 2.64.6
series.
Signed-off-by: Anatol Belski
---
.../glib-2.0/glib-2.0/CVE-2021-27219.patch
libtcolors is actually needed, I'll see if
> > I can prepare a patch to skip it, but I don't think it will buy more
> > than 1s, it's just two object files.
> >
> > The good news is that meson support is about to land upstream, which
> > should be significantly faster
For software updates, I want to have what would have gone into the boot
partition of the WIC image as a separate file.
If I want to have the contents of the rootfs as an ext4 image, I can
just specify IMAGE_TYPES="ext4" in my image recipe.
This image I can feed to SWUdate and write to the
Signed-off-by: Adrian Fiergolski
---
meta/recipes-graphics/wayland/weston-init.bb | 1 +
meta/recipes-graphics/wayland/weston-init/init | 1 +
2 files changed, 2 insertions(+)
diff --git a/meta/recipes-graphics/wayland/weston-init.bb
b/meta/recipes-graphics/wayland/weston-init.bb
index
actually needed, I'll see if
> > I can prepare a patch to skip it, but I don't think it will buy more
> > than 1s, it's just two object files.
> >
> > The good news is that meson support is about to land upstream, which
> > should be significantly faster than autoconf
laptop it takes 32s to do
> > > configure + make -j2. Most of that is autoconf - make -j2 takes 8s.
> > >
> > > Only 3 libraries are built with this combination: libcommon.a,
> > > libtcolors.a, and libuuid.a/so. No executables or anything else is
> > > buil
> -Original Message-
> From: Robert Yang
> Sent: den 15 mars 2021 03:32
> To: Peter Kjellerstedt ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a
> warning when login with root is disabled
>
> On 3/12/21 10:13 PM,
From: Dorinda Bassey
Added HOMEPAGE and DESCRIPTION for recipes with missing
descriptions or homepage.
Signed-off-by: Dorinda Bassey
---
meta-selftest/recipes-test/aspell/aspell_0.0.0.1.bb | 1 +
.../recipes-test/git-submodule-test/git-submodule-test.bb| 1 +
2 files
On Mon, 2021-03-15 at 10:49 +, Richard Purdie wrote:
> On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> > On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > > From: Luca Boccassi
> > > >
> > > >
On Tue, Feb 23, 2021 at 02:35:53PM +0100, Martin Jansa via
lists.openembedded.org wrote:
> * not sure if there are some valid use-cases for missing manifest, but
> recently I'm seeing increasing number of build failures where something
> from native recipe is missing (seen it with pseudo,
On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > From: Luca Boccassi
> >
> > Recently util-linux gained an (optional) build dependency on libcryptsetup.
> > But libcryptsetup build-depends on util-linux for blkid
On Mon, 2021-03-15 at 10:44 +, Luca Boccassi wrote:
> On Sun, 2021-03-14 at 22:10 +, Richard Purdie wrote:
> > On Thu, 2021-03-11 at 15:09 +, luca.bocca...@gmail.com wrote:
> > > From: Luca Boccassi
> > >
> > > Recently util-linux gained an (optional) build dependency on
> > >
ke libtcolors is actually needed, I'll see if
> I can prepare a patch to skip it, but I don't think it will buy more
> than 1s, it's just two object files.
>
> The good news is that meson support is about to land upstream, which
> should be significantly faster than autoconf + mak
SysVinit sets by default the $HOME directory to "/" for the init scripts.
It's picked then by the weston-launcher and make weston-terminal to have
wrongly set $HOME environment variable for the root user.
Signed-off-by: Adrian Fiergolski
---
Sorry, the previous patch far wrongly formatted.
This patch is wrongly formatted and should be ignored. I have already
sent a proper one.
Adrian
On 15.03.2021 15:01, Adrian Fiergolski wrote:
> Signed-off-by: Adrian Fiergolski
> ---
> meta/recipes-graphics/wayland/weston-init.bb | 1 +
> meta/recipes-graphics/wayland/weston-init/init | 1 +
Hi Mike,
On 15.03.21 15:46, Mike Looijmans wrote:
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com
Please
Hi Stefano,
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com
Please consider the environment before printing
On Sun, Mar 14, 2021 at 3:10 PM kai wrote:
>
> On 3/10/21 11:09 AM, kai wrote:
>
> From: Chen Qi
>
> /var/run has been deprecated by systemd, so use /run instead,
> as suggested by systemd.
>
> Ping.
This is in the group of patches sent for review on 3/13:
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijm...@topicproducts.com
W: www.topicproducts.com
Please consider the environment before printing this e-mail
On
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *apt* to *2.2.2* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe apt failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cmake* to *3.19.6* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.19.5-3.19.6.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *autoconf-archive* to
*2021.02.19* has Succeeded.
Next steps:
- apply the patch: git am
0001-autoconf-archive-upgrade-2019.01.06-2021.02.19.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *openssh* to *8.5p1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-openssh-upgrade-8.4p1-8.5p1.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bison* to *3.7.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-bison-upgrade-3.7.5-3.7.6.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dnf* to *4.6.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-dnf-upgrade-4.6.0-4.6.1.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*277b4ed1776f721145b2649d888f1deb445fecc5* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.16.2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *e2fsprogs* to *1.46.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-e2fsprogs-upgrade-1.46.1-1.46.2.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *liburi-perl* to *5.08* has
Succeeded.
Next steps:
- apply the patch: git am 0001-liburi-perl-upgrade-1.74-5.08.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.12.05* has
Succeeded.
Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.12.04-0.12.05.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-importlib-metadata*
to *3.7.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-importlib-metadata-upgrade-3.4.0-3.7.3.patch
- check the changes
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mesa* to *21.0.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe mesa failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.8.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hypothesis-upgrade-6.2.0-6.8.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.30.2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-git-upgrade-2.30.1-2.30.2.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-efi* to *3.0.13* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gnu-efi-upgrade-3.0.12-3.0.13.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libdnf* to *0.60.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libdnf -V 0.60.0 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libedit* to *20210216-3.1*
has Succeeded.
Next steps:
- apply the patch: git am
0001-libedit-upgrade-20191231-3.1-20210216-3.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.16.2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-go-upgrade-1.16-1.16.2.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.27* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gtk-3-upgrade-3.24.25-3.24.27.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *zstd* to *1.4.9* has
Succeeded.
Next steps:
- apply the patch: git am 0001-zstd-upgrade-1.4.8-1.4.9.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *asciidoc* to *9.1.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe asciidoc failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *msmtp* to *1.8.15* has
Succeeded.
Next steps:
- apply the patch: git am 0001-msmtp-upgrade-1.8.14-1.8.15.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bind* to *9.16.12* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-bind-upgrade-9.16.11-9.16.12.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *automake* to *1.16.3* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade automake -V 1.16.3
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *less* to *580* has Succeeded.
Next steps:
- apply the patch: git am 0001-less-upgrade-563-580.patch
- check the changes to upstream patches and summarize them in the commit
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to
*9776715b96b14705579c505f586cb2427b272ca6* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade vulkan-samples
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gdk-pixbuf* to *2.42.2* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gdk-pixbuf failed.
NOTE: Starting bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools-scm* to
*5.0.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-scm-upgrade-5.0.1-5.0.2.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libhandy* to *1.2.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libhandy failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *sudo* to *1.9.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-sudo-upgrade-1.9.5p2-1.9.6.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *epiphany* to *3.38.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-epiphany-upgrade-3.38.2-3.38.3.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *acl* to *2.3.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-acl-upgrade-2.2.53-2.3.0.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.2.170.0*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libinput* to *1.17.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libinput-upgrade-1.16.4-1.17.0.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to
*0a7f9cfbb62f9d1b1ef9d22f6d9f212a89aa06f3* has Succeeded.
Next steps:
- apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch
- check the changes
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *strace* to *5.11* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe strace failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to
*54.1.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-upgrade-54.1.1-54.1.2.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *adwaita-icon-theme* to
*3.38.0* has Failed (devtool error).
Detailed error information:
The following devtool command failed: finish -f adwaita-icon-theme
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *pango* to *1.48.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-pango-upgrade-1.48.2-1.48.3.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnutls* to *3.7.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gnutls-upgrade-3.7.0-3.7.1.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lttng-modules* to *2.12.5*
has Succeeded.
Next steps:
- apply the patch: git am 0001-lttng-modules-upgrade-2.12.4-2.12.5.patch
- check the changes to upstream patches and
Recipe upgrade statistics:
* Succeeded: 39
gnu-efi, 3.0.13, Yi Zhao
openssh, 8.5p1, Armin Kuster
autoconf-archive, 2021.02.19, Robert Yang
bison, 3.7.6, Chen Qi
btrfs-tools, 5.11, Wang Mingyu
createrepo-c, 0.17.1, Alexander Kanavin
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *attr* to *2.5.0* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade attr -V 2.5.0
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-loader* to *1.2.170.0*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-headers* to
*1.2.170.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-vulkan-headers-upgrade-1.2.162.0-1.2.170.0.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxkbcommon* to *1.1.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxkbcommon-upgrade-1.0.3-1.1.0.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wpebackend-fdo* to *1.8.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-wpebackend-fdo-upgrade-1.8.0-1.8.1.patch
- check the changes to upstream patches and
Move some definitions from u-boot.inc into uboot-config.bbclass and
similarly from kernel-fitimage.bbclass into uboot-sign.bbclass, so that
they can be useful when signing the U-boot proper fitimage, for a
verified-boot SPL.
Signed-off-by: Klaus Heinrich Kiwi
---
Duplicate the variables governing u-boot signing so that we can have a
different set of keys/parameters signing the SPL.
Signed-off-by: Klaus Heinrich Kiwi
---
meta/classes/uboot-config.bbclass | 2 ++
meta/classes/uboot-sign.bbclass | 55 ---
2 files changed, 46
Add the necessary infrastructure to create a U-boot proper fitimage,
sign it (using the same keys as the kernel-fitimage), and put the public
key in the SPL binary so that verified SPL boot can be accomplished.
Signed-off-by: Klaus Heinrich Kiwi
---
meta/classes/kernel-fitimage.bbclass | 11 +-
Derived from the similar kernel fitImage sign testcase, the U-Boot
fitImage testcases will test both the standalone (only SPL_SIGN_ENABLE
set) as well as cascaded (both UBOOT_SIGN_ENABLE as well as
SPL_SIGN_ENABLE) scenarios.
Signed-off-by: Klaus Heinrich Kiwi
---
This patch series aims at extending U-Boot's verified boot support to
also include SPL.
Presently, setting UBOOT_SIGN_ENABLE instructs the classes uboot-sign
and kernel-fitimage to create and sign a Linux Kernel fitImage. This
proposal introduces the variable SPL_SIGN_ENABLE that aims at (re-)
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
---
.../{libedit_20191231-3.1.bb => libedit_20210216-3.1.bb} | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
rename meta/recipes-devtools/libedit/{libedit_20191231-3.1.bb =>
libedit_20210216-3.1.bb} (82%)
diff --git a/meta/recipes-devtools/libedit/libedit_20191231-3.1.bb
https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#Stable.2FLTS_Patch_Acceptance_Policies
Stable/LTS Patch Acceptance Policies
Potentially Acceptable:
* Bug fix only version upgrades for upstreams with a good stable process
Unacceptable:
* General version upgrades
So, unless there's a
options I've set, on my laptop it takes 32s to do
> > > > configure + make -j2. Most of that is autoconf - make -j2 takes 8s.
> > > >
> > > > Only 3 libraries are built with this combination: libcommon.a,
> > > > libtcolors.a, and libuuid.a
Hi Klaus,
Can we make the patch not only support sign u-boot fitimage with
different key, but also allow sign later?
Similar to kernel-fitimage.bbclass::fitimage_assemble(), step 1~6
create a "sign-able" fit-image and step 7 do the sign.
Can we add a new control variable i.e. DO_UBOOT_SIGN
86 matches
Mail list logo
