Two of my patches are in master-next since some time. Is there any reason why
they don't appear in master?
https://patchwork.openembedded.org/series/24760/#
https://patchwork.openembedded.org/series/24775/#
I would like to send further patches for meta-openembedded which
depend on the above
Hi Richard,
thanks, that does help maybe a little. Personally, I find the license /
compliance topic one of the most annoying things in embedded development
*by far*. I also wonder, why nobody else has stumbled across this, since
I guess it is quite common to rule out GPLv3, because most
Signed-off-by: Wang Mingyu
---
.../glib-2.0/{glib-2.0_2.64.3.bb => glib-2.0_2.64.4.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-core/glib-2.0/{glib-2.0_2.64.3.bb => glib-2.0_2.64.4.bb}
(93%)
diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.64.3.bb
Signed-off-by: Wang Mingyu
---
.../dbus/{dbus-test_1.12.18.bb => dbus-test_1.12.20.bb} | 0
meta/recipes-core/dbus/dbus.inc | 4 ++--
meta/recipes-core/dbus/{dbus_1.12.18.bb => dbus_1.12.20.bb} | 0
3 files changed, 2 insertions(+), 2 deletions(-)
rename
CVE-2017-14160.patch
CVE-2018-10392.patch
removed since they are included in 1.3.7
-License-Update: Copyright year updated to 2020.
license text: URL of Xiph.Org Foundation changed to https://xiph.org/
Signed-off-by: Wang Mingyu
---
.../libvorbis/libvorbis/CVE-2017-14160.patch | 34
Signed-off-by: Wang Mingyu
---
.../fribidi/{fribidi_1.0.9.bb => fribidi_1.0.10.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/fribidi/{fribidi_1.0.9.bb => fribidi_1.0.10.bb}
(76%)
diff --git a/meta/recipes-support/fribidi/fribidi_1.0.9.bb
== Series Details ==
Series: Modied the license to GPLv2.1+ to keep with LICENSE file. (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/24527/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response.
On Wed, 2020-07-08 at 10:19 +0200, Matthias Schoepfer wrote:
> thanks, that does help maybe a little. Personally, I find the license
> / compliance topic one of the most annoying things in embedded
> development *by far*. I also wonder, why nobody else has stumbled
> across this, since I guess it
On Wed, 2020-07-08 at 08:20 +0200, Christian Eggers wrote:
> Two of my patches are in master-next since some time. Is there any
> reason why
> they don't appear in master?
>
> https://patchwork.openembedded.org/series/24760/#
> https://patchwork.openembedded.org/series/24775/#
>
> I would like
Please reference to https://gitlab.com/gnutls/gnutls/-/issues/1018.
Upstream-Status: Backport
[https://gitlab.com/gnutls/gnutls/-/merge_requests/1285].
Signed-off-by: Zheng Ruoqin
---
...se-to-GPLv2.1-to-keep-with-LICENSE-f.patch | 88 +++
From: Changqing Li
'bitbake world -k' when DISTRO_FEATURES don't have x11 and wayland,
report errors:
Nothing PROVIDES 'gtk+3'
Nothing RPROVIDES 'blueman'
gtk+3 set ANY_OF_DISTRO_FEATURES, so add it here too
since we DEPENDS on it
Signed-off-by: Changqing Li
---
On Wed, 2020-07-08 at 13:09 +0200, Konrad Weihmann wrote:
> It warns about trailing blanks before the delimiter, as otherwise the
> task can't be removed properly
>
> Signed-off-by: Konrad Weihmann
> ---
> meta/classes/rootfs-postcommands.bbclass | 8
> 1 file changed, 8 insertions(+)
remove the traling blanks before the ;-delimiter, so one could use
"_remove" to avoid running tasks like 'rootfs_update_timestamp',
which are currently hardcoded and not bound to any
configurable feature flag
Signed-off-by: Konrad Weihmann
---
meta/classes/rootfs-postcommands.bbclass | 6 +++---
- libblkid is exclusively licensed under LGPL-2.1+ (libblkid/COPYING)
- libfdisk is exclusively licensed under LGPL-2.1+ (libfdisk/COPYING)
- libmount is exclusively licensed under LGPL-2.1+ (libmount/COPYING)
- libsmartcols is exclusively licensed under LGPL-2.1+
(libsmartcols/COPYING)
- libuuid
The right ibt(intel bluetooth) firmware is under the folder of "intel".
Signed-off-by: Jun Miao
---
meta/recipes-kernel/linux-firmware/linux-firmware_20200619.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20200619.bb
Hi Richard,
Am Mittwoch, 8. Juli 2020, 11:20:40 CEST schrieb Richard Purdie:
> The issue is I still don't really like the eudev one in particular. A
> native eudev really doesn't make sense and I'm reluctant to encourage
> people to build such a thing. I suspect you can't convince
>
According to the PACKAGES variable, LICENSE_avahi-client is misspelled.
Additionally, the libavahi-client package actually only includes
LGPLv2.1+ software (as opposed to the global LICENSE variable).
Signed-off-by: Christian Eggers
---
meta/recipes-connectivity/avahi/avahi_0.8.bb | 2 +-
1
On Wed, 2020-07-08 at 11:40 +0200, Christian Eggers wrote:
> Am Mittwoch, 8. Juli 2020, 11:20:40 CEST schrieb Richard Purdie:
> > The issue is I still don't really like the eudev one in particular.
> > A
> > native eudev really doesn't make sense and I'm reluctant to
> > encourage
> > people to
It warns about trailing blanks before the delimiter, as otherwise the
task can't be removed properly
Signed-off-by: Konrad Weihmann
---
meta/classes/rootfs-postcommands.bbclass | 8
1 file changed, 8 insertions(+)
diff --git a/meta/classes/rootfs-postcommands.bbclass
According to [1], a license manifest is generated during image creation:
"The Yocto Project generates a license manifest during image creation that is
located in ${DEPLOY_DIR}/licenses/image_name-datestamp to assist with any
audits."
This manifest lists all packages installed on the target
On Wed, Jul 08, 2020 at 11:40:30AM +0200, Christian Eggers wrote:
>...
> For NATIVE, I need the libs for running automatic unit tests on the
> build machine. One could probably ask whether unit tests should
> depend on libraries like libudev or libnm.
>...
I would rather ask why you aren't
On Wed, 2020-07-08 at 17:48 +0200, Christian Eggers wrote:
> According to [1], a license manifest is generated during image
> creation:
>
> "The Yocto Project generates a license manifest during image creation
> that is located in ${DEPLOY_DIR}/licenses/image_name-datestamp to
> assist with any
Am Mittwoch, 8. Juli 2020, 16:20:03 CEST schrieb Adrian Bunk:
> I would rather ask why you aren't running automatic unit tests
> built for the target inside qemu.
>
> cu
> Adrian
This may be an option. Currently the platform (x86 or arm)
decides whether real peripheral routines or mock objects
On Wed, 2020-07-08 at 17:07 +0200, Christian Eggers wrote:
> From Richard I got no response to the question whether
> potentially every package may be extended for nativesdk/native,
> or these platforms a reserved for packages required for "building".
There needs to be a sensible use case for
On Wed, Jul 08, 2020 at 04:35:21PM +0100, Richard Purdie wrote:
> On Wed, 2020-07-08 at 17:07 +0200, Christian Eggers wrote:
> > From Richard I got no response to the question whether
> > potentially every package may be extended for nativesdk/native,
> > or these platforms a reserved for packages
Put files from installed tests into a ptest package to avoid having
them in an image and to avoid having more runtime dependencies
than necessary.
Signed-off-by: Konrad Weihmann
---
meta/classes/distutils-common-base.bbclass | 5 +
1 file changed, 5 insertions(+)
diff --git
as ptest FILES could be determined before or after the classes was
inherited, if is much safer to append to the setting of
FILES_${PN}-ptest
Signed-off-by: Konrad Weihmann
---
meta/classes/ptest.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Instead of recognizing only environment-setup scripts in
${STAGING_DIR_TARGET} or ${STAGING_DIR_NATIVE}, respectively - lurk also into
${SDKPATH}/buildtools/sysroots/${SDK_SYS} where nativesdk-openssl installs
setup files.
Remove overwriting of OPENSSL_CONF from buildtools-tarball.bb to clarify
If you are running your builds inside an environment where you don't
have access to the build tree (e.g. an autobuilder where you can only
download final artifacts such as images), then debugging build failures
can be difficult - you can't examine log files, the source tree or output
files. When
This is fairly trivial but I've found it useful in my setup - I'd like to
know if others would as well. Improvement suggestions welcome.
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
On Wed, 2020-07-08 at 11:02 -0700, Paul Eggleton wrote:
> If you are running your builds inside an environment where you don't
> have access to the build tree (e.g. an autobuilder where you can only
> download final artifacts such as images), then debugging build
> failures
> can be difficult -
From: Alexander Kanavin
Drop backports.
Drop 0001-gen.c-extend-DIRNAMESIZE-from-256-to-512.patch and
0001-lib-dns-gen.c-fix-too-long-error.patch as problem is fixed
upstream.
(From OE-Core rev: 6965ec5c491e71d5951dfb58fc060bd0b717e33d)
Signed-off-by: Alexander Kanavin
Signed-off-by: Ross
From: Armin Kuster
Source: http://w1.fi/security/
Disposition: Backport from http://w1.fi/security/2020-1/
Affects <= 2.9 wpa-supplicant
(From OE-Core rev: 720d29cbfce34375402c6a4c17e440ffbb2659bf)
Signed-off-by: Armin Kuster
(cherry picked from commit
From: Kai Kang
It fails to build gcr if no commmand gpg on build host:
| meson.build:44:0: ERROR: Program(s) ['gpg2', 'gpg'] not found or not
executable
Add dependency gnupg-native to fix the error.
(From OE-Core rev: da7360247995d7c8e79dfcaa0c0761952a9013f1)
Signed-off-by: Kai Kang
From: Khem Raj
Certain recipes e.g. bash readline ( from meta-gplv2 ) download patches instead
of having them in
metadata, this could fail cve_check
ERROR: readline-5.2-r9 do_cve_check: File Not found:
qemuarm/build/../downloads/readline52-001
This patch ensures that download is done before
Backported patch removed.
Signed-off-by: Adrian Bunk
---
...20-8492-Fix-AbstractBasicAuthHandler.patch | 248 --
.../{python3_3.7.7.bb => python3_3.7.8.bb}| 5 +-
2 files changed, 2 insertions(+), 251 deletions(-)
delete mode 100644
From: Kai Kang
Remove service templates wpa_supplicant-nl80211@.service and
wpa_supplicant-wired@.service from SYSTEMD_SERVICE that they should NOT
be started/stopped by calling 'systemctl' in postinst and prerm scripts.
(From OE-Core rev: 7910a0d6f332253608767a9576a0d521dd87efd7)
From: Kai Kang
Postinst script from xorg-font-common.inc doesn't apply to this recipe.
So clear the postinst script of encodings.
(From OE-Core rev: ba94c908b99713ce115e9240df525c6442a60c7a)
Signed-off-by: Kai Kang
(cherry picked from commit 99ae6dbb7278dfd264453af852c108fa56a0d4e3)
From: Richard Purdie
We were seeing a ton of empty perl modules being created such as
"perl-module-x86-64-linux-encoding" where the name would include
${TARGET_ARCH}-linux. These files were already being filtered in an
earlier do_split_packages() expression so exclude them from the latter
one to
From: akuster
Bug fix only updates.
suitable for Stable branch updates where applicable.
Drop CVE patches included in update
LIC_FILES_CHKSUM update copyright year to 2020
Full changes found at :
https://gitlab.isc.org/isc-projects/bind9/-/blob/v9_11/CHANGES
(From OE-Core rev:
From: Otavio Salvador
This changeset fixes a feature regression in ubiformat. Older versions
of ubiformat, when invoked with a flash-image, would return 0 in the
case no error was encountered. Upon upgrading to latest, it was
discovered that ubiformat returned 255 even without encountering an
From: Lee Chee Yang
(From OE-Core rev: 3f69946c6159fa359bc5800ee72ef6151d9ecd36)
Signed-off-by: Lee Chee Yang
Signed-off-by: Steve Sakoman
Signed-off-by: Richard Purdie
Signed-off-by: Adrian Bunk
---
.../dbus/dbus/CVE-2020-12049.patch| 78 +++
From: Lee Chee Yang
(From OE-Core rev: d9c5d9c52eb1f03ff9c907a76dda31042fb26edb)
Signed-off-by: Lee Chee Yang
Signed-off-by: Steve Sakoman
Signed-off-by: Richard Purdie
Signed-off-by: Adrian Bunk
---
.../perl/files/CVE-2020-10543.patch | 36 +
From: Sakib Sajal
Fixes CVE-2020-11655
(From OE-Core rev: 3b06a6c73f4e49c6d00f758423c2e8865ec2de00)
Signed-off-by: Sakib Sajal
Signed-off-by: Richard Purdie
[ without the CVE-2020-11656 fix that did not apply cleanly ]
Signed-off-by: Adrian Bunk
---
.../sqlite/files/CVE-2020-11655.patch
From: Joe Slater
vim will abort in many places with this setting. Replace
it with the benign _FORTIFY_SOURCE=1.
(From OE-Core rev: d9de155f6452f916edd3131addd0c2eebaf4d639)
Signed-off-by: Joe Slater
(cherry picked from commit 18129cbaeddb3278efe9963718556e3765f06c1e)
Signed-off-by: Steve
From: Jan-Simon Moeller
file-native when built on a Debian 10 host will embed a dependency to
'libbz2.so.1.0' (instead of 'libbz2.so.1'). This can cause issues
when sharing the sstate between hosts e.g.:
recipe-sysroot-native/usr/lib/rpm/rpmdeps:
error while loading shared libraries:
From: Pierre-Jean Texier
See full changelog https://github.com/eggert/tz/blob/master/NEWS#L11
(From OE-Core rev: 9d74b048e3a160d7a9a20e85817e9eb3a558af63)
Signed-off-by: Pierre-Jean Texier
Signed-off-by: Richard Purdie
Signed-off-by: Adrian Bunk
---
From: Richard Purdie
patchelf can corrupt shared libraries if the program headers don't
immediately follow the elf header. Add a patch submitted upstream
to address this.
(From OE-Core rev: faaf5f34332290708f3720a5488b3d1549d9e95a)
Signed-off-by: Richard Purdie
(cherry picked from commit
From: Lee Chee Yang
(From OE-Core rev: 2e497029ee00babbc50f3c1d99580230bc46155c)
Signed-off-by: Lee Chee Yang
Signed-off-by: Steve Sakoman
Signed-off-by: Richard Purdie
Signed-off-by: Adrian Bunk
---
.../libexif/libexif/CVE-2020-13114.patch | 73 +++
From: Ralph Siemsen
In the generated cve.log files, include the epoch in the product
version. This better matches how versions are displayed elsewhere,
in particular the bb.warn("Found unpatched CVE...") that appears
on the terminal when CVEs are found.
(From OE-Core rev:
Em qua., 8 de jul. de 2020 às 16:58, Jens Rehsack escreveu:
>
> Instead of recognizing only environment-setup scripts in
> ${STAGING_DIR_TARGET} or ${STAGING_DIR_NATIVE}, respectively - lurk also into
> ${SDKPATH}/buildtools/sysroots/${SDK_SYS} where nativesdk-openssl installs
> setup files.
>
>
== Series Details ==
Series: "[zeus] python3: Upgrade 3.7.7 ..." and 18 more
Revision: 1
URL : https://patchwork.openembedded.org/series/25061/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have
Every selftest run is currently polluting the autobuilder DL_DIR. Avoid
this by using a temporary directory for the test which is cleaned up.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
For SDK environments where people still use subversion, let it easily being
added to buildtools-tarball to invite more developers relying on Yocto
based SDKs without much requirement to setup anything on the development
workplace.
Signed-off-by: Jens Rehsack
---
As an unconditionally dependency of subversion, extend serf recipe for
building a nativesdk variant being usable by nativesdk-subversion.
Signed-off-by: Jens Rehsack
---
meta/recipes-support/serf/serf_1.3.9.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
> Am 08.07.2020 um 13:09 schrieb Konrad Weihmann :
>
> remove the traling blanks before the ;-delimiter, so one could use
^
here & subject: do you mean "trailing"?
> "_remove" to avoid running tasks like 'rootfs_update_timestamp',
> which are currently hardcoded
On 7/9/20 7:30 AM, Jens Rehsack wrote:
Am 08.07.2020 um 13:09 schrieb Konrad Weihmann :
remove the traling blanks before the ;-delimiter, so one could use
^
here & subject: do you mean "trailing"?
"_remove" to avoid running tasks like
Signed-off-by: Jun Miao
---
meta/recipes-kernel/linux-firmware/linux-firmware_20200619.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20200619.bb
b/meta/recipes-kernel/linux-firmware/linux-firmware_20200619.bb
index
Chamelium is a hardware device that can be used for external display
test automation [1].
It is disabled by default and can be turned on through PACKAGECONFIG.
[1] https://www.chromium.org/chromium-os/testing/chamelium
Signed-off-by: Arthur She
---
On Tue, 2020-07-07 at 18:01 -0700, Arthur She wrote:
> Hi Anuj,
> Thanks for your review.
> I don't need to put "-Dchamelium=disabled" in the EXTRA_OEMESON.
> Because chamelium is disabled by default.
> Is it correct?
Yes, since it's disabled by default, -Dchamelium=disabled is already
being
Hi Anuj,
Thanks for your explanation.
I've sent patch v2 out.
Thanks,
Arthur
On Wed, Jul 8, 2020 at 6:29 PM Mittal, Anuj wrote:
> On Tue, 2020-07-07 at 18:01 -0700, Arthur She wrote:
> > Hi Anuj,
> > Thanks for your review.
> > I don't need to put "-Dchamelium=disabled" in the EXTRA_OEMESON.
>
> Am 08.07.2020 um 23:20 schrieb Otavio Salvador
> :
>
> Em qua., 8 de jul. de 2020 às 16:58, Jens Rehsack
> escreveu:
>>
>> Instead of recognizing only environment-setup scripts in
>> ${STAGING_DIR_TARGET} or ${STAGING_DIR_NATIVE}, respectively - lurk also into
>>
62 matches
Mail list logo
