Tuesday, 2022-02-08

*** florian_kc <florian_kc!~florian@dynamic-093-132-028-099.93.132.pool.telefonica.de> has quit IRC (Ping timeout: 256 seconds)00:06
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)00:23
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 256 seconds)00:28
*** camus <camus!~Instantbi@> has joined #yocto00:29
*** dev1990 <dev1990!~dev@dynamic-78-8-66-141.ssp.dialog.net.pl> has quit IRC (Quit: Konversation terminated!)00:55
*** dev1990 <dev1990!~dev@dynamic-78-8-66-141.ssp.dialog.net.pl> has joined #yocto00:56
*** olani <olani!~olani@> has quit IRC (Ping timeout: 256 seconds)00:56
*** olani <olani!~olani@> has joined #yocto00:57
*** dev1990 <dev1990!~dev@dynamic-78-8-66-141.ssp.dialog.net.pl> has quit IRC (Client Quit)00:59
*** codavi <codavi!~akiCA@user/akica> has quit IRC (Ping timeout: 256 seconds)01:24
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)01:56
*** JPEW <JPEW!sid500061@helmsley.irccloud.com> has quit IRC (Read error: Connection reset by peer)02:02
*** JPEW <JPEW!sid500061@> has joined #yocto02:02
*** Guest59 <Guest59!~Guest59@d154-5-124-172.bchsia.telus.net> has joined #yocto02:06
*** Guest59 <Guest59!~Guest59@d154-5-124-172.bchsia.telus.net> has quit IRC (Client Quit)02:07
*** rber|res <rber|res!~rber|res@> has joined #yocto02:32
*** RobertBerger <RobertBerger!~rber|res@> has quit IRC (Ping timeout: 256 seconds)02:34
*** amitk <amitk!~amit@> has joined #yocto04:02
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 276 seconds)04:37
*** ekathva <ekathva!~ekathva@2001:999:50:cab1:59c2:628d:2b45:2b24> has joined #yocto04:57
*** rsalveti <rsalveti!uid117878@id-117878.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)05:17
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto05:36
*** lowfi <lowfi!~lowfi@user/lowfi> has joined #yocto05:51
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:12
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto06:12
*** Saur <Saur!~pkj@proxy01.se.axis.com> has joined #yocto06:12
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:14
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)06:20
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:20
*** lowfi <lowfi!~lowfi@user/lowfi> has quit IRC (Quit: Leaving)06:20
*** m4ho <m4ho!~m4ho@p5098be52.dip0.t-ipconnect.de> has joined #yocto06:25
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)06:25
*** camus1 <camus1!~Instantbi@> has joined #yocto06:30
*** camus <camus!~Instantbi@> has quit IRC (Remote host closed the connection)06:31
*** camus1 is now known as camus06:31
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)06:32
*** ad__ <ad__!~heisenbug@user/ad/x-9056428> has quit IRC (Quit: ZNC 1.7.2+deb3~bpo9+1 - https://znc.in)07:28
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has joined #yocto07:28
*** goliath <goliath!~goliath@user/goliath> has joined #yocto07:32
*** frieder <frieder!~frieder@mue-88-130-73-056.dsl.tropolys.de> has joined #yocto07:36
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has joined #yocto07:37
LetoThe2ndyo dudX07:39
LetoThe2ndRP: rburton: discuss https://twitter.com/rik_ferguson/status/1490639767675019272?s=21 (I might need to adjust my behaviour toward you :P )07:40
*** mckoan|away is now known as mckoan07:44
mckoangood morning07:44
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:ec13:1027:6819:6645> has quit IRC (Quit: vladest)07:46
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:382:4feb:a43:f44d> has joined #yocto07:49
LetoThe2ndyo mckoan07:53
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has joined #yocto07:57
*** zpfvo <zpfvo!~fvo@> has joined #yocto07:57
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto08:06
qschulzmornin folks08:06
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 252 seconds)08:06
*** zpfvo <zpfvo!~fvo@> has joined #yocto08:07
*** ekathva_ <ekathva_!~ekathva@2001:999:50:cab1:cb06:9935:dc:f7e7> has joined #yocto08:17
*** ekathva <ekathva!~ekathva@2001:999:50:cab1:59c2:628d:2b45:2b24> has quit IRC (Ping timeout: 250 seconds)08:19
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has quit IRC (Quit: ZNC 1.7.2+deb3~bpo9+1 - https://znc.in)08:22
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has joined #yocto08:22
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto08:23
*** DasChaos[m] <DasChaos[m]!~daschaosm@2001:470:69fc:105::403> has joined #yocto08:24
*** dev1990 <dev1990!~dev@dynamic-78-8-66-141.ssp.dialog.net.pl> has joined #yocto08:25
*** rob_w <rob_w!~rob@2001:a61:6050:d201:91c6:ab22:3d0a:4dde> has joined #yocto08:30
RPLetoThe2nd: seems fairly accurate :)08:31
LetoThe2ndRP: hehehe08:32
RPLetoThe2nd: I was temped to start that "with the greatest respect," .... :)08:33
LetoThe2ndRP: I actually looked up the list if it stated "fairly accurate"08:33
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 250 seconds)08:35
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has quit IRC (Quit: ZNC 1.7.2+deb3~bpo9+1 - https://znc.in)08:36
*** zpfvo <zpfvo!~fvo@> has joined #yocto08:36
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has joined #yocto08:36
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 260 seconds)08:41
*** zpfvo <zpfvo!~fvo@> has joined #yocto08:41
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Quit: Leaving)08:44
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has quit IRC (Quit: ZNC 1.7.2+deb3~bpo9+1 - https://znc.in)08:45
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has joined #yocto08:45
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)08:55
*** zpfvo <zpfvo!~fvo@> has joined #yocto08:56
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto08:56
*** jqua[m] <jqua[m]!~quaresmam@2001:470:69fc:105::1:2faa> has quit IRC (Quit: You have been kicked for being idle)09:00
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:05
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)09:05
*** zpfvo <zpfvo!~fvo@> has joined #yocto09:06
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto09:12
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Remote host closed the connection)09:22
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto09:24
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:382:4feb:a43:f44d> has quit IRC (Remote host closed the connection)09:33
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:48d0:f33e:409d:9b16> has joined #yocto09:34
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has quit IRC (Quit: ZNC 1.7.2+deb3~bpo9+1 - https://znc.in)09:34
*** ad__ <ad__!~heisenbug@mail.kernel-space.org> has joined #yocto09:35
*** ad__ <ad__!~heisenbug@mail.kernel-space.org> has quit IRC (Client Quit)09:38
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has joined #yocto09:39
SchlumpfHi, what is the root path of the yocto patch mechanism? I have to set a relative path in the .patch file to find the file to patch, but it doesn't find it09:41
LetoThe2ndSchlumpf: i would guess ${S}?09:43
qschulzSchlumpf: https://docs.yoctoproject.org/ref-manual/variables.html#term-SRC_URI09:45
qschulzpatchdir defaults to S09:45
qschulzSchlumpf: but even better way to deal with this, is to use devtool modify, then commit the change in the devtool workspace for this recipe and then devtool finish or something like that09:46
qschulz(I never update recipes with devtool, only modify them and then handle the patching process myself...)09:46
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has quit IRC (Quit: ZNC 1.7.2+deb3~bpo9+1 - https://znc.in)09:50
*** ad__ <ad__!~heisenbug@2a01:4f8:c2c:5a84::1> has joined #yocto09:51
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Ping timeout: 256 seconds)09:54
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto10:04
rburtonLetoThe2nd: that is 100% accurate fwiw10:05
LetoThe2ndrburton: hrhr10:05
SchlumpfletoThe2nd: qschulz: I thought that, too. And that seems to be correct. I dumped the PWD in do_patch(). But it still doesn't find the file...10:08
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has joined #yocto10:10
ad__gm, in dunfell, trying to produce sdk i get: nothing provides nativesdk-perl needed by nativesdk-autoconf-2.69-r11.x86_64-nativesdk10:21
ad__am i missing some layer for it ?10:21
*** ZygmuntKrynicki[ is now known as zyga[m]10:26
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 240 seconds)10:30
*** argonautx <argonautx!~argonautx@i5E8670F2.versanet.de> has joined #yocto10:30
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto10:30
*** zpfvo <zpfvo!~fvo@> has joined #yocto10:30
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 252 seconds)10:37
*** zpfvo <zpfvo!~fvo@> has joined #yocto10:37
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 276 seconds)10:52
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto10:53
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto11:06
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)11:07
*** zpfvo <zpfvo!~fvo@> has joined #yocto11:07
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)11:12
*** zpfvo <zpfvo!~fvo@> has joined #yocto11:12
*** Circuitsoft <Circuitsoft!uid393878@id-393878.lymington.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)11:17
agherzanRP: there is no way I can reproduce this pseudo race issue. Is there any chance I can pick up the pseudo dbs from the autobuilder?11:51
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Ping timeout: 256 seconds)12:17
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Quit: Leaving)12:27
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)12:35
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto12:35
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 252 seconds)12:36
*** zpfvo <zpfvo!~fvo@> has joined #yocto12:37
*** ilunev <ilunev!~koolkhel@2a00:8740:2c:5ca1:f01b:7979:958b:b1ef> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)12:59
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)13:01
*** zpfvo <zpfvo!~fvo@> has joined #yocto13:02
*** jatedev <jatedev!~jatedev@> has quit IRC (Ping timeout: 256 seconds)13:06
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)13:13
RPagherzan: since this happened a while ago, I think it is unlikely now. I can't remember if we were able to save any of that builddir :/13:17
agherzanRP: could it be that we just fixed it inadvertently? It's just that not seeing anything suspicions in either the tasks code nor in the pseudo command checks, could imply that.13:28
RPagherzan: I guess something like https://git.yoctoproject.org/pseudo/commit/?h=oe-core&id=d03de55845edf68908879db841834584d4724c43 maybe? when was this issue previously?13:31
agherzanRP: the build logs are from 7 months ago13:33
agherzanSo it would have included this fix too13:33
RPagherzan: that is what I thought :/13:34
RPagherzan: I wonder if this was with glibc 2.34 ?13:36
agherzanRP: No, 2.3313:38
*** smsm <smsm!~smsm@eth1-fw1-nbg6.eb.noris.de> has joined #yocto13:40
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)13:41
*** zpfvo <zpfvo!~fvo@> has joined #yocto13:42
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)13:51
*** zpfvo <zpfvo!~fvo@> has joined #yocto13:52
RPagherzan: which rules out some of the other pseudo changes13:54
RPagherzan: I was looking over https://git.yoctoproject.org/pseudo/log/?h=oe-core13:54
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:54
DasChaos[m]Hello guys,... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/24e48d28ef96df8ca9be1d6bf9ab9783ee20c0b2)13:55
RPagherzan: it is possible some of the changes there could have let something slip through and cause an issue :/13:56
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c29d:d7c0::f824> has quit IRC (Quit: Leaving)14:01
*** tperrot_ <tperrot_!~tprrt@shells.bootlin.com> has quit IRC (Quit: leaving)14:08
*** tgamblin <tgamblin!~tgamblin@2607:fea8:c29d:d7c0::f824> has joined #yocto14:08
*** tprrt <tprrt!~tprrt@shells.bootlin.com> has joined #yocto14:08
*** tprrt is now known as tperrot14:08
*** goliath <goliath!~goliath@user/goliath> has joined #yocto14:10
rburtonRP: sent a oeqa addition to build newlib as part of selftest.  very *very* minimum viable product, but would have caught the license problem14:31
agherzanRP: fair point. Checking it a bit more.14:32
*** tnovotny <tnovotny!~tnovotny@ip-78-45-97-113.net.upcbroadband.cz> has joined #yocto14:37
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)14:37
*** zpfvo <zpfvo!~fvo@> has joined #yocto14:37
*** kroon <kroon!~kroon@37-247-29-68.customers.ownit.se> has quit IRC (Quit: Leaving)14:38
*** jclsn <jclsn!~jclsn@> has joined #yocto14:43
*** akiCA <akiCA!~akiCA@user/akica> has joined #yocto14:43
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)14:45
*** zpfvo <zpfvo!~fvo@> has joined #yocto14:46
*** codavi <codavi!~akiCA@user/akica> has joined #yocto14:47
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has quit IRC (Read error: Connection reset by peer)14:48
*** akiCA <akiCA!~akiCA@user/akica> has quit IRC (Ping timeout: 256 seconds)14:50
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)14:51
*** zpfvo <zpfvo!~fvo@> has joined #yocto14:52
*** osama <osama!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto14:54
*** rsalveti <rsalveti!uid117878@id-117878.uxbridge.irccloud.com> has joined #yocto15:00
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto15:10
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has joined #yocto15:12
*** GillesM <GillesM!~gilles@> has joined #yocto15:13
vdCan an IMAGE_CMD mount the image file to add extra commands?15:27
RPvd: you don't normally have root privs so no15:29
*** GillesM <GillesM!~gilles@> has quit IRC (Quit: Leaving)15:31
vdRP: I would like to extend the btrfs support to add subvolumes, either with more control over the btrfs IMAGE_FSTYPES, or via wic (a subvolume can be described as a mountpoint from another parent partition). Do you have a guess where to start? The rootfs.py WIC's plugin maybe?15:33
*** jatedev <jatedev!~jatedev@> has joined #yocto15:35
*** pgowda_ <pgowda_!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)15:35
vderf no, wic doesn't mount its image files neither, I guess scripts on the target system is the only option.15:36
rburtonunless you can tell the btrfs commands to set up the stuff you want at creation time15:39
*** ekathva_ <ekathva_!~ekathva@2001:999:50:cab1:cb06:9935:dc:f7e7> has quit IRC (Remote host closed the connection)15:46
vdrburton: I can create a service script which is run after the partition device and before initrd-root-fs.target for example15:49
LetoThe2ndstupid me again. wheres the sync call described?16:00
tlwoernersgw: we're experiencing a heat wave in ontario, it's around 0°C. i too have my fan on to help keep it cool ;-)16:01
RPLetoThe2nd: which sync call?16:02
LetoThe2ndRP: found it, nevermind.16:02
*** davidinux <davidinux!~davidinux@net-188-153-130-222.cust.vodafonedsl.it> has quit IRC (Ping timeout: 256 seconds)16:08
vdrburton: the same goes for a luks partition I assume?16:10
rburtonyou are a normal user at all stages of a build.  luckily, disk image creation is normally not restricted to root, so if the tools can do it ofline, you can do it at image generation time16:19
vdrburton: got it, I'll see what cryptsetup offers16:21
T_UNIX[m]JaMa: hey, is there a channel dedicated to meta-qt5 ?16:24
*** pinenewb <pinenewb!~justforfn@c-67-177-234-26.hsd1.co.comcast.net> has joined #yocto16:28
pinenewbhi, I'm building a meta layer for the PineNote, but I'm running into an image tarball issue.  The yocto generated linux tarball is doing everything correctly, but a couple of kernel module paths (specifically broadcom) are really long (over 100 chars). So when I go to unpack the rootfs tarball from the default PineNote Android OS, tar chokes when it hits those long file paths.  I'm having to manually delete the directory from the16:32
pinenewbtarball in Linux before I copy & extract it16:32
pinenewbI recognize that this is not a yocto problem, but I'm wondering if anyone has suggestions on how to make this work a bit better out of the box16:33
pinenewbmaybe change INSTALL_MOD_PATH to a shorter path, and then create a symlink dir to where the kernel expects the files to be?  Part of the problem is my lengthy kernel version: 5.16.0-rc8-yocto-standard-pinenote16:34
qschulzpinenewb: please consider having it supported in meta-rockchip, I'm sure tlwoerner will be delighted to have one more device supported :)16:35
qschulz(likely requires most of the support to be upstream though, to be discussed with tlwoerner I guess)16:36
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)16:36
*** zpfvo <zpfvo!~fvo@> has joined #yocto16:36
pinenewbyeah, ideally this would be supported in meta-rockchip or some other upstream layer.  Is pinephone in meta-rockchip?16:37
pinenewbI haven't spent the time to figure out the pine64/rock64 relationship, but I dont think there's a meta-pine64, is there?16:37
khemit should be in meta-pine64 its allwinner16:40
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)16:41
*** zpfvo <zpfvo!~fvo@> has joined #yocto16:41
pinenewbwhat is the "official" meta-pine64?16:42
pinenewboh nevermind, looks like alistair23's16:43
khemyep https://github.com/alistair23/meta-pine6416:44
pinenewbk, will look at merging my stuff into that meta layer instead of creating a new one.  Any suggestions on the Android tar path length problem?16:46
khemcan you re-state the problem16:47
pinenewbmy output rootfs tarball has a couple of really long paths for broadcom kernel modules, and the default PineNote Android OS can't unpack the tarball without blowing up16:48
pinenewbI'm having to remove the files from the tarball manually before I can unpack it16:49
pinenewbit's totally _not_ a yocto problem, but I'm hoping there's a yocto solution16:49
khemsometimes max filelength can come in as problem16:49
tlwoerneryes, i always like seeing more MACHINEs in meta-rockchip :-D16:50
pinenewbI'm thinking that I might change INSTALL_MOD_PATH to a really short base path (/kmod) or something, then just create a symlink to the /lib/modules/<kernel_version> directory?16:50
tlwoerneri have a board on my desk that i haven't found the time to add in a while!16:51
pinenewbwell I don't have too many rockchip boards other than this new PineNote, but I happen to have a bit of free time right now :)16:51
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 256 seconds)16:52
khemyou might have PATH_MAX overflow16:53
pinenewbit seems like the OS itself can handle the path length, just not tar (untar).  If I remove the "leaf" directory that's blows up "tar -x" then I can drop it back in where its supposed to be after the rootfs tarball successfully extracts16:55
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 268 seconds)16:55
*** zpfvo <zpfvo!~fvo@> has joined #yocto16:55
pinenewbI dunno, maybe it's just a transient problem for me.  I basically have the device booting Linux & connecting to WiFi at this point with SSH access, so maybe I don't need to use the Android partition any more16:58
pinenewbit's just slightly annoying that I'm getting a rootfs tarball that only extracts in *most* places16:59
*** osama1 <osama1!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has joined #yocto16:59
*** smsm <smsm!~smsm@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Quit: Client closed)16:59
*** osama <osama!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Read error: Connection reset by peer)16:59
*** osama2 <osama2!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto17:00
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)17:00
qschulzpinenewb: for a quick and dirty hack you cna always just mv the files in the do_install:append of your recipe in a directory with a shorter name and do the ls by hand17:01
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 256 seconds)17:01
*** zpfvo <zpfvo!~fvo@> has joined #yocto17:02
*** osama1 <osama1!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 240 seconds)17:03
*** zpfvo <zpfvo!~fvo@> has quit IRC (Remote host closed the connection)17:04
pinenewbyeah, that would be an improvement.  Very unfortunate that it's the broadcom kmods though (no network without fixing the links)17:05
khemwhich distro are you on ?17:06
pinenewbI do have filesystem access when I untar, so I can fix the links then17:07
smurrayI assume the root issue is that the tar in Android sucks?17:07
khemtry. echo -e "#include <sys/param.h>\nMAXPATHLEN" | gcc -E -x c - | tail -n 117:07
pinenewbpulling in smaeul's kernel.  all of the heavy lifting is already done in terms of device tree & kernel stuff17:08
pinenewbyes, that is the problem. tar in Android sucks17:08
pinenewbkhem: that command doesn't work for (on Android): /system/bin/sh: gcc: inaccessible or not found17:15
pinenewbI'm in an ADB shell with sudo, but I just don't know enough android17:15
pinenewbonly know enough to get me back to linux :)17:15
pinenewbon my build host I get 409617:16
*** Alternate_Pacifi is now known as The_Pacifist17:17
khemyeah and a bit google-fu tells me its 1024 for android17:20
JaMaT_UNIX[m]: no17:21
pinenewbwell this definitely seems to be a very narrow problem with the particular version of tar on Android, so I'll just come up with a hackaround for now17:22
*** osama3 <osama3!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has joined #yocto17:26
*** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has joined #yocto17:29
*** osama2 <osama2!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Read error: Connection reset by peer)17:29
*** osama3 <osama3!~osama@ipbcc2935c.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 240 seconds)17:31
*** osama4 <osama4!~osama@eth1-fw1-nbg6.eb.noris.de> has quit IRC (Quit: WeeChat 3.4)17:40
*** frieder <frieder!~frieder@mue-88-130-73-056.dsl.tropolys.de> has quit IRC (Ping timeout: 256 seconds)17:40
*** mckoan is now known as mckoan|away17:49
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)18:06
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has joined #yocto18:08
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)18:15
*** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Quit: LIBERT..zzz)18:41
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has joined #yocto18:43
*** jatedev <jatedev!~jatedev@> has quit IRC (Quit: Client closed)18:45
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 256 seconds)18:45
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Quit: WeeChat 3.4)18:46
*** pinenewb <pinenewb!~justforfn@c-67-177-234-26.hsd1.co.comcast.net> has quit IRC (Quit: Leaving)18:51
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)19:00
agherzanat all: What do people use nowadays for CI on GitHub Yocto based projects?19:10
*** gchamp <gchamp!~champagne@ipagstaticip-d73c7528-4de5-0861-800b-03d8b15e3869.sdsl.bell.ca> has quit IRC (Quit: WeeChat 2.3)19:11
agherzanI tried GitLab CI - premium feature and no support for fork MRs. I tried GutHub actions, a big security mess on self-hosted workers and hard to scale builds when cache is a concern.19:11
agherzanI'm currently thinking of giving drone.io a try. I know khem was saying good things about it. Do we have any other experience in that regard? And no, I'm not coming back to Jenkins.19:12
fraymight not be what you are looking for.. but pushed and such kick off jenkins jobs in our environment.. then we group/cache/schedule builds and do them in our jenkins environmnet.19:13
frayignoring the jenkins side, I have seen other do something similar.. where the CI work flows can handle the kick off, and the 'results'.. but the work itself is done externally in their own systems19:13
agherzanfray: I had something similar both on personal and work infras. And maintaining Jenkins is not a nice thing. Especially if you look into the security concerns of various aspects.19:27
frayya, that is why I said from a practical standpoint ignore the build side.. it's all about kicking off a build with appropriate data (what needs to be built), scheduling it (do I do one build per change, or bundle the changes or some combination), and results success means what, failures mean what, and how are success/failure "logs" returned19:29
frayall of that can be done securely (you transform and transfer) or insecurely you just point people directly to a public instance of your CI system..19:29
fraythe right answer is somewhere in the middle, but I've not seen a "correct" everyone should do this behavior..19:30
frayWe've got tooling requirements for some open source repositories that require potentially proprietary (licensed) software, add to that needs to sanitize bad actor contributions that could attempt to run things on your build environmnet.. so our "public" CI is being designed to work more in a DMZ where it's "inside", but not inside our network...19:31
fraythat also gives us the ability to restrict what the machine can do on the external.. such as limit network access during the build, etc19:31
frayalso helps make this whole thing agnostic to the actual "build" infrastructure (jenkins or otherwise).. but still allow connections w/ github, gitlab or "other"19:32
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)19:32
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has joined #yocto19:40
agherzanI like the agonistic aspect of that. Also yes. All those infra requirements are to be taken into consideration but for public Foss projects, they probably don't matter that much. When you move into proprietary code and pipelines things change pretty fundamentally.19:43
frayeven for open source, as github found, you really need CPU process limits, network limits, etc.  bad actors will take over CI infrastructure to act as network proxies, download software, mine crypto, etc19:44
agherzanI'm more looking into what people use for their public projects in the yocto context19:44
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has joined #yocto19:45
*** agrue_ <agrue_!~agrue@host-23-251-65-139.VALOLT4.epbfi.com> has quit IRC (Quit: ZNC 1.7.5+deb4 - https://znc.in)19:52
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto19:53
*** agrue <agrue!~agrue@host-23-251-65-139.VALOLT4.epbfi.com> has joined #yocto19:54
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 256 seconds)19:54
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)19:58
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto20:02
*** bluelightning <bluelightning!~paul@2406:e003:151f:d701:9917:f282:6b72:75c9> has joined #yocto20:02
ziga_How do I know which "defconfig" file is used in image?20:03
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has joined #yocto20:16
*** argonautx <argonautx!~argonautx@i5E8670F2.versanet.de> has quit IRC (Quit: Leaving)20:18
*** tnovotny <tnovotny!~tnovotny@ip-78-45-97-113.net.upcbroadband.cz> has quit IRC (Ping timeout: 240 seconds)20:23
*** ex-bugsbunny <ex-bugsbunny!~Harry@p4fc2edaa.dip0.t-ipconnect.de> has quit IRC (Remote host closed the connection)20:55
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has joined #yocto20:59
khemAndrei Gherzan: I am happy with github actions with own runners now a days21:15
khemalthough I had no complaints with drone.io as well, only issue was I had to host the server and that costs 🙂21:15
khemAndrei Gherzan: look at meta-clang and yoe-distro if you are interested in running github actions https://github.com/kraj/meta-clang/tree/master/.github/workflows21:21
agherzankhem: are you using self hosted workers?21:22
agherzanAnd how do you handle the security warnings that the GitHub docs point to?21:22
agherzanDo you do any special configuration?21:22
khemno, ignore it21:23
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 276 seconds)21:23
agherzan:) right21:23
agherzanAnd you keep cache locally on the build server, right?21:23
khemas long as you make your runners secure, you are ok. you can run it in container21:24
khemyes cache is local21:24
agherzanOf course yes. I'll use docker runners21:24
agherzanI'll try it tomorrow. Maybe things changed since I was looking into that21:25
khemofcourse my local runner is down these days ☹️ which is a different issue21:26
*** risca <risca!~quassel@h-155-4-62-42.A980.priv.bahnhof.se> has quit IRC (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)21:30
vdI see recipes using custom FOO[bar], FOO_bar or a mixture of both. Is there a recommended way between crafted variables names or flags?21:30
*** amitk_ <amitk_!~amit@> has joined #yocto21:30
*** risca <risca!~quassel@h-155-4-62-42.A980.priv.bahnhof.se> has joined #yocto21:30
*** risca <risca!~quassel@h-155-4-62-42.A980.priv.bahnhof.se> has quit IRC (Client Quit)21:33
*** risca <risca!~quassel@h-155-4-62-42.A980.priv.bahnhof.se> has joined #yocto21:33
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 256 seconds)21:33
kergothvd: Generally flags should be used to define metadata about the metadata. SRC_URI[sha256sum] is the sum for the uri, etc. Sometimes it's overloaded to get access to a dictionary-like structure within the limitations of the bitbake file format, but that's not ideal unless it's in line with the original intention21:34
*** rob_w <rob_w!~rob@2001:a61:6050:d201:91c6:ab22:3d0a:4dde> has quit IRC (Read error: Connection reset by peer)21:42
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Quit: Leaving)22:00
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 256 seconds)22:01
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has joined #yocto22:20
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto22:27
*** mvlad <mvlad!~mvlad@2a02:2f08:4b12:b100:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)22:29
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds)22:55
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)23:06
RPkanavin: https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/4678/steps/16/logs/stdio - that traceback patch needs work :/23:16
RPand I see a patch, you're ahead of me :)23:18
vdkergoth: so in general you'd recommend defining FOO_somekey-bar instead of abusing FOO[bar]23:19
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto23:19
*** Bardon <Bardon!~Bardon@user/Bardon> has quit IRC (Ping timeout: 256 seconds)23:28
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Remote host closed the connection)23:37
smurrayvd: using custom varflags like FOO[bar] in your own recipes can be problematic for downstream users as they can't be appended or easily removed, AFAIK it requires anon python23:47
smurrayvd: so IMO the usage needs to be somewhat simple or not something you expect anyone to ever want to customize23:48
*** florian_kc <florian_kc!~florian@dynamic-002-244-168-091.2.244.pool.telefonica.de> has joined #yocto23:55
kergothgood points23:57
*** GillesM <GillesM!~gilles@> has joined #yocto23:57
*** GillesM <GillesM!~gilles@> has quit IRC (Client Quit)23:58

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