There doesn't seem to be a clear reason to have two separate
variables to hold whitelisted GPLv3 recipes. Both variables are
treated the same, so adding a recipe to LGPLv2_WHITELIST_GPL-3.0 is
already equivalent to adding it to WHITELIST_GPL-3.0.
Anyone needing to whitelist a GPLv3 recipe should
An elevation of privilege vulnerability in libnl could enable a local
malicious application to execute arbitrary code within the context of
the Wi-Fi service. This issue is rated as Moderate because it first
requires compromising a privileged process and is mitigated by
current platform
On Fri, May 11, 2018 at 12:21 PM, Martin Jansa wrote:
> * sdl1 since qemu-2.12.0 depends on x11 in DISTRO_FEATURES, switch to sdl2
>
> Signed-off-by: Martin Jansa
Reviewed-by: Alistair Francis
Alistair
> ---
>
On Fri, May 11, 2018 at 12:20 PM, Martin Jansa wrote:
> * enable x11 in native builds
>
> Signed-off-by: Martin Jansa
Reviewed-by: Alistair Francis
Alistair
> ---
> meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb | 4
On Fri, May 11, 2018 at 12:44 PM, Martin Jansa wrote:
> On Thu, May 10, 2018 at 03:06:47PM -0700, Alistair Francis wrote:
>> On Thu, May 10, 2018 at 2:58 PM, Martin Jansa wrote:
>> > See
On Fri, May 11, 2018 at 12:21 PM, Martin Jansa wrote:
> From: Martin Jansa
>
> Signed-off-by: Martin Jansa
> Signed-off-by: Ross Burton
Reviewed-by: Alistair Francis
On Fri, May 11, 2018 at 12:21 PM, Martin Jansa wrote:
> From: Martin Jansa
>
> * drop patches which are now included upstream
>
> Signed-off-by: Martin Jansa
> Signed-off-by: Ross Burton
On Fri, May 11, 2018 at 6:17 PM, wrote:
> Hi Bruce,
>
>
>
> Thanks for your insights. The defconfig is coming from
> KBUILD_DEFCONFIG_machinename = “our_defconfig” in our machine conf. I
> understand that the defconfig is just another configuration fragment, but
>
Hi Bruce,
Thanks for your insights. The defconfig is coming from
KBUILD_DEFCONFIG_machinename = “our_defconfig” in our machine conf. I
understand that the defconfig is just another configuration fragment, but given
that it has its own variable (KBUILD_DEFCONFIG) I guess I was expecting a bit
This one?
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=ross/mut=2e9012e6b44b83b3952598b08cd9d5dadd633b69
Ross
On 11 May 2018 at 20:33, Otavio Salvador
wrote:
> On Fri, May 11, 2018 at 12:41 PM, Burton, Ross wrote:
>>
I threw the branch at the Yocto Project autobuilder today, produced a
number of failures:
http://errors.yoctoproject.org/Errors/Latest//?filter=b23dba19607412c8cc7d267d95354d65f5631088=commit
Ross
On 5 May 2018 at 01:26, Khem Raj wrote:
> Hi All
>
> As you might have
On Fri, May 11, 2018 at 5:32 PM, Martin Jansa wrote:
> On Fri, May 11, 2018 at 05:21:09PM -0400, Chris Patterson wrote:
>> On Fri, May 11, 2018 at 3:10 PM, Christopher Larson
>> wrote:
>> > This is not a correct fix. We have a gettext bbclass for a
On Fri, May 11, 2018 at 05:21:09PM -0400, Chris Patterson wrote:
> On Fri, May 11, 2018 at 3:10 PM, Christopher Larson wrote:
> > This is not a correct fix. We have a gettext bbclass for a reason.
> >
>
> I did look at that prior to doing this. It was my initial approach,
>
On Fri, May 11, 2018 at 3:10 PM, Christopher Larson wrote:
> This is not a correct fix. We have a gettext bbclass for a reason.
>
I did look at that prior to doing this. It was my initial approach,
but inheriting gettext causes qemu build to fail when it modifies the
On Fri, May 11, 2018 at 3:28 PM, Chris Laplante via Openembedded-core <
openembedded-core@lists.openembedded.org> wrote:
> OK, I figured out why this happens. This line in kernel-yocto.bbclass:
>
>
>
> scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes}
> ${bsp_definition} ${sccs}
Hi all,
I'm working on using Jenkins to host our Yocto build. One of the things that
would be nice is to be able to do a "bitbake our-user-image", upload the
artifacts to our network file storage, and then do a "bitbake our-user-image -c
populate_sdk_ext". I'd like to do these separately so
From: Dan McGregor
Fedora uses permissions of 555 for /proc and /sys. Debian doesn't
seem to explicitly set their permissions. In addition they're mounted
555. Having them be 755 causes permission issues on upgrades inside a
container when the guest does not have the
From: Dan McGregor
It should be /proc/self/mounts instead of /proc/mounts. Also switch to
using a relative link in base-files, as seems to be the convention in
other distributions.
Signed-off-by: Dan McGregor
---
From: Dan McGregor
Signed-off-by: Dan McGregor
---
meta/conf/bitbake.conf| 1 +
meta/files/fs-perms-persistent-log.txt| 4 ++--
meta/files/fs-perms.txt | 4 ++--
On Thu, May 10, 2018 at 03:06:47PM -0700, Alistair Francis wrote:
> On Thu, May 10, 2018 at 2:58 PM, Martin Jansa wrote:
> > See http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu
> > +
On Fri, May 11, 2018 at 12:41 PM, Burton, Ross wrote:
> Somehow, these patches are causing selftest to fail:
>
> ERROR: Not supported fstype:
>
> https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/1051/steps/Running%20oe-selftest/logs/stdio
You forgot the
On 05/10/2018 05:02 AM, Burton, Ross wrote:
> Hi Jackie,
>
> Did you get to look at the distcc 3.3 upgrade failures? We're open
> again for updates and moving to 3.3 instead of a forked repository on
> Armin's personal github would be nice!
yes it would.
- armin
>
> Ross
>
> On 22 March 2018
OK, I figured out why this happens. This line in kernel-yocto.bbclass:
scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} ${bsp_definition}
${sccs} ${patches} ${KERNEL_FEATURES}
... passes the BSP def before the sccs. In my case, the BSP def is
mymachine.scc, and the sccs is the
* enable x11 in native builds
Signed-off-by: Martin Jansa
---
meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.8.bb
index
* sdl1 since qemu-2.12.0 depends on x11 in DISTRO_FEATURES, switch to sdl2
Signed-off-by: Martin Jansa
---
meta/recipes-devtools/qemu/qemu.inc | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-devtools/qemu/qemu.inc
* drop "fdt sdl" listed twice in PACKAGECONFIG
* sdl2 when selected needs sdl as well and will depend on both libsdl
and libsdl
* keep all 4 disabled by default
* spice, usbredir recipes will eventually be in meta-networking layer
(you can use jansa/spice branch from meta-openembedded-contrib
From: Martin Jansa
Signed-off-by: Martin Jansa
Signed-off-by: Ross Burton
---
.../qemu/qemu/add-ptest-in-makefile-v10.patch | 13 ---
.../qemu/apic-fixup-fallthrough-to-PIC.patch | 15
From: Martin Jansa
* drop patches which are now included upstream
Signed-off-by: Martin Jansa
Signed-off-by: Ross Burton
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
This is not a correct fix. We have a gettext bbclass for a reason.
On Fri, May 11, 2018 at 9:35 AM, Chris Patterson wrote:
> From: Chris Patterson
>
> Otherwise QEMU build may fail with missing `msgfmt` command.
>
> | make -C po install
> | GEN
Hi all,
Is it expected for do_kernel_configme to apply the defconfig last (after
configuration fragments introduced by sccs)?
For some reason, in the call to merge_config,
".kernel-meta/configs//./defconfig" is passed last whereas I'd expect it would
be first (since that should be the base
On Fri, May 11, 2018 at 10:25 AM, Chris Patterson wrote:
> From: Chris Patterson
>
> Otherwise QEMU build may fail with missing `msgfmt` command.
>
> | make -C po install
> | GEN bg.mo
> | GEN tr.mo
> | GEN de_DE.mo
> | /bin/sh:
From: Chris Patterson
Signed-off-by: Chris Patterson
---
meta-networking/recipes-support/strongswan/strongswan_5.6.2.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
* We use ssp impl directly from glibc/musl now.
Signed-off-by: Martin Jansa
---
meta/recipes-devtools/perl/perl-ptest.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/perl/perl-ptest.inc
On Fri, May 11, 2018 at 1:10 AM, André Draszik wrote:
> From: André Draszik
>
> This is similar to commit f76ee525a75d, but instead of disabling
> the patch on all builds, we only remove it for x86-64 builds, as
> the original change's commit message
From: Chris Patterson
Otherwise QEMU build may fail with missing `msgfmt` command.
| make -C po install
| GEN bg.mo
| GEN tr.mo
| GEN de_DE.mo
| /bin/sh: msgfmt: command not found
| /bin/sh: msgfmt: command not found
Signed-off-by: Chris Patterson
From: Chris Patterson
Otherwise QEMU build may fail with missing `msgfmt` command.
| make -C po install
| GEN bg.mo
| GEN tr.mo
| GEN de_DE.mo
| /bin/sh: msgfmt: command not found
| /bin/sh: msgfmt: command not found
Signed-off-by: Chris Patterson
We cleaned up the metadata so this can be enabled again.
Signed-off-by: Ross Burton
---
scripts/contrib/patchreview.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/contrib/patchreview.py b/scripts/contrib/patchreview.py
index
From: Khem Raj
packages like fontforge-native fail with mysterious errors like
| ../../git/inc/gwwiconv.h:44:21: error: conflicting types for ‘gww_iconv_close’
| #define iconv_close gww_iconv_close
| ^~~
| ../../git/inc/gwwiconv.h:37:13:
We cleaned up the metadata so this can be enabled again.
Signed-off-by: Ross Burton
---
scripts/contrib/patchreview.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/contrib/patchreview.py b/scripts/contrib/patchreview.py
index
* update to version 3.3
* Remove 0001-zeroconf-Include-fcntl.h.patch since it's
included in v3.3
* Add update-distcc-symlinks into FILES.
Signed-off-by: Jackie Huang
* Correct upstream SRC_URI and SRCREV to v3.3
* Correct default to fix starting distccd service
Signed-off-by: Ross Burton
---
...ig-3.0.12-Coverity-fix-issue-reported-for-SWIG_Python_FixMetho.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Signed-off-by: Ross Burton
---
.../gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipes-gnome/gtk+/gtk+/0001-Do-not-look-into-HOME-when-looking-for-gtk-modules.patch
On Fri, May 11, 2018 at 04:32:31PM +0200, Ricardo Ribalda Delgado wrote:
> When a wks makes reference to multiple rootfs, libspeudo data is not
> properly chossen. This results in filesystems with invalid UIDs for all
> the files.
>
> This can be tested with this .wks file:
> part / --source
Somehow, these patches are causing selftest to fail:
ERROR: Not supported fstype:
https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/1051/steps/Running%20oe-selftest/logs/stdio
Ross
On 4 May 2018 at 18:43, Otavio Salvador wrote:
> Add ontrack DM6 aux3
On 05/11/2018 01:39 PM, Peter Kjellerstedt wrote:
However, I gave this some more thought, and maybe it would be better to
let bitbake set the soft limit for max open files to, e.g., 1024. That
way we would not need to modify the code in rpm as it would adapt itself
automatically. I tried adding
When a wks makes reference to multiple rootfs, libspeudo data is not
properly chossen. This results in filesystems with invalid UIDs for all
the files.
This can be tested with this .wks file:
part / --source rootfs --fstype=ext4 --rootfs-dir=core-image-base
part /mnt/data1/ --fstype=ext4 --source
Hello
So this is what I have tried out:
I have downloaded master from openembedded-core
(f04e6bd144deb0c8fe2742f66b18904b6619a502)
then:
bitbake core-image-minimal core-image-base syslinux
Create a file test.wks
part / --source rootfs --fstype=ext4 --rootfs-dir=core-image-base
part /mnt/data1/
On 11 May 2018 at 00:52, Khem Raj wrote:
> Fixes installed-vs-shipped QA errors
>
> Reported-by: Dan McGregor
The email address I typically use in my git submissions is
dan.mcgre...@usask.ca. The gmail address is what I use only for
mailing lists.
From: André Draszik
This is similar to commit f76ee525a75d, but instead of disabling
the patch on all builds, we only remove it for x86-64 builds, as
the original change's commit message mentioned issues with this
patch applied on that architecture only.
Signed-off-by:
This repository is infrequently updated and doesn't really release, so just
watch for new commits.
Signed-off-by: Ross Burton
---
meta/recipes-core/musl/musl-utils.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/musl/musl-utils.bb
Whilst we're using a fork of the upstream repository, disable upstream checking.
Once we upgrade to 3.3 this can be removed.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/distcc/distcc_3.2.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> André Draszik
> Sent: den 11 maj 2018 10:10
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [pyro][PATCH 2/2] gcc:
> -Original Message-
> From: Alexander Kanavin [mailto:alexander.kana...@linux.intel.com]
> Sent: den 11 maj 2018 07:44
> To: Peter Kjellerstedt ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 2/2] rpm: Assume a max limit of 1024
If dbus-glib doesn't need --with-introspect-xml anymore then the dbus
recipe can stop installing it.
Ross
On 11 May 2018 at 03:20, Chen Qi wrote:
> The obsolete '--with-introspect-xml' option is removed.
>
> Signed-off-by: Chen Qi
> ---
>
From: André Draszik
This is similar to commit f76ee525a75d, but instead of disabling
the patch on all builds, we only remove it for x86-64 builds, as
the original change's commit message mentined issues with this
patch applied on that architecture only.
Signed-off-by:
From: André Draszik
This reverts commit f76ee525a75dd6e443743bf723ad4511707c7f49.
With the patch removed we otherwise get QEMU (mipsel) segfaults:
--- SIGSEGV {si_signo=SIGSEGV, si_code=1, si_addr = 0x000d4e40} ---
qemu: uncaught target signal 11 (Segmentation fault) -
Reported-by: Martin Jansa
Signed-off-by: Khem Raj
---
...format-truncation-warning-with-gcc-8.patch | 36 +++
.../recipes-core/libxcrypt/libxcrypt_4.0.0.bb | 4 ++-
2 files changed, 39 insertions(+), 1 deletion(-)
create mode 100644
packages like fontforge-native fail with mysterious errors like
| ../../git/inc/gwwiconv.h:44:21: error: conflicting types for ‘gww_iconv_close’
| #define iconv_close gww_iconv_close
| ^~~
| ../../git/inc/gwwiconv.h:37:13: note: previous declaration of
Fixes installed-vs-shipped QA errors
Reported-by: Dan McGregor
Signed-off-by: Khem Raj
---
meta/recipes-devtools/gcc/gcc-sanitizers.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/gcc/gcc-sanitizers.inc
From: Mingli Yu
Add the contract lib which implements contract
programming (a.k.a., Design by Contract or DbC) [1]
for the C++ programming language.
Signed-off-by: Mingli Yu
---
meta/recipes-support/boost/boost.inc | 1 +
1 file changed, 1
Please ignore this patch.
Thanks,
On 2018年05月11日 11:34, mingli...@windriver.com wrote:
From: Mingli Yu
Add the contract lib
Signed-off-by: Mingli Yu
---
meta/recipes-support/boost/boost.inc | 1 +
1 file changed, 1 insertion(+)
diff
61 matches
Mail list logo