| *** jij <jij!jonashg@nat/axis/x-kmkoargdyezvjfjt> has quit IRC | 00:03 | |
| *** Saur <Saur!pkj@nat/axis/x-uienismpsqbfwfai> has quit IRC | 00:04 | |
| *** learningc <learningc!~learningc@121.121.98.53> has quit IRC | 00:20 | |
| *** vineela <vineela!vtummala@nat/intel/x-pkjfrbpvxmorsust> has quit IRC | 00:27 | |
| *** learningc <learningc!~learningc@mti-37-145.tm.net.my> has joined #yocto | 00:33 | |
| *** Crofton <Crofton!~Crofton@167.220.99.118> has quit IRC | 01:04 | |
| *** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has quit IRC | 01:15 | |
| *** armpit <armpit!~armpit@45.19.219.178> has quit IRC | 01:19 | |
| *** lucaceresoli <lucaceresoli!~lucaceres@45.11.168.109.cust.ip.kpnqwest.it> has quit IRC | 01:37 | |
| *** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC | 01:37 | |
| *** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto | 01:37 | |
| *** lucaceresoli <lucaceresoli!~lucaceres@45.11.168.109.cust.ip.kpnqwest.it> has joined #yocto | 01:39 | |
| *** vineela <vineela!vtummala@nat/intel/x-ykxvoohhfdwsjcvd> has joined #yocto | 02:23 | |
| *** vineela <vineela!vtummala@nat/intel/x-ykxvoohhfdwsjcvd> has quit IRC | 02:33 | |
| *** cp <cp!~cp@b157153.ppp.asahi-net.or.jp> has quit IRC | 02:54 | |
| *** cp <cp!~cp@b157153.ppp.asahi-net.or.jp> has joined #yocto | 02:56 | |
| *** vineela <vineela!~vtummala@134.134.137.79> has joined #yocto | 03:16 | |
| *** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 03:29 | |
| *** jeranio <jeranio!290dbceb@41.13.188.235> has joined #yocto | 03:31 | |
| jeranio | Hello | 03:31 |
|---|---|---|
| jeranio | Is the next Coding live Yocto on the 8th October? | 03:32 |
| jeranio | 5pm Berlin Time ? | 03:32 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 03:33 | |
| *** jeranio <jeranio!290dbceb@41.13.188.235> has quit IRC | 03:37 | |
| *** armpit <armpit!~armpit@2601:202:4180:a5c0:2c5e:3326:62f0:95f9> has joined #yocto | 03:45 | |
| *** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has quit IRC | 04:33 | |
| *** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto | 04:33 | |
| *** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto | 04:33 | |
| *** lazyape_home <lazyape_home!~lazyape@80.107.149.24> has joined #yocto | 04:36 | |
| *** elfGamal <elfGamal!~elg@5.253.206.78> has quit IRC | 04:37 | |
| *** elGamal <elGamal!~elg@5.253.206.78> has joined #yocto | 04:38 | |
| *** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has quit IRC | 04:38 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 04:38 | |
| *** lazyape <lazyape!~lazyape@80.107.149.24> has quit IRC | 04:38 | |
| *** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC | 04:38 | |
| *** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has quit IRC | 04:38 | |
| *** smartin <smartin!~smartin@207.ip-37-59-126.eu> has quit IRC | 04:38 | |
| *** jaeckel <jaeckel!~jaeckel@unaffiliated/jaeckel> has joined #yocto | 04:49 | |
| *** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 04:51 | |
| *** linuxjacques <linuxjacques!~jacques@nslu2-linux/jacques> has joined #yocto | 04:52 | |
| *** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto | 04:52 | |
| *** smartin <smartin!~smartin@207.ip-37-59-126.eu> has joined #yocto | 04:52 | |
| *** agust <agust!~agust@p54833695.dip0.t-ipconnect.de> has joined #yocto | 05:05 | |
| *** thomasd13 <thomasd13!d472ff94@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto | 05:11 | |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto | 05:19 | |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC | 05:22 | |
| *** kroon <kroon!~kroon@213.185.29.22> has joined #yocto | 05:43 | |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto | 05:43 | |
| *** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 06:03 | |
| *** Klox <Klox!~Klox@c-24-1-131-19.hsd1.il.comcast.net> has quit IRC | 06:14 | |
| *** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has quit IRC | 06:19 | |
| *** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto | 06:19 | |
| *** kroon <kroon!~kroon@213.185.29.22> has quit IRC | 06:23 | |
| *** mckoan|away is now known as mckoan | 06:25 | |
| *** florian_kc is now known as florian | 06:32 | |
| *** goliath <goliath!~goliath@37-247-85-246.natip.skydsl.at> has joined #yocto | 06:32 | |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 06:45 | |
| *** Klox <Klox!~Klox@c-24-1-131-19.hsd1.il.comcast.net> has joined #yocto | 06:59 | |
| *** goliath <goliath!~goliath@37-247-85-246.natip.skydsl.at> has quit IRC | 07:00 | |
| *** yann <yann!~yann@aputeaux-653-1-137-254.w86-195.abo.wanadoo.fr> has quit IRC | 07:05 | |
| *** coretec <coretec!d43ed5a2@212.62.213.162> has joined #yocto | 07:06 | |
| *** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has joined #yocto | 07:16 | |
| *** amine <amine!~amine@static-176-158-51-218.ftth.abo.bbox.fr> has joined #yocto | 07:26 | |
| *** yacar_ <yacar_!~yacar@80.215.198.20> has joined #yocto | 07:47 | |
| *** amine <amine!~amine@static-176-158-51-218.ftth.abo.bbox.fr> has quit IRC | 07:50 | |
| *** amine <amine!~amine@static-176-158-51-218.ftth.abo.bbox.fr> has joined #yocto | 07:52 | |
| *** Saur <Saur!pkj@nat/axis/x-wlpbmpksfrvbvlyq> has joined #yocto | 07:58 | |
| *** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto | 07:59 | |
| *** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has joined #yocto | 08:01 | |
| *** LocutusOfBorg <LocutusOfBorg!LocutusOfB@ubuntu/member/locutusofborg> has joined #yocto | 08:15 | |
| LocutusOfBorg | hello, I have a simple question for imx6q mfgtool handling, is anybody out there to help? | 08:16 |
| LocutusOfBorg | the question is: I have an imx6qsabresd, and I would like to build the mfgtools artifacts via yocto (e.g. warrior is fine) | 08:16 |
| LetoThe2nd | LocutusOfBorg: pick your poison: http://layers.openembedded.org/layerindex/branch/master/recipes/?q=mfgtool | 08:17 |
| LocutusOfBorg | I fail to find documentation on the "current" mfgtool version and documentation on the build procedure, e.g. | 08:19 |
| LocutusOfBorg | LetoThe2nd, this fails.... for some reasons, 1) meta-fsl-arm is dead, 2) fsl-image-mfgtool-initramfs is not buildable for imx6q but only for imx6s | 08:20 |
| LocutusOfBorg | 3) imx-uuc was working really good, it contains even a patch done by me... but it relies on FSL_UTP feature, that is now dropped on the kernel side, so it seems to be not working anymore | 08:20 |
| LocutusOfBorg | 4) new mfgtool seems to have changed the way of communicating, deprecating FSL_UTP | 08:20 |
| LocutusOfBorg | 5) I can't find proper documentation on the current way, and I don't want to build an oooooold yocto version just to have mfgtool artifacts | 08:21 |
| LetoThe2nd | LocutusOfBorg: well then your best chances are probably poking the layer maintainer if there's something in the making, or actually sending patches. the layerindex gives you the current publicly available state, and if that is obsolete, then... :-( | 08:22 |
| mckoan | LocutusOfBorg: the new name of meta-fsl-arm is meta-freescale | 08:24 |
| mckoan | LocutusOfBorg: https://freescale.github.io/ | 08:24 |
| LocutusOfBorg | mckoan, yes, since some years, but the stuff in meta-freescale is not working, as said above | 08:24 |
| LocutusOfBorg | I was even the probably first person to complain when they moved layer without making people aware... | 08:24 |
| *** tvm <tvm!~tvm@ip-86-49-228-196.net.upcbroadband.cz> has joined #yocto | 08:31 | |
| yacar_ | zeddi: I worked on the bug yesterday, I've added SPDX Identifier to scc and cfg files, there's a file : cfg/debug/kgdb/debug-kgdb-serial-console.scc~ which looks like an open file by an editor, should I remove the file? | 08:44 |
| yacar_ | zeddii: I misspelled your pseudo sorry ! | 08:45 |
| *** prabhakarlad <prabhakarlad!c18ddb24@193.141.219.36> has joined #yocto | 08:49 | |
| prabhakarlad | Hi all, what is the correct way to append COMPATIBLE_MACHINE for a recipe | 08:49 |
| mckoan | prabhakarlad: can you describe better your question? | 08:55 |
| Domin1k | prabhakarlad: https://www.yoctoproject.org/docs/latest/bitbake-user-manual/bitbake-user-manual.html#appending-and-prepending i prefere += | 08:55 |
| Domin1k | prabhakarlad: COMPATIBLE_MACHINE is just a variable | 08:56 |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 08:59 | |
| prabhakarlad | Domin1k COMPATIBLE_MACHINE += doesnt work, nor does _append | 08:59 |
| *** tprrt <tprrt!~tprrt@217.114.204.178> has joined #yocto | 09:02 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 09:03 | |
| Domin1k | prabhakarlad: oh sorry im wrong. it looks like it should be made like this COMPATIBLE_MACHINE = "qemux86|qemux86-64" | 09:03 |
| prabhakarlad | yes, but how do we append it in a bbappend file ? | 09:05 |
| *** woutervh <woutervh!~woutervh@84.199.255.188> has joined #yocto | 09:08 | |
| Domin1k | prabhakarlad: i would guess doing COMPATIBLE_MACHINE += "|my_new_machine". But if you say this does not work i would wait until an yocto expert answers your question. I'm just a rookie that is trying to help. | 09:09 |
| LetoThe2nd | Domin1k: i'd guess thats pretty close, yet _append instead of +=. because append doesn't insert a blank space | 09:10 |
| Domin1k | LetoThe2nd: (y) | 09:12 |
| prabhakarlad | LetoThe2nd, the original bb file has COMPATIBLE_MACHINE = "(qemux86|qemux86-64)" so now when I create a bbappend file and do +=/append it doesnt work. | 09:13 |
| Domin1k | prabhakarlad: it looks like the ) makes it unappendable | 09:15 |
| *** prabhakarlad <prabhakarlad!c18ddb24@193.141.219.36> has quit IRC | 09:16 | |
| *** dreyna_ <dreyna_!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 09:20 | |
| Domin1k | Im wondering if ther is a good way handling with big rescources in bitbake? I Have a Repo with a lot of rescources like Images, Videos etc. I would like to install them to my Image directly within the bitbake process. But it looks like the bitbake duplikates these files quite often. I have the fetched resources in the workdir, a duplicate as a | 09:23 |
| Domin1k | tar.gz inside the folder "build/download/", the rpm-package and finaly inside my wic-image. By now i need about 1.2 TB of diskspace for a build. | 09:23 |
| LetoThe2nd | Domin1k: all which is some form opf payload isn't really meant to go into the layers. the layers, as the meta- already suggests, should not contain those images, videos, etc. | 09:26 |
| LetoThe2nd | Domin1k: if you have already properly split them out into a payload recipe that fetches them, then i'm not aware of any redcution technique at the moment. | 09:27 |
| Domin1k | What do you actually mean with a payload recipe? I have a recipe that builds my app within my own foo_poky/meta-foocraft/ layer inside this recipe i have seprerated the resources in a package with PACKAGES += "${PN}-resources" FILES_${PN}-resources += "/mnt/app/resources/*" | 09:34 |
| *** kroon <kroon!~kroon@213.185.29.22> has joined #yocto | 09:35 | |
| LetoThe2nd | Domin1k: seperating means, the recipe pulls the resourced from some out-of tree location, like ftp or whatever, as does not acutally contain them as files next to the recipe. | 09:37 |
| Domin1k | LetoThe2nd: I pull them from a clearcase-vob (VCS-repository) so that should be ok. I have to ask my boss for another diskupgrade then. | 09:42 |
| LetoThe2nd | Domin1k: "you wann make big app boss, you gonna big disk boss"" | 09:43 |
| LetoThe2nd | +buy | 09:43 |
| Domin1k | LetoThe2nd: for a development scenario this isn't that much relevant. I could build the image without the app resources and work with a nfs mount from my device to the resources repo on my workstation | 09:44 |
| Domin1k | LetoThe2nd: the final size of the wic image is just 234 GB but needing 5 times that much to build this image sounds a bit crazy. | 09:47 |
| *** marler899721 <marler899721!0f41fc0d@ztxe01hpics303.austin.hp.com> has quit IRC | 09:48 | |
| LetoThe2nd | Domin1k: our images are usually ~40M and we need 30GB or 40GB to build them. don't you think my "why does it need a thousand times the space for the build" sounds more crazy than your 5? | 09:49 |
| *** yacar_ <yacar_!~yacar@80.215.198.20> has quit IRC | 09:51 | |
| *** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC | 09:51 | |
| *** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto | 09:52 | |
| Domin1k | LetoThe2nd: My boss thinks we would do better using a ubuntu image. At the moment we are using a stripped down debian image but i'm sure yocto will help us to build a better image and solve a lot of issues that we have at the moment with our current image-build-environment. | 09:53 |
| LetoThe2nd | Domin1k: it all depends on the use case, and using debian/ubunt can be totally valid too. it all depend. | 09:55 |
| LetoThe2nd | Domin1k: you can of course use some evil magic and "inject" the payload through some rootfs postprocessing, but it kinda defeats the point of OE/yocto. and if thats only for the couple of bucks that some disk space costs, its a bad deal taking the maintenance effort into account. | 09:56 |
| *** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 10:05 | |
| *** coretec <coretec!d43ed5a2@212.62.213.162> has quit IRC | 10:19 | |
| *** learningc <learningc!~learningc@mti-37-145.tm.net.my> has quit IRC | 10:22 | |
| *** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has quit IRC | 10:32 | |
| *** Domin1k <Domin1k!c1669b04@193.102.155.4> has quit IRC | 10:39 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 10:43 | |
| *** bluca <bluca!~bluca@88.98.246.218> has joined #yocto | 10:50 | |
| *** learningc <learningc!~learningc@121.121.98.53> has joined #yocto | 11:03 | |
| *** yann|work <yann|work!~yann@85.118.38.73> has joined #yocto | 11:06 | |
| *** thinkmassive <thinkmassive!thinkmassi@gateway/shell/matrix.org/x-xuotgbrxnczvzdmq> has quit IRC | 11:07 | |
| *** kayterina <kayterina!kayterina-@gateway/shell/matrix.org/x-hwulrotpyicgmrnb> has quit IRC | 11:07 | |
| *** nrossi <nrossi!nrossimatr@gateway/shell/matrix.org/x-euabtsighxzzilgj> has quit IRC | 11:07 | |
| *** bachp <bachp!bachpmatri@gateway/shell/matrix.org/x-lbmyizapxypkkluc> has quit IRC | 11:07 | |
| *** MarcWe1 <MarcWe1!hmwmatrixo@gateway/shell/matrix.org/x-zfbnqdxpsrujppra> has quit IRC | 11:07 | |
| *** wak-work <wak-work!wak-workma@gateway/shell/matrix.org/x-bbppztpiixhozaer> has quit IRC | 11:07 | |
| *** silviof <silviof!silv-iomat@gateway/shell/matrix.org/x-cohmpvvguynesgub> has quit IRC | 11:07 | |
| __angelo | hi folks :) question : i see different directory layouts when yocto-based distros are created, what should be a good directory layout to use ? | 11:10 |
| rburton | personally i put bitbake and all the layers alongside each other | 11:11 |
| rburton | assuming thats what you mean | 11:11 |
| __angelo | rburton, yes. I find different layouts around, probably coming from different tutorial/how to | 11:11 |
| __angelo | rburton, so you use kind of older oe style, right ? | 11:12 |
| rburton | not sure i'd call it old | 11:12 |
| *** thomasd13 <thomasd13!d472ff94@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC | 11:13 | |
| __angelo | ok. so you are not using poky stuff ? | 11:14 |
| rburton | that' a good example of bitbake and layers all in one place | 11:16 |
| rburton | *poky is an example* | 11:16 |
| rburton | if you want your own distro make your own distro | 11:16 |
| rburton | otherwise you'll be upset when eg poky changes | 11:16 |
| rburton | (which is does, often) | 11:17 |
| *** yacar_ <yacar_!~yacar@80.215.134.112> has joined #yocto | 11:17 | |
| __angelo | many thanks | 11:17 |
| *** bachp <bachp!bachpmatri@gateway/shell/matrix.org/x-pwzobiuhiagwffxn> has joined #yocto | 11:17 | |
| *** ThomasD13 <ThomasD13!d472ff94@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto | 11:21 | |
| __angelo | about "upset when eg poky changes", this is not totally clear. Can i fix to a revision and work on that ? | 11:25 |
| LetoThe2nd | __angelo: for example when you update from sumo to thud, to warrior, there might be changes in poky | 11:26 |
| *** pepone <pepone!~user@197.red-88-27-200.staticip.rima-tde.net> has joined #yocto | 11:31 | |
| __angelo | LetoThe2nd, ok | 11:32 |
| pepone | Hey, I'm trying to track down a bug with network stack in core-image-minimal, what is the default libc build with core-image-minimal? | 11:32 |
| __angelo | thanks | 11:33 |
| *** nrossi <nrossi!nrossimatr@gateway/shell/matrix.org/x-jmbiebujxfyouvjo> has joined #yocto | 11:33 | |
| *** silviof <silviof!silv-iomat@gateway/shell/matrix.org/x-zxccmwwttecdsqzy> has joined #yocto | 11:33 | |
| LetoThe2nd | pepone: glibc | 11:34 |
| pepone | I getting some issues with TCP close connection, specially sever sending TCP FIN/RST gets unoticed by client, server connection gets closed but client conn remains open | 11:36 |
| *** berton <berton!~berton@181.220.83.67> has joined #yocto | 11:37 | |
| pepone | testing with a bunch of distros and only getting this issues with Yocto Warrior | 11:37 |
| kanavin_ | pepone, are you using the latest warrior? | 11:40 |
| pepone | 2.7.1 | 11:40 |
| rburton | pepone: what kernel though | 11:40 |
| pepone | 38d5c8ea98cfa49825c473eba8984c12edf062be | 11:40 |
| rburton | pepone: most BSPs provide their own kernel | 11:40 |
| kanavin_ | particularly, you probably need this fix | 11:41 |
| kanavin_ | commit f5cc3bf166c8eca58630e267cc58bdd88fbc6e95 | 11:41 |
| kanavin_ | Author: Bruce Ashfield <bruce.ashfield@gmail.com> | 11:41 |
| kanavin_ | Date: Fri Apr 26 10:52:17 2019 -0400 | 11:41 |
| kanavin_ | linux-yocto/5.0: integrate TCP timeout / hang fix | 11:41 |
| kanavin_ | 11:41 | |
| kanavin_ | it was a bug in 5.0 kernels | 11:41 |
| pepone | 5.0.3-yocto-standard #1 PREEMPT Mon Sep 9 17:44:34 UTC 2019 armv7l armv7l armv7l GNU/Linux | 11:41 |
| pepone | kanavin_: Thanks I will give it a try if I manage to update the BB kernel | 11:43 |
| rburton | that was in 2.7.1 though | 11:44 |
| *** tgamblin <tgamblin!~tgamblin@128.224.252.2> has joined #yocto | 11:44 | |
| *** jij <jij!jonashg@nat/axis/x-ugwcqvgzevzigrmf> has joined #yocto | 11:46 | |
| pepone | Yes I have that commit in my tree | 11:47 |
| *** berton <berton!~berton@181.220.83.67> has quit IRC | 11:59 | |
| *** berton <berton!~berton@181.220.83.67> has joined #yocto | 11:59 | |
| *** nighty- <nighty-!~nighty@b157153.ppp.asahi-net.or.jp> has joined #yocto | 12:09 | |
| *** kroon <kroon!~kroon@213.185.29.22> has quit IRC | 12:12 | |
| *** goliath <goliath!~goliath@37-247-85-246.natip.skydsl.at> has joined #yocto | 12:18 | |
| *** pharaon2502 <pharaon2502!~hropatest@89.201.166.50> has left #yocto | 12:24 | |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 12:24 | |
| *** orzen <orzen!~orz@84-216-100-149.customers.ownit.se> has quit IRC | 12:30 | |
| *** Domin1k <Domin1k!c1669b04@193.102.155.4> has joined #yocto | 12:31 | |
| *** orzen <orzen!~orz@84-216-100-149.customers.ownit.se> has joined #yocto | 12:37 | |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC | 12:45 | |
| *** woutervh <woutervh!~woutervh@84.199.255.188> has quit IRC | 12:55 | |
| *** Crofton <Crofton!~Crofton@50.224.179.20> has joined #yocto | 12:58 | |
| *** goliath <goliath!~goliath@37-247-85-246.natip.skydsl.at> has quit IRC | 13:03 | |
| zeddii | RP: at least we got a bit of interest in the strace report on lkml. | 13:06 |
| RP | zeddii: yes, I saw. Hopefully we can get them to reproduce it and then get somewhere :) | 13:07 |
| zeddii | I had to scramble to dig up the manual build steps for it, I hope I didn't screw them up :D | 13:08 |
| *** ThomasD13 <ThomasD13!d472ff94@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC | 13:11 | |
| RP | zeddii: we'll see what they say and worst case we may have to come up with a simpler reprocuder | 13:11 |
| RP | vmeson: ^^^ | 13:12 |
| *** Domin1k <Domin1k!c1669b04@193.102.155.4> has quit IRC | 13:13 | |
| *** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has joined #yocto | 13:20 | |
| *** pepone <pepone!~user@197.red-88-27-200.staticip.rima-tde.net> has quit IRC | 13:25 | |
| kanavin_ | zeddii, do you have a link? | 13:27 |
| *** thomasd13 <thomasd13!d472ff94@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto | 13:28 | |
| zeddii | kanavin_, https://lkml.org/lkml/2019/10/1/789 | 13:31 |
| *** iceaway2_ <iceaway2_!~pelle@37.233.78.69> has quit IRC | 13:32 | |
| kanavin_ | zeddii, thanks, hope they manage to reproduce | 13:32 |
| kanavin_ | zeddii, it does not happen on opensuse's 5.2 kernel though :( | 13:32 |
| thomasd13 | When I specify a kernel feature with KERNEL_FEATURES_append , does it matter if this feature is built in the kernel or if it is provided as kernel module? | 13:33 |
| *** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has quit IRC | 13:35 | |
| *** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has joined #yocto | 13:39 | |
| zeddii | kanavin_: there may be some kernel config at play then. I saw it on a mainline test that I ran, but I’ll revisit that before they tell me they can’t reproduce it. I suppose I could diff the opensuse 5.2 kernel to see if they have a patch in that area. | 13:42 |
| kanavin_ | zeddii, yes, also maybe running the test on physical hardware could help narrow it down | 13:44 |
| kanavin_ | (e.g. nuc or something like that) | 13:44 |
| zeddii | I saw it on linux-yocto-dev as well, which is pretty much a raw mainline kernel, so I know it wasn’t fixed in the 5.3 cycle. but the kernel config is very similar to the 5.2 one we use. I’m going to test 5.4-rc1 shortly to see if it is there. | 13:45 |
| kanavin_ | it might be specific to qemu | 13:46 |
| zeddii | I don’t have any h/w test boxes handy to test on. Do we have results for 5.2 on genericx86-64 that don’t show the issue ? or do we not run those there .. or is that not h/w ? I’m not aware of all the details there. | 13:47 |
| *** AndersD <AndersD!~AndersD@h83-209-191-235.cust.a3fiber.se> has joined #yocto | 13:50 | |
| kanavin_ | I don't think the AB has any real HW, everything runs through qemu, maybe RP can clarify | 13:51 |
| RP | kanavin_: all AB stuff runs on qemu. There are manual QA tests, its unclear if they'd run the ptests on the real hardware though | 14:03 |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 14:04 | |
| *** lfa <lfa!~lfa@217.19.35.51> has quit IRC | 14:07 | |
| *** thomasd13 <thomasd13!d472ff94@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC | 14:18 | |
| *** tprrt <tprrt!~tprrt@217.114.204.178> has quit IRC | 14:59 | |
| *** behanw <behanw!uid110099@gateway/web/irccloud.com/x-bntukftaoffzqiwo> has joined #yocto | 15:12 | |
| *** yacar_ <yacar_!~yacar@80.215.134.112> has quit IRC | 15:12 | |
| *** Crofton <Crofton!~Crofton@50.224.179.20> has quit IRC | 15:30 | |
| *** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC | 15:35 | |
| *** yacar_ <yacar_!~yacar@80.215.134.112> has joined #yocto | 15:49 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 15:52 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 15:52 | |
| *** yann|work <yann|work!~yann@85.118.38.73> has quit IRC | 15:54 | |
| *** Crofton <Crofton!~Crofton@167.220.105.17> has joined #yocto | 15:55 | |
| *** learningc <learningc!~learningc@121.121.98.53> has quit IRC | 16:04 | |
| *** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 16:14 | |
| *** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has quit IRC | 16:15 | |
| Crofton | The autobuilder runs on imaginary hardware | 16:16 |
| *** yacar_ <yacar_!~yacar@80.215.134.112> has quit IRC | 16:20 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 16:20 | |
| mckoan | Crofton: LOL | 16:21 |
| *** mckoan is now known as mckoan|away | 16:25 | |
| *** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 16:29 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 16:58 | |
| *** vineela <vineela!~vtummala@134.134.139.83> has joined #yocto | 17:02 | |
| RP | Crofton: I'm now thinking we'd have to number them with imaginary numbers | 17:08 |
| Crofton | of course | 17:08 |
| Crofton | A guy asked me about this email last night | 17:09 |
| Crofton | https://lists.yoctoproject.org/pipermail/yocto/2019-June/045574.html | 17:09 |
| Crofton | Looks like no repleis | 17:09 |
| JPEW | I was thinking that wouldn't be hard too add an optional QA check for that case. | 17:10 |
| Crofton | I you care about reproducible builds AUTOREV in a recipe is a serious issue | 17:14 |
| JPEW | Right, I think they understood that the layers are poorly written(?) since AUTOREV is non-optional, but there's no tool to detect it ATM | 17:15 |
| JPEW | The hard part is making AUTOREV a valid option (e.g. not fail QA) when it does make sense and someone does actually want it... | 17:17 |
| JPEW | Maybe tie the QA check to the reproducibl_build.bbclass? | 17:17 |
| JPEW | Sounds like I'm volunteering to reply to the email :) | 17:18 |
| Crofton | RP ^^^ | 17:21 |
| RP | JPEW: sounds like the right track to me FWIW | 17:22 |
| Crofton | ah yes, I was going there was a class that flagged the system we super care about reproducibilty | 17:22 |
| Crofton | Stuff like this is why we need to get out and actually meet with people. He pointed the email out to us last night | 17:23 |
| RP | Indeed. I tend to feel bad as there are a lot of emails that should get replies that don't | 17:24 |
| Crofton | https://blog.3mdeb.com/ | 17:25 |
| Crofton | https://blog.3mdeb.com/2019/2019-08-07-qubes-os-and-3mdeb-minisummit/ | 17:26 |
| Crofton | second blog post needs review | 17:28 |
| JPEW | RP, Crofton: Does this look OK: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13567 ? | 17:51 |
| yocti | Bug 13567: normal, Undecided, ---, ross.burton, NEW , Add QA check for recipes that use AUTOREV by default | 17:51 |
| Crofton | Yes, we don't want to trip people expecting a reproducible build with autorev recieps | 17:53 |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 18:25 | |
| yocti | New news from stackoverflow: Failure while compiling apt - Yocto <https://stackoverflow.com/questions/57294288/failure-while-compiling-apt-yocto> | 18:30 |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 18:43 | |
| *** tgamblin <tgamblin!~tgamblin@128.224.252.2> has quit IRC | 18:59 | |
| *** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto | 19:03 | |
| *** bluca <bluca!~bluca@88.98.246.218> has quit IRC | 19:09 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:13 | |
| yocti | New news from stackoverflow: Adding sqlite Qt5 plugin in Yocto <https://stackoverflow.com/questions/58208176/adding-sqlite-qt5-plugin-in-yocto> | 19:30 |
| Tartarus | RP: Can you tag bitbake 1.43.2 please? | 19:36 |
| RP | Tartarus: I can but there aren't many tags in there :/ | 19:37 |
| Tartarus | There's only 44 tags I see, yeah | 19:37 |
| Tartarus | imho, tags for BB_MIN_VERSION values is helpful for ease of switching branches around | 19:37 |
| RP | Tartarus: probably, I just now worry which other ones I'll be asked for | 19:38 |
| Tartarus | sec ;) | 19:39 |
| Tartarus | 1.39.1, which is what thud asks for | 19:40 |
| Tartarus | older than that is no longer actively supported | 19:40 |
| RP | already there | 19:40 |
| Tartarus | So shrug | 19:40 |
| Tartarus | er | 19:40 |
| Tartarus | heh | 19:40 |
| * Tartarus kicks bitbake | 19:40 | |
| * Tartarus kicks git | 19:40 | |
| RP | careful, bitbake can kick back ;-) | 19:41 |
| Tartarus | So, yeah, I think with that, that's enough tags now | 19:41 |
| Tartarus | and hopefully a mental note to tag bitbake when bumping BB_MIN_VERSION in the future will be 'it'. | 19:42 |
| RP | Tartarus: I will try | 19:42 |
| Tartarus | thanks! | 19:43 |
| radsquirrel | is there something written down out there that helps you decide when to use = vs ?= vs ??= | 19:49 |
| radsquirrel | and _append vs += | 19:49 |
| radsquirrel | from a best practices point of view. | 19:49 |
| *** Ad0 <Ad0!~Ad0@93.124.245.194> has quit IRC | 19:55 | |
| kroon | radsquirrel, there is always the bitbake manual | 19:55 |
| kroon | radsquirrel, I think I've seen some bitbake cheat sheet aswell | 19:55 |
| *** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 19:55 | |
| *** Ad0 <Ad0!~Ad0@93.124.245.194> has joined #yocto | 20:00 | |
| mischief | what is the variable ROOTFS_BOOTSTRAP_INSTALL for? | 20:00 |
| *** yates <yates!~user@rrcs-96-10-234-158.midsouth.biz.rr.com> has joined #yocto | 20:02 | |
| yates | do .rpm packages provide a method to run pre- and/or post-install scripts, or are they basically just files which get copied over? | 20:03 |
| yates | and/or does "smart" provide such a capability on top of the .rpm file installation? | 20:04 |
| bluelightning | yates: we do intrinsically support pre/postinstall (and pre-postuninstall) scripts, and they get funnelled through into the packages (rpms in this case) | 20:07 |
| bluelightning | yates: smart supports them in as much that it calls rpm and rpm will run them | 20:07 |
| bluelightning | the only "special" bit is that when building the image, we try to execute them on the build host, and if they succeed then great - if not, they get deferred to first boot | 20:08 |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 20:08 | |
| bluelightning | (which of course won't work if you are using a read-only rootfs) | 20:08 |
| bluelightning | there is a little bit of magic to explicitly mark postinsts that are known to require running on the target in more recent versions but if you're talking about smart I suspect that won't apply in your case | 20:09 |
| bluelightning | the best practice is to try to ensure the postinstalls *can* run during image construction | 20:09 |
| bluelightning | what that really means is use $D in front of paths | 20:10 |
| bluelightning | and don't assume any special hardware is there | 20:10 |
| yates | bluelightning: the scripts are put into the .rpm file? | 20:10 |
| yates | what do you mean by "first boot"? | 20:11 |
| yates | deferred to first boot? | 20:11 |
| kergoth | it means exactly what it says. they run the first time the device boots. which isn't viable on an r/o fs | 20:12 |
| yates | why can't you run a first-boot script on a r/o fs? | 20:14 |
| yates | because they have to be deleted after first boot? | 20:14 |
| yates | bluelightning: so it seems there is a provision in both the .rpm format and in yocto to do this. | 20:15 |
| bluelightning | yates: yes and yes | 20:15 |
| yates | does the now-ancient morty support this? | 20:16 |
| bluelightning | yes | 20:16 |
| bluelightning | we've had it for a very long time | 20:16 |
| yates | bluelightning: thanks for this info. Very valuable. | 20:16 |
| bluelightning | np | 20:16 |
| *** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 20:28 | |
| *** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC | 20:44 | |
| radsquirrel | kroon: I've definitely read the bitbake manual. | 20:53 |
| radsquirrel | it describes the differences in behaviors between the different operators very well. | 20:54 |
| radsquirrel | was looking more for the "why" | 20:54 |
| radsquirrel | I have been thinking about starting a blog. my first post might be called "how to choose a bitbake variable assignment operator" | 20:59 |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 21:00 | |
| ecdhe | that's great radsquirrel | 21:00 |
| ecdhe | I still don't know what ?= means | 21:00 |
| ecdhe | I'm not sure how to search for it on google or what the name of the operator is | 21:00 |
| radsquirrel | it means if the same variable has been assigned previously with = it won't take your assignment with ?= | 21:01 |
| radsquirrel | by previously I mean in the global configuration (so something assigned by way of bitbake.conf) | 21:01 |
| radsquirrel | or in the case of a recipe and a bbappend, previously would mean the recipe | 21:02 |
| ecdhe | nice and contextually ambiguous -- makes debugging so much easier when you can't tell what the effect of it will be just by looking at it. | 21:02 |
| radsquirrel | well...I'll see what I can do about the blog :-) | 21:03 |
| radsquirrel | and if anyone wants to drop hints on why I might pick = over ?= or ??= over ?= ... feel free. | 21:03 |
| radsquirrel | I'll include them. | 21:03 |
| *** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 21:04 | |
| mischief | is there a way to specify some packages on a per-machine basis that are initramfs only? or should i invent a new variable? | 21:10 |
| *** berton <berton!~berton@181.220.83.67> has quit IRC | 21:15 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 21:18 | |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 21:24 | |
| *** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 21:24 | |
| *** falstaff <falstaff!~quassel@37.17.234.113> has quit IRC | 21:25 | |
| *** Hauke <Hauke!~Hauke@hauke-m.de> has quit IRC | 21:28 | |
| *** yann <yann!~yann@91-170-159-152.subs.proxad.net> has joined #yocto | 22:06 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 22:17 | |
| kergoth | ugh, the vscode bitbake extensions reliably hang my Remote - SSH workspace when opening a medium sized .inc. at least, the two extensions that work at all do | 22:27 |
| kergoth | guess i'll do without highlighting for now.. | 22:28 |
| *** agust <agust!~agust@p54833695.dip0.t-ipconnect.de> has quit IRC | 22:37 | |
| khem | kergoth: or switch to neovim :) | 22:38 |
| kergoth | that's what i usually use, been playing around with vscode + Remote - SSH recently | 22:38 |
| khem | yeah vscode is quite good IDE, I would say | 22:39 |
| khem | I use it quite a lot myself but time and again nvim fallback is used :) | 22:40 |
| khem | for kernel sources it works fine | 22:40 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 22:50 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 23:23 | |
| *** Hauke <Hauke!~Hauke@hauke-m.de> has joined #yocto | 23:56 | |
| *** vineela <vineela!~vtummala@134.134.139.83> has quit IRC | 23:59 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!