| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 276 seconds) | 00:04 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 00:09 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 246 seconds) | 00:13 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 00:14 | |
| *** _azcraft <_azcraft!~AzCraft@195.214.252.213> has quit IRC (Remote host closed the connection) | 00:14 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving) | 00:26 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-4-112.hawaiiantel.net> has quit IRC (Quit: Leaving.) | 00:49 | |
| *** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Ping timeout: 248 seconds) | 00:52 | |
| *** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto | 00:54 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 246 seconds) | 01:16 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 01:17 | |
| *** davidinux <davidinux!~davidinux@host-82-55-204-236.retail.telecomitalia.it> has quit IRC (Ping timeout: 255 seconds) | 02:04 | |
| *** davidinux <davidinux!~davidinux@host-80-116-36-71.pool80116.interbusiness.it> has joined #yocto | 02:06 | |
| *** barometz <barometz!~dvanb@92-109-61-249.cable.dynamic.v4.ziggo.nl> has quit IRC (Ping timeout: 250 seconds) | 02:07 | |
| *** barometz <barometz!~dvanb@92-109-61-249.cable.dynamic.v4.ziggo.nl> has joined #yocto | 02:12 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 246 seconds) | 02:20 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 02:21 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 02:29 | |
| *** alimon <alimon!~alimon@2806:10b7:2:506d:2c32:cfff:fe8e:de1f> has quit IRC (Ping timeout: 264 seconds) | 03:02 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 276 seconds) | 03:25 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 03:26 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:651c:100:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 260 seconds) | 03:43 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:653c:1500:2ce:39ff:fecf:efcd> has joined #yocto | 03:45 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 03:50 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 03:50 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 268 seconds) | 04:29 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 04:30 | |
| *** amitk <amitk!~amit@103.59.74.58> has joined #yocto | 04:42 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection) | 04:49 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds) | 05:19 | |
| *** nemik <nemik!~nemik@76.74.126.42> has joined #yocto | 05:19 | |
| *** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto | 05:27 | |
| *** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 250 seconds) | 05:29 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 05:29 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 255 seconds) | 05:33 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 05:33 | |
| *** amitk <amitk!~amit@103.59.74.58> has quit IRC (Ping timeout: 255 seconds) | 05:33 | |
| *** amitk <amitk!~amit@103.208.71.118> has joined #yocto | 06:04 | |
| *** rob_w <rob_w!~rob@2001:a61:6012:6901:e907:2962:8a32:fd3e> has joined #yocto | 06:18 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 246 seconds) | 06:36 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 06:36 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 06:38 | |
| ArgaKhan | Hello, I get the error; linux-dummy-dev : Depends: linux-dummy (= 1.0-r1) but it is not installable. I am using Kirkstone version and I added ALLOW_EMPTY:${PN} = "1" in poky/meta/recipes-kernel/linux/linux-dummy.bb but the problem persists. | 06:49 |
|---|---|---|
| *** frwol <frwol!~frwol@user/frwol> has joined #yocto | 07:15 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 07:23 | |
| *** fabo <fabo!~fabo@88.169.167.85> has joined #yocto | 07:33 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 07:33 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:34 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 264 seconds) | 07:40 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 07:40 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 07:40 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 07:40 | |
| fmartinsons[m] | Hello is anyone here using codium (https://vscodium.com/) for development, if so, did you know an extension for syntax highligh of yocto recipes and classes ? | 07:50 |
| fmartinsons[m] | Seems there is one: https://github.com/EugenWiens/vscode-bitbake but I cannot find it inside codium :/ | 07:50 |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Ping timeout: 255 seconds) | 07:51 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto | 07:52 | |
| *** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto | 08:00 | |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto | 08:07 | |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4c03:f700:7656:3cff:fe3f:7ce9> has joined #yocto | 08:07 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 08:20 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 08:20 | |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 255 seconds) | 08:34 | |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto | 08:36 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 260 seconds) | 08:45 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 08:45 | |
| *** ArgaKhan <ArgaKhan!~ArgaKhan@95.70.157.222> has quit IRC (Remote host closed the connection) | 08:51 | |
| fmartinsons[m] | I manage to install it manually by downloading the vsix file from https://marketplace.visualstudio.com/items?itemName=EugenWiens.bitbake and follow this tuto: https://milicendev.netlify.app/article/install-vs-codium-and-integrate-vs-code-extensions/ | 09:04 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 09:06 | |
| *** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 268 seconds) | 09:10 | |
| *** Bardon <Bardon!~Bardon@user/Bardon> has quit IRC (Ping timeout: 252 seconds) | 09:23 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection) | 09:27 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto | 09:27 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto | 09:31 | |
| *** ptsneves <ptsneves!~Thunderbi@84.47.155.82> has joined #yocto | 09:34 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 250 seconds) | 09:49 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 09:50 | |
| *** Guest6 <Guest6!~Guest6@131.228.66.14> has joined #yocto | 10:01 | |
| Guest6 | Does bitbake git fetch considers .gitconfig for url? | 10:02 |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has joined #yocto | 10:06 | |
| *** Peter[m]12 <Peter[m]12!~hoyesmatr@2001:470:69fc:105::3:376> has joined #yocto | 10:10 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 10:15 | |
| *** Bardon <Bardon!~Bardon@user/Bardon> has joined #yocto | 10:16 | |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has quit IRC (Ping timeout: 260 seconds) | 10:17 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 10:20 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 10:21 | |
| *** davidinux <davidinux!~davidinux@host-80-116-36-71.pool80116.interbusiness.it> has quit IRC (Ping timeout: 246 seconds) | 10:25 | |
| *** davidinux <davidinux!~davidinux@194.147.59.250> has joined #yocto | 10:26 | |
| *** Guest4467 <Guest4467!~Guest44@86-82-153-189.fixed.kpn.net> has joined #yocto | 10:29 | |
| Guest4467 | Hi, why is qt so popular in embedded linux and why can't flutter be the replacement considering it is license free? | 10:30 |
| Guest4467 | Is it about interfacing with hardware (i2c, spi etc.) that qt provides out-of-the-box experience? | 10:30 |
| rburton | Nothing stopping you using flutter? Qt has paid support, which many companies like. | 10:32 |
| LetoThe2nd | Guest4467: well flutter sees interest there and is used for things. if it matches your needs, go use it. | 10:32 |
| LetoThe2nd | and i've never heard about qt having out of the box spi support, but that would be kinda "neat" ;-) | 10:32 |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has joined #yocto | 10:39 | |
| LetoThe2nd | Guest4467: oh and for the record, flutter is a) definitively not "license free", it is "bsd" which is clearly defined and b) it involves quite a bit of magic that is tied to Google. Not everybody likes that. | 10:41 |
| neverpanic | flutter is, in typical Google manner, ridiculously hard to compile from source with a ton of dependencies. Qt isn't. | 10:41 |
| tunahan | Hello, can someone help, I haven't been able to solve it for about 1 month. I get the error "linux-dummy-dev : Depends: linux-dummy (= 1.0-r1) but it is not installable". I am using the "Kirkstone" version and added "ALLOW_EMPTY:${PN} = "1"" in "poky/meta/recipes-kernel/linux/linux-dummy.bb" but the problem persists. "dev-pkgs" is turned on in "EXTRA_IMAGE_FEATURES". Link to my log file: https://paste.ee/p/qPzy6 | 10:41 |
| LetoThe2nd | neverpanic: thats what i, more elegantly called "magic" ;-) | 10:42 |
| *** me57 <me57!~me@84.199.19.19> has joined #yocto | 10:43 | |
| neverpanic | My hardware token's GUI app to display TOTP codes has recently moved from Qt to flutter, I had a look at what it would take to package it, and I'm staying with the old Qt copy for now. | 10:43 |
| mario-goulart | Also, flutter is relatively recent. A lot of projects might even predate it. | 10:43 |
| LetoThe2nd | having said that, there seem to be people happy with using flutter in embedded. :-) | 10:44 |
| qschulz | Guest4467: some people are using LVGL BTW if you're looking for other techs too | 10:44 |
| LetoThe2nd | e.g. use what ever matches your usecase. | 10:44 |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has quit IRC (Ping timeout: 250 seconds) | 10:46 | |
| me57 | Hello, all. I have a question on how to proceed creating a (python) virtual environment (venv) for the target using a (host) yocto recipe. How should I proceed ? Could anyone give me some pointer(s), please. I am relatively new to Yocto. | 10:49 |
| me57 | (I hope I am in the correct chat channel, to start with) | 10:49 |
| LetoThe2nd | me57: you're in the right channel, but not sure everybody understands the question. your recipe, -native host only requires being run in a venv? (please not that I'm not a python guy, just trying to help and clarify). | 10:52 |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 246 seconds) | 10:52 | |
| LetoThe2nd | me57: and if so, why would that be? yocto treats all recipes as separate sysroots anyways. | 10:53 |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 10:53 | |
| Guest4467 | Is there a GUI tool that uses only Rust? | 10:54 |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds) | 10:54 | |
| *** nemik <nemik!~nemik@76.74.126.42> has joined #yocto | 10:54 | |
| me57 | a python venv is basically an environment in which some python script is running; the venv provides the needed imported modules on the running computer (in this case, the target) without so-to-say "polluting" the rest of the (target) environment. | 10:55 |
| Guest4467 | The reason why I mentioned Flutter is that it doesn't seem to have libraries such as Qt that interact well with hardware protocols such as CAN, I2C etc. Which is why I brought this topic up. Even though you can compile it perfectly, it uses Dart. | 10:55 |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has joined #yocto | 10:55 | |
| *** davidinux <davidinux!~davidinux@194.147.59.250> has quit IRC (Ping timeout: 276 seconds) | 10:56 | |
| me57 | So this venv has to be installed by some (target) program. Which, I am afraid, cannot be done on the host | 10:56 |
| me57 | It could possibly be done on the target the first time the target system runs, but I don't think this is the better way... | 10:57 |
| *** davidinux <davidinux!~davidinux@host-80-116-36-71.pool80116.interbusiness.it> has joined #yocto | 10:57 | |
| Guest4467 | qschulz Didn't heard of that one before, LVGL sounds interesting thanks! Just like with other tools in which Rust "can" be used, they have https://github.com/rafaelcaricio/lvgl-rs | 10:58 |
| Guest4467 | KDAB stated Rust bindings isn't quite what Rust devs want (memory safety), they developed CXX-RUST for Qt. Is there something similar to LVGL? | 10:58 |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 246 seconds) | 10:58 | |
| *** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 276 seconds) | 10:59 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 11:00 | |
| *** rob_w <rob_w!~rob@2001:a61:6012:6901:e907:2962:8a32:fd3e> has quit IRC (Quit: Leaving) | 11:04 | |
| *** Guest4467 <Guest4467!~Guest44@86-82-153-189.fixed.kpn.net> has quit IRC (Quit: Client closed) | 11:04 | |
| *** camus <camus!~Instantbi@116.236.93.172> has quit IRC (Remote host closed the connection) | 11:05 | |
| me57 | LetoThe2nd so I don't know how to proceed. To learn : what do you mean by your statement "yocto treats all recipes as separate sysroots anyways" ? What does "treating a recipe as a sysroot" mean ? | 11:07 |
| ptsneves | Guest4467: Another thing is that qt has native libraries which might be important for low cost hardware. Flutter if i remember correctly is an interpreted language | 11:09 |
| ptsneves | me57: It measn that for the purposes of building the recipe a custom sysroot is created in the recipe workspace. It does not bring more nor less than what you specified is needed to build the recipe | 11:10 |
| *** Tyaku <Tyaku!~Tyaku@82-64-140-155.subs.proxad.net> has joined #yocto | 11:14 | |
| *** camus <camus!~Instantbi@116.236.93.172> has joined #yocto | 11:16 | |
| polprog | I have a recipe (.bb) that aims to add a file to ${sysconfdir}/dropbear/, but it does not appear in the final rootfs.. how do i go about troubleshooting it? | 11:16 |
| me57 | ptsneves I think I understand this. So as I need 3 modules to be installed in the venv, I know I'll have to first make those modules. AFAIK, this can be done on the host using the yocto cross-toolchain. But the virtual environment is something that cannot run on the host (I think). I think it will have to run on the target. So, I have the problem | 11:17 |
| me57 | that it is not present in my created filesystem for the target, but to be generated by the target ? | 11:17 |
| me57 | s/virtual environment/virtual environment creation/ | 11:18 |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has quit IRC (Ping timeout: 265 seconds) | 11:26 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 11:26 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection) | 11:27 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 11:27 | |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has joined #yocto | 11:32 | |
| polprog | i found the issue, when i open a devshell for this recipe i get dropped into ${S} which is empty and the source file i need to copy is directly in ${S}/../ | 11:37 |
| polprog | but adjusting ${S} = "${WORKDIR}" as per the wiki did not change ${S} in the devshell | 11:38 |
| polprog | what should i do to either make it place the source file into ${S} or make ${S} point where the srouce file is placed? | 11:40 |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 276 seconds) | 11:57 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 11:57 | |
| *** azcraft <azcraft!~AzCraft@195.214.252.213> has joined #yocto | 12:17 | |
| ptsneves | me57: i am not familiar with venv, that you mention. It is not a yocto concept | 12:18 |
| rburton | polprog: can you share the recipe? | 12:19 |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has quit IRC (Ping timeout: 256 seconds) | 12:21 | |
| polprog | rburton: i got the recipe buildingwithout errors now but it still does not appear in the target rootfs. the recipe is here: http://0x0.st/H-1D.bb | 12:21 |
| rburton | yeah that's not right | 12:21 |
| polprog | i have IMAGE_INSTALL += " hostkey " in my layer.conf but it still does not create the file in the target rootfs | 12:22 |
| rburton | sure, because do_rootfs is a task that only runs if you're building a rootfs, and your recipe builds a package | 12:22 |
| polprog | should i use do_install then? | 12:23 |
| rburton | instead you should have a do_install() that basically does install -d ${D}${sysconfig}/dropbear ; install ${S}/dropbear... ${D}${sysconfdir}/dropbear | 12:23 |
| rburton | FILES isn't needed as the default contains sysconfdir | 12:23 |
| rburton | and just assign to SRC_URI | 12:24 |
| rburton | you can drop PR too whilst you're there | 12:24 |
| me57 | ptsneves OK, no problem. I am only looking for the conceptual things to do. And cross-compiling, cross-linking and all the like are things that can be done on the host, for the target. And it can all be put "as-built-on-the-host" into the target filesystem. | 12:26 |
| polprog | rburton: so something like this? http://0x0.st/H-1R.bb | 12:26 |
| me57 | What I am looking for, is what there is to be done for configuring things /on the target/ with code that has to (/can only) run on the target. | 12:26 |
| rburton | polprog: yep | 12:26 |
| polprog | rburton: allright, let me build it and see if it apperas in the rootfs | 12:27 |
| rburton | polprog: and don't do stuff like IMAGE_INSTALL in a layer.conf, that's horrible :) | 12:27 |
| polprog | how should i specify it then :D? | 12:27 |
| rburton | polprog: image recipe, distro conf, local.conf | 12:27 |
| rburton | me57: you can make a venv in a recipe (afaik) | 12:28 |
| me57 | rburton Glad to hear ! Could you give me some links or pointer to doc on how to do this ? | 12:32 |
| rburton | me57: create a venv in a task, put it in a package | 12:33 |
| rburton | haven't tried, but can't see why it *wouldn't* work | 12:34 |
| rburton | it _is_ a terrible idea | 12:34 |
| me57 | OK, that's the principle. Question is : how do I do this (i.e. create a venv in a task) ? | 12:34 |
| rburton | python3 -mvenv my-new-venv | 12:34 |
| me57 | Why is it (a terrible idea) ? | 12:34 |
| Ablu[m] | How can I do a custom patching logic (cannot be a .patch, since it depends on build environment variables) in a way that if the task that does the patching changes, I force bitbake to do a fresh unpack before (so that the source is in a clean state and does not have my patch logic applied already). Does that even work with the dependency model? How is this handled for normal .patch files (I tried to check the code, but I was not able to find | 12:34 |
| Ablu[m] | anything specific to this)? | 12:34 |
| rburton | me57: it's a terrible idea because you throw away all the useful bits of yocto for actual products: source caches, reproducibility, licenses manifests, etc | 12:35 |
| *** azcraft <azcraft!~AzCraft@195.214.252.213> has quit IRC (Remote host closed the connection) | 12:35 | |
| me57 | would I (not sure if I am well enough a python guy to see what you mean) ? | 12:36 |
| polprog | rburton: can i have my local.conf in <mylayer>/conf/ ? (where the layer.conf is?) I dont want to have it in the build directory since xilinx tools nuke it often | 12:37 |
| rburton | polprog: sounds like you need to make a new distro config or an image recipe | 12:37 |
| me57 | rburton Would you know of an example I could have a look at (on how to create a venv in a task) ? I haven't succeeded (yet) to find some, probably because I just don't google the correct terms for what I try to achieve) ? | 12:40 |
| rburton | not off hand | 12:42 |
| me57 | rburton because if I execute your sample above ("python3 -mvenv my-new-venv"), this will run on the host, but I'm puzzled there, as the result is intended for the target ? | 12:42 |
| rburton | *all* commands when you're building a recipe run on the host | 12:42 |
| me57 | yes, for sure ! | 12:43 |
| rburton | if you desperately want to do it on the target, then have a script to run on the target. write a systemd first-boot unit to run it, or something. | 12:43 |
| me57 | that's indeed what I was afraid for. I would've hoped there was a host-based way to do this ... | 12:44 |
| polprog | i have a feeling yocto is a nice (very complicated but nice) buildsystem but the way petalinux uses it is just plain stupid | 12:45 |
| polprog | ive added the IMAGE_INSTALL line to a (new) local.conf, lets see if it works | 12:45 |
| Ablu[m] | hm it looks like do_patch() {} also does not magic regarding forcing a fresh unpack. Probably it just checks whether stuff is already applied somehow? At least when I just overwrite do_patch() {} then my logic also executes again... So I guess I would have to find a way to put a template into SRC_URI and base the patching on that? 🤔 | 12:49 |
| rburton | Ablu[m]: if a file in SRC_URI cahnges, unpack has to re-run | 12:51 |
| rburton | you should definitely put your "patch" in SRC_URI if its a file | 12:51 |
| rburton | then it gets cached, archived, tracked, etc | 12:51 |
| *** camus <camus!~Instantbi@116.236.93.172> has quit IRC (Quit: camus) | 12:53 | |
| Ablu[m] | rburton: 👍️. Right. I realized that what I was trying would not work with caching in any way... I guess I could just put a shell script there and have that execute during build... | 12:54 |
| *** Tyaku <Tyaku!~Tyaku@82-64-140-155.subs.proxad.net> has quit IRC (Ping timeout: 264 seconds) | 12:54 | |
| mischief | me57: why you need venv? why not normal python build/install etc? | 12:54 |
| *** Tyaku <Tyaku!~Tyaku@82-64-140-155.subs.proxad.net> has joined #yocto | 12:55 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 12:55 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 12:55 | |
| rburton | the correct thing to do is absolulely to just write a recipe for the package | 12:56 |
| rburton | s | 12:56 |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 250 seconds) | 12:59 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 13:00 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds) | 13:01 | |
| me57 | @mis | 13:02 |
| *** Tyaku <Tyaku!~Tyaku@82-64-140-155.subs.proxad.net> has quit IRC (Quit: Lost terminal) | 13:02 | |
| me57 | mischief This is not up to me to decide. I've been said something like "this is not the pythonic way". | 13:03 |
| rburton | _every distro_ on the plane is arguing with python about what 'pythonic' means, because when you're building a distro (read: entire disk image from the kernel up) you don't care what the python-way is, because the pythonic way only applies to single applications | 13:04 |
| rburton | on the planet, obviously | 13:04 |
| me57 | rburton I can follow you. | 13:05 |
| me57 | I just can't be involved in some political discussions ... | 13:05 |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has joined #yocto | 13:06 | |
| ptsneves | rburton: I think in this plane there is this discussion. I wonder what the shadow plane consensus on python is. | 13:06 |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed) | 13:07 | |
| *** amitk <amitk!~amit@103.208.71.118> has quit IRC (Ping timeout: 250 seconds) | 13:09 | |
| me57 | rburton mischief OTOH, we are building a yocto image targeting an SBC on which we want the final (TBH : application-oriented) customisations using yocto. Maybe it's just tweaking yocto a little too much... | 13:09 |
| mischief | hey, we also build a yocto image targeting an SBC! what a coincidence :-) | 13:11 |
| me57 | can't be. You're kidding | 13:11 |
| mischief | worst case you could tar up your program, extract it in a yocto recipe and be on your merry way | 13:12 |
| mischief | though that's a terrible idea | 13:12 |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 13:13 | |
| me57 | In the meantime I have found pypi.bbclass . Seems to go in the direction I'm after. | 13:15 |
| *** AKN <AKN!~AKN@49.205.87.101> has joined #yocto | 13:18 | |
| qschulz | me57: considering that Yocto only allows you to include **one** version of a package in your image, pyenv/venv is likely useless | 13:18 |
| qschulz | I'd use venv if I had to support multiple Python-based software stack not necessarily requiring the same dependencies or their versions | 13:18 |
| qschulz | but you're going to have a bad time using yocto for that anyways, venv is not going to help you do it properly i'm afraid | 13:19 |
| qschulz | (except if you download dependency with pip directly inside your recipe, but then youre just not going the Yocto way :) ) | 13:19 |
| me57 | qschulz The idea behind it would be that if we update the one python program, we don't have to tweak the complete system setup in such a case, just update the venv containing the python program | 13:21 |
| rburton | so fun for, ensurepip really doesn't like running inside a venv with our python. not sure what's going on there. | 13:21 |
| rburton | oh god my typing today | 13:22 |
| rburton | python being python means we have to beat it with a bit stick to be relocated, and i think the relocation is upsetting it | 13:22 |
| me57 | rburton ... meaning the target venv creation would be the least error-prone way to create the venv, right ? | 13:23 |
| me57 | (I mean, the venv creation ... on the target itself) | 13:24 |
| rburton | probably, albeit horrible | 13:25 |
| rburton | of course unless you've got 100 dependencies, you could have written the recipes for them already by now :) | 13:25 |
| *** kscherer <kscherer!~kscherer@bras-base-otwaon1146w-grc-26-174-95-44-180.dsl.bell.ca> has joined #yocto | 13:26 | |
| polprog | rburton: it works now! Thank you very much :) | 13:28 |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 246 seconds) | 13:29 | |
| *** nemik <nemik!~nemik@76.74.126.42> has joined #yocto | 13:29 | |
| polprog | also i think there is an error in this paragraph: https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles#Incorrect_source_folder_.24.7BS.7D | 13:29 |
| polprog | ${S} = "${WORKDIR}/correctfoldername" | 13:29 |
| polprog | should be | 13:29 |
| polprog | S = "${WORKDIR}/correctfoldername" | 13:29 |
| polprog | right? | 13:29 |
| rburton | yes | 13:30 |
| rburton | hm that wiki page is horrid | 13:30 |
| rburton | just use the proper docs | 13:30 |
| rburton | me57: so venvs need to be relocated as they contain a build-time path in, which is fun | 13:31 |
| *** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 255 seconds) | 13:34 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 13:34 | |
| ptsneves | If i wanted to find all providers that set a variable to a value, how would i do that from tinfoil? | 13:36 |
| rburton | ptsneves: see scripts/contrib/verify-homepage, athough that does a bit of extra work to filter out BBCLASSEXTENDs. you'll need to iterate all recipes. | 13:38 |
| ptsneves | rburton: interesting it iterates through the recipecaches. Any reason it is prefered to tinfoil.all_recipe_files? | 13:39 |
| *** azcraft <azcraft!~AzCraft@195.214.252.213> has joined #yocto | 13:40 | |
| rburton | ptsneves: honestly, that script probably predates all_recipe_files | 13:40 |
| ptsneves | rburton: ok because all_recipe_files even has a variants argument that excludes BBCLASSEXTENDs | 13:41 |
| ptsneves | good to know | 13:41 |
| rburton | yeah use that :) | 13:41 |
| ptsneves | tinfoil is amazing :) | 13:41 |
| *** sakoman <sakoman!~steve@dhcp-72-253-4-112.hawaiiantel.net> has joined #yocto | 14:00 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 268 seconds) | 14:03 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 14:04 | |
| *** astlep5504 <astlep5504!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has joined #yocto | 14:14 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 14:23 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 276 seconds) | 14:25 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 14:25 | |
| tunahan | Hello, can someone help, I haven't been able to solve it for about 1 month. I get the error "linux-dummy-dev : Depends: linux-dummy (= 1.0-r1) but it is not installable". I am using the "Kirkstone" version and added "ALLOW_EMPTY:${PN} = "1"" in "poky/meta/recipes-kernel/linux/linux-dummy.bb" but the problem persists. "dev-pkgs" is turned on in "EXTRA_IMAGE_FEATURES". Link to my log file: https://paste.ee/p/qPzy6 | 14:25 |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto | 14:35 | |
| abelloni | ALLOW_EMPTY:${PN}-dev = "1" ? | 14:37 |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection) | 14:40 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto | 14:40 | |
| *** AKN <AKN!~AKN@49.205.87.101> has quit IRC (Read error: Connection reset by peer) | 14:45 | |
| tunahan | That didn't work either. While trying your method, I saw another file named "openembedded-core/meta/recipes-kernel/linux/linux-dummy.bb" and I added "ALLOW_EMPTY:${PN} = "1"" in it. Problem solved, thank you for your help. | 14:46 |
| rburton | poky is a copy of oe-core, so you don't need both | 14:46 |
| rburton | they're the same file, and you were editing the wrong one | 14:46 |
| tunahan | Do I need to delete poky in this case? | 14:50 |
| *** me57 <me57!~me@84.199.19.19> has quit IRC (Ping timeout: 260 seconds) | 15:00 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 246 seconds) | 15:08 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 15:08 | |
| qschulz | tunahan: likely only one of the layers is used, check your conf/bblayers.conf in your build directory | 15:16 |
| qschulz | you should see either openembedded-core or poky in there | 15:16 |
| qschulz | remove the one that doesn't appear here | 15:16 |
| tunahan | qschulz: yes, there is no poky bblayers either. That little distraction cost me a month. So sad. But thanks for your help. | 15:22 |
| *** fabo <fabo!~fabo@88.169.167.85> has quit IRC (Quit: Client closed) | 15:27 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving) | 15:41 | |
| *** berton[m] <berton[m]!~berton@2001:470:69fc:105::ce36> has quit IRC (Quit: You have been kicked for being idle) | 16:00 | |
| *** BenkeHargitai[m] <BenkeHargitai[m]!~benkexmat@2001:470:69fc:105::3:191c> has quit IRC (Quit: You have been kicked for being idle) | 16:00 | |
| *** d-s-e <d-s-e!~d.s.e@i59F7CEE4.versanet.de> has quit IRC (Quit: Konversation terminated!) | 16:07 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 276 seconds) | 16:11 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 16:12 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 16:14 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 16:14 | |
| *** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection) | 16:19 | |
| *** vmeson <vmeson!~rmacleod@198-48-226-243.cpe.pppoe.ca> has quit IRC (Read error: Connection reset by peer) | 16:19 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 252 seconds) | 16:19 | |
| *** nemik <nemik!~nemik@76.74.126.42> has joined #yocto | 16:19 | |
| *** vvmeson <vvmeson!~rmacleod@198-48-226-243.cpe.pppoe.ca> has joined #yocto | 16:19 | |
| *** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 252 seconds) | 16:24 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 16:24 | |
| *** Guest6 <Guest6!~Guest6@131.228.66.14> has quit IRC (Quit: Client closed) | 16:28 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 16:29 | |
| *** Xagen <Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has joined #yocto | 16:32 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 252 seconds) | 16:34 | |
| *** |Xagen <|Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has quit IRC (Ping timeout: 276 seconds) | 16:36 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat) | 16:38 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 246 seconds) | 16:39 | |
| *** nemik <nemik!~nemik@76.74.126.42> has joined #yocto | 16:39 | |
| *** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 260 seconds) | 16:43 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 16:44 | |
| fury | i am having the issue described in this thread: https://lists.yoctoproject.org/g/yocto/topic/95170677#58598 - but i can't use master because "ERROR: Layer raspberrypi is not compatible with the core layer which only supports these series: mickledore (layer is compatible with kirkstone)" | 16:47 |
| fury | any ideas on how to fix? | 16:47 |
| rburton | use meta-raspberrypi master and not kirkstone | 16:48 |
| rburton | you need to match the layer branches | 16:48 |
| rburton | of course using master is for the brave and/or foolish, as its not a release | 16:48 |
| fury | oof... guess i'm out of luck, i don't think there's a qt layer that is compatible with anything newer than kirkstone | 16:49 |
| rburton | meta-qt5? that supports mickledore too. | 16:49 |
| fury | i am trying to build boot2qt for qt 6.4.3 and running into all sorts of weird issues, this was one of them | 16:49 |
| fury | and that's the latest i can find | 16:50 |
| fury | it's all set up for kirkstone | 16:50 |
| rburton | fury: try using the 64-bit raspberrypi machines | 16:50 |
| rburton | i _think_ that bug in the rust code is an omission for the 32-bit platforms | 16:50 |
| fury | i need to build for pi 0 w unfortunately :( | 16:51 |
| fury | and i also had to downgrade libvpx because newer versions of that dropped support for armv6 lol | 16:51 |
| rburton | i guess upgrading to the pi0 2 is not an option | 16:51 |
| fury | not until i can get my hands on one (or two) | 16:52 |
| fury | i am signed up for stock alerts | 16:52 |
| * fury crosses fingers | 16:52 | |
| * rburton fires off a kirkstone build to see if he can replicate the rust thing | 16:52 | |
| fury | this is the guide i'm trying to follow... https://raymii.org/s/tutorials/Yocto_boot2qt_for_the_Raspberry_Pi_4_both_Qt_6_and_Qt_5.html - i got 5.15.2 to work (zeus), with a few edits, but other things are going wrong, such as not maintaining the wifi connection, so i thought (heh) why not try a newer version... | 16:54 |
| rburton | zeus! | 16:54 |
| fury | yeah, old as methuselah at this point, amirite | 16:54 |
| rburton | i wonder if the boot2qt demos is one reason why we keep on getting people using zeus | 16:55 |
| rburton | well the boot2qt manifest uses the latest kirkstone out of the box | 16:55 |
| rburton | and the qt 6.5 manifest uses langdale, so has the rust fixes | 16:57 |
| rburton | https://code.qt.io/cgit/yocto/boot2qt-manifest.git/tree/6.5.xml | 16:57 |
| fury | sweet. i'll try building that one then | 16:58 |
| *** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto | 17:01 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 17:07 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 252 seconds) | 17:15 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 17:15 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 17:33 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 17:34 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 17:34 | |
| *** amitk <amitk!~amit@103.59.74.58> has joined #yocto | 17:45 | |
| *** vvmeson <vvmeson!~rmacleod@198-48-226-243.cpe.pppoe.ca> has quit IRC (Quit: Konversation terminated!) | 17:57 | |
| *** seninha_ <seninha_!~seninha@user/seninha> has joined #yocto | 17:59 | |
| * moto-timo actively upgrading customer zeus->kirkstone | 18:00 | |
| *** vvmeson <vvmeson!~rmacleod@198-48-226-243.cpe.pppoe.ca> has joined #yocto | 18:01 | |
| moto-timo | But iMX.6 platforms | 18:01 |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 260 seconds) | 18:02 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-132-065-157.93.132.pool.telefonica.de> has joined #yocto | 18:05 | |
| JaMa | rburton: I blame Xilinx for people still using zeus | 18:09 |
| *** alimon <alimon!~alimon@2806:10b7:2:8a1b:2c32:cfff:fe8e:de1f> has joined #yocto | 18:13 | |
| moto-timo | https://www.docker.com/blog/we-apologize-we-did-a-terrible-job-announcing-the-end-of-docker-free-teams/ | 18:14 |
| moto-timo | yes, yes you did. | 18:14 |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 248 seconds) | 18:17 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 18:18 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 18:21 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving) | 18:22 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 18:24 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit) | 18:25 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-132-065-157.93.132.pool.telefonica.de> has quit IRC (Ping timeout: 246 seconds) | 18:26 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 18:36 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 18:36 | |
| tangofoxtrot | I have a project that is still stuck on thud. :( | 18:36 |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 18:37 | |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4c03:f700:7656:3cff:fe3f:7ce9> has quit IRC (Quit: Leaving) | 18:40 | |
| JaMa | tangofoxtrot: what it is? | 18:40 |
| tangofoxtrot | customer project. No changes allowed. | 18:41 |
| JaMa | I wanted to know which projects to avoid :) | 18:41 |
| JaMa | or consumer products if it's used in some | 18:42 |
| tangofoxtrot | hah... NDA. Doubt you will ever see one, so you're safe. | 18:44 |
| sudip | tangofoxtrot: you are lucky, one of mine is at Krogoth :( | 18:44 |
| tangofoxtrot | Nice! :D Another project was at Jethro - they are upgrading to Dunfell. So.. progress! | 18:45 |
| *** azcraft <azcraft!~AzCraft@195.214.252.213> has quit IRC (Remote host closed the connection) | 18:55 | |
| *** azcraft <azcraft!~AzCraft@195.214.252.213> has joined #yocto | 18:56 | |
| moto-timo | Not that long ago someone said they were "stuck on daisy". | 18:56 |
| moto-timo | Other than medical devices, radio frequency compliance, FIPS... etc. (expensive validation testing) there are very few valid reasons to stay on old Yocto Project releases. | 18:58 |
| moto-timo | s/validation/compliance/ | 18:58 |
| tangofoxtrot | No argument from me. | 19:07 |
| moto-timo | Now, getting silicon vendors to continue supporting older SOCs/SOMs... even when you hand them the upgrade... that's a different story | 19:08 |
| *** amitk <amitk!~amit@103.59.74.58> has quit IRC (Quit: Lost terminal) | 19:13 | |
| *** amitk <amitk!~amit@103.59.74.58> has joined #yocto | 19:14 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds) | 19:14 | |
| *** nemik <nemik!~nemik@76.74.126.42> has joined #yocto | 19:14 | |
| *** amitk <amitk!~amit@103.59.74.58> has quit IRC (Client Quit) | 19:16 | |
| *** amitk <amitk!~amit@103.59.74.58> has joined #yocto | 19:16 | |
| *** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 255 seconds) | 19:18 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 19:19 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 246 seconds) | 19:21 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 19:22 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 19:30 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 19:35 | |
| *** Wouter010067044 <Wouter010067044!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 19:35 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 19:41 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 19:41 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 250 seconds) | 20:24 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 20:25 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 276 seconds) | 20:34 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds) | 21:13 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 21:26 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 21:27 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 255 seconds) | 21:29 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 21:30 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection) | 21:30 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-4-112.hawaiiantel.net> has quit IRC (Quit: Leaving.) | 21:35 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-4-112.hawaiiantel.net> has joined #yocto | 22:07 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection) | 22:16 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto | 22:16 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 276 seconds) | 22:34 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 22:34 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 22:36 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 22:37 | |
| *** amitk <amitk!~amit@103.59.74.58> has quit IRC (Ping timeout: 255 seconds) | 22:57 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has quit IRC (Remote host closed the connection) | 23:28 | |
| *** invalidopcode1 <invalidopcode1!~invalidop@cpe-172-90-200-106.socal.res.rr.com> has joined #yocto | 23:28 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has quit IRC (Ping timeout: 248 seconds) | 23:38 | |
| *** BoJalling <BoJalling!~BoJalling@152.115.47.4> has joined #yocto | 23:39 | |
| *** Estrella <Estrella!~quassel@075-081-060-240.res.spectrum.com> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 23:39 | |
| *** Estrella <Estrella!~quassel@075-081-060-240.res.spectrum.com> has joined #yocto | 23:42 | |
| *** gchamp_ <gchamp_!~champagne@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has quit IRC (Remote host closed the connection) | 23:44 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!