Tuesday, 2023-08-08

*** olani <olani!~olani@31-208-215-228.cust.bredband2.com> has joined #yocto00:43
*** olani- <olani-!~olani@31-208-215-228.cust.bredband2.com> has joined #yocto00:43
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Quit: Leaving.)01:02
*** Ablu <Ablu!~Ablu@user/Ablu> has quit IRC (Ping timeout: 245 seconds)01:32
*** LocutusOfBorg <LocutusOfBorg!~locutusof@151.58.174.15> has quit IRC (Quit: ZNC 1.8.2+deb3 - https://znc.in)01:33
*** Ablu <Ablu!~Ablu@user/Ablu> has joined #yocto01:36
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)01:57
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto01:57
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 260 seconds)02:26
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto02:28
*** jclsn <jclsn!~jclsn@2a04:4540:651f:2a00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 240 seconds)02:43
*** jclsn <jclsn!~jclsn@2a04:4540:6517:9900:2ce:39ff:fecf:efcd> has joined #yocto02:45
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto03:00
*** otavio_ <otavio_!~otavio@189-11-177-7.user3p.brasiltelecom.net.br> has quit IRC (Ping timeout: 246 seconds)03:09
*** otavio_ <otavio_!~otavio@189-11-177-7.user3p.brasiltelecom.net.br> has joined #yocto04:01
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has quit IRC (Quit: Leaving.)05:09
*** xmn <xmn!~xmn@2600:4040:9390:8c00:d446:8458:e6a6:355e> has quit IRC (Ping timeout: 240 seconds)05:51
*** yocti` <yocti`!~limnoria@mail.yoctoproject.org> has joined #yocto06:06
*** yocti <yocti!~limnoria@mail.yoctoproject.org> has quit IRC (Killed (NickServ (GHOST command used by yocti`)))06:06
*** zeddiii <zeddiii!~zeddii@174.112.183.231> has joined #yocto06:07
*** yocti` is now known as yocti06:07
*** ChanServ sets mode: +o yocti06:07
*** Amynka_ <Amynka_!~amy@gentoo/developer/amynka> has joined #yocto06:07
*** Ch^W_ <Ch^W_!~mouser@ec2-34-223-147-188.us-west-2.compute.amazonaws.com> has joined #yocto06:07
*** tct <tct!~tct@user/tct> has joined #yocto06:08
*** targetdi1k <targetdi1k!~daemonchi@45-33-4-162.ip.linodeusercontent.com> has joined #yocto06:08
*** sotaover3ide <sotaover3ide!~sotaoverr@ool-4578fe22.dyn.optonline.net> has joined #yocto06:09
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto06:12
*** sotaover1ide <sotaover1ide!~sotaoverr@ool-4578fe22.dyn.optonline.net> has quit IRC (*.net *.split)06:12
*** tokamak <tokamak!~Tokamak@2603:c020:4004:fff:9f61:fd7:3164:946a> has quit IRC (*.net *.split)06:12
*** silbe <silbe!~silbe@2a03:4000:20:16f:96de:80ff:fe22:1aaa> has quit IRC (*.net *.split)06:12
*** zeddii <zeddii!~zeddii@174.112.183.231> has quit IRC (*.net *.split)06:12
*** tin_ <tin_!uid610731@id-610731.ilkley.irccloud.com> has quit IRC (*.net *.split)06:12
*** Amynka <Amynka!~amy@gentoo/developer/amynka> has quit IRC (*.net *.split)06:12
*** Crofton <Crofton!sid401373@id-401373.lymington.irccloud.com> has quit IRC (*.net *.split)06:12
*** targetdisk <targetdisk!~daemonchi@45-33-4-162.ip.linodeusercontent.com> has quit IRC (*.net *.split)06:12
*** halstead <halstead!sid505447@id-505447.ilkley.irccloud.com> has quit IRC (*.net *.split)06:12
*** praneeth_ <praneeth_!sid506451@id-506451.tinside.irccloud.com> has quit IRC (*.net *.split)06:12
*** flynn378 <flynn378!sid63564@id-63564.ilkley.irccloud.com> has quit IRC (*.net *.split)06:12
*** Ch^W <Ch^W!~mouser@ec2-34-223-147-188.us-west-2.compute.amazonaws.com> has quit IRC (*.net *.split)06:12
*** stacktrust_ <stacktrust_!sid452860@id-452860.hampstead.irccloud.com> has quit IRC (*.net *.split)06:12
*** jbo <jbo!~tct@user/tct> has quit IRC (*.net *.split)06:12
*** smurray <smurray!sid98062@id-98062.hampstead.irccloud.com> has quit IRC (*.net *.split)06:12
*** olof <olof!zibri@shell.x20.se> has quit IRC (*.net *.split)06:12
*** MrFrank <MrFrank!~MrFrank@mx1.fracta.dev> has quit IRC (*.net *.split)06:12
*** stacktrust_ <stacktrust_!sid452860@id-452860.hampstead.irccloud.com> has joined #yocto06:17
*** smurray <smurray!sid98062@id-98062.hampstead.irccloud.com> has joined #yocto06:17
*** MrFrank <MrFrank!~MrFrank@mx1.fracta.dev> has joined #yocto06:17
*** praneeth_ <praneeth_!sid506451@id-506451.tinside.irccloud.com> has joined #yocto06:18
*** tin_ <tin_!sid610731@id-610731.ilkley.irccloud.com> has joined #yocto06:18
*** olof <olof!zibri@shell.x20.se> has joined #yocto06:19
*** tokamak <tokamak!~Tokamak@129.158.40.255> has joined #yocto06:19
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:25
*** flynn378 <flynn378!sid63564@id-63564.ilkley.irccloud.com> has joined #yocto06:32
*** halstead <halstead!sid505447@id-505447.ilkley.irccloud.com> has joined #yocto06:32
*** Crofton <Crofton!sid401373@id-401373.lymington.irccloud.com> has joined #yocto06:32
LetoThe2ndyo dudX06:41
*** frieder <frieder!~frieder@i5C75E643.versanet.de> has joined #yocto06:55
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto06:55
*** zpfvo <zpfvo!~fvo@i59F5CF6E.versanet.de> has joined #yocto06:56
*** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has joined #yocto07:05
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto07:05
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Remote host closed the connection)07:06
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto07:07
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto07:21
*** pabigot <pabigot!~pab@34.sub-75-236-174.myvzw.com> has quit IRC (Ping timeout: 246 seconds)07:23
*** pabigot <pabigot!~pab@34.sub-75-236-174.myvzw.com> has joined #yocto07:38
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto07:42
*** Guest23 <Guest23!~Guest58@194.39.218.19> has joined #yocto07:43
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:51
*** davidinux <davidinux!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has joined #yocto07:53
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)08:07
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto08:07
*** davidinux <davidinux!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has quit IRC (Ping timeout: 246 seconds)08:11
*** davidinux <davidinux!~davidinux@176.227.242.119> has joined #yocto08:11
*** AndreRicardo <AndreRicardo!~AndreRica@155.94.33.143> has joined #yocto08:11
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)08:12
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto08:12
*** davidinux <davidinux!~davidinux@176.227.242.119> has quit IRC (Ping timeout: 240 seconds)08:15
*** silbe <silbe!~silbe@2a03:4000:20:16f:96de:80ff:fe22:1aaa> has joined #yocto08:18
*** davidinux <davidinux!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has joined #yocto08:18
*** davidinux1 <davidinux1!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has joined #yocto08:23
*** davidinux <davidinux!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has quit IRC (Ping timeout: 246 seconds)08:24
*** Guest23 <Guest23!~Guest58@194.39.218.19> has quit IRC (Quit: Client closed)08:25
*** Guest23 <Guest23!~Guest23@194.39.218.19> has joined #yocto08:26
Guest23Is it already known whether Poky 4.3 will support building on Fedora 38?08:26
*** el_gatito <el_gatito!~thomas@2a02-a466-e8b5-fd--15.fixed6.kpn.net> has joined #yocto08:27
*** astlep55040 <astlep55040!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has joined #yocto08:31
*** astlep5504 <astlep5504!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has quit IRC (Ping timeout: 246 seconds)08:31
*** davidinux1 <davidinux1!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has quit IRC (Ping timeout: 260 seconds)08:36
LetoThe2ndGuest23: you have think about it in a slightly different way. poky will definitely receive patches to build on newer glibcs, probably relatively soon. so in the beginning, it will build on F38, expectedly. and once they do the next glibc update, it will probably break again. this is a peculiarity of fedora, and anything that is a rolling release.08:40
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has joined #yocto08:42
*** davidinux1 <davidinux1!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has joined #yocto08:42
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has quit IRC (Ping timeout: 256 seconds)08:46
*** mvlad <mvlad!~mvlad@2a02:2f08:4c1b:8200:7656:3cff:fe3f:7ce9> has joined #yocto08:48
*** davidinux1 <davidinux1!~davidinux@ftip004290803.acc4.faraday.21cn-nte.bt.net> has quit IRC (Ping timeout: 256 seconds)08:48
adrianfGuest23: For me Fedora 38 works without problems since uninative was updated (kirkstone, master). The question is probably when it will be added to SANITY_TESTED_DISTROS.08:51
*** mihai <mihai!~mihai@user/mihai> has quit IRC (Quit: Leaving)08:53
Guest23Yeah for mickledore it also works though there was some recipe in meta-intel which I cannot remember currently which did not work with the newer glibc version08:55
Guest23Oh it was not even meta-intel, it was OVMF. Which I had to patch to use uninative 4.008:56
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has joined #yocto09:11
RPadrianf: we usually do that once we have some builds confirming things work..09:11
RPI wish we did better at the process but it does involve multiple people and steps09:12
*** pabigot <pabigot!~pab@34.sub-75-236-174.myvzw.com> has quit IRC (Ping timeout: 245 seconds)09:14
qschulzI tried to build 4.0.11 which I assume has the new uninative but it didn't build on fedora38, so I guess I did something wrong? (it failed in dnf-native at least)09:18
*** pabigot <pabigot!~pab@34.sub-75-236-174.myvzw.com> has joined #yocto09:28
Guest23No, the 4.0 uninative seems to be only used starting with the next Poky 4.3 release: https://github.com/yoctoproject/poky/commit/6ebe71a52eae6b539560aa6a1ea12964dd10ed1e09:28
qschulzGuest23: https://github.com/yoctoproject/poky/commit/43b94d2b8496eae6e512c6deb291b5908b7ada4709:30
Guest23qschulz thanks for the hint, I was still on Mickledore 4.2.1, the backport seems to only be in mickledore 4.2.2. I will try to update09:39
Guest23Related question: Why is there a mickledore-next branch and why is it behind mickledore?09:39
*** davidinux1 <davidinux1!~davidinux@92.118.60.162> has joined #yocto09:42
*** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has quit IRC (*.net *.split)09:52
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC (*.net *.split)09:52
*** hnez <hnez!~quassel@flummi.grey.stw.pengutronix.de> has quit IRC (*.net *.split)09:52
*** dkl <dkl!~dkl@prometheus.umask.eu> has quit IRC (*.net *.split)09:52
*** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has quit IRC (*.net *.split)09:52
*** _lore_ <_lore_!~lorenzo@net-130-25-106-149.cust.vodafonedsl.it> has quit IRC (*.net *.split)09:52
*** ernstp <ernstp!sid168075@id-168075.hampstead.irccloud.com> has quit IRC (*.net *.split)09:52
*** smooge <smooge!~smooge@centos/qa/smooge> has quit IRC (*.net *.split)09:52
*** Fanfwe <Fanfwe!~fanfwe@im.goudal.net> has quit IRC (*.net *.split)09:52
*** polprog <polprog!~ath0@user/polprog> has quit IRC (*.net *.split)09:52
*** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has joined #yocto10:04
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto10:04
*** hnez <hnez!~quassel@flummi.grey.stw.pengutronix.de> has joined #yocto10:04
*** dkl <dkl!~dkl@prometheus.umask.eu> has joined #yocto10:04
*** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has joined #yocto10:04
*** _lore_ <_lore_!~lorenzo@net-130-25-106-149.cust.vodafonedsl.it> has joined #yocto10:04
*** ernstp <ernstp!sid168075@id-168075.hampstead.irccloud.com> has joined #yocto10:04
*** smooge <smooge!~smooge@centos/qa/smooge> has joined #yocto10:04
*** Fanfwe <Fanfwe!~fanfwe@im.goudal.net> has joined #yocto10:04
*** polprog <polprog!~ath0@user/polprog> has joined #yocto10:04
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has quit IRC (Ping timeout: 246 seconds)10:11
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has joined #yocto10:13
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has quit IRC (Ping timeout: 256 seconds)10:19
*** patersonc <patersonc!uid614485@id-614485.hampstead.irccloud.com> has joined #yocto10:26
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)10:47
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto10:48
*** olani <olani!~olani@31-208-215-228.cust.bredband2.com> has quit IRC (Ping timeout: 246 seconds)10:58
*** olani <olani!~olani@66.159.215.7> has joined #yocto10:58
*** olani- <olani-!~olani@31-208-215-228.cust.bredband2.com> has quit IRC (Ping timeout: 246 seconds)10:58
*** olani- <olani-!~olani@66.159.215.7> has joined #yocto10:59
*** zelgomer_ <zelgomer_!~jake@gateway/tor-sasl/zelgomer> has joined #yocto11:16
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)11:17
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto11:17
rburtonzeddiii: am i right in thinking meta-virt and oe-core disagree about python-dtc? our builds are failing as lopper can't find python3-dtc-native11:18
*** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has quit IRC (Ping timeout: 240 seconds)11:18
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has joined #yocto11:46
*** otavio_ <otavio_!~otavio@189-11-177-7.user3p.brasiltelecom.net.br> has quit IRC (Remote host closed the connection)11:47
*** otavio_ <otavio_!~otavio@189-11-177-7.user3p.brasiltelecom.net.br> has joined #yocto11:52
*** g0hl1n <g0hl1n!~g0hl1n@138.199.6.225> has quit IRC (Ping timeout: 245 seconds)11:57
*** g0hl1n <g0hl1n!~g0hl1n@83-215-125-121.dyn.cablelink.at> has joined #yocto11:58
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)12:08
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto12:08
*** Tyaku_ <Tyaku_!~Tyaku@lfbn-orl-1-202-97.w92-152.abo.wanadoo.fr> has joined #yocto12:17
smooge/C/C12:20
smoogewoops sorry12:20
*** Tyaku_ <Tyaku_!~Tyaku@lfbn-orl-1-202-97.w92-152.abo.wanadoo.fr> has quit IRC (Quit: Lost terminal)12:44
*** xmn <xmn!~xmn@pool-71-105-152-109.nycmny.fios.verizon.net> has joined #yocto12:46
zeddiiirburton: I've been away, I'm updating and re-testing my meta-virt master-next now, so I'll fix it shortly if so.12:47
*** valdemaras <valdemaras!~valdemara@86.38.215.134> has joined #yocto12:47
rburtonzeddiii: cool12:47
rburtonGuest23: the next branches are for staging and testing, and are not _guaranteed_ to be in advance of the real branch12:48
LetoThe2ndzeddiii: can I get your gut feeling on backporting docker-compose to kirkston in a custom layer? or is there some version dependency that causes it to be just mickledore and later?12:50
zeddiiidocker-compose is only tricky in that it isn't the python3-docker-compose you want, as it isn't updated anymore, I'm dropping that recipe completely in this release. so it is the docker-compose_git.bb12:53
zeddiiiwhich is a non-vendored git repo, so it has the big SRC_URI to fetch all the bits, I'm not 100% sure if some of those could have go version entanglements with older releases.12:54
LetoThe2ndzeddiii: so building docker-compose_git.bb on kirkstone should be somewhat feasible?12:55
zeddiiiit should be yes. just go itself is the question mark for me.12:56
LetoThe2ndkay. will give it a spin then.12:56
*** AndreRicardo <AndreRicardo!~AndreRica@155.94.33.143> has quit IRC (Quit: Client closed)13:08
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)13:13
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto13:13
d-s-eis it possible to set bitbake dependencies dynamically? Something like mutiple do_sometask[depends] += "${FOO}:do_deploy" inside a do_configure task, with FOO coming from a list of names?13:14
rburtonsure, as long as it evaluates to the right thing and the right point in time13:18
vvnd-s-e: you can do it in an anonymous python13:18
rburtonie this is in the wic class: do_image_wic[depends] += "${@' '.join('%s-native:do_populate_sysroot' % r for r in ('parted', 'gptfdisk', 'dosfstools', 'mtools'))}"13:18
rburtonor do_populate_sdk[depends] += "${@' '.join([x + ':do_populate_sysroot' for x in d.getVar('SDK_DEPENDS').split()])}  ${@d.getVarFlag('do_rootfs', 'depends', False)}"13:19
*** davidinux1 <davidinux1!~davidinux@92.118.60.162> has quit IRC (Ping timeout: 260 seconds)13:20
d-s-eoh yes, python, sometimes I forget the possibilities ;)13:22
*** davidinux1 <davidinux1!~davidinux@185.137.36.189> has joined #yocto13:22
*** Tyaku <Tyaku!~Tyaku@lfbn-orl-1-202-97.w92-152.abo.wanadoo.fr> has joined #yocto13:33
TyakuHi, Is it possible to "force" the rebuild of a recipe on every build ?    My objective is to store in the image, something like the "build date". As we don't always rebuild the image entirely (because we are in development), we cant use the kernel build time or something like that).13:34
TyakuMy objective would be to get a recipe that store in a file the currenttime when "built". I don't know if it's the best option.13:35
*** AndreRicardo <AndreRicardo!~AndreRica@155.94.33.143> has joined #yocto13:35
*** AndreRicardo <AndreRicardo!~AndreRica@155.94.33.143> has quit IRC (Client Quit)13:35
rburtonTyaku: mark the task that does the change with the nostamp flag and it will rerun every time13:36
rburtonthat will mean you rebuild an image even if there's no changes, because you said you wanted it to run fresh every time13:37
*** Cristos <Cristos!~Cristos@2a02:a316:2441:200:336:b44c:5cbe:84ae> has joined #yocto13:38
CristosHello13:38
*** AndreRicardo <AndreRicardo!~AndreRica@155.94.33.143> has joined #yocto13:38
CristosI have a general question regarding Qt5 layer. I need to build it with a particular version of openssl (1.1.1) instead of the default one (3.x). Yet, there is no version of openssl in the qt5 meta layer, just PACKAGECONFIG_OPENSSL and PACKAGECONFIG[openssl] entries. How to write a bbappend to change the openssl version for Qt5?13:41
TyakuHum hum, yeah everytime I call bitbake it will rebuild the rootfs/image. Yeah it's not necessary optimum.13:41
TyakuThere is no such thing directly managed by yocto ? during the image creation for example something that set the current date somewhere ?13:42
rburtonwell only if you ask it for the image13:42
rburtonsure you can absolutely drop a file into the image during rootfs time13:42
*** valdemaras <valdemaras!~valdemara@86.38.215.134> has quit IRC (Quit: valdemaras)13:43
rburtonjust write the file in a rootfs postprocess hook13:43
TyakuIs there something "ready to be used" somewhere or do we have to do it "from scratch" (bbappends on the recipe that generate the rootfs/image.)13:43
Tyakuok13:43
TyakuThanks I will search/check how to do it with your terms.13:44
rburtonyou'll already have /etc/timestamp in your rootfs13:45
rburton_but_ it defaults to a static timestamp for reproducibility, so just unset the right variable13:46
rburtonyou want to look in rootfs-postcommands.bbclass13:46
*** g0hl1n <g0hl1n!~g0hl1n@83-215-125-121.dyn.cablelink.at> has quit IRC (Ping timeout: 245 seconds)13:52
*** sakoman <sakoman!~steve@dhcp-72-234-106-30.hawaiiantel.net> has joined #yocto13:54
*** xmn <xmn!~xmn@pool-71-105-152-109.nycmny.fios.verizon.net> has quit IRC (Quit: ZZZzzz…)13:56
TyakuThanks, I'm trying to set  'REPRODUCIBLE_TIMESTAMP_ROOTFS=""' in the local.conf. First observation: It is rebuilding lot of things (linux-imx etc) so it will take a lot of time on each builds.14:00
TyakuAccording to this. I think one of the best option, will be to configure REPRODUCIBLE_TIMESTAMP_ROOTFS="XXXXXXXXXXX" when we have to build a "release"14:00
Tyaku(manually, with the date of the release)14:01
*** Guest23 <Guest23!~Guest23@194.39.218.19> has quit IRC (Quit: Client closed)14:05
*** LocutusOfBorg <LocutusOfBorg!~locutusof@151.58.174.15> has joined #yocto14:14
*** Tyaku <Tyaku!~Tyaku@lfbn-orl-1-202-97.w92-152.abo.wanadoo.fr> has quit IRC (Quit: Lost terminal)14:15
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has quit IRC (Ping timeout: 245 seconds)14:26
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)14:27
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto14:27
LetoThe2ndzeddiii: it falls over with a ginormous go log and I have NFC what it tries to tell me :-(14:28
zeddiiithe summary is probably "incompatible with this version of go"14:29
LetoThe2ndLOL14:31
LetoThe2nd+114:31
*** zelgomer_ is now known as zelgomer14:31
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)14:32
*** hrberg <hrberg!~quassel@171.79-160-161.customer.lyse.net> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)14:39
*** hrberg <hrberg!~quassel@171.79-160-161.customer.lyse.net> has joined #yocto14:39
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has joined #yocto14:40
*** paulg <paulg!~paulg@104-195-159-20.cpe.teksavvy.com> has joined #yocto14:49
*** davidinux1 <davidinux1!~davidinux@185.137.36.189> has quit IRC (Ping timeout: 245 seconds)14:56
*** davidinux1 <davidinux1!~davidinux@185.137.36.189> has joined #yocto14:56
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Ping timeout: 245 seconds)15:03
*** zeddiii is now known as zeddii15:12
*** AndreRicardo <AndreRicardo!~AndreRica@155.94.33.143> has quit IRC (Quit: Client closed)15:14
*** d-s-e <d-s-e!~d.s.e@i59F7C1F3.versanet.de> has quit IRC (Ping timeout: 246 seconds)15:14
*** goliath <goliath!~goliath@user/goliath> has joined #yocto15:32
kergoth_https://github.com/openembedded/openembedded-core/blob/52572a930b8c3518e07010bafc2a1920d4a11884/meta/lib/oe/utils.py#L104C12-L104C12 there's also a build_depends_string() utility function to add the ":<task>" to a list of deps, regarding the earlier examples from wic/sdk15:48
kergoth_yawn15:48
rburtonkergoth_: oh that's useful15:49
kergoth_Yeah I didn't know that existed until a couple days ago when I happened across a usage :)15:49
rburtononly seven years old15:49
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)15:49
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 260 seconds)15:50
*** Cristos <Cristos!~Cristos@2a02:a316:2441:200:336:b44c:5cbe:84ae> has quit IRC (Quit: Client closed)15:52
*** davidinux1 <davidinux1!~davidinux@185.137.36.189> has quit IRC (Ping timeout: 244 seconds)15:55
*** davidinux1 <davidinux1!~davidinux@185.137.36.189> has joined #yocto15:55
*** pabigot <pabigot!~pab@34.sub-75-236-174.myvzw.com> has quit IRC (Ping timeout: 260 seconds)16:06
RPhalstead: would we be able to make a uninative 4.1 release with master?16:06
halsteadRP: Yes, I need to figure out these internal cert issues first and then I can start on that. Is it ready to queue up now?16:07
RPhalstead: yes, it is ready whenever you are. The cert issues have priority16:08
*** frieder <frieder!~frieder@i5C75E643.versanet.de> has quit IRC (Ping timeout: 245 seconds)16:10
*** pabigot <pabigot!~pab@159.sub-75-236-161.myvzw.com> has joined #yocto16:21
halsteadRP: internal certs are sorted. uninative 4.1 rc1 is building.16:21
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)16:24
*** el_gatito <el_gatito!~thomas@2a02-a466-e8b5-fd--15.fixed6.kpn.net> has quit IRC (Ping timeout: 256 seconds)16:27
*** zpfvo <zpfvo!~fvo@i59F5CF6E.versanet.de> has quit IRC (Remote host closed the connection)16:28
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)16:39
*** florian <florian!~florian@dynamic-093-135-017-158.93.135.pool.telefonica.de> has joined #yocto16:41
RPhalstead: thanks!17:01
*** florian <florian!~florian@dynamic-093-135-017-158.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 256 seconds)17:06
*** davidinux1 <davidinux1!~davidinux@185.137.36.189> has quit IRC (Quit: WeeChat 3.5)17:14
*** valdemaras <valdemaras!~valdemara@86.38.215.134> has joined #yocto17:16
*** valdemaras <valdemaras!~valdemara@86.38.215.134> has left #yocto17:18
*** amitk <amitk!~amit@58.84.60.103> has joined #yocto17:20
*** valdemaras <valdemaras!~valdemara@86.38.215.134> has joined #yocto17:35
*** geoffhp <geoffhp!~geoff@cpe-107-185-48-203.socal.res.rr.com> has joined #yocto17:50
*** rber|res <rber|res!~rber|res@80.155.39.214> has joined #yocto17:53
*** valdemaras <valdemaras!~valdemara@86.38.215.134> has quit IRC (Quit: valdemaras)17:57
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)18:04
*** valdemaras <valdemaras!~valdemara@86.38.215.134> has joined #yocto18:16
*** pbsds <pbsds!~pbsds@84.20.102.94> has quit IRC (Quit: The Lounge - https://thelounge.chat)18:22
*** pbsds <pbsds!~pbsds@84.20.102.94> has joined #yocto18:23
*** alex88 <alex88!~alex88@user/alex88> has quit IRC (Ping timeout: 245 seconds)18:23
*** alex88 <alex88!~alex88@user/alex88> has joined #yocto18:25
*** florian <florian!~florian@dynamic-093-135-017-158.93.135.pool.telefonica.de> has joined #yocto18:28
*** targetdi1k is now known as targetdisk18:47
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 245 seconds)18:50
*** vladest <vladest!~Thunderbi@6.174.199.178.dynamic.wline.res.cust.swisscom.ch> has joined #yocto18:55
*** starblue <starblue!~juergen@dslb-088-078-102-033.088.078.pools.vodafone-ip.de> has joined #yocto18:55
*** amitk <amitk!~amit@58.84.60.103> has quit IRC (Remote host closed the connection)19:01
*** mvlad <mvlad!~mvlad@2a02:2f08:4c1b:8200:7656:3cff:fe3f:7ce9> has quit IRC (Remote host closed the connection)19:12
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat)19:22
*** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto19:22
*** brrm <brrm!~brrm@ip-078-043-203-234.um18.pools.vodafone-ip.de> has quit IRC (Ping timeout: 260 seconds)19:29
*** brrm <brrm!~brrm@ip-078-043-203-234.um18.pools.vodafone-ip.de> has joined #yocto19:29
*** brrm <brrm!~brrm@ip-078-043-203-234.um18.pools.vodafone-ip.de> has quit IRC (Client Quit)19:33
*** brrm <brrm!~brrm@ip-078-043-203-234.um18.pools.vodafone-ip.de> has joined #yocto19:35
*** amitk_ <amitk_!~amit@58.84.60.103> has quit IRC (Ping timeout: 260 seconds)19:36
jonmasonRP: "fix" for qemuarm frambuffer issue is now on lkml https://lore.kernel.org/lkml/20230808140152.3605346-1-jon.mason@arm.com/19:38
jonmasonhopefully this can get either accepted or the can fix it more properly, then we can cherry-pick it back to 6.419:38
RPjonmason: thanks. has this been discussed with zeddii?19:53
*** tct is now known as jbo19:53
jonmasonI asked him about the requirements to get a patch added to linux-yocto, and he said "I rule with an iron fist".  Ok, he didn't say that, but it was implied ;-)19:56
jonmasonpersonally, I'd prefer for it to be accepted upstream, and then we can wait for it to get pulled back into the LTS19:57
jonmasonbut, as you can see, it's fairly tame19:57
zeddiiheh. I'm ok to take the patch whenever. jonmason, feel free to lob it at linux-yocto whenever and I'll put it on the branches. I just finished another round of -stable20:03
RPjonmason, zeddii: given this is the last blocker to getting 6.4 by default, I think we can't wait for upstream...20:06
jonmasonRP: was the systemd thing resolved?20:06
RPjonmason: I have a patch which I believe might20:07
jonmasonok, I'll send to the relevant mailing list20:07
* RP is tempted to ask "which systemd thing"20:07
RPwe have about 5 :/20:07
jonmasonkernel + systemd + networking20:07
RPjonmason: I have a patch for the 6.4 systemd blocker20:08
jonmasonI was going to bisect it, if no one else got to it.  as i _think_ I've fixed the edk2 update issues20:08
RPjonmason: we don't need to, we kind of know what happened20:08
RP(network device renaming was added to the kernel somewhere in 6.2 and systemd triggers off it)20:09
jonmasonI hate systemd20:09
RPjonmason: the thing everyone wants as default? :)20:10
RPjonmason: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=bd039b5ea2a91ea707ee8539df26456bd5be80af apparently20:10
jonmasonit's an invasive species with no predators20:10
*** Guest67 <Guest67!~Guest67@S010600cb7a0e53b5.ed.shawcable.net> has joined #yocto20:11
jonmasonah, I guess that makes sense.  I mean, why not just rename stuff whenever you feel like it, even though you could do it at boot time20:11
Guest67hello, is it possible to specify which steps to skip in a recipe? Say for example, I want to skip the configure and compile step20:11
jonmasonGuest67: I'm not sure it's preferred, but you can just pass in empty functions for those steps20:12
LetoThe2ndGuest67: even in the documentation: https://docs.yoctoproject.org/dev-manual/new-recipe.html#packaging-externally-produced-binaries20:12
Guest67ty20:13
LetoThe2ndGuest67: have fun20:14
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has quit IRC (Quit: Haxxa flies away.)20:15
*** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has joined #yocto20:17
*** rber|res <rber|res!~rber|res@80.155.39.214> has quit IRC (Remote host closed the connection)20:23
*** belgianguy <belgianguy!~belgiangu@ptr-651fbf6ywqpcuutlzxo.18120a2.ip6.access.telenet.be> has joined #yocto20:25
*** vladest <vladest!~Thunderbi@6.174.199.178.dynamic.wline.res.cust.swisscom.ch> has quit IRC (Ping timeout: 246 seconds)20:28
belgianguyHi all, I've stumbled on a board (Myon I, by Keith and Koep) which I wanted to install Linux on. However I can't find meta info for use in Yocto, it has some similarities to DragonBoard410c, would that be a good starting point?20:29
belgianguy(I am very new to all this embedded Linux stuff)20:29
LetoThe2ndbelgianguy: technically i would say "start with meta-qcom and beat it until it works" :)20:31
belgianguyHi @LetoThe2nd, thanks, I had indeed already stumbled on meta-qcom (there are 2 different repos though)20:32
belgianguyAre there any examples that use meta-qcom which detail beatings administered? :)20:34
LetoThe2ndbelgianguy: qcom stuff is not the easiest, unfortunately.i might have somebody who can help you there, but not sure if they are around on IRC20:35
belgianguyI did install Yocto and did its initial "first image tutorial", but now am kinda lost as in what to look into to get the hang of it20:37
belgianguyAs first and foremost I don't want the blue magic smoke to escape from my board :) so I want to check everything that I don't accidentally make a short-lived toaster20:38
LetoThe2ndbelgianguy: "did install yocto" sounds kinda wrong in itself already, sorry. did you follow a specific tutorial? or do you mean you did a first build as outlined on docs.yoctoproject.org?20:38
belgianguyYes, the first build as outlined on the project page20:39
LetoThe2ndbelgianguy: okay. just to sort out the wording then - you did a first build based on the YP technology for a qemu based platform. this did not install anything anywhere.20:40
belgianguyTrue, agreed20:41
LetoThe2ndbelgianguy: so, usually the next two things will be understanding metadata, and board support. its a bit dated now (sorry), but I think this should be helpful: https://www.youtube.com/playlist?list=PLD4M5FoHz-TxMfBFrDKfIS_GLY25Qsfyj20:43
belgianguyLetoThe2nd, ah, thanks, then I will pursue those topics now, and try and see if I can make a jump to the qcom stuff at the end :)20:44
belgianguyor find some other pathways that I need to traverse before attempting that :)20:44
LetoThe2ndbelgianguy: have fun! to be honest, I'd try to get a proper understanding of layers, recipes, machines and distros before actually going for qcom stuff - mostly because handling it properly will require said understanding.20:46
belgianguyLetoThe2nd, added them to the list, the better prepared I am the better the result will be, thanks!20:46
LetoThe2ndnp. off for tonight, then.20:46
belgianguy@LetoThe2nd, thanks and good night!20:47
halsteadRP: I've sent one very borked patch and a corrected patch directly to you for RC testing.21:06
*** zwelch_ <zwelch_!~zwelch@fluffy.mandolincreekfarm.com> has quit IRC (Ping timeout: 245 seconds)21:07
RPhalstead: thanks, I think it might be better if abelloni pulls this in to one of this builds rather than me adding to the mix on the autobuilder!21:08
RPhalstead: I've put the patch in master-next so abelloni can find it21:08
halsteadRP, hopefully you changed the comment ;)21:09
halsteadOr... I suppose it's fine in master-next. We can change it before it goes into master.21:11
*** zwelch <zwelch!~zwelch@fluffy.mandolincreekfarm.com> has joined #yocto21:11
RPhalstead: I was meaning to remind myself to check! The versions didn't change, this one is for new patchelf patches21:13
*** Guest67 <Guest67!~Guest67@S010600cb7a0e53b5.ed.shawcable.net> has quit IRC (Quit: Client closed)21:21
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)21:32
RPhalstead, abelloni: I've started a build with uninative in21:45
RPdl9pf, smurray, denix: There is a uninative test patch in master-next FWIW22:13
*** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has quit IRC (Quit: Leaving.)22:39
*** florian <florian!~florian@dynamic-093-135-017-158.93.135.pool.telefonica.de> has quit IRC (Ping timeout: 256 seconds)22:55
*** camus1 <camus1!~Instantbi@58.246.136.203> has joined #yocto23:00
*** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Remote host closed the connection)23:00
*** camus1 is now known as camus23:00
*** olani- <olani-!~olani@66.159.215.7> has quit IRC (Remote host closed the connection)23:12

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!