Whitelist CVE-2016-20012 as the upstream OpenSSH developers
see this as an important security feature and do not intend to
'fix' it.
Link: https://security-tracker.debian.org/tracker/CVE-2016-20012
https://ubuntu.com/security/CVE-2016-20012
Signed-off-by: Sana Kazi
Signed-off-by: Sana Kazi
---
Add patch to fix CVE-2021-41617
Link: https://bugzilla.suse.com/attachment.cgi?id=854015
Signed-off-by: Sana Kazi
Signed-off-by: Sana Kazi
---
.../openssh/openssh/CVE-2021-41617.patch | 52 +++
.../openssh/openssh_8.2p1.bb | 1 +
2 files changed, 53 insert
On 12/16/21 22:56, Richard Purdie wrote:
CAUTION: Email originated externally, do not click links or open attachments
unless you recognize the sender and know the content is safe.
On Thu, 2021-12-16 at 18:38 +0800, Hsia-Jun Li wrote:
From: "Hsia-Jun(Randy) Li"
Both meson and cmake would w
This avoids the following build error after having run `devtool modify
tzdata`:
cp: cannot stat '.../qemux86-64/workspace/sources/tzdata//usr': No
such file or directory
Signed-off-by: Peter Kjellerstedt
---
PATCHv2: No changes.
meta/recipes-extended/timezone/tzdata.bb | 4 ++--
1 file ch
The name of the package is provided automatically.
Signed-off-by: Peter Kjellerstedt
---
PATCHv2: No changes.
meta/recipes-extended/timezone/tzdata.bb | 12
1 file changed, 12 deletions(-)
diff --git a/meta/recipes-extended/timezone/tzdata.bb
b/meta/recipes-extended/timezone/tz
* Whitespace and indentation clean up.
* Change shell variables from "${foo}" to "$foo".
* Remove "/*" from directories specified in FILES.
* Remove RCONFLICTS:${PN} for the packages from the timezones recipe,
which was dropped from OE-Classic in 2007...
Signed-off-by: Peter Kjellerstedt
---
P
python3-pyelftools uses python3-debugger, python3-pprint.
So add dependencies on these packages.
Signed-off-by: Chaitanya Vadrevu
---
meta/recipes-devtools/python/python3-pyelftools_0.27.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pyelftools_0.27
python3-pyelftools uses python3-debugger, python3-pprint.
So add dependencies on these packages.
Signed-off-by: Chaitanya Vadrevu
---
meta/recipes-devtools/python/python3-pyelftools_0.27.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pyelftools_0.27
Patch withdrawn: turns out meta-tegra was pulling in an old toolchain
for CUDA reasons, and that just got fixed. Probably there isn't another
aarch64 platform still using a non-fixed toolchain, and if there happens
to be one maybe they will run across this patch to carry it in their own
layer.
Not
On Thu, Dec 16, 2021 at 9:00 AM Chaitanya Vadrevu
wrote:
>
> python3-pyelftools uses python3-debugger, python3-pprint.
> So add dependencies on these packages.
>
> Signed-off-by: Chaitanya Vadrevu
> ---
> meta/recipes-devtools/python/python3-pyelftools_0.27.bb | 2 ++
> 1 file changed, 2 inserti
On Thu, Dec 16, 2021 at 2:07 PM Jon Mason wrote:
>
> Signed-off-by: Jon Mason
> ---
> meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> b/meta/recipes-kernel/linux/linux-yocto-dev.
Signed-off-by: Jon Mason
---
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb
b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 80f62a0412ad..744b74ce3749 100644
--- a/meta/recipes-ker
On Thu, 2021-12-16 at 18:25 +0100, Quentin Schulz wrote:
> Hi Richard,
>
> On December 16, 2021 2:22:18 PM GMT+01:00, Richard Purdie
> wrote:
> > The only recipe mentioning python3-idna in OE-Core is python3-jsonschema.
> > python3-jsonschema only depends on it if the nongpl package config optio
Hi,
The next OpenEmbedded Happy Hour is being canceled due to the Holidays and
since we had the last one on December 3. The next Happy Hour will take place
on January 26 2022:
https://www.openembedded.org/wiki/Calendar
--
Regards,
Denys Dmytriyenko
PGP: 0x420902729A92C964 - https://denix.org
Hello Tom,
Em qui., 16 de dez. de 2021 às 15:55, Tom Hochstein
escreveu:
> A colleague notes a cmake problem in the SDK due to CMAKE_SYSTEM_PROCESSOR
> being set to 'cortexa53-crypto', which the package doesn't recognize. The
> package builds fine with bitbake because CMAKE_SYSTEM_PROCESSOR is
A colleague notes a cmake problem in the SDK due to CMAKE_SYSTEM_PROCESSOR
being set to 'cortexa53-crypto', which the package doesn't recognize. The
package builds fine with bitbake because CMAKE_SYSTEM_PROCESSOR is set to
'aarch64', which the package does recognize.
The value for the SDK comes
The correct SPDX license for the test data contained in this code appears
to be Unicode-TOU. Update the LICENSE field to match and avoid package
QA warnings.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/python/python3-idna_3.3.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi Martin,
I just noticed that since this change, syslogd is compiled in by default, even I
have SRC_URI:remove = "file://syslog.cfg" in a bbappend. Is this intentional?
Otherwise, I'd prefer change the back to disabled by default (SRC_URI still
contains syslog.cfg by default).
Regards,
Jan
On W
Hi Richard,
On December 16, 2021 2:22:18 PM GMT+01:00, Richard Purdie
wrote:
>The only recipe mentioning python3-idna in OE-Core is python3-jsonschema.
>python3-jsonschema only depends on it if the nongpl package config option
>is set. We don't set this option.
>
That is unfortunately incorrect
Hi all,
On December 16, 2021 4:03:14 PM GMT+01:00, Saul Wold
wrote:
>
>
>On 12/8/21 01:57, Eero Aaltonen wrote:
>> On Mon, 2021-12-06 at 23:31 +, Richard Purdie via
>> lists.openembedded.org wrote:
>>> On Mon, 2021-12-06 at 16:35 +0100, Quentin Schulz wrote:
blocklist has a more obvious
On Thu, Dec 16, 2021 at 7:53 AM Matt Madison via
lists.openembedded.org
wrote:
>
> On Thu, Dec 16, 2021 at 6:47 AM Joshua Watt wrote:
> >
> > On Wed, Dec 15, 2021 at 8:16 AM Matt Madison wrote:
> > >
> > > I'm finding that none of the Rust recipes are getting setscened in my
> > > builds off
>
On Thu, Dec 16, 2021 at 12:29 AM Alexander Kanavin
wrote:
>
> On Thu, 16 Dec 2021 at 00:28, Khem Raj wrote:
>>
>> > Drop 0001-fiber-libs-Define-SYS_futex-if-it-does-not-exist.patch as
>> > it is difficult to rebase and needs to land upstream first.
>>
>> It's not that rebasing is too hard for thi
python3-pyelftools uses python3-debugger, python3-pprint.
So add dependencies on these packages.
Signed-off-by: Chaitanya Vadrevu
---
meta/recipes-devtools/python/python3-pyelftools_0.27.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pyelftools_0.27
On Thu, Dec 16, 2021 at 6:47 AM Joshua Watt wrote:
>
> On Wed, Dec 15, 2021 at 8:16 AM Matt Madison wrote:
> >
> > I'm finding that none of the Rust recipes are getting setscened in my
> > builds off
> > master due to the the SRCPV hack that was added to make the cargo fetcher
> > visible during
On 16.12.21 15:54, Richard Purdie wrote:
On Thu, 2021-12-16 at 13:26 +0100, Konrad Weihmann wrote:
if a patch uses Upstream-Status: Inappropriate it should provide a machine
readable reasoning in square brackets.
According to latest wiki entry that would be
not author
native
licensing
config
On 12/8/21 01:57, Eero Aaltonen wrote:
On Mon, 2021-12-06 at 23:31 +, Richard Purdie via
lists.openembedded.org wrote:
On Mon, 2021-12-06 at 16:35 +0100, Quentin Schulz wrote:
blocklist has a more obvious meaning than blacklist and is also not
an
issue wrt inclusivity, so let's use that n
On Thu, 2021-12-16 at 18:38 +0800, Hsia-Jun Li wrote:
> From: "Hsia-Jun(Randy) Li"
>
> Both meson and cmake would work fine, left those GNU autotools,
> customer script projects.
>
> The behaviour of meson would become that as the following for
> the Android target:
> lib/libfoo.so is the real b
On Thu, 2021-12-16 at 13:26 +0100, Konrad Weihmann wrote:
> if a patch uses Upstream-Status: Inappropriate it should provide a machine
> readable reasoning in square brackets.
>
> According to latest wiki entry that would be
>
> not author
> native
> licensing
> configuration
> enable feature
> d
On 16.12.21 15:41, Richard Purdie wrote:
On Wed, 2021-12-15 at 13:12 +0100, Konrad Weihmann wrote:
so one can get the layer name from a filepath
Signed-off-by: Konrad Weihmann
---
v2: order by path length to correctly map nested layer
meta/lib/oe/recipeutils.py | 11 ++-
1 file c
Please merge these changes.
Thanks,
Anuj
The following changes since commit b8fa0c446ecb3f65d7c134426a07c6244959cdf7:
libdrm: upgrade 2.4.108 -> 2.4.109 (2021-12-09 09:17:26 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/honiste
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.13.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
On Wed, Dec 15, 2021 at 8:16 AM Matt Madison wrote:
>
> I'm finding that none of the Rust recipes are getting setscened in my builds
> off
> master due to the the SRCPV hack that was added to make the cargo fetcher
> visible during parsing. There's no error reported about it, but by adding an
> e
On Wed, 2021-12-15 at 13:12 +0100, Konrad Weihmann wrote:
> so one can get the layer name from a filepath
>
> Signed-off-by: Konrad Weihmann
> ---
> v2: order by path length to correctly map nested layer
>
> meta/lib/oe/recipeutils.py | 11 ++-
> 1 file changed, 10 insertions(+), 1 dele
The only recipe mentioning python3-idna in OE-Core is python3-jsonschema.
python3-jsonschema only depends on it if the nongpl package config option
is set. We don't set this option.
The idna recipe has license issues with questions around the Unicode license
(still in meta-oe) and which version va
if a patch uses Upstream-Status: Inappropriate it should provide a machine
readable reasoning in square brackets.
According to latest wiki entry that would be
not author
native
licensing
configuration
enable feature
disable feature
bugfix .*
embedded specific
no upstream
other
a detailed reasoni
which enables us to drop the -r option on qemu-static-riscv32
invocations.
Signed-off-by: Matt Madison
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
...s-minimum-kernel-version-for-riscv32.patch | 40 +++
2 files changed, 41 insertions(+)
create mode 100644
meta/rec
This addresses an issue with allarch recipes that use meson, where
inheriting qemu.bbclass causes task signature changes when built with
MACHINEs with different architectures due to the reference to the
OLDEST_KERNEL variable for setting up qemu wrapper invocations.
V2:
* Backport Khem's qemu pa
which is introducing task hash changes for some
allarch package builds, and should no longer
be needed with recent versions of qemu.
Signed-off-by: Matt Madison
---
meta/classes/qemu.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/qemu.bbclass b/meta/clas
Hi Alexander,
> From: Alexander Kanavin
> Sent: Thursday, December 16, 2021 1:40 AM
> To: openembedded-core@lists.openembedded.org
>
> Cc: Alexander Kanavin ; Alexey Brodkin
>
> Subject: [PATCH 15/26] dpkg: update 1.20.9 -> 1.21.1
>
> Signed-off-by: Alexander Kanavin
> ---
> meta/recipes
From: "Hsia-Jun(Randy) Li"
It is fair to regard Android as Linux target, we repack
the sysroot, so we don't need to bother those helper
from openssl.
Signed-off-by: Hsia-Jun(Randy) Li
---
meta/recipes-connectivity/openssl/openssl_3.0.0.bb | 4
1 file changed, 4 insertions(+)
diff --git a
From: "Hsia-Jun(Randy) Li"
Signed-off-by: Randy Li
Signed-off-by: Hsia-Jun(Randy) Li
---
meta/classes/meson-routines.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/meson-routines.bbclass
b/meta/classes/meson-routines.bbclass
index be3aeedeba..f9a06a16d8 100644
---
From: "Hsia-Jun(Randy) Li"
Both meson and cmake would work fine, left those GNU autotools,
customer script projects.
The behaviour of meson would become that as the following for
the Android target:
lib/libfoo.so is the real binary library
lib/libfoo.so.x -> libfoo.so
lib/libfoo.so.x.y -> libfoo
From: "Hsia-Jun(Randy) Li"
Signed-off-by: Randy Li
Signed-off-by: Hsia-Jun(Randy) Li
---
meta/classes/cmake.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
index 92b9197c48..40ae4fba08 100644
--- a/meta/classes/cmake.bbclass
Discussion in https://github.com/rust-lang/git2-rs/pull/759 doesn't exactly
fill one with confidence, but still, can this be handled and fixed in rust
upstream? Non-upstreamable patches for what is a common use case aren't a
good idea.
Alex
On Thu, 16 Dec 2021 at 10:19, S. Lockwood-Childs wrote:
Typical error when trying to build a rust app (for example, librsvg)
for aarch64 targets looks like:
undefined references to `__aarch64_ldadd8_rel'
The upstream rust commit
"add target feature outline-atomics" 0f9f241aac21bc77fb9e757da18207abefdc841d
has caused a number of such link failure regr
On Thu, 16 Dec 2021 at 00:28, Khem Raj wrote:
> > Drop 0001-fiber-libs-Define-SYS_futex-if-it-does-not-exist.patch as
> > it is difficult to rebase and needs to land upstream first.
>
> It's not that rebasing is too hard for this patch but this patch is an
> incorrect way to fix what it's trying
46 matches
Mail list logo