Re: [OE-core] [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin

2017-08-08 Thread Andre McCurdy
On Tue, Aug 8, 2017 at 11:55 AM, Mark Hatle  wrote:
> On 8/8/17 12:35 PM, Alexander Kanavin wrote:
>> On 08/08/2017 06:58 PM, Mark Hatle wrote:
>>> Can we somehow make openssl(10) or nettle a choice when compiling?
>>>
>>> I ask because I've worked on a few systems where people seem to want one
>>> encryption engine for as much of the system as possible (usually openssl).
>>> While gstreamer has not been a problem in such systems, I could see it being
>>> something that would need to be considered.
>>
>> This would need to be done across all recipes where such choice is
>> supported, as a 'preferred crypto engine' distro feature. There's been
>> talk of doing this, but I don't remember what was the outcome.
>>
>> Also, the plugin needs to be ported to 1.1 first, as the choice will
>> otherwise be taken away when 1.0 goes EOL.
>
> For now I'm fine with 1.0 support.  So something like:
>
> # ensure OpenSSL is used for HLS AES description instead of nettle
> # (OpenSSL is a shared dependency with dtls)
> PACKAGECONFIG[hls_openssl10] = "--enable-hls
> --with-hls-crypto=openssl,--disable-hls,openssl10"
>
> PACKAGECONFIG[hls] = "--enable-hls
> --with-hls-crypto=nettle,--disable-hls,nettle"
>
> But my concern is changing the choice of encryption engine could break various
> existing uses.  (Like I said, -I- don't have that use, but I expect others 
> do..
> perhaps not with gstreamer-plugins-bad though?)

I looked at the gstreamer code briefly and the crypto dependency seems
fairly trivial (basically just AES decryption) so switching between
openssl and nettle doesn't look like it's going to be a big risk (even
for users obliged to avoid the LGPLv3 version of nettle in oe-core).

For reference, the problem with openssl 1.1 seems to be that gstreamer
embeds an openssl EVP_CIPHER_CTX struct directly within the
GstHLSDemuxStream struct, but openssl 1.1 requires that such structs
are now allocated and freed dynamically:

  https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes
  
https://cgit.freedesktop.org/gstreamer/gst-plugins-bad/tree/ext/hls/gsthlsdemux.h#n84

>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v5] kernel: Add support for multiple kernel packages

2017-08-08 Thread Wold, Saul
On Tue, 2017-08-08 at 10:30 -0500, Haris Okanovic wrote:
> Some distros may want to provide alternate kernel "flavors" via feeds
> or
> within bootable images. For example, readily available builds which
> provide certain diagnostic features can enable developers and testers
> to
> more quickly resolve issues by avoiding lengthy kernel builds.
> 
> This change allows for building multiple flavors of the kernel and
> module packages by templatizing kernel package names via a new
> KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to the
> old
> name of "kernel", but can be overridden by certain recipes providing
> alternate kernel flavors.
> 
> To maintain compatibility, recipes providing alternate kernel flavors
> cannot be the "preferred provider" for virtual/kernel. This is
> because
> OE puts the preferred provider's build and source at
> "tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
> "tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
> "tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes using
> the
> default KERNEL_PACKAGE_NAME="kernel" follows the old semantics --
> build
> in the old location and may be preferred provider -- while recipes
> using
> all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and
> don't
> provide "virtual/kernel".
> 
> Testing:
>  1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
> linux-yocto-tiny_4.9.bb so that it may build alongside
> the main kernel.
>  2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel
> flavors.
>  3. Verified image and modules IPKs exist for both:
> tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
> tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-tiny
>  4. Verified linux-yocto is the "preferred provider", and was built
> in
> shared directory: tmp-glibc/work-shared/qemux86/kernel-*
>  5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
> core-image-base.bb to include both kernel flavors.
>  6. `bitbake core-image-base` to build an image.
>  7. Verified image contains two bzImage's under /boot/, with
> "yocto-standard" selected to boot via symlink.
> 
Thank you for continuing to work on this.  I did a simple test of
building a single kernel and lttng-modules without your change and then
added this patch and tried lttng-modules with no additional changes to
my local.conf, just regular single kernel workflow.

I got the following issue:

ERROR: lttng-modules-2.9.3-r0 do_package: Error executing a python
function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure
was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:split_kernel_module_packages(d)
 0003:
File: '/srv/sdb/releases/master/meta/classes/kernel-module-
split.bbclass', lineno: 139, function: split_kernel_module_packages
 0135:module_regex = '^(.*)\.k?o$'
 0136:
 0137:module_pattern_prefix =
d.getVar('KERNEL_MODULE_PACKAGE_PREFIX')
 0138:module_pattern_suffix =
d.getVar('KERNEL_MODULE_PACKAGE_SUFFIX')
 *** 0139:module_pattern = module_pattern_prefix +
kernel_package_name + '-module-%s' + module_pattern_suffix
 0140:
 0141:postinst = d.getVar('pkg_postinst_modules')
 0142:postrm = d.getVar('pkg_postrm_modules')
 0143:
Exception: TypeError: Can't convert 'NoneType' object to str implicitly

ERROR: lttng-modules-2.9.3-r0 do_package: Function failed:
split_kernel_module_packages
ERROR: Logfile of failure stored in:
/srv/sdb/releases/master/builds/corei7/tmp/work/genericx86_64-poky-
linux/lttng-modules/2.9.3-r0/temp/log.do_package.80115
NOTE: recipe lttng-modules-2.9.3-r0: task do_package: Failed

I believe the problem is that I tried to build lttng-modules standalone
and so the kernel.bbclass does not get involved to set the
KERNEL_PACKAGE_NAME default.

I see that your procedure above works for.

Thanks again for your work, sorry I am finding interesting issues
still.

Sau!


> Discussion thread:
> http://lists.openembedded.org/pipermail/openembedded-core/2015-Decemb
> er/thread.html#114122
> 
> Signed-off-by: Ioan-Adrian Ratiu 
> Signed-off-by: Gratian Crisan 
> Signed-off-by: Haris Okanovic 
> Coauthored-by: Gratian Crisan 
> Coauthored-by: Haris Okanovic 
> Coauthored-by: Josh Hernstrom 
> ---
> [PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR to
> the
> "work" directory in alternate kernel builds, instead of "work-
> shared",
> so
> that the two builds don't clobber each other.
> 
> [PATCH v3] An updated version of this change rebased onto the current
> OE-core master. Changes:
>  - Remove PREFERRED_PROVIDER check in linux-yocto.inc in alternate
>    kernel builds, since alternate kernels aren't the
>    PREFERRED_PROVIDER for virtual/kernel by definition.
>  - Remove 

Re: [OE-core] [oe-core][PATCH 1/1] php: move to version 7.1.8

2017-08-08 Thread Khem Raj
On Tue, Aug 8, 2017 at 1:40 PM, Slater, Joseph  wrote:
> I’ll look at the CVEs.  LICENSE updated from 2016 to 2017.  Text is the
> same.Joe

I have posted an upgrade to 7.1.7 which addresses some of concerns
raised here plus build
fixes when compiling with clang.

https://patchwork.openembedded.org/series/8131/#

>
>
>
> From: Martin Jansa [mailto:martin.ja...@gmail.com]
> Sent: Tuesday, August 08, 2017 1:31 PM
> To: Leonardo Sandoval
> Cc: Slater, Joseph; Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [oe-core][PATCH 1/1] php: move to version 7.1.8
>
>
>
> And wrong ML
>
>
>
> On Tue, Aug 8, 2017 at 9:37 PM, Leonardo Sandoval
>  wrote:
>
> On Tue, 2017-08-08 at 13:16 -0700, Joe Slater wrote:
>> Fixes many CVEs.
>
> would be a plus if you list those.
>
> why LIC_FILES_CHKSUM changed?
>
> Leo
>
>
>>
>> Signed-off-by: Joe Slater 
>> ---
>>  .../{php-7.1.0 => php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch | 0
>>  meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb} | 6
>> +++---
>>  2 files changed, 3 insertions(+), 3 deletions(-)
>>  rename meta-oe/recipes-devtools/php/{php-7.1.0 =>
>> php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch (100%)
>>  rename meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb} (64%)
>>
>> diff --git
>> a/meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
>> b/meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
>> similarity index 100%
>> rename from
>> meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
>> rename to
>> meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
>> diff --git a/meta-oe/recipes-devtools/php/php_7.1.0.bb
>> b/meta-oe/recipes-devtools/php/php_7.1.8.bb
>> similarity index 64%
>> rename from meta-oe/recipes-devtools/php/php_7.1.0.bb
>> rename to meta-oe/recipes-devtools/php/php_7.1.8.bb
>> index 210d91f..c0b2541 100644
>> --- a/meta-oe/recipes-devtools/php/php_7.1.0.bb
>> +++ b/meta-oe/recipes-devtools/php/php_7.1.8.bb
>> @@ -1,10 +1,10 @@
>>  require php.inc
>>
>> -LIC_FILES_CHKSUM = "file://LICENSE;md5=b602636d46a61c0ac0432bbf5c078fe4"
>> +LIC_FILES_CHKSUM = "file://LICENSE;md5=c0af599f66d0461c5837c695fcbc5c1e"
>>
>>  SRC_URI += "file://change-AC_TRY_RUN-to-AC_TRY_LINK.patch"
>> -SRC_URI[md5sum] = "54e364b60a88db77adb96aacb10f10a4"
>> -SRC_URI[sha256sum] =
>> "68bcfd7deed5b3474d81dec9f74d122058327e2bed0ac25bbc9ec70995228e61"
>> +SRC_URI[md5sum] = "d22451dc20bbdf4b8bb656dc787c2a36"
>> +SRC_URI[sha256sum] =
>> "7064a00a9450565190890c7a4be04e646e0be73b2e0f8c46ae34419f343ca2f8"
>>
>>  PACKAGECONFIG[mysql] =
>> "--with-mysqli=${STAGING_BINDIR_CROSS}/mysql_config \
>>
>> --with-pdo-mysql=${STAGING_BINDIR_CROSS}/mysql_config \
>> --
>> 2.7.4
>>
>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] libinput: Upgrade 1.7.3 -> 1.8.1

2017-08-08 Thread Richard Purdie
On Mon, 2017-08-07 at 15:09 +0300, Jussi Kukkonen wrote:
> New feature release, see
> https://lists.freedesktop.org/archives/wayland-devel/2017-June/034286
> .html
> for the major features. This is the last major release to support
> autotools.
> 
> Configure flag "--enable-event-gui" changed name.
> 
> Configure flags no longer default to "auto": explicitly disable the
> things that were previously automatically disabled.
> 
> Package the binaries into libinput-bin while being careful with
> packaging as the main package gets renamed to libinput10.
> 
> Signed-off-by: Jussi Kukkonen 

Looks like there is a race somewhere in the new version:

https://autobuilder.yocto.io/builders/nightly-wic/builds/411/steps/BuildImages_1/logs/stdio

Cheers,

Richard
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v3] externalsrc: Handle .git not being a directory

2017-08-08 Thread Joshua Watt
On Tue, 2017-08-08 at 14:46 -0500, Leonardo Sandoval wrote:
> On Tue, 2017-08-08 at 20:32 +0100, Burton, Ross wrote:
> > On 8 August 2017 at 02:46, Joshua Watt 
> > wrote:
> > +git_dir = subprocess.check_output(['git',
> > 'rev-parse', '--absolute-git-dir'],
> > cwd=s_dir).decode("utf-8").rstrip()
> > 
> > 
> > Doesn't work with my old git:
> > 
> > 
> > bb.data_smart.ExpansionError: Failure expanding variable
> > do_compile[file-checksums], expression was ${@srctree_hash_files(d)
> > }
> > which triggered exception FileNotFoundError: [Errno 2] No such file
> > or
> > directory: '--absolute-git-dir/index'
> > Summary: There was 1 ERROR message shown, returning a non-zero exit
> > code.
> > 
> > 
> > 
> > $ git rev-parse --absolute-git-dir
> > --absolute-git-dir
> > $ git --version
> > git version 2.11.0
> > 
> 
> I also tried it and got same log. my git is a bit newer (2.12.3).

Ok. I wasn't sure exactly when that option was added, I'll use the
older one.

> 
> Leo
> > 
> > Ross
> > -- 
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> 

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin

2017-08-08 Thread Mark Hatle
On 8/8/17 2:14 PM, Burton, Ross wrote:
> On 8 August 2017 at 18:35, Alexander Kanavin 
>  > wrote:
> 
> On 08/08/2017 06:58 PM, Mark Hatle wrote:
> 
> Can we somehow make openssl(10) or nettle a choice when compiling?
> 
> I ask because I've worked on a few systems where people seem to want 
> one
> encryption engine for as much of the system as possible (usually 
> openssl).
> While gstreamer has not been a problem in such systems, I could see 
> it being
> something that would need to be considered.
> 
> 
> This would need to be done across all recipes where such choice is
> supported, as a 'preferred crypto engine' distro feature. There's been 
> talk
> of doing this, but I don't remember what was the outcome.
> 
> 
> There was a bug for this but I literally closed it earlier today on the 
> grounds
> that it would mean patching every user of a crypto library to add an 
> abstraction
> and alternative codepaths.  If you don't patch every instance then there is no
> point in a global option.

Getting a bit off-topic here, but...

I do expect that at some point in the future someone will come along and offer a
distribution wide setting for preferred (and alternative) encryption and make
the associated changes to the various recipes to enforce this.

Many of the systems I am working with are starting to have those types of needs.
 A preferred encryption resource that everything that can - should use.  Along
with alternatives that are 'acceptable' if the primary isn't available.
Otherwise other encryption would be prohibited and should trigger an automatic
blacklist or failure.

(In this case, there is a lot of work to be done, and potentially any encryption
user/provider [even internal] needs to be audited.  This is not an 'over night'
process... thus I doubt you'll be seeing it tomorrow from anyone here.)

So don't necessarily dismiss the idea -- but I do think it's outside of the
immediate scope for the Yocto Project itself, but I would expect something to
eventually be presented by a member of the larger OpenEmbedded community.

--Mark

> We can have packageconfigs, and expose the choice if the upstream does, but I
> think the only sane option is to leave it to the user to set the options.  
> It's
> trivial enough to blacklist openssl if you never want to use it.
> 
> Ross

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [oe-core][PATCH 1/1] php: move to version 7.1.8

2017-08-08 Thread Slater, Joseph
I’ll look at the CVEs.  LICENSE updated from 2016 to 2017.  Text is the same.   
 Joe

From: Martin Jansa [mailto:martin.ja...@gmail.com]
Sent: Tuesday, August 08, 2017 1:31 PM
To: Leonardo Sandoval
Cc: Slater, Joseph; Patches and discussions about the oe-core layer
Subject: Re: [OE-core] [oe-core][PATCH 1/1] php: move to version 7.1.8

And wrong ML

On Tue, Aug 8, 2017 at 9:37 PM, Leonardo Sandoval 
>
 wrote:
On Tue, 2017-08-08 at 13:16 -0700, Joe Slater wrote:
> Fixes many CVEs.

would be a plus if you list those.

why LIC_FILES_CHKSUM changed?

Leo

>
> Signed-off-by: Joe Slater 
> >
> ---
>  .../{php-7.1.0 => php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch | 0
>  meta-oe/recipes-devtools/php/{php_7.1.0.bb => 
> php_7.1.8.bb} | 6 +++---
>  2 files changed, 3 insertions(+), 3 deletions(-)
>  rename meta-oe/recipes-devtools/php/{php-7.1.0 => 
> php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch (100%)
>  rename meta-oe/recipes-devtools/php/{php_7.1.0.bb => 
> php_7.1.8.bb} (64%)
>
> diff --git 
> a/meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
>  
> b/meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
> similarity index 100%
> rename from 
> meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
> rename to 
> meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
> diff --git a/meta-oe/recipes-devtools/php/php_7.1.0.bb 
> b/meta-oe/recipes-devtools/php/php_7.1.8.bb
> similarity index 64%
> rename from meta-oe/recipes-devtools/php/php_7.1.0.bb
> rename to meta-oe/recipes-devtools/php/php_7.1.8.bb
> index 210d91f..c0b2541 100644
> --- a/meta-oe/recipes-devtools/php/php_7.1.0.bb
> +++ b/meta-oe/recipes-devtools/php/php_7.1.8.bb
> @@ -1,10 +1,10 @@
>  require php.inc
>
> -LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=b602636d46a61c0ac0432bbf5c078fe4"
> +LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=c0af599f66d0461c5837c695fcbc5c1e"
>
>  SRC_URI += 
> "file://change-AC_TRY_RUN-to-AC_TRY_LINK.patch"
> -SRC_URI[md5sum] = "54e364b60a88db77adb96aacb10f10a4"
> -SRC_URI[sha256sum] = 
> "68bcfd7deed5b3474d81dec9f74d122058327e2bed0ac25bbc9ec70995228e61"
> +SRC_URI[md5sum] = "d22451dc20bbdf4b8bb656dc787c2a36"
> +SRC_URI[sha256sum] = 
> "7064a00a9450565190890c7a4be04e646e0be73b2e0f8c46ae34419f343ca2f8"
>
>  PACKAGECONFIG[mysql] = "--with-mysqli=${STAGING_BINDIR_CROSS}/mysql_config \
>  
> --with-pdo-mysql=${STAGING_BINDIR_CROSS}/mysql_config \
> --
> 2.7.4
>


--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] ✗ patchtest: failure for php: move to version 7.1.8

2017-08-08 Thread Patchwork
== Series Details ==

Series: php: move to version 7.1.8
Revision: 1
URL   : https://patchwork.openembedded.org/series/8129/
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 proposed
series by patchtest resulting in the following failures:



* Issue Series does not apply on top of target branch 
[test_series_merge_on_head] 
  Suggested fixRebase your series on top of targeted branch
  Targeted branch  master (currently at a5bb13a5d7)

* Issue Series sent to the wrong mailing list or some patches from 
the series correspond to different mailing lists [test_target_mailing_list] 
  Suggested fixSend the series again to the correct mailing list (ML)
  Suggested ML openembedded-de...@lists.openembedded.org 
[http://git.openembedded.org/meta-openembedded/]
  Patch's path:meta-oe/recipes-devtools/php/php_7.1.0.bb



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [oe-core][PATCH 1/1] php: move to version 7.1.8

2017-08-08 Thread Martin Jansa
And wrong ML

On Tue, Aug 8, 2017 at 9:37 PM, Leonardo Sandoval <
leonardo.sandoval.gonza...@linux.intel.com> wrote:

> On Tue, 2017-08-08 at 13:16 -0700, Joe Slater wrote:
> > Fixes many CVEs.
>
> would be a plus if you list those.
>
> why LIC_FILES_CHKSUM changed?
>
> Leo
>
> >
> > Signed-off-by: Joe Slater 
> > ---
> >  .../{php-7.1.0 => php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch | 0
> >  meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb} |
> 6 +++---
> >  2 files changed, 3 insertions(+), 3 deletions(-)
> >  rename meta-oe/recipes-devtools/php/{php-7.1.0 =>
> php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch (100%)
> >  rename meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb}
> (64%)
> >
> > diff --git 
> > a/meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
> b/meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_
> RUN-to-AC_TRY_LINK.patch
> > similarity index 100%
> > rename from meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-
> to-AC_TRY_LINK.patch
> > rename to meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-
> to-AC_TRY_LINK.patch
> > diff --git a/meta-oe/recipes-devtools/php/php_7.1.0.bb
> b/meta-oe/recipes-devtools/php/php_7.1.8.bb
> > similarity index 64%
> > rename from meta-oe/recipes-devtools/php/php_7.1.0.bb
> > rename to meta-oe/recipes-devtools/php/php_7.1.8.bb
> > index 210d91f..c0b2541 100644
> > --- a/meta-oe/recipes-devtools/php/php_7.1.0.bb
> > +++ b/meta-oe/recipes-devtools/php/php_7.1.8.bb
> > @@ -1,10 +1,10 @@
> >  require php.inc
> >
> > -LIC_FILES_CHKSUM = "file://LICENSE;md5=b602636d46a61c0ac0432bbf5c078f
> e4"
> > +LIC_FILES_CHKSUM = "file://LICENSE;md5=c0af599f66d0461c5837c695fcbc5c
> 1e"
> >
> >  SRC_URI += "file://change-AC_TRY_RUN-to-AC_TRY_LINK.patch"
> > -SRC_URI[md5sum] = "54e364b60a88db77adb96aacb10f10a4"
> > -SRC_URI[sha256sum] = "68bcfd7deed5b3474d81dec9f74d12
> 2058327e2bed0ac25bbc9ec70995228e61"
> > +SRC_URI[md5sum] = "d22451dc20bbdf4b8bb656dc787c2a36"
> > +SRC_URI[sha256sum] = "7064a00a9450565190890c7a4be04e
> 646e0be73b2e0f8c46ae34419f343ca2f8"
> >
> >  PACKAGECONFIG[mysql] = "--with-mysqli=${STAGING_BINDIR_CROSS}/mysql_config
> \
> >  
> > --with-pdo-mysql=${STAGING_BINDIR_CROSS}/mysql_config
> \
> > --
> > 2.7.4
> >
>
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [oe-core][PATCH 1/1] php: move to version 7.1.8

2017-08-08 Thread Leonardo Sandoval
On Tue, 2017-08-08 at 13:16 -0700, Joe Slater wrote:
> Fixes many CVEs.

would be a plus if you list those.

why LIC_FILES_CHKSUM changed?

Leo

> 
> Signed-off-by: Joe Slater 
> ---
>  .../{php-7.1.0 => php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch | 0
>  meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb} | 6 
> +++---
>  2 files changed, 3 insertions(+), 3 deletions(-)
>  rename meta-oe/recipes-devtools/php/{php-7.1.0 => 
> php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch (100%)
>  rename meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb} (64%)
> 
> diff --git 
> a/meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
>  
> b/meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
> similarity index 100%
> rename from 
> meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
> rename to 
> meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
> diff --git a/meta-oe/recipes-devtools/php/php_7.1.0.bb 
> b/meta-oe/recipes-devtools/php/php_7.1.8.bb
> similarity index 64%
> rename from meta-oe/recipes-devtools/php/php_7.1.0.bb
> rename to meta-oe/recipes-devtools/php/php_7.1.8.bb
> index 210d91f..c0b2541 100644
> --- a/meta-oe/recipes-devtools/php/php_7.1.0.bb
> +++ b/meta-oe/recipes-devtools/php/php_7.1.8.bb
> @@ -1,10 +1,10 @@
>  require php.inc
>  
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=b602636d46a61c0ac0432bbf5c078fe4"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=c0af599f66d0461c5837c695fcbc5c1e"
>  
>  SRC_URI += "file://change-AC_TRY_RUN-to-AC_TRY_LINK.patch"
> -SRC_URI[md5sum] = "54e364b60a88db77adb96aacb10f10a4"
> -SRC_URI[sha256sum] = 
> "68bcfd7deed5b3474d81dec9f74d122058327e2bed0ac25bbc9ec70995228e61"
> +SRC_URI[md5sum] = "d22451dc20bbdf4b8bb656dc787c2a36"
> +SRC_URI[sha256sum] = 
> "7064a00a9450565190890c7a4be04e646e0be73b2e0f8c46ae34419f343ca2f8"
>  
>  PACKAGECONFIG[mysql] = "--with-mysqli=${STAGING_BINDIR_CROSS}/mysql_config \
>  
> --with-pdo-mysql=${STAGING_BINDIR_CROSS}/mysql_config \
> -- 
> 2.7.4
> 


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [oe-core][PATCH 1/1] php: move to version 7.1.8

2017-08-08 Thread Joe Slater
Fixes many CVEs.

Signed-off-by: Joe Slater 
---
 .../{php-7.1.0 => php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch | 0
 meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb} | 6 +++---
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename meta-oe/recipes-devtools/php/{php-7.1.0 => 
php-7.1.8}/change-AC_TRY_RUN-to-AC_TRY_LINK.patch (100%)
 rename meta-oe/recipes-devtools/php/{php_7.1.0.bb => php_7.1.8.bb} (64%)

diff --git 
a/meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch 
b/meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
similarity index 100%
rename from 
meta-oe/recipes-devtools/php/php-7.1.0/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
rename to 
meta-oe/recipes-devtools/php/php-7.1.8/change-AC_TRY_RUN-to-AC_TRY_LINK.patch
diff --git a/meta-oe/recipes-devtools/php/php_7.1.0.bb 
b/meta-oe/recipes-devtools/php/php_7.1.8.bb
similarity index 64%
rename from meta-oe/recipes-devtools/php/php_7.1.0.bb
rename to meta-oe/recipes-devtools/php/php_7.1.8.bb
index 210d91f..c0b2541 100644
--- a/meta-oe/recipes-devtools/php/php_7.1.0.bb
+++ b/meta-oe/recipes-devtools/php/php_7.1.8.bb
@@ -1,10 +1,10 @@
 require php.inc
 
-LIC_FILES_CHKSUM = "file://LICENSE;md5=b602636d46a61c0ac0432bbf5c078fe4"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=c0af599f66d0461c5837c695fcbc5c1e"
 
 SRC_URI += "file://change-AC_TRY_RUN-to-AC_TRY_LINK.patch"
-SRC_URI[md5sum] = "54e364b60a88db77adb96aacb10f10a4"
-SRC_URI[sha256sum] = 
"68bcfd7deed5b3474d81dec9f74d122058327e2bed0ac25bbc9ec70995228e61"
+SRC_URI[md5sum] = "d22451dc20bbdf4b8bb656dc787c2a36"
+SRC_URI[sha256sum] = 
"7064a00a9450565190890c7a4be04e646e0be73b2e0f8c46ae34419f343ca2f8"
 
 PACKAGECONFIG[mysql] = "--with-mysqli=${STAGING_BINDIR_CROSS}/mysql_config \
 --with-pdo-mysql=${STAGING_BINDIR_CROSS}/mysql_config \
-- 
2.7.4

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] State of bitbake world, Failed tasks 2017-08-07

2017-08-08 Thread Martin Jansa
http://www.openembedded.org/wiki/Bitbake_World_Status

== Number of issues - stats ==
{| class='wikitable'
!|Date   !!colspan='3'|Failed tasks 
!!|Signatures !!colspan='14'|QA !!Comment
|-
||  ||qemuarm   ||qemux86   ||qemux86_64||all   
||already-stripped  ||libdir||textrel   ||build-deps
||file-rdeps||version-going-backwards   ||host-user-contaminated
||installed-vs-shipped  ||unknown-configure-option  ||symlink-to-sysroot
||invalid-pkgconfig ||pkgname   ||ldflags   ||compile-host-path 
||  
|-
||2017-08-07||2 ||2 ||5 ||0 ||0 ||0 
||5 ||0 ||0 ||5 ||0 
||0 ||0 ||0 ||0 ||0 
||0 ||0 ||  
|}

== Failed tasks 2017-08-07 ==

INFO: jenkins-job.sh-1.8.25 Complete log available at 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20170808_093147.log

=== common (0) ===

=== common-x86 (0) ===

=== qemuarm (2) ===
* meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb:do_compile
* 
meta-openembedded/meta-oe/recipes-support/mysql/mariadb_5.5.55.bb:do_compile

=== qemux86 (1) ===
* meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile

=== qemux86_64 (3) ===
* 
meta-openembedded/meta-networking/recipes-daemons/squid/squid_3.5.26.bb:do_configure
* 
meta-openembedded/meta-oe/recipes-support/mongodb/mongodb_git.bb:do_compile
* openembedded-core/meta/recipes-graphics/mesa/mesa_17.1.5.bb:do_configure

=== Number of failed tasks (9) ===
{| class=wikitable
|-
|| qemuarm  || 2 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemuarm.20170806_111543.log/
 || http://errors.yoctoproject.org/Errors/Build/43150/
|-
|| qemux86  || 2 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemux86.20170806_111546.log/
 || http://errors.yoctoproject.org/Errors/Build/43153/
|-
|| qemux86_64   || 5 || 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.world.qemux86-64.20170807_125222.log/
 || http://errors.yoctoproject.org/Errors/Build/43156/
http://errors.yoctoproject.org/Errors/Build/43172/
|}

=== PNBLACKLISTs (1) ===

=== QA issues (10) ===
{| class=wikitable
!| Count||Issue
|-
||0 ||already-stripped
|-
||0 ||build-deps
|-
||0 ||compile-host-path
|-
||0 ||file-rdeps
|-
||0 ||host-user-contaminated
|-
||0 ||installed-vs-shipped
|-
||0 ||invalid-pkgconfig
|-
||0 ||ldflags
|-
||0 ||libdir
|-
||0 ||pkgname
|-
||0 ||symlink-to-sysroot
|-
||0 ||unknown-configure-option
|-
||5 ||textrel
|-
||5 ||version-going-backwards
|}



=== Incorrect PACKAGE_ARCH or sstate signatures (0) ===

Complete log: 
http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.signatures.20170807_093247.log/

No issues detected


PNBLACKLISTs:
openembedded-core/:
meta-browser:
meta-openembedded:
meta-networking/recipes-support/lksctp-tools/lksctp-tools_1.0.17.bb:PNBLACKLIST[lksctp-tools]
 ?= "${@bb.utils.contains('DISTRO_FEATURES', 'ld-is-gold', "BROKEN: fails to 
link against sctp_connectx symbol", '', d)}"
meta-qt5:
meta-smartphone:
meta-webos-ports:
PNBLACKLIST[android-system] = "depends on lxc from meta-virtualiazation which 
isn't included in my world builds"
PNBLACKLIST[bigbuckbunny-1080p] = "big and doesn't really need to be tested so 
much"
PNBLACKLIST[bigbuckbunny-480p] = "big and doesn't really need to be tested so 
much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be tested so 
much"
PNBLACKLIST[bigbuckbunny-720p] = "big and doesn't really need to be tested so 
much"
PNBLACKLIST[tearsofsteel-1080p] = "big and doesn't really need to be tested so 
much"
PNBLACKLIST[build-appliance-image] = "tries to include whole downloads 
directory in /home/builder/poky :/"


QA issues by type:
count: 0issue: already-stripped


count: 0issue: libdir


count: 5issue: textrel
chromium-54.0.2810.2: ELF binary 
'/tmp/work/i586-oe-linux/chromium/54.0.2810.2-r0/packages-split/chromium/usr/bin/chromium/chrome'
 has relocations in .text [textrel]
chromium-wayland-53.0.2785.143: ELF binary 
'/tmp/work/i586-oe-linux/chromium-wayland/53.0.2785.143-r0/packages-split/chromium-wayland/usr/bin/chromium/chrome'
 has relocations in .text [textrel]
corosync-2.4.2: ELF binary 
'/tmp/work/core2-64-oe-linux/corosync/2.4.2-r0/packages-split/corosync/usr/sbin/corosync'
 has relocations in .text [textrel]
x264-r2731+gitAUTOINC+2b741f81e5: ELF binary 
'/tmp/work/i586-oe-linux/x264/r2731+gitAUTOINC+2b741f81e5-r0/packages-split/x264-bin/usr/bin/x264'
 has relocations in .text [textrel]
x264-r2731+gitAUTOINC+2b741f81e5: ELF binary 
'/tmp/work/i586-oe-linux/x264/r2731+gitAUTOINC+2b741f81e5-r0/packages-split/x264/usr/lib/libx264.so.148'
 has relocations in .text 

Re: [OE-core] [PATCH v3] externalsrc: Handle .git not being a directory

2017-08-08 Thread Leonardo Sandoval
On Tue, 2017-08-08 at 20:32 +0100, Burton, Ross wrote:
> On 8 August 2017 at 02:46, Joshua Watt  wrote:
> +git_dir = subprocess.check_output(['git',
> 'rev-parse', '--absolute-git-dir'],
> cwd=s_dir).decode("utf-8").rstrip()
> 
> 
> Doesn't work with my old git:
> 
> 
> bb.data_smart.ExpansionError: Failure expanding variable
> do_compile[file-checksums], expression was ${@srctree_hash_files(d)}
> which triggered exception FileNotFoundError: [Errno 2] No such file or
> directory: '--absolute-git-dir/index'
> Summary: There was 1 ERROR message shown, returning a non-zero exit
> code.
> 
> 
> 
> $ git rev-parse --absolute-git-dir
> --absolute-git-dir
> $ git --version
> git version 2.11.0
> 
I also tried it and got same log. my git is a bit newer (2.12.3).

Leo
> 
> Ross
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v3] externalsrc: Handle .git not being a directory

2017-08-08 Thread Burton, Ross
On 8 August 2017 at 02:46, Joshua Watt  wrote:

> +git_dir = subprocess.check_output(['git', 'rev-parse',
> '--absolute-git-dir'], cwd=s_dir).decode("utf-8").rstrip()
>

Doesn't work with my old git:

bb.data_smart.ExpansionError: Failure expanding variable
do_compile[file-checksums], expression was ${@srctree_hash_files(d)} which
triggered exception FileNotFoundError: [Errno 2] No such file or directory:
'--absolute-git-dir/index'
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

$ git rev-parse --absolute-git-dir
--absolute-git-dir
$ git --version
git version 2.11.0

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin

2017-08-08 Thread Burton, Ross
On 8 August 2017 at 18:35, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:

> On 08/08/2017 06:58 PM, Mark Hatle wrote:
>
>> Can we somehow make openssl(10) or nettle a choice when compiling?
>>
>> I ask because I've worked on a few systems where people seem to want one
>> encryption engine for as much of the system as possible (usually openssl).
>> While gstreamer has not been a problem in such systems, I could see it
>> being
>> something that would need to be considered.
>>
>
> This would need to be done across all recipes where such choice is
> supported, as a 'preferred crypto engine' distro feature. There's been talk
> of doing this, but I don't remember what was the outcome.
>

There was a bug for this but I literally closed it earlier today on the
grounds that it would mean patching every user of a crypto library to add
an abstraction and alternative codepaths.  If you don't patch every
instance then there is no point in a global option.

We can have packageconfigs, and expose the choice if the upstream does, but
I think the only sane option is to leave it to the user to set the
options.  It's trivial enough to blacklist openssl if you never want to use
it.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin

2017-08-08 Thread Mark Hatle
On 8/8/17 12:35 PM, Alexander Kanavin wrote:
> On 08/08/2017 06:58 PM, Mark Hatle wrote:
>> Can we somehow make openssl(10) or nettle a choice when compiling?
>>
>> I ask because I've worked on a few systems where people seem to want one
>> encryption engine for as much of the system as possible (usually openssl).
>> While gstreamer has not been a problem in such systems, I could see it being
>> something that would need to be considered.
> 
> This would need to be done across all recipes where such choice is 
> supported, as a 'preferred crypto engine' distro feature. There's been 
> talk of doing this, but I don't remember what was the outcome.
> 
> Also, the plugin needs to be ported to 1.1 first, as the choice will 
> otherwise be taken away when 1.0 goes EOL.

For now I'm fine with 1.0 support.  So something like:

# ensure OpenSSL is used for HLS AES description instead of nettle
# (OpenSSL is a shared dependency with dtls)
PACKAGECONFIG[hls_openssl10] = "--enable-hls
--with-hls-crypto=openssl,--disable-hls,openssl10"

PACKAGECONFIG[hls] = "--enable-hls
--with-hls-crypto=nettle,--disable-hls,nettle"


But my concern is changing the choice of encryption engine could break various
existing uses.  (Like I said, -I- don't have that use, but I expect others do..
perhaps not with gstreamer-plugins-bad though?)

--Mark

> Alex
> 

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin

2017-08-08 Thread Alexander Kanavin

On 08/08/2017 06:58 PM, Mark Hatle wrote:

Can we somehow make openssl(10) or nettle a choice when compiling?

I ask because I've worked on a few systems where people seem to want one
encryption engine for as much of the system as possible (usually openssl).
While gstreamer has not been a problem in such systems, I could see it being
something that would need to be considered.


This would need to be done across all recipes where such choice is 
supported, as a 'preferred crypto engine' distro feature. There's been 
talk of doing this, but I don't remember what was the outcome.


Also, the plugin needs to be ported to 1.1 first, as the choice will 
otherwise be taken away when 1.0 goes EOL.


Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 3/7] btrfs-tools: update to 4.12

2017-08-08 Thread Khem Raj
On Tue, Aug 8, 2017 at 10:19 AM, Alexander Kanavin
 wrote:
> On 08/08/2017 06:48 PM, Khem Raj wrote:
>>
>> I think such a patch would be good upstream too. There are many
>> packages making distinction between
>> build host and target host and help cross compilation.
>
>
> btrfs-tools does not support this distinction. The host compiler is enforced
> in the patch through an openembedded-specific variable.

yes, however there are packages which define *_FOR_BUILD variables for
such distinctions, this
could do the same and upstream would most likely be happy to get this
improvement.

>
> Alex
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 3/7] btrfs-tools: update to 4.12

2017-08-08 Thread Alexander Kanavin

On 08/08/2017 06:48 PM, Khem Raj wrote:

I think such a patch would be good upstream too. There are many
packages making distinction between
build host and target host and help cross compilation.


btrfs-tools does not support this distinction. The host compiler is 
enforced in the patch through an openembedded-specific variable.


Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH v4 2/2] sstatetests: limit the number of signature comparisons when differ

2017-08-08 Thread leonardo . sandoval . gonzalez
From: Leonardo Sandoval 

For perfomance reasons, limit the number of signature comparisons when
stamps differ. The limit set is hardcoded to 20.

[YOCTO #11651]

Signed-off-by: Leonardo Sandoval 
---
 meta/lib/oeqa/selftest/cases/sstatetests.py | 39 ++---
 1 file changed, 25 insertions(+), 14 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py 
b/meta/lib/oeqa/selftest/cases/sstatetests.py
index 0b36027918..47900886a3 100644
--- a/meta/lib/oeqa/selftest/cases/sstatetests.py
+++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
@@ -458,6 +458,24 @@ http_proxy = "http://example.com/;
 base = os.sep.join(root.rsplit(os.sep, 2)[-2:] + [name])
 f[base] = shash
 return f
+
+def compare_sigfiles(files, files1, files2, compare=False):
+for k in files:
+if k in files1 and k in files2:
+print("%s differs:" % k)
+if compare:
+sigdatafile1 = self.topdir + 
"/tmp-sstatesamehash/stamps/" + k + "." + files1[k]
+sigdatafile2 = self.topdir + 
"/tmp-sstatesamehash2/stamps/" + k + "." + files2[k]
+output = bb.siggen.compare_sigfiles(sigdatafile1, 
sigdatafile2)
+if output:
+print('\n'.join(output))
+elif k in files1 and k not in files2:
+print("%s in files1" % k)
+elif k not in files1 and k in files2:
+print("%s in files2" % k)
+else:
+assert "shouldn't reach here"
+
 files1 = get_files(self.topdir + "/tmp-sstatesamehash/stamps/")
 files2 = get_files(self.topdir + "/tmp-sstatesamehash2/stamps/")
 # Remove items that are identical in both sets
@@ -468,18 +486,11 @@ http_proxy = "http://example.com/;
 # No changes, so we're done
 return
 
-for k in files1.keys() | files2.keys():
-if k in files1 and k in files2:
-print("%s differs:" % k)
-sigdatafile1 = self.topdir + "/tmp-sstatesamehash/stamps/" + k 
+ "." + files1[k]
-sigdatafile2 = self.topdir + "/tmp-sstatesamehash2/stamps/" + 
k + "." + files2[k]
-output = bb.siggen.compare_sigfiles(sigdatafile1, sigdatafile2)
-if output:
-print('\n'.join(output))
-elif k in files1 and k not in files2:
-print("%s in files1" % k)
-elif k not in files1 and k in files2:
-print("%s in files2" % k)
-else:
-assert "shouldn't reach here"
+files = list(files1.keys() | files2.keys())
+# this is an expensive computation, thus just compare the first 
'max_sigfiles_to_compare' k files
+max_sigfiles_to_compare = 20
+first, rest = files[:max_sigfiles_to_compare], 
files[max_sigfiles_to_compare:]
+compare_sigfiles(first, files1.keys(), files2.keys(), compare=True)
+compare_sigfiles(rest, files1.keys(), files2.keys(), compare=False)
+
 self.fail("sstate hashes not identical.")
-- 
2.12.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH v4 1/2] sstatetests: Use python function instead of bitbake-diffsigs script

2017-08-08 Thread leonardo . sandoval . gonzalez
From: Leonardo Sandoval 

Using a python function instead of launching a subprocess fasten the
diffsigs computation.

[YOCTO #11651]

Signed-off-by: Leonardo Sandoval 
---
 meta/lib/oeqa/selftest/cases/sstatetests.py | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py 
b/meta/lib/oeqa/selftest/cases/sstatetests.py
index 07a206824a..0b36027918 100644
--- a/meta/lib/oeqa/selftest/cases/sstatetests.py
+++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
@@ -8,6 +8,8 @@ from oeqa.utils.commands import runCmd, bitbake, get_bb_var, 
get_test_layer
 from oeqa.selftest.cases.sstate import SStateBase
 from oeqa.core.decorator.oeid import OETestID
 
+import bb.siggen
+
 class SStateTests(SStateBase):
 
 # Test sstate files creation and their location
@@ -469,9 +471,11 @@ http_proxy = "http://example.com/;
 for k in files1.keys() | files2.keys():
 if k in files1 and k in files2:
 print("%s differs:" % k)
-print(subprocess.check_output(("bitbake-diffsigs",
-   self.topdir + 
"/tmp-sstatesamehash/stamps/" + k + "." + files1[k],
-   self.topdir + 
"/tmp-sstatesamehash2/stamps/" + k + "." + files2[k])))
+sigdatafile1 = self.topdir + "/tmp-sstatesamehash/stamps/" + k 
+ "." + files1[k]
+sigdatafile2 = self.topdir + "/tmp-sstatesamehash2/stamps/" + 
k + "." + files2[k]
+output = bb.siggen.compare_sigfiles(sigdatafile1, sigdatafile2)
+if output:
+print('\n'.join(output))
 elif k in files1 and k not in files2:
 print("%s in files1" % k)
 elif k not in files1 and k in files2:
-- 
2.12.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v3 2/2] sstatetests: limit the number of signature comparisons when differ

2017-08-08 Thread Leonardo Sandoval
On Tue, 2017-08-08 at 15:40 +0100, Burton, Ross wrote:
> On 7 August 2017 at 22:33,
>  wrote:
> From: Leonardo Sandoval
> 
> 
> For perfomance reasons, limit the number of signature
> comparisons when
> stamps differ. The limit set is hardcoded to 20.
> 
> [YOCTO #11651]
> 
> Signed-off-by: Leonardo Sandoval
> 
> ---
>  meta/lib/oeqa/selftest/cases/sstatetests.py | 40
> +++--
>  1 file changed, 26 insertions(+), 14 deletions(-)
> 
> diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py
> b/meta/lib/oeqa/selftest/cases/sstatetests.py
> index 0b36027918..6298443a18 100644
> --- a/meta/lib/oeqa/selftest/cases/sstatetests.py
> +++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
> @@ -458,6 +458,25 @@ http_proxy = "http://example.com/;
>  base = os.sep.join(root.rsplit(os.sep,
> 2)[-2:] + [name])
>  f[base] = shash
>  return f
> +
> +def compare_sigfiles(files, files1, files2,
> compare=False):
> +for k in files:
> +if k in files1 and k in files2:
> +i_sigfile += 1
> 
> 
> Surely this is going to produce an i_sigfile is not defined error?

Right, I forgot to remove that line and test it properly. Will send
another revision.

Leo



> 
> 
> Ross 


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin

2017-08-08 Thread Mark Hatle
On 8/8/17 10:30 AM, Alexander Kanavin wrote:
> It has not been ported to openssl 1.1 (and there's nothing in upstream git),
> but it's possible to use nettle or gcrypt intead.
> 
> Signed-off-by: Alexander Kanavin 
> ---
>  meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc 
> b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
> index e964fef3f20..7427772a45f 100644
> --- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
> +++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
> @@ -40,9 +40,7 @@ PACKAGECONFIG[flite]   = 
> "--enable-flite,--disable-flite,flite-alsa"
>  PACKAGECONFIG[fluidsynth]  = 
> "--enable-fluidsynth,--disable-fluidsynth,fluidsynth"
>  PACKAGECONFIG[gles2]   = 
> "--enable-gles2,--disable-gles2,virtual/libgles2"
>  PACKAGECONFIG[gtk] = "--enable-gtk3,--disable-gtk3,gtk+3"
> -# ensure OpenSSL is used for HLS AES description instead of nettle
> -# (OpenSSL is a shared dependency with dtls)
> -PACKAGECONFIG[hls] = "--enable-hls 
> --with-hls-crypto=openssl,--disable-hls,openssl"
> +PACKAGECONFIG[hls] = "--enable-hls 
> --with-hls-crypto=nettle,--disable-hls,nettle"

Can we somehow make openssl(10) or nettle a choice when compiling?

I ask because I've worked on a few systems where people seem to want one
encryption engine for as much of the system as possible (usually openssl).
While gstreamer has not been a problem in such systems, I could see it being
something that would need to be considered.

Otherwise no concerns with the rest of the patch set.

>  PACKAGECONFIG[kms] = "--enable-kms,--disable-kms,libdrm"
>  PACKAGECONFIG[libmms]  = "--enable-libmms,--disable-libmms,libmms"
>  PACKAGECONFIG[libssh2] = "--enable-libssh2,--disable-libssh2,libssh2"
> 

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v4] kernel: Add support for multiple kernel packages

2017-08-08 Thread Haris Okanovic



On 08/03/2017 11:18 AM, Ovidiu-Adrian Vancea wrote:

On Thu, 2017-07-27 at 11:01 -0700, Rees, Kevron wrote:

On Wed, Jul 19, 2017 at 8:56 AM, Wold, Saul 
wrote:

On Tue, 2017-07-18 at 08:34 -0500, Haris Okanovic wrote:


On 07/17/2017 03:31 PM, Wold, Saul wrote:


On Wed, 2017-07-05 at 12:33 -0500, Haris Okanovic wrote:


Some distros may want to provide alternate kernel "flavors"
via
feeds
or
within bootable images. For example, readily available builds
which
provide certain diagnostic features can enable developers and
testers
to
more quickly resolve issues by avoiding lengthy kernel
builds.

This change allows for building multiple flavors of the
kernel
and
module packages by templatizing kernel package names via a
new
KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults
to
the
old
name of "kernel", but can be overridden by certain recipes
providing
alternate kernel flavors.

To maintain compatibility, recipes providing alternate kernel
flavors
cannot be the "preferred provider" for virtual/kernel. This
is
because
OE puts the preferred provider's build and source at
"tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
"tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
"tmp-glibc/work/*/$PN/" like other recipes. Therefore,
recipes
using
the
default KERNEL_PACKAGE_NAME="kernel" follows the old
semantics --
build
in the old location and may be preferred provider -- while
recipes
using
all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR
and
don't
provide "virtual/kernel".

Testing:
   1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
  linux-yocto-tiny_4.9.bb so that it may build alongside
  the main kernel.
   2. `bitbake linux-yocto linux-yocto-tiny` to build both
kernel
flavors.
   3. Verified image and modules IPKs exist for both:
  tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
  tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-
yocto-
tiny
   4. Verified linux-yocto is the "preferred provider", and
was
built
in
  shared directory: tmp-glibc/work-shared/qemux86/kernel-*
   5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
  core-image-base.bb to include both kernel flavors.
   6. `bitbake core-image-base` to build an image.
   7. Verified image contains two bzImage's under /boot/, with
  "yocto-standard" selected to boot via symlink.

Discussion thread:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ope
nembedded.org_pipermail_openembedded-2Dcore_2015-
2DDe=DwICAg=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA
=35FLeGKBmrBGMHAhCV37-B4ddgcjLZXUChuxj5DD6Sk=-J-
ERX3BXdjXgeeIE_ZNE7GozSVtUpP3Wt6FV_jtLtM=z_ITagkjX7-
q9KHaytBdqTZeJYksmYYjciSiELDYIGE=
cemb
er/thread.html#114122

Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Gratian Crisan 
Signed-off-by: Haris Okanovic 
Coauthored-by: Gratian Crisan 
Coauthored-by: Haris Okanovic 
Coauthored-by: Josh Hernstrom 
---
[PATCH v2] Change STAGING_KERNEL_DIR and
STAGING_KERNEL_BUILDDIR
to
the
"work" directory in alternate kernel builds, instead of
"work-
shared",
so
that the two builds don't clobber each other.

[PATCH v3] An updated version of this change rebased onto the
current
OE-core master. Changes:
   * Remove PREFERRED_PROVIDER check in linux-yocto.inc in
alternate
 kernel builds, since alternate kernels aren't the
 PREFERRED_PROVIDER for virtual/kernel by definition.
   * Remove "virtual/kernel" from PROVIDES in alternate kernel
builds.

[PATCH v4] Another rebase onto master; no functional change.
Improved description and testing steps.


So I finally had a chance to get back to this and test build
with
it, I
saw the following WARNING, which lead to the ERROR:

WARNING: Variable key FILES_${PN}-dev (${includedir}
${FILES_SOLIBSDEV}
${libdir}/*.la ${libdir}/*.o ${libdir}/pkgconfig
${datadir}/pkgconfig
${datadir}/aclocal ${base_libdir}/*.o ${libdir}/${BPN}/*.la
${base_libdir}/*.la) replaces original key FILES_linux-yocto-
dev
(/boot/System.map* /boot/Module.symvers* /boot/config*
${KERNEL_SRC_PATH}
${nonarch_base_libdir}/modules/${KERNEL_VERSION}/build).
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: QA Issue: linux-yocto: Files/directories were
installed
but
not shipped in any package:
/boot/System.map-4.10.17-yocto-standard
/boot/Module.symvers-4.10.17-yocto-standard
/boot/config-4.10.17-yocto-standard
Please set FILES such that these items are packaged.
Alternatively
if
they are unneeded, avoid installing them or delete them within
do_install.
linux-yocto: 3 installed and not shipped files. [installed-vs-
shipped]
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: Fatal QA errors found, failing task.
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: Function failed: do_package

Something seems to be causing the 

Re: [OE-core] [PATCH v4] kernel: Add support for multiple kernel packages

2017-08-08 Thread Haris Okanovic



On 07/19/2017 10:56 AM, Wold, Saul wrote:

On Tue, 2017-07-18 at 08:34 -0500, Haris Okanovic wrote:


On 07/17/2017 03:31 PM, Wold, Saul wrote:


On Wed, 2017-07-05 at 12:33 -0500, Haris Okanovic wrote:


Some distros may want to provide alternate kernel "flavors" via
feeds
or
within bootable images. For example, readily available builds
which
provide certain diagnostic features can enable developers and
testers
to
more quickly resolve issues by avoiding lengthy kernel builds.

This change allows for building multiple flavors of the kernel
and
module packages by templatizing kernel package names via a new
KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to
the
old
name of "kernel", but can be overridden by certain recipes
providing
alternate kernel flavors.

To maintain compatibility, recipes providing alternate kernel
flavors
cannot be the "preferred provider" for virtual/kernel. This is
because
OE puts the preferred provider's build and source at
"tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
"tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
"tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes
using
the
default KERNEL_PACKAGE_NAME="kernel" follows the old semantics --
build
in the old location and may be preferred provider -- while
recipes
using
all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and
don't
provide "virtual/kernel".

Testing:
   1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
  linux-yocto-tiny_4.9.bb so that it may build alongside
  the main kernel.
   2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel
flavors.
   3. Verified image and modules IPKs exist for both:
  tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
  tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-
tiny
   4. Verified linux-yocto is the "preferred provider", and was
built
in
  shared directory: tmp-glibc/work-shared/qemux86/kernel-*
   5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
  core-image-base.bb to include both kernel flavors.
   6. `bitbake core-image-base` to build an image.
   7. Verified image contains two bzImage's under /boot/, with
  "yocto-standard" selected to boot via symlink.

Discussion thread:
http://lists.openembedded.org/pipermail/openembedded-core/2015-De
cemb
er/thread.html#114122

Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Gratian Crisan 
Signed-off-by: Haris Okanovic 
Coauthored-by: Gratian Crisan 
Coauthored-by: Haris Okanovic 
Coauthored-by: Josh Hernstrom 
---
[PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR
to
the
"work" directory in alternate kernel builds, instead of "work-
shared",
so
that the two builds don't clobber each other.

[PATCH v3] An updated version of this change rebased onto the
current
OE-core master. Changes:
   * Remove PREFERRED_PROVIDER check in linux-yocto.inc in
alternate
 kernel builds, since alternate kernels aren't the
 PREFERRED_PROVIDER for virtual/kernel by definition.
   * Remove "virtual/kernel" from PROVIDES in alternate kernel
builds.

[PATCH v4] Another rebase onto master; no functional change.
Improved description and testing steps.


So I finally had a chance to get back to this and test build with
it, I
saw the following WARNING, which lead to the ERROR:

WARNING: Variable key FILES_${PN}-dev (${includedir}
${FILES_SOLIBSDEV}
${libdir}/*.la ${libdir}/*.o ${libdir}/pkgconfig
${datadir}/pkgconfig
${datadir}/aclocal ${base_libdir}/*.o ${libdir}/${BPN}/*.la
${base_libdir}/*.la) replaces original key FILES_linux-yocto-dev
(/boot/System.map* /boot/Module.symvers* /boot/config*
${KERNEL_SRC_PATH}
${nonarch_base_libdir}/modules/${KERNEL_VERSION}/build).
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: QA Issue: linux-yocto: Files/directories were installed
but
not shipped in any package:
/boot/System.map-4.10.17-yocto-standard
/boot/Module.symvers-4.10.17-yocto-standard
/boot/config-4.10.17-yocto-standard
Please set FILES such that these items are packaged. Alternatively
if
they are unneeded, avoid installing them or delete them within
do_install.
linux-yocto: 3 installed and not shipped files. [installed-vs-
shipped]
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: Fatal QA errors found, failing task.
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: Function failed: do_package

Something seems to be causing the FILES_linux-yocto-dev info to be
overridden, I have not tracked down the culprit yet.



`FILES_linux-yocto-dev` is set to the default value from OE's
bitbake.conf. `FILES_kernel-dev` on the other hand is set by
kernel.bbclass; when `KERNEL_PACKAGE_NAME` expands to `kernel`.

I think the real issue here is that QA checks care about
`FILES_${PN}-dev` at all even though that 

Re: [OE-core] [PATCH v4] kernel: Add support for multiple kernel packages

2017-08-08 Thread Haris Okanovic



On 07/27/2017 01:01 PM, Rees, Kevron wrote:

On Wed, Jul 19, 2017 at 8:56 AM, Wold, Saul  wrote:

On Tue, 2017-07-18 at 08:34 -0500, Haris Okanovic wrote:


On 07/17/2017 03:31 PM, Wold, Saul wrote:


On Wed, 2017-07-05 at 12:33 -0500, Haris Okanovic wrote:


Some distros may want to provide alternate kernel "flavors" via
feeds
or
within bootable images. For example, readily available builds
which
provide certain diagnostic features can enable developers and
testers
to
more quickly resolve issues by avoiding lengthy kernel builds.

This change allows for building multiple flavors of the kernel
and
module packages by templatizing kernel package names via a new
KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to
the
old
name of "kernel", but can be overridden by certain recipes
providing
alternate kernel flavors.

To maintain compatibility, recipes providing alternate kernel
flavors
cannot be the "preferred provider" for virtual/kernel. This is
because
OE puts the preferred provider's build and source at
"tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
"tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
"tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes
using
the
default KERNEL_PACKAGE_NAME="kernel" follows the old semantics --
build
in the old location and may be preferred provider -- while
recipes
using
all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and
don't
provide "virtual/kernel".

Testing:
   1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
  linux-yocto-tiny_4.9.bb so that it may build alongside
  the main kernel.
   2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel
flavors.
   3. Verified image and modules IPKs exist for both:
  tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
  tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-
tiny
   4. Verified linux-yocto is the "preferred provider", and was
built
in
  shared directory: tmp-glibc/work-shared/qemux86/kernel-*
   5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
  core-image-base.bb to include both kernel flavors.
   6. `bitbake core-image-base` to build an image.
   7. Verified image contains two bzImage's under /boot/, with
  "yocto-standard" selected to boot via symlink.

Discussion thread:
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openembedded.org_pipermail_openembedded-2Dcore_2015-2DDe=DwIBaQ=I_0YwoKy7z5LMTVdyO6YCiE2uzI1jjZZuIPelcSjixA=8Bziuw3IaCGjyrSAphuGwHmVdHcVwza-srUYwL9U_Ms=EXsasUKMXo4dlk7nFW3VDV8Z06QZKhwHTWyH5F0E6-c=vJgjJOYKOYNz18XjXjP-gc0MvGMrdm1Z8EbcLuaxFqA=
cemb
er/thread.html#114122

Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Gratian Crisan 
Signed-off-by: Haris Okanovic 
Coauthored-by: Gratian Crisan 
Coauthored-by: Haris Okanovic 
Coauthored-by: Josh Hernstrom 
---
[PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR
to
the
"work" directory in alternate kernel builds, instead of "work-
shared",
so
that the two builds don't clobber each other.

[PATCH v3] An updated version of this change rebased onto the
current
OE-core master. Changes:
   * Remove PREFERRED_PROVIDER check in linux-yocto.inc in
alternate
 kernel builds, since alternate kernels aren't the
 PREFERRED_PROVIDER for virtual/kernel by definition.
   * Remove "virtual/kernel" from PROVIDES in alternate kernel
builds.

[PATCH v4] Another rebase onto master; no functional change.
Improved description and testing steps.


So I finally had a chance to get back to this and test build with
it, I
saw the following WARNING, which lead to the ERROR:

WARNING: Variable key FILES_${PN}-dev (${includedir}
${FILES_SOLIBSDEV}
${libdir}/*.la ${libdir}/*.o ${libdir}/pkgconfig
${datadir}/pkgconfig
${datadir}/aclocal ${base_libdir}/*.o ${libdir}/${BPN}/*.la
${base_libdir}/*.la) replaces original key FILES_linux-yocto-dev
(/boot/System.map* /boot/Module.symvers* /boot/config*
${KERNEL_SRC_PATH}
${nonarch_base_libdir}/modules/${KERNEL_VERSION}/build).
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: QA Issue: linux-yocto: Files/directories were installed
but
not shipped in any package:
/boot/System.map-4.10.17-yocto-standard
/boot/Module.symvers-4.10.17-yocto-standard
/boot/config-4.10.17-yocto-standard
Please set FILES such that these items are packaged. Alternatively
if
they are unneeded, avoid installing them or delete them within
do_install.
linux-yocto: 3 installed and not shipped files. [installed-vs-
shipped]
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: Fatal QA errors found, failing task.
ERROR: linux-yocto-4.10.17+gitAUTOINC+e92bd55409_6648a34e00-r0
do_package: Function failed: do_package

Something seems to be causing the FILES_linux-yocto-dev info to be
overridden, I have not tracked down the 

Re: [OE-core] [PATCH 3/7] btrfs-tools: update to 4.12

2017-08-08 Thread Khem Raj
On Mon, Aug 7, 2017 at 4:45 AM, Alexander Kanavin
 wrote:
> Add a patch to force a native build for a helper binary
> (which is not installed or used outside of the build process).
>
> Signed-off-by: Alexander Kanavin 
> ---
>  ...-Makefile-build-mktables-using-native-gcc.patch | 30 
> ++
>  .../{btrfs-tools_4.11.1.bb => btrfs-tools_4.12.bb} |  6 +++--
>  2 files changed, 34 insertions(+), 2 deletions(-)
>  create mode 100644 
> meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-build-mktables-using-native-gcc.patch
>  rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_4.11.1.bb => 
> btrfs-tools_4.12.bb} (88%)
>
> diff --git 
> a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-build-mktables-using-native-gcc.patch
>  
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-build-mktables-using-native-gcc.patch
> new file mode 100644
> index 000..0a3b5fd7102
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Makefile-build-mktables-using-native-gcc.patch
> @@ -0,0 +1,30 @@
> +From e58369f6d36bc51eb59d6afa34c1cae3ff0810ef Mon Sep 17 00:00:00 2001
> +From: Alexander Kanavin 
> +Date: Mon, 7 Aug 2017 14:10:38 +0300
> +Subject: [PATCH] Makefile: build mktables using native gcc
> +
> +It's a throwaway helper binary used during build, and so it needs to
> +be native.
> +
> +Upstream-Status: Inappropriate [oe specific]

I think such a patch would be good upstream too. There are many
packages making distinction between
build host and target host and help cross compilation.

> +Signed-off-by: Alexander Kanavin 
> +---
> + Makefile | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/Makefile b/Makefile
> +index b3e2b63..347aaf1 100644
> +--- a/Makefile
>  b/Makefile
> +@@ -323,7 +323,7 @@ version.h: version.sh version.h.in configure.ac
> +
> + mktables: kernel-lib/mktables.c
> +   @echo "[CC] $@"
> +-  $(Q)$(CC) $(CFLAGS) $< -o $@
> ++  $(Q)$(BUILD_CC) $(CFLAGS) $< -o $@
> +
> + kernel-lib/tables.c: mktables
> +   @echo "[TABLE]  $@"
> +--
> +2.13.2
> +
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.1.bb 
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.12.bb
> similarity index 88%
> rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.1.bb
> rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_4.12.bb
> index a7b42e9546b..c3cc89c2b0f 100644
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.11.1.bb
> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_4.12.bb
> @@ -14,8 +14,10 @@ DEPENDS = "util-linux attr e2fsprogs lzo acl"
>  DEPENDS_append_class-target = " udev"
>  RDEPENDS_${PN} = "libgcc"
>
> -SRCREV = "88221fc081a7a0979a012f243b66cf097382cc8f"
> -SRC_URI = 
> "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git"
> +SRCREV = "0607132c3200bcead1426e6dc685432008de95de"
> +SRC_URI = 
> "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git \
> +   file://0001-Makefile-build-mktables-using-native-gcc.patch \
> +   "
>
>  inherit autotools-brokensep pkgconfig manpages
>
> --
> 2.13.2
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 3/4] cryptodev-tests: depend on openssl 1.0

2017-08-08 Thread Alexander Kanavin
Upstream ticket:
https://github.com/cryptodev-linux/cryptodev-linux/issues/22

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-kernel/cryptodev/cryptodev-tests_1.9.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/cryptodev/cryptodev-tests_1.9.bb 
b/meta/recipes-kernel/cryptodev/cryptodev-tests_1.9.bb
index 9cb5dcb94f0..9afb3de217e 100644
--- a/meta/recipes-kernel/cryptodev/cryptodev-tests_1.9.bb
+++ b/meta/recipes-kernel/cryptodev/cryptodev-tests_1.9.bb
@@ -2,7 +2,7 @@ require cryptodev.inc
 
 SUMMARY = "A test suite for /dev/crypto device driver"
 
-DEPENDS += "openssl"
+DEPENDS += "openssl10"
 
 SRC_URI += " \
 file://0001-Add-the-compile-and-install-rules-for-cryptodev-test.patch \
-- 
2.13.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH v5] kernel: Add support for multiple kernel packages

2017-08-08 Thread Haris Okanovic
Some distros may want to provide alternate kernel "flavors" via feeds or
within bootable images. For example, readily available builds which
provide certain diagnostic features can enable developers and testers to
more quickly resolve issues by avoiding lengthy kernel builds.

This change allows for building multiple flavors of the kernel and
module packages by templatizing kernel package names via a new
KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to the old
name of "kernel", but can be overridden by certain recipes providing
alternate kernel flavors.

To maintain compatibility, recipes providing alternate kernel flavors
cannot be the "preferred provider" for virtual/kernel. This is because
OE puts the preferred provider's build and source at
"tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
"tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
"tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes using the
default KERNEL_PACKAGE_NAME="kernel" follows the old semantics -- build
in the old location and may be preferred provider -- while recipes using
all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and don't
provide "virtual/kernel".

Testing:
 1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
linux-yocto-tiny_4.9.bb so that it may build alongside
the main kernel.
 2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel flavors.
 3. Verified image and modules IPKs exist for both:
tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-tiny
 4. Verified linux-yocto is the "preferred provider", and was built in
shared directory: tmp-glibc/work-shared/qemux86/kernel-*
 5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
core-image-base.bb to include both kernel flavors.
 6. `bitbake core-image-base` to build an image.
 7. Verified image contains two bzImage's under /boot/, with
"yocto-standard" selected to boot via symlink.

Discussion thread:
http://lists.openembedded.org/pipermail/openembedded-core/2015-December/thread.html#114122

Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Gratian Crisan 
Signed-off-by: Haris Okanovic 
Coauthored-by: Gratian Crisan 
Coauthored-by: Haris Okanovic 
Coauthored-by: Josh Hernstrom 
---
[PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR to the
"work" directory in alternate kernel builds, instead of "work-shared",
so
that the two builds don't clobber each other.

[PATCH v3] An updated version of this change rebased onto the current
OE-core master. Changes:
 - Remove PREFERRED_PROVIDER check in linux-yocto.inc in alternate
   kernel builds, since alternate kernels aren't the
   PREFERRED_PROVIDER for virtual/kernel by definition.
 - Remove "virtual/kernel" from PROVIDES in alternate kernel builds.

[PATCH v4] Another rebase onto master; no functional change.
Improved description and testing steps.

[PATCH v5]
 - Warn when PN == KERNEL_PACKAGE_NAME (bug # 11905)
 - Add KERNEL_DEPLOYSUBDIR to avoid DEPLOYDIR collisions

https://github.com/harisokanovic/openembedded-core/tree/dev/hokanovi/multi-kernel-packages-v5
---
 meta/classes/kernel-module-split.bbclass  |   9 ++-
 meta/classes/kernel.bbclass   | 114 +++---
 meta/conf/documentation.conf  |   1 +
 meta/recipes-kernel/linux/linux-dtb.inc   |   2 +-
 meta/recipes-kernel/linux/linux-yocto.inc |   2 +-
 5 files changed, 81 insertions(+), 47 deletions(-)

diff --git a/meta/classes/kernel-module-split.bbclass 
b/meta/classes/kernel-module-split.bbclass
index 1035525dac..9716c5937b 100644
--- a/meta/classes/kernel-module-split.bbclass
+++ b/meta/classes/kernel-module-split.bbclass
@@ -30,7 +30,7 @@ do_install_append() {
 
 PACKAGESPLITFUNCS_prepend = "split_kernel_module_packages "
 
-KERNEL_MODULES_META_PACKAGE ?= "kernel-modules"
+KERNEL_MODULES_META_PACKAGE ?= "${KERNEL_PACKAGE_NAME}-modules"
 
 KERNEL_MODULE_PACKAGE_PREFIX ?= ""
 KERNEL_MODULE_PACKAGE_SUFFIX ?= "-${KERNEL_VERSION}"
@@ -129,16 +129,19 @@ python split_kernel_module_packages () {
postfix = format.split('%s')[1]
d.setVar('RPROVIDES_' + pkg, pkg.replace(postfix, ''))
 
+kernel_package_name = d.getVar("KERNEL_PACKAGE_NAME", True)
+kernel_version = d.getVar("KERNEL_VERSION", True)
+
 module_regex = '^(.*)\.k?o$'
 
 module_pattern_prefix = d.getVar('KERNEL_MODULE_PACKAGE_PREFIX')
 module_pattern_suffix = d.getVar('KERNEL_MODULE_PACKAGE_SUFFIX')
-module_pattern = module_pattern_prefix + 'kernel-module-%s' + 
module_pattern_suffix
+module_pattern = module_pattern_prefix + kernel_package_name + 
'-module-%s' + module_pattern_suffix
 
 postinst = d.getVar('pkg_postinst_modules')
 postrm = d.getVar('pkg_postrm_modules')
 
-modules = do_split_packages(d, 

[OE-core] [PATCH 4/4] gstreamer-plugins-bad: replace openssl dependency with nettle for hls plugin

2017-08-08 Thread Alexander Kanavin
It has not been ported to openssl 1.1 (and there's nothing in upstream git),
but it's possible to use nettle or gcrypt intead.

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc 
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
index e964fef3f20..7427772a45f 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc
@@ -40,9 +40,7 @@ PACKAGECONFIG[flite]   = 
"--enable-flite,--disable-flite,flite-alsa"
 PACKAGECONFIG[fluidsynth]  = 
"--enable-fluidsynth,--disable-fluidsynth,fluidsynth"
 PACKAGECONFIG[gles2]   = 
"--enable-gles2,--disable-gles2,virtual/libgles2"
 PACKAGECONFIG[gtk] = "--enable-gtk3,--disable-gtk3,gtk+3"
-# ensure OpenSSL is used for HLS AES description instead of nettle
-# (OpenSSL is a shared dependency with dtls)
-PACKAGECONFIG[hls] = "--enable-hls 
--with-hls-crypto=openssl,--disable-hls,openssl"
+PACKAGECONFIG[hls] = "--enable-hls 
--with-hls-crypto=nettle,--disable-hls,nettle"
 PACKAGECONFIG[kms] = "--enable-kms,--disable-kms,libdrm"
 PACKAGECONFIG[libmms]  = "--enable-libmms,--disable-libmms,libmms"
 PACKAGECONFIG[libssh2] = "--enable-libssh2,--disable-libssh2,libssh2"
-- 
2.13.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 2/4] openssh: depend on openssl 1.0

2017-08-08 Thread Alexander Kanavin
The proposed openssl 1.1 patches are here:
https://github.com/openssh/openssh-portable/pull/48

Openssl maintainers are not in a hurry to get 1.1 support in;
if it doesn't show up within reasonable time, we can take a patch
from Fedora:
http://lists.mindrot.org/pipermail/openssh-unix-dev/2016-November/035454.html

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-connectivity/openssh/openssh_7.5p1.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-connectivity/openssh/openssh_7.5p1.bb 
b/meta/recipes-connectivity/openssh/openssh_7.5p1.bb
index 7bd313bb4e8..3b8fd7d1cc5 100644
--- a/meta/recipes-connectivity/openssh/openssh_7.5p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_7.5p1.bb
@@ -8,7 +8,8 @@ SECTION = "console/network"
 LICENSE = "BSD"
 LIC_FILES_CHKSUM = "file://LICENCE;md5=e326045657e842541d3f35aada442507"
 
-DEPENDS = "zlib openssl"
+# openssl 1.1 patches are proposed at 
https://github.com/openssh/openssh-portable/pull/48
+DEPENDS = "zlib openssl10"
 DEPENDS += "${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}"
 
 SRC_URI = 
"http://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-${PV}.tar.gz \
-- 
2.13.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 1/4] openssl: add a 1.1 version

2017-08-08 Thread Alexander Kanavin
Existing openssl 1.0 recipe is renamed to openssl10; it will
continue to be provided for as long as upstream supports it
(and there are still several recipes which do not work with openssl
1.1 due to API differences).

A few files (such as openssl binary) are no longer installed by openssl 1.0,
because they clash with openssl 1.1.

Signed-off-by: Alexander Kanavin 
---
 meta/conf/distro/include/no-static-libs.inc|   3 +
 ...ve-test-that-requires-running-as-non-root.patch |  49 +
 ...1-Take-linking-flags-from-LDFLAGS-env-var.patch |  43 
 .../recipes-connectivity/openssl/openssl/run-ptest |   4 +-
 .../openssl/{openssl.inc => openssl10.inc} |  14 +-
 ...build-with-clang-using-external-assembler.patch |   0
 .../{openssl => openssl10}/Makefiles-ptest.patch   |   0
 .../Use-SHA256-not-MD5-as-default-digest.patch |   0
 .../configure-musl-target.patch|   0
 .../{openssl => openssl10}/configure-targets.patch |   0
 .../debian/c_rehash-compat.patch   |   0
 .../openssl/{openssl => openssl10}/debian/ca.patch |   0
 .../debian/debian-targets.patch|   0
 .../{openssl => openssl10}/debian/man-dir.patch|   0
 .../debian/man-section.patch   |   0
 .../{openssl => openssl10}/debian/no-rpath.patch   |   0
 .../debian/no-symbolic.patch   |   0
 .../{openssl => openssl10}/debian/pic.patch|   0
 .../debian/version-script.patch|   0
 .../debian1.0.2/block_digicert_malaysia.patch  |   0
 .../debian1.0.2/block_diginotar.patch  |   0
 .../debian1.0.2/soname.patch   |   0
 .../debian1.0.2/version-script.patch   |   0
 .../engines-install-in-libdir-ssl.patch|   0
 .../openssl/{openssl => openssl10}/find.pl |   0
 .../{openssl => openssl10}/oe-ldflags.patch|   0
 .../openssl-1.0.2a-x32-asm.patch   |   0
 .../openssl/openssl10/openssl-c_rehash.sh  | 222 +
 .../openssl-fix-des.pod-error.patch|   0
 .../openssl-util-perlpath.pl-cwd.patch |   0
 .../openssl_fix_for_x32.patch  |   0
 .../openssl/{openssl => openssl10}/parallel.patch  |   0
 .../{openssl => openssl10}/ptest-deps.patch|   0
 .../ptest_makefile_deps.patch  |   0
 .../openssl/openssl10/run-ptest|   2 +
 .../{openssl => openssl10}/shared-libs.patch   |   0
 .../{openssl_1.0.2l.bb => openssl10_1.0.2l.bb} |   4 +-
 .../recipes-connectivity/openssl/openssl_1.1.0f.bb | 155 ++
 38 files changed, 491 insertions(+), 5 deletions(-)
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/0001-Remove-test-that-requires-running-as-non-root.patch
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/0001-Take-linking-flags-from-LDFLAGS-env-var.patch
 mode change 100755 => 100644 
meta/recipes-connectivity/openssl/openssl/run-ptest
 rename meta/recipes-connectivity/openssl/{openssl.inc => openssl10.inc} (95%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/0001-Fix-build-with-clang-using-external-assembler.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/Makefiles-ptest.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/Use-SHA256-not-MD5-as-default-digest.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/configure-musl-target.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/configure-targets.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/c_rehash-compat.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/ca.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/debian-targets.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/man-dir.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/man-section.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/no-rpath.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/no-symbolic.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/pic.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/version-script.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian1.0.2/block_digicert_malaysia.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian1.0.2/block_diginotar.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian1.0.2/soname.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian1.0.2/version-script.patch (100%)
 rename 

[OE-core] [PATCH 0/4] Add openssl 1.1

2017-08-08 Thread Alexander Kanavin
This patch series introduces the recipe for openssl 1.1 (openssl 1.0 is 
preserved
but renamed to openssl10), and does a few necessary adjustmenets and updates to 
other
recipes.

Openssl 1.1 is an opt-out; it has the same recipe name as openssl 1.0 had, and 
so
all dependencies are compiled with it by default. If there's an API issue, 
please
fix it, or adjust the recipe to depend on 'openssl10' (which is a lesser 
solution,
and subject to openssl 1.0 eventually being removed from oe-core).

This iteration of the patchset fixes an issue with installing certificates
when building images; specifically a special version of c_rehash utility needs
to be used on build host.

The following changes since commit 621ca8b66c8f927713d98bc4d37a0f151e4b:

  ca-certificates: update to 20170717 (2017-08-08 18:24:06 +0300)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib akanavin/openssl-1.1
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/openssl-1.1

Alexander Kanavin (4):
  openssl: add a 1.1 version
  openssh: depend on openssl 1.0
  cryptodev-tests: depend on openssl 1.0
  gstreamer-plugins-bad: replace openssl dependency with nettle for hls
plugin

 meta/conf/distro/include/no-static-libs.inc|   3 +
 meta/recipes-connectivity/openssh/openssh_7.5p1.bb |   3 +-
 ...ve-test-that-requires-running-as-non-root.patch |  49 +
 ...1-Take-linking-flags-from-LDFLAGS-env-var.patch |  43 
 .../recipes-connectivity/openssl/openssl/run-ptest |   4 +-
 .../openssl/{openssl.inc => openssl10.inc} |  14 +-
 ...build-with-clang-using-external-assembler.patch |   0
 .../{openssl => openssl10}/Makefiles-ptest.patch   |   0
 .../Use-SHA256-not-MD5-as-default-digest.patch |   0
 .../configure-musl-target.patch|   0
 .../{openssl => openssl10}/configure-targets.patch |   0
 .../debian/c_rehash-compat.patch   |   0
 .../openssl/{openssl => openssl10}/debian/ca.patch |   0
 .../debian/debian-targets.patch|   0
 .../{openssl => openssl10}/debian/man-dir.patch|   0
 .../debian/man-section.patch   |   0
 .../{openssl => openssl10}/debian/no-rpath.patch   |   0
 .../debian/no-symbolic.patch   |   0
 .../{openssl => openssl10}/debian/pic.patch|   0
 .../debian/version-script.patch|   0
 .../debian1.0.2/block_digicert_malaysia.patch  |   0
 .../debian1.0.2/block_diginotar.patch  |   0
 .../debian1.0.2/soname.patch   |   0
 .../debian1.0.2/version-script.patch   |   0
 .../engines-install-in-libdir-ssl.patch|   0
 .../openssl/{openssl => openssl10}/find.pl |   0
 .../{openssl => openssl10}/oe-ldflags.patch|   0
 .../openssl-1.0.2a-x32-asm.patch   |   0
 .../openssl/openssl10/openssl-c_rehash.sh  | 222 +
 .../openssl-fix-des.pod-error.patch|   0
 .../openssl-util-perlpath.pl-cwd.patch |   0
 .../openssl_fix_for_x32.patch  |   0
 .../openssl/{openssl => openssl10}/parallel.patch  |   0
 .../{openssl => openssl10}/ptest-deps.patch|   0
 .../ptest_makefile_deps.patch  |   0
 .../openssl/openssl10/run-ptest|   2 +
 .../{openssl => openssl10}/shared-libs.patch   |   0
 .../{openssl_1.0.2l.bb => openssl10_1.0.2l.bb} |   4 +-
 .../recipes-connectivity/openssl/openssl_1.1.0f.bb | 155 ++
 .../cryptodev/cryptodev-tests_1.9.bb   |   2 +-
 .../gstreamer/gstreamer1.0-plugins-bad.inc |   4 +-
 41 files changed, 495 insertions(+), 10 deletions(-)
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/0001-Remove-test-that-requires-running-as-non-root.patch
 create mode 100644 
meta/recipes-connectivity/openssl/openssl/0001-Take-linking-flags-from-LDFLAGS-env-var.patch
 mode change 100755 => 100644 
meta/recipes-connectivity/openssl/openssl/run-ptest
 rename meta/recipes-connectivity/openssl/{openssl.inc => openssl10.inc} (95%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/0001-Fix-build-with-clang-using-external-assembler.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/Makefiles-ptest.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/Use-SHA256-not-MD5-as-default-digest.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/configure-musl-target.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/configure-targets.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/c_rehash-compat.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/ca.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl => 
openssl10}/debian/debian-targets.patch (100%)
 rename meta/recipes-connectivity/openssl/{openssl 

[OE-core] [PATCH v5] kernel: Add support for multiple kernel packages

2017-08-08 Thread Haris Okanovic
Some distros may want to provide alternate kernel "flavors" via feeds or
within bootable images. For example, readily available builds which
provide certain diagnostic features can enable developers and testers to
more quickly resolve issues by avoiding lengthy kernel builds.

This change allows for building multiple flavors of the kernel and
module packages by templatizing kernel package names via a new
KERNEL_PACKAGE_NAME variable in kernel.bbclass. It defaults to the old
name of "kernel", but can be overridden by certain recipes providing
alternate kernel flavors.

To maintain compatibility, recipes providing alternate kernel flavors
cannot be the "preferred provider" for virtual/kernel. This is because
OE puts the preferred provider's build and source at
"tmp-glibc/work-shared/$MACHINE/kernel-build-artifacts/" and
"tmp-glibc/work-shared/$MACHINE/kernel-source/" instead of
"tmp-glibc/work/*/$PN/" like other recipes. Therefore, recipes using the
default KERNEL_PACKAGE_NAME="kernel" follows the old semantics -- build
in the old location and may be preferred provider -- while recipes using
all other KERNEL_PACKAGE_NAME's build from the normal WORKDIR and don't
provide "virtual/kernel".

Testing:
 1. Prepended `KERNEL_PACKAGE_NAME = "tiny-linux"` to
linux-yocto-tiny_4.9.bb so that it may build alongside
the main kernel.
 2. `bitbake linux-yocto linux-yocto-tiny` to build both kernel flavors.
 3. Verified image and modules IPKs exist for both:
tmp-glibc/deploy/ipk/qemux86/kernel-* for linux-yocto
tmp-glibc/deploy/ipk/qemux86/tiny-linux* for linux-yocto-tiny
 4. Verified linux-yocto is the "preferred provider", and was built in
shared directory: tmp-glibc/work-shared/qemux86/kernel-*
 5. Appended `CORE_IMAGE_BASE_INSTALL += "tiny-linux"` to
core-image-base.bb to include both kernel flavors.
 6. `bitbake core-image-base` to build an image.
 7. Verified image contains two bzImage's under /boot/, with
"yocto-standard" selected to boot via symlink.

Discussion thread:
http://lists.openembedded.org/pipermail/openembedded-core/2015-December/thread.html#114122

Signed-off-by: Ioan-Adrian Ratiu 
Signed-off-by: Gratian Crisan 
Signed-off-by: Haris Okanovic 
Coauthored-by: Gratian Crisan 
Coauthored-by: Haris Okanovic 
Coauthored-by: Josh Hernstrom 
---
[PATCH v2] Change STAGING_KERNEL_DIR and STAGING_KERNEL_BUILDDIR to the
"work" directory in alternate kernel builds, instead of "work-shared",
so
that the two builds don't clobber each other.

[PATCH v3] An updated version of this change rebased onto the current
OE-core master. Changes:
 - Remove PREFERRED_PROVIDER check in linux-yocto.inc in alternate
   kernel builds, since alternate kernels aren't the
   PREFERRED_PROVIDER for virtual/kernel by definition.
 - Remove "virtual/kernel" from PROVIDES in alternate kernel builds.

[PATCH v4] Another rebase onto master; no functional change.
Improved description and testing steps.

[PATCH v5]
 - Warn when PN == KERNEL_PACKAGE_NAME (bug # 11905)
 - Add KERNEL_DEPLOYSUBDIR to avoid DEPLOYDIR collisions

https://github.com/harisokanovic/openembedded-core/tree/dev/hokanovi/multi-kernel-packages-v5
---
 meta/classes/kernel-module-split.bbclass  |   9 ++-
 meta/classes/kernel.bbclass   | 114 +++---
 meta/conf/documentation.conf  |   1 +
 meta/recipes-kernel/linux/linux-dtb.inc   |   2 +-
 meta/recipes-kernel/linux/linux-yocto.inc |   2 +-
 5 files changed, 81 insertions(+), 47 deletions(-)

diff --git a/meta/classes/kernel-module-split.bbclass 
b/meta/classes/kernel-module-split.bbclass
index 1035525dac..9716c5937b 100644
--- a/meta/classes/kernel-module-split.bbclass
+++ b/meta/classes/kernel-module-split.bbclass
@@ -30,7 +30,7 @@ do_install_append() {
 
 PACKAGESPLITFUNCS_prepend = "split_kernel_module_packages "
 
-KERNEL_MODULES_META_PACKAGE ?= "kernel-modules"
+KERNEL_MODULES_META_PACKAGE ?= "${KERNEL_PACKAGE_NAME}-modules"
 
 KERNEL_MODULE_PACKAGE_PREFIX ?= ""
 KERNEL_MODULE_PACKAGE_SUFFIX ?= "-${KERNEL_VERSION}"
@@ -129,16 +129,19 @@ python split_kernel_module_packages () {
postfix = format.split('%s')[1]
d.setVar('RPROVIDES_' + pkg, pkg.replace(postfix, ''))
 
+kernel_package_name = d.getVar("KERNEL_PACKAGE_NAME", True)
+kernel_version = d.getVar("KERNEL_VERSION", True)
+
 module_regex = '^(.*)\.k?o$'
 
 module_pattern_prefix = d.getVar('KERNEL_MODULE_PACKAGE_PREFIX')
 module_pattern_suffix = d.getVar('KERNEL_MODULE_PACKAGE_SUFFIX')
-module_pattern = module_pattern_prefix + 'kernel-module-%s' + 
module_pattern_suffix
+module_pattern = module_pattern_prefix + kernel_package_name + 
'-module-%s' + module_pattern_suffix
 
 postinst = d.getVar('pkg_postinst_modules')
 postrm = d.getVar('pkg_postrm_modules')
 
-modules = do_split_packages(d, 

Re: [OE-core] [PATCH 01/10] oeqa/targetcontrol.py: simplify checking for qemu_use_kvm

2017-08-08 Thread Richard Purdie
On Mon, 2017-07-31 at 02:50 -0700, Robert Yang wrote:
> The "if qemu_use_kvm" is not needed.
> 
> Signed-off-by: Robert Yang 
> ---
>  meta/lib/oeqa/targetcontrol.py | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/lib/oeqa/targetcontrol.py
> b/meta/lib/oeqa/targetcontrol.py
> index 3255e3a5c63..11e6c820e85 100644
> --- a/meta/lib/oeqa/targetcontrol.py
> +++ b/meta/lib/oeqa/targetcontrol.py
> @@ -132,9 +132,8 @@ class QemuTarget(BaseTarget):
>  dump_host_cmds = d.getVar("testimage_dump_host")
>  dump_dir = d.getVar("TESTIMAGE_DUMP_DIR")
>  qemu_use_kvm = d.getVar("QEMU_USE_KVM")
> -if qemu_use_kvm and \
> -   (qemu_use_kvm == "True" and "x86" in d.getVar("MACHINE") or \
> -d.getVar("MACHINE") in qemu_use_kvm.split()):
> +if qemu_use_kvm == "True" and "x86" in d.getVar("MACHINE") or \
> +d.getVar("MACHINE") in qemu_use_kvm.split():
>  use_kvm = True
>  else:
>  use_kvm = False
> 

It is needed since qemu_use_kvm could be None and None.split() will
cause an error.

Cheers,

Richard
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH] ca-certificates: update to 20170717

2017-08-08 Thread Alexander Kanavin
Upstream lacks a tag for this release, so make it a PR bump.

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-support/ca-certificates/ca-certificates_20161130.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb 
b/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb
index 42088b98994..9a80f433711 100644
--- a/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb
+++ b/meta/recipes-support/ca-certificates/ca-certificates_20161130.bb
@@ -13,7 +13,8 @@ DEPENDS_class-native = "openssl-native"
 DEPENDS_class-nativesdk = "ca-certificates-native openssl-native"
 PACKAGE_WRITE_DEPS += "ca-certificates-native"
 
-SRCREV = "61b70a1007dc269d56881a0d480fc841daacc77c"
+SRCREV = "adc13592b55ef00450412d61a2145d162a4afb19"
+PR = "r20170717"
 
 SRC_URI = "git://anonscm.debian.org/collab-maint/ca-certificates.git \
file://0002-update-ca-certificates-use-SYSROOT.patch \
-- 
2.13.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH v3 2/2] sstatetests: limit the number of signature comparisons when differ

2017-08-08 Thread Burton, Ross
On 7 August 2017 at 22:33, 
wrote:

> From: Leonardo Sandoval 
>
> For perfomance reasons, limit the number of signature comparisons when
> stamps differ. The limit set is hardcoded to 20.
>
> [YOCTO #11651]
>
> Signed-off-by: Leonardo Sandoval  linux.intel.com>
> ---
>  meta/lib/oeqa/selftest/cases/sstatetests.py | 40
> +++--
>  1 file changed, 26 insertions(+), 14 deletions(-)
>
> diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py
> b/meta/lib/oeqa/selftest/cases/sstatetests.py
> index 0b36027918..6298443a18 100644
> --- a/meta/lib/oeqa/selftest/cases/sstatetests.py
> +++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
> @@ -458,6 +458,25 @@ http_proxy = "http://example.com/;
>  base = os.sep.join(root.rsplit(os.sep, 2)[-2:] +
> [name])
>  f[base] = shash
>  return f
> +
> +def compare_sigfiles(files, files1, files2, compare=False):
> +for k in files:
> +if k in files1 and k in files2:
> +i_sigfile += 1
>

Surely this is going to produce an i_sigfile is not defined error?

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH v4 0/8] support profile-optimized build for Python

2017-08-08 Thread Markus Lehtonen
Fourth attempt on enabling profile-guided-optimization (PGO) for Python.

Changes since v3:
- rebased on latest oe-core (with Python v3.5.3)
- typo in assignment of PYTHON3_PROFILE_TASK_DEFAULT fixed
- task dependencies of python-pgo-image altered to allow do_profile task to be
  run

The following changes since commit a5bb13a5d7d7a668ca61da6b17884e3b05b95355:

  python: don't include -tests with modules (2017-08-03 11:14:04 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib marquiz/fixes-9338
  
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=marquiz/fixes-9338

Markus Lehtonen (8):
  python3-native: support profile optimized build
  python3: fix depends of python3-tests
  python3: add python3-profile-opt recipe
  devtools/images: add python-pgo-image
  python3: support profile optimized build
  python3: fix profile-optimized build of modules
  python3: add python3-tools subpackage
  python3: remove two setup.py cross-compile hacks

 meta/recipes-devtools/images/python-pgo-image.bb   | 92 ++
 .../python/python-3.5-manifest.inc | 10 ++-
 .../python/python3-native_3.5.3.bb |  9 +++
 meta/recipes-devtools/python/python3-profile-opt   |  1 +
 .../python/python3-profile-opt_3.5.3.bb| 15 
 .../python3/0001-cross-compile-support.patch   |  9 ---
 ...efile-add-install_generate_profile-target.patch | 25 ++
 ...-CFLAGS-for-extensions-when-cross-compili.patch | 56 +
 .../python3-setup.py-no-host-headers-libs.patch| 33 
 .../setup.py-find-libraries-in-staging-dirs.patch  | 30 ---
 meta/recipes-devtools/python/python3_3.5.3.bb  | 58 ++
 11 files changed, 246 insertions(+), 92 deletions(-)
 create mode 100644 meta/recipes-devtools/images/python-pgo-image.bb
 create mode 12 meta/recipes-devtools/python/python3-profile-opt
 create mode 100644 meta/recipes-devtools/python/python3-profile-opt_3.5.3.bb
 create mode 100644 
meta/recipes-devtools/python/python3/Makefile-add-install_generate_profile-target.patch
 create mode 100644 
meta/recipes-devtools/python/python3/Use-correct-CFLAGS-for-extensions-when-cross-compili.patch
 delete mode 100644 
meta/recipes-devtools/python/python3/python3-setup.py-no-host-headers-libs.patch
 delete mode 100644 
meta/recipes-devtools/python/python3/setup.py-find-libraries-in-staging-dirs.patch

-- 
2.12.3

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] qemux86 qemux86-64: Enable pci

2017-08-08 Thread Jussi Kukkonen
This patch is in the master-next branch: that's a good indication it'll
move to master when master is next updated (assuming no problems come up in
testing).

  Jussi

On 8 August 2017 at 13:53, He Zhe  wrote:

> Ping.
>
> On 2017年07月31日 21:11, zhe...@windriver.com wrote:
> > From: He Zhe 
> >
> > lspci and some other software require "pci" in MACHINE_FEATURES and PCI
> > is valid in the qemux86* context.
> >
> > Signed-off-by: He Zhe 
> > ---
> >  meta/conf/machine/qemux86-64.conf | 2 +-
> >  meta/conf/machine/qemux86.conf| 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/conf/machine/qemux86-64.conf
> b/meta/conf/machine/qemux86-64.conf
> > index 4f30033..9f78191 100644
> > --- a/meta/conf/machine/qemux86-64.conf
> > +++ b/meta/conf/machine/qemux86-64.conf
> > @@ -28,7 +28,7 @@ XSERVER = "xserver-xorg \
> > xserver-xorg-module-libint10 \
> > "
> >
> > -MACHINE_FEATURES += "x86"
> > +MACHINE_FEATURES += "x86 pci"
> >
> >  MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
> >
> > diff --git a/meta/conf/machine/qemux86.conf b/meta/conf/machine/
> qemux86.conf
> > index e232947..d778fa7 100644
> > --- a/meta/conf/machine/qemux86.conf
> > +++ b/meta/conf/machine/qemux86.conf
> > @@ -27,7 +27,7 @@ XSERVER = "xserver-xorg \
> > xserver-xorg-module-libint10 \
> > "
> >
> > -MACHINE_FEATURES += "x86"
> > +MACHINE_FEATURES += "x86 pci"
> >
> >  MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
> >
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [PATCH] qemux86 qemux86-64: Enable pci

2017-08-08 Thread He Zhe
Ping.

On 2017年07月31日 21:11, zhe...@windriver.com wrote:
> From: He Zhe 
>
> lspci and some other software require "pci" in MACHINE_FEATURES and PCI
> is valid in the qemux86* context.
>
> Signed-off-by: He Zhe 
> ---
>  meta/conf/machine/qemux86-64.conf | 2 +-
>  meta/conf/machine/qemux86.conf| 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/conf/machine/qemux86-64.conf 
> b/meta/conf/machine/qemux86-64.conf
> index 4f30033..9f78191 100644
> --- a/meta/conf/machine/qemux86-64.conf
> +++ b/meta/conf/machine/qemux86-64.conf
> @@ -28,7 +28,7 @@ XSERVER = "xserver-xorg \
> xserver-xorg-module-libint10 \
> "
>  
> -MACHINE_FEATURES += "x86"
> +MACHINE_FEATURES += "x86 pci"
>  
>  MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
>  
> diff --git a/meta/conf/machine/qemux86.conf b/meta/conf/machine/qemux86.conf
> index e232947..d778fa7 100644
> --- a/meta/conf/machine/qemux86.conf
> +++ b/meta/conf/machine/qemux86.conf
> @@ -27,7 +27,7 @@ XSERVER = "xserver-xorg \
> xserver-xorg-module-libint10 \
> "
>  
> -MACHINE_FEATURES += "x86"
> +MACHINE_FEATURES += "x86 pci"
>  
>  MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d"
>  

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 2/2] diffstat: exclude aclocal

2017-08-08 Thread Ross Burton
Instead of moving aclocal.m4 to acinclude.m4 in a custom do_configure, simply
tell autoreconf not to run aclocal.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/diffstat/diffstat_1.61.bb | 9 ++---
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/meta/recipes-devtools/diffstat/diffstat_1.61.bb 
b/meta/recipes-devtools/diffstat/diffstat_1.61.bb
index 583b387e957..f8b7b06cf24 100644
--- a/meta/recipes-devtools/diffstat/diffstat_1.61.bb
+++ b/meta/recipes-devtools/diffstat/diffstat_1.61.bb
@@ -18,14 +18,9 @@ S = "${WORKDIR}/diffstat-${PV}"
 
 inherit autotools gettext ptest
 
-LDFLAGS += "${TOOLCHAIN_OPTIONS}"
+EXTRA_AUTORECONF += "--exclude=aclocal"
 
-do_configure () {
-   if [ ! -e ${S}/acinclude.m4 ]; then
-   mv ${S}/aclocal.m4 ${S}/acinclude.m4
-   fi
-   autotools_do_configure
-}
+LDFLAGS += "${TOOLCHAIN_OPTIONS}"
 
 do_install_ptest() {
cp -r ${S}/testing ${D}${PTEST_PATH}
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[OE-core] [PATCH 1/2] diffstat: use HTTP mirror for SRC_URI

2017-08-08 Thread Ross Burton
The Invisible Mirror FTP service is currently down, and FTP is horrible, so
switch to the HTTP mirror.

Signed-off-by: Ross Burton 
---
 meta/recipes-devtools/diffstat/diffstat_1.61.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/diffstat/diffstat_1.61.bb 
b/meta/recipes-devtools/diffstat/diffstat_1.61.bb
index 0ec41c3abfd..583b387e957 100644
--- a/meta/recipes-devtools/diffstat/diffstat_1.61.bb
+++ b/meta/recipes-devtools/diffstat/diffstat_1.61.bb
@@ -7,7 +7,7 @@ SECTION = "devel"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://install-sh;endline=42;md5=b3549726c1022bee09c174c72a0ca4a5"
 
-SRC_URI = "ftp://invisible-island.net/diffstat/diffstat-${PV}.tgz \
+SRC_URI = "http://invisible-mirror.net/archives/${BPN}/${BP}.tgz \
file://run-ptest \
 "
 
-- 
2.11.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


Re: [OE-core] [oe-commits] [openembedded-core] 04/09: image/rm_work: Promote do_image_complete to be more sstate like

2017-08-08 Thread Martin Jansa
With this change I'm seeing all images failing with:

| DEBUG: Executing shell function do_rm_work
| mv:
?1.0-r0.4.0.do_image_complete.fb2421734f998a50c93250deb80d3024.MACHINE? and
?1.0-r0.4.0.do_image_complete.fb2421734f998a50c93250deb80d3024.MACHINE
? are the same file
| WARNING: exit code 1 from a shell command.

I'll check what's special on my config (what's matched in $j) that this
issue wasn't triggered on autobuilder, but any hints would be welcome as
well.

On Mon, Jul 31, 2017 at 4:14 PM,  wrote:

> This is an automated email from the git hooks/post-receive script.
>
> rpurdie pushed a commit to branch master
> in repository openembedded-core.
>
> commit 2ff9d40dc88d43567472218cf3d3faf414398c71
> Author: Richard Purdie 
> AuthorDate: Sun Jul 30 16:06:57 2017 +0100
>
> image/rm_work: Promote do_image_complete to be more sstate like
>
> We relied on the missing do_image_complete_setscene task to ensure the
> dummy
> sstate tarball that was created would never be used. This lead to its
> own
> issues and a better fix for SSTATE_SKIP_CREATION has now been merged.
>
> We can therefore make do_image_complete look like a more standard
> sstate
> task which means image generation doesn't keep rerunning when using
> rm_work.
>
> We do need to turn do_image_complete's stamp into an sstate version to
> handle this (it otherwise matches the do_image_* glob).
>
> Signed-off-by: Richard Purdie 
> ---
>  meta/classes/image.bbclass   | 4 
>  meta/classes/rm_work.bbclass | 5 +
>  2 files changed, 9 insertions(+)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 0885fdb..696aacd 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -289,6 +289,10 @@ do_image_complete[sstate-inputdirs] =
> "${IMGDEPLOYDIR}"
>  do_image_complete[sstate-outputdirs] = "${DEPLOY_DIR_IMAGE}"
>  do_image_complete[stamp-extra-info] = "${MACHINE}"
>  addtask do_image_complete after do_image before do_build
> +python do_image_complete_setscene () {
> +sstate_setscene(d)
> +}
> +addtask do_image_complete_setscene
>
>  # Add image-level QA/sanity checks to IMAGE_QA_COMMANDS
>  #
> diff --git a/meta/classes/rm_work.bbclass b/meta/classes/rm_work.bbclass
> index 2a4e808..71c21a0 100644
> --- a/meta/classes/rm_work.bbclass
> +++ b/meta/classes/rm_work.bbclass
> @@ -61,6 +61,11 @@ do_rm_work () {
>  i=dummy
>  break
>  ;;
> +*do_image_complete*)
> +mv $i `echo $i | sed -e "s#${j}#${j}_setscene#"`
> +i=dummy
> +break
> +;;
>  *do_rootfs*|*do_image*|*do_bootimg*|*do_bootdirectdisk*|*
> do_vmimg*|*do_write_qemuboot_conf*)
>  i=dummy
>  break
>
> --
> To stop receiving notification emails like this one, please contact
> the administrator of this repository.
> --
> ___
> Openembedded-commits mailing list
> openembedded-comm...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core