**** BEGIN LOGGING AT Sat Dec 05 02:59:57 2020 Dec 05 03:42:36 khem: i see my glmark2 patches are in master-next, is it too late for a v4? Dec 05 14:05:25 moto-timo, sorry for the delay, I just woke up, timezones... Dec 05 14:06:24 well, python -m build is indeed the new command to build wheels Dec 05 14:06:39 the problem is installing them Dec 05 14:07:30 if you can use pip, you have no issue, if you can't, there's no way yet Dec 05 14:08:27 I am not sure if you are building wheels with setuptools and installing them or installing via setuptools directly (setup.py install) Dec 05 14:08:53 the former is the only way supported in PEP 517 Dec 05 14:09:37 so you'll essentially need to build and then install a wheel Dec 05 17:49:52 Hello, I've got a recipe that fetches binary package from CI using wget: https://pastebin.com/7zGP1v2N and then installs them into system image. However, once the "sources" (in my case built binaries) are once pulled, they are never ever updated again Dec 05 17:50:09 is there any way to force bitbake to pull sources for this recipe *always*? Dec 05 17:59:08 kpo_: You'd have to change the checksums anyway? Dec 05 18:02:49 well, yes - I've come to this parallely. However, when I ditch the checksums altogether, then bitbake shouts with error to bring them back :P Dec 05 18:03:57 bitbake isn't designed to do what you're trying to do. Recipe build outputs are cached in what's called the sstate cache, and it isn't designed to rebuild a think that didn't change from its PoV (because its recipe didn't change) Dec 05 18:04:04 Changing the checksums should trigger the rebuild Dec 05 18:05:11 s/think/thing/ Dec 05 18:05:16 alright, then how does git fetcher with SRC_AUTOREV work? It always checks if repository has newer commits than what bitbake pulled lastly Dec 05 18:05:52 It kind of threw me off Dec 05 18:08:19 So is there any bitbake-ish way to do it properly? Dec 05 18:13:58 Does AUTOREV work for SVN? That might be an option. Other than that, I'd just automate editing the recipe. Dec 05 20:12:26 FFY00: the thing for us with using pip is that it will install all the dependencies. We don't do that. We carefully install only things we know about... unless we have no choice (like Go and npm packaging...). But you've given me enough food for thought and I truly appreciate it. Dec 05 20:17:28 it doesn't need to do that Dec 05 20:17:33 it can be disabled Dec 05 20:17:46 1sec Dec 05 20:20:12 pip install --isolated --ignore-installed --no-deps my-package.whl Dec 05 20:21:21 FFY00: ahhh... I was not aware of that Dec 05 20:21:34 that should be able to install only the wheel without messing anything Dec 05 20:21:51 but pip was really not designed for that Dec 05 20:21:52 I mostly use pipenv and not pip directly (but pipenv on development/desktop) Dec 05 20:21:55 yeah Dec 05 20:21:57 you might also want PIP_CONFIG_FILE=/dev/null Dec 05 20:22:14 we are working on a standalone wheel installer Dec 05 20:22:21 but it's not ready yet Dec 05 20:22:25 :/ Dec 05 20:22:40 I might start playing with the WIP :) Dec 05 20:23:17 meanwhile, I'll at least create a recipe for pypa/build Dec 05 20:23:18 let me know if you run into any trouble Dec 05 20:23:34 will do :) I'll tryi to communicate in the standard Python channels Dec 05 20:23:47 one thing to be aware is that pypa/build will build in a isolated environment by default Dec 05 20:23:55 you might want that or not Dec 05 20:24:21 depending on how it works in our environment, that is exactly what we want Dec 05 20:24:23 by default it will create a virtual environment and build the package there Dec 05 20:24:47 for eg. in Arch Linux packaging we don't want that Dec 05 20:24:54 ah Dec 05 20:25:47 there's -n/--no-isolation to disable if you want Dec 05 20:26:02 should save up a few seconds too Dec 05 20:26:19 and remove the internet dependency Dec 05 20:26:44 ooh. that is appealing :) Dec 05 20:27:00 we normally only allow internet during "fetch" Dec 05 20:27:08 yeah Dec 05 20:27:16 then you probably want -n :P Dec 05 20:27:26 we do this mostly for end users Dec 05 20:27:38 to force them to build in a clean environment Dec 05 20:27:54 :) Dec 05 20:27:58 which makes packaging issue like missing dependencies more evident Dec 05 20:28:08 *issues Dec 05 20:28:29 but overall for consumers it shouldn't be a problem Dec 05 20:28:45 indeed... we have both build and runtime issues with missing dependencies... mostly iterative solutions still Dec 05 20:29:13 how do you bootstrap the python environment btw? Dec 05 20:29:29 or you don't need to? Dec 05 20:30:07 I haven't used octo yet, so I am missing some details :P Dec 05 20:30:11 *yocto Dec 05 20:38:17 hi all, i cloned the meta-openembedded layer in my yocto, added the layer in bblayers.conf and when i run "bitbake libmicrohttp", the build is sucessful, but when i try to add "DEPENDS+=libmicrohttpd" to elfutils_0.180.bb file, i recieve the following error running "bitbake libmicrohttpd" again Dec 05 20:39:44 https://www.irccloud.com/pastebin/eRqxCr6k/ Dec 05 20:40:20 i'd really appreciate any help on this, thanks. Dec 05 20:42:50 dorinda: two options, (1) edit the libmicrohttpd recipe and add: Dec 05 20:43:01 BBCLASSEXTEND = "native" Dec 05 20:43:25 oh... but you don't want DEPENDS I don't think that is build time Dec 05 20:43:28 ? Dec 05 20:44:06 please describe what your goal is here? Dec 05 20:46:30 FFY00: our approach to python is rather complicated, but the main recipe is: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/python/python3_3.9.0.bb Dec 05 20:46:43 oh yes, i did add BBCLASSEXTEND ="native nativesdk" but there was another error, can recall what it was, let me try this BBCLASSEXTEND = "native" Dec 05 20:48:00 FFY00: because we want minimal target installs, we also create sub-packages of what is normally included in the standard libraries: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/python/python3/python3-manifest.json Dec 05 20:48:26 i was trying to include some dependencies in elfutil_0.180.bb, so when i add libmicrohttpd the error pops up Dec 05 20:49:05 dorinda: is libmicrohttpd a build time dependency for elfutils? Dec 05 20:50:08 dorinda: it is very important to understand the distinction between DEPENDS (build time) and RDEPENDS (run time) dependencies Dec 05 20:52:23 hum Dec 05 20:52:49 okay, not sure but i had tried including it in PACKAGECONFIG option for elfutils as a build time dependency, and there was no error. Dec 05 21:00:31 dorinda: right, so what you are looking at is build time (since it is in configure.ac) https://sourceware.org/git/?p=elfutils.git;a=blob;f=configure.ac;h=c1a6954da24572680f8b73edeb9a890674f422e2;hb=HEAD#l730 Dec 05 21:06:55 dorinda: so right now, in PACKAGECONFIG[libdebuginfod], it has curl at the end... you are trying to add libhttpd, sqlite and libarchive? Dec 05 21:06:59 https://sourceware.org/git/?p=elfutils.git;a=blob;f=configure.ac;h=c1a6954da24572680f8b73edeb9a890674f422e2;hb=HEAD#l743 Dec 05 21:07:22 http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/elfutils/elfutils_0.181.bb?h=master#n43 Dec 05 21:07:40 ^^libmicrohttpd Dec 05 21:10:00 ok, hold on, i noticed this is elfutils_0.181.bb, could it be because am using an old version? Dec 05 21:10:43 dorinda: perhaps, I don't know when the change was added to elfutils Dec 05 21:11:17 dorinda: but you should be working on the latest tip of openembedded-core and meta-openembedded/meta-oe for new work Dec 05 21:11:33 dorinda: also, I see that elfutils has a 0.182 release now Dec 05 21:12:51 the branch i was on gatesgarth, had elfutil_0.180.bb what ive tried now is switch branch to the one that has this 0.181 release, although my yocto is still building it. Dec 05 21:13:51 anything new will need to be merged into "master" before it would be backported to a stable release like gatesgarth Dec 05 21:14:13 so if you are working on a WIP branch it might need to be rebased Dec 05 21:14:19 0.182 yeah, but not yet in yocto environment i guess, ok thanks. Dec 05 21:16:24 just a matter of time before the update to 0.182 is added :) Dec 05 21:16:24 but for now, work on 0.181 Dec 05 21:16:25 alright thank you. let me see how that goes. Dec 05 21:16:25 dorinda: I did look at the recipes for libmicrohttpd, sqlite and libarchive... libmicrohttpd is missing BBCLASSEXTENDS = "native" so that would be a problem for building elfutils-native Dec 05 21:17:41 but package config should pick it up if it is present, so you should not need a different DEPENDS Dec 05 21:18:17 yeah, i had added it before building elfutils Dec 05 21:18:26 this is assuming libmicrohttpd is well behaved and creates a package config entry in the right place Dec 05 21:18:30 k Dec 05 21:19:48 hmm, okay thank. Dec 05 22:20:14 FFY00: between pip's --isolated and -t arguments I might be able to make this work :) Dec 05 22:20:34 FFY00: I will say a big thank you to the pypa folks for making pypa/build simple Dec 05 22:20:53 no worries :) **** ENDING LOGGING AT Sun Dec 06 02:59:56 2020