**** BEGIN LOGGING AT Wed Oct 11 03:00:02 2017
Oct 11 07:11:55 <wouterstreamit> I have a board with a chip of which I only have a binary driver - how can I have yocto use this driver (stored in kernel/drivers/.../[chip name].o in the compilation?
Oct 11 07:48:43 <rheagar> Hi , when i try enable read-only-rootfs feature, i meet a warning on "lib32-gio-querymodules: Invalid ELF image for this architecture", seems some module use lib32-glib, when do update_gio_module_cache-lib32 failed , does anyone has some idea on this ? thanks
Oct 11 07:49:39 <rheagar> for read-only-rootfs, any modules can not configured offline will lead to fail.
Oct 11 12:13:28 <wouterstreamit> I am trying to use openbox instead of matchbox, I can install it fine but matchbox still starts. If I change /usr/bin/x-session-manager to start openbox instead of matchbox it works. How can I not install matchbox and configure /usr/bin/x-session-manager to start openbox instead?
Oct 11 12:15:37 <cpf> hello. I would like to add a file in the rootfs. (lets say in /home/user1/) Where do I have to specify or copy the file ? Do I have to write something in the local.conf ? Is it the same thing if I want to copy a firmware file for a USB dongle ?
Oct 11 12:16:16 <cpf> (this is considering that I am building an core-image-base..)
Oct 11 12:19:17 <LetoThe2nd> cpf: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#packaging-externally-produced-binaries
Oct 11 12:20:03 <LetoThe2nd> wouterstreamit: find out what pulls in matchbox? like, inspect bitbake -e $YOURIMAGE
Oct 11 12:26:37 <wouterstreamit> LetoThe2nd: matchbox comes from packagegroup-core-x11-base - I think it is included by a line IMAGE_FEATURES += "${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'x11-base', '', d)}" in my base image
Oct 11 12:27:49 <LetoThe2nd> wouterstreamit: there is the possibility then that it gets pulled through something like virtual/windowmanager or such, then you can override it. otherwise you'll have to rip out that packagegroup and manually replace it with your own selection
Oct 11 12:30:30 <wouterstreamit> So if I manage to not install matchbox, is the openbox recipe smart enough to autostart instead of it?
Oct 11 12:32:31 <LetoThe2nd> no idea
Oct 11 18:52:00 <open-nandra> hi all
Oct 11 18:52:11 <open-nandra> I' building small system based on pyro
Oct 11 18:52:27 <open-nandra> I've added few python3 custom programs  + dependencies
Oct 11 18:52:38 <open-nandra> some of python dependencies was from 2.7
Oct 11 18:53:01 <open-nandra> when I run program it cannot import some packages as IMO they are not in python3.5
Oct 11 18:53:03 <open-nandra> subdir
Oct 11 18:53:15 <open-nandra> is there any was how to workaround this?
Oct 11 18:53:20 <open-nandra> maybe some pythonpath poking?
Oct 11 19:00:10 <lsandov> open-nandra: but how can you expect that python3 process will take python2 code?  I believe you need to create the python3 versions of those dependencies
Oct 11 19:00:39 <open-nandra> lsandov: Idon't want to hear that :), but thanks
Oct 11 19:00:41 <open-nandra> will do
Oct 11 19:01:33 <rburton> open-nandra: py2 and py3 are only compatible if the code is very carefully written
Oct 11 19:01:59 <open-nandra> rburton: I need to use python-daemon for which exist recipe
Oct 11 19:02:10 <open-nandra> so I probably need to create python3-daemon version
Oct 11 19:02:47 <rburton> yes
Oct 11 19:03:00 <rburton> assuming its been ported to py3 upstream, that's mostly trivial
Oct 11 19:03:18 <open-nandra> rburton: ok thanks I'll look
Oct 11 19:03:50 <rburton> open-nandra: https://pypi.python.org/pypi/python-daemon-3K/1.5.8
Oct 11 19:04:37 <open-nandra> rburton: ok but I have also rpi-gpio
Oct 11 19:04:44 <open-nandra> + python-serial
Oct 11 19:07:56 <lsandov> open-nandra: migrating modules are easy, the hard part are the interpreters
Oct 11 19:08:16 <lsandov> *is
Oct 11 19:11:36 <open-nandra> lsandov: ok I'll try
Oct 11 19:11:40 <open-nandra> thanks for all info
Oct 11 20:52:14 <majuk> So I am using dropbear and I need sftp. I see references to openssh-sftp-server as if it were a recipe [at least around the time of the fido release], but I can find no evidence of that recipe. Any pointers here?
Oct 11 20:52:38 <majuk> My alternative path is dissecting the openssh recipe which is gonna get ugly in a hurry.
Oct 11 21:16:57 <malinus> majuk: try searching here http://layers.openembedded.org/layerindex/branch/master/recipes/
Oct 11 21:17:43 <majuk> malinus: Yea, only get openssh and it's package group
Oct 11 21:17:51 <majuk> Which makes me think it wasn't actually a package.
Oct 11 21:17:58 <majuk> s/package/recipe
Oct 11 21:18:14 <majuk> Thanks though.
Oct 11 21:24:08 <kergoth> majuk: there's an sftp package that comes out of hte openssh recipe, you can install it alongside dropbear afaik
Oct 11 21:27:32 <majuk> kergoth: Thanks. That's gonna be the road I hoe when I decide if this is a viable solution.
Oct 11 23:37:54 <Tartarus> kergoth: Sanity check please?  What's done in https://git.automotivelinux.org/AGL/meta-agl/tree/meta-agl/recipes-graphics/wayland/weston-ini-conf.bb#n26 results in WESTONSECTION (and in turn a number of other variable-with-flags) not ending up in the signature state.  This is a 'feature' and the resolution is to use do_...[vardeps] to track them in turn, yes?
Oct 11 23:38:03 <Tartarus> Or is there something I'm missing / some better way to do that?
Oct 11 23:38:25 <Tartarus> (Setting aside the merits of making a weston.ini file that way)
Oct 12 00:34:25 <jg_> ccccccgeljfeelebvlhukvvhhekrckclefvfftbljruf
**** ENDING LOGGING AT Thu Oct 12 03:00:01 2017