On 5/6/22 17:35, Erik Skultety wrote:
> Since QEMU doesn't maintain a spec file in upstream, we cannot build RPM
> artifacts as part of the CI as we do for libvirt. Instead of hard-coding the
> build steps for QEMU though patch 3/5 pulls in QEMU's CI job template which
> means we'll remain in sync
On Fri, May 06, 2022 at 05:35:15PM +0200, Erik Skultety wrote:
> Since QEMU doesn't maintain a spec file in upstream, we cannot build RPM
> artifacts as part of the CI as we do for libvirt. Instead of hard-coding the
> build steps for QEMU though patch 3/5 pulls in QEMU's CI job template which
> me
Since QEMU doesn't maintain a spec file in upstream, we cannot build RPM
artifacts as part of the CI as we do for libvirt. Instead of hard-coding the
build steps for QEMU though patch 3/5 pulls in QEMU's CI job template which
means we'll remain in sync if QEMU makes changes to its build process.
E
