From je-vv at e.email Mon Jul 4 22:22:12 2022 From: je-vv at e.email (Javier) Date: Mon, 4 Jul 2022 14:22:12 -0600 Subject: [artix-general] about jami Message-ID: Hello ! I've noticed artix includes under [galaxy] "jami-daemon". This is not system wide daemon though, it's called and used by the jami client, which [community] one supported on arch is "jami-qt". I use "jami-qt", but I'm wondering if the intention is to include it eventually as part or [galaxy]. And if not, why keeping "jami-daemon" under [galaxy]? Is there systemd specific stuff in there? Not complaining BTW, just wondering. I believe "jami-daemon" and "jami-qt" must be in sync at all times, and having [galaxy] "jami-daemon" out of sync with respects to [community] "jami-qt" can be an issue. And I'd hope "jami-qt" gets included into artix official repos some day, :) It's worth noting, thankfully, things got simpler, since before there was even a separate library client, whereas right now there are only those 2 packages... Greetings ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From rptnix at amerytel.net Wed Jul 6 00:12:17 2022 From: rptnix at amerytel.net (epektasis) Date: Tue, 5 Jul 2022 17:12:17 -0500 Subject: [artix-general] mkinitcpio warning about modules.builtin.modinfo Message-ID: Greetings. I have been building my own kernels for some time on Artix but today mkinitcpio produced a repeatable error message, after building the hooks and displayed "generating module dependencies:" depmod: WARNING: could not open modules.builtin.modinfo at /tmp/mkinitcpio./root/lib/modules/: no such file or directory but the process continued and announced that image generation was successful and, indeed, the generated image was where it was directed to be. It was the root user who ran the mkinitcpio -k -g command, so there should not have been a permissions issue in /tmp/. The same warning message displayed on four different kernels, including two from kernel.org and the "stock" Artix linux-lts kernel. The warning message displayed using various kernel config files, including my own, the Artix linux-lts one, and even with the make defconfig option. The make modules_install command was run after mrproper, make {localmod,old,def}config, and make; then the resulting bzImage was copied to /boot (this is a BIOS system) and then mkinitcpio was run. The module files were in /lib/modules/. The machine rebooted fine. Apparently the warning message is an empty threat? From rptnix at amerytel.net Wed Jul 6 03:29:13 2022 From: rptnix at amerytel.net (epektasis) Date: Tue, 5 Jul 2022 20:29:13 -0500 Subject: [artix-general] mkinitcpio warning about modules.builtin.modinfo In-Reply-To: References: Message-ID: On Tue, Jul 05, 2022 at 05:12:17PM -0500, epektasis wrote: > Greetings. I have been building my own kernels for some time on Artix but > today mkinitcpio produced a repeatable error message, after building the hooks > and displayed "generating module dependencies:" > > depmod: WARNING: could not open modules.builtin.modinfo at > /tmp/mkinitcpio./root/lib/modules/: > no such file or directory > > but the process continued and announced that image generation was successful > and, indeed, the generated image was where it was directed to be. > > It was the root user who ran the mkinitcpio -k -g > command, so there should not have been a permissions issue in /tmp/. > > The same warning message displayed on four different kernels, including > two from kernel.org and the "stock" Artix linux-lts kernel. The warning > message displayed using various kernel config files, including my own, the > Artix linux-lts one, and even with the make defconfig option. > > The make modules_install command was run after mrproper, make > {localmod,old,def}config, and make; then the resulting bzImage was copied to > /boot (this is a BIOS system) and then mkinitcpio was run. The module files > were in /lib/modules/. > > The machine rebooted fine. Apparently the warning message is an empty threat? > > I saw that mkinitcpio 31-3 just came through on the updates and the warning message did not show when it ran. Guess the above was limited to 31-2. Sorry for the noise. e.