On 15/05/2025 08:59, Sandro Bonazzola via virt wrote:
>
>
> Il giorno gio 15 mag 2025 alle ore 07:53 Fabian Arrotin
> <arrfab@centos.org <mailto:arrfab@centos.org>> ha scritto:
>
> On 12/05/2025 15:21, Fabian Arrotin wrote:
>
> [cut]
>
> Packages (includind now qemu-kvm 10.0, just released to stream 10 this
> week) are signed and pushed to
> https://mirror.stream.centos.org/SIGs/10-stream/virt/ppc64le/kvm-
> power/ <https://mirror.stream.centos.org/SIGs/10-stream/virt/
> ppc64le/kvm-power/>
>
> I'd like to work on centos-release-kvm-power pkg but was just wondering
> : as we *don't* inherit from any pkg from centos-release-virt-common, I
> was considering skipping it (and so just ship the virt GPG key in
> centos-release-kvm-power).
> I guess it's fine for you all ? or maybe I should still use -common in
> case some other SIG would suddenly like to embed both (and so no
> conflicting files in different pkgs when trying to set these up in
> parallel)
>
> Opinions ?
>
>
> Within oVirt I guess it will be useful enabling ppc64le on el10 so if
> you don't mind, I would prefer you still use -common dependency (it
> basically just ships the GPG key). It will also avoid updating the key
> in multiple places if for some reason we need to issue a new one.
>
Makes sense .. let me then work on centos-release-kvm-power, that would
Requires: centos-release-virt-common
BTW, just looking at existing rpm pkgs for this, and I see
centos-release-kvm but its it still needed anymore ? it seems it's only
carrying some specific "{rust-}vhost*" pkgs (for ovirt ?)
Sandro Bonazzola
MANAGER, ENGINEERING
Red Hat In-Vehicle Operating System