Tuesday, 2021-10-05

*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has joined #yocto00:11
*** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has quit IRC (Remote host closed the connection)00:48
*** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has joined #yocto01:07
*** RobertBerger <RobertBerger!~rber|res@ppp-2-86-134-166.home.otenet.gr> has joined #yocto01:32
*** rber|res <rber|res!~rber|res@ppp-2-86-134-166.home.otenet.gr> has quit IRC (Ping timeout: 252 seconds)01:34
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC (Quit: Leaving.)02:06
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto02:22
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has quit IRC (Remote host closed the connection)02:29
*** jmiehe1 <jmiehe1!~Thunderbi@user/jmiehe> has joined #yocto03:19
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Ping timeout: 252 seconds)03:20
*** jmiehe1 is now known as jmiehe03:20
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)04:26
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto04:40
alicefhello, poky git certification changed ? yesterday I got some invalid certification error on accessing poky04:41
aliceffatal: unable to access 'https://git.yoctoproject.org/git/poky/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none04:41
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)05:01
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto05:20
*** landgraf1 is now known as landgraf05:20
*** landgraf is now known as landgraf105:21
*** landgraf1 is now known as landgraf05:21
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto05:50
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)05:53
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto05:54
*** Sion <Sion!~dev@178-84-56-61.dynamic.upc.nl> has joined #yocto05:57
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor)06:00
*** m4ho <m4ho!~m4ho@81.20.119.6> has quit IRC (Quit: WeeChat 3.1)06:07
ndec_agherzan: sorry about the delay.. I am (now) seeing your request.06:20
*** m4ho <m4ho!~m4ho@81.20.119.6> has joined #yocto06:24
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:6c1e:fdd9:577c:74e9> has quit IRC (Quit: Leaving)06:29
JosefHolzmayrTheyo dudX06:29
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:32
*** frieder <frieder!~frieder@mue-88-130-78-070.dsl.tropolys.de> has joined #yocto06:35
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-07-184-145-217-104.dsl.bell.ca> has quit IRC (Quit: WeeChat 3.3-dev)06:36
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.96.230> has joined #yocto06:36
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto06:42
*** Guest54 <Guest54!~Guest54@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto06:43
*** mckoan|away is now known as mckoan06:46
mckoangood morning06:47
mckoanalicef: actually it is https://git.yoctoproject.org/cgit/cgit.cgi/poky/06:48
mckoanalicef: and https://git.yoctoproject.org/git/poky is out of order06:49
mckoanndec_: ^06:50
JosefHolzmayrThemckoan: alicef git clone git://git.yoctoproject.org/poky.git works for me06:51
JosefHolzmayrThehttps://git.yoctoproject.org/cgit/cgit.cgi/poky/ also does06:52
*** zpfvo <zpfvo!~fvo@88.130.217.155> has joined #yocto06:58
agherzanHey ndec_ , there is no delay. I was just wondering what are cu current ETAs. Thanks06:59
*** ant__ <ant__!~ant@host-82-54-240-7.retail.telecomitalia.it> has quit IRC (Ping timeout: 250 seconds)07:04
alicefJosefHolzmayrThe: depend from your ca-signature package I think07:07
alicefca-certificates/now 20210119~18.04.1 dosen't work07:07
Guest54Hey guys, just want to ask the pro's here. What IRC client you use? My hexchat does not work anymore because of the certificate issue with libera :)07:07
SionHello, I use Konverstation07:08
alicefGuest54: let's encrypt also changed certification https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/07:08
JosefHolzmayrTheGuest54: irccloud, element via bride, irssi. it depends.07:09
SionKonversation* I really need some coffee :)07:09
JosefHolzmayrThe*bridge, even07:09
alicefdeprecating DST Root CA X307:09
alicefyou need to trust ISRG Root X107:09
JosefHolzmayrThealicef: just updated to 20210119~20.04.2 (its a 20.4 box obviously), still no problem here.07:10
Guest54This certification stuff is a topic I havn't digged into it yet..07:10
alicefmaybe is only for 18.04 ?07:11
JosefHolzmayrThealicef: possible07:11
alicefalso could be that you still are caching new one07:11
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto07:11
alicefI'm no certicate expert btw :/07:12
JosefHolzmayrThealicef: also possible.07:12
JosefHolzmayrTheneither am i, just poking things and trying.07:12
*** goz3rr <goz3rr!~goz3rr@2a02-a44d-7801-1-c69-2582-850-63ce.fixed6.kpn.net> has joined #yocto07:14
JosefHolzmayrThealicef: i'd say asking the admin to verify the cert chain might be a good idea, but it doesn't seem to be a widespread issue at the moment.07:17
mckoanalicef: JosefHolzmayrThe: I am on 18.04 and git clone works07:18
mckoangit clone git://git.yoctoproject.org/poky07:18
mckoanGuest54: irssi07:19
alicefmckoan: what version of ca-certificates ?07:29
mckoanalicef: 20210119~18.04.207:40
alicefmaybe is a repo problem ...07:45
alicefrepo command not repo repository07:45
mckoanalicef: update repo too07:46
mckoanalicef: no, sorry we are testing git clone only07:46
alicefI had to fix it manually with git config --global http.sslverify false07:46
qschulzoverride: there's no version for drivers in the kernel, they are just part of the kernel, so whatever the kernel version is at that time, that's their "version". Also, technically that means almost nothing since you can have a vendor kernel which has a completely different source code for your driver07:46
*** alicef is now known as alicef_07:47
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (*.net *.split)08:12
*** wooosaii <wooosaii!~wooo@89-212-21-243.static.t-2.net> has quit IRC (*.net *.split)08:12
*** tlwoerner <tlwoerner!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has quit IRC (*.net *.split)08:12
*** alinucs <alinucs!~abo@215.ip-51-38-235.eu> has quit IRC (*.net *.split)08:12
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (*.net *.split)08:12
*** jsandman <jsandman!~jsandman@95.179.203.88> has quit IRC (*.net *.split)08:12
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC (*.net *.split)08:12
*** marka <marka!~marka@198-84-181-245.cpe.teksavvy.com> has quit IRC (*.net *.split)08:12
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has quit IRC (*.net *.split)08:12
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has quit IRC (*.net *.split)08:12
*** mcfrisk <mcfrisk!mcfrisk@kapsi.fi> has quit IRC (*.net *.split)08:12
*** Tokamak <Tokamak!~Tokamak@172.58.187.89> has quit IRC (Ping timeout: 252 seconds)08:15
user_Hi team,We want to deploy a HTTPs server  in a yecto build system,With libulfius C based protocol. Tried adding Recipes to SDk but while Building complete SDk along with Ulfius,orcania,yder  do_compile is failing.Please suggest is there any way to resolve it or any alternate yecto supported http package available.08:18
JosefHolzmayrTheuser_: the way is to provide proper information and logs and ask concise questions about the points where you are stuck.08:23
*** alinucs <alinucs!~abo@215.ip-51-38-235.eu> has joined #yocto08:23
JosefHolzmayrTheuser_: for a bunch of already prepared httpds, see https://layers.openembedded.org/layerindex/branch/master/layer/meta-webserver/08:23
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto08:24
*** wooosaii <wooosaii!~wooo@89-212-21-243.static.t-2.net> has joined #yocto08:24
*** tlwoerner <tlwoerner!~tlwoerner@pppoe-209-91-167-254.vianet.ca> has joined #yocto08:24
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has joined #yocto08:24
*** jsandman <jsandman!~jsandman@95.179.203.88> has joined #yocto08:24
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto08:24
*** marka <marka!~marka@198-84-181-245.cpe.teksavvy.com> has joined #yocto08:24
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has joined #yocto08:24
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has joined #yocto08:24
*** mcfrisk <mcfrisk!mcfrisk@kapsi.fi> has joined #yocto08:24
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto08:30
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:43
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Quit: ZZZzzz…)08:48
*** lucaceresoli <lucaceresoli!~ceresoli@tech.aim-sportline.com> has joined #yocto08:55
*** kiran_ <kiran_!~kiran@2607:fea8:5a80:ea0:c39:e42c:85fd:eccd> has quit IRC (Ping timeout: 252 seconds)09:20
goz3rrI've recently started running into an issue with building using the crops/poky:ubuntu-20.04 docker container where at one point an rm -rf command gets killed with SIGABRT. If I manually delete the file that is being deleted and run the build again it just fails in the same way on a different file. The only "fix" so far is to delete the entire build09:22
goz3rrdirectory and start a build from scratch09:22
goz3rrException: subprocess.CalledProcessError: Command '['rm', '-rf', '/workdir/poky/build/tmp/work/colibri_imx6ull-tdx-linux-gnueabi/xpac-image-dev/1.0-r0/rootfs']' died with <Signals.SIGABRT: 6>.09:22
goz3rrWhat would be the best approach to start debugging something like this?09:22
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto09:31
*** arlen <arlen!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has quit IRC (Ping timeout: 250 seconds)09:39
ndec_agherzan: the timeline is (supposed to be) ~1 week for me + TSC to review, then 1 week for AB/members to review.09:40
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Ping timeout: 256 seconds)09:47
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto09:50
agherzanSounds good. That gives me a reference. I understand it is not a commitment. Thanks ndec_10:12
*** Guest54 <Guest54!~Guest54@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Quit: Client closed)10:21
*** oobitots <oobitots!~oobitots@aer01-mda2-dmz-wsa-4.cisco.com> has joined #yocto10:25
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has joined #yocto10:46
manuel1985Hi people. Does anyone know how to delete a directory, but not its contents?10:50
manuel1985Sounds weird, I know.10:50
qschulzmanuel1985: what do you want to do?10:50
manuel1985I once ended up being in the seemingly same directory in two terminal windows, showing different content. Took me half a day to realize these were different directories, as they had different inodes. Want to recreate that and teach my team so they won't as well lose half a day like I did.10:51
manuel1985Essentially I want to set up a testground. Or demonstrator.10:52
manuel1985cannot just `rm` the dir, as it's refusing to do anything unless `--recursive` is given. But with `--recursive`, it obviously removes the content as well.10:54
manuel1985IIRC, back then, I could even create new files in the dir not existing anymore.10:55
qschulzmanuel1985: what about mv?10:55
qschulzotherwise yeah, you'll have to dig into inodes and I can't help with that :)10:56
manuel1985qschulz: You were right! The trick is not to remove the olddir, but to `mv` it.10:58
manuel1985That will blow my teams minds. Am teaching them some unix.10:58
qschulzmanuel1985: the trick is to close and reopen the terminal when something happens you don't understand :p11:03
manuel1985qschulz: `cd ~ && cd -` is my favorite command :) should bind it to an alias11:04
qschulzmanuel1985: alias isthisreallife='cd "$HOME" && cd -' :)11:05
manuel1985qschulz: That's a very suitable name!11:32
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto11:36
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)11:45
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto11:46
*** mckoan is now known as mckoan|away11:48
JosefHolzmayrThewhats so funny about `cd ~ && cd -`?12:03
qschulzmanuel1985: IIRC, I used to do `cd .` and I think that worked too when the inode is different but in the same place on the fs?12:12
qschulzJosefHolzmayrThe: nothing, just discussing how to recover from a directory whose inode has changed while a terminal is in said directory12:13
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has joined #yocto12:13
JosefHolzmayrTheUhr huh12:14
*** oobitots <oobitots!~oobitots@aer01-mda2-dmz-wsa-4.cisco.com> has quit IRC (Quit: Client closed)12:15
*** dmoseley_ <dmoseley_!~dmoseley@24.96.56.90> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)12:18
*** lexano <lexano!~lexano@cpe00e06722f0e4-cm98524a70e35e.cpe.net.cable.rogers.com> has joined #yocto12:19
*** dmoseley <dmoseley!~dmoseley@24.96.56.90> has joined #yocto12:22
*** ant__ <ant__!~ant@host-195-31-129-205.business.telecomitalia.it> has joined #yocto12:30
*** angolini <angolini!uid62003@id-62003.helmsley.irccloud.com> has joined #yocto12:41
*** dagmcr <dagmcr!sid323878@id-323878.uxbridge.irccloud.com> has quit IRC (Excess Flood)12:43
*** dagmcr <dagmcr!sid323878@id-323878.uxbridge.irccloud.com> has joined #yocto12:43
overrideback with my CAN driver questions12:55
overridehow can I know for certain what version of CAN driver's running on my board currently ??12:56
smurraylook in the kernel you're running?12:57
*** oobitots <oobitots!~oobitots@aer01-mda1-dmz-wsa-7.cisco.com> has joined #yocto12:59
*** oobitots <oobitots!~oobitots@aer01-mda1-dmz-wsa-7.cisco.com> has quit IRC (Client Quit)13:00
qschulzoverride: https://www.yoctoproject.org/irc/%23yocto.2021-10-05.log.html#t2021-10-05T07:46:5213:00
qschulzbasically, just find the sources of the kernel you are using on your board, with patches applied and that's the current state of your driver13:01
overridesmurray: So tired the modinfo command to figure whats running on the kernel, now how do I figure what version of the driver is on the main/master for the linux repo. Im guessing this repo has the latest and greatest drivers? https://github.com/torvalds/linux/tree/master/drivers/net/can13:02
*** Guest3 <Guest3!~Guest3@2a01:e0a:76:4400:1299:6fdd:33a7:a323> has joined #yocto13:03
qschulzoverride: there is no such thing as a version for a driver except if it's an out-of-tree driver, which does not seem to be the case for you13:03
qschulzoverride: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/ is the master branch of the kernel13:04
overrideqschulz: sorry missed your relpies from before. So the board vendor I understand might have patched the kernel and all and theres no such version for the driver..13:05
overridebut like can I atleast figure out what was the base version or something they started applying their patches to?13:06
overridewe basicslly just have to grep and look for clues?13:07
rburtonif you have a kernel tree then the top level Makefile contains the version13:12
qschulzoverride: git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/ && git fetch upstream && git merge-base upstream/master HEAD13:15
qschulzthat's the kernel base, but then your vendor could have also merged back some branches from upstream13:15
qschulzso what rburton said, but they might also have fucked up the whole thing by resolvin merge conflicts like idiots... welcome to vendor BSP world :) (or let's say anything !upstream :) )13:18
*** Ad0 <Ad0!~Ad0@93.124.245.194> has joined #yocto13:25
*** Guest323 <Guest323!~Guest3@80.215.178.98> has joined #yocto13:27
*** Guest3 <Guest3!~Guest3@2a01:e0a:76:4400:1299:6fdd:33a7:a323> has quit IRC (Ping timeout: 256 seconds)13:27
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC (Quit: off)13:28
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-07-184-145-217-104.dsl.bell.ca> has joined #yocto13:32
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto13:35
*** Guest323 <Guest323!~Guest3@80.215.178.98> has quit IRC (Quit: Client closed)13:38
overriderburton: where would the tree be getting fetched into? I looked around in the usual workspace and tmp kinda folders13:40
overrideI have no idea what might be a good thing to find . -name for or something for the kernel tree..13:41
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has quit IRC (Ping timeout: 252 seconds)13:42
qschulzoverride: we talked about preferred_version and preferred-provider yesterday13:42
qschulzthat's how you find out13:42
manuel1985Did some of you ever have a worn-out eMMC? One of our devices has the following kernel panic: https://pastebin.pl/view/528338ee13:46
manuel1985`mmc extcsd read` reports `0x10`, though, that is wear is in the range of 0% to 10%13:47
qschulzmanuel1985: imx8m family IIRC?13:48
*** some_coder23 <some_coder23!~some_code@2a02:8109:a280:2d8d:9502:f9d3:d146:db2c> has joined #yocto13:48
qschulzmanuel1985: for both wear levels?13:49
manuel1985Nope, NVIDIA Jetson TX213:49
manuel1985qschulz13:49
manuel1985yes, for both wear levels13:49
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto13:50
manuel1985Also wondering why BOTH wear levels are != 0x00, as one is for SLC and the other for MLC IIRC. Thought an eMMC can either be of this or that technology.13:50
qschulzmanuel1985: no you can have both at the same time13:52
qschulzyou don't have to set the user area partition to the full size of the emmc13:52
qschulzand then you have a mix13:52
manuel1985qschulz: I see, thx13:53
qschulzthough it's a one-time setting, you cannot reduce or increase the size of the user area partition13:53
qschulzonce set13:53
*** ant__ <ant__!~ant@host-195-31-129-205.business.telecomitalia.it> has quit IRC (Quit: Leaving)14:04
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection)14:09
*** Tokamak <Tokamak!~Tokamak@172.58.189.117> has joined #yocto14:17
*** Sion <Sion!~dev@178-84-56-61.dynamic.upc.nl> has quit IRC (Ping timeout: 268 seconds)14:24
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Ping timeout: 256 seconds)14:26
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto14:27
*** Tokamak <Tokamak!~Tokamak@172.58.189.117> has quit IRC (Ping timeout: 245 seconds)14:29
*** Tokamak <Tokamak!~Tokamak@172.58.189.117> has joined #yocto14:33
*** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has quit IRC (Ping timeout: 246 seconds)14:34
*** troth1 <troth1!~troth@c-24-8-35-226.hsd1.co.comcast.net> has quit IRC (Quit: Leaving.)14:35
*** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has joined #yocto14:36
*** troth <troth!~troth@c-24-8-35-226.hsd1.co.comcast.net> has joined #yocto14:41
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto14:43
*** Tokamak <Tokamak!~Tokamak@172.58.189.117> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)14:48
*** pidge <pidge!~pidge@194.110.145.166> has joined #yocto14:54
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:c924:72d:8664:838b> has joined #yocto14:56
*** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed)15:06
*** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has quit IRC (Ping timeout: 252 seconds)15:07
*** otavio <otavio!~otavio@201-34-65-230.user3p.brasiltelecom.net.br> has joined #yocto15:09
*** mihai <mihai!~mihai@user/mihai> has quit IRC (Quit: Leaving)15:17
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has quit IRC (Quit: Leaving)15:25
*** pidge <pidge!~pidge@194.110.145.166> has quit IRC (Quit: Client closed)15:46
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:47
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Quit: Leaving)15:47
*** davidinux <davidinux!~davidinux@84.17.59.156> has quit IRC (Ping timeout: 268 seconds)15:50
*** kpo <kpo!~kpo@bwu34.internetdsl.tpnet.pl> has joined #yocto15:56
*** dev1990 <dev1990!~dev@dynamic-78-8-51-35.ssp.dialog.net.pl> has joined #yocto15:57
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto15:58
kpoHello! I'm using yocto for building ARM image for Raspberry PI. Is it possible to utilize bitbake to run unit tests? I've got qmake based project, that can built two executables (based on subdirs template): 'app' and 'tests'. I would like to build 'tests' for host architecture, i.e. x64, run them, and if they pass, build 'app' for ARM and add it to the Image. If running 'tests' fail, then bitbake should fail15:59
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has quit IRC (Client Quit)16:02
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC (Remote host closed the connection)16:04
*** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has joined #yocto16:05
yatesis there a list of the top-level personnel involved in yocto? i'm giving an internal talk on the Yocto Summit 2021 to my colleagues and thought it would be good to mention some of the key names.16:06
yatese.g., rburton, etc?16:07
yatesi know Khem Raj, but don't know his focus on yocto16:07
yateskergoth, tlwoerner, ...16:07
*** JaMa <JaMa!~martin@ip-109-238-218-228.aim-net.cz> has joined #yocto16:08
*** zpfvo <zpfvo!~fvo@88.130.217.155> has quit IRC (Remote host closed the connection)16:09
yatesDavid Reyna, ... etc16:10
yatesi can see the names, but knowing their role would be nice.16:10
yatesroles16:10
kanavinRP: I am going slightly mad here with sstate hashes where the hash in filename doesn't match the hash printed by bitbake-dumpsig16:11
kanavinjust wondered if by any chance it's known16:11
kergothyates: I don't have an official role, personally, though I did in the past. Just a developer at siemens disw and contributor when possible. I will be working to change that in the future to attempt to help alleviate rp's massive overload.16:12
kergothwon't speak for anyone else, not sure if there's an org chart at htis point16:12
kanavin(btw I do have a working mozjs 91.1.0 build now, which uses quite a bit more rust than librsvg :)16:12
yateskergoth: ok i understand16:14
yatesi am including the profile for each presentation which includes the name of the presenter and their involvment - thus i'm realizing such a list of names up front is not necessary16:15
kergothyates: https://www.yoctoproject.org/about/technical-leadership/ https://www.yoctoproject.org/about/administrative-leadership/ https://www.yoctoproject.org/community/ambassadors/16:15
kergothseems to be what's on the site, admittedly minimal16:15
kergothdoesn't cover stable branch maintainers or rburton's role, etc16:15
yatesnice!16:15
kergothmaintainers info in the oe-core repo may provide more insight16:16
yatesi will include these links on a slide - good info16:17
kanavinyates, RP is the architect and integrator, khem is in charge of toolchains, Bruce is doing the kernel, I'm maintaining oe-core16:17
yatesBruce Schneir?16:18
kanavinBruce Ashfield16:18
kanavinthen there's Armin doing meta-oe stable maintenance, same khem doing meta-oe integration16:19
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Remote host closed the connection)16:19
kanavinAnuj maintans recent releases, Steve Sakoman maintains LTS16:20
yateswould you mind emailing me the full names (first/last) with roles at randyy@scc-inc.com, please?16:20
kanavinI would16:20
yatesi don't know some of these people16:20
kanavintoo much work :)16:20
yatesok16:20
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto16:20
kanavinI'd rather sort out rust issues16:20
yatesthat will keep you busy16:21
kanavinyou bet it does http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/package-version-updates16:21
yatesp)16:21
kanavinreally, who is doing what is not important, the important thing is that your organizations joins YP as a member, and hires people to maintain things16:22
yatesat least now everyone knows my email and can send me nastygrams about all my stupid questions!16:22
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)16:22
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)16:22
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto16:23
kanavinsomehow a lot of companies tend to thing YP maintains and develops itself, and they can just take it and all will be fine16:23
kergothThat's pretty common with open source projects in general16:24
kergothjust look at how much critical infrastructure is nearly unmaintained16:25
kergothhttps://xkcd.com/2347/ comes to mind16:25
kanavinit's a failure of market economy, yes16:25
yateskergoth: +1, lol16:26
yatesbut it's not funny..16:26
kergothyeah.. one of those laugh so you don't cry kind of things eh.. software sucks16:27
kergothheh16:27
kergothwell we do what we can16:27
RPkanavin: it is probably hash equivalence16:27
yateswhat about Montana? :)16:28
kanavinRP: I've piled up quite a few patches beating rust into shape. One of the more invasive changes is that I made BUILD_SYS/TARGET_SYS strings fully formed - no more omissions or defaults, e.g. BUILD_SYS is now x86_64-oenative-linux-gnu instead of x86_64-linux16:29
kanavinmakes things a lot simpler with rust16:29
RPkanavin: you mean changing project wide outside rust?16:30
kanavinRP: yes16:30
RPkanavin: that idea fills me with dread16:30
kanavinRP: I'll test it with a-full and meta-oe on the AB16:30
RPkanavin: I'm reluctant to go changing things like that without a really good reason16:31
kanavinthere are a few places where absence of -gnu is assumed, I'm fixing those up16:31
RPkanavin: back on the hash subject, the difference in calc hash to the one in use is almost certainly due to hash equivalence being involved. I've struggled to see how we can reconcile things16:33
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)16:33
*** jmiehe1 <jmiehe1!~Thunderbi@user/jmiehe> has joined #yocto16:33
*** jmiehe1 <jmiehe1!~Thunderbi@user/jmiehe> has quit IRC (Client Quit)16:35
kanavinRP: I am seeing unnecessary rebuilds of rust-native in different build directories sharing the sstate cache, will check again now why they happen. there are two different siginfo files in the cache, but if you run bitbake-dumpsig on them, it prints same computed task hash at the end16:38
kanavinRP: how to check further?16:39
RPkanavin: are they for different arm machines? JaMa posted about a hash problem with rust-cross and sigs16:45
RPkanavin: sorry, you said native16:45
RPkanavin: are you sharing the hashequiv data between the builds?16:46
*** goliath <goliath!~goliath@user/goliath> has joined #yocto16:47
*** davidinux <davidinux!~davidinux@84.17.59.156> has joined #yocto16:52
*** goz3rr <goz3rr!~goz3rr@2a02-a44d-7801-1-c69-2582-850-63ce.fixed6.kpn.net> has quit IRC (Quit: Client closed)17:11
*** frieder <frieder!~frieder@mue-88-130-78-070.dsl.tropolys.de> has quit IRC (Remote host closed the connection)17:21
kanavinRP: I'm not sure, I am using the default config for both, so I guess I do.17:44
kanavinRP: the issue is, one builds completes, places the populate_sysroot into cache. Then the other build ignores that, and proceeds to rebuild, and also places populate_sysroot into cache. The siginfo files have the same content (as reported by bitbake-dumpsig), but their filenames are different17:50
khemRP:  I think problem will show up when doing similar machine builds e.g. so perhaps make a copy of qemuarm to qemuarmcopy or something and see if it gets reused17:59
kanavinI'm using qemumips64 and qemux86_6417:59
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)18:02
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.96.230> has quit IRC (Quit: ZNC 1.8.2 - https://znc.in)18:09
kanavinRP: ah, I think I'm not sharing that data, as that is actually the default :) it's different databases in different build directories18:14
kanavinI do wonder why the filename and the task hash inside it differ, as I suspect that's why a rebuild is happening, since the file cannot be found from the calculated task hash :-/18:15
kanavinI wiped everything and doing a clean build now, first one, then the other18:16
kanavinRP: ok, that helped. maybe things in build/cache/ were somehow not right :-/ I'll keep an eye on it.18:25
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.96.230> has joined #yocto18:32
*** Tokamak <Tokamak!~Tokamak@172.58.189.117> has joined #yocto18:57
*** some_coder23 <some_coder23!~some_code@2a02:8109:a280:2d8d:9502:f9d3:d146:db2c> has quit IRC (Quit: Client closed)18:58
RPkanavin: its a non-obvious side effect of the hash equiv changes. I'm not sure what we do to improve usability19:06
*** ant__ <ant__!~ant@host-82-54-240-7.retail.telecomitalia.it> has joined #yocto19:14
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:c924:72d:8664:838b> has quit IRC (Ping timeout: 246 seconds)19:26
*** amitk_ <amitk_!~amit@103.208.69.58> has quit IRC (Ping timeout: 245 seconds)20:07
vmesonfor your amusement, my build  of world_on_ a RPi4  of a  recentish poky repo is ~ 80% done.  It's only slightly slower than the YP autobuilder's arm64 builders.20:28
RPvmeson: so we should replace the autobuilder with a cluster of RPi4s ?20:31
vmesonRP - heh, let me finish the build and see how the selftests go! ;-)20:33
*** florian <florian!~florian@dynamic-078-048-070-254.78.48.pool.telefonica.de> has joined #yocto20:35
JaMavmeson: did you start that build when RPi4 was initially launched? :)20:54
ant__RP: hi, I must have missed it, on ubuntu 18.4 bitbake spits21:16
ant__  return f(*args, **kwds)21:16
ant__ /usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__21:17
ant__ return f(*args, **kwds)21:17
ant__then loads the cache and runs fine21:17
RPant__: we know, its python itself, not bitbake21:17
ant__ok, thx21:17
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)21:19
*** Xagen <Xagen!~Xagen@2600:1700:211:7e60:bd26:5fca:78f3:add1> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)21:19
ant__btw I have converted today  IMAGE_FSTYPES:collie21:20
ant__:)21:21
*** artri <artri!~artri@208.116.134.46> has joined #yocto21:42
artriGood evening folks. I have a customised dunfell image on a device and ifup (busybox really) refuses to bring up any ifs listed in /etc/network/interfaces. It won't even print an error. Anyone has seen this behavior before? Any help is appreciated21:44
*** florian <florian!~florian@dynamic-078-048-070-254.78.48.pool.telefonica.de> has quit IRC (Ping timeout: 245 seconds)21:52
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has quit IRC (Quit: Leaving.)21:54
RPJPEW: is there an easy way to check what a hash is resolving to from the commandline?22:06
JPEWIt's been so long I do not remember22:07
RPJPEW: fair enough, I'm sure I can hack something up22:08
RPJPEW: I'm puzzling about why the autobuilder has built gcc:do_populate_lic for qemux86-64 yet builds pointing at the hashequiv server and sstate are building it22:11
RPon the autobuilder I see DEBUG: Task 6259ae8263bd94d454c086f501c37e64c4e83cae806902ca95b4ab513546b273 unihash changed 3bde230c743fc45ab61a065d7a1815fbfa01c4740e4c895af2eb8dc0f684a4ab -> 6259ae8263bd94d454c086f501c37e64c4e83cae806902ca95b4ab513546b273 by server typhoon.yocto.io:868622:11
RPso the server changes unihash back to taskhash which seems confused22:11
JPEWYa. There is a command line hashserver client, but I forget what it can do22:12
JPEWIt would probably be useful to have something that can do more advanced queries for debugging22:13
*** goliath <goliath!~goliath@user/goliath> has joined #yocto22:27
RPJPEW: its some kind of weird circular reference. WARNING: Found unihash 3bde230c743fc45ab61a065d7a1815fbfa01c4740e4c895af2eb8dc0f684a4ab in place of 6259ae8263bd94d454c086f501c37e64c4e83cae806902ca95b4ab513546b273 for /home/rpurdie/poky/meta/recipes-devtools/gcc/gcc_11.2.bb:do_populate_lic from unix:///home/rpurdie/poky/build/hashserve.sock22:34
RPJPEW: then later it reports the outhash and gets back the original hash it started with22:34
RPJPEW: rerunning the build always repeats the build of the thing though since the 3bde230c object is never created in sstate22:35
* RP will look more tomorrow, have a headache now :(22:39
*** dev1990 <dev1990!~dev@dynamic-78-8-51-35.ssp.dialog.net.pl> has quit IRC (Quit: Konversation terminated!)22:39
RPJPEW: I think the issue is that when we call report_unihash(), taskhash can a unihash we got back from the hashequiv server rather than the original taskhash22:48
JPEWRP that sounds like a problem22:58
RPJPEW: I'm not sure how/why/where that would happen23:04
* RP will look more tomorrow23:04
*** artri <artri!~artri@208.116.134.46> has quit IRC (Ping timeout: 245 seconds)23:08
*** sakoman <sakoman!~steve@rrcs-66-91-142-162.west.biz.rr.com> has joined #yocto23:23
*** florian <florian!~florian@78.48.70.254> has joined #yocto23:31
*** paulg <paulg!~paulg@24-212-228-244.cable.teksavvy.com> has quit IRC (Quit: Leaving)23:42
*** florian <florian!~florian@78.48.70.254> has quit IRC (Ping timeout: 245 seconds)23:47

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