Friday, 2022-01-28

*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 240 seconds)00:06
*** florian <florian!> has quit IRC (Ping timeout: 250 seconds)00:14
*** dev1990 <dev1990!~dev@> has quit IRC (Quit: Konversation terminated!)01:08
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)01:27
*** alicef_ <alicef_!~none@gentoo/developer/alicef> has joined #yocto02:02
*** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Ping timeout: 240 seconds)02:03
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has quit IRC (Ping timeout: 256 seconds)02:06
*** alicef_ <alicef_!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)02:08
*** alicef <alicef!~none@gentoo/developer/alicef> has joined #yocto02:09
*** r0bin <r0bin!~r0bin@gateway/tor-sasl/r0bin> has joined #yocto02:10
*** fevi <fevi!> has joined #yocto02:10
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has joined #yocto02:13
*** fevi <fevi!> has quit IRC (Remote host closed the connection)02:18
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has quit IRC (Ping timeout: 240 seconds)02:32
*** creich_ <creich_!> has joined #yocto02:33
*** creich <creich!> has quit IRC (Ping timeout: 250 seconds)02:34
*** fevi <fevi!> has joined #yocto02:37
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has joined #yocto02:39
*** r0bin <r0bin!~r0bin@gateway/tor-sasl/r0bin> has quit IRC (Remote host closed the connection)02:53
*** r0bin <r0bin!~r0bin@gateway/tor-sasl/r0bin> has joined #yocto02:55
*** r0bin <r0bin!~r0bin@gateway/tor-sasl/r0bin> has quit IRC (Quit: WeeChat 2.8)03:01
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)03:12
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto03:13
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto03:39
*** coldspark29 <coldspark29!~claussenj@2a04:4540:6505:f700:d8b:8871:2d5d:e831> has quit IRC (Ping timeout: 260 seconds)03:42
*** coldspark29 <coldspark29!~claussenj@2a04:4540:6530:2000:e1ab:5b9:3251:4a79> has joined #yocto03:42
*** amitk <amitk!~amit@> has joined #yocto03:55
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)04:24
*** dti <dti!~dtometzki@fedora/dtometzki> has quit IRC (Quit: ZNC 1.8.2 -
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto04:55
*** geoffhp <geoffhp!> has quit IRC (Quit: Leaving)05:42
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)05:47
*** pnxs_ <pnxs_!> has joined #yocto05:58
*** Dracos-Carazza_ <Dracos-Carazza_!~Dracos-Ca@> has joined #yocto05:58
*** mischief1 <mischief1!> has joined #yocto06:00
*** opello <opello!~opello@about/csharp/opello> has joined #yocto06:00
*** xantoz_ <xantoz_!> has joined #yocto06:02
*** neverpan1c <neverpan1c!> has joined #yocto06:02
*** davidinux <davidinux!~davidinux@> has joined #yocto06:05
*** zeddiii <zeddiii!> has joined #yocto06:05
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has quit IRC (*.net *.split)06:07
*** amitk <amitk!~amit@> has quit IRC (*.net *.split)06:07
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has quit IRC (*.net *.split)06:07
*** fevi <fevi!> has quit IRC (*.net *.split)06:07
*** paulg <paulg!> has quit IRC (*.net *.split)06:07
*** grma <grma!~gruberm@> has quit IRC (*.net *.split)06:07
*** fitzsim <fitzsim!> has quit IRC (*.net *.split)06:07
*** zeddii <zeddii!> has quit IRC (*.net *.split)06:07
*** xantoz <xantoz!> has quit IRC (*.net *.split)06:07
*** dkl_ <dkl_!> has quit IRC (*.net *.split)06:07
*** ardo <ardo!> has quit IRC (*.net *.split)06:07
*** pnxs <pnxs!> has quit IRC (*.net *.split)06:07
*** LetoThe2nd <LetoThe2nd!> has quit IRC (*.net *.split)06:07
*** bunk <bunk!~bunk@debian/bunk> has quit IRC (*.net *.split)06:07
*** alejandrohs <alejandrohs!~alejandro@user/alejandrohs> has quit IRC (*.net *.split)06:07
*** neverpanic <neverpanic!> has quit IRC (*.net *.split)06:07
*** Saur <Saur!> has quit IRC (*.net *.split)06:07
*** lexano <lexano!~lexano@> has quit IRC (*.net *.split)06:07
*** xperia64 <xperia64!> has quit IRC (*.net *.split)06:07
*** opello_ <opello_!> has quit IRC (*.net *.split)06:07
*** mischief <mischief!> has quit IRC (*.net *.split)06:07
*** Piraty <Piraty!~irc@user/piraty> has quit IRC (*.net *.split)06:07
*** ldericher <ldericher!> has quit IRC (*.net *.split)06:07
*** MWelchUK <MWelchUK!> has quit IRC (*.net *.split)06:07
*** sgw <sgw!~swold_loc@user/sgw> has quit IRC (*.net *.split)06:07
*** amitk <amitk!~amit@> has joined #yocto06:12
*** alejandrohs <alejandrohs!~alejandro@> has joined #yocto06:12
*** dtometzki <dtometzki!~dtometzki@fedora/dtometzki> has joined #yocto06:12
*** fevi <fevi!> has joined #yocto06:12
*** dkl_ <dkl_!> has joined #yocto06:12
*** ardo <ardo!> has joined #yocto06:12
*** LetoThe2nd <LetoThe2nd!> has joined #yocto06:12
*** xperia64 <xperia64!> has joined #yocto06:12
*** Piraty <Piraty!~irc@user/piraty> has joined #yocto06:12
*** ldericher <ldericher!> has joined #yocto06:12
*** MWelchUK <MWelchUK!> has joined #yocto06:12
*** sgw <sgw!~swold_loc@user/sgw> has joined #yocto06:12
*** lexano <lexano!~lexano@> has joined #yocto06:13
*** paulg <paulg!> has joined #yocto06:14
*** bunk <bunk!~bunk@debian/bunk> has joined #yocto06:14
*** Saur <Saur!> has joined #yocto06:16
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 276 seconds)06:28
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)06:33
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto06:38
*** geoffhp <geoffhp!> has joined #yocto06:42
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:59
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Client Quit)07:01
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)07:04
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto07:05
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto07:06
*** rob_w <rob_w!> has joined #yocto07:06
*** pgowda_ <pgowda_!> has joined #yocto07:10
*** creich_ <creich_!> has quit IRC (Quit: Leaving)07:10
*** creich <creich!> has joined #yocto07:11
*** Schlumpf <Schlumpf!> has joined #yocto07:18
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 245 seconds)07:20
*** smsm <smsm!> has joined #yocto07:25
smsmIs there a recommended book to read to understand the philosophy and design of Yocto ?07:25
*** lucaceresoli_ <lucaceresoli_!~lucaceres@> has joined #yocto07:30
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto07:31
*** mischief1 is now known as mischief07:33
*** mckoan|away is now known as mckoan07:39
mckoangood morning07:39
mckoansmsm: but my favourite remains "Embedded Linux Systems With the Yocto Project" by  Rudolf J. Streif07:41
mckoansmsm: I wonder why is no longer listed in the YP page07:41
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)07:43
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto07:49
smsmmckoan thank you:)07:51
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 250 seconds)07:55
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto07:58
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto07:59
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)08:01
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto08:03
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)08:09
*** lucaceresoli_ <lucaceresoli_!~lucaceres@> has quit IRC (Quit: Leaving)08:11
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto08:11
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 260 seconds)08:16
*** grma <grma!~gruberm@> has joined #yocto08:21
*** mvlad <mvlad!~mvlad@2a02:2f08:4311:5500:24d7:51ff:fed6:906d> has joined #yocto08:32
*** rfuentess <rfuentess!> has joined #yocto08:35
*** dvorkindmitry <dvorkindmitry!~dv@> has joined #yocto08:36
*** dev1990 <dev1990!~dev@> has joined #yocto08:37
dvorkindmitryI always see this problem if trying to generate SDK a day after the image started to build from scratch: Locale is installed only at first dir:
*** rfuentess_ <rfuentess_!> has joined #yocto08:40
*** Austriker <Austriker!> has joined #yocto08:42
*** rfuentess <rfuentess!> has quit IRC (Ping timeout: 250 seconds)08:43
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto08:43
AustrikerHi, I am having trouble setting up X11 client on my headless device. I had it working before by adding X11 to EXTRA_IMAGE_FEATURES += "x11". but this had a side effect. The xserver-nodm kept crashing so it was eating up some ressources. I still have X11 in my DISTRO_FEATURES but when I ssh -XY to the device I get `X11 forwarding request failed on08:48
Austrikerchannel 0`. What is the correct way to get X11 forwarding working without xserver-nodm for example. I have a an app that requires a GUI for configuration.08:48
*** rfuentess__ <rfuentess__!> has joined #yocto08:53
*** rfuentess_ <rfuentess_!> has quit IRC (Ping timeout: 250 seconds)08:55
*** d0ku <d0ku!> has joined #yocto09:04
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer)09:04
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto09:06
*** smsm <smsm!> has quit IRC (Ping timeout: 256 seconds)09:09
erbo_Austriker: Is X11 forwarding enabled in sshd_config, and xauth installed?09:19
erbo_There's also an option for xauth location in sshd_config that might be worth setting, XAuthLocation09:20
Austrikererbo_ yes X11 forwarding is enabled but xauth is not installed.09:22
erbo_Austriker: I'm by no means an X11 forwarding expert, but I think you need xauth on the server side09:23
*** rfuentess_ <rfuentess_!> has joined #yocto09:25
michalkotylaHi everyone. I try to disable serial in debug version of my image recipes. I tried to do this with executing systemctl --root=${IMAGE_ROOTFS} disable serial-getty@.service; but it cause an error: systemctl: error: argument command: invalid choice: 'disable' (choose from 'enable', 'mask', 'preset-all')09:25
michalkotylaDo you have any ideas how to do it in different way? i do not want to mask service, only disable09:25
Austrikererbo_ I am building a new image with xauth and the changes in the settings. I hope this will solve the issue.09:26
*** rfuentess__ <rfuentess__!> has quit IRC (Ping timeout: 250 seconds)09:27
*** rfuentess <rfuentess!~rfuentess@2a01:cb14:87e:2200:20bd:7577:dcbe:65ec> has joined #yocto09:27
*** rfuentess_ <rfuentess_!> has quit IRC (Ping timeout: 252 seconds)09:29
*** argonautx <argonautx!> has joined #yocto09:30
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)09:34
*** florian <florian!> has joined #yocto09:37
erbo_michalkotyla: I guess it's systemd-serialgetty that adds entries in /etc/systemd/system/ for all entries in SERIAL_CONSOLES09:38
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto09:40
erbo_So you could remove those entries manually in a rootfs post process command if you only want it done for a certain image. But maybe a more elegant solution would be bbappend the systemd-serialgetty recipe and split /etc/systemd/system/* into a separate package and only install that in images where you want it auto-enabled.09:41
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 240 seconds)09:48
michalkotylamaybe, i will try with it - thanks09:48
*** tnovotny <tnovotny!> has joined #yocto09:55
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto10:03
*** Austriker <Austriker!> has quit IRC (Quit: Client closed)10:16
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto10:25
*** rfuentess_ <rfuentess_!> has joined #yocto10:26
*** rfuentess <rfuentess!~rfuentess@2a01:cb14:87e:2200:20bd:7577:dcbe:65ec> has quit IRC (Ping timeout: 252 seconds)10:28
*** Herrie <Herrie!> has quit IRC (Ping timeout: 260 seconds)10:35
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto10:39
*** rfuentess__ <rfuentess__!~rfuentess@2a01:cb14:87e:2200:20bd:7577:dcbe:65ec> has joined #yocto10:46
*** rfuentess_ <rfuentess_!> has quit IRC (Ping timeout: 250 seconds)10:48
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 245 seconds)10:50
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:52
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto10:57
kanavinRP: maybe but I do wonder what are those specific products that can be only supported with directfb10:59
kanavin(and I mean something that's not too old)10:59
*** rfuentess__ <rfuentess__!~rfuentess@2a01:cb14:87e:2200:20bd:7577:dcbe:65ec> has quit IRC (Remote host closed the connection)10:59
*** rob_w <rob_w!> has quit IRC (Remote host closed the connection)11:10
rburtondunfell kernel build failing with ld: scripts/dtc/ multiple definition of `yylloc'; scripts/dtc/dtc-lexer.lex.o:(.bss+0x38): first defined here11:10
rburtonspider-sense kicking off but i can't remember the fix11:11
rburtonzeddiii: can you backport e33a814e772cdc36436c8c188d8c42d019fda639 to the11:14
rburtonyeah just found it11:14
rburtonzeddiii: can you backport e33a814e772cdc36436c8c188d8c42d019fda639 to the 5.3 kernel in dunfell11:14
rburtonoh hang on that's our recipe11:15
rburtonso why did it break overnight11:15
rburtonaaah new host11:16
rburtonmystery over11:16
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 252 seconds)11:17
rburtonzeddiii: stand down, my fault :)11:17
qschulzrburton: also.. 5.3 :p ?11:21
rburtonyeah, don't ask11:22
rburtoni spent a week writing a tool to turn a layer into a report for project managers which has bright red annotations for non-upstreamed patches and old releases :)11:22
qschulzrburton: hehe11:23
qschulzswitching to 5.4 shouldn't be that big of a task though11:24
coldspark29[m]Is there a way to just generate a toolchain for C? `bitbake -c populate-sdk image` builds everything and I don't need that11:25
coldspark29[m]Would it maybe just build the toolchain for the kernel if I put `bitbake -c populate-sdk linux-imx`?11:26
rburtonbitbake meta-toolchain builds just the compilers and a few tools11:26
coldspark29[m]rburton: Looks pretty similar to me though11:29
RPJPEW: The more I look at this reproducibility issue, the more worried I get :(11:29
rburtoncoldspark29[m]: copy the meta-toolchain recipe and remove stuff you don't need then11:35
coldspark29[m]It inherits populate_sdk :D11:39
rburtonthats because the sdk code is common11:40
rburtonmeta-toolchain is the compiler, binutils, and a few tools.11:40
coldspark29[m]I will leave it now11:41
coldspark29[m]Hoping it finishes building soon11:41
coldspark29[m]Thanks anyway11:41
kanavinI just clicked stop on something I shouldn't have11:45
kanavinon the AB11:45
kanavinand I promised not to do it :(11:45
RPkanavin: highlighting the issue so we can debug it would be better :/12:14
svuorelahmm.. looks like my environment setup file for my sdk has gotten -O2 -D_FORTIFY_SOURCE=2 in the CC/CPP/CXX environment variables - given that I during usage of my sdk sometimes want a -O0 build, this is obviously not what I want. What should I look for to find the cause ?12:21
RPIn the problem reproducible build, do_package and do_package_write_deb came from sstate, write_ipk and write_rpm did not. The trouble is the binaries in do_package don't match the binaries in do_package_write_deb :(12:27
*** rfuentess <rfuentess!> has joined #yocto12:29
*** davidinux <davidinux!~davidinux@> has quit IRC (Quit: WeeChat 2.8)12:36
svuorelahmm. even more. a 3rd of my custom recipes contains TARGET_CC_ARCH += "${LDFLAGS}"12:38
svuorela - is that right ?12:38
rburtonthat's basically working around the makefiles or whatever not respecting LDFLAGS12:40
svuorelaok. I wonder if that leaks stuff into my environment setup file ?12:41
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto12:44
*** ardo <ardo!> has quit IRC (Read error: Connection reset by peer)13:14
SaurRP: I started digging a small hole yesterday (to remove \n from mirror variables throughout poky, as I discussed with Michael on the lists), and I ended up with something the size of Grand Canyon. I hope you can help me and maybe throw me rope to get me out of here while saving some of the artefacts that I dug up...13:16
*** GillesM <GillesM!> has joined #yocto13:18
RPSaur: I can try and help!13:20
RPzeddiii: I hate to say this but the reproducibility issues are looking like they're triggered by kernel headers :(13:20
*** ardo <ardo!> has joined #yocto13:22
RPzeddiii: and the commit which "triggers" this is from abelloni :)13:23
RPabelloni: stop breaking things for us! :)13:23
SaurRP: Well, the \n changes were trivial enough, no problems there. However, since one of the changed files was, I made the mistake of thinking I should run bitbake-selftest. Turns I apparently haven't done that before (shame on me), which lead to that I first had to fix so that I can run it (we have global Git hooks that interfere with bitbake-selftest setting to a dummy value.13:24
RPWhat happens is that the above commit changes the line numbers for the pending and enabled variable declarations in the uapi rtc.h header. rtcwake.c in util linux embeds that info into the debug symbols in rtcwake. For some reason hashequiv isn't tracking this correctly13:25
SaurThat too wasn't too hard to fix. Then when I ran it, I first enabled BB_SKIP_NETTESTS since I'm behind a firewall, and realized that's probably something you don't do as it failed the crate tests. Easily fixed.13:25
*** kroon <kroon!> has joined #yocto13:25
RPSaur: I likely missed adding the skip network test on the crate tests when I added them. yes13:26
SaurThen I managed to configure the proxy settings so I could actually run all the tests. All looked great until it failed two npm tests related to premirror and that is when chaos started.13:26
RPSaur: the npm tests probably aren't being run anywhere at the moment :(13:26
SaurExactly, I kind of figured that out after having dug into for quite a while.13:26
RPSaur: sorry, they're on my "need to do something about it" list :(13:27
RPalong with many many other things :(13:27
SaurThe problem now is that I though I should fix them, but I am not really sure what the correct thing to do is, or what is the expected behaviour from the npm fetcher...13:27
moto_timo[m]That list never seems to get shorter does it13:28
RPSaur: we could never enable them on the autobuilder since they need npm from meta-oe. The plan was to figure out how to add that but somehow they bitrotted along the way13:28
RPI don't really know the node stuff well enough to know what the right fix is13:28
SaurLooking at the npm fetcher it uses the downloadfilename= parameter do specify the name of the npm packages it downloads. If you don't specify it yourself it will put the downloaded files in an "npm2" directory. However, if you actually do specify downloadfilename= to npm://, it will not do this and rather put them exactly as the downloadfilename= parameter specifies. This causes confusion if one takes the download directory and attempts t13:31
Sauro use it as a premirror as some npms are in npm2 and others are in the root.13:31
RPJPEW: the question now is how does a kernel header change defeat the hashequivalence mechanism for package_write_deb on util-linux :/13:32
RPSaur: I'd say it should use npm2 in all cases13:33
SaurTo me it makes much more sense to always put all downloaded npms in the npm2 directory, which is a trivial change. However, I do not know if there are any consequences of that which I do not realize...13:33
RPSaur: You'd hope that would just cause a few extra downloads for some users?13:34
SaurMore like if people have expectations of where the files end up when doing things such as taking the downloaded files a nd creating mirrors or so...13:35
SaurBut maybe there aren't that many users of the npm fetcher that that is a problem...13:36
RPSaur: copying DL_DIR would still work and yes, I doubt there are that many users so I think we should fix it13:36
RPWould be interesting to see if anyone does notice13:36
SaurI guess I'll just propose the change to the list and see if anyone objects.13:36
RPSaur: gets my vote FWIW :)13:37
RPWould be nice to have those tests fixed!13:37
SaurI have a fix for the first test so far.13:37
SaurAs for the second test, which I don't really understand what it's trying to test, it gets harder. And that's not really due to the npm part, but the fact that it sets a premirror like https?$://.*/.* file:///tmp/bitbake-fetch-s5wcbmf1/mirror/npm2/savoirfairelinux-node-server-example-1.0.0.tgz13:39
SaurThe problem is that after uri_replace() has had its go at it, the resulting URI ends up as /tmp/bitbake-fetch-s5wcbmf1/mirror/npm2/savoirfairelinux-savoirfairelinux-node-server-example-1.0.0.tgz, which it obviously will not find sine the URL should actually be /tmp/bitbake-fetch-s5wcbmf1/mirror/npm2/savoirfairelinux-node-server-example-1.0.0.tgz13:40
*** kroon <kroon!> has quit IRC (Quit: Leaving)13:41
SaurI believe this is a result of commit 96c30007dc0b32eee2b15771daec7948bc9bfd97 in the bitbake repository.13:42
SaurMore specifically the call to result_decoded[loc] = result_decoded[loc].replace(uri_basename, basename)13:42
SaurWhere, for the npm case uri_basename is node-server-example-1.0.0.tgz and basename is savoirfairelinux-node-server-example-1.0.0.tgz13:43
RPSaur: which test is this specifically?13:44
SaurI don't really see the point of the test in itself, but it did find this problem, which I believe is real.13:45
*** sakoman <sakoman!> has joined #yocto13:46
RPSaur: I don't really see what that test is meant to be doing either :/13:47
RPSaur: I was wondering if we need to go back to when these were added and see if we can bisect down which fetcher change broke them. Not sure if that is worth it and would tell us anything or not13:48
RPIt is what I was originally thinking of doing to track down the issues13:48
*** prabhakarlad <prabhakarlad!> has joined #yocto13:49
SaurThe first change is 8a3ff9f3eaf19d4258eb070c5dc230dface269b2 which tried to solve the problem where downloadfilename= is used together with a premirror. The tests were modified/added in 61db3e96530d650e098436fd086f0182d32998f7 and 5ba191a0407af9e652e3b86302dce3e952d6b587. Then the second try to fix it is in commit 96c30007dc0b32eee2b15771daec7948bc9bfd97, and that is when the tests got broken.13:52
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)13:56
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto13:56
JPEWRP: Do you have the depsig files by chance?13:57
zeddiiiRP: interesting ... so the fix will have to be in hashequiv ? or did you want me to poke at the headers or are we into another sorting utility ?14:00
*** florian_kc <florian_kc!> has joined #yocto14:05
*** fevi <fevi!> has quit IRC (Remote host closed the connection)14:06
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 256 seconds)14:12
*** florian_kc <florian_kc!> has joined #yocto14:13
*** fitzsim <fitzsim!> has joined #yocto14:24
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 250 seconds)14:26
*** davidinux <davidinux!~davidinux@> has joined #yocto14:28
*** smsm <smsm!> has joined #yocto14:30
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 256 seconds)14:32
*** GillesM <GillesM!> has quit IRC (Quit: Leaving)14:33
*** smsm <smsm!> has quit IRC (Ping timeout: 256 seconds)14:38
*** smsm <smsm!> has joined #yocto14:38
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto14:38
*** Dracos-Carazza_ is now known as Dracos-Carazza14:52
RPzeddiii: its a hashequiv issue, the kernel headers are just a trigger :/14:58
RPJPEW: I do not have all of what we need, no :/14:59
*** coldspark29 <coldspark29!~claussenj@2a04:4540:6530:2000:e1ab:5b9:3251:4a79> has quit IRC (Ping timeout: 268 seconds)15:01
JPEWRP: Fair enough. So the theory is that the kernel header line numbers are getting encoded in the debug data?15:04
JPEW... and somehow that changed between 2 runs of the reproducible build test?15:04
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto15:06
JPEWOr, the first build came from sstate, and hashequiv somehow "missed" that the output change and marked them as equivalent?15:06
*** smsm <smsm!> has quit IRC (Quit: Client closed)15:08
RPJPEW: The build that came from sstate had a do_package_setscene built with the new headers but a do_package_write_deb_setscene that was built with the old ones (or vice versa)15:12
RPFor reasons unknown, ipk/rpm rebuild and didn't come from sstate and packaged the do_package data which then didn't match the deb15:13
JPEWrpm and ipk didn't pull from sstate at all?15:17
JPEW(presumably, that's why the A build took so long?)15:18
RPJPEW: they rebuilt the rpm and ipk step from do_package15:19
RPJPEW: I don't know why :/15:19
SaurRP: After reading through, I now think I know what the problem with downloadfilename= and premirror is. Scotts expectation is that if you have a SRC_URI that asks for foo.tgz and downloads it as bar.tgz, it should still ask for foo.tgz when searching the premirror. And this is sane if you set the premirror to some external source which carries the same files as the origin server in t15:28
Saurhe URI. However, if you instead expect to use whatever you have downloaded in one build to serve as your local premirror for another build, then you expect bitbake to look for bar.tgz in the premirror as that is the name it will have when it lands in ${DL_DIR}.15:28
RPSaur: ah, yes. We would expect to be able to reuse a download as a premirror :/15:30
SaurRP: Both uses cases seem to valid. So the question then becomes, should bitbake look for both the downloadfilename and the original file when trying to locate a file?15:30
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 252 seconds)15:30
RPSaur: hmm, I can see both cases :/15:30
*** ar__ <ar__!~akiCA@user/akica> has joined #yocto15:31
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto15:33
*** codavi <codavi!~akiCA@user/akica> has joined #yocto15:36
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 252 seconds)15:36
*** ar__ <ar__!~akiCA@user/akica> has quit IRC (Ping timeout: 256 seconds)15:39
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)15:41
vdCan two distro using the same libc can share TMPDIR, or is it better to split them with e.g. TCLIBCAPPEND = "-${DISTRO}"?15:43
rburtonkhem: meta-oe is still broken with folks depending on mockdbus-native15:47
*** dev1990 <dev1990!~dev@> has quit IRC (Quit: Konversation terminated!)15:48
SaurRP: Is it possible to enable the logger messages that are produced while running bitbake-selftest some way? Currently I am adding print() statements as I go along to get it to output what is happening...15:49
smurrayvd: I believe sharing would be fine, though you'd likely need to be copying the deployed artifacts you need out after building each one if there's any overlap15:51
RPSaur: Offhand I don't remember how, I usually end up doing that too :(15:51
vdsmurray: true, because the deploy paths (e.g. DEPLOY_DIR_IMAGE) do not include ${DISTRO} by default15:52
vdsmurray: so DEPLOY_DIR:append = "/${BB_CURRENT_MC}" should be just enough in fact, keeping TMPDIR and TCLIBCAPPEND to their defaults15:53
smurrayvd: if you're using multiconfig and potentially building both at the same time it's perhaps better to fully split them with e.g. TMPDIR = "${TOPDIR}/tmp-${BB_CURRENT_MC}"15:56
smurrayvd: but it kind of depends on what's different in the distro configs.  I'm not sure significantly different distro configs that result in a bunch of package differences will play nicely wrt trying to build both rootfs-es at the same time if TMPDIR is shared15:58
*** Epictek[m] <Epictek[m]!~epictekma@2001:470:69fc:105::d7cd> has quit IRC (Quit: You have been kicked for being idle)16:00
*** mckoan is now known as mckoan|away16:00
vdsmurray: you're right. I just want to stick with a default and safe conf that I forget about. I'm adding a site.conf with DEPLOY_DIR:append = "/${BB_CURRENT_MC}", TMPDIR:append = "-${BB_CURRENT_MC}", TCLIBCAPPEND = "".16:03
smurrayvd: if you change TMPDIR you shouldn't need to also tweak DEPLOYDIR unless you've changed it to point outside of TMPDIR with some other tweak16:06
*** dvorkindmitry <dvorkindmitry!~dv@> has quit IRC (Quit: KVIrc 5.0.0 Aria
vdsmurray: correct, on my server I set DEPLOY_DIR = "/srv/http" for development16:07
smurrayvd: also note that for the main bitbake BB_CURRENT_MC = "default".  In my AGL setup I tweak TMPDIR in the multiconfig .conf's to have tmp, tmp-conf1, tmp-conf1.  But that's more of a style thing16:07
smurrayerr, tmp, tmp-conf1, tmp-conf216:08
smurrayneed to go make a coffee ;)16:08
RPvd: it all depends whether your distro configs match or not. If they don't, using the same TMPDIR for them in a multiconfig will not work16:08
vdRP: even if they do match, the cost of splitting them is just that a few files will be copied over, right? (like removing TMPDIR and starting a build again)16:10
*** d0ku <d0ku!> has quit IRC (Ping timeout: 256 seconds)16:14
RPvd: yes16:15
smurrayheh, in the one AGL demo build they decided they want Qt configured differently in 2 different multiconfigs, it's slow enough to build that that outweighs everything else ;)16:19
vdRP: how do you feel about a patch adding something like this to bitbake.conf: MCAPPEND ?= "${@'/' + d.getVar('BB_CURRENT_MC') if d.getVar('BB_CURRENT_MC') != 'default' else ''}" DEPLOY_DIR .= "${MCAPPEND}" TMPDIR .= "${MCAPPEND}"; to provide users a safe environment by default that they can tweak if their multiconfigs match, or do you prefer to keep it as it is today?16:22
LetoThe2ndwhom should I poke for wiki access? RP ndec michaelo16:27
qschulzhalstead: maybe too I think16:27
LetoThe2ndqschulz: ya right16:27
LetoThe2ndi tell ya folks, its only a couple of day until i'm finally back to annoy you all!16:28
qschulzLetoThe2nd: :muscle:16:28
RPLetoThe2nd: halstead16:29
qschulzwell, emoji fail16:29
vdsmurray: I feel the pain, qtwebengine actually convinced me to buy an AMD 5950X / 64Go RAM build machine...16:29
RPvd: I don't think we want to hardcoded multiconfig layouts like that into oe-core16:29
vdRP: I see. It's better to let one define this in their local/site/auto/mc configs I understand16:30
LetoThe2ndits really a strange feeling to wrap up 14 respectively 16 years at a company, with a full month of PTO.16:30
smurrayvd: I've got a Threadripper so it's somewhat manageable on the CPU front, atm memory is the issue, 64GB actually isn't enough for that config w/o cutting parallelism down a bunch.  I've got another 64GB sitting here that arrived from Newegg this week to put in ;)16:31
vdsmurray: while compiling qtbase/qtwebengine, htop goes to maximum 50Go RAM usage for me. Am I lucky?16:32
smurrayvd: it's building 2 copies of qtbase and qtdeclarative, etc. at the same time (one for each multiconfig) that blows up for me here.  64GB + 40GB swap wasn't enough16:33
RPJPEW: I think I see how this breaks. gcc-cross depends on linux-libc-headers and then all the target recipes depend on gcc-cross. The output of gcc-cross might not change when linux-libc-headers changes16:33
RPLetoThe2nd: I know what you mean, I felt odd leaving Intel16:34
vdsmurray: ha true you have to qt builds in parallel. At first I saw multiconfig as a nice way to split my build variants (customer branding etc.), but I learnt the hard way to keep as much as possible in a multiconfig and only use different ones for actual architecture variants.16:35
LetoThe2ndRP: yeah. and so many little things involved and surfacing now.16:35
smurrayvd: my original setup for this one AGL build had one mc for all the containers, but folks decided they want different configurations for each ¯\_(ツ)_/¯16:37
vdsmurray: I'm not in your shoes but I would definitely work hard towards convincing them to go back to a common qt config...16:39
smurrayvd: the people involved have said their next step is significantly different distro configs, so I've decided it's somewhat futile to push back16:41
smurrayvd: I assume they have better build hardware than I do ;)16:41
vdsmurray: if that ends up being two different distro, it actually makes sense yeah. The trap with multiconfigs is wishing to use them to split a common environment, that is definitely bad16:43
smurrayvd: it's somewhat debatable in this instance IMO, but I'll not bore you ;)16:46
vdsmurray: ha ha no worries, it's friday (whatever that means)16:47
*** GillesM <GillesM!> has joined #yocto16:56
*** GillesPP <GillesPP!> has joined #yocto16:56
SaurRP: Argh, I knew it wouldn't be as simple as just look for both the original name and the downloadfilename. My idea was to look for downloadfilename first as that is typically what would be in a local mirror, and then for the original name. However, what if someone specifies a URL like;downloadfilename=bitbake-1.0.tar.gz, i.e., where both files exists. In this case it i17:01
Saurs probably more expected that the original file is found first... I just can't win, can I?17:01
khemrburton:  the needed patch is staged in oe-core master-next17:02
rburtoni still maintain that needing dbus-mock-native is a bug in the build17:03
rburtonthe check is wrong, it needs *target* dbus-mock17:03
*** rfuentess <rfuentess!> has quit IRC (Remote host closed the connection)17:06
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)17:06
khemrburton: you need to prove it, I dont claim to be expert17:06
vdwhat is the preferred way to add a bootloader as a dependency for a WIC image? EXTRA_IMAGEDEPENDS += "virtual/bootloader", WKS_FILE_DEPENDS_BOOTLOADERS:${MACHINE} = "virtual/bootloader", do_image_wic[depends] += "virtual/bootloader:do_deploy"? The latter is quite intrusive17:09
khemjonmason: yt ?17:10
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)17:10
RPrburton: I thought that but didn't get to investigate17:10
RPSaur: that is rather problematic, yes :(17:10
SaurRP: I actually don't think the problem is solvable without making the two uses cases explicit, by either adding more URI parameters or, e.g., making a distinction between premirrors and mirrors, where premirrors would look for downloadfilename while mirrors would look for the original name. Either way would most likely break someone's use cases...17:12
RPSaur: we probably need to document this parameter behaving in a particular way I guess17:14
*** florian_kc <florian_kc!> has joined #yocto17:19
RPJPEW, abelloni: you can see what I mean if you grep for "pending", it refers to the field in the struct from rtc.h17:19
JPEWAh, do cross recipes need the same thing we did to native>17:20
JPEWAh, do cross recipes need the same thing we did to native?17:20
JPEWerg, can't edit lines in IRC :)17:21
RPJPEW: probably but in this case we have a target dependency on the libc headers as those are target, not cross17:21
RPand cross shouldn't hard depend on target17:21
RPJPEW: this effectively applies to any indirect dependency in the sysroot :/17:22
RPJPEW: recipe A installs header X, recipe B depends on A but doesn't use X, recipe C depends on recipe B, uses header X. Hash from A never makes it to C17:23
*** whuang0389 <whuang0389!> has joined #yocto17:41
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto17:48
*** Schlumpf <Schlumpf!> has quit IRC (Quit: Konversation terminated!)17:53
*** florian <florian!> has quit IRC (Quit: Ex-Chat)17:53
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 256 seconds)17:57
*** neverpan1c is now known as neverpanic18:00
*** prabhakarlad <prabhakarlad!> has joined #yocto18:02
*** pgowda_ <pgowda_!> has quit IRC (Quit: Connection closed for inactivity)18:05
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)18:27
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 256 seconds)18:35
*** whuang0389 <whuang0389!> has quit IRC (Quit: Client closed)18:39
JPEWRP: Hmm.... I'm not sure what we can do about that18:39
JPEWRP: Other than C should DEPEND On A18:41
*** mvlad <mvlad!~mvlad@2a02:2f08:4311:5500:24d7:51ff:fed6:906d> has quit IRC (Quit: Leaving)18:42
*** tlwoerner_ <tlwoerner_!> has joined #yocto18:53
*** Herrie <Herrie!> has joined #yocto18:54
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has quit IRC (Remote host closed the connection)18:55
*** bantu <bantu!> has quit IRC (Ping timeout: 256 seconds)18:55
*** zkrx <zkrx!> has quit IRC (Ping timeout: 256 seconds)18:55
*** tlwoerner <tlwoerner!> has quit IRC (Ping timeout: 256 seconds)18:55
*** rfried <rfried!> has quit IRC (Ping timeout: 256 seconds)18:55
*** bantu <bantu!> has joined #yocto18:55
*** rfried <rfried!> has joined #yocto18:56
*** zkrx <zkrx!> has joined #yocto18:57
*** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has joined #yocto18:58
*** argonautx <argonautx!> has quit IRC (Quit: Leaving)19:04
*** florian_kc <florian_kc!> has joined #yocto19:20
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto19:21
*** coldspark29 <coldspark29!~claussenj@2a04:4540:6530:2000:d9b7:bcd6:6a60:71a7> has joined #yocto19:56
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC (Ping timeout: 250 seconds)20:13
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 240 seconds)20:31
*** alejandrohs <alejandrohs!~alejandro@> has quit IRC (Quit: WeeChat 3.3)20:31
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto20:55
*** GillesM <GillesM!> has quit IRC (Quit: Leaving)21:07
*** GillesPP <GillesPP!> has quit IRC (Quit: Leaving)21:07
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)21:41
vdif you want to version your site.conf and auto.conf to share them between co-workers, do you ususally version build/conf/ or do you create a layer to store them?22:01
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)22:03
vdsmurray: actually regarding this ^ how do you version/share your multiconfigs if I may ask?22:04
smurrayvd: in AGL they're checked into the conf/multiconfig directory in the associated layer22:05
*** kernelspace is now known as ad__22:06
*** florian_kc <florian_kc!> has joined #yocto22:11
vdsmurray: yep ok so the best is to put that in a layer. Public or a custom one, if private. Thank you!22:12
vdI often thought about one having a "build" layer for each project, it kinda makes sense.22:13
smurrayvd: in AGL there are specific images and some recipes associated with the multiconfig setup, so it's all been placed its own layer22:15
vdit's definitely cleaner for storing customer specifics recipes, multiconfigs, common site configs, etc. for sure22:16
smurrayvd: with something like kas, you could potentially rely on the conf's being generated from the yaml config file, and just track changes by checking it in somewhere22:19
vdsmurray: yeah I'm using kas, mainly for fetching/patching the repos, but I'm not a fan of tools which abstract too much other tools like bitbake22:20
smurrayvd: yeah, it can potentially be fun to debug when things break22:21
vdkas kinda incites you to store your config in yaml fragments, while you could have a pure bitbake config with multiconfig/site/auto etc., which I prefer22:21
smurraykas or something like the scripting that AGL does to generate bblayers.conf/local.conf kicks in when you have an array of users who want to build with different BSPs or other options22:22
vdsmurray: I'm moving towards having only "repos:" stated in the kas yaml config, and use a script to wrap './kas-container shell project.yml -c "bitbake $@"'22:22
smurrayit can be hard to juggle making that work in one massive build configuration22:23
vdsmurray: totally agree. Especially when you need that patch in meta-openembedded, this patch in oe-core, etc. Kas is wonderful for that. I just wish it was less intrusive and could simply be scoped to only generating the bblayers.conf for the yaml file.22:24
vdActually I started the conversation with kergoth to implement layer fetching via bitbake recipes, since it already provides a fetcher, dependency management, preferred version, etc. But it didn't go anywhere22:25
vdI'm wondering if that can be an option.22:26
smurrayit gets discussed now and again. IMO it's sort of a hard problem because different people want different things, scoping "good enough" isn't easy22:26
SaurWell, you have a bit of chicken and egg problem if you want to use bitbake to fetch the layers, as you need bitbake and the layer that defines the other layers before you can have it fetch the others...22:28
vdsmurray: via SRC_URI you can fetch a layer from anywhere really, and DEPENDS could be used as well. It's sad to see this mechanism not used for the layer themselves :)22:28
smurrayvd: as Saur says, there's some chicken and egg issues22:29
vdSaur: true. Maybe the only assumption is that 'bitbake' is in $PATH. All you'd need would be a 'bitbake' Docker image for example, if you don't have bitbake locally.22:30
SaurWell you also need to be able to tell it what to fetch, which would be a layer in itself because that is what bitbake knows about, which means you need some way to get that layer...22:31
vdSaur: similarly to how bitbake currently assumes paths for bitbake.conf and bblayers.conf, it can assume a fixed path where to find layer recipes22:32
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Quit: Leaving)22:39
abelloniRP: what did I break ? :)22:40
abelloniRP: you don't like new ioctls ? ;)22:40
abelloniRP: actually, I'm serious, I don't see how I would have done otherwise22:43
*** sakoman <sakoman!> has joined #yocto22:43
abelloniI would actually expect something like this one to break reproducibility:
abellonibut not the other one22:44
*** dmoseley <dmoseley!~dmoseley@> has quit IRC (Ping timeout: 240 seconds)23:24
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto23:24
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 250 seconds)23:41

Generated by 2.17.2 by Marius Gedminas - find it at!