Hello Khem Raj,
We have tested the applicability for this patch on master as well and as per
analysis it is applicable.
I've sent the same patch for master branch as well in a separate mail.
Thanks & Regards,
Saloni
From: Khem Raj
Sent: Wednesday, January 15,
If gnu hash is enabled for mips then we can not use gold linker since
gnu hash handling is only supported with good old BFD linker alone
Fixes
.gnu.hash is incompatible with the MIPS ABI
See gold/mips.cc in binutils for reference
Signed-off-by: Khem Raj
---
Clang detects that getcwd is being re-declared and signatures don't
match, simple solution is to let clang use overloadable attribute
Signed-off-by: Khem Raj
---
.../gettext/gettext-0.20.1/overloadable.patch | 22 +++
meta/recipes-core/gettext/gettext_0.20.1.bb | 1 +
2 files
On Wed, Jan 8, 2020 at 5:45 PM Richard Purdie
wrote:
>
> On Wed, 2020-01-08 at 12:14 +0900, Masahiro Yamada wrote:
> > So, the concept of "recursive dependency" sounds
> > somewhat odd to me.
> >
> > I guess I am missing important use-cases.
> > I'd like to know the reason why we need
> I've gone back and forth and re-implemented the code to do so a half dozen
> times. Chronologically, these are the fundamental
> strategies I've attempted:
>
> 1. Simply in terms of buildhistory-collect-srcrevs.
> Pros: dead simple
> Cons: requires that you actually build stuff
vim-tiny: update from 8.1.1518 to 8.2
The date in the license was updated to 2020 and
a trailing space was removed from one line.
Signed-off-by: Oleg Polyakov
---
.../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.bb} | 0
meta/recipes-support/vim/vim.inc | 4
On Wed, Jan 15, 2020 at 1:36 PM Bruce Ashfield wrote:
>
> I already have an entire queue in development for this.
>
> So hold onto this series. I'll publish my branch later this week, or early
> next.
Actually, I'll see how it stacks on top of my changes and send a
unified branch to try out.
I already have an entire queue in development for this.
So hold onto this series. I'll publish my branch later this week, or early next.
Bruce
On Wed, Jan 15, 2020 at 1:08 PM Paul Barker wrote:
>
> Patch 1 allows the kernel-yocto bbclass to be inherited directly in a recipe
> without needing
On Tue, 14 Jan 2020 at 19:37, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
>
> The autobuilder failed with this again, I went in and the first bit of
> debugging I added was to say which file its failing on. Answer was:
>
> WARNING: python3-3.8.1-r0 do_package:
>
This allows the kernel-yocto bbclass to be inherited in a recipe without
needing to include linux-yocto.inc. The bbclass should stand on its own
and linux-yocto.inc does a few things which may not be desired in other
kernel recipes (such as modifying KERNEL_FEATURES).
The LINUX_VERSION_EXTENSION
The machine_branch and machine_srcrev variables were set but not used in
do_kernel_metadata.
Signed-off-by: Paul Barker
---
meta/classes/kernel-yocto.bbclass | 7 ---
1 file changed, 7 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass
b/meta/classes/kernel-yocto.bbclass
index
CONFIG_LOCALVERSION may already be set in a defconfig or config fragment
and this should not be unconditionally overridden.
Signed-off-by: Paul Barker
---
meta/classes/kernel-yocto.bbclass | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Patch 1 allows the kernel-yocto bbclass to be inherited directly in a recipe
without needing to use linux-yocto.inc. I can then use kconfig fragments in
my kernel recipe without pulling in the whole of linux-yocto.inc (which
includes some things I don't want like KERNEL_FEATURES changes and the
Thanks, we are almost there :) Please set the version in the filename to
8.2 (not 8.2.0) so that 'devtool latest-version vim' prints a matching
result, and 'devtool check-upgrade-status vim' prints nothing.
Alex
On Wed, 15 Jan 2020 at 18:59, Oleg Polyakov
wrote:
> vim-tiny: update from
vim-tiny: update from 8.1.1518 to 8.2.0
The date in the license was updated to 2020 and
a trailing space was removed from one line.
Signed-off-by: Oleg Polyakov
---
.../vim/{vim-tiny_8.1.1518.bb => vim-tiny_8.2.0.bb} | 0
meta/recipes-support/vim/vim.inc |
A new yearly snapshot was taken on January 2nd of 2020, this bumps
newlib to 3.2.0.
- Mentor Graphics added tcl license (amdgcn-* targets)
- BSD-Clause-2 was added as well by Dinux (pru-* targets)
Signed-off-by: Alejandro Enedino Hernandez Samaniego
---
.../newlib/{libgloss_3.1.0.bb =>
On Wed, Jan 15, 2020 at 7:51 AM Saloni Jain wrote:
>
> From: Sana Kazi
>
> Added patch for CVE-2019-12900 as backport from upstream.
> Fixes out of bound access discovered while fuzzying karchive.
>
is this fix already present in the bzip2 version we have in master ?
> Tested by:
On 15/01/2020 15:47, Saloni Jain wrote:
From: Sana Kazi
Added patch for CVE-2019-12900 as backport from upstream.
Fixes out of bound access discovered while fuzzying karchive.
Tested by: sana.k...@kpit.com
Signed-off-by: Saloni Jain
Need a S-o-b in the patch itself alongside a CVE tag,
In case of multilib, the do_package fails with:
ERROR: libubootenv-0.2-r0 do_package: QA Issue: libubootenv: Files/directories
were installed but not shipped in any package:
/usr/lib/libubootenv.so
/usr/lib/libubootenv.so.0.2
Issue is fixed in libubootenv repo - this patch updates SRCREV to
== Series Details ==
Series: bzip2: Fix CVE-2019-12900 (rev6)
Revision: 6
URL : https://patchwork.openembedded.org/series/18434/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
== Series Details ==
Series: bzip2: Fix CVE-2019-12900 (rev5)
Revision: 5
URL : https://patchwork.openembedded.org/series/18434/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
== Series Details ==
Series: bzip2: Fix CVE-2019-12900 (rev4)
Revision: 4
URL : https://patchwork.openembedded.org/series/18434/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
From: Sana Kazi
Added patch for CVE-2019-12900 as backport from upstream.
Fixes out of bound access discovered while fuzzying karchive.
Tested by: sana.k...@kpit.com
Signed-off-by: Saloni Jain
---
.../bzip2/bzip2-1.0.6/CVE-2019-12900.patch | 34 ++
1 file changed,
From: Sana Kazi
Added patch for CVE-2019-12900 as backport from upstream.
Fixes out of bound access discovered while fuzzying karchive.
Tested by: sana.k...@kpit.com
Signed-off-by: Saloni Jain
---
.../bzip2/bzip2-1.0.6/CVE-2019-12900.patch | 34 ++
From: Sana Kazi
Added patch for CVE-2019-12900 as backport from upstream.
Fixes out of bound access discovered while fuzzying karchive.
Tested by: sana.k...@kpit.com
Signed-off-by: Saloni Jain
---
.../bzip2/bzip2-1.0.6/CVE-2019-12900.patch | 34 ++
1 file changed,
Drop the i686 build fix, this is integrated upstream now.
Signed-off-by: Ross Burton
---
.../01_Fix-build-on-i686.patch| 55 ---
.../xorg-driver/xf86-video-intel_git.bb | 7 +--
2 files changed, 2 insertions(+), 60 deletions(-)
delete mode 100644
On Wed, 15 Jan 2020 at 13:05, Ricardo Ribalda Delgado
wrote:
>
> Hello
>
> I am trying to figure out the best way to achieve this. I have a
> system with a host and a target. The target netboots form the host and
> have a different package architecture.
>
> Usually I was solving this with one
On Tue, 2020-01-14 at 14:59 +0100, Alexander Kanavin wrote:
> Drop backports, rebase other patches.
>
> 0001-main.c-if-OEPYTHON3HOME-is-set-use-instead-of-PYTHON.patch
> is removed as the use case (allowing python 2 and 3 to coexist
> in SDKs) is no longer relevant with Python 2.x reaching end of
On 15/01/2020 01:25, Maxime Roussin-Bélanger wrote:
I have modified the recipe to use manpages, but it is impossible to run
a build from master, because
of my python3 pyenv setup. I had to add
+DEPENDS = "python3-native"
to ca-certificates, without it was impossible to go through the
Hello
I am trying to figure out the best way to achieve this. I have a
system with a host and a target. The target netboots form the host and
have a different package architecture.
Usually I was solving this with one partition per image/machine,
combined using a .wks file like:
part /export
On Tue, 2020-01-14 at 10:12 +0100, Martin Jansa wrote:
> * otherwise PKGR seen in do_install, do_deploy and do_deploy_links
> will
> have different value in each of them (PRSERV will return different
> value of EXTENDPRAUTO because TASKHASH is different for each of
> these
> tasks and also
On Tue, 2020-01-14 at 10:12 +0100, Martin Jansa wrote:
> The following changes since commit
> b6d4150f9c74f25a4022a3fa0bd489a8e85deb77:
>
> gettext: fix typo in Upstream-Status (2020-01-13 13:07:32 +)
>
> are available in the Git repository at:
>
>
I don't know: I am not seeing the issue locally, and it doesn't happen on
the autobuilder, so it's difficult to give a useful answer.
Alex
On Wed, 15 Jan 2020 at 02:26, Maxime Roussin-Bélanger <
maxime.roussinbelan...@gmail.com> wrote:
> I have modified the recipe to use manpages, but it is
On Tue, 14 Jan 2020 at 23:37, Randy MacLeod
wrote:
> That's also what 'devtool latest-version vim' should currently report and
> 'devtool upgrade' upgrade to: I purposely cut off the point releases and
> left only the major.minor part there.
>
> Right. This will also give Oleg an excuse to try
34 matches
Mail list logo
