The do_bundle_initramfs() only processes kernel image
types that are found in KERNEL_IMAGETYPE_FOR_MAKE whereas
the build system can generate other types that are not
directly supported by the kernel build system. In which
case when we come to the deploy phase not all the images
mentioned in
From: Mingli Yu
After qemu upgrades to 5.2.0 in commit [1], if also switches
to meson and the previous logic which introduces the testsuites
changes in [2] and results in below error when run ptest test:
# ./run-ptest
for f in ; do \
nf=$(echo $f | sed 's/tests\//\.\//g'); \
$nf; \
Hello Yann,
On Thu, Feb 4, 2021 at 1:11 AM Yann Dirson wrote:
>
>
>
> Le mer. 3 févr. 2021 à 21:56, Andrey Zhizhikin a écrit :
>>
>> Hello Yann,
>>
>> > index 5fa99821c4..872592fdae 100644
>> > --- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.12.bb
>> > +++
If image recipe depends on another image recipe it will try to use
license recipeinfo that is not deployed. It will result in:
| Exception: FileNotFoundError: [Errno 2] No such file or directory:
| 'TMPDIR/deploy/licenses/foo-image/recipeinfo'
We can't determine in a simple and efficient way if
The following changes since commit 1988d07b65ad38bdf8fac8615f11fb6536a75806:
wic: Optimise fstab modification for ext2/3/4 and msdos partitions
(2021-01-28 04:41:47 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
Hi,
I submitted something similar awhile back to this mailing list.
https://lists.openembedded.org/g/openembedded-core/message/146607?p=,,,20,0,0,0::relevance,,Michael.Ho%40bmw.de,20,2,0,79619287
If yours makes more sense (I didn't think there's ever a case where an image
recipe actually has a
>I guess I mean should my change (not dep[0] == pn) be removed and yours
>take its place as yours should cover that case.
Hi Michael,
I would say we should keep both. Your change would be enough for most cases
and most developers wouldn't even need to care about that problem. I think
image
>I didn't see anything on the docs mailing list, but we should also
>have a matching update to the docs for the new variable (unless it is
>already in the docs, I didn't check for that).
Thanks, please check now:
https://lists.yoctoproject.org/g/docs/message/860
Best regards,
Tomasz
(Sorry, didn't read your patch correctly, it already included my change).
I guess I mean should my change (not dep[0] == pn) be removed and yours
take its place as yours should cover that case.
Kind regards,
Michael Ho
--
BMW Car IT GmbH
Michael Ho
Spezialist Entwicklung – Build and Release
On Thu, Feb 4, 2021 at 7:10 AM Tomasz Dziendzielski
wrote:
>
> If image recipe depends on another image recipe it will try to use
> license recipeinfo that is not deployed. It will result in:
> | Exception: FileNotFoundError: [Errno 2] No such file or directory:
> |
On 2021-02-04 4:38 p.m., Joshua Watt wrote:
Bash 5.1 enabled bracketed input mode by default, but this causes a lot
of problems with automated testing as it can inject a lot of control
sequences into non-interactive output. Disable it to cleanup the output
an preserve the pre-5.1 behavior
0001-fix-up-check-for-hardlinks-always-false-if-inode-0xF.patch
removed since it is included in 1.45.7
Signed-off-by: Wang Mingyu
---
...-hardlinks-always-false-if-inode-0xF.patch | 55 ---
...2fsprogs_1.45.6.bb => e2fsprogs_1.45.7.bb} | 3 +-
2 files changed, 1 insertion(+),
0001-Move-python-helper-scripts-used-only-in-tests-to-Pyt.patch
0001-libparted-fs-add-sourcedir-lib-to-include-paths.patch
0002-tests-use-skip_-rather-than-skip_test_-which-is-unde.patch
removed since they are included in 3.4
Signed-off-by: Wang Mingyu
---
References
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3177
Signed-off-by: Wang Mingyu
---
.../python/python3/CVE-2021-3177.patch| 179 ++
meta/recipes-devtools/python/python3_3.9.1.bb | 1 +
2 files changed, 180 insertions(+)
create mode 100644
Our nologin path is /sbin/nologin instead of /bin/nologin.
Signed-off-by: Chen Qi
---
meta/recipes-core/systemd/systemd_247.2.bb | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/meta/recipes-core/systemd/systemd_247.2.bb
Fix the do_compile error:
| ../../../mc-4.8.26/lib/tty/tty-ncurses.c: In function 'tty_colorize_area':
| ../../../mc-4.8.26/lib/tty/tty-ncurses.c:557:5: error: unknown type name
'cchar_t'; did you mean 'wchar_t'?
add -DNCURSES_WIDECHAR=1 when musl.
Signed-off-by: Zheng Ruoqin
---
Further to 50ff9afb39, only detect code changes in submodules that are
subdirectories of the EXTERNALSRC directory.
Signed-off-by: Douglas Royds
---
meta/classes/externalsrc.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/externalsrc.bbclass
On Wed, 2021-02-03 at 10:55 +0100, Zoltan Boszormenyi via
lists.openembedded.org wrote:
> 2021. 01. 14. 16:40 keltezéssel, Kamel Bouhara írta:
> > On Thu, Jan 14, 2021 at 03:25:50PM +0100, Jean-Marie Lemetayer
> > wrote:
> > > Hi Kamel,
> > >
> >
> > Hi Jean-Marie,
> >
> > > Thanks for your
Please merge these changes in gatesgarth.
Thanks,
Anuj
The following changes since commit 4e8022635fc8543d135fed3091a9f555899d1b3c:
linuxloader: Avoid confusing string concat errors (2021-01-27 09:32:36 +)
are available in the Git repository at:
Bash 5.1 enabled bracketed input mode by default, but this causes a lot
of problems with automated testing as it can inject a lot of control
sequences into non-interactive output. Disable it to cleanup the output
an preserve the pre-5.1 behavior
Signed-off-by: Joshua Watt
---
Remove patches for CVE-2019-25013 and CVE-2020-27618 since they are
present in the branch now. Add both CVEs to CVE_CHECK_WHITELIST.
760e1d28782 gconv: Fix assertion failure in ISO-2022-JP-3 module (bug 27256)
d3cb8f6222a aarch64: fix static PIE start code for BTI [BZ #27068]
082798622d8
Looks ok although you should be deleting the unused patch files too
On Thu, Feb 4, 2021 at 12:35 PM Steve Sakoman wrote:
> Remove patches for CVE-2019-25013 and CVE-2020-27618 since they are
> present in the branch now. Add both CVEs to CVE_CHECK_WHITELIST.
>
> 760e1d28782 gconv: Fix assertion
I've been doing quite some tests and things last week, my conclusion so
far is that the latest gcc seems to trigger a bug particular to this
CPU. Maybe even this particular batch.
Hours of testing found no issues with RAM.
I've also done huge amounts of builds with zeus, no problems.
Then
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 27 januari 2021 18:28
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 6/7] native: Stop clearing PACKAGES
>
> Native
Remove patches for CVE-2019-25013 and CVE-2020-27618 since they are
present in the branch now. Add both CVEs to CVE_CHECK_WHITELIST.
760e1d28782 gconv: Fix assertion failure in ISO-2022-JP-3 module (bug 27256)
d3cb8f6222a aarch64: fix static PIE start code for BTI [BZ #27068]
082798622d8
On Thu, 2021-02-04 at 19:43 +, Peter Kjellerstedt wrote:
>
>
> > diff --git a/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb
> > b/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb
> > index 16708fd581d..226e1c7b89f 100644
> > --- a/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.40.0.bb
> >
26 matches
Mail list logo
