Thursday, 2022-02-03

*** nateglims <nateglims!~nateglims@204.246.162.35> has quit IRC (Quit: Client closed)00:04
*** florian_kc <florian_kc!~florian@dynamic-093-132-155-222.93.132.pool.telefonica.de> has joined #yocto00:13
*** d0ku <d0ku!~d0ku@178.43.19.180.ipv4.supernova.orange.pl> has quit IRC (Remote host closed the connection)00:33
*** florian_kc <florian_kc!~florian@dynamic-093-132-155-222.93.132.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)01:02
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC (Quit: Leaving.)01:04
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)01:06
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto01:07
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)01:12
*** jclsn <jclsn!~jclsn@84.242.21.3.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Quit: Ping timeout (120 seconds))01:32
*** jclsn <jclsn!~jclsn@84.242.21.3.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto01:33
*** vmeson <vmeson!~rmacleod@198-48-226-187.cpe.pppoe.ca> has quit IRC (Quit: Konversation terminated!)01:41
*** Tokamak <Tokamak!~Tokamak@172.58.191.35> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)01:55
*** jclsn <jclsn!~jclsn@84.242.21.3.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds)02:09
*** jclsn <jclsn!~jclsn@84.242.21.3.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto02:12
*** ar__ <ar__!~akiCA@user/akica> has quit IRC (Ping timeout: 250 seconds)02:44
*** jclsn0 <jclsn0!~jclsn@149.233.195.74.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto03:20
*** lowfi <lowfi!~lowfi@user/lowfi> has joined #yocto03:22
*** jclsn <jclsn!~jclsn@84.242.21.3.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Ping timeout: 240 seconds)03:22
*** jclsn0 is now known as jclsn03:22
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto03:31
*** amitk <amitk!~amit@103.208.71.118> has joined #yocto03:47
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has quit IRC (Quit: Leaving)03:53
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has joined #yocto03:54
*** dgriego_ <dgriego_!~dgriego@user/dgriego> has quit IRC (Read error: Connection reset by peer)06:02
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto06:03
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Remote host closed the connection)06:15
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has joined #yocto06:16
*** davidinux <davidinux!~davidinux@84.17.59.156> has joined #yocto06:20
*** davidinux <davidinux!~davidinux@84.17.59.156> has quit IRC (Ping timeout: 240 seconds)06:32
*** davidinux <davidinux!~davidinux@37.120.201.222> has joined #yocto06:35
*** lowfi <lowfi!~lowfi@user/lowfi> has quit IRC (Quit: Leaving)06:42
*** frieder <frieder!~frieder@i59F4B12E.versanet.de> has joined #yocto07:12
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has joined #yocto07:24
*** tlwoerner <tlwoerner!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has quit IRC (Ping timeout: 240 seconds)07:24
*** sstiller <sstiller!~sstiller@p200300f07f17f6000c402916f285f152.dip0.t-ipconnect.de> has joined #yocto07:25
*** jonmason <jonmason!sid36602@id-36602.lymington.irccloud.com> has quit IRC (*.net *.split)07:25
*** flynn378 <flynn378!sid63564@id-63564.ilkley.irccloud.com> has quit IRC (*.net *.split)07:25
*** rhadye <rhadye!sid217449@id-217449.tinside.irccloud.com> has quit IRC (*.net *.split)07:25
*** kergoth <kergoth!uid528530@id-528530.lymington.irccloud.com> has quit IRC (*.net *.split)07:25
*** madisox <madisox!sid453692@id-453692.ilkley.irccloud.com> has quit IRC (*.net *.split)07:25
*** moto-timo <moto-timo!sid495702@fedora/ttorling> has quit IRC (*.net *.split)07:25
*** _wmills <_wmills!~wmills@pool-71-163-150-39.washdc.fios.verizon.net> has quit IRC (*.net *.split)07:25
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (*.net *.split)07:25
*** marc1 <marc1!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has quit IRC (*.net *.split)07:25
*** lexano <lexano!~lexano@174.119.69.134> has quit IRC (*.net *.split)07:25
*** Lihis <Lihis!~Lihis@ns3006753.ip-151-80-42.eu> has quit IRC (*.net *.split)07:25
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has quit IRC (*.net *.split)07:25
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC (*.net *.split)07:25
*** rfried <rfried!~rfried@practical-trainings.com> has quit IRC (*.net *.split)07:25
*** bantu <bantu!~bantu@edna.bantux.com> has quit IRC (*.net *.split)07:25
*** geoffhp <geoffhp!~geoff@cpe-107-185-48-203.socal.res.rr.com> has quit IRC (*.net *.split)07:25
*** LetoThe2nd <LetoThe2nd!~Josef_Hol@ec2-52-29-15-71.eu-central-1.compute.amazonaws.com> has quit IRC (*.net *.split)07:25
*** xperia64 <xperia64!~xperia64@pool-71-115-223-249.syrcny.fios.verizon.net> has quit IRC (*.net *.split)07:25
*** Piraty <Piraty!~irc@user/piraty> has quit IRC (*.net *.split)07:25
*** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has quit IRC (*.net *.split)07:25
*** sgw <sgw!~swold_loc@user/sgw> has quit IRC (*.net *.split)07:25
*** kanavin <kanavin!~Alexander@82.119.31.27> has quit IRC (Read error: Connection reset by peer)07:26
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto07:26
*** _wmills <_wmills!~wmills@pool-71-163-150-39.washdc.fios.verizon.net> has joined #yocto07:28
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto07:28
*** marc1 <marc1!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has joined #yocto07:28
*** lexano <lexano!~lexano@174.119.69.134> has joined #yocto07:28
*** Lihis <Lihis!~Lihis@ns3006753.ip-151-80-42.eu> has joined #yocto07:28
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has joined #yocto07:28
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto07:28
*** rfried <rfried!~rfried@practical-trainings.com> has joined #yocto07:28
*** bantu <bantu!~bantu@edna.bantux.com> has joined #yocto07:28
*** geoffhp <geoffhp!~geoff@cpe-107-185-48-203.socal.res.rr.com> has joined #yocto07:28
*** LetoThe2nd <LetoThe2nd!~Josef_Hol@ec2-52-29-15-71.eu-central-1.compute.amazonaws.com> has joined #yocto07:28
*** xperia64 <xperia64!~xperia64@pool-71-115-223-249.syrcny.fios.verizon.net> has joined #yocto07:28
*** Piraty <Piraty!~irc@user/piraty> has joined #yocto07:28
*** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has joined #yocto07:28
*** sgw <sgw!~swold_loc@user/sgw> has joined #yocto07:28
*** jonmason <jonmason!sid36602@id-36602.lymington.irccloud.com> has joined #yocto07:28
*** flynn378 <flynn378!sid63564@id-63564.ilkley.irccloud.com> has joined #yocto07:28
*** rhadye <rhadye!sid217449@id-217449.tinside.irccloud.com> has joined #yocto07:28
*** kergoth <kergoth!uid528530@id-528530.lymington.irccloud.com> has joined #yocto07:28
*** madisox <madisox!sid453692@id-453692.ilkley.irccloud.com> has joined #yocto07:28
*** moto-timo <moto-timo!sid495702@fedora/ttorling> has joined #yocto07:28
*** tlwoerner <tlwoerner!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has joined #yocto07:29
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)07:32
*** mckoan|away is now known as mckoan07:34
mckoangood morning07:34
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 250 seconds)07:35
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto07:46
*** tlwoerner <tlwoerner!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has quit IRC (Ping timeout: 256 seconds)07:46
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:49
LetoThe2ndyo dudX and mckoans07:50
*** tlwoerner <tlwoerner!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has joined #yocto07:54
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto07:54
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto08:02
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)08:05
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)08:08
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto08:08
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto08:14
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto08:16
jclsnMorning08:19
qschulzhowdy08:23
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)08:30
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto08:32
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto08:40
*** smsm <smsm!~smsm@eth1-fw1-nbg6.eb.noris.de> has joined #yocto09:03
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Ping timeout: 256 seconds)09:14
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto09:15
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Quit: Leaving)09:15
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto09:16
*** olani <olani!~olani@66.159.215.7> has joined #yocto09:17
*** zyga <zyga!~zyga__@178.182.246.167.nat.umts.dynamic.t-mobile.pl> has joined #yocto09:19
zygagood morning09:20
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Ping timeout: 256 seconds)09:38
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto09:38
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Ping timeout: 256 seconds)09:43
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto09:44
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:6d20:b3c:b4df:8f25> has quit IRC (Remote host closed the connection)10:00
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:cadb:2c7f:ef83:5aa9> has joined #yocto10:04
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto10:04
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Ping timeout: 256 seconds)10:16
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto10:19
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Ping timeout: 256 seconds)10:29
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)10:36
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto10:41
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto10:44
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has joined #yocto10:47
*** olani <olani!~olani@66.159.215.7> has quit IRC (Ping timeout: 256 seconds)10:52
*** pbergin <pbergin!~pbergin@h-79-136-99-68.na.cust.bahnhof.se> has joined #yocto10:56
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 276 seconds)11:03
*** zyga-office <zyga-office!~zyga__@31.0.173.147> has joined #yocto11:26
*** zyga <zyga!~zyga__@178.182.246.167.nat.umts.dynamic.t-mobile.pl> has quit IRC (Ping timeout: 240 seconds)11:29
*** mckoan is now known as mckoan|away11:43
LetoThe2ndsuppose i have a bsp that provides machineA. now I want to manipulate a couple of things for that machine from my layer, and build for it. am I right in the understanding that MACHINEOVERRIDES does the trick here?11:47
LetoThe2nde.g. I create a machineA_special, which contains MACHINEOVERRIDES = "machineA:"11:48
RPLetoThe2nd: yes11:52
RPLetoThe2nd: although I'd not put _ in a machine name11:52
LetoThe2ndRP: heh you're right. underscores are one of my bad habits.11:52
LetoThe2ndRP: so then a build for MACHINE = "specialMachineA" gives my machineA + my special sauce - correct?11:53
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Ping timeout: 256 seconds)11:57
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)11:59
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto11:59
RPLetoThe2nd: yes12:04
LetoThe2ndRP: thx12:05
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto12:06
*** ziga_ <ziga_!~ziga@89-212-219-192.dynamic.t-2.net> has joined #yocto12:14
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)12:15
ziga_I have a image that was created with Yocto. I have the password and I can login. How can I check which Yocto project version was used to create the image? I tried using "uname -a" which outputs: "Linux 4.8.3-yocto-standard #1 PREEMPT Tue Feb 19 19:30:06 UTC 2019...".12:18
LetoThe2ndziga_: /etc/os_release12:18
ziga_This file was removed from the image. It does not exist. Any other method?12:20
LetoThe2ndziga_: nothing concise that i know of. yocto-standard sounds like at least the kernel is a generic one, so you can go digging which release supported 4.812:23
RPziga_: you can compare the versions of things in the image with versions of things in different yocto releases12:24
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto12:24
qschulzLetoThe2nd: don't forget that it's =. and BEFORE any include/require in the configruation file12:28
LetoThe2ndqschulz: thanks, good hint!12:28
ziga_I tried the kernel - I am using Beaglebone Black so I assume that person who created the image used meta-ti layer and kernel linux-ti-staging. But when I search through releases of linux-ti-staging I can't find exact match - it looks like "morty" comes the closest (https://github.com/YoeDistro/meta-ti/tree/morty/recipes-kernel/linux) but that is not it. I need 4.8.3 :/12:29
LetoThe2ndziga_: then i'd say, get in touch with the one who did the build.12:31
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto12:33
ziga_He vanished without a trace and left company (our customer) in pain. :D12:33
*** davidinux <davidinux!~davidinux@37.120.201.222> has quit IRC (Ping timeout: 240 seconds)12:34
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Ping timeout: 240 seconds)12:35
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto12:35
LetoThe2ndziga_: then you might need to hire some assistance.12:35
qschulzziga_: https://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/12:35
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto12:36
ziga_Aha! This one might be the right one! https://github.com/yoctoproject/poky/tree/morty/meta/recipes-kernel/linux They used Your kernel and not from meta-ti it seems.12:39
*** davidinux <davidinux!~davidinux@net-188-153-130-222.cust.vodafonedsl.it> has joined #yocto12:40
derRichardis there a good way to debug sstate-cache cache misses? i'd like to understand why a fully populated sstate-cache (provided via SSTATE_MIRRORS) matches only 40%. some of my recipes/layers must be wonky.12:54
qschulzI think there's seomthing related to hashserv?12:59
qschulzI remember only hitting 55% sstate-cache reuse on dunfell a few months back12:59
*** olani <olani!~olani@134.238.48.37> has joined #yocto13:01
* derRichard finds oe-check-sstate13:01
derRichardqschulz: so, even with a clean yocto release i won't have a good cache utilization? :-(13:05
derRichardi'm on hardknott bte13:05
derRichardbtw13:05
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:cadb:2c7f:ef83:5aa9> has quit IRC (Remote host closed the connection)13:06
qschulzyeah, I had 55% on vanilla poky13:07
derRichardoh dear.13:07
qschulzthere's probably something to do know with the hashserv. I think there's one that's publicly accessible?13:07
qschulzotherwise, you need to host your own13:07
qschulzIIRC, haven't looked at that13:07
derRichardwtf is hashserv? :)13:08
qschulzthe counterpart of sstate-cache13:08
qschulzsstate-cache stores what is the hash of a task and its output so that if a task has the same hash, the sstate-cache output can be reused13:09
derRichardas long it is some bitbake internal i'm good. but my build need to work offline.13:09
qschulzhowever, this is quite inefficient if you change something small in a task, e.g. a space, which does not change the outcome of a task13:10
derRichardin my case it rebuild even core stuff like gcc and glibc ;-\13:10
derRichardif it rebuilds customer applications all time, i'm still fine with it13:11
qschulzwhich means that bitbake will now detect that both tasks have the same output, therefore the rest of the task dependency tree can be taken from sstate-cache instead of being rebuilt because the new task is slightly changed13:11
RPderRichard: are you sharing an sstate cache without sharing a hash equivalence server ?13:11
derRichardRP: i fear so. so, what is the right way to share sstate cache across multiple users/machines?13:11
RPderRichard: what you're doing is correct however it misses a key detail. We enabled hash equivalence by default in some of our recent releases and this "defeats" sstate sharing :/13:12
RPderRichard: so either disable hash equivalence or share the hash equivalence data with sstate13:12
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:a5f2:a4cd:9672:b146> has joined #yocto13:13
derRichardhm, i need to read on "hash equivalence" first. i have little idea what this is13:14
RPderRichard: it tracks what the output of sstate tasks looks like and if it was the same as a previous build, it marks them as equivalent and skips the following other things that might have rebuilt13:14
qschulzI think michaelo wrote some documentation on this recently?13:15
RPqschulz: I will let you point to that :)13:15
derRichardi thought this is all what sstate cache does? why do i need to disable it to utilize the cache?13:16
RPderRichard: sstate just dumbly caches the output of tasks. It doesn't short circuit later tasks if the output hasn't changed, only if the input is the same13:16
RPderRichard: you'd better look at the manual :/13:17
* derRichard reads :)13:17
derRichardactually i was just looks for a way how to use sstate-cache better. now i ended up in interals :)13:18
RPderRichard: just disable hash equivlance then13:18
* RP shurgs. You asked why13:18
derRichardRP: :-)13:18
derRichardah, since zeus BB_SIGNATURE_HANDLER is set to OEBasicHash13:19
derRichardand when i set it back to OEBasic things should work13:19
RPderRichard: no :/13:19
derRichardnot?13:19
RPI said disable hash equivalence, not change the signature handler13:19
derRichardgrml13:19
RPderRichard: https://git.yoctoproject.org/poky/commit/?id=1fb4aa42f9c3b9738d78d198ad695fe4fcb6dc2f13:20
qschulzhttps://docs.yoctoproject.org/overview-manual/concepts.html#hash-equivalence13:21
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has quit IRC (Ping timeout: 256 seconds)13:22
derRichardqschulz: ah, this is what i was looking for. i was poking in the reference manual13:22
LetoThe2ndconcerning documentation, where are the requirements for compatible layers noted down?13:27
RPLetoThe2nd: the yocto-check-layer tests effectively encompass them?13:35
LetoThe2ndRP: yeah but if I happen to have a presentation where I kinda want to reference it?13:36
RPLetoThe2nd: https://www.yoctoproject.org/ecosystem/branding/compatible-registration/ ?13:38
LetoThe2ndRP: ah from there I found https://docs.yoctoproject.org/bsp-guide/bsp.html#requirements-and-recommendations-for-released-bsps13:40
*** vladest1 <vladest1!~Thunderbi@2001:1715:9d9c:c530:d7e1:7d2b:12e9:e8a9> has joined #yocto13:42
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:a5f2:a4cd:9672:b146> has quit IRC (Ping timeout: 256 seconds)13:43
*** vladest1 is now known as vladest13:43
RPLetoThe2nd: I'm not sure that is a definitive list now but those things are certainly good13:44
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:d7e1:7d2b:12e9:e8a9> has quit IRC (Remote host closed the connection)13:46
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:e716:a550:5669:7548> has joined #yocto13:48
LetoThe2ndRP: yeah. I'm just currently preparing something which will actually highlight the benefits of having proper layers, and possibly HW vendors that pörovide such.13:48
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto13:49
derRichardRP: okay. i don't get it. from the docs i understand that BB_SIGNATURE_HANDLER controls the hash equivalence feature. but a few lines before you told me BB_SIGNATURE_HANDLER is something different13:50
RPderRichard: it is controlled by BB_HASHSERVE. Ensure that isn't set13:52
RPderRichard: I think I'm misremembering how this works, sorry :(13:53
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 240 seconds)13:53
derRichardRP: part of my confusion is, when i unset BB_HASHSERVE, i get "ERROR: OEEquivHash requires BB_HASHSERVE to be set". so i need to touch BB_SIGNATURE_HANDLER too13:54
RPderRichard: I thought you could just remove BB_HASHSERVE and disable it but looking at the code I guess not. Sorry, I'm not at my best today :(13:54
derRichardno problem at all. :-)13:55
kayterina[m]where can I see the series of commands that run with bitbake <target>? For example that a task runs before do_compile or if I can see dependencies between them13:57
qschulzkayterina[m]: bitbake -g <target> and then look at one of the dot files (don't use dot)13:58
derRichardjust to very sure: when i build a target, save sstate-cache somewhere else on my local disk and later use the very same layers/recipes/local.conf plus SSTATE_MIRRORS set to the previously saved sstate-cache, i should get close to 100% cache utilization, right? (with hashserve being disabled)13:58
RPderRichard: you mentioned OEBasic and I suspect you want the OE core default, OEBasicHash13:58
kayterina[m]aah...that infinite parsing of recipes13:58
LetoThe2ndkayterina[m]: bitbake -g target, then you can look at the task-depends.dot13:58
LetoThe2ndqschulz: hi513:59
RPderRichard: and yes, you should13:59
derRichardRP: hmm, this is not what i see. maybe there is something else wonky13:59
derRichardand yes, OEBasicHash of course, not OEBasic :)13:59
* derRichard diggs deeper14:00
RPthere is a huge difference between the two14:00
derRichardyes, i figured :)14:00
kayterina[m]then I can ask directly does 'bitbake <target>' executes 'sysroot_populate' and if so, it should equal to devtool build14:00
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #yocto14:13
*** ykrons <ykrons!~guillaume@62.192.23.101> has joined #yocto14:25
RPkayterina[m]: bitbake <target> executes the do_build task of target14:32
RPkayterina[m]: anything that is depended upon by the do_build task would run14:32
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto14:34
agherzanThere seems to be an issue in the GMT time for the weekly triage meeting. It states 14.30GMT and it should be 15.30GMT14:43
agherzanI'm not sure whom to ping for the change14:47
rburtonstephen jolley is the owner of the invite14:48
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Ping timeout: 256 seconds)14:53
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto14:55
*** ar__ <ar__!~akiCA@user/akica> has joined #yocto14:59
RPsakoman: can you please trim that crazy size email next time you reply, my email client hates it!14:59
RPagherzan: you definitely need stephen for that15:00
sakomanRP: Sorry!  Will do15:00
RPsakoman: a cpu core goes awol for a minute if I scroll past any of that thread :)15:02
sakomanI fear I replied a second time before seeing your message15:02
agherzan@RP thanks15:02
*** vmeson <vmeson!~rmacleod@198-48-226-187.cpe.pppoe.ca> has joined #yocto15:03
*** pbergin <pbergin!~pbergin@h-79-136-99-68.na.cust.bahnhof.se> has quit IRC (Quit: Leaving)15:08
*** codavi <codavi!~akiCA@user/akica> has joined #yocto15:22
*** davidinux <davidinux!~davidinux@net-188-153-130-222.cust.vodafonedsl.it> has quit IRC (Ping timeout: 240 seconds)15:23
*** davidinux <davidinux!~davidinux@37.120.201.221> has joined #yocto15:24
*** ar__ <ar__!~akiCA@user/akica> has quit IRC (Ping timeout: 256 seconds)15:25
*** jatedev <jatedev!~jatedev@63.148.217.19> has joined #yocto15:29
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)15:29
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto15:33
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Quit: Leaving)15:36
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto15:41
*** Tokamak <Tokamak!~Tokamak@172.58.191.35> has joined #yocto15:44
*** olani <olani!~olani@134.238.48.37> has quit IRC (Remote host closed the connection)15:46
rburtonkhem: do you have a new glibc recipe in flight already?16:11
*** smsm <smsm!~smsm@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Ping timeout: 256 seconds)16:13
*** sstiller <sstiller!~sstiller@p200300f07f17f6000c402916f285f152.dip0.t-ipconnect.de> has quit IRC (Remote host closed the connection)16:44
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Ping timeout: 256 seconds)16:53
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto16:53
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Ping timeout: 256 seconds)16:58
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto16:58
*** frieder <frieder!~frieder@i59F4B12E.versanet.de> has quit IRC (Remote host closed the connection)16:58
rburtonPSA: the unshare trick done by latest bitbake doesn't work inside non-privileged docker containers17:13
JPEWrburton: Not really that surprising I suppose17:16
rburtonit blocks unshare entirely, there's tickets for allowing user namespaces to work but they're untouched for months17:17
rburtonhttps://github.com/moby/moby/issues/42441 fwiw17:18
shivamurthyrburton: as per your suggestion, I have downloaded poky, and started build with qemux86-6417:21
RPrburton: he did a while ago when we last tested it17:21
shivamurthywithout any changes17:21
shivamurthyhttps://www.irccloud.com/pastebin/tH5KiZ4k/17:22
shivamurthyhttps://www.irccloud.com/pastebin/ZmYKvbrn/17:23
shivamurthyrburton: ^^^17:24
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Remote host closed the connection)17:24
shivamurthythis is dunfell release17:24
*** zpfvo <zpfvo!~fvo@88.130.220.72> has joined #yocto17:32
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)17:32
*** zpfvo <zpfvo!~fvo@88.130.220.72> has quit IRC (Client Quit)17:36
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has joined #yocto17:42
ex-bugsbunnyhi y'all :-)17:52
ex-bugsbunnyI have a question about BBFILES_DYNAMIC17:52
ex-bugsbunnyin the past I fiddled with dynamically using BBMASK to avoid .bbappend files in case the base recipe is missing until I read about that fine variable17:53
agherzanRP: Any hints on how to reproduce #14484? I didn't manage on a simple build.17:53
ex-bugsbunnyhowever, I mis-used it first, because I took the "Use the BBFILES_DYNAMIC variable to avoid" in the documentation more serious than the "Activates content" in the very beginning.17:54
ex-bugsbunnymy expectation was: yeah, great, just add the paths in question to that variable and leave BBFILES variables untouched, bitbake will sort out the dynamic files from the BBFILES, but obviously I was wrong17:56
ex-bugsbunnyso my question: why was it implemented that way?17:56
ex-bugsbunnyI mean, it is great to have that dynamic way of handling recipes and append files, but it forces you to restructure the layers once you find something becoming dynamic (because the layer gets re-used in a different context)17:58
RPagherzan: it is a rare race so it probably won't reproduce easily. If you wanted to you'd need to creating something that would brute force it, running many package creations in loops18:03
RPagherzan: I did worry it was some kind of race in psuedo's file deletion paths too :/18:03
agherzanRP: looks like it. Ok. I'll keep messing up with it18:07
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 256 seconds)18:18
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Ping timeout: 256 seconds)18:22
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto18:26
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)18:34
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)18:40
*** Tokamak <Tokamak!~Tokamak@172.58.191.35> has quit IRC (Ping timeout: 256 seconds)19:00
*** florian_kc <florian_kc!~florian@dynamic-002-243-019-124.2.243.pool.telefonica.de> has joined #yocto19:02
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has joined #yocto19:03
*** Tokamak <Tokamak!~Tokamak@172.58.188.214> has joined #yocto19:05
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 256 seconds)19:07
*** jatedev <jatedev!~jatedev@63.148.217.19> has quit IRC (Quit: Client closed)19:13
shivamurthyHi All, I am getting a problem while building dunfell release on Ubuntu 20.04.19:33
shivamurthyhttps://www.irccloud.com/pastebin/3WRitbNG/19:33
*** zyga-office <zyga-office!~zyga__@31.0.173.147> has quit IRC (Quit: Leaving)19:34
shivamurthyMACHINE : qemux86-6419:34
shivamurthyhttps://www.irccloud.com/pastebin/NL9vnWJB/19:44
rfs613shivamurthy: try "sudo apt install help2man"19:54
shivamurthyrfs613: i installed it:19:55
shivamurthyhttps://www.irccloud.com/pastebin/0LoDGd7P/19:55
rfs613shivamurthy: hmm, it seems to work in the autobuilder: https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/464419:59
shivamurthyrfs613: the problem started after I upgraded (sudo apt update and sudo apt upgrade)20:01
rfs613hmm so maybe a recent ubuntu update, okay20:02
rfs613I guess others will run into this also ;-)20:02
shivamurthyrfs613: around 60 packages upgraded, I am not sure the way to find that list now to downgrade :(20:02
rfs613shivamurthy: agreed. It might be something simple, like the autoconf package needs to list help2man as a new dependency. I'm just guessing here, there are others who are a lot more knowledgeable on the channel.20:07
vdis bmaptool faster than dd even without a .bmap file, or is it the same without it?20:09
shivamurthyrfs613: that not worked for me20:10
*** jatedev <jatedev!~jatedev@63.148.217.19> has joined #yocto20:13
rfs613shivamurthy: i'm looking at the list of updates.. the only one that jumps out at me is command-not-found got updated, it seems like a long shot, but maybe that broke something? There don't seem to be any updates to autoconf, help2man, or even very many -dev packages.20:20
khemvd: without mapfile bmaptool is no much different20:23
vdkhem: thanks20:24
khemrfs613: does help2man-native appears in the DEPENDS of autoconf recipe20:24
rfs613khem: DEPENDS="m4-native gnu-config-native texinfo-dummy-native"  so it looks like no...20:25
khemok then add it20:27
rfs613shivamurthy: ^^ can you give that a try?20:27
shivamurthyrfs613: DEPENDS="m4-native gnu-config-native texinfo-dummy-native help2man-native" , like this?20:30
rfs613shivamurthy: yup20:31
khemyeah20:31
shivamurthyit looks to have many dependcies20:32
shivamurthyhttps://www.irccloud.com/pastebin/cUsEF8Io/20:32
rfs613hmm, circular loop of dependencies maybe?20:33
shivamurthyyes20:33
JPEWrburton: Hmm, I wonder if podman works; I had assumed that's what you were using when you said "unprivledged" :)20:34
rfs613ah yes, help2man-native has DEPENDS="  autoconf-native automake-native"20:34
rfs613khem: how to break the loop?20:34
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto20:34
khemoh20:36
khemI think autoconf should not be using help2man20:36
khemso I wonder why its coming20:36
khemas dependency in your build20:36
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)20:36
khemcan you delete your tmp/ and rebuild20:36
rfs613(and undo the change to DEPENDS of course)20:38
shivamurthyok20:39
shivamurthythis time I cleaned,  tmp, downloads, sstate-cache, and cache20:41
shivamurthyalso removed help2man from autoconf.inc20:41
shivamurthybut, instead of bitbake core-image-minimal, I tried bitbake autoconf-native20:42
rfs613ok, it will still likely build a bunch of dependencies first before getting to autconf-native20:42
shivamurthysame problem I am getting, ^^^ rfs613 and khem20:42
shivamurthyrfs613 ^^^20:43
rfs613oh that's fast ;-)20:43
*** jatedev <jatedev!~jatedev@63.148.217.19> has quit IRC (Quit: Client closed)20:43
shivamurthyI removed DEPENDS once I got those errors20:43
shivamurthy:)20:43
rfs613i'm trying to get my qemux86_64 build working, so I can test out the same things20:44
*** jatedev <jatedev!~jatedev@63.148.217.19> has joined #yocto20:47
rfs613ok, I am seeing help2man: command not found.... but this is ignored and the build continues anyway20:48
rfs613shivamurthy: so I'd suggest we look at your original error log more carefully, maybe there's something besides the help2man going wrong? (eg. earlier than what you posted in 3WRitbNG)20:50
jatedevIs github changing default branch names from master to main? People are starting to do this and it's affecting my builds20:51
rfs613jatedev: for new repos yes... and some projects are changing their existing master branch20:51
rfs613https://github.com/github/renaming20:52
shivamurthyrfs613: for me build continued but failed later like this:20:52
shivamurthyERROR: Task (virtual:native:/home/ubuntu/workspace/yocto-build/poky/meta/recipes-devtools/autoconf/autoconf_2.69.bb:do_compile) failed with exit code '1'20:52
rfs613shivamurthy: can you share more of the log.do_compile file? I suspect there is another error earlier on.20:57
rfs613(it should be in tmp/work/x86_64-linux/autoconf-native/2.69-r11/temp/20:59
rfs613or just search that file for the first error / ERROR  or "exit 1"21:01
shivamurthyrfs613: i got the file, but how to upload it here size is big21:05
rfs613shivamurthy: use a site like pastebin, dpaste, github gist, etc.21:06
shivamurthyhttps://pastebin.com/p6qTYbz921:08
ad__hi, using a layer with new way : instead of _  used from the rest of my layers. Is there a way to support this ?21:11
rfs613shivamurthy: ok, yours looks quite similar to mine, but I don't get the "Error 127" right after "help2man: command not found"21:13
rfs613shivamurthy: here's mine for comparison: https://pastebin.com/G4XbaVxn21:17
*** codavi is now known as akiCA21:17
akiCAHello folks, anyone familiar with meta-java online? It fails to parse with error: meta-java/recipes-core/icedtea/icedtea7-native_2.1.3.bb: QA Issue: recipe uses DEPENDS_${PN}, should use DEPENDS [pkgvarcheck]21:19
shivamurthyrfs613: ok, does system upgrade cause this problem?21:19
akiCABut I don't see DEPENDS_${PN} being used anywhere in recipe or included files21:19
rfs613shivamurthy: I'm hesitant to try that right now, as I don't want to break my builds right now.21:21
shivamurthyrfs613: I understand :)21:21
rfs613shivamurthy: i'd need to setup the same thing inside a vm or docker, so I can upgrade without affecting my real build.21:22
rfs613but i have to go pickup kids from school in 10 mins, so no time for that now21:23
shivamurthyrfs613: i have old lxc container snapshot, let me try21:23
khemshivamurthy: I think you need to find why help2man is being needed for autoconf-native21:23
khemthats the root issue, it should not be needed21:23
rfs613khem: if you look at both shivamurthy and my logs (on pastebin) they both clearly try to call help2man... as part of "Makeing all in man" from autoconf make21:24
rfs613maybe there is a way to tell autoconf not to recurse into the 'man' directory... or we could patch that out.21:24
shivamurthykhem: I saw autoconf-2.71 recipe from new yocto release, they added new patch to remove man, just now I saw this: https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/autoconf/autoconf/no-man.patch21:26
khemright, apply that to dunfell too21:26
rfs613that looks promising!21:26
khemand perhaps send that upstream as well, if it works21:26
shivamurthyokay, let me try21:27
*** florian_kc <florian_kc!~florian@dynamic-002-243-019-124.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 256 seconds)21:28
*** RP <RP!~richard@2001:8b0:aba:5f3c:96de:80ff:fe6d:2d2b> has quit IRC (Ping timeout: 252 seconds)21:30
rfs613shivamurthy: good luck, i'll try to check back later tonight...21:32
*** amitk <amitk!~amit@103.208.71.118> has quit IRC (Ping timeout: 240 seconds)21:44
shivamurthyrf613: khem: thanks for the help, autoconf is resolved with no-man patch, but I had to change it for 2.69,21:58
shivamurthyrfs613: thanks for the help21:58
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Quit: Leaving)22:06
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC (Quit: Leaving.)22:12
*** RP <RP!~richard@2001:8b0:aba:5f3c:96de:80ff:fe6d:2d2b> has joined #yocto22:18
RPsmurray: I guess you knew https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/749 was coming?22:20
smurrayRP: you took the weston 10.0 upgrade into master-next, I guess?22:21
RPsmurray: yes22:22
smurrayRP: I can take a look, should be relatively straightforward (famous last words)22:22
RPsmurray: I'm sure that has cursed it ;-)22:23
smurrayRP: iirc, it's mostly dropping backported patches22:23
RPsmurray: we're at the "see what breaks" stage of testing so if there is a huge issue, now is the time to flag it!22:23
smurrayRP: okay, I'll rig up a test tree here.  I suspect our issues will be more with agl-compositor than with the weston bbappend22:24
RPsmurray: I figured you may be more sensitive to this one than many22:25
smurrayRP: heh, it's several of the vendor BSPs that are likely borked for a while, but I've only been testing AGL's "next" branch with qemu & rpi4 for the most part22:26
smurrayRP: the other fun things for BSPs will be gstreamer & mesa 22 if they make it into kirkstone22:27
RPgstreamer has patches so that is possible. I've not seen mesa yet22:27
kanavinmesa updates are usually straightforward, so I think it's likely to make it too22:31
kanavinkhem, I have llvm 13.0.1 upgrade patch lined up22:32
*** lucaceresoli <lucaceresoli!~lucaceres@77.244.183.192> has quit IRC (Ping timeout: 256 seconds)22:38
*** florian_kc <florian_kc!~florian@dynamic-002-243-019-124.2.243.pool.telefonica.de> has joined #yocto22:43
*** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has quit IRC (Quit: ZNC 1.8.0 - https://znc.in)23:04
*** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has joined #yocto23:05
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)23:21
derRichardhmm. on a vanilla hardknott i get 99% sstate match. with customer layer just 40.23:25
derRichardtime to figure what they did^^23:25
*** akiCA <akiCA!~akiCA@user/akica> has quit IRC (Ping timeout: 256 seconds)23:27
*** florian_kc <florian_kc!~florian@dynamic-002-243-019-124.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)23:35
*** dev1990 <dev1990!~dev@dynamic-78-8-66-141.ssp.dialog.net.pl> has quit IRC (Quit: Konversation terminated!)23:46
smurrayRP: I've got the fixes in hand for weston 10.0, just give me a ping when you're about to push it to master23:57

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