From: Andrei Gherzan
Due to a bug in glibc 2.33, the value of the icache line size is now
reported as unsupported option. This breaks qemu at runtime with:
cacheinfo.c:182: init_cache_info: Assertion `(isize & (isize - 1)) == 0'
failed.
Aborted (core dumped)
We haven't caught this one yet becau
From: Andrei Gherzan
`devtool` uses `copy_recipe_files` for the upgrade operation when
creating the new, workspace recipe. Before handling the copy operations,
the function checks the entry in `SRC_URI` against `FILE` while in turn
uses absolute paths. When BBLAYERS contains entries that are not
From: Richard Purdie
Python 3.9 dropped isAlive() so use the preferred is_alive().
(From OE-Core rev: 9bb06428cbb2ac0f3d98a1696f050d3393385503)
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/utils/commands.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oe
From: Andrei Gherzan
Signed-off-by: Andrei Gherzan
---
...h-Fix-pseudo-to-work-with-glibc-2.33.patch | 46 +++
...wrapper-for-fstatat-fstatat64-in-gli.patch | 77 +++
meta/recipes-devtools/pseudo/pseudo_git.bb| 2 +
3 files changed, 125 insertions(+)
create mode 10
From: Andrei Gherzan
It was observerd that with glibc 2.33, sysconf reports unsupported
option (-1) for _SC_LEVEL1_ICACHE_LINESIZE.
This can be reproduced with sysconf tool:
```
└─❯ docker run -ti --rm archlinux:base-20210214.0.15477 getconf -a |
grep "GNU_LIBC_VERSION\|LEVEL1_ICACHE_LINESIZE"
On Fri, Feb 19, 2021 at 1:16 PM Khem Raj wrote:
>
> After discussing with Martin offline and also his test reports
> indicate that we are not getting worse with this patch. So I am
> comfortable backporting it to dunfell.
Thanks! I'll add this to my patch queue.
Steve
> On Tue, Feb 16, 2021 at
After discussing with Martin offline and also his test reports
indicate that we are not getting worse with this patch. So I am
comfortable backporting it to dunfell.
On Tue, Feb 16, 2021 at 6:08 PM Martin Jansa wrote:
>
> > Generally it was done so it applied on latest data which may be regenerat
Removed upstreamed patches.
Added new package configs.
Signed-off-by: Oleksandr Kravchuk
---
...075-ifconfig.c-pointtopoint_spelling.patch | 26 ---
.../Bug_541172-netstat.c-exit-codes.patch | 22
...ols_1.60-20181103.bb => net-tools_2.10.bb} | 9 +++
3
Removed upstreamed patch.
Signed-off-by: Oleksandr Kravchuk
---
...1-hwclock-make-glibc-2.31-compatible.patch | 83 ---
.../{busybox_1.32.0.bb => busybox_1.33.0.bb} | 4 +-
2 files changed, 1 insertion(+), 86 deletions(-)
delete mode 100644
meta/recipes-core/busybox/busybox/0
Changelog:
- Fix issue with DHCP v6 Rapid Commit option check.
- Fix issue with handling RFC8018/RFC1423 padding.
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-core/ell/{ell_0.37.bb => ell_0.38.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/ell/{ell_0.37
Removed CVE patch was upstreamed.
License-Update: copyright years.
Signed-off-by: Oleksandr Kravchuk
---
.../python/python3/CVE-2021-3177.patch| 191 --
.../{python3_3.9.1.bb => python3_3.9.2.bb}| 5 +-
2 files changed, 2 insertions(+), 194 deletions(-)
delete mod
On Fri, 2021-02-19 at 17:53 +, Jate Sujjavanich wrote:
> Limit setcap search to PATH for cross builds preventing host
> contamination. Add DEPENDS for libcap-native to supply this for
> PACKAGECONFIG libcap.
>
> The previous setting of NO_SETCAP_OR_SUID broke setuid or setcap of
> /bin/ping an
Limit setcap search to PATH for cross builds preventing host
contamination. Add DEPENDS for libcap-native to supply this for
PACKAGECONFIG libcap.
The previous setting of NO_SETCAP_OR_SUID broke setuid or setcap of
/bin/ping and other executables.
Signed-off-by: Jate Sujjavanich
---
...tcap-sea
This reverts commit d10da5f6e6d6d3600645dbe43ed412ff23b55095.
---
meta/recipes-extended/iputils/iputils_s20200821.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-extended/iputils/iputils_s20200821.bb
b/meta/recipes-extended/iputils/iputils_s20200821.bb
index
On Thu, 2021-02-18 at 11:30 +0100, Tomasz Dziendzielski wrote:
> > > Recipes using populate_sdk.bbclass are failing with pseudo abort due to
> > > path mismatch on these paths.
> > >
> > > Signed-off-by: Tomasz Dziendzielski
> > > ---
> > > meta/conf/bitbake.conf | 2 +-
> > > 1 file changed, 1
On Fri, 2021-02-19 at 09:53 +0100, Mans Zigher wrote:
> Hi,
>
> I have a problem getting my customer to understand how to work with
> OE. They have a set of private packages that they continuously need to
> bump up to use the latest version. The packages are stored up in an
> artifactory server. I
I think we need the revert patch, the libcap-native DEPENDS, and then some
logic to exclude the hard-coded paths to setcap if we are cross-compiling.
This seems more mesonic and may be submittable upstream. Your hypothesis
that they hard code the setcap paths for non-root users makes sense,
Richard
GPLv2 and GPLv2+ are two difference licenses with different meanings
and we can't just pretend they're the same thing. Change the code
to treat them separately.
Signed-off-by: Richard Purdie
---
meta/classes/license.bbclass | 11 ++-
meta/lib/oe/license.py | 9 +
2 files c
Where a user adds "GPLv3" to INCOMPATIBLE_LICENSE they almost certainly
mean both GPLv3-only and GPLv3-or-later. Update the code to handle this
correctly.
Signed-off-by: Richard Purdie
---
meta/classes/license.bbclass | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta/classes/license
From: Zbigniew Bodek
Problem spotted on dunfell-23.0.4
Normally, unversioned .so is removed from -dev (default) package
however it is still being referred by other agents, such as webkitgtk.
That can be observed while executing i.e. Epiphany Browser.
For instance:
platformInitializeWebProcess()
On Fri, 2021-02-19 at 11:19 +, florian.bezd...@siemens.com wrote:
> Hi Richard,
>
> On Fri, 2021-02-19 at 10:55 +, Richard Purdie wrote:
> > On Thu, 2021-02-18 at 13:06 +, florian.bezd...@siemens.com wrote:
> > > From: Florian Bezdeka
> > >
> > > The following patch is the summary of
On Fri, 2021-02-19 at 11:26 +, Jose Quaresma wrote:
> The only change needed on the recipe are:
>
> -PACKAGECONFIG[libcap] = "-DUSE_CAP=true, -DUSE_CAP=false, libcap"
> +PACKAGECONFIG[libcap] = "-DUSE_CAP=true, -DUSE_CAP=false, libcap
> libcap-native"
>
> The patch 0001-Add-support-for-setca
Hi,
The only change needed on the recipe are:
-PACKAGECONFIG[libcap] = "-DUSE_CAP=true, -DUSE_CAP=false, libcap"
+PACKAGECONFIG[libcap] = "-DUSE_CAP=true, -DUSE_CAP=false, libcap
libcap-native"
The patch 0001-Add-support-for-setcap-in-STAGING_DIR_NATIVE.patch is not
need because
with the additio
Hi Richard,
On Fri, 2021-02-19 at 10:55 +, Richard Purdie wrote:
> On Thu, 2021-02-18 at 13:06 +, florian.bezd...@siemens.com wrote:
> > From: Florian Bezdeka
> >
> > The following patch is the summary of a nice journey through the file
> > system jungle regarding Y2038 problem. It all
0001-build-sys-do-not-build-plymouth-ctrl.c-w-disabled-pl.patch
0001-hwclock-do-not-assume-__NR_settimeofday_time32.patch
removed since they are included in 2.36.2
Signed-off-by: Wang Mingyu
---
...-build-plymouth-ctrl.c-w-disabled-pl.patch | 52 ---
...-not-assume-__NR_settimeof
Signed-off-by: Wang Mingyu
---
.../{xkeyboard-config_2.31.bb => xkeyboard-config_2.32.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xorg-lib/{xkeyboard-config_2.31.bb =>
xkeyboard-config_2.32.bb} (92%)
diff --git a/meta/recipes-graphics/xorg-lib/xk
On Thu, 2021-02-18 at 13:06 +, florian.bezd...@siemens.com wrote:
> From: Florian Bezdeka
>
> The following patch is the summary of a nice journey through the file
> system jungle regarding Y2038 problem. It all began with a warning which
> is reported by kernels >= 5.4:
>
> ext4 filesyste
On Fri, 2021-02-19 at 11:13 +0100, Quentin Schulz wrote:
> Hi Richard,
>
> On Thu, Feb 18, 2021 at 04:56:40PM +, Richard Purdie wrote:
> > Where a user adds "GPLv3" to INCOMPATIBLE_LICENSE they almost certainly
> > mean both GPLv3-only and GPLv3-or-later. Update the code to handle this
> > cor
Hi Richard,
On Thu, Feb 18, 2021 at 04:56:40PM +, Richard Purdie wrote:
> Where a user adds "GPLv3" to INCOMPATIBLE_LICENSE they almost certainly
> mean both GPLv3-only and GPLv3-or-later. Update the code to handle this
> correctly.
>
> Signed-off-by: Richard Purdie
> ---
> meta/classes/lic
Hi,
I have a problem getting my customer to understand how to work with
OE. They have a set of private packages that they continuously need to
bump up to use the latest version. The packages are stored up in an
artifactory server. I have an idea of maybe helping them out by adding
a manifest file
30 matches
Mail list logo
