I worked around this problem by building a current version of rpm (4.15.1)
from source. I prefixed the build to /usr/local, with the exception of var
which I pointed to the system rpm db. The versions were close enough that
I figured there was no major schema difference. I used the updated rpm
command to manually install virt-win, then updated everything else with the
normal system rpm. I thought of upgrading the system to the new version of
rpm, looking at the installed rpm's SPEC file, there are many patches over
the stock code. I don't have the time to go through and figure out which
patches are minor fixes, and which may make major changes to the way rpm
works on RedHat/CentOS. I decided I didn't want to introduce something
that could cause me more problems in the future, especially not for a
single package. I am concerned this type of problem may spread as more
people build rpms that use the new compression method.
RPMs that are supposed to be shared among EL6/EL7/EL8 should probably just
use the old compression method for compatibility. Alternatively, the new
compression method could be back-ported/enabled for the entire family if
there is a desire to consolidate everything; seems excessive, but certainly
possible. Just my 2c.
-Edmond
On Sun, Feb 9, 2020 at 3:20 AM Gal Zaidman <gzaidman(a)redhat.com> wrote:
Forwarding this to virtio-win developers and packagers.
Notice that virtio-win is a package in Fedora/Centos/RHEL and it is not an
"ovirt/RHV" package so ovirt doesn't package it.
On Sun, Feb 9, 2020 at 4:59 AM <eshwayri(a)gmail.com> wrote:
> Same problem. Looks like the virtio rpm is now built with the new
> compression method, but rpm for EL7 hasn't been updated to support it.
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5Q4AQYIVCAQ...
>