Re: [yocto] Metadata is missing in some Python packages

2019-04-09 Thread Guenther Meyer 
On Fri, 5 Apr 2019 18:17:43 +0100
"Burton, Ross"  wrote:

> What metadata in particular do you refer to?

The *egg-info folders and everything contained in them, especially
the files PKG-INFO or METADATA. The recipes are basically identical.

Some packages have it, some not:

Django-2.1.7-py3.5.egg-info
EasyProcess-0.2.5-py3.5.egg-info
HelperSDT
HelperSDT-0.1.0-py3.5.egg-info
OpenSSL
PyHamcrest-1.9.0-py3.5.egg-info
PySocks-1.6.8-py3.5.egg-info
PyVirtualDisplay-0.2.1-py3.5.egg-info
Twisted-0.0.0-py3.5.egg-info
aioredis
aioredis-1.2.0-py3.5.egg-info
asgiref
asgiref-2.3.2-py3.5.egg-info
asn1crypto
asn1crypto-0.24.0-py3.5.egg-info
async_timeout
async_timeout-3.0.1-py3.5.egg-info
attr
attrs-18.1.0-py3.5.egg-info
autobahn
autobahn-19.1.1-py3.5.egg-info
behave
behave-1.2.6-py3.5.egg-info
can
certifi
certifi-2018.8.13-py3.5.egg-info
cffi
cffi-1.11.5-py3.5.egg-info
channels
channels-2.1.7-py3.5.egg-info
channels_redis
channels_redis-2.3.2-py3.5.egg-info
chardet
chardet-3.0.4-py3.5.egg-info
click
click-6.7-py3.5.egg-info
constantly
constantly-15.1.0-py3.5.egg-info
cryptography
cryptography-2.3-py3.5.egg-info
daphne
daphne-2.2.5-py3.5.egg-info
django
django_model_utils-3.1.2-py3.5.egg-info
easyprocess
hamcrest
hiredis
hiredis-1.0.0-py3.5.egg-info
idna
idna-2.7-py3.5.egg-info
incremental
incremental-17.5.0-py3.5.egg-info
model_utils
msgpack
msgpack_python-0.5.6-py3.5.egg-info
ndg
ndg_httpsclient-0.5.1-py3.5.egg-info
parse-1.8.4-py3.5.egg-info
parse_type
parse_type-0.4.2-py3.5.egg-info
ply
ply-3.11-py3.5.egg-info
psutil
psutil-5.4.6-py3.5.egg-info
psycopg2
psycopg2-2.7.5-py3.5.egg-info
pyOpenSSL-18.0.0-py3.5.egg-info
pyasn1
pyasn1-0.4.4-py3.5.egg-info
pycparser
pycparser-2.18-py3.5.egg-info
python_can-2.2.1-py3.5.egg-info
pytz
pytz-2018.5-py3.5.egg-info
pyvirtualdisplay
requests
requests-2.19.1-py3.5.egg-info
selenium
selenium-3.141.0-py3.5.egg-info
service_identity
service_identity-18.1.0-py3.5.egg-info
setuptools
setuptools-40.0.0-py3.5.egg-info
six-1.11.0-py3.5.egg-info
twisted
txaio
txaio-18.8.1-py3.5.egg-info
urllib3
urllib3-1.23-py3.5.egg-info
websocket
websocket_client-0.54.0-py3.5.egg-info
wrapt
wrapt-1.10.11-py3.5.egg-info
zope
zope.interface-4.5.0-py3.5.egg-info


-- 
Summer-Hack-Session 2.8
http://session.pestilenz.org/session2/



pgpKSjlkN5AhL.pgp
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Metadata is missing in some Python packages

2019-04-09 Thread Burton, Ross 
Specifically for twisted, do you mean these files:

python3-twisted-core:
/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/PKG-INFO

/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/SOURCES.txt

/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/dependency_links.txt

/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/entry_points.txt

/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/not-zip-safe

/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/requires.txt

Ross

On Tue, 9 Apr 2019 at 08:49, Guenther Meyer  wrote:
>
> On Fri, 5 Apr 2019 18:17:43 +0100
> "Burton, Ross"  wrote:
>
> > What metadata in particular do you refer to?
>
> The *egg-info folders and everything contained in them, especially
> the files PKG-INFO or METADATA. The recipes are basically identical.
>
> Some packages have it, some not:
>
> Django-2.1.7-py3.5.egg-info
> EasyProcess-0.2.5-py3.5.egg-info
> HelperSDT
> HelperSDT-0.1.0-py3.5.egg-info
> OpenSSL
> PyHamcrest-1.9.0-py3.5.egg-info
> PySocks-1.6.8-py3.5.egg-info
> PyVirtualDisplay-0.2.1-py3.5.egg-info
> Twisted-0.0.0-py3.5.egg-info
> aioredis
> aioredis-1.2.0-py3.5.egg-info
> asgiref
> asgiref-2.3.2-py3.5.egg-info
> asn1crypto
> asn1crypto-0.24.0-py3.5.egg-info
> async_timeout
> async_timeout-3.0.1-py3.5.egg-info
> attr
> attrs-18.1.0-py3.5.egg-info
> autobahn
> autobahn-19.1.1-py3.5.egg-info
> behave
> behave-1.2.6-py3.5.egg-info
> can
> certifi
> certifi-2018.8.13-py3.5.egg-info
> cffi
> cffi-1.11.5-py3.5.egg-info
> channels
> channels-2.1.7-py3.5.egg-info
> channels_redis
> channels_redis-2.3.2-py3.5.egg-info
> chardet
> chardet-3.0.4-py3.5.egg-info
> click
> click-6.7-py3.5.egg-info
> constantly
> constantly-15.1.0-py3.5.egg-info
> cryptography
> cryptography-2.3-py3.5.egg-info
> daphne
> daphne-2.2.5-py3.5.egg-info
> django
> django_model_utils-3.1.2-py3.5.egg-info
> easyprocess
> hamcrest
> hiredis
> hiredis-1.0.0-py3.5.egg-info
> idna
> idna-2.7-py3.5.egg-info
> incremental
> incremental-17.5.0-py3.5.egg-info
> model_utils
> msgpack
> msgpack_python-0.5.6-py3.5.egg-info
> ndg
> ndg_httpsclient-0.5.1-py3.5.egg-info
> parse-1.8.4-py3.5.egg-info
> parse_type
> parse_type-0.4.2-py3.5.egg-info
> ply
> ply-3.11-py3.5.egg-info
> psutil
> psutil-5.4.6-py3.5.egg-info
> psycopg2
> psycopg2-2.7.5-py3.5.egg-info
> pyOpenSSL-18.0.0-py3.5.egg-info
> pyasn1
> pyasn1-0.4.4-py3.5.egg-info
> pycparser
> pycparser-2.18-py3.5.egg-info
> python_can-2.2.1-py3.5.egg-info
> pytz
> pytz-2018.5-py3.5.egg-info
> pyvirtualdisplay
> requests
> requests-2.19.1-py3.5.egg-info
> selenium
> selenium-3.141.0-py3.5.egg-info
> service_identity
> service_identity-18.1.0-py3.5.egg-info
> setuptools
> setuptools-40.0.0-py3.5.egg-info
> six-1.11.0-py3.5.egg-info
> twisted
> txaio
> txaio-18.8.1-py3.5.egg-info
> urllib3
> urllib3-1.23-py3.5.egg-info
> websocket
> websocket_client-0.54.0-py3.5.egg-info
> wrapt
> wrapt-1.10.11-py3.5.egg-info
> zope
> zope.interface-4.5.0-py3.5.egg-info
>
>
> --
> Summer-Hack-Session 2.8
> http://session.pestilenz.org/session2/
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Metadata is missing in some Python packages

2019-04-09 Thread Guenther Meyer 
On Tue, 9 Apr 2019 10:55:38 +0100
"Burton, Ross"  wrote:

> Specifically for twisted, do you mean these files:
> 
> python3-twisted-core:
> 
> /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/PKG-INFO
> 
> /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/SOURCES.txt
> 
> /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/dependency_links.txt
> 
> /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/entry_points.txt
> 
> /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/not-zip-safe
> 
> /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/requires.txt

yes, exactly.


-- 
Summer-Hack-Session 2.8
http://session.pestilenz.org/session2/



pgplAN_axDjBp.pgp
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Metadata is missing in some Python packages

2019-04-09 Thread Burton, Ross 
So for me they're in python3-twisted-core on target, and if you have
the right DEPENDS then it should be there for build time.

Ross

On Tue, 9 Apr 2019 at 11:03, Guenther Meyer  wrote:
>
> On Tue, 9 Apr 2019 10:55:38 +0100
> "Burton, Ross"  wrote:
>
> > Specifically for twisted, do you mean these files:
> >
> > python3-twisted-core:
> > 
> > /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/PKG-INFO
> > 
> > /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/SOURCES.txt
> > 
> > /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/dependency_links.txt
> > 
> > /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/entry_points.txt
> > 
> > /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/not-zip-safe
> > 
> > /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/requires.txt
>
> yes, exactly.
>
>
> --
> Summer-Hack-Session 2.8
> http://session.pestilenz.org/session2/
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] m4-mative: "Please port gnulib fseeko.c to your platform!"

2019-04-09 Thread Robert P. J. Day 
On Mon, 8 Apr 2019, Burton, Ross wrote:

> Looks like that bug in gnulib that broke m4 (and others) when glibc
> changed.
>
> Fixed upstream
> https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a718
> and oe-core master/thud/possibly sumo also carry the relevant patch
> for m4.
>
> If you're using older releases against a newer release then 1) this
> is why we have supported host distros and 2) the patch is easy to
> backport.

  so, to confirm what i thought, this is a bug in gnulib which
suggests i should dig through the build configuration to see where i
can, say, set a PREFERRED_VERSION of a newer version of gnulib that
no longer has tat bug? or, barring that, just add the appropriate
local patch on my end.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
 http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] m4-mative: "Please port gnulib fseeko.c to your platform!"

2019-04-09 Thread Burton, Ross 
On Tue, 9 Apr 2019 at 11:14, Robert P. J. Day  wrote:
>   so, to confirm what i thought, this is a bug in gnulib which
> suggests i should dig through the build configuration to see where i
> can, say, set a PREFERRED_VERSION of a newer version of gnulib that
> no longer has tat bug? or, barring that, just add the appropriate
> local patch on my end.

No, gnulib is a copy/paste library.  The bug was fixed in gnulib, and
new releases of m4 are fixed, but you'll need to cherry-pick the fix
from oe-core master (we apply the patch to our m4 recipe) back to
whatever stable branch you're using.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] m4-mative: "Please port gnulib fseeko.c to your platform!"

2019-04-09 Thread Robert P. J. Day 
On Tue, 9 Apr 2019, Burton, Ross wrote:

> On Tue, 9 Apr 2019 at 11:14, Robert P. J. Day  wrote:
> >   so, to confirm what i thought, this is a bug in gnulib which
> > suggests i should dig through the build configuration to see where i
> > can, say, set a PREFERRED_VERSION of a newer version of gnulib that
> > no longer has tat bug? or, barring that, just add the appropriate
> > local patch on my end.
>
> No, gnulib is a copy/paste library.  The bug was fixed in gnulib, and
> new releases of m4 are fixed, but you'll need to cherry-pick the fix
> from oe-core master (we apply the patch to our m4 recipe) back to
> whatever stable branch you're using.

  ah, got it, thanks.

rday
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Metadata is missing in some Python packages

2019-04-09 Thread Guenther Meyer 
On Tue, 9 Apr 2019 11:11:04 +0100
"Burton, Ross"  wrote:

> So for me they're in python3-twisted-core on target, and if you have
> the right DEPENDS then it should be there for build time.

I will have a look at this, when I'm back in the office again.
The thing is, I needed a newer version of twisted, so I did my own
recipe. But obviously it is not enough to let setuptools do the work.


-- 
Summer-Hack-Session 2.8
http://session.pestilenz.org/session2/



pgpUdOh2NGKsp.pgp
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Metadata is missing in some Python packages

2019-04-09 Thread Burton, Ross 
An upgrade should just be a matter of taking the meta-python recipe
and doing a version bump/checksum update.  If you've written a recipe
from scratch then you're probably missing some of the glue required.

Ross

On Tue, 9 Apr 2019 at 11:17, Guenther Meyer  wrote:
>
> On Tue, 9 Apr 2019 11:11:04 +0100
> "Burton, Ross"  wrote:
>
> > So for me they're in python3-twisted-core on target, and if you have
> > the right DEPENDS then it should be there for build time.
>
> I will have a look at this, when I'm back in the office again.
> The thing is, I needed a newer version of twisted, so I did my own
> recipe. But obviously it is not enough to let setuptools do the work.
>
>
> --
> Summer-Hack-Session 2.8
> http://session.pestilenz.org/session2/
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Anyone used uBlox EMMY-W1 and has patches?

2019-04-09 Thread JH 
Hi,

The Marvell firmware sd8887_uapsta_a2 seems diff to the current sd8887_uapsta.

Thanks.

- jupiter
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [sumo] [PATCH v1] systemd: fix musl compilation

2019-04-09 Thread akuster 



On 4/9/19 5:45 AM, Sinan Kaya wrote:
> On 3/29/2019 10:42 AM, Sinan Kaya wrote:
>> musl compilation has been broken since systemd: fix CVE-2018-6954.
>> Fixing this
>> by placing #ifdef for glob definition.
>>
>> Signed-off-by: Sinan Kaya
>
> I didn't see any comments here but I wanted to let everyone know that
> sumo-next branch is currently broken with MUSL unless this patch is
> applied.

After closer look, I don't the "Upstream-Status:" nor a signoff in the
patch being added in the bb file.

Does this issue affect later branches ?

- armin

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] dhcp and avahi package addition to image

2019-04-09 Thread Pandey, Kamal 
Hello,

I was trying to add avahi and dhcp  to my image. While running $bitbake dhcp 
avahi, everything is working fine but when I add these packages to packagegroup 
 or directly to the image recipe using EXTRA_IMAGE_INSTALL or 
IMAGE_INSTALL_append. It starts giving error.
The error  for avahi is shown below:
ERROR: core-image-special-pdm3-1.0-r0 do_rootfs: Could not invoke dnf. Command 
'/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/recipe-sysroot-native/usr/bin/dnf
 -y -c 
/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs/etc/dnf/dnf.conf
 
--setopt=reposdir=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs/etc/yum.repos.d
 
--repofrompath=oe-repo,/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/oe-rootfs-repo
 
--installroot=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs
 
--setopt=logdir=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/temp
 --nogpgcheck install packagegroup-pdm3-apps packagegroup-pdm3-qt 
packagegroup-core-tools-debug packagegroup-core-boot packagegroup-core-x11 
packagegroup-pdm3-base packagegroup-core-tools-profile packagegroup-pdm3-fonts 
base-passwd packagegroup-core-ssh-openssh shadow run-postinsts 
kernel-image-fitimage-4.14.79-yocto-standard' returned 1:
Added oe-repo repo from 
/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Tue 09 Apr 2019 01:49:20 PM UTC.
Error:
Problem: conflicting requests
  - nothing provides avahi needed by packagegroup-pdm3-apps-1.0-r1.noarch

ERROR: core-image-special-pdm3-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/temp/log.do_rootfs.12565
ERROR: Task 
(/home/iepl007/yocto_build/poky/../meta-pdm3-dev/meta-ifm-pdm3/recipes-core/images/core-image-special-pdm3.bb:do_rootfs)
 failed with exit code '1'


And the error for dhcp is shown below:


ERROR: Nothing RPROVIDES 'dhcp' (but 
/home/iepl007/yocto_build/poky/../meta-pdm3-dev/meta-ifm-pdm3/recipes-core/packagegroups/packagegroup-pdm3-app.bb
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp']
NOTE: Runtime target 'packagegroup-pdm3-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-pdm3-apps', 'dhcp']
ERROR: Required build target 'pdm3-special-swuimage' has no buildable providers.
Missing or unbuildable dependency chain was: ['pdm3-special-swuimage', 
'core-image-special-pdm3', 'packagegroup-pdm3-apps', 'dhcp']

Please provide a solution for this I don't want to clean my sstate-cache or the 
tmp directory. I am ready to debug the corrupted sstate if someone is 
experienced with sstate-cache.
Thanks
Kamal Pandey
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] dhcp and avahi package addition to image

2019-04-09 Thread Alexander Kanavin 
Most likely neither of these recipes actually provides a package named
'dhcp' or 'avahi'. Run 'bitbake -e avahi' and look for the PACKAGES
variable in the output, that would tell you the actual package names
that you can add to the image.

Alex

On Tue, 9 Apr 2019 at 16:16, Pandey, Kamal  wrote:
>
> Hello,
>
>
>
> I was trying to add avahi and dhcp  to my image. While running $bitbake dhcp 
> avahi, everything is working fine but when I add these packages to 
> packagegroup  or directly to the image recipe using EXTRA_IMAGE_INSTALL or 
> IMAGE_INSTALL_append. It starts giving error.
>
> The error  for avahi is shown below:
>
> ERROR: core-image-special-pdm3-1.0-r0 do_rootfs: Could not invoke dnf. 
> Command 
> '/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/recipe-sysroot-native/usr/bin/dnf
>  -y -c 
> /home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs/etc/dnf/dnf.conf
>  
> --setopt=reposdir=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs/etc/yum.repos.d
>  
> --repofrompath=oe-repo,/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/oe-rootfs-repo
>  
> --installroot=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs
>  
> --setopt=logdir=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/temp
>  --nogpgcheck install packagegroup-pdm3-apps packagegroup-pdm3-qt 
> packagegroup-core-tools-debug packagegroup-core-boot packagegroup-core-x11 
> packagegroup-pdm3-base packagegroup-core-tools-profile 
> packagegroup-pdm3-fonts base-passwd packagegroup-core-ssh-openssh shadow 
> run-postinsts kernel-image-fitimage-4.14.79-yocto-standard' returned 1:
>
> Added oe-repo repo from 
> /home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/oe-rootfs-repo
>
> Last metadata expiration check: 0:00:00 ago on Tue 09 Apr 2019 01:49:20 PM 
> UTC.
>
> Error:
>
> Problem: conflicting requests
>
>   - nothing provides avahi needed by packagegroup-pdm3-apps-1.0-r1.noarch
>
>
>
> ERROR: core-image-special-pdm3-1.0-r0 do_rootfs: Function failed: do_rootfs
>
> ERROR: Logfile of failure stored in: 
> /home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/temp/log.do_rootfs.12565
>
> ERROR: Task 
> (/home/iepl007/yocto_build/poky/../meta-pdm3-dev/meta-ifm-pdm3/recipes-core/images/core-image-special-pdm3.bb:do_rootfs)
>  failed with exit code '1'
>
>
>
>
>
> And the error for dhcp is shown below:
>
>
>
>
>
> ERROR: Nothing RPROVIDES 'dhcp' (but 
> /home/iepl007/yocto_build/poky/../meta-pdm3-dev/meta-ifm-pdm3/recipes-core/packagegroups/packagegroup-pdm3-app.bb
>  RDEPENDS on or otherwise requires it)
>
> NOTE: Runtime target 'dhcp' is unbuildable, removing...
>
> Missing or unbuildable dependency chain was: ['dhcp']
>
> NOTE: Runtime target 'packagegroup-pdm3-apps' is unbuildable, removing...
>
> Missing or unbuildable dependency chain was: ['packagegroup-pdm3-apps', 
> 'dhcp']
>
> ERROR: Required build target 'pdm3-special-swuimage' has no buildable 
> providers.
>
> Missing or unbuildable dependency chain was: ['pdm3-special-swuimage', 
> 'core-image-special-pdm3', 'packagegroup-pdm3-apps', 'dhcp']
>
>
>
> Please provide a solution for this I don’t want to clean my sstate-cache or 
> the tmp directory. I am ready to debug the corrupted sstate if someone is 
> experienced with sstate-cache.
>
> Thanks
>
> Kamal Pandey
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] shared cmake modules

2019-04-09 Thread Gabriele Zampieri 
Hi,

yes, following:

- cmake-modules.bb https://pastebin.com/5VqN9msS
- xxx-log.bb : https://pastebin.com/LYcPW3hc

The first one install the modules, thus is a dependency of many libraries,
the second one is a simple logger library that uses first's module

Thanks for your help,
Gabriele





Il giorno lun 8 apr 2019 alle ore 19:05 Henrik Lindblom <
henriklindbloms...@gmail.com> ha scritto:

> FILES_${PN}-dev = "${MODULES_DEST_PATH}/*"
>>
>
> Does your library recipe explicitly depend on -dev? Can you
> share the failing recipe?
>
> Cheers,
> Henrik
>
> On Wed, Apr 3, 2019 at 1:18 PM Gabriele Zampieri 
> wrote:
>
>> Hi all,
>>
>> I'm setting up a layer that will compile our applications and libraries.
>> All the applications are based on cmake and they share modules. Before
>> using yocto I kept the modules in /cmake (under version control)
>> alongside applications and libraries. With yocto I wrote a recipe that
>> checkout the module repo and install them in
>> "${STAGING_DATADIR}/cmake/Modules/". I took this path from
>> "meta/classes/cmake.bbclass". If i build the module target, I get the files
>> installed in the target recipe datadir. If I want to build a library (that
>> depends also on my modules recipe) the task do_configure fails because
>> cmake cannot find none of my include. Digging around I found that the
>> toolchain.cmake file points to a module location that doesn't exist in the
>> library workdir, but in module recipe (${STAGING_DATADIR}/cmake/Modules/).
>>
>> The module recipe looks like as follow:
>>
>> MODULES_DEST_PATH = "${STAGING_DATADIR}/cmake/Modules"
>> FILES_${PN}-dev = "${MODULES_DEST_PATH}/*"
>>
>> do_install() {
>> DEST_DIR=${MODULES_DEST_PATH}
>>
>> # Create the destination folder
>> install -d $DEST_DIR
>> install -m 0444 ${S}/my/module.cmake $DEST_DIR
>> ..
>> }
>>
>> So my question is: where should I install the shared modules
>> (MODULE_DEST_PATH int the above snippet)? and how to update the
>> CMAKE_MODULE_PATH properly to append that location?
>>
>> Thanks,
>> Gabriele
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW14'19

2019-04-09 Thread sjolley.yp.pm 
Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)

Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019 and it should
release today!

 

SWAT Team Rotation:

*   SWAT lead is currently: Amanda 
*   SWAT team rotation: Amanda -> Chen on Apr. 12, 2019
*   SWAT team rotation: Chen -> Armin Apr. 19, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   YP 2.8 Planning meeting Tuesday April 16nd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Bug Triage meeting Thursday April 11th at 7:30am PDT (
 https://zoom.us/j/454367603)

 

Key Status/Updates:

*   YP 2.7 M3 rc1 will be released today. The YP 2.7 M3 rc1 report is
summarized at

https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and
the results are at

https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/.
*   YP 2.5.3 and YP 2.6.2 stable releases were built and have been
submitted to QA
*   YP 2.6.2 is currently going through the QA process with YP 2.5.3
queued behind it. 
*   Process issues in the way ptest was being processed by QA have been
discovered which mean the previous ptest results are not comparable with the
new QA process. For consistency going forward we will be using the new QA
process as the definitive results and will be comparing for regressions
based upon these.
*   The "warrior" branches for 2.7 have been created and the metadata
updated, patches are being slowed in line with release stablisation with
increasingly critical fixes only.
*   The remaining things which are planned for YP 2.7 M4 before we have
the final 2.7 rc1 build are:

*   Upgrading -tiny to the 5.0 linux-yocto kernel (currently 4.18)
*   Removal of the 4.18 kernel
*   Fixing the python3 ptest timeout and result status issues
*   Fixing some of the util-linux ptest failures
*   Potentially integrating a key and long time puzzling pseudo issue
*   Integrating qemumips shutdown issues identified in the kernel
*   Continue to investigate python3 testsuite hang on 5.0+ kernels
(trying to get help upstream)

*   Worrying things which we don't have good plans for currently (mainly
lack of people to help with):

*   Intermittent autobuilder failures (fork running out of resources -
which resources?, oe-selftest intermittent issues, gpg signing resource
problems, occasional PR server failure and more)
*   Build-appliance testing issues (show up on each QA report across
multiple releases)
*   40% valgrind ptest failures
*   Known bitbake memory resident bugs
*   Other ptest failures

*   The 2.8 planning discussions are starting and there is a google doc
summarising the discussions so far:

https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJG
XbU/

If people are planning to work on specific things in 2.8 please let us know
so we can incorporate this into our plans. If you're interested in working
on anything in the document, please also let us know or talk with us in one
of the planning meetings.

 

Planned Releases for YP 2.7:

*   YP 2.7 M4 Cutoff was Apr. 1, 2019
*   YP 2.7 M4 Release Target is Apr. 26, 2019

 

Planned upcoming dot releases:

*   YP 2.5.3 (Sumo) is in QA.
*   YP 2.6.2 (Thud) is in QA.

 

Tracking Metrics:

*   WDD 2471 (last week 2442) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1553 (last week 1542
*   Patches in the Pending State: 655 (42%) [last week 656 (42%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [sumo] [PATCH v1] systemd: fix musl compilation

2019-04-09 Thread Sinan Kaya 

On 4/9/2019 7:49 AM, akuster wrote:

After closer look, I don't the "Upstream-Status:" nor a signoff in the
patch being added in the bb file.

Does this issue affect later branches ?


I can fix this. The issue was introduced while backporting a CVE patch
from debian.

So, we are fixing a problem by patching "the patch".

We'd squash this into the original CVE under normal circumstances but
original patch has been already checked in.

Can I assume that upstream status would be "inappropriate"?

I can add these tags once we reach to an agreement.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Eclipse support dropped with immediate effect

2019-04-09 Thread Richard Purdie 
I'm sorry to have to say this but the project is terminating its
official eclipse plugin support with immediate effect.

There is nobody willing to keep the builds going, fix bugs, port to new
eclipse releases or release the current plugin. This has been raised in
many forums, multiple times and nobody stepped up to help. With nobody
to do the work, we can't keep it going, it is that simple.

We'll be removing the automated testing of the eclipse plugin from the
autobuilder with immediate effect for all project releases.

Richard



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] poky-tiny: set 5.0 as the preferred kernel

2019-04-09 Thread bruce . ashfield 
From: Bruce Ashfield 

Updating poky-tiny to prefer 5.0 as the kernel version. Boot
tested against qemux86 and qemuarm. This removes the last user
of the 4.18 kernel, so we can queue it for removal from master.

Signed-off-by: Bruce Ashfield 
---
 meta-poky/conf/distro/poky-tiny.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-poky/conf/distro/poky-tiny.conf 
b/meta-poky/conf/distro/poky-tiny.conf
index 690cb0d5c9..243d492918 100644
--- a/meta-poky/conf/distro/poky-tiny.conf
+++ b/meta-poky/conf/distro/poky-tiny.conf
@@ -38,7 +38,7 @@ TCLIBC = "musl"
 # Distro config is evaluated after the machine config, so we have to explicitly
 # set the kernel provider to override a machine config.
 PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
-PREFERRED_VERSION_linux-yocto-tiny ?= "4.18%"
+PREFERRED_VERSION_linux-yocto-tiny ?= "5.0%"
 
 # We can use packagegroup-core-boot, but in the future we may need a new 
packagegroup-core-tiny
 #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"
-- 
2.19.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] shared cmake modules

2019-04-09 Thread Henrik Lindblom 
Your recipes seem a bit off. Doesn't bitbake complain about them at all?

In your logger library you declare a dependency to
"texa-cmake-modules", not "cmake-modules". Also, assuming the naming
conflict is only present in pastebin versions of your recipes, in
cmake-modules.bb you add all files under ${MODULES_DEST_PATH} to both
FILES_${PN}-dev and FILES_${PN}. These variables are used to populate
packages ${PN}-dev and ${PN} respectively. The order in which they
"grab" the files depends on PACKAGES, which has a default value of
"${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale
${PACKAGE_BEFORE_PN} ${PN}". Since ${PN}-dev appears before ${PN} in
this list, your cmake-modules package is most likely empty (I think
this should even yield a QA warning). Furthermore, your
MODULE_DEST_PATH incorrectly points to a path under ${STAGING_DATADIR}
which is also
where you install all your files in do_install(). Correct path for
installation is

${D}${datadir}/cmake/Modules

and for FILES

${datadir}/cmake/Modules/*

Depending on how you fix cmake-modules you likely need to change

DEPENDS = "cmake-modules boost"

to

DEPENDS = "cmake-modules-dev boost"

in your library recipe, adjusting for the actual name of your cmake
module.

See:
https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-D
https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-PACKAGES
https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#var-FILES

Cheers,
Henrik

On Tue, Apr 9, 2019 at 5:39 PM Gabriele Zampieri 
wrote:

> Hi,
>
> yes, following:
>
> - cmake-modules.bb https://pastebin.com/5VqN9msS
> - xxx-log.bb : https://pastebin.com/LYcPW3hc
>
> The first one install the modules, thus is a dependency of many libraries,
> the second one is a simple logger library that uses first's module
>
> Thanks for your help,
> Gabriele
>
>
>
>
>
> Il giorno lun 8 apr 2019 alle ore 19:05 Henrik Lindblom <
> henriklindbloms...@gmail.com> ha scritto:
>
>> FILES_${PN}-dev = "${MODULES_DEST_PATH}/*"
>>>
>>
>> Does your library recipe explicitly depend on -dev? Can you
>> share the failing recipe?
>>
>> Cheers,
>> Henrik
>>
>> On Wed, Apr 3, 2019 at 1:18 PM Gabriele Zampieri 
>> wrote:
>>
>>> Hi all,
>>>
>>> I'm setting up a layer that will compile our applications and libraries.
>>> All the applications are based on cmake and they share modules. Before
>>> using yocto I kept the modules in /cmake (under version control)
>>> alongside applications and libraries. With yocto I wrote a recipe that
>>> checkout the module repo and install them in
>>> "${STAGING_DATADIR}/cmake/Modules/". I took this path from
>>> "meta/classes/cmake.bbclass". If i build the module target, I get the files
>>> installed in the target recipe datadir. If I want to build a library (that
>>> depends also on my modules recipe) the task do_configure fails because
>>> cmake cannot find none of my include. Digging around I found that the
>>> toolchain.cmake file points to a module location that doesn't exist in the
>>> library workdir, but in module recipe (${STAGING_DATADIR}/cmake/Modules/).
>>>
>>> The module recipe looks like as follow:
>>>
>>> MODULES_DEST_PATH = "${STAGING_DATADIR}/cmake/Modules"
>>> FILES_${PN}-dev = "${MODULES_DEST_PATH}/*"
>>>
>>> do_install() {
>>> DEST_DIR=${MODULES_DEST_PATH}
>>>
>>> # Create the destination folder
>>> install -d $DEST_DIR
>>> install -m 0444 ${S}/my/module.cmake $DEST_DIR
>>> ..
>>> }
>>>
>>> So my question is: where should I install the shared modules
>>> (MODULE_DEST_PATH int the above snippet)? and how to update the
>>> CMAKE_MODULE_PATH properly to append that location?
>>>
>>> Thanks,
>>> Gabriele
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] problem with ruby

2019-04-09 Thread Khem Raj 
probably it has to be added to linker flags explicitly.

On Tue, Apr 9, 2019 at 12:00 AM Clement CHERBEIX
 wrote:
>
> It's done but I keep the same problem, I've add zlib in the PACKAGECONFIG too 
> without any result...
>
>
>
> 
> De : Khem Raj 
> Envoyé : lundi 8 avril 2019 20:04
> À : Clement CHERBEIX
> Cc : Yocto Project
> Objet : Re: [yocto] problem with ruby
>
> On Mon, Apr 8, 2019 at 9:44 AM Clément Cherbeix
>  wrote:
> >
> > Hello all,
> >
> > I’m trying to add the MIB mechanics in my yocto project, for that I use 
> > dadi (ruby depenedent) but I get an error when bitbake try to compile :
> >
> > DEBUG: Executing shell function do_compile
> >
> > ERROR:  Loading command: build (LoadError)
> >
> > cannot load such file -- zlib
> >
> > ERROR:  While executing gem ... (NoMethodError)
> >
> > undefined method `invoke_with_build_args' for nil:NilClass
> >
> > WARNING: 
> > /home/modem/tkh/build/tmp/work/x86_64-linux/libxml-ruby-native/2.8.0-r0/temp/run.do_compile.567:1
> >  exit 1 from 'LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" gem build $gem'
> >
> >
> >
> > I have tried to build the gem in an environment outside of Yocto and it was 
> > correct but when I try to do it in Yocto, I get my error.
> > Did someone have an idea on what to do ?
> > what is the recommended way of building ruby via gem in yocto ?
> >
> >
>
> It seems that it is using ruby-native but does not have zlib-native
> and it cant find this library. Can you add zlib to DEPENDS in ruby
> recipe and see if that helps.
>
> >
> > Here is my build environment :
> >
> > BB_VERSION   = "1.40.0"
> >
> > BUILD_SYS= "x86_64-linux"
> >
> > NATIVELSBSTRING  = "universal"
> >
> > TARGET_SYS   = "x86_64-poky-linux"
> >
> > DISTRO   = "poky"
> >
> > DISTRO_VERSION   = "2.6.1"
> >
> > TUNE_FEATURES= "m64 corei7"
> >
> >
> >
> > Thanks in advance !
> >
> >
> >
> > Clément C.
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Building rootFS fails [log_check]

2019-04-09 Thread Felix Lelchuk 

Hi,

I'm facing some strange problems trying to backport old 1.9 Ruby to Thud Poky.
All packages build fine but the image's do_rootfs fails with below message and
without any image winding up in tmp/deploy/images/:

-
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: my-image-1.0-r0 do_rootfs: [log_check] my-image: found 2 error messages 
in the logfile:
[log_check] D: create 040755  1 (   0,   0) 0 
/usr/share/ri/1.9.1/system/Net/HTTPExpectationFailed
[log_check] D: create 040755  1 (   0,   0) 0 
/usr/share/ri/1.9.1/system/Net/HTTPPreconditionFailed

ERROR: my-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/1.0-r0/temp/log.do_rootfs.19421
ERROR: Task (my-image.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 7927 tasks of which 7800 didn't need to be rerun 
and 1 failed.
-

I believe there are some QA-related heuristics in place which dislike the naming of the 
two mentioned files for they contain "Failed" in their filename. Unlike Thud, 
that used to work in Krogoth.

If this was a pure QA-warning I'd assume there is a switch to ignore it but it 
seems to be treated like an actual error.

I'd be glad to hear about the best way to proceed with this. Thank you!

Best Regards,

Felix Lelchuk

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [ANNOUNCEMENT] Milestone 3 for Yocto Project 2.7 (yocto-2.7_M3) now available

2019-04-09 Thread Tracy Graydon 
We are pleased to announce the third milestone release for Yocto Project 2.7 
(yocto-2.7_M3) is available for download now.

Download:

http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.7_M3/

poky: 753e2a0ede4449917c75353b57f13bbafe70fac8
oecore: 619a8ab875ee8e2914cd58947f342808d817833c
bitbake: e1f252408982a62485bbf874a01fd30a02aeed32
eclipse-poky-neon: cd86f167be58a11b289af4ef236b4adec57ec316
eclipse-poky-oxygen: 210c58c5a7147127f9c840718c6cd2a56e871718
meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575
meta-intel: c7c0e12c98cec527bcdcf26594d34bbeb16057c5
meta-mingw: 750706a3501ec9f5e3fa6dcbfb13a9027b6a875e
meta-qt3: 23d7543ebd7e82ba95cbe19043ae4229bdb3b6b1
meta-qt4: b37d8b93924b314df3591b4a61e194ff3feb5517

The YP 2.7 M3 rc1 report is summarized in the mailing list threads: 

QA Report: 
https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and the 
results are at 
Test Results: 
https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/
Build log: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/94
Release criteria: 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status#Milestone_3_-_Target_Mar._8.2C_2019


Thank you.

Tracy Graydon
Yocto Project Build and Release
tracy.gray...@intel.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [poky] [PATCH] poky-tiny: set 5.0 as the preferred kernel

2019-04-09 Thread akuster808 



On 4/9/19 9:09 PM, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield 
>
> Updating poky-tiny to prefer 5.0 as the kernel version. Boot
> tested against qemux86 and qemuarm. This removes the last user
> of the 4.18 kernel, so we can queue it for removal from master.
Thanks Bruce.

- Armin
>
> Signed-off-by: Bruce Ashfield 
> ---
>  meta-poky/conf/distro/poky-tiny.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-poky/conf/distro/poky-tiny.conf 
> b/meta-poky/conf/distro/poky-tiny.conf
> index 690cb0d5c9..243d492918 100644
> --- a/meta-poky/conf/distro/poky-tiny.conf
> +++ b/meta-poky/conf/distro/poky-tiny.conf
> @@ -38,7 +38,7 @@ TCLIBC = "musl"
>  # Distro config is evaluated after the machine config, so we have to 
> explicitly
>  # set the kernel provider to override a machine config.
>  PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-tiny"
> -PREFERRED_VERSION_linux-yocto-tiny ?= "4.18%"
> +PREFERRED_VERSION_linux-yocto-tiny ?= "5.0%"
>  
>  # We can use packagegroup-core-boot, but in the future we may need a new 
> packagegroup-core-tiny
>  #POKY_DEFAULT_EXTRA_RDEPENDS += "packagegroup-core-boot"

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] Eclipse support dropped with immediate effect

2019-04-09 Thread akuster808 



On 4/9/19 8:52 PM, Richard Purdie wrote:
> I'm sorry to have to say this but the project is terminating its
> official eclipse plugin support with immediate effect.

Does this affect the stable branches as well?

- armin
>
> There is nobody willing to keep the builds going, fix bugs, port to new
> eclipse releases or release the current plugin. This has been raised in
> many forums, multiple times and nobody stepped up to help. With nobody
> to do the work, we can't keep it going, it is that simple.
>
> We'll be removing the automated testing of the eclipse plugin from the
> autobuilder with immediate effect for all project releases.
>
> Richard
>
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [sumo] [PATCH v1] systemd: fix musl compilation

2019-04-09 Thread akuster808 



On 4/9/19 8:44 PM, Sinan Kaya wrote:
> On 4/9/2019 7:49 AM, akuster wrote:
>> After closer look, I don't the "Upstream-Status:" nor a signoff in the
>> patch being added in the bb file.
>>
>> Does this issue affect later branches ?
>
> I can fix this. The issue was introduced while backporting a CVE patch
> from debian.
>
> So, we are fixing a problem by patching "the patch".
Ah, sorry that didn't register.
>
> We'd squash this into the original CVE under normal circumstances but
> original patch has been already checked in.
>
> Can I assume that upstream status would be "inappropriate"?
Its not applicable in this case.

Maybe a note for the patch and your signoff seems more than enough
unless the broader community has an issue with that. .

thanks,
Armin
>
> I can add these tags once we reach to an agreement.


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.5.3.rc3)

2019-04-09 Thread Jain, Sangeeta 
Hello All,

Intel and WR YP QA is now working on QA execution for YP build 2.5.3.RC3. We 
are planning to execute following tests for this cycle:

OEQA-Manual tests for following modules:
1.  SDK
2.  Eclipse-plugin
3.  Kernel
4.  Toaster
5.  Bitbake (oe-core)
6.  Build-appliance
7.  Crops
8.  Compliance-test
9.  Bsp-hw
10. Bsp-qemu

Runtime auto test for following platforms:

1.  MinnowTurbo 32bit
2.  MinnowTurbot 64 bit
3.  NUC 7
4.  NUC 6
5.  Edgerouter
6.  MPC8315e-rdb
7.  Beaglebone

Other auto tests:

1.  Qemu-selftest
2.  Qemu-meta-ide

ETA for completion is Thursday, 18 April.

Thanks & Regards,
Sangeeta Jain

>-Original Message-
>From: yocto-boun...@yoctoproject.org  On
>Behalf Of Poky Build User
>Sent: Thursday, 28 March, 2019 1:47 PM
>To: yocto@yoctoproject.org
>Cc: ota...@ossystems.com.br; Chan, Aaron Chun Yew
>; akuster...@gmail.com
>Subject: [yocto] QA notification for completed autobuilder build 
>(yocto-2.5.3.rc3)
>
>
>A build flagged for QA (yocto-2.5.3.rc3) was completed on the autobuilder and 
>is
>available at:
>
>
>https://autobuilder.yocto.io/pub/releases/yocto-2.5.3.rc3
>
>
>Build hash information:
>
>bitbake: c0af6c81f8d5487ea2cef54a78fd1cb1d0dc6520
>eclipse-poky-neon: cd86f167be58a11b289af4ef236b4adec57ec316
>eclipse-poky-oxygen: 210c58c5a7147127f9c840718c6cd2a56e871718
>meta-gplv2: d7687d404bbc9ba3f44ec43ea8828d9071033513
>meta-intel: ba5f7ecd26630b74b6338c1828847a64ab172453
>meta-mingw: 628dcfed62ce8dcc408e5b4a5e5c0aaa921b20ad
>meta-qt3: 02f273cba6c25f5cf20cb66d8a417a83772c3179
>meta-qt4: 8e791c40140460825956430ba86b6266fdec0a93
>oecore: 0a2db923fd17019d07d88204b355aa46590f0b97
>poky: 84b78df15ff77b2fe2aeb62fcaa265dce7ebfbbb
>
>
>
>This is an automated message from the Yocto Project Autobuilder
>Git: git://git.yoctoproject.org/yocto-autobuilder2
>Email: richard.pur...@linuxfoundation.org
>
>
>
>--
>___
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH 1/2] layer.conf: update to warrior release name series

2019-04-09 Thread kai.kang 
From: Kai Kang 

Sync with oe-core to update to warrior release name series.

Signed-off-by: Kai Kang 
---
 conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index 5fecac6..b10bd76 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -18,7 +18,7 @@ BBFILE_PRIORITY_selinux = "5"
 # cause compatibility issues with other layers
 LAYERVERSION_selinux = "1"
 
-LAYERSERIES_COMPAT_selinux = "thud"
+LAYERSERIES_COMPAT_selinux = "warrior"
 
 LAYERDEPENDS_selinux = " \
 core \
-- 
2.20.0

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH 2/2] setools: fix build failure with gcc 7

2019-04-09 Thread kai.kang 
From: Kai Kang 

Backport patch from setools upstream to fix build failure with GCC 7 due
to possible truncation of snprintf output. It could be reproduced on 64
bit bsps such as qemux86-64 and qemumips64 with configs:

  SELECTED_OPTIMIZATION = "${DEBUG_OPTIMIZATION}"
  DEBUG_BUILD = "1"

Signed-off-by: Kai Kang 
---
 ...e-with-GCC-7-due-to-possible-truncat.patch | 90 +++
 1 file changed, 74 insertions(+), 16 deletions(-)

diff --git 
a/recipes-security/setools/setools/Fix-build-failure-with-GCC-7-due-to-possible-truncat.patch
 
b/recipes-security/setools/setools/Fix-build-failure-with-GCC-7-due-to-possible-truncat.patch
index d0faba8..a5af041 100644
--- 
a/recipes-security/setools/setools/Fix-build-failure-with-GCC-7-due-to-possible-truncat.patch
+++ 
b/recipes-security/setools/setools/Fix-build-failure-with-GCC-7-due-to-possible-truncat.patch
@@ -1,6 +1,10 @@
-From 790d7a538f515d27d2390f1ef56c9871b107a346 Mon Sep 17 00:00:00 2001
-From: Steve Langasek 
-Date: Sun, 27 Aug 2017 21:28:40 -0700
+Upstream-Status: Backport 
[https://github.com/TresysTechnology/setools/commit/e41adf0]
+
+Signed-off-by: Kai Kang 
+
+From e41adf01647c695b80b112b337e76021bb9f30c3 Mon Sep 17 00:00:00 2001
+From: Laurent Bigonville 
+Date: Tue, 26 Sep 2017 15:15:30 +0200
 Subject: [PATCH] Fix build failure with GCC 7 due to possible truncation of
  snprintf output
 
@@ -15,33 +19,87 @@ libqpol/policy_extend.c:161:22: note: directive argument in 
the range [1, 429496
 snprintf(buff, 9, "@ttr%04zd", i + 1);
   ^~~
 
-Exceeding 10,000 attributes is necessarily going to result in collisions
-inserting into the hash table given this naming scheme, and we already error
-out on the first collision; but there will be holes since types are not
-handled the same as attributes.  Short of making backwards-incompatible
-changes to the entry names, this is probably the best way to fix this build
-failure while reducing the chances of a hash collision in the unlikely event
-that the hashtable is (nearly) full.
+Increase the size of the buffer to avoid collisions
 
 Closes: https://github.com/TresysTechnology/setools/issues/174
-Signed-off-by: Mark Hatle 
+Signed-off-by: Laurent Bigonville 
 ---
- libqpol/policy_extend.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
+ libqpol/policy_extend.c | 16 
+ 1 file changed, 8 insertions(+), 8 deletions(-)
 
 diff --git a/libqpol/policy_extend.c b/libqpol/policy_extend.c
-index 742819b..70e8f7c 100644
+index 742819b..739e184 100644
 --- a/libqpol/policy_extend.c
 +++ b/libqpol/policy_extend.c
+@@ -110,7 +110,7 @@ static int qpol_policy_remove_bogus_aliases(qpol_policy_t 
* policy)
+  *  Builds data for the attributes and inserts them into the policydb.
+  *  This function modifies the policydb. Names created for attributes
+  *  are of the form @ttr where value is the value of the attribute
+- *  as a four digit number (prepended with 0's as needed).
++ *  as a ten digit number (prepended with 0's as needed).
+  *  @param policy The policy from which to read the attribute map and
+  *  create the type data for the attributes. This policy will be altered
+  *  by this function.
+@@ -125,7 +125,7 @@ static int qpol_policy_build_attrs_from_map(qpol_policy_t 
* policy)
+   uint32_t bit = 0, count = 0;
+   ebitmap_node_t *node = NULL;
+   type_datum_t *tmp_type = NULL, *orig_type;
+-  char *tmp_name = NULL, buff[10];
++  char *tmp_name = NULL, buff[16];
+   int error = 0, retv;
+ 
+   INFO(policy, "%s", "Generating attributes for policy. (Step 4 of 5)");
+@@ -137,7 +137,7 @@ static int qpol_policy_build_attrs_from_map(qpol_policy_t 
* policy)
+ 
+   db = &policy->p->p;
+ 
+-  memset(&buff, 0, 10 * sizeof(char));
++  memset(&buff, 0, 16 * sizeof(char));
+ 
+   for (i = 0; i < db->p_types.nprim; i++) {
+   /* skip types */
 @@ -158,7 +158,7 @@ static int qpol_policy_build_attrs_from_map(qpol_policy_t 
* policy)
 * with this attribute */
/* Does not exist */
if (db->p_type_val_to_name[i] == NULL){
 -  snprintf(buff, 9, "@ttr%04zd", i + 1);
-+  snprintf(buff, 9, "@ttr%04zd", (i + 1) % 1);
++  snprintf(buff, 15, "@ttr%010zd", i + 1);
tmp_name = strdup(buff);
if (!tmp_name) {
error = errno;
+@@ -240,7 +240,7 @@ static int qpol_policy_build_attrs_from_map(qpol_policy_t 
* policy)
+  *  Builds data for empty attributes and inserts them into the policydb.
+  *  This function modifies the policydb. Names created for the attributes
+  *  are of the form @ttr where value is the value of the attribute
+- *  as a four digit number (prepended with 0's as needed).
++ *  as a ten digit number (prepended with 0's as needed).
+  *  @param policy The policy to which to add type data for attributes.
+  *  This policy