Thursday, 2023-01-05

*** Algotech75 <Algotech75!~algotech@2a01:e0a:5e0:29b0:7ccf:687f:6d25:cd13> has quit IRC (Quit: Leaving)00:01
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)00:06
*** invalidopcode <invalidopcode!> has joined #yocto00:06
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
*** Wouter010067 <Wouter010067!> has joined #yocto00:10
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)00:11
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)00:30
*** dev1990 <dev1990!> has joined #yocto00:31
*** dev1990 <dev1990!> has quit IRC (Quit: Konversation terminated!)00:38
*** warthog19 is now known as warthog900:51
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)00:55
*** seninha <seninha!~seninha@user/seninha> has joined #yocto01:21
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 260 seconds)01:22
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 252 seconds)01:39
*** nemik <nemik!> has joined #yocto01:39
*** nemik <nemik!> has quit IRC (Ping timeout: 252 seconds)01:44
*** nemik <nemik!~nemik@> has joined #yocto01:44
*** dmoseley <dmoseley!> has quit IRC (Excess Flood)01:45
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 246 seconds)01:47
*** dmoseley <dmoseley!> has joined #yocto02:00
*** camus <camus!~Instantbi@> has joined #yocto02:01
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 255 seconds)02:04
*** davidinux <davidinux!~davidinux@> has joined #yocto02:06
*** camus1 <camus1!~Instantbi@> has joined #yocto02:06
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 272 seconds)02:06
*** camus1 is now known as camus02:06
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)02:11
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto02:12
*** starblue <starblue!> has quit IRC (Ping timeout: 268 seconds)02:39
*** starblue <starblue!> has joined #yocto02:41
*** xmn <xmn!> has quit IRC (Ping timeout: 272 seconds)02:54
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)02:58
*** seninha <seninha!~seninha@user/seninha> has joined #yocto02:59
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)03:12
*** xmn <xmn!> has joined #yocto03:32
*** marc1 <marc1!> has quit IRC (Ping timeout: 260 seconds)03:47
*** jclsn <jclsn!~jclsn@2a04:4540:652c:4a00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 260 seconds)03:49
*** jclsn <jclsn!~jclsn@2a04:4540:6520:fc00:2ce:39ff:fecf:efcd> has joined #yocto03:51
*** amitk <amitk!~amit@> has joined #yocto04:25
*** AKN <AKN!~AKN@> has joined #yocto04:38
riscaMan, do_package for ltp-ddt sure is slow on this old build. I started the build of this specific package almost 2 h ago :(04:44
riscaThis is not a bug report. I'm sure this has been fixed in later yocto/poky releases04:45
*** warthog9 <warthog9!> has quit IRC (Ping timeout: 246 seconds)05:09
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 252 seconds)05:09
*** nemik <nemik!> has joined #yocto05:09
*** nemik <nemik!> has quit IRC (Ping timeout: 272 seconds)05:14
*** nemik <nemik!~nemik@> has joined #yocto05:14
*** warthog19 <warthog19!> has joined #yocto05:28
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)05:28
*** invalidopcode <invalidopcode!> has joined #yocto05:28
*** warthog19 is now known as warthog905:34
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 272 seconds)05:44
*** nemik <nemik!~nemik@> has joined #yocto05:49
*** thomasd13 <thomasd13!> has joined #yocto05:50
barathmorning! question time. If I have a PACKAGECONFIG arg which sets a kernel module parameter, does setting that PACKAGECONFIG fit better into a machine conf or a distro conf? the module is only ever installed for for one machine06:05
*** seninha <seninha!~seninha@user/seninha> has joined #yocto06:41
*** azcraft <azcraft!~AzCraft@> has joined #yocto06:51
*** alessioigor <alessioigor!~alessioig@> has joined #yocto07:13
*** demirok <demirok!~bell@user/demirok> has joined #yocto07:36
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)07:36
*** alessioigor <alessioigor!~alessioig@> has joined #yocto07:36
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
*** Wouter010067 <Wouter010067!> has joined #yocto07:45
*** AKN <AKN!~AKN@> has quit IRC (Ping timeout: 252 seconds)07:48
*** olani <olani!> has quit IRC (Ping timeout: 260 seconds)07:54
*** xmn <xmn!> has quit IRC (Ping timeout: 255 seconds)07:58
LetoThe2ndbarath: if the MACHINE triggers it, respectively the need for it is defined through hardware, then it goes into the machine configuration (my $.02)08:09
LetoThe2ndand yo dudX08:09
*** zpfvo <zpfvo!> has joined #yocto08:09
*** gho <gho!> has joined #yocto08:09
barathhm, the kernel module itself is built due to the kernel config enabling it. the behavior of the kernel module is controlled by this PACKAGECONFIG which belongs to a recipe which installs a modprobe.d options config file and sets the parameter based on this PACKAGECONFIG, so in that way it seemed like policy... :D08:12
barathI guess it's dependent on the machine, ultimately, but also policy in a way08:12
LetoThe2ndbarath: if it is policy, then you always have to ask what defines it. is it the ABI/API that is affected by it? then distro. does it relate to hardware? then machine.08:14
LetoThe2ndbut of course there are always corner cases, and my opinion is certainly not authorative.08:14
*** zpfvo <zpfvo!> has quit IRC (Quit: Leaving.)08:17
*** zpfvo <zpfvo!> has joined #yocto08:17
barathbasically, the parameter toggles some behavior of the kernel module which is hardware related. but whether the behavior should be toggled or not depends on the use case of the image/distro, so that's why I thought policy08:17
barathwe'll see how it evolves :D08:17
*** lamm1 <lamm1!~lamm@> has joined #yocto08:18
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:22
*** AKN <AKN!~AKN@> has joined #yocto08:24
*** yocti <yocti!> has joined #yocto08:28
*** ChanServ sets mode: +o yocti08:28
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)08:45
*** invalidopcode <invalidopcode!> has joined #yocto08:45
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 252 seconds)08:48
*** yocti` <yocti`!> has joined #yocto08:51
*** yocti <yocti!> has quit IRC (Killed (NickServ (GHOST command used by yocti`)))08:51
*** yocti` is now known as yocti08:52
*** ChanServ sets mode: +o yocti08:52
*** nemik <nemik!> has quit IRC (Ping timeout: 246 seconds)08:53
*** nemik <nemik!~nemik@> has joined #yocto08:54
*** danielt <danielt!~danielt@2001:470:69fc:105::34d8> has quit IRC (Quit: You have been kicked for being idle)09:00
*** rocto <rocto!~rocto@user/rocto> has joined #yocto09:07
*** rocto <rocto!~rocto@user/rocto> has left #yocto09:07
*** bps <bps!~bps@> has joined #yocto09:08
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 246 seconds)09:27
*** zpfvo <zpfvo!> has joined #yocto09:30
*** tomzy_0 <tomzy_0!> has joined #yocto09:33
*** olani <olani!> has joined #yocto09:33
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)09:37
*** gsalazar_ <gsalazar_!> has joined #yocto09:39
*** gsalazar <gsalazar!> has quit IRC (Ping timeout: 260 seconds)09:42
*** prabhakarlad <prabhakarlad!> has joined #yocto09:44
*** d-s-e <d-s-e!> has joined #yocto09:45
*** gsalazar__ <gsalazar__!> has joined #yocto09:48
*** gsalazar_ <gsalazar_!> has quit IRC (Ping timeout: 265 seconds)09:51
*** d-s-e <d-s-e!> has quit IRC (Ping timeout: 265 seconds)10:08
*** d-s-e <d-s-e!> has joined #yocto10:09
*** seninha <seninha!~seninha@user/seninha> has joined #yocto10:12
*** gsalazar__ <gsalazar__!> has quit IRC (Quit: Leaving)10:37
*** gsalazar <gsalazar!> has joined #yocto10:38
*** manuel1985 <manuel1985!~manuel198@> has joined #yocto10:52
*** manuel1985 <manuel1985!~manuel198@> has quit IRC (Ping timeout: 268 seconds)10:58
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)11:03
*** seninha <seninha!~seninha@user/seninha> has joined #yocto11:03
*** AKN <AKN!~AKN@> has quit IRC (Ping timeout: 268 seconds)11:07
*** starblue <starblue!> has quit IRC (Ping timeout: 268 seconds)11:10
*** starblue <starblue!> has joined #yocto11:12
*** schtobia <schtobia!> has quit IRC (Quit: Bye!)11:19
*** schtobia <schtobia!> has joined #yocto11:20
*** olani <olani!> has quit IRC (Remote host closed the connection)11:25
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5380:54c0:ac8c:c10f:5c99:7020> has quit IRC (Ping timeout: 264 seconds)11:25
*** olani <olani!> has joined #yocto11:30
*** olani <olani!> has quit IRC (Remote host closed the connection)11:31
*** florian_kc <florian_kc!> has joined #yocto11:31
*** lamm1 <lamm1!~lamm@> has quit IRC (Ping timeout: 252 seconds)11:34
*** olani <olani!> has joined #yocto11:35
*** AKN <AKN!~AKN@> has joined #yocto11:41
qschulzdoes anyone remember how to create a new recipe for a pypi package?11:43
qschulzI remember there's a tool to do it, cannot find it (or cannot execute the script correctly :) )11:43
qschulzdevtool add?11:44
JaMayes, it will call recipetool in the end11:45
JaMarecipetool create <sources>11:45
qschulzand what is <sources> supposed to be?11:46
qschulz(it's a recipe for esptool)11:47
LetoThe2ndqschulz: ah having ESP32 fun too?11:47
qschulzLetoThe2nd: our latest SoM has an ESP32 for WiFi+BT on it :)11:48
LetoThe2ndqschulz: hehe11:48
*** d-s-e <d-s-e!> has quit IRC (Ping timeout: 268 seconds)11:48
qschulzi'm looking for the automagic tool to create the recipe because I know one exists11:48
qschulzbut I feel like I would have been faster writing it myself by the time I find the tool to do it :D11:49
LetoThe2ndqschulz: fun fact: i am currently working on a number of content pieces / demos that showcase a simple Mender client running directly on the ESP32.11:49
JaMaqschulz: URL to tarball or git repo11:50
qschulzJaMa: get a python backstrace with malformedurl exception :/11:51
JaMaqschulz: what URL did you use?11:51
qschulzJaMa: both the github URL and the tarball in pythonhosted11:52
qschulz(testing on kirkstone 4.0.6 from  a fedora37 host)11:53
JaMait's URL as in SRC_URI, so git://github.com11:53
JaManot sure why the first one would be malformedurl11:54
*** Payam <Payam!> has joined #yocto11:54
qschulzJaMa: same with git://11:54
qschulzI'll write it by hand, ping moto-timo our Python guy and see if he's any clue how to do it or what's going on :)11:55
qschulzJaMa: thanks for the support though :)11:55
JaMaworked for me, here is the generated recipe
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)12:01
qschulzJaMa: the issue is in another recipe /me facepalms12:05
qschulzoh no, I'm stupid :)12:06
qschulzI have a u-boot recipe that is machine specific12:06
qschulzand I didn't make it machine specific, so the variables aren't actually set12:07
*** seninha <seninha!~seninha@user/seninha> has joined #yocto12:13
*** Payam <Payam!> has quit IRC (Quit: Leaving)12:13
rburtonPSA: if you're debugging python code, is useful. Just pass bb.plain as the output callable and you get code breakdown on the console.12:16
*** olani <olani!> has quit IRC (Remote host closed the connection)12:17
*** Payam <Payam!> has joined #yocto12:18
Payamhow faster a yocto build would  be if I use a computer with 32 core in comparison on 16 cores?12:19
Payamwhen it comes to building and not downloading12:19
*** olani <olani!> has joined #yocto12:22
*** demirok <demirok!~bell@user/demirok> has quit IRC (Ping timeout: 260 seconds)12:22
*** olani <olani!> has quit IRC (Remote host closed the connection)12:23
smoogePayam, that depends on a lot of things outside of 'number of cores'. What is the memory layout of the motherboard, is there enough RAM per CPU and does the cpu cores actually handle that, what is the cache size of the chips, what is the IO and disk contention of the system (if its one disk then 32 cores only helps a little and you will be in D a lot), etc.12:23
JaMadepends on what you're building12:23
smoogePayam I have seen builds either be faster or slower depending on those and what you are building.12:23
Payamit is a c5-4xlarge runner instance on aws12:24
*** olani <olani!> has joined #yocto12:24
Payamsame build takes 5 hours with a 8 cores12:24
Payam4x has 1612:24
Payamso I wana try 8x has 3212:24
smoogethen you are most likely going to be waiting on 'disk' IO for what you are trying to build. Things which can be 'parallelized' may be faster but I would not expect it to be more than 30% faster with a lot of CPU time idle at times12:25
LetoThe2ndPayam: on average i would say maybe 20%. the sweet spot these days is somewhere in the 16-24 core area, and adding more cores does not give any real advantage. rather optimize your sstate usage, then.12:25
Payamyeah allright12:25
*** demirok <demirok!~bell@user/demirok> has joined #yocto12:26
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 272 seconds)12:29
*** nemik <nemik!> has joined #yocto12:29
*** nemik <nemik!> has quit IRC (Ping timeout: 268 seconds)12:34
*** nemik <nemik!~nemik@> has joined #yocto12:34
*** Payam <Payam!> has quit IRC (Quit: Leaving)12:37
*** Payam <Payam!> has joined #yocto12:41
PayamI use the AGL sstate mirror but I get his error : You are using a local hash equivalence server but have configured an sstate mirror.12:41
Payamshould I instead use the yocto mirror?12:42
rburtonif you're using a public sstate mirror then you also need to use their hashequiv server12:44
rburtonif they have a sstate mirror then they should tell you the hashequiv server url too12:44
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 248 seconds)12:47
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5380:54c0:ac8c:c10f:5c99:7020> has joined #yocto12:50
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5380:54c0:ac8c:c10f:5c99:7020> has quit IRC (Max SendQ exceeded)12:50
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5380:54c0:ac8c:c10f:5c99:7020> has joined #yocto12:51
PayamI use yoctoproject mirror instead12:54
Payamlet see if that gives same warning12:54
*** zpfvo <zpfvo!> has joined #yocto13:03
mcfriskLAYERSERIES_COMPAT changes to mickledore are applied in various places. should I append kirkstone to that locally when things just seem to work?13:07
JaMamcfrisk: in most layers where I've changed it to just mickledore is separate kirkstone compatible branch, which layer are you talking about?13:09
*** marc1 <marc1!> has joined #yocto13:09
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 255 seconds)13:13
mcfriskJaMa: meta-clang is latest, it still works with kirkstone13:15
JaMait didn't work even with langdale13:15
mcfriskfor us it does work and did not hit that with Ubuntu 22.0413:17
JaMamaybe you don't build target clang?13:18
mcfriskI would like to get us closer to master branches so I'll just overwrite the compat in our higher prio layers (seems local.conf can't do that)13:19
JaMahigher prio cannot do that as well, it needs to be in layer.conf parsed earlier (based on BBLAYERS order)13:20
PayamI used the state mirror on yoctoproject but it didn't help so much13:21
JaMaor you can volunteer to maintain kirkstone-clang15 branch (like there was dunfell-clang12 for newer clang for dunfell)13:22
Payamand I can not find the Hash server for agl13:22
Payamagl is very bad at documenting stuff13:22
mcfriskyes, needs to be in layer.conf of some layer down in the list of BBLAYERS13:22
mcfriskmaintainer is a bit too much, but I will continue using master and will come with patches if I can fix issues seen there13:23
JaMakhem: ^^13:24
*** Payam <Payam!> has quit IRC (Quit: Leaving)13:27
*** florian_kc <florian_kc!> has joined #yocto13:33
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)13:43
*** seninha <seninha!~seninha@user/seninha> has joined #yocto13:44
*** sakoman <sakoman!> has joined #yocto13:52
RPSad to see a patch removing corgi from the linux kernel :/13:55
*** goliath <goliath!~goliath@user/goliath> has joined #yocto13:56
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)13:58
barathI'm investigating whether I should replace a custom init env script with using oe-init-build-env. do people usually have their own custom init scripts? we can't use the oe-init-build-env script directly, since our checkout of poky is not in what we'd consider the "root"/"top" dir and other layers are outside of the poky dir so all paths relative to oeroot wouldnt be right14:01
qschulzbarath: you can use bitbake-layers add-layer with relative/absolute paths to setup your build environment14:04
kanavinbarath, I'm not sure why '. /full/path/to/poky/oe-init-build-env' wouldn't work for you14:04
qschulzwe have a layer setup tool now since langdale I believe, ahven't used it yet so don't rmember the name but kanavin will be able to help14:04
qschulzsome use kas also to set this all up14:05
kanavinbarath, people usually do use custom init scripts, but those usually wrap . oe-init-build-env one way or another.14:05
JaMaRP: :( meta-handheld looks also a bit sad14:07
barathhm thanks for those pointers. '. /full/path/to/poky/oe-init-build-env' works, but then my own layer's bblayer.conf.sample needs to do something like ##OEROOT##/../path/to/my/layer. I guess that's okay, just feels odd somehow. our current hacky init script just sets up TOPDIR such that all layers (poky, ours) are under it14:07
barathand my TEMPLATECONF needs to set paths relative to poky as well. I guess it's all just a matter of perspective :D14:08
kanavinbarath,  ##OEROOT##/../path/to/my/layer is totally fine14:08
barathalrighty. I guess I'm just not used to all paths being relative to poky14:09
qschulzoooh first time I need to add a recipe for something in the public domain!14:10
qschulzI guess it's not CC0 isn't it?14:11
*** xmn <xmn!> has joined #yocto14:11
barathdepends on the country I think :/14:15
rburtonqschulz: call it MIT, "public domain" is meaningless in the real world14:16
qschulzrburton: "If the Public Domain is not adequate for your purpose, you can instead consider this module under the MIT License as you prefer." kinda weird :)14:17
rburtonmight as well make it MIT and be done, as public domain is a legal minefield14:18
qschulzrburton: they don't provide a License file with the MIT license content though14:19
kanavinrburton, that's a very sad thing to say14:19
qschulz(will take the one from COMMON_LIC_DIR instead)14:19
qschulzah shoot, I had forgotten about python3-cryptography moving to rust... that;s going to be an expensive build only to add esptool support at runtime 😭14:21
rburtonkanavin: the entire point of cc0 was to formalise 'public domain' into something actually with legal basis14:21
kanavinrburton, yeah, I just find it sad that works without copyright is a 'legal minefield'14:22
rburtonthere's not worldwide agreement14:22
rburtonso if there's no license asserted, what is the license?14:22
smoogedepending on which country in the EU you are in, there are different definitions of public domain which mean completely different things. They also only 'cover' certain articles.14:24
kanavinrburton, there isn't. it's like asking a non-religious person what is their religion.14:24
smoogesorry should stay out of licensing conversations.14:24
kanavinbut what happens when copyright expires?14:25
rburtonkanavin: which suddenly turns from an interesting academic exercise to an expensive legal exercise when the lawyers get involved14:25
rburtonkanavin: depends on the juristiction14:25
kanavinI know disney is working hard to make it perpetual, and no significant works had their copyright expired in decades thanks to their efforts14:25
kanavinbut it is still supposed to happen, so that our 'culture' can grow14:25
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)14:26
*** alessioigor <alessioigor!~alessioig@> has joined #yocto14:26
kanavinRP: patch for qemu reproducibility sen14:30
*** thomasd13 <thomasd13!> has quit IRC (Ping timeout: 268 seconds)14:31
rburtonqschulz: the licence checksum is a way of validating the license, so the fragment of the readme that says "public domain, fallback to MIT" is sufficient14:31
qschulzrburton: ah, because the license file is actually matched from LICENSE variable?14:32
rburtonthe checksum is for telling the maintainer that the license strings changed14:32
*** demirok <demirok!~bell@user/demirok> has joined #yocto14:33
rburtonso if they relicened the next release to gpl, you'd get shouted at by bitbake14:33
qschulzyup, that I knew, I just had forgotten which variable "controlled" the license files to be included14:34
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
qschulzthat's why you need this NO_GENERIC_LICENSE for the ones that aren;t in COMON_LIC_DIR14:35
*** Wouter010067 <Wouter010067!> has joined #yocto14:35
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto14:39
*** AKN <AKN!~AKN@> has quit IRC (Read error: Connection reset by peer)14:43
*** d-s-e <d-s-e!> has joined #yocto14:47
*** d-s-e <d-s-e!> has quit IRC (Client Quit)14:48
*** azcraft <azcraft!~AzCraft@> has quit IRC (Remote host closed the connection)14:55
*** dmoseley <dmoseley!> has quit IRC (Excess Flood)14:55
*** azcraft <azcraft!~AzCraft@> has joined #yocto14:55
*** dmoseley <dmoseley!> has joined #yocto15:02
*** yashraj466 <yashraj466!~yashraj46@2401:4900:1b86:e48:f70b:13ef:5a20:4d9b> has joined #yocto15:05
*** vvmeson <vvmeson!> has quit IRC (Ping timeout: 252 seconds)15:11
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 252 seconds)15:23
*** vvmeson <vvmeson!> has joined #yocto15:26
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)15:39
*** Estrella <Estrella!> has quit IRC (Quit: - Chat comfortably. Anywhere.)15:39
*** invalidopcode <invalidopcode!> has joined #yocto15:39
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto15:43
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 248 seconds)15:46
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)15:51
*** Estrella <Estrella!> has joined #yocto15:52
*** demirok <demirok!~bell@user/demirok> has joined #yocto15:53
moto-timoqschulz: we never got around to teaching devtool/recipetool about the pypi.bbclass15:57
moto-timoqschulz: start with devtool add esptool
moto-timoqschulz: then add 'pypi' to inherit and drop the SRC_URI and the extra checksums... then begin the joys of dependencies (e.g. you need python3-reedsolo')15:59
*** zpfvo <zpfvo!> has joined #yocto16:01
rburtonyocton: 👋16:01
moto-timoyocton: 👋16:01
qschulzmoto-timo: ah I thought there was something already, or was there just someone who started the discussion and I h appened to be there at that time and took it as granted?16:02
qschulzmoto-timo: yeah, that's what i've done so far16:02
qschulzmoto-timo: there may be some discussion around python3-esptool recipe I made though16:02
qschulzwe'll see :)16:02
qschulzpython3-reedsolo has no dependency, but its scares me a bit, we'll see16:03
moto-timoqschulz: this is one case where 'esptool' might be the right name for the recipe... we should see what Debian named it (assuming it is available)16:03
qschulz(basically esptool pypi package contains three tools, and you don't necessarily need those three tools)16:03
moto-timoqschulz: the "rule" is "is it a tool or a library"16:04
moto-timoqschulz: ah, yes...16:04
qschulz(one of them requiring python3-cryptography, I'd rather split them into three different packages)16:04
qschulz(especially since I need the one that does NOT need it :) )16:05
moto-timoqschulz: that is fine... then you would want to use the PYPI_PACKAGE = "esptool" in each of the recipes so it reuses the  SRC_URI (off the top of my head)16:05
qschulzmoto-timo: esptool in debian16:05
qschulzmoto-timo: actually, since they are runtime dependencies only, a single recipe with three different packages should be jsut fine no?16:05
moto-timoqschulz: just fine yes16:05
qschulzmoto-timo: that's where I'm at currentlyu16:06
qschulzbeen waiting for python3-cryptography and its dependencies to compile for the last 1h3016:06
moto-timowelcome to Rust!16:07
qschulzI was so happy with my small builds16:07
qschulzand then I got the request to add esptool and nmcli to our images16:07
qschulzless happy now :)16:07
qschulz(nmcli brings mesa, wayland and whatnot)16:08
moto-timoI had a probably already mangled host struggling to build rust-native, nodejs and (a broken) u-boot at the same time  yesterday... it crashed the terminal twice ;)16:08
moto-timomangled == swap was maxed16:08
qschulz(I could probably slim it down but it's just demo images we provide, so not really worth it to sink hours in it)16:08
qschulzmoto-timo: my poor laptop with i7-10510U and 16gb of RAM salutes you :)16:09
moto-timoFWIW that recipe looks good... I am sure there is a way we could disable the py3-crypto build, but ... sigh16:10
moto-timoqschulz: you might want BBCLASSEXTEND = "native" ? don't know if esptool would be desireable in other recipes or not16:11
qschulzmoto-timo: thanks, you said the recipe should be rather called esptool than python3-esptool?16:11
moto-timoqschulz: it's a case where it _could_ reasonably be called esptool, but IMHO python3-esptool is ok too16:12
qschulzmoto-timo: I don't think so no, at least doesn't come to mind. Though... one usecase could be to build esptool so that it can be run from the host to flash the device (outside of Yocto)16:12
qschulzmoto-timo: what I struggle with is that esptool is both the name of the repo/pypi package and the name of one of the scripts it contains16:12
moto-timoqschulz: yeah, I think leave it python3-esptool is fine16:13
moto-timoqschulz: as for flashing outside of Yocto that probably hints at BBCLASSEXTEND nativesdk ;)16:13
qschulzshould I have a package called python3-esptool-esptool :D ?16:13
moto-timoor set PACKAGES to the three tool names?16:14
moto-timowhich would mean allow empty PN16:15
qschulzyeah, I have python3-esptool, python3-esptool-espefuse python3-esptool-espsecure right now16:15
qschulzso many different possibilities :)16:16
moto-timoqschulz: related (ship the python libraries)
moto-timoqschulz: but Debian is on ancient 2.8 version :/16:22
qschulzmoto-timo: yes, there's a reason we're not using it but pip's :)16:22
qschulzmoto-timo: not related to native/nativesdk your link right?16:23
rburtonndec: yay more yocto store credit.  shall i buy another very bright hoodie? :)16:23
moto-timoqschulz: right, I meant related to package split discussion16:23
qschulzmoto-timo: I have files in /usr/lib/python*/site-packages/ so I believe this should be covered16:24
qschulzbut now I'm curious what debian did16:24
ndecrburton: heh.. sorry about the delay.. there was a problem with getting the redeem codes.. but all speakers should have their code now!16:25
rburtoni've got two messenger bags but that yocto one is pretty sweet, just not sure when i'd use it unless i can convince my son its a cool school bag16:25
qschulzndec: rburton: shoot, i'll have to present again to get myself some swag16:25
qschulzoh no so very sad16:25
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)16:27
ndecmy son really likes all the yocto t shirt and swag .. the problem is with my wife ;)16:27
moto-timoqschulz: but it might not apply anymore since it is such a different version16:27
ldtsndec: maybe switch from cotton to silk...nice yocto scarfs :)16:28
moto-timondec: battling for closet space?16:28
LetoThe2ndmy wife would probably prefer yocto over metal shirts.16:30
ndecwell, she thinks there is too much yocto clothes.. i am trying to explain it can't be too much.. ;)16:30
ndecLetoThe2nd: right, I don't have metal shirts, at least!16:31
LetoThe2ndndec: room for improvement!16:31
qschulzLetoThe2nd: what about Yocto metal shirts16:32
moto-timowhen we have a conference in Finland16:32
LetoThe2ndqschulz: no i'm not going to wear chainmail16:32
LetoThe2ndmoto-timo: i'll be in oslo rather soon...16:33
*** florian_kc <florian_kc!> has joined #yocto16:36
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 246 seconds)16:38
*** zpfvo <zpfvo!> has joined #yocto16:41
*** zpfvo <zpfvo!> has quit IRC (Remote host closed the connection)17:01
*** gho <gho!> has quit IRC (Quit: Leaving.)17:08
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 255 seconds)17:09
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 265 seconds)17:15
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 252 seconds)17:18
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)17:34
*** invalidopcode <invalidopcode!> has joined #yocto17:34
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 260 seconds)17:38
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto17:40
*** bps <bps!> has joined #yocto17:45
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 272 seconds)17:46
*** dmoseley <dmoseley!> has quit IRC (Excess Flood)17:46
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto17:47
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 268 seconds)17:49
*** nemik <nemik!~nemik@> has joined #yocto17:49
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 272 seconds)17:53
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto17:53
*** dmoseley <dmoseley!> has joined #yocto17:54
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 260 seconds)17:59
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto18:01
*** roussinm1 <roussinm1!> has joined #yocto18:05
*** tomzy_0 <tomzy_0!> has quit IRC (Quit: Client closed)18:18
*** yashraj466 <yashraj466!~yashraj46@2401:4900:1b86:e48:f70b:13ef:5a20:4d9b> has quit IRC (Quit: Client closed)18:45
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)18:49
*** yashraj466 <yashraj466!~yashraj46@2401:4900:1b86:e48:f70b:13ef:5a20:4d9b> has joined #yocto18:51
*** florian_kc <florian_kc!> has joined #yocto18:57
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 268 seconds)19:29
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
*** Wouter010067 <Wouter010067!> has joined #yocto19:35
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 252 seconds)19:49
*** nemik <nemik!> has joined #yocto19:49
*** nemik <nemik!> has quit IRC (Ping timeout: 252 seconds)19:53
*** nemik <nemik!~nemik@> has joined #yocto19:54
*** kriive <kriive!~kriive@user/kriive> has quit IRC (Ping timeout: 252 seconds)20:03
*** gsalazar <gsalazar!> has quit IRC (Ping timeout: 252 seconds)20:22
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto20:28
*** gsalazar <gsalazar!> has joined #yocto20:45
*** florian_kc <florian_kc!> has joined #yocto20:45
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 260 seconds)20:54
*** prabhakarlad <prabhakarlad!> has joined #yocto21:10
*** mvlad <mvlad!~mvlad@2a02:2f08:470d:8800:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)21:10
*** gsalazar <gsalazar!> has quit IRC (Ping timeout: 272 seconds)21:14
*** gsalazar <gsalazar!> has joined #yocto21:19
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)21:27
*** gsalazar <gsalazar!> has quit IRC (Ping timeout: 260 seconds)21:43
*** florian_kc <florian_kc!> has joined #yocto21:50
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection)22:13
*** roussinm1 <roussinm1!> has quit IRC (Ping timeout: 268 seconds)22:26
*** gsalazar <gsalazar!> has joined #yocto22:36
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 260 seconds)22:45
*** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 252 seconds)23:04
RPJPEW: I think I've done something dangerous with bitbake and the threading. My worry is that the server/process code now has two threads and in one of the threads we do the parsing using multiprocessing.Process :/23:08
RPWe're careful that we don't hold locks with the fork() would occur but I suspect there can be potential issues23:13
*** gsalazar <gsalazar!> has quit IRC (Ping timeout: 268 seconds)23:13
JPEWRP: oh ya. Didn't think about that. Threading and forks don't mix23:17
RPJPEW: I have a second issue that when we create the parser Process() processes they inherit and keep full copies of the Cooker object in memory even if it isn't referenced. We can't just start from scratch in the parser thread though as there is context we do need23:18
JPEWWhy is that a problem?23:21
RPJPEW: every parser process is ending up with an RSS of 1.6GB locally. Copy on write in the kernel helps most of the time, until python gc kicks in23:23
JPEWRP: this would only be seen on the second time parsing is done with memory resident bitbake?23:26
JPEWOr is it all the time23:26
*** yashraj466 <yashraj466!~yashraj46@2401:4900:1b86:e48:f70b:13ef:5a20:4d9b> has quit IRC (Quit: Client closed)23:27
RPJPEW: even single threaded, it can be an issue with a partially valid cache from disk with parsing needed for some subset of recipes23:27
RPer, even single instance23:27
RPobviously memory resident with the new cache triggered makes things a lot worse23:27
JPEWYa makes sense23:28
*** florian_kc <florian_kc!> has joined #yocto23:40
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)23:44

Generated by 2.17.2 by Marius Gedminas - find it at!