prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
enok has quit [Ping timeout: 255 seconds]
enok has joined #yocto
florian has joined #yocto
piotr has joined #yocto
piotr is now known as Guest6633
<Guest6633>
Hello everyone, I'm looking for the information about performing builds on Ubuntu 24.04. I had some issues with building Kirkstone based images there which I resolved but now I'm trying the Dunfell builds and I'm stuck... Do you know what's the official status of support on that distribution?
sukbeom has quit [Quit: Ping timeout (120 seconds)]
sukbeom has joined #yocto
<kanavin>
Guest6633, dunfell is end of life and isn't supported, especially on newer host distros
<Xogium>
even older than kirkstone afaik
<Guest6633>
Thanks @kanavin. What about other releases like Kirkstone and Scarthgap - are those officially supported or not yet?
<Guest6633>
You're right @Xogium. LTS'es are Dunfell -> Kirkstone -> Scarthgap and Dunfell is already eol, while other 2 are still active (until 2026 and 2028)
Guest6633 is now known as lewicki-pk
<kanavin>
lewicki-pk, not yet. 'Officially supported' means 'are a part of the test cluster', and that takes some time to bring up.
<kanavin>
lewicki-pk, but eventually it should happen
<kanavin>
lewicki-pk, I'd suggest you stay with 2204 for now
<ldywicki>
@lewicki-pk do you fire oe-scripts directly from host or use some wrapper such as KAS?
<lewicki-pk>
Thanks for the link. Regarding staying - it's too late now. I got a new laptop and spend a day configuring it so I'll stick to 24.04LTS - maybe this will make me contribute something :D
xmn has joined #yocto
<lewicki-pk>
@ldywicki - I fire oe-scripts directly. Using KAS is being discussed in my team but not yet started.
<ldywicki>
if you are stuck with older yocto branch you can always try to fire kas-docer, it will get you older tools and effectively chroot you back ;)
<lewicki-pk>
@ldywicki - Thats great tip and I'll do that since I have to support the devices in the field for 15/20 years so it would be nice to have possibility to rebuild in the future :-)
<ldywicki>
Just remember to cache container image somewhere :-)
<kanavin>
lewicki-pk, if you can build master on 2404, and there are fixes to be done for bitbake/core/poky/etc, those would be welcome
<ldywicki>
docker made some changes to their policies so if you rely on dockerhub images can disappear after few years. Pushing them to internal or external repo (ie. google contaienr registry or github registry) will keep you covered.
<kanavin>
lewicki-pk, presumably support for 15-20 years will happen through field updates to newer, supported yoctos?
<kanavin>
then there's no acute need to rebuild ancient stacks, although it should still be possible
Saur_Home86 has quit [Quit: Client closed]
Saur_Home86 has joined #yocto
enok has quit [Ping timeout: 268 seconds]
xmn has quit [Ping timeout: 268 seconds]
Poppy has joined #yocto
alessioigor has quit [Quit: Client closed]
<Poppy>
Hello guys, stupid question, I'm working on custom image (with bbclass) I have added SRC_URI += "part.config" in image recipe to "configure" the new image creation. But the file is not copied inside WORKDIR (maybe because of noexec of image.bbclass) what is the best way to perform this operation ? thanks and have a good day
alessioigor has joined #yocto
mbulut has joined #yocto
<mbulut>
gm gents
<mbulut>
say i have a core-image-minimal.bbappend for production builds
<mbulut>
how would i ideally define another image recipe that has all what core-image-minimal has and some extra sugar on top?
<mbulut>
if i create a core-image-minimal-dev.bb and require core-image-minimal.bb from that, I lose my packages defined in core-image-minimal.bbappend
<mbulut>
i cannot require core-image-minimal.bbappend either...
<mbulut>
oh
<mbulut>
maybe I should share the packages in an .inc file and include that from both...
<kanavin>
mbulut, core-image-minimal is a sample recipe, if you want to tweak it, copy into myproduct-image-minimal.bb first
<kanavin>
and then you can define bbclasses and .inc files as you please without needing bbappends
Daanct12 has quit [Quit: WeeChat 4.3.2]
<rburton>
mbulut: yeah the answer is don't define "your images" by reusing core-image-* and bbappend. copy-paste if you need to, but make your own images.
<mbulut>
oh, ok that's good to know
<mbulut>
I was thinking it might be good practice to append the minimal images that are provided by upstream in case I wanna switch to a different poky release
<mbulut>
but maybe i was wrong
mort has quit [Read error: Connection reset by peer]
<rburton>
that's why you don't just append the example images
<rburton>
they'll change
Guest11 has quit [Quit: Client closed]
<rburton>
if you're using yocto in production you want to control the images and distro, don't just extend poky. upgrade, poky changes, and your product changes.
wooosaiiii has quit [Remote host closed the connection]
wooosaiiii1 is now known as wooosaiiii
enok has quit [Ping timeout: 256 seconds]
jdiez has joined #yocto
<lewicki-pk>
Just a comment to what we talked about at 10:30- Thanks again @kanavin and @ldywicki. I'll try KAS. Regarding updates in 15 years: this is not so easy, because we might need to get the exact build with just one small bug fixed. If we were to deliver the completely new software (e.g. through swu) this would require recertifying everything -> huge costs, etc. It might be required in some cases but in some
<lewicki-pk>
other ones (like adding a sleep to the bash script) would allow us to skip full suite of retests...
<kanavin>
lewicki-pk, but how do you fix security issues?
<lewicki-pk>
@kanavin depending on the client - either I don't (if thats requested) or through software update to much newer version...
cbeznea_ has joined #yocto
ablu_ has joined #yocto
Jones42 has joined #yocto
jpuhlman- has joined #yocto
davidinux1 has joined #yocto
zpfvo1 has joined #yocto
mcfrisk_ has joined #yocto
mrpelotaz0 has joined #yocto
warthog19 has joined #yocto
zpfvo has quit [*.net *.split]
cbeznea has quit [*.net *.split]
davidinux has quit [*.net *.split]
ablu has quit [*.net *.split]
Haxxa has quit [*.net *.split]
jpuhlman has quit [*.net *.split]
qschulz has quit [*.net *.split]
Danct12 has quit [*.net *.split]
kanavin has quit [*.net *.split]
mrpelotazo has quit [*.net *.split]
warthog9 has quit [*.net *.split]
u1106 has quit [*.net *.split]
stgl has quit [*.net *.split]
wkennington_ has quit [*.net *.split]
armpit has quit [*.net *.split]
mcfrisk has quit [*.net *.split]
bradfa has quit [*.net *.split]
jkridner has quit [*.net *.split]
mithro has quit [*.net *.split]
georgem has quit [*.net *.split]
halstead has quit [*.net *.split]
neverpanic has quit [*.net *.split]
warthog19 is now known as warthog9
ablu_ is now known as ablu
neverpanic has joined #yocto
qschulz has joined #yocto
Haxxa has joined #yocto
kanavin has joined #yocto
Danct12 has joined #yocto
stgl has joined #yocto
u1106 has joined #yocto
wkennington_ has joined #yocto
armpit has joined #yocto
bradfa has joined #yocto
jkridner has joined #yocto
mithro has joined #yocto
georgem has joined #yocto
halstead has joined #yocto
Poppy has joined #yocto
<Poppy>
Is it possible to use SRC_URI inside a recipe image (inherited of image class)?
<DvorkinDmitry>
I have two MACHINE=x1 that is alias for MACHINE=x0. In Nanbield the recipe found the file at /recipename/x0/myfile, in Scarthgap it doesn't. Why?
CombatWombat42 has joined #yocto
<mbulut>
does anyone know if there's a bbclass or examples for python packages that use pyproject.toml and pdm build backend?
<mbulut>
meta-python in meta-oe doesn't seem to have any..
<mbulut>
but maybe I'm better off blueprinting from another package that's built by just inheriting setuptools3
<kanavin>
mbulut, I think python3-jsonref in meta-python shows how to do it
<kanavin>
setuptools3 works only if you have setup.py in the tree, and that's considered obsolete
cbeznea_ has left #yocto [Leaving]
<mbulut>
oh, cool - that's using pdm too! :)
<mbulut>
thx for helping me find the nugget i was looking for
rob_w has quit [Remote host closed the connection]
enok has quit [Ping timeout: 255 seconds]
enok has joined #yocto
florian_kc has joined #yocto
Xagen has quit [Ping timeout: 252 seconds]
leon-anavi has quit [Quit: Leaving]
enok has quit [Ping timeout: 264 seconds]
Jones42_ has quit [Ping timeout: 255 seconds]
goliath has quit [Quit: SIGSEGV]
mbulut has quit [Quit: Leaving]
mbulut has joined #yocto
CrazyGecko has quit [Quit: Konversation terminated!]
<mbulut>
kanavin, the pypi bbclass doesn't seem to work just by its own as it doesn't provide any compile or install function -- the jsonref recipe you found hence also inherits setuptools3
<kanavin>
mbulut, which branch are you on?
<mbulut>
kirkstone(-ish)
<kanavin>
master please
<kanavin>
kirkstone is old and obsolete :-D
<mbulut>
I can't just yet -- we
<kanavin>
you can clone it separately
<mbulut>
we
<mbulut>
we're locked on kirkstone atm and can't change it right now
<mbulut>
ok
<kanavin>
yes, but you can clone meta-oe master separately
<kanavin>
and set up a build with it and poky if you want
<kanavin>
the key part is that it inherits python_setuptools_build_meta
<mbulut>
won't that collide with meta-oe kirkstone?
<mbulut>
I can't replace it just yet
<kanavin>
how? if you clone a repo to a separate directory
<kanavin>
just make a whole new separate directory and clone meta-oe to that
rfuentess has quit [Remote host closed the connection]
<mbulut>
yeah, sure but what about bblayers.conf? wouldn't i have to specify the layer that has the newer pypi.bbclass so my recipe can find it? (and wouldn't that collide with the kirkstone layer?)
<mbulut>
or am i just lost and don't understand you? :)
Saur_Home71 has joined #yocto
Saur_Home86 has quit [Ping timeout: 250 seconds]
yudjinn has quit [Ping timeout: 268 seconds]
yudjinn has joined #yocto
Xagen has joined #yocto
CombatWombat42 has quit [Ping timeout: 272 seconds]
eLmankku has joined #yocto
<kilobyte_ch>
Maybe dumb question, I'm building a JS application in a Bitbake recipe. Basically it is a Bitbake which inherits npm. In the do_compile() I'm doing a few npm things and in the do_install() I do a copy of the built files onto the target fs. This works great, but it results in nodejs getting build after it performed my bitbake. But I don't need nodejs. I have no r/depends with nodejs or similar. Is
<kilobyte_ch>
there a best practice to not build nodejs in such a case?
lquirion has quit [Quit: Leaving]
khem has quit [Quit: WeeChat 4.3.2]
tnovotny has quit [Remote host closed the connection]
mckoan is now known as mckoan|away
grsandeep85 has joined #yocto
zpfvo1 has quit [Remote host closed the connection]
dash_hope has joined #yocto
sakoman has quit [Read error: Connection reset by peer]
sakoman has joined #yocto
florian_kc has quit [Ping timeout: 268 seconds]
<kanavin>
mbulut, I was only suggesting that you set up a master build with meta-oe and poky, to see how it's done in a newer yocto. If kirkstone doesn't have the needed classes, you have options: replicate what the classes do in a recipe directly, or backport the classes into a custom layer etc. The point was to establish a working reference point with an upstream recipe (python3-jsonref), then consider how you can bring that into your
<kanavin>
custom build.
<rburton>
kanavin: pushed to xsettings-daemon
<kanavin>
rburton, thanks. I'm triaging more pending patches :)
sakoman has quit [Ping timeout: 264 seconds]
Saur_Home62 has joined #yocto
Saur_Home71 has quit [Ping timeout: 250 seconds]
gsalazar has quit [Ping timeout: 268 seconds]
<mbulut>
kanavin, now I got you. I'll look into master and pick the approach that gets me going for now -- probably backporting the classes into sth like a temporary mypypi.bbclass in my layer will be the better way to go so I don't have to change a lot in the recipes when I'm able to upgrade
<mbulut>
thx a lot
sakoman has joined #yocto
<kanavin>
cheers
CombatWombat42 has joined #yocto
dash_hope has quit [Ping timeout: 250 seconds]
frieder has quit [Remote host closed the connection]
dash_hope has joined #yocto
dash_hope has quit [Quit: Client closed]
florian_kc has joined #yocto
jmd has quit [Remote host closed the connection]
Kubu_work has quit [Quit: Leaving.]
sgw has joined #yocto
florian has quit [Killed (NickServ (GHOST command used by florian_kc!~florian@dynamic-002-243-191-082.2.243.pool.telefonica.de))]
florian_kc is now known as florian
dash_hope has joined #yocto
florian_kc has joined #yocto
Saur_Home62 has quit [Quit: Client closed]
Saur_Home62 has joined #yocto
dash_hope has quit [Quit: Client closed]
alessioigor has quit [Quit: Client closed]
dash_hope has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
grsandeep85 has quit [Quit: Client closed]
dash_hope has quit [Ping timeout: 250 seconds]
Haxxa has joined #yocto
florian has quit [Ping timeout: 264 seconds]
<DvorkinDmitry>
I have MACHINE=x1 that is alias for MACHINE=x0. In Nanbield the recipe found the file at /recipename/x0/myfile, in Scarthgap it doesn't. Why?
enok has joined #yocto
<JaMa>
DvorkinDmitry: is the FILESPATH the same?
<DvorkinDmitry>
JaMa, in Scarthgap it searches in recipename/x1/, but doesn't even try recipename/x0/
florian has joined #yocto
static_rocket has joined #yocto
<mischief>
any way to shut up 'references may fail if not absolute' from the git fetcher?
<mischief>
(for git submodules)
mvlad has quit [Quit: Leaving]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dash_hope has joined #yocto
<DvorkinDmitry>
JaMa, I'm wrong. it is started from Longdale. Before longdale URLs gave the warning for files that is not in x1 dir, they where taken from x0. But for Liongdale it just gives the error whithiut attempting the /x0 dir
<JaMa>
is x0 in MACHINE_OVERRIDES of x1? check how FILESPATH is constucted and debug from there
<DvorkinDmitry>
MACHINEOVERRIDES =. "x1:x0:"
jmiehe has joined #yocto
jmiehe has quit [Client Quit]
grsandeep85 has joined #yocto
jmiehe has joined #yocto
grsandeep85 has quit [Quit: Client closed]
jmiehe has quit [Quit: jmiehe]
<DvorkinDmitry>
JaMa, I can't debug with -e, it fails before creating the log