**** BEGIN LOGGING AT Thu Jan 12 02:59:56 2023 Jan 12 07:44:07 good morning Jan 12 12:09:03 I am looking into deployment onto a pre-built yocto OS that does not have any package manager installed. The aim is to find a way to avoid recompiling everything to include e.g. rpm. Of course I could just scp my files onto the device but is there a more elegant way? Jan 12 12:13:42 package things as tar files? Jan 12 12:17:12 That would be an option similar to `scp` I'd say. I wonder if there is something like a "remote package manager" that does have some tracking logic built into it (e.g. supports simple update/remove). That would be cool... Jan 12 12:21:55 cb5r: this can be relatively easily be done through Menders custom update modules. Jan 12 15:28:23 cb5r: if your use case is development then devtool can deploy without package management (scp, basically). Jan 12 15:28:59 if its for production then a proper updater would be the way to go, swupdate, rauc, or some other one that i can't remember Jan 12 15:30:58 LetoThe2nd: mender definitely sounds like an awesome piece of software! I'll definitely keep it in mind! Jan 12 15:32:40 rburton: I'm looking for both, development AND production. I will look at the ones you mentioned. Thank you! Jan 12 16:54:12 Hey gods, is there any simple way to make RPM packages name conformant to common naming format, like when the build is for "genericx86_64" it produces rpms with "x86_64", "genericx86_64", "core2_64" and "noarch" architectures, while I want only "x86_64" or "noarch"? Jan 12 16:55:03 I've tried to change TUNE_PKGARCH and PACKAGE_ARCH but it does not help: either rpms are built with incorrect architecture, or dnf refuses to install them during do_rootfs Jan 12 17:34:54 zhmylove: MACHINE specific components doesn't make sense to build as seemingly generic x86_64, why do you want to have only one package arch? Jan 12 17:36:02 JaMa: I do actually want build all the packages either as *.x86_64.rpm or *.noarch.rpm; while by default Yocto produces also *.genericx86_64.rpm and *.core2_64.rpm... Jan 12 17:36:22 if you don't care about multi-machine builds, you can change the default PACKAGE_ARCH to be MACHINE_ARCH, but it's PIA Jan 12 17:36:42 and I want ponny, that doesn't explain why Jan 12 17:37:46 Actually, some recipes do re-define PACKAGE_ARCH variable right from .bb and I can not change this setting even using several overrides Jan 12 17:38:23 you can change DEFAULTTUNE if you don't want to use core2_64, but using the same for MACHINE specific and noarch recipes doesn't make sense Jan 12 17:38:29 I mean that it's possible to replace the value, but then do_rootfs fails with dnf errors like: "package ncurses-terminfo-base-6.3+20220423-r0.x86_64 is intended for a different archite" Jan 12 17:40:13 $ bitbake-getvar -r zlib PACKAGE_ARCHS Jan 12 17:40:20 PACKAGE_ARCHS="all any noarch aarch64 armv8a armv8a-crc cortexa72 raspberrypi4_64" Jan 12 17:40:40 PACKAGE_ARCHS is used to define feeds used by package manager Jan 12 17:41:07 you cannot change PACKAGE_ARCH to random string and expect dnf to be able to find it Jan 12 17:45:48 I'm setting it to "x86_64" Jan 12 17:46:03 As it's valid for some other packages and dnf manages to install 'em properly Jan 12 19:46:26 looks like meta-qt5 needs to be compatible with mickledore ... Nayone sent antyihing in yet? Jan 12 19:46:57 hmm Jan 12 19:47:34 my bad Jan 12 20:11:54 Who is responsible for https://www.yoctoproject.org/irc/oe/ ? It's not updated since 2022 Dec, it's a bug :) **** ENDING LOGGING AT Fri Jan 13 02:59:56 2023