| 00:56.51 | *** join/#oe tgamblin (~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com) |
| 01:43.19 | *** join/#oe Leatherface (~leatherfa@helvetet.eu) |
| 04:10.24 | *** join/#oe davidlt (~davidlt@78-63-27-146.static.zebra.lt) |
| 05:01.23 | *** join/#oe infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 05:01.23 | *** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel |
| 07:19.21 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 07:20.26 | *** join/#oe jkridner|pd (~jkridner@pdpc/supporter/active/jkridner) |
| 08:31.14 | *** join/#oe ant__ (~ant__@host10-8-dynamic.0-87-r.retail.telecomitalia.it) |
| 09:03.04 | *** join/#oe ao2 (~ao2@87.19.23.254) |
| 09:22.27 | *** join/#oe g0hl1n (~g0hl1n@83-215-125-121.lhau.dyn.salzburg-online.at) |
| 09:34.27 | *** join/#oe florian (~florian_k@Maemo/community/contributor/florian) |
| 09:58.27 | *** join/#oe florian (~florian_k@Maemo/community/contributor/florian) |
| 10:15.14 | *** join/#oe ant__ (~ant__@host85-244-dynamic.251-95-r.retail.telecomitalia.it) |
| 10:30.08 | *** join/#oe escanor (uid387784@gateway/web/irccloud.com/x-yzouenwmcmoqrmmb) |
| 10:56.56 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 11:36.37 | leon-anavi | khem, so far I haven't been able to reproduce the lirc 0.10.1 issue even on the yoe setup with docker: https://gist.github.com/leon-anavi/7c3c2e41604b8d40c981a2f12567f3fc#file-lirc-0-10-1-qemux86-64-yoe-log |
| 11:37.26 | leon-anavi | I'm probably doing something wrong with my attempts. I have a clue where this error might be coming from, just need to reproduce it to be able to test the potential fix. |
| 12:04.24 | *** join/#oe kroon (~kroon@37-247-29-68.customers.ownit.se) |
| 13:20.25 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 13:55.48 | *** join/#oe florian (~florian_k@Maemo/community/contributor/florian) |
| 13:59.12 | *** join/#oe yann (~yann@91-170-159-152.subs.proxad.net) |
| 14:33.03 | *** join/#oe kroon (~kroon@37-247-29-68.customers.ownit.se) |
| 15:02.34 | *** join/#oe ao2 (~ao2@87.19.23.254) |
| 15:08.02 | khem | leon-anavi: yes mee too, I think it must have been some oe-core master-next cruft |
| 15:10.52 | leon-anavi | I am not feeling comfortable making a new version of the patch for upgrading lirc in an attempt to fix this issue python-pkg/VERSION without being able to properly reproduce and test it locally. |
| 15:25.16 | khem | no worries I will queue it and watch for few CI cycles |
| 15:29.18 | leon-anavi | ok, thanks for helping me out with this patch! |
| 16:07.27 | armpit | khem, c4 build fails with cc1: error: switch '-mcpu=armv8.2-a' conflicts with '-march=armv8-a' switch [-Werror] |
| 16:08.52 | armpit | will poke at it a bit |
| 16:17.15 | *** join/#oe florian (~florian_k@Maemo/community/contributor/florian) |
| 17:24.21 | *** join/#oe Jin^eLD (~jin@45.62.252.190) |
| 17:24.36 | Jin^eLD | heh, timed out and did notice.. |
| 17:24.41 | Jin^eLD | I am wondering, how are dependencies handled with pypi? if a package has a gazillion of dependencies that are not available as recipes, what will happen? will they get pulled in or will it fail? |
| 17:24.51 | Jin^eLD | I guess I just need to try.. |
| 17:25.33 | Jin^eLD | packaging python applications seems to be quite a PITA not only due to the number of python modules they depend on, but also when they depend on specific versions of those modules... |
| 17:29.09 | kergoth | heh, there's a reason most people on desktop systems don't distribute their python projects as distro packages :) |
| 17:29.38 | kergoth | don't usually, rather |
| 17:30.18 | *** join/#oe escanor (uid387784@gateway/web/irccloud.com/x-pvkavccndofgrpwj) |
| 17:31.12 | Jin^eLD | kergoth: its an extreme PITA :) |
| 17:31.21 | Jin^eLD | and I guess I now know why "virtual env" came around |
| 17:31.54 | kergoth | exactly. easier to just ship the whole damn thing in a self contained blob. sometimes even more so, include the interpreter too in a single executable :) |
| 17:32.01 | kergoth | or docker image, or.. |
| 17:32.02 | Jin^eLD | as easy as it is to develop in python, this forest of modules and their versions, which actually makes it so easy to develop stuff, is a major PITA when trying to get something to work... |
| 17:32.17 | Jin^eLD | doh |
| 17:32.36 | Jin^eLD | so how do we handle that? |
| 17:33.04 | Jin^eLD | will those deps get pulled and packaged with the main app or do I need to go through each single one of the dependencies and create a recipe for it if its not yet available? |
| 17:33.31 | kergoth | my guess is it's the latter, but haven't read the bbclasses, so can't say with much confidence |
| 17:33.47 | kergoth | presumably we could create new classes to do it differently if that's the xcase, though. to make something more self contained |
| 17:34.09 | kergoth | hmm |
| 17:34.30 | Jin^eLD | well, one problem I see is that this is no leightweight at all, I ended up with +150MB of python deps in the rootfs, so I guess blobbing is not a good idea in Yocto context |
| 17:34.41 | kergoth | oof |
| 17:34.56 | Jin^eLD | but resolving that stuff manually is so damn teadious :) |
| 17:35.32 | Jin^eLD | I was looking at meta-maker, which packaged a pre-release octoprint |
| 17:35.43 | Jin^eLD | and upping it to the release version turned out to be quite an effort |
| 17:36.11 | Jin^eLD | gazillon of deps pinned to specific versions |
| 17:36.25 | Jin^eLD | and of course the work meta-maker guys did is somewhat outdated now and the versions do not match anymore |
| 17:41.05 | Jin^eLD | moto-timo: btw are you guys maintaining meta-maker any longer or is it dead? i.e. would you be interested in some updates or should I not bother and publish them in my own layer? |
| 17:43.21 | *** join/#oe kroon (~kroon@37-247-29-68.customers.ownit.se) |
| 17:50.48 | khem | armpit: try with oe-core/master-next you need a patch from there https://git.openembedded.org/openembedded-core/commit/?h=master-next&id=14cbd2c4e1b300fbafbd8f221c2c3f5cff1d5811 |
| 17:51.41 | khem | armpit: once in master they should be backported to dunfell too, I will send a request eventually |
| 17:51.52 | *** join/#oe nerdboy (~sarnold@gentoo/developer/nerdboy) |
| 17:53.55 | khem | armpit: send another pull for meta-odroid to get x11 going |
| 17:54.04 | khem | s/send/sent/ |
| 18:40.28 | *** join/#oe dv_ (~dv@62-178-50-190.cable.dynamic.surfer.at) |
| 19:40.28 | armpit | yep. saw it. thanks |
| 19:42.35 | armpit | I am working on dunfell meta-odroid for the c4 backports.. |
| 19:43.36 | armpit | I lost on of my build systems do to "dd" the wrong device name... its why I don't fly |
| 20:16.57 | *** join/#oe sakoman (~steve@rrcs-66-91-142-162.west.biz.rr.com) |
| 20:24.26 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 21:27.41 | *** join/#oe ant__ (~ant__@host85-244-dynamic.251-95-r.retail.telecomitalia.it) |
| 22:11.43 | *** join/#oe florian (~florian_k@Maemo/community/contributor/florian) |
| 23:49.28 | *** join/#oe dv_ (~dv@62.178.50.190) |