mbulut has quit [Remote host closed the connection]
rfuentess has joined #yocto
Guest49 has joined #yocto
ray-san2 has joined #yocto
<frosteyes>
just a small question. The nut branches, is this for "next under test". Was just wondering about the name.
Guest66 has joined #yocto
vladest has joined #yocto
Guest49 has quit [Ping timeout: 250 seconds]
<mcfrisk_>
should all native recipes have "-native" recipe name postfix? I think a lot of code assumis this.
<mcfrisk_>
so if "inherit native" then recipe name should have -native too?
zpfvo has joined #yocto
leon-anavi has quit [Quit: Leaving]
leon-anavi has joined #yocto
enok has joined #yocto
<ernstp>
it's usually the build-appliance-image: Update to kirkstone head revision commit that get's tagged for release right?
rfuentess has quit [Quit: Leaving]
florian has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
leon-anavi has quit [Quit: Leaving]
Guest66 has quit [Quit: Client closed]
zhmylove has joined #yocto
<zhmylove>
Hey Gods! Running do_populate_sdk results in an error: "core-image-bare-1.0-r0 do_populate_sdk: The sstate manifest for task 'nativesdk-crash:package_write_rpm' (multilib variant '') could not be found" — am I missing something? I've added nativesdk to BBCLASSEXTEND and nativesdk-crash compiles properly. Could it save sstate manifest into improper place?
mvlad has joined #yocto
Tyaku has joined #yocto
Guest19 has joined #yocto
<rburton>
mcfrisk_: yes
<rburton>
mcfrisk_: even if the code didn't have some hardcoded -native checks in the recipe name, not doing so would be very confusing
rber|res has quit [Quit: Leaving]
Vonter has quit [Ping timeout: 256 seconds]
Vonter has joined #yocto
Vonter has quit [Client Quit]
Vonter has joined #yocto
Tyaku has quit [Quit: Lost terminal]
jpuhlman has quit [Read error: Connection reset by peer]
<qschulz>
If one passes a filename which isn't a path, then it's trying to find all files matching this filename at any depth in the repo
prabhakalad has quit [Ping timeout: 272 seconds]
prabhakalad has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.2.1]
leon-anavi has joined #yocto
Guest32 has joined #yocto
Guest19 has quit [Ping timeout: 250 seconds]
florian has quit [Quit: Ex-Chat]
xmn has joined #yocto
jmiehe has joined #yocto
Guest32 has quit [Quit: Client closed]
<zeddii>
anyone in the knnow about syslinux and how it interacts with rootfs creation and wic ? I'm having a hell of a time validating Xen uprevs in meta-virt and I'm very slowly trying to untangle if the images are being created properly.
<qschulz>
ah, this missing CONFIGURE_FILES probably impacts any linux recipe as well?
Xagen has joined #yocto
<jclsn>
Is there an issue with the Qt mirror atm? I am getting a ton of fetcher failures, even on lts-5.15
manuel1985 has quit [Ping timeout: 268 seconds]
sev99 has joined #yocto
nindoja2 has joined #yocto
ak77 has joined #yocto
vladest has quit [Ping timeout: 255 seconds]
<yocton>
I just saw a glimps of my name in the Bug triage Zoom chat before closing the window... I missed the related discussion sorry :(
<rburton>
jclsn: what qt mirror? I heard upstream deleted a load of branches so maybe you need to move to another release or something. (Remember to blame qt for this)
<jclsn>
rburton: code.qt.io
<jclsn>
I am using lts-5.15 which was updated recently
<jclsn>
I would assume that the mirrors get changed there
vladest has joined #yocto
khem has joined #yocto
<khem>
RP: is there a way to add extra cmdline options to git clone when using git fetcher ?
rfuentess has quit [Remote host closed the connection]
zhmylove has quit [Remote host closed the connection]
<RP>
khem: re: the git fetcher, not sure there is
<RP>
khem: I'm trying not to take upgrades :/
<khem>
RP yeah regarding upgrades gnome 46 is releasing and it’s lts so I was inclined to take the patches to upgrade recipes to use gnome 46 but don’t have strong opinion
<khem>
Is bitbake -b supported or do we want folks to use bitbake -c
<RP>
khem: bitbake -b would be very hard to use correctly now
<RP>
khem: I'll test those upgrades
<khem>
So how do we wean folks away from bitbake -b
<rburton>
the --help says it doesn't respect any dependencies, so I suggest any newbie who uses it we ask where they got it from and get documentation fixed
<RP>
khem: I doubt anyone has used -b successfully for years
goliath has joined #yocto
frieder has quit [Quit: Leaving]
nerdboy has quit [Remote host closed the connection]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
nindoja2 has quit [Quit: Client closed]
GNUmoon2 has quit [Remote host closed the connection]
GNUmoon2 has joined #yocto
<khem>
@moto-timo: I wonder if F_TLOCK is replaced with F_LOCK and made a blocking call could synchronise it with out loops
GNUmoon2 has quit [Remote host closed the connection]
<JPEW>
denix: Ah, the joy of fixing CI so you can fix a bug :)
<jwinarsk>
I'm hitting another case of `do_package: dwarfsrcfiles failed with exit code 1`. This is in master building static lib with clang, and lto enabled. Problem only arises adding debuginfod to DISTRO_FEATURES.
<jwinarsk>
libfilamat.a: not a valid ELF file
<jwinarsk>
ar x returns nothing. objdump -a lists out the object files
<denix>
JPEW: nice, thanks!
afong_ has quit [Ping timeout: 264 seconds]
vladest has quit [Remote host closed the connection]
prabhakalad has quit [Ping timeout: 264 seconds]
prabhakalad has joined #yocto
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
jmd has quit [Remote host closed the connection]
<sev99>
Hello! I have been trying to use the Hash Server functionality demonstrated at the most recent Yocto Summit and have run into a small issue with authenticating users. I can create a user with appropriate permissions using `bitbake-hashclient` but when doing a build (where I would expect that user to be the one reporting to the hash server) it is
<sev99>
reporting back that the user is `anonymous`. I thought that putting those credentials in netrc meant they would be used (since it seems that is how `bitbake-hashclient` functions) but that does not seem to be the case. Where should those credentials be placed in order for hashes to be reported under that user?
sev99 has quit [Quit: Client closed]
mvlad has quit [Remote host closed the connection]
sev99 has joined #yocto
vladest has joined #yocto
prabhakalad has quit [Ping timeout: 255 seconds]
prabhakalad has joined #yocto
<JPEW>
denix: Pyrex v1.9.1 is released, so you should be able to pull up and use it now
davidinux has quit [Ping timeout: 255 seconds]
davidinux has joined #yocto
<marex>
khem: since the LVGL 9.1.0 is now in meta-oe/master , and this is a release tag, shall I drop PV .= "+git${SRCPV}" from the recipes and send a patch ?
<denix>
JPEW: thanks!
<denix>
$ pyrex-run which ssh
<denix>
/usr/bin/ssh
<JPEW>
\o/
<moto-timo>
JPEW: CI is the gift that keeps on giving, but sometimes keeps on taking. ;)
* moto-timo
counts the number of Friday nights fixing crops build failures and the number is way too large
sotaoverride has quit [Ping timeout: 255 seconds]
Xagen has quit [Ping timeout: 272 seconds]
amitk_ has quit [Remote host closed the connection]
ctraven has joined #yocto
<moto-timo>
khem: I know you are under the weather so this is not urgent, but I did come across a qt6 build failure with my rpi5 PR (https://github.com/YoeDistro/yoe-distro/pull/912). I had only built yoe-simple-image (which works just fine).
<JPEW>
sev99: Right, I don't think bitbake reads the .netrc, let me check
olani- has joined #yocto
<RP>
khem: looks like we need the gtk4 upgrade for those other upgrades
Vonter has quit [Ping timeout: 246 seconds]
Vonter has joined #yocto
<sev99>
JPEW Thank you! I brielfy looked through it and didnt think it did for this. Figured I would ask on here just to double check and see if those credentials were meant to be grabbed in a different way by bitbake
<JPEW>
sev99: Heh, specifying the username and password isn't implemented yet; I knew I was forgetting something. Let me work on that
<sev99>
JPEW no worries ^_^ I appreciate the help and the confirmation.
alessioigor has quit [Ping timeout: 255 seconds]
<jwinarsk>
`To resolve this issue you will need to determine how the detected path is entering the output. Sometimes it may require adjusting scripts or code to use a relative path rather than an absolute one, or to pick up the path from runtime configuration or environment variables.` Joy
<vvn>
hi there -- With meta-freescale I have "[ERROR] DFI error. Please check DDR configuration" when I try to uuu core-image-minimal to an imx8ulp-lpddr4-evk, on both mickledore and scarthgap