1)Upgrade byacc from 20161202 to 20170201.
2)License checksum changed,since the copyright years were updated.
Signed-off-by: Huang Qiyu
---
.../recipes-extended/byacc/{byacc_20161202.bb => byacc_20170201.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-extende
== Series Details ==
Series: Allow postinst functions to be verbose
Revision: 1
URL : https://patchwork.openembedded.org/series/6370/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed
If BB_VERBOSE_LOGS is enabled, then make the postinst function use
set -x so that its execution is traced. This greatly simplifies
debugging, especially in case of failures as nothing is recorded in
the logs otherwise to indicate what caused the failure.
Signed-off-by: Peter Kjellerstedt
---
met
This enables tracing of the postinst functions created in base-passwd
and useradd.bbclass if BB_VERBOSE_LOGS is enabled. I found this
extremely useful during verification of the useradd functionality,
especially as there otherwise is absolutely nothing in the logs of why
a failure in a postinst fun
If BB_VERBOSE_LOGS is enabled, then make the postinst functions use
set -x so that their execution is traced. This greatly simplifies
debugging, especially in case of failures as nothing is recorded in
the logs otherwise to indicate what caused the failure.
Also reduce code duplication in useradd_
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Richard Purdie
> Sent: den 12 april 2017 20:34
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] base-passwd/use
Upgrade gdk-pixbuf from 2.36.5 to 2.36.6.
Signed-off-by: Huang Qiyu
---
.../gdk-pixbuf/{gdk-pixbuf_2.36.5.bb => gdk-pixbuf_2.36.6.bb}| 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
rename meta/recipes-gnome/gdk-pixbuf/{gdk-pixbuf_2.36.5.bb =>
gdk-pixbuf_2.36.6.bb} (96%)
dif
On 13 April 2017 at 06:12, Huang Qiyu wrote:
> -LIC_FILES_CHKSUM = "file://package/debian/copyright;md5=
> 74533d32ffd38bca4cbf1f1305f8bc60"
> +LIC_FILES_CHKSUM = "file://package/debian/copyright;md5=
> 9176bfb16dab43ebcb8e50d9ee9550b6"
>
Always explain why the license checksum needed changing.
On 13 April 2017 at 03:24, Wold, Saul wrote:
> I would like to advocate that this is similar to the kernel, there are
> new firmware packages available for new hardware and if we want to be
> supporting leading edge hardware, we need to have the latest versions
> of linux-firmware.
>
> This is wh
On 13 April 2017 at 08:42, Romain Perier
wrote:
> --- /dev/null
> +++ b/meta/recipes-extended/logrotate/logrotate/logrotate.service
> @@ -0,0 +1,10 @@
> +[Unit]
> +Description=Rotate log files
> +ConditionACPower=true
> +
> +[Service]
> +Type=oneshot
> +ExecStart=/usr/sbin/logrotate /etc/logrotat
Signed-off-by: Ross Burton
---
.../unzip/unzip/18-cve-2014-9913-unzip-buffer-overflow.patch| 2 +-
.../unzip/unzip/19-cve-2016-9844-zipinfo-buffer-overflow.patch | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
a/meta/recipes-extended/unzip/unzip/18-cve-2
On 13 April 2017 at 22:09, Andreas Müller
wrote:
> > base.bbclass doesn't test for .7z extensions, so won't detect this
> > dependency either.
> >
> Correct - but note that 7z extractor p7zip-native is not (yet) in oe-core.
>
There's plenty of prior for base.bbclass supporting extractors/fetcher
nativesdk builds now control the DISTRO_FEATURES (oe-core 731744) so this
workaround is no longer required.
This reverts commit 415b72ffcbd26e5f3664370d8b2a9b8105fb6342.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/dnf/dnf_git.bb | 6 --
1 file changed, 6 deletions(-)
diff --git a/
On Thu, Apr 13, 2017 at 10:58 PM, Andre McCurdy wrote:
> On Thu, Apr 13, 2017 at 1:34 PM, Andreas Müller
> wrote:
>> On Thu, Apr 13, 2017 at 5:57 PM, Burton, Ross wrote:
>>> On 13 April 2017 at 16:53, Andreas Müller
>>> wrote:
OK - but why do I see this error in do_unpack?
>>>
>>> Wha
On Thu, Apr 13, 2017 at 1:34 PM, Andreas Müller
wrote:
> On Thu, Apr 13, 2017 at 5:57 PM, Burton, Ross wrote:
>> On 13 April 2017 at 16:53, Andreas Müller
>> wrote:
>>>
>>> OK - but why do I see this error in do_unpack?
>>
>> What recipe and task?
>>
>> Ross
>>
> It is not that simple and it dri
On Thu, Apr 13, 2017 at 5:57 PM, Burton, Ross wrote:
>
> On 13 April 2017 at 16:53, Andreas Müller
> wrote:
>>
>> OK - but why do I see this error in do_unpack?
>
>
> What recipe and task?
>
> Ross
>
It is not that simple and it drives me mad (as usual :)
Failing recipes were [1-2]. They failed
Setting QB_DRIVE_TYPE=/dev/vd selects virtio without triggering any
warnings. Previously, that was only possible by setting an unknown
value and relying on the fallback to virtio, which caused some
warnings to be printed.
Signed-off-by: Patrick Ohly
---
scripts/runqemu | 15 +--
1 fi
== Number of issues - stats ==
{| class='wikitable'
!|Date !!colspan='3'|Failed tasks
!!colspan='6'|Failed depencencies!!|Signatures
!!colspan='14'|QA !!Comment
|-
|| ||qemuarm ||qemux86 ||qemux86_64
||q
On Thu, 2017-04-13 at 15:06 +0100, Burton, Ross wrote:
>
> On 13 April 2017 at 10:11, Rebecca Chang Swee Fun h...@intel.com> wrote:
> > +ARCHFILE ?= ""
> > +
> > +ARCHFILE_aarch64 = "file://objarch.h"
> > +
> > +ARCHFILE_arm = "file://objarch.h"
> > +
> > +ARCHFILE_armeb = "file://objarch.h"
> >
On Thu, Apr 13, 2017 at 9:22 AM, Felipe Ferreri Tonello <
e...@felipetonello.com> wrote:
> Hi Marc,
>
> On 10/04/17 20:02, Marc Ferland wrote:
> > Mostly fixes to BLE.
> >
> > Also in this commit:
> >
> > - Experimental tools are no longer experimental and are part of the
> > official tools.
> >
On 13 April 2017 at 16:53, Andreas Müller
wrote:
> OK - but why do I see this error in do_unpack?
>
What recipe and task?
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listin
On Thu, Apr 13, 2017 at 5:49 PM, Martin Jansa wrote:
> Some recipes like firefox depend on unzip even outside the do_unpack task:
> https://github.com/OSSystems/meta-browser/commit/1e9c2d21cd4757b8d2352c2ff5aa72f3409d59f9
> https://github.com/OSSystems/meta-browser/commit/bd2c39ddba00a3e0171e30ee4
Some recipes like firefox depend on unzip even outside the do_unpack task:
https://github.com/OSSystems/meta-browser/commit/1e9c2d21cd4757b8d2352c2ff5aa72f3409d59f9
https://github.com/OSSystems/meta-browser/commit/bd2c39ddba00a3e0171e30ee4a4585b56122990a
but I agree these cases should be fixed by
On Thu, Apr 13, 2017 at 8:44 AM, Andreas Müller <
schnitzelt...@googlemail.com> wrote:
> fixes do_unpack for *.zip-files:
>
> | /bin/sh: unzip: command not found
>
> Signed-off-by: Andreas Müller
> ---
> meta/conf/bitbake.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --gi
fixes do_unpack for *.zip-files:
| /bin/sh: unzip: command not found
Signed-off-by: Andreas Müller
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index af3937a..1ea0dea 100644
--- a/meta/conf/bitbake
On 13 April 2017 at 11:15, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> This runs against upstream recommendation and common distro practice. And
> it will break scripts that have not been ported to Python 3. Please fix the
> scripts instead to refer to python 3 whenever possibl
dnf requires a serparate repo for each architecture. This patch
writes one config file per PACKAGE_FEED_URIS entry with an entry
for each architecture, if any.
It also uses a space separated version of the repo id as the repo
name instead of just the id again.
Signed-off-by: Ian.Arkver
---
meta
ping
On 04/05/2017 09:09 AM, Fabio Berton wrote:
Volatiles files are installed in different locations depending on
distro feature update-rc.d or systemd. For update-rc.d volatiles
configuration files are installed in /etc/default/volatiles and
for systemd in /etc/tmpfiles.d/. So, we need to inst
ping
On 04/05/2017 09:09 AM, Fabio Berton wrote:
Volatiles files are installed in different locations depending on
distro feature update-rc.d or systemd. For update-rc.d volatiles
configuration files are installed in /etc/default/volatiles and
for systemd in /etc/tmpfiles.d/. So, we need to inst
On 12 April 2017 at 07:38, Martin Jansa wrote:
> I don't use meta-clang to check where does it install the llvm-config
> scripts if it's different location than what we have in meta-oe or not,
> but I assume khem was testing his mesa change with meta-clang's llvm.
>
Trevor, what layer were you g
On 13 April 2017 at 10:11, Rebecca Chang Swee Fun <
rebecca.swee.fun.ch...@intel.com> wrote:
> +ARCHFILE ?= ""
> +
> +ARCHFILE_aarch64 = "file://objarch.h"
> +
> +ARCHFILE_arm = "file://objarch.h"
> +
> +ARCHFILE_armeb = "file://objarch.h"
> +
> +ARCHFILE_i586 = "file://objarch.h"
> +
> +ARCHFILE_
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/gpgme/gpgme_1.8.0.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-support/gpgme/gpgme_1.8.0.bb
b/meta/recipes-support/gpgme/gpgme_1.8.0.bb
index cb9143aded8..4ddf6ed9996 100644
--- a/meta/recipes-support/gpgme/gpgme
Existing patch was actually doing the wrong thing and
sometimes removing a linking flag (-lgpgme) that should be present.
Instead, gpgme-config actually has internal logic to remove /usr/lib from the
output,
which works only in non-multilib setups, so it is adjusted to include all
possible
/usr/
Hi Marc,
On 10/04/17 20:02, Marc Ferland wrote:
> Mostly fixes to BLE.
>
> Also in this commit:
>
> - Experimental tools are no longer experimental and are part of the
> official tools.
> - Experimental was renamed to "testing" (hence the addition of the
> "testing" pacakge config option).
>
Hi Peter,
Oops, well spotted - have fixed the branch and sent a v2.
Thanks,
Paul
On Friday, 14 April 2017 12:35:29 AM NZST Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core-boun...@lists.openembedded.org
> > [mailto:openembedded-core-boun...@lists.openembedded.
This is a non-existent event - we already have the actual
bb.build.TaskSucceeded further down in the list hence why it wasn't
noticed earlier.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/standard.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/lib/devtool/standard.py b/scr
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of
> Paul Eggleton
> Sent: den 13 april 2017 14:28
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 3/3] devtool: ext
Since the existence of "command" in itself is not guaranteed, using it
to determine if other executables exist is moot. Instead just run the
executables and let the shell determine if they exist. By piping stderr
to /dev/null we avoid unnecessary warnings in case they do not exist.
Signed-off-by:
Since we apparently cannot rely on the command utility to always
exist, it is better to avoid using it in the profile script. Rather
than using command to detect if tty and resize exist (which obviously
will not work if command itself does not exist), just call them
directly while piping any output
Most of the other extract-based commands have this option but oddly I
left it out for modify - I guess because if I was debugging an issue here
I just used devtool extract to do so, but there's no reason why we can't
have it here and it is useful.
Signed-off-by: Paul Eggleton
---
scripts/lib/dev
The following changes since commit 334020a800434d20e7c3312890a2baca295c41c7:
oe-run-native: explicitly use bash (2017-04-13 10:52:54 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/devtool26
http://cgit.openembedded.org/openembedded
This is a non-existent event - we already have the actual
bb.build.TaskSucceeded further down in the list hence why it wasn't
noticed earlier.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/standard.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/lib/devtool/standard.py b/scr
If a task such as do_fetch fails when we're extracting source for a
recipe (within devtool modify / upgrade / extract / sync) then we should
naturally stop processing instead of blundering on; in order to do that
we need to be listening for the TaskFailed event. Thanks to Richard
Purdie for noticin
Since the existence of "command" in itself is not guaranteed, using it
to determine if other executables exist is mote. Instead just run the
executables and let the shell determine if they exist. By piping stderr
to /dev/null we avoid unnecessary warnings in case they do not exist.
Signed-off-by:
Since we apparently cannot rely on the command utility to always
exist, it is better to avoid using it in the profile script. Rather
than using command to detect if tty and resize exist (which obviously
will not work if command itself does not exist), just call them
directly while piping any output
On 04/13/2017 01:15 PM, Alexander Kanavin wrote:
On 04/13/2017 11:33 AM, Dmitry Rozhkov wrote:
If only python3 is installed on an image nothing provides
/usr/bin/python even though many scripts compatible with
both python2 and python3 just state `#!/usr/bin/env python`
in their shebang line.
Ma
On 04/13/2017 11:33 AM, Dmitry Rozhkov wrote:
If only python3 is installed on an image nothing provides
/usr/bin/python even though many scripts compatible with
both python2 and python3 just state `#!/usr/bin/env python`
in their shebang line.
Make python and python3 recipes provide alternatives
populate_sdk_ext sets TMPDIR to a known static value with '/tmp' directory
name and that name is hard coded in a few places (e.g., in
meta-environment-extsdk.bb that writes the eSDK environment variables).
Distros that do not reset TCLIBCAPPEND (poky does) end up getting
TMPDIR = /tmp-${TCLIBCAPPE
Fixed when len(TMPDIR) = 410:
aclocal: error: cannot open echo 'm4_define [snip]' configure.ac |: Argument
list too long'
This is becuase it has a lot of m4 files, use relative path for them
can fix the problem.
Signed-off-by: Robert Yang
---
meta/recipes-extended/grep/grep_3.0.bb | 3 +++
1 f
Use 'test -n "$POSIX_SHELL"' rather than 'test -x "$POSIX_SHELL"' so
that 'POSIX_SHELL = "/usr/bin/env sh"' can work.
Signed-off-by: Robert Yang
---
.../0001-config-libopts.m4-regenerate-it-from-config-libopts..patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/r
The following changes since commit e41c90b852167bbcb434da57b84280e855acae33:
busybox: In defconfig enable ASH_CMDCMD for built-in 'command' (2017-04-12
15:18:42 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/4fixes
http://cgit.opene
It should be -IOEINCDIR, not -I-IOEINCDIR.
Signed-off-by: Robert Yang
---
meta/classes/binconfig.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/binconfig.bbclass b/meta/classes/binconfig.bbclass
index 1be5fc4..39c3e2b 100644
--- a/meta/classes/binconfig.
It should be ${libdir} rather than /usr/lib, otherwise it would fail
when multilib:
MACHINE = "qemux86-64"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
$ bitbake apt
[snip]
install: target /path/to/apt/1.2.12-r0/image/usr/lib/apt is not a di
On Thu, 2017-04-13 at 16:59 +0800, Robert Yang wrote:
> Hi Patrick,
>
> On 04/13/2017 04:46 PM, Patrick Ohly wrote:
> > On Tue, 2017-04-11 at 02:21 -0700, Robert Yang wrote:
> >> Fixed when the image is large and not enough memory:
> >> grep: memory exhausted
> >> Aborted
> >>
> >> [YOCTO #110
From: "Chang, Rebecca Swee Fun"
The following warning occurs when building with meta-zephyr
with MACHINE set to arduino-101-sss:
WARNING:
/srv/sdc/builds/11319/meta/recipes-extended/ghostscript/ghostscript_9.20.bb:
Unable to get checksum for ghostscript SRC_URI entry objarch.h: file could not
Hi Patrick,
On 04/13/2017 04:46 PM, Patrick Ohly wrote:
On Tue, 2017-04-11 at 02:21 -0700, Robert Yang wrote:
Fixed when the image is large and not enough memory:
grep: memory exhausted
Aborted
[YOCTO #11073]
Signed-off-by: Robert Yang
---
meta/classes/qemuboot.bbclass | 3 +++
scripts
Hi Patrick,
On 04/13/2017 04:46 PM, Patrick Ohly wrote:
On Tue, 2017-04-11 at 02:21 -0700, Robert Yang wrote:
Fixed when the image is large and not enough memory:
grep: memory exhausted
Aborted
[YOCTO #11073]
Signed-off-by: Robert Yang
---
meta/classes/qemuboot.bbclass | 3 +++
scripts
On Tue, 2017-04-11 at 02:21 -0700, Robert Yang wrote:
> Fixed when the image is large and not enough memory:
> grep: memory exhausted
> Aborted
>
> [YOCTO #11073]
>
> Signed-off-by: Robert Yang
> ---
> meta/classes/qemuboot.bbclass | 3 +++
> scripts/runqemu | 19 +++-
If only python3 is installed on an image nothing provides
/usr/bin/python even though many scripts compatible with
both python2 and python3 just state `#!/usr/bin/env python`
in their shebang line.
Make python and python3 recipes provide alternatives for
/usr/bin/python and /usr/bin/python-config.
Currently, this recipe only supports daily scheduling via a cron job.
This commit adds support for systemd in the recipe, with the
corresponding services backported from upstream. When the distro feature
is enabled the systemd variant will be used. The timer granularity and
its accuracy are also co
On 13 April 2017 at 08:02, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> On 04/13/2017 05:19 AM, Zhixiong Chi wrote:
>
>> autoconf-archive is not in oe-core, is it?
>>>
>>>
>> Yes,it is.
>> As Alex said, it shouldn't depend the recipe from the other layers.
>> I will try to move
Am Donnerstag, den 13.04.2017, 08:53 +0200 schrieb Phil Wise:
> On 13.04.2017 08:34, Patrick Ohly wrote:
> > On Wed, 2017-04-12 at 13:47 +, thilo.ceston...@ts.fujitsu.com wrote:
> > > I want to build a tool which makes use of boost-program-options lib. As
> > > long as I compile for the target
62 matches
Mail list logo
