Monday, 2021-11-15

« Sunday, 2021-11-14 Index Tuesday, 2021-11-16 »
*** florian__ <florian__!~florian@dynamic-078-049-162-074.78.49.pool.telefonica.de> has joined #yocto00:16
*** florian__ <florian__!~florian@dynamic-078-049-162-074.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 260 seconds)00:32
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC (Quit: Leaving.)00:36
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto01:52
*** hpsy <hpsy!~hpsy@user/hpsy> has quit IRC (Ping timeout: 256 seconds)02:04
*** Tokamak <Tokamak!~Tokamak@172.58.191.72> has quit IRC (Ping timeout: 264 seconds)02:18
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto02:19
*** RobertBerger <RobertBerger!~rber|res@ppp-2-86-140-242.home.otenet.gr> has joined #yocto02:32
*** rber|res <rber|res!~rber|res@ppp-2-86-140-242.home.otenet.gr> has quit IRC (Ping timeout: 268 seconds)02:34
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)02:47
*** pgowda_ <pgowda_!uid516182@ilkley.irccloud.com> has joined #yocto04:34
pgowda_Am getting the following error during bitbake meta-toolchain using latest yocto sources04:37
pgowda_Checksum mismatch for local file build/downloads/libxslt-1.1.34.tar.gz04:37
pgowda_Cleaning and trying again.04:37
pgowda_WARNING: Renaming build/downloads/libxslt-1.1.34.tar.gz to build/downloads/libxslt-1.1.34.tar.gz_bad-checksum_0f48107788b888364801b2051a42fae2d007ce09266c6b0e6ef378eb5aeef5eb04:37
pgowda_Plz let me know if anyone else is facing the same issue?04:37
pgowda_Any workaround to fix the issue?04:38
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 260 seconds)04:40
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto04:40
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 268 seconds)05:29
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto06:51
*** gourve_l <gourve_l!~laurent@static-176-175-104-214.ftth.abo.bbox.fr> has quit IRC (*.net *.split)06:58
*** iokill <iokill!~dave@static.16.105.130.94.clients.your-server.de> has quit IRC (*.net *.split)06:58
*** fray <fray!~fray@70.99.78.136> has quit IRC (*.net *.split)06:58
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has quit IRC (*.net *.split)06:58
*** rfried <rfried!~rfried@practical-trainings.com> has quit IRC (*.net *.split)06:58
*** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has quit IRC (*.net *.split)06:58
*** fray <fray!~fray@70.99.78.136> has joined #yocto06:58
*** iokill <iokill!~dave@static.16.105.130.94.clients.your-server.de> has joined #yocto06:58
*** gourve_l <gourve_l!~laurent@40.72.95.92.rev.sfr.net> has joined #yocto06:59
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has joined #yocto06:59
*** ldericher <ldericher!~LDer@pantalaimon.yavook.de> has joined #yocto06:59
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:03
*** marex <marex!~marex@195.140.252.251> has quit IRC (*.net *.split)07:04
*** zeddii <zeddii!~zeddii@cpe04d4c4975b80-cmf4c11490699b.cpe.net.cable.rogers.com> has quit IRC (*.net *.split)07:04
*** beneth <beneth!~beneth@ip208.ip-54-36-198.eu> has quit IRC (*.net *.split)07:04
*** kmaincent <kmaincent!~kmaincent@2001:41d0:305:1000::2a58> has quit IRC (*.net *.split)07:04
*** marex <marex!~marex@195.140.252.251> has joined #yocto07:04
*** kmaincent <kmaincent!~kmaincent@2001:41d0:305:1000::2a58> has joined #yocto07:04
*** zeddii <zeddii!~zeddii@cpe04d4c4975b80-cmf4c11490699b.cpe.net.cable.rogers.com> has joined #yocto07:07
*** adrian__ <adrian__!~F_Adrian@62.32.0.69> has joined #yocto07:09
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto07:09
*** beneth <beneth!~beneth@ip208.ip-54-36-198.eu> has joined #yocto07:24
*** tre <tre!~tre@ip5b4343c3.dynamic.kabel-deutschland.de> has joined #yocto07:30
*** sstiller <sstiller!~sstiller@p200300f07f11d500514249f49e98ea75.dip0.t-ipconnect.de> has joined #yocto07:41
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto07:41
*** fleg <fleg!64bf4386e9@user/fleg> has joined #yocto07:59
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto08:00
*** gsalazar_ <gsalazar_!~gsalazar@161.230.168.194> has joined #yocto08:02
*** gsalazar__ <gsalazar__!~gsalazar@194.38.148.130> has joined #yocto08:07
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto08:09
*** gsalazar_ <gsalazar_!~gsalazar@161.230.168.194> has quit IRC (Ping timeout: 265 seconds)08:10
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC (Quit: reboot)08:23
*** lucaceresoli <lucaceresoli!~ceresoli@host-79-2-93-196.business.telecomitalia.it> has joined #yocto08:31
qschulztlwoerner: I think there's a misunderstanding, it is both in 5.15 upstream tree and >=5.14.12 upstream stable releases. I was just wondering how to handle a Yocto release which has a 5.14 kernel < 5.14.12 and one >= 5.14.12, one being the original release and the other in dot releases (yet to be released)08:53
qschulzjaskij[m]: no worries, I'm interested to see where you go with those dot files and if it can finally be useful when rendered :) (and not take days to be rendered :p)08:54
qschulzjaskij[m]: nice tool!08:56
qschulzpgowda_: I assume the tarball you're receiving from upstream has a bad checksum but I'd have guessed this would result in an error if no mirrors with valid checksum were available09:00
RPpgowda_: FWIW I tried re-downloading that here and it seems to work ok09:11
*** nad <nad!~nad@pr-svc-em1-016.emea.corpinter.net> has joined #yocto09:11
pgowda_It had issues during download,,, One of my colleague working in the same machine encountered the same issue09:12
RPqschulz: the only way to do that is going to be conditional patch application09:12
pgowda_The following patch fixed the issue09:12
pgowda_diff --git a/meta/recipes-support/libxslt/libxslt_1.1.34.bb b/meta/recipes-support/libxslt/libxslt_1.1.34.bb09:12
pgowda_index c888f3d7e1..5181be4c0b 10064409:12
pgowda_--- a/meta/recipes-support/libxslt/libxslt_1.1.34.bb09:12
pgowda_+++ b/meta/recipes-support/libxslt/libxslt_1.1.34.bb09:12
pgowda_@@ -13,7 +13,7 @@ LIC_FILES_CHKSUM = "file://Copyright;md5=0cd9a07afbeb24026c9b03aecfeba458"09:12
pgowda_ SECTION = "libs"09:12
pgowda_ DEPENDS = "libxml2"09:12
pgowda_-SRC_URI = "http://xmlsoft.org/sources/libxslt-${PV}.tar.gz \09:12
pgowda_+SRC_URI = "ftp://xmlsoft.org/libxslt/libxslt-${PV}.tar.gz \09:12
pgowda_           "09:12
pgowda_ SRC_URI[md5sum] = "db8765c8d076f1b6caafd9f2542a304a"09:12
pgowda_Just replaced the http with ftp... Maybe issue with our network blocking hhtp09:13
*** RobertBerger <RobertBerger!~rber|res@ppp-2-86-140-242.home.otenet.gr> has quit IRC (Remote host closed the connection)09:13
RPpgowda_: the original url seems to work fine here FWIW09:13
qschulzfrosteyes: very nice commit log :) thanks for contributing :)09:15
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto09:15
pgowda_OK,,, Thanks for confirmation,,, Maybe the issue in our side09:15
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 268 seconds)09:16
*** camus1 is now known as camus09:16
*** RobertBerger <RobertBerger!~rber|res@ppp-2-86-140-242.home.otenet.gr> has joined #yocto09:16
qschulzjaskij[m]: wondering if we could also add information on common inter-recipe dependencies (e.g. DEPENDS is do_configure[depends] += "recipeB:do_populate_sysroot" (or is it do_prepare_recipe_sysroot? I always mix both))09:17
qschulzso something like a text above the "dependency arrow" between what you call clusters, to explicit if it's DEPENDS or RDEPENDS/RRECOMMENDS09:19
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 265 seconds)09:19
qschulzif you have access to that kind of information, maybe even point the file/line where it is defined but just saying "this dependency is VERY commonly the result of a DEPENDS" would be very helpful for benon-veterans :)09:20
qschulz-be09:20
qschulzRP: yes that's what I gathered from your answer last Friday (thx BTW :) ), was just answering to tlwoerner :)09:22
*** RobertBerger <RobertBerger!~rber|res@ppp-2-86-140-242.home.otenet.gr> has quit IRC (Read error: Connection reset by peer)09:23
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto09:25
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:28
*** Granjow <Granjow!~simon@46.140.188.244> has joined #yocto09:31
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 260 seconds)09:32
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto09:32
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto09:35
JosefHolzmayrTheyo dudX09:37
qschulzo/09:38
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto09:44
GranjowHi there =)09:58
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto10:00
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Ping timeout: 265 seconds)10:13
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto10:15
*** Granjow <Granjow!~simon@46.140.188.244> has quit IRC (Ping timeout: 265 seconds)10:38
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 250 seconds)11:22
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto11:23
*** zyga-mbp <zyga-mbp!~zyga@31.0.173.147> has joined #yocto11:27
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 265 seconds)11:30
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto11:31
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)11:34
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto11:35
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto11:36
*** Granjow <Granjow!~simon@46.140.188.244> has joined #yocto11:43
jaskij[m]qschulz: edges ("arrows") between clusters are possible. That said, the only data I have are task dependencies - so either I'll need help identifying those common dependencies and creating the data from there, or need extra info dump from BB.11:57
jaskij[m]I already have separate code paths for the cluster and non-cluster version anyway12:00
jaskij[m]here's GV docs on this: https://graphviz.org/faq/#FaqClusterEdge12:04
*** nad <nad!~nad@pr-svc-em1-016.emea.corpinter.net> has quit IRC (Quit: Client closed)12:04
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 265 seconds)12:07
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto12:08
jaskij[m]qschulz: if you don't mind, I've made an issue on GitLab: https://gitlab.com/jaskij/oe-dependency-tool/-/issues/512:09
jaskij[m]one neat thing for you old-timers, GL has decent support for e-mail based issue discussion: https://docs.gitlab.com/ee/administration/reply_by_email.html12:09
*** adrian_ <adrian_!~F_Adrian@165.225.26.253> has joined #yocto12:12
jaskij[m]changing topics: looking through kernel-devicetree.bbclass, `KERNEL_DEVICETREE` supports listing multiple device trees, but it is not mentioned in the docs?12:13
*** adrian__ <adrian__!~F_Adrian@62.32.0.69> has quit IRC (Ping timeout: 256 seconds)12:15
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 250 seconds)12:16
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto12:16
*** kroon_ <kroon_!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto12:18
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Ping timeout: 268 seconds)12:20
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 265 seconds)12:22
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto12:23
qschulzjaskij[m]: send a patch :)12:23
jaskij[m]Once I understand the logic in the class :P12:24
qschulzjaskij[m]: to me at least, it'd be enough to re-use the existing edges and add text to it?12:24
qschulze.g. the "with clusters" image, you can see there's one arrow from a task of one cluster to another12:25
jaskij[m]Yes, but does it come from DEPENDS or RDEPENDS?12:25
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)12:25
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto12:25
jaskij[m]Also, GV is generally bad with placing edge labels, so it might end up messy :/12:26
qschulzjaskij[m]: well, DEPENDS and RDEPENDS are always between two distincts tasks so the guess from task names is pretty safe12:26
jaskij[m]Cool. Now I just need to know which tasks those are ;)12:27
qschulzjaskij[m]: GH can do answers by mail too.12:27
qschulzjaskij[m]: I sent one for DEPENDS about 3h ago  :)12:28
qschulzdo_configure[depends] += "recipeB:do_populate_sysroot"12:28
qschulzI'll check12:28
jaskij[m]qschulz: Yeah, after linking that I realized it's a fairly common feature.12:28
qschulzjaskij[m]: https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-DEPENDS12:29
*** gsalazar_ <gsalazar_!~gsalazar@161.230.168.194> has joined #yocto12:30
*** gsalazar_ is now known as gsalazar12:30
jaskij[m]qschulz: now I feel like an idiot for not RTFMing. Thanks.12:31
jaskij[m]*thanks for checking12:32
jaskij[m]No irony or sarcasm intended12:32
qschulzIt took me some time to put one and one together and figure out that DEPENDS relies on tasks too. It should have been obvious but it wasn't in my brain12:33
*** gsalazar__ <gsalazar__!~gsalazar@194.38.148.130> has quit IRC (Ping timeout: 250 seconds)12:33
qschulzWhen I send links it's just to add sources, or not retype its content, no RTFM'ing intended :)12:33
qschulzI don't know how RDEPENDS dependencies are handled in the task tree tbh :/12:34
qschulzI'm not even sure if it's handled by bitbake or by the package manager handling the rootfs building from packages :/12:36
jaskij[m]Nah, I'm irritated with myself for not checking the manual and having you do it for me, is all.12:36
qschulzI assume there is something for bitbake otherwise it wouldn't know which recipe to build for which RDEPENDS12:36
rburtonautomatic RDEPENDS are added in do_package based on linkage12:36
qschulzrburton: the question is how to identify RDEPENDS "relationships" between two recipes12:37
rburtontypically the providers are in DEPENDS (albeit implicity, maybe) as otherwise you get warnings12:37
qschulzfrom the task tree12:37
rburtoni guess you don't, from the task tree12:37
qschulzrburton: s/DEPENDS/PACKAGES/ ?12:37
rburtonpkgdata has the complete set of runtime deps12:37
RPThe information about where a dependency comes from is lost in the final task graph as it really doesn't make much sense any more12:38
qschulzRP: from BB PoV sure, but from user PoV, if I want to understand why a package/recipe is pulled-in, knowing how it12:38
RPA dependency could be from a direct [depends] line, an [mcdepends], a DEPENDS, an RDEPENDS:XXX, from the runall/runonly commandline options and so on12:38
qschulz's added is a nice thing :)12:39
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Remote host closed the connection)12:39
RPqschulz: we don't store that info in the resulting taskdata/runqueue and we simply can't afford to :(12:39
qschulzRP: mmm yeah, it was more a suggestion like "likely to be from a DEPENDS in recipe A" to be added on an edge12:39
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto12:39
rburtonfrom the users point of view you want to look at the package dependency tree, not the bitbake task tree, surely12:40
RPFor example, a recrdepends can all all kinds of dependencies12:40
*** nad <nad!~nad@pr-svc-em1-016.emea.corpinter.net> has joined #yocto12:40
jaskij[m]-g used to output a pn-depends.dot, but that was dropped12:43
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)12:44
RPjaskij[m]: specifically because it was broken, it didn't show all these dependencies and that upset people trying to use it12:44
RPit showed some subset of the dependencies12:44
RPThis is why in the bug you mentioned I suggested the "exclude a recipe" approach to answering this question12:45
jaskij[m]I don't have it at hand, pet me finish my lunch brake and I'll read the bug convo again12:46
jaskij[m]But yes, exclusions are already planned12:46
jaskij[m]I think I could even default to excluding anything *-native and *-cross12:47
RPjaskij[m]: my point is that by doing the exclusion in bitbake, you find out exactly what is including it12:51
RPeven if it is via some recrdepends or something else odd12:52
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has quit IRC (Quit: Leaving)12:59
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 264 seconds)13:03
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has joined #yocto13:06
*** mckoan_ is now known as mckoan13:08
jaskij[m]So it comes back to using BB. Unsurprising - there's only so much you can do with task-depends.dot13:09
RPthe data simply isn't there and internally bitbake doesn't have it in runqueue either :(13:10
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed)13:11
jaskij[m]If I understand it right, `tinfoil` is a Python module for external software to work with BB's cache?13:11
rburtonnot just the cache, but its for external software to interface with bitbake13:14
jaskij[m]Is there any sort of Bitbake dev manual? Or do I just look at the code?13:15
RPjaskij[m]: tinfoil lets you have access to bitbake's internal apis. However whilst that does have task dependency graph functions, they will only give you the data that is in task-depends.dot too13:15
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)13:16
RPMy point is that runqueue which is where this data is built, doesn't have the information about which dependency line causes which end dependency because that doesn't really make sense in the way bitbake computes the task graph13:16
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto13:25
jaskij[m]RP: I'm trying to make sense on your comment in 3362 (that dep tools bug). Do you mean to actually blacklist the package from build and see what fails?13:25
RPjaskij[m]: yes13:34
*** kroon_ <kroon_!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Remote host closed the connection)13:36
*** kroon_ <kroon_!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto13:36
jaskij[m]That would definitely work, but I'm concerned about the speed of such a solution.13:36
jaskij[m]OTOH, I've realized that to efficiently work with task-depends.dot, you'd need a GUI where you can set up filters on the fly.13:38
*** tre <tre!~tre@ip5b4343c3.dynamic.kabel-deutschland.de> has quit IRC (Remote host closed the connection)13:40
*** akiCA <akiCA!~akiCA@user/akica> has joined #yocto13:43
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 268 seconds)13:44
*** codavi <codavi!~akiCA@user/akica> has joined #yocto13:44
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 260 seconds)13:47
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto13:48
*** akiCA <akiCA!~akiCA@user/akica> has quit IRC (Ping timeout: 265 seconds)13:48
*** paulg <paulg!~boodler@104-195-159-20.cpe.teksavvy.com> has joined #yocto13:50
*** FredO2 <FredO2!~willy562@bras-base-crnypq0201w-grc-01-76-68-181-2.dsl.bell.ca> has quit IRC (Remote host closed the connection)13:51
*** FredO2 <FredO2!~willy562@bras-base-crnypq0201w-grc-01-76-68-181-2.dsl.bell.ca> has joined #yocto13:51
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 250 seconds)13:52
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto13:53
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto13:55
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 265 seconds)13:58
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto13:58
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 250 seconds)14:13
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto14:16
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Ping timeout: 265 seconds)14:20
*** __Ozymandias__ <__Ozymandias__!~ozy@2605:a601:afbf:9800:b62e:99ff:fe3c:2882> has quit IRC (Quit: Konversation terminated!)14:33
*** zpfvo <zpfvo!~fvo@88.130.222.199> has joined #yocto14:35
*** gsalazar_ <gsalazar_!~gsalazar@194.38.148.130> has joined #yocto14:45
*** gsalazar <gsalazar!~gsalazar@161.230.168.194> has quit IRC (Ping timeout: 250 seconds)14:48
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:6099:bc9c:ac5b:94f9> has joined #yocto14:49
*** Granjow <Granjow!~simon@46.140.188.244> has quit IRC (Ping timeout: 265 seconds)15:11
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection)15:12
*** jsbronder <jsbronder!jsbronder@user/jbronder> has quit IRC (Quit: WeeChat 3.2)15:32
*** jsbronder <jsbronder!jsbronder@user/jbronder> has joined #yocto15:32
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)15:41
*** Guest2 <Guest2!~Guest2@2a01:e0a:1b9:3e10:97e3:5361:aa3:23fb> has joined #yocto15:42
*** Guest2 <Guest2!~Guest2@2a01:e0a:1b9:3e10:97e3:5361:aa3:23fb> has quit IRC (Client Quit)15:42
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto15:49
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)15:55
*** cperon <cperon!~cperonmat@2001:470:69fc:105::2d1a> has quit IRC (Quit: You have been kicked for being idle)16:00
*** sstiller <sstiller!~sstiller@p200300f07f11d500514249f49e98ea75.dip0.t-ipconnect.de> has quit IRC (Quit: Leaving)16:02
*** pgowda_ <pgowda_!uid516182@ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)16:17
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)16:21
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto16:24
*** ant__ <ant__!~ant@host-87-15-32-224.retail.telecomitalia.it> has joined #yocto16:42
vdhi there -- what should I grep to find examples of copying file via python?16:50
rburtonvd: https://docs.python.org/3/library/shutil.html16:51
vdthank you. Can a bitbake function have dash in its name? i.e. ROOTFS_POSTPROCESS_COMMAND += "func-with-dashes;"16:54
vdor is it unusual16:54
*** troth <troth!~troth@c-24-8-35-226.hsd1.co.comcast.net> has quit IRC (Ping timeout: 264 seconds)16:54
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)16:55
rburtonuse underscores16:56
jaskij[m]vd:  dashes are not legal in Python function names, so even if you're writing a shell function I'd avoid them16:56
vdthanks16:56
*** dev1990 <dev1990!~dev@dynamic-78-8-166-98.ssp.dialog.net.pl> has joined #yocto17:04
*** troth <troth!~troth@c-24-8-35-226.hsd1.co.comcast.net> has joined #yocto17:11
*** zpfvo <zpfvo!~fvo@88.130.222.199> has quit IRC (Remote host closed the connection)17:18
vddoes bitbake detect that a class defines a variable already defined by another class?17:22
vdor does it lead to hard to debug issues?17:23
rburtonno, the second just overwrites the first17:24
rburtonautotools.bbclass sets EXTRA_OECONF to a default value, and other classes can extend as needed17:24
rburtonso you really wouldn't want that to cause a warning17:24
*** mckoan is now known as mckoan|away17:25
vdI'm writing my own class to embed an initrd image within the rootfs, but INITRD is already used by the image-live class (which I don't use but still).17:25
vdI must choose a more unique name instead of initrd.bbclass I assume :)17:25
rburtonwell, you could just use that name and assume people don't inherit both :)17:26
vdthey shouldn't, because it is two distinct initrd strategies17:27
vdmine is more of an extension to bootspec to embed an image and add an initrd line to the specs17:29
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)17:30
*** nad <nad!~nad@pr-svc-em1-016.emea.corpinter.net> has quit IRC (Quit: Client closed)17:31
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto17:38
*** florian__ <florian__!~florian@dynamic-002-243-041-137.2.243.pool.telefonica.de> has joined #yocto17:42
kanavinrburton, I'm going to force correctly formatted and spelled upstream-status in oe-core patches17:44
kanavinkeep discovering patches that either lack it completely, or misspell things17:44
kanavinvia insane.bbclass17:44
kanavinwould be nice to force [reason] on Pending patches too btw, but maybe in the glorious future17:45
kanavinRP ^^^17:46
rburtoni used to run patchreview weekly but that was on an intel machine that doesn't exist anymore17:49
*** florian__ <florian__!~florian@dynamic-002-243-041-137.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)17:50
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-07-184-145-217-104.dsl.bell.ca> has joined #yocto17:52
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)17:57
RPkanavin: abelloni did promise me a patch. You can check them with "./scripts/contrib/patchreview.py meta "17:58
RPkanavin: but yes, enforcing that way may help. I've been hoping we get patchtest aback17:58
jaskij[m]`I_SWEAR_TO_MIGRATE_TO_PYTHON3` - beautiful. No, I'm not using Python2, just looking at the recipe for python-can17:59
*** adrian_ <adrian_!~F_Adrian@165.225.26.253> has quit IRC (Ping timeout: 250 seconds)18:07
jaskij[m]What's the status of Rust? Do I need to update to honister, or is `meta-rust` usable for Hardknott (and Dunfell)?18:07
*** ilunev <ilunev!~koolkhel@185.9.184.217> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)18:12
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto18:14
kanavinjaskij[m], you need to use the separate meta-rust layer for the older releases18:20
kanavinotherwise, just check if rust recipes are in meta.18:20
kanavinmeta/18:20
kanavinah18:20
kanavinI guess you need to try and see18:20
kanavinthe project doesn't test the layer in CI18:21
jaskij[m]qschulz RP : One idea I just hit upon for clearing up the task dependency tree for rendering is that *many* tasks only have a single dependency (eg. `do_compile -> do configure`). Personally, I see no harm in collapsing those into a single node for the purposes of displaying stuff.18:29
*** whuang0389 <whuang0389!~whuang038@cpeac202ebbe763-cmac202ebbe760.cpe.net.fido.ca> has joined #yocto18:40
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Quit: Leaving)18:41
*** rfried <rfried!~rfried@practical-trainings.com> has joined #yocto18:59
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto19:00
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-07-184-145-217-104.dsl.bell.ca> has quit IRC (Quit: WeeChat 3.3-dev)19:03
*** deurzen <deurzen!~deurzen@host-212-114-218-222.customer.m-online.net> has joined #yocto19:06
*** codavi <codavi!~akiCA@user/akica> has quit IRC (Read error: Connection reset by peer)19:08
deurzenHello everyone, I'm attempting a very basic (config-wise) Yocto build, with the end goal of getting Kubernetes (or K3s) running. Has anyone successfully attempted this? I'm getting 'dial tcp ... no route to host' and other 'dial tcp ...' error variations all over the place. I've tried building K3s on Hardknott and Kubernetes on Dunfell, both without success19:09
*** codavi <codavi!~akiCA@user/akica> has joined #yocto19:09
*** whuang0389 <whuang0389!~whuang038@cpeac202ebbe763-cmac202ebbe760.cpe.net.fido.ca> has quit IRC (Quit: Client closed)19:27
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto19:30
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)19:34
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto19:40
*** florian__ <florian__!~florian@dynamic-093-131-070-024.93.131.pool.telefonica.de> has joined #yocto19:43
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)19:44
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)19:46
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)19:46
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto19:47
*** florian__ is now known as florian19:48
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC (Quit: Leaving.)19:58
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 265 seconds)20:00
*** fleg <fleg!64bf4386e9@user/fleg> has quit IRC (Remote host closed the connection)20:05
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)20:09
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto20:19
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection)20:20
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto20:21
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)20:24
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto20:24
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)20:40
*** adrian_ <adrian_!~F_Adrian@62.32.0.69> has joined #yocto20:40
vdis there a python equivalent for 'install' in recipes?20:43
vd(to install files in the target filesystem)20:43
JPEWvd: do_install is _usually_ shell code, but I suppose you could write it in python if you wanted? Not sure if that would break anything20:45
vdJPEW I'm actually looking for a better implementation for calling 'install' via bb.process.run which isn't very smart20:47
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto20:47
*** kroon_ <kroon_!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Quit: Leaving)20:55
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:6099:bc9c:ac5b:94f9> has quit IRC (Ping timeout: 250 seconds)20:59
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Read error: Connection reset by peer)21:00
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto21:01
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)21:18
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto21:19
*** florian <florian!~florian@dynamic-093-131-070-024.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)21:26
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)21:34
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto21:34
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)21:36
RPjaskij[m]: That is probably reasonable although you'd somehow have to show that in the labelling and you have the dilemma of which side to collapse onto21:42
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto21:47
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto22:01
jaskij[m]<RP> "jaskij: That is probably..." <- Of course for label. As for side, I believe if I merge/collapse the nodes it shouldn't matter. I'm currently booted into the wrong OS to make a graphical example, but say if you have a -> c, b -> c, c -> d, d -> e, d -> f changing it into a -> cd, b -> cd, cd -> e, cd -> f should preserve all the information while simplifying the graph.22:21
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)22:24
*** bluelightning <bluelightning!~paul@2406:e003:151f:d701:9dfb:8bcd:46ae:ee7b> has joined #yocto22:24
*** florian <florian!~florian@dynamic-093-131-070-024.93.131.pool.telefonica.de> has joined #yocto22:58
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto23:06
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto23:22
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has quit IRC (Client Quit)23:25
*** Tokamak <Tokamak!~Tokamak@172.58.188.114> has joined #yocto23:29
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto23:57
« Sunday, 2021-11-14 Index Tuesday, 2021-11-16 »

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