Re: [Rpm-maint] [rpm-software-management/rpm] What's the scope of --root (supposed to be)? (Discussion #2735)

2024-04-20 Thread Sam Morris
I think I've stumbled into this. I was trying to use a public GitHub Actions runner to create container images built from the `ubi-micro` images, which don't have `dnf` installed within. I found that `dnf --installroot=... install` failed because the PGP keys it wanted weren't found in the

Re: [Rpm-maint] [rpm-software-management/rpm] What's the scope of --root (supposed to be)? (Discussion #2735)

2024-03-04 Thread Rong Tao
Thanks a lot, i just stuck on this for a long time. My build container `/etc/rpm/macros.image-language-conf`=`%_install_langs en_US.UTF-8`, The ISO i built with this container, it's Anaconda INSTALLATION screen only support English. -- Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] What's the scope of --root (supposed to be)? (Discussion #2735)

2023-11-06 Thread Panu Matilainen
`--macros` is problematic because it requires rewriting the entire path, most of which is fairly critical to normal operation. Basically rpm must always initialize itself with the macros from the same version, otherwise there's weird stuff can happen. Which means, rpm from the host must

Re: [Rpm-maint] [rpm-software-management/rpm] What's the scope of --root (supposed to be)? (Discussion #2735)

2023-10-25 Thread Michal Domonkos
FTR, I've stumbled upon these two recent PRs that somewhat extend the scope of `--root` and may act as some kind of precedent if we choose to involve macro configuration, too: * #2582 * #2503 -- Reply to this email directly or view it on GitHub: