Danct12 has quit [Read error: Connection reset by peer]
Ram-Z has joined #yocto
Ram-Z has quit [Remote host closed the connection]
Ram-Z has joined #yocto
Danct12 has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
emdevt has joined #yocto
ablu has quit [Read error: Connection reset by peer]
qschulz has quit [Remote host closed the connection]
ablu has joined #yocto
qschulz has joined #yocto
tgamblin has quit [Ping timeout: 258 seconds]
davidinux has quit [Ping timeout: 240 seconds]
davidinux has joined #yocto
starblue has quit [Ping timeout: 255 seconds]
starblue has joined #yocto
Vonter has quit [Ping timeout: 258 seconds]
Vonter has joined #yocto
Daanct12 has joined #yocto
rber|res has quit [Ping timeout: 255 seconds]
goliath has quit [Quit: SIGSEGV]
rber|res has joined #yocto
emdevt__ has joined #yocto
emdevt has quit [Ping timeout: 260 seconds]
jclsn has quit [Ping timeout: 255 seconds]
jclsn has joined #yocto
ChriLoe has quit [Ping timeout: 245 seconds]
mrpelotazo has quit [Read error: Connection reset by peer]
mrpelotazo has joined #yocto
amitk has joined #yocto
Vonter has quit [Ping timeout: 258 seconds]
Vonter has joined #yocto
camus has quit [Quit: camus]
camus has joined #yocto
ablu has quit [Remote host closed the connection]
ablu has joined #yocto
ablu has quit [Remote host closed the connection]
ablu has joined #yocto
ablu has quit [Remote host closed the connection]
jmd has joined #yocto
mbulut has joined #yocto
ablu has joined #yocto
ablu has quit [Remote host closed the connection]
ablu has joined #yocto
alessioigor has joined #yocto
ablu has quit [Remote host closed the connection]
mbulut has quit [Quit: Leaving]
ablu has joined #yocto
linfax has joined #yocto
brrm has quit [Ping timeout: 240 seconds]
brrm has joined #yocto
JerryM has joined #yocto
taruu has joined #yocto
n0thing has joined #yocto
zpfvo has joined #yocto
<taruu>
Hello guys, I started working and studying the yocto project and ran into a problem that I couldn’t find guides or documentation for the meta levels used in the project. Can you tell me where I can find guides or discussions on this topic to understand how to use them?
xantoz has quit [Ping timeout: 255 seconds]
<RP>
The auto-upgrade-helper code is horrific :(
<kanavin>
I didn't write it :)
<RP>
kanavin: I know. I'm just struggling not to rip the whole thing apart
<kanavin>
RP: I'm also getting mildly annoyed at the assigned maintainers, where are the actual updates from them? we might need a new, harsher round of unassigning :(
<kanavin>
if there's no reaction for the round running right now within a month, I'll try to politely do something
<RP>
kanavin: Multiple challenges there. Some are fine with the AUH handling things in general, some just can't respond fast enough :/
<kanavin>
but AUH email is not the update itself. It's just a notice to the maintainer to take and resend. And this isn't happening, and across multiple people.
<RP>
kanavin: people see it differently
<RP>
kanavin: why do manually what the tool is already doing?
<kanavin>
RP: because it's not perfect, some patches can be taken as they are, others need tweaks, and in any case it needs someone to look at its output.
<RP>
kanavin: I know that but people often don't think about it
mvlad has joined #yocto
<kanavin>
RP: are you specifically reviewing latest auh patches, or is it something unrelated (I'm going to look at them now)?
<RP>
kanavin: I'm trying to add layer support to AUH to make it work for meta-oe
<kanavin>
RP: but there's a new patchset for that sent 9 hours ago?
xantoz has joined #yocto
<yocton>
Hi! I've sent that. Let me know if I can help
taruu has quit [Ping timeout: 240 seconds]
leon-anavi has joined #yocto
<RP>
kanavin: I'm getting confused. I'm looking at that patchset
<RP>
yocton: thanks!
<RP>
yocton: I have some ideas on how we could improve things but in the interests of time, I think working with what is there may be best
<yocton>
"fatal: 'origin/main' is not a commit and a branch 'tmp-auh-upgrades' cannot be created from it" default branch of meta-oe would be origin/master
taruu has joined #yocto
<RP>
yocton: yes, the script needs that tweaking, if we need that code at all :/
<RP>
kanavin: do you know of anywhere we use this tmp-auh-upgrades branch or is it just a leftover of the cron job?
<RP>
can we just delete weeklyjob.sh too?
<adrianf>
RP: Just a few thoughts on the maintenance of devtool. devtool offers different, almost independent functions. Would it make sense to have a maintainer for each function? For example: "Working on a recipe", "Recipe in workspace" are completely different things.
<RP>
adrianf: if someone wanted to volunteer as the maintainer for some specific functions that would be a better position than we're currently in so I'm open to it
<RP>
kanavin, yocton: According to that run, meta-oe is entirely up to date with nothing needing upgrading
<yocton>
I find that suspicious...
<RP>
People are running devtool upgrade against meta-oe a fair bit and the components there don't change as often as those in core, but, yes...
<RP>
INFO: Skip package meta-oe/libjson-perl (status = UNKNOWN_BROKEN, current version = 4.03000, next version = 4.10)
<yocton>
Running upgrade-helper.py with -d5 will log why recipes are skipped
xmn has quit [Quit: ZZZzzz…]
<RP>
cmp = vercmp_string(uv['current_version'], uv['version']) returns 1 for that
<kanavin>
RP: tmp-auh-upgrades is made from origin/master so that auh doesn't make its update commits directly into a master checkout
<kanavin>
RP: yes, I think weeklyjob.sh is actually unused, and so doesn't need to be maintained
<kanavin>
yocton, I looked at your patchset, it's basically fine
<adrianf>
RP: Deprecating the eSDK installer (do_propulate_sdk_ext) would also simplify the situation. With the meta-ide-support generated environment script, the new bitbake-layer save-build-conf / create-layers-setup functions from Alex and the shared sstate-cache there is a much easier to maintain and more flexible replacement for all available functions.
<kanavin>
adrianf, I think some people still find value in all-included shell archives, the biggest value in them is in fact that they include the cache objects
n0thing has quit [Quit: Client closed]
n0thing has joined #yocto
<kanavin>
adrianf, you are welcome to join the sstate-for-all thread on the mailing archives, where we discussed how esdk-type environment can be provided directly in a yocto build (it's basically meta-ide-support+restricted tooling+locked signatures). I'm refactoring populate_sdk_ext to make various pieces reusable.
<kanavin>
there was some discussion around that just earlier this week
<kanavin>
RP: I'm looking at the version checks in meta-oe. Something doesn't compute there: they either match the latest, or are broken. Statistically that is not possible, so it's likely broken ones in fact do miss later versions being available.
<kanavin>
(I mean, I'm looking at the checks performed by auh-meta-oe on the AB. This needs to be checked locally as well).
<n0thing>
What would be your advice to a junior who wants to contribute to Yocto and has only been in the industry for 1.5 years? Where should I start? When I can't even produce anything of value...
<rburton>
n0thing: there's a newcomer tag in bugzilla for bugs which should be _relatively_ simple
<kanavin>
n0thing, I would advice you to subscribe to the openembedded-core mailing list, and look out for weekly status update mails (they are also archived here https://wiki.yoctoproject.org/wiki/Weekly_Status )
<kanavin>
there are numerous ways to contribute listed here, but one particular item I'd appreciate is providing version updates for oe-core
<n0thing>
rburton then it seems like a good start to become a member of bugzilla and start try to solving the problems under the newcomer tag. thanks!
<adrianf>
akanavin: found it. Thank you.
<n0thing>
kanavin Thanks! I will check
<n0thing>
I would like to ask one more question. It is not related to yocto but i would appreciate if you could answer it. What are the qualifications that a junior embedded linux developer should have? What should he/she know?
<RP>
kanavin: something isn't adding up. I see the same results locally
<RP>
adrianf: I'm not sure we can drop the esdk installer but I would like to improve it and make it less black box magic, there is discussion on the list about that
<yocton>
Almost no recipe in meta-oe has a RECIPE_MAINTAINER => every upgrade is skipped because of that? (e.g. krb5)
<kanavin>
n0thing, a public coding or documentation portfolio. Doesn't matter how small or unimpressive you think it is, as long as it exists. Shopping list of qualifications matters less than that. I personally don't have half the things that people list as 'mandatory' for an embedded linux developer :-D
<kanavin>
basically, do a project that interests you personally, and publicly document every step of the way
<kanavin>
RP: are you running devtool check-upgrade-status or devtool latest-version on those?
radanter has joined #yocto
<RP>
kanavin: auh with a single recipe specified
<RP>
n0thing: there was a mention recently on the mailing list about cleaning up class XXX(object): -> class XXX(): syntax. That is old python 2.x remnants. If you want to send some simple patches that would get you some commits :)
<yocton>
RECIPE_MAINTAINER:pn-krb5="Someone" in local.conf and "upgrade-helper.py krb5 -d5" at least start some upgrade compilation
<kanavin>
this should be fixed so that version checks work even in the absence of that
<yocton>
That's 2 separate problems : 1) version check is broken on some recipes (UNKNONW_BROKEN in logs), 2) Some upgradable recipes are silently skipped (unless debug is displayed with -d5) because of missing maintainer
florian_kc has joined #yocto
<kanavin>
can you identify where the skipping happens?
<yocton>
_pkg_upgradable(): D(" Skipping upgrade of %s: no maintainer" % pn) (line 652)
<kanavin>
right. I wonder if we should set RECIPE_MAINTAINER for each layer in meta-oe then (there are now per-layer overrides for that).
<kanavin>
e.g. RECIPE_MAINTAINER:layer-gnome-layer = "someone" etc
<yocton>
Same idea. I'll send a patch for master-next
<RP>
yocton: thanks, sounds good to me
<yocton>
In yocto-autobuilder-helper/scripts/auh-config/local.conf.append or extravars in config.json?
<RP>
yocton: might as well put it in extravars
<yocton>
ok!
<RP>
kanavin: I'm starting to think we should rework auto-upgrade-helper into something in oe-core
<RP>
with a suitable amount of cleanup and refactoring
<kanavin>
RP: yes. it's full of brittle hacks around running external executables and parsing their output
florian_kc has quit [Ping timeout: 240 seconds]
sotaoverride has quit [Killed (tantalum.libera.chat (Nickname regained by services))]
sotaover1ide is now known as sotaoverride
sotaover1ide has joined #yocto
<JerryM>
get_metadata_git_*(path, d) in meta/lib/oe/buildcfg.py include 'd' but never use it, is there a reason this is still included?
<RP>
JerryM: I think there used to be a set of functions for different SCMs and some probably needed it
Piraty_ is now known as Piraty
tgamblin has joined #yocto
<RP>
yocton, kanavin: I think the patches are the right direction so I've merged the auh repo ones
<RP>
I also added a couple of tweaks to drop things
<JerryM>
RP: I figured as much, although I took a very brief glance at the history but couldn't find any references anyway, howver currently there is nothing in oe-core that uses it so I figure it would be safe to remove regardless
<diecore>
Hello! I need some help, I can't find the .its file in the /boot/dts folder as also I can't find were the DTC compiler is executed for compiling the .dts for the sam9x75 target I am working with. The weird thing is that at the kernel recipe inside the do_deploy:append() function there is the line cp ${S}/arch/${ARCH}/boot/dts/${MACHINE}*.its ${DTB_PATH} that copies the .its but I rather find it only at /tmp/deploy/images/XXX path
<diecore>
which is actually generated after building the image with bitbake.
paulg has joined #yocto
<diecore>
My goal is to modify the dts and its for my needs but is so confusing :-(
<zhmylove>
Hey Gods! According to https://wiki.yoctoproject.org/wiki/Releases Nanbield shoul've already released by the end of October. But there is still no release tag on nanbield branch. Does anyone aware of actual Nanbield release date? Thanks!
<rburton>
shortly
<rburton>
mainly just finishing the documentation now
<rburton>
kernel 6.5 "issues" resulted in the release slipping a few weeks
<zhmylove>
rburton: thanks!
<zhmylove>
BTW is there any chance it'll release until 15th November?
<rburton>
i expect early november
<zhmylove>
Thank you, Ross! Have a nice day!
paulg has quit [Ping timeout: 255 seconds]
n0thing has quit [Quit: Client closed]
tnovotny has joined #yocto
n0thing has joined #yocto
florian_kc has joined #yocto
silbe has quit [Ping timeout: 272 seconds]
xmn has joined #yocto
Xagen has joined #yocto
taruu has quit [Ping timeout: 272 seconds]
vmeson has quit [Remote host closed the connection]
prabhakarlad has joined #yocto
vmeson has joined #yocto
elfenix|cloud has joined #yocto
justHaunted is now known as justache
paulg has joined #yocto
brabander has joined #yocto
silbe has joined #yocto
jmd has joined #yocto
<brabander>
Is it still correct that you can set INITRAMFS_IMAGE in a recipe, as stated in the local.conf.sample.extended file ? Because even when I set this value to some non-nonsensical value bitbake seems to accept & ignore it.
Guest96 has joined #yocto
<Guest96>
Hello,
<Guest96>
does anyone know how to include the openssl library that will be used in a makefile which in then will be called by oe_runmake
<n0thing>
"LDFLAGS += -lssl -lcrypto" maybe?
<vmeson>
FYI, large numberic values for a UID don't seem to be a problem now that Kai has fixed an XFCE tar issue. Our IT dept started giving people UIDs > 2M ! "tar: value 1762430260 out of uid_t range 0..2097151"
florian_kc has quit [Ping timeout: 260 seconds]
<Guest96>
n0thing the ldflags are already included in my makefile
<n0thing>
Guest96 DEPENDS += " openssl" maybe?
prabhakarlad has quit [Quit: Client closed]
zhmylove has quit [Quit: Leaving]
<Guest96>
n0thing done that also
<n0thing>
Guest96 If you share the problem with pastebin, you may get more specific suggestion&solution.
<Guest96>
n0thing do you mean the output error or my recipe file?
<n0thing>
Guest96 You should to run oe_runmake in do_compile() instead of do_install().
<n0thing>
You used DEPENDS += "util-linux", DEPENDS += "openssl" seperate but I suggest you to write them as one, so DEPENDS += "util-linux openssl".
<dacav>
Hi. We have a read-only filesystem, and we would like to enable users to change password, both root and regular users. Does yocto support something like that?
<rburton>
dacav: you'll have to use something like overlayfs
<rburton>
dacav: obviously that changed password needs to go on disk somewhere
<adrianf>
RP: kanavin: I tried to catch up with your discussion in the emails as good as possible. Maybe you give the devtool ide plugin a try. It has 2 modes: A recipe mode and a none recipe mode. The none recipe mode is exactly what you have been discussing with the devtool esdk command. A few minutes ago the patches passed the AB gate, I guess.
<Guest96>
n0thing I still get the same error even after using do_compile()
n0thing has quit [Quit: Client closed]
Guest96 has quit [Quit: Client closed]
dgriego has quit [Quit: Bye]
linfax has quit [Ping timeout: 255 seconds]
Guest96 has joined #yocto
tnovotny has quit [Quit: Leaving]
zpfvo has quit [Ping timeout: 245 seconds]
sugarbeet has quit [Ping timeout: 240 seconds]
sugarbeet has joined #yocto
Tyaku has quit [Quit: Lost terminal]
zpfvo has joined #yocto
JerryM has quit [Quit: Konversation terminated!]
xmn has quit [Ping timeout: 260 seconds]
xmn has joined #yocto
zpfvo has quit [Remote host closed the connection]
florian_kc has joined #yocto
radanter has quit [Remote host closed the connection]
Guest96 has quit [Quit: Client closed]
florian_kc has quit [Ping timeout: 255 seconds]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
sotaoverride has quit [Quit: Lost terminal]
ctraven has joined #yocto
flom84 has joined #yocto
flom84 has quit [Remote host closed the connection]
leon-anavi has quit [Quit: Leaving]
florian_kc has joined #yocto
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
lolock is now known as stgloor
Minvera has joined #yocto
prabhakarlad has joined #yocto
amitk has quit [Ping timeout: 255 seconds]
mvlad has quit [Remote host closed the connection]
kevinrowland has joined #yocto
prabhakarlad has quit [Quit: Client closed]
jmd has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
alessioigor has quit [Quit: alessioigor]
dash_hope has joined #yocto
dash_hope has quit [Client Quit]
khem has joined #yocto
florian_kc has quit [Ping timeout: 248 seconds]
florian_kc has joined #yocto
rber|res has quit [Ping timeout: 240 seconds]
rber|res has joined #yocto
kevinrowland has quit [Quit: Client closed]
dvergatal has quit [Ping timeout: 255 seconds]
dvergatal has joined #yocto
tgamblin has quit [Remote host closed the connection]