== Series Details ==
Series: libnl: 3.2.29 -> 3.4.0 (rev4)
Revision: 4
URL : https://patchwork.openembedded.org/series/9397/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the pr
1) Upgrade libnl from 3.2.29 to 3.4.0.
2) Add one patch "0001-PATCH-fix-libnl-3.4.0-musl-compile-problem.patch", for
musl compile.
3) Delete one patch "fix-pktloc_syntax_h-race.patch", since upstream has
refactored the makefiles, and the problematic code is now absent.
Signed-off-by: Huang Qiyu
Add needed patches for portability across glibc/musl
enable systemd on musl too
Disable utmp,ldconfig,nss,resolved,localed for musl
which is not supported on musl
Signed-off-by: Khem Raj
---
...PATH_WTMPX-and-_PATH_UTMPX-if-not-defined.patch | 43 ++
...llback-parse_printf_format-implementatio
Signed-off-by: Fan Xin
---
.../coreutils/{coreutils_8.27.bb => coreutils_8.28.bb}| 8
1 file changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-core/coreutils/{coreutils_8.27.bb => coreutils_8.28.bb}
(95%)
diff --git a/meta/recipes-core/coreutils/coreutils_8.27.b
1. Update the md5sum and sha256sum for curl 7.56.1
2. Delete the following patchs which have been applied in curl 7.56.1
CVE-2017-199.patch
CVE-2017-1000100.patch
CVE-2017-1000101.patch
3. Delete the do_install_append() due to the curl/curlbuild.h have been removed.
Sig
On Thu, Oct 26, 2017 at 1:51 PM, Slater, Joseph
wrote:
> I think values for the BACKFILL_CONSIDERED can be used, but only if they are
> literals. I don't think any variable expansion occurs when getVar() is used
> at the point of backfilling.
Maybe the assumption is that MACHINE_FEATURES_BACKF
I think values for the BACKFILL_CONSIDERED can be used, but only if they are
literals. I don't think any variable expansion occurs when getVar() is used at
the point of backfilling. I think the a better way of setting MACHINE or
DISTRO_FEATURES would be to directly append/remove using overrid
From: Leonardo Sandoval
All CVE patches and the glibc one removed because these are already integrated
into 2.10.1.
Signed-off-by: Leonardo Sandoval
---
v2: removed the glibc-2.25.patch, already into 2.10.1. At v1, I hit [YOCTO
#10450]
where devtool upgrade complain in just one hunk, even
On Thu, Oct 26, 2017 at 1:44 PM, Anibal Limón
wrote:
Hi Leo,
The patch looks good at first glance, i have some comments,
- We need a way to handle the results output because with this you
will have N results files, may be extend the shell script
to consolidate the results file.
As a pro
Hi Leo,
The patch looks good at first glance, i have some comments,
- We need a way to handle the results output because with this you will
have N results files, may be extend the shell script
to consolidate the results file.
- With this if one selftest depends on other there is no way to now it
On Thu, Oct 26, 2017 at 10:15 AM, Slater, Joseph
wrote:
> Okay, I don't know why, but at the time of backfilling the CONSIDERED list is
> empty! This is not true if I use "=" to set it unconditionally in
> arch-mips.inc, but it IS true if I try to set it via anything involving an
> override (i
I believe the patchtest complain is valid, some brief explanation
should be given.
But the way it is present need some improvement. We should not be
listing all licenses, just the ones that change.
Leo
On Thu, Oct 26, 2017 at 11:32 AM, Patchwork
wrote:
== Series Details ==
Series: linu
From: Leonardo Sandoval
The below is a profiling experiment, running oe-selftest -r (the proposed
implementation, see patch description for more info):
Procedure:
With patch 1/1, multiple oe-selftest jobs can be launched in
parallel. One tool that launch jobs in parallel is GNU Parallel [1], al
From: Leonardo Sandoval
The main idea is to isolate the oe-selftest execution so neither the current
build dir nor the configuration data is touch/polluted. This approach uses
a wrapper script (which is the one presented on this commit) which creates
a unique directory and inside it does a shallo
Okay, I don't know why, but at the time of backfilling the CONSIDERED list is
empty! This is not true if I use "=" to set it unconditionally in
arch-mips.inc, but it IS true if I try to set it via anything involving an
override (including append).
Isn't getVar() supposed to expand the variable
== Series Details ==
Series: linux-firmware: Bump to bf04291 revision
Revision: 1
URL : https://patchwork.openembedded.org/series/9498/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been execute
This includes following changes:
bf04291 WHENCE: Add new qed firmware
d8fc990 WHENCE: Add new radeon firmware
7245319 WHENCE: Fix syntax error for iwlwifi-8265-31.ucode entry
18d71a8 Revert "ath10k: QCA988X hw2.0: update firmware to 10.2.4.70.63-2"
4ebfab3 ath10k: QCA6174 hw3.0: update board-2.bin
On Thu, 2017-10-26 at 09:37 -0500, Leonardo Sandoval wrote:
> I used devtool upgrade and the only hunk I need to remove was
> thisone, the rest were applied cleanly.
The rest was applied *silently*, but not *cleanly*. The lesson here is
basically that developers shouldn't blindly trust the tools.
Hi Patrick
On Thu, Oct 26, 2017 at 4:33 AM, Patrick Ohly
wrote:
On Thu, 2017-10-19 at 13:10 -0700,
leonardo.sandoval.gonza...@linux.intel.com wrote:
From: Leonardo Sandoval
All CVE patches removed because these are already integrated in
2.10.1.
...
meta/recipes-devtools/qemu/qemu/gli
Bump version to 2.14.3 in order to eliminate CVE-2017-14867 vulnerability.
Reference:
https://nvd.nist.gov/vuln/detail/CVE-2017-14867
Upstream patches:
https://github.com/git/git/commit/9a42c03cb71eaa9d41ba67275de38c997a791c32
https://github.com/git/git/commit/fce13af5d20cad8dcb2d0e47bcf01b6960f0
On Wed, Oct 25, 2017 at 05:57:16AM -0700, Armin Kuster wrote:
> LICENSE changed to to rewording
"due to"
> https://github.com/eggert/tz/commit/7097a652778d35acf747d14f8bf7b3ced479bbc0#diff-9879d6db96fd29134fc802214163b95a
>
> Briefly:
> Northern Cyprus switches from +03 to +02/+03 on 2017-10
On Thu, Oct 26, 2017 at 08:25:00AM -0400, Denys Dmytriyenko wrote:
> On Tue, Oct 24, 2017 at 06:37:17PM +, Lee, Yong wrote:
> > Thank you.
> > I switched to internal toolchain and building GCC 5.4 (included in meta) is
> > complete and is onto glibc.
> >
> > In summary, TI SDK appears to be b
On Tue, Oct 24, 2017 at 06:37:17PM +, Lee, Yong wrote:
> Thank you.
> I switched to internal toolchain and building GCC 5.4 (included in meta) is
> complete and is onto glibc.
>
> In summary, TI SDK appears to be broken as the none-default GCC version
> included in their package (ie. Linaro
On 10/26/2017 12:33 PM, Patrick Ohly wrote:> The patch is already
present in the upstream 2.10.0. Patching during a> build succeeds
by adding the same hunks again to configure (which> seems to cause
no problems during build) and skipping the one which it> detects as
already
Hi Thomas,
On Wed, 2017-10-25 at 20:03 +0200, Thomas Perrot wrote:
> Avoid a circular dependency between do_concat_dtb and do_assemble_fitimage
> when UBOOT_SIGN_ENABLE is active:
>
> Dependency loop #1 found:
> do_concat_dtb (dependent Tasks ['linux-
> yocto_4.10.bb:do_assemble_fitimage'])
>
Hi Thomas,
On Wed, 2017-10-25 at 20:03 +0200, Thomas Perrot wrote:
> Ignore fitImage type in do_bundle_initramfs task because the packaging is
> made by do_assemble_fitimage_initramfs
You should also follow the instructions from the patchtest email you're
receiving
http://lists.openembedded.org/p
On Thu, 2017-10-19 at 13:10 -0700,
leonardo.sandoval.gonza...@linux.intel.com wrote:
> From: Leonardo Sandoval
>
> All CVE patches removed because these are already integrated in
> 2.10.1.
...
> meta/recipes-devtools/qemu/qemu/glibc-2.25.patch | 14 -
diff --git a/meta/recipes-devtools/qemu/qe
On 10/26/2017 10:55 AM, Ovidiu Panait wrote:
Bump version to 2.13.6 in order to eliminate CVE-2017-14867 vulnerability.
The latest version is 2.14.3, can you update to that please?
Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.op
On 10/26/2017 10:04 AM, Huang, Qiyu wrote:
Well, from the new Makefile.am file,I can't find the related content about this
patch.
And in the fix-pktloc_syntax_h-race.patch, the description is like this:
libnl has progressed to 0.3.2 and there does not appear to be any "make -j"
issues with thi
On Tue, 2017-10-17 at 18:59 -0400, Denys Dmytriyenko wrote:
> On Tue, Oct 17, 2017 at 08:31:10AM -0200, Otavio Salvador wrote:
> > Em 17 de out de 2017 6:21 AM, "Fabien Lahoudere" <
> > fabien.lahoud...@collabora.co.uk> escreveu:
> >
> > On Mon, 2017-10-16 at 21:34 +0100, Burton, Ross wrote:
> >
Bump version to 2.13.6 in order to eliminate CVE-2017-14867 vulnerability.
Reference:
https://nvd.nist.gov/vuln/detail/CVE-2017-14867
Upstream patches:
https://github.com/git/git/commit/9a42c03cb71eaa9d41ba67275de38c997a791c32
https://github.com/git/git/commit/fce13af5d20cad8dcb2d0e47bcf01b6960f0
Well, from the new Makefile.am file,I can't find the related content about this
patch.
And in the fix-pktloc_syntax_h-race.patch, the description is like this:
libnl has progressed to 0.3.2 and there does not appear to be any "make -j"
issues with this build after my limited testing on that newe
32 matches
Mail list logo