On Thu, Dec 16, 2021 at 09:35:31AM +0100, Laszlo Ersek wrote:
On 12/15/21 16:51, Richard W.M. Jones wrote:
The bottom line is still that it's librpm's problem now to handle any guest rpmdb, no matter how ancient (well, at least RHEL >= 5). If you have the latest rpm installed and it still doesn't work then it could be a bug in librpm, although I'm pretty sure I tested this case.
The latest "rpm" package in Fedora 34, rpm-4.16.1.3-1.fc34:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1726304
built on 22 Mar 2021, does not (cannot) have the fix. The upstream rpm fix is:
https://github.com/rpm-software-management/rpm/commit/ea2754b4f14e0a195f4633...
which is between tags "rpm-4.17.0-alpha" and "rpm-4.17.0-beta1", and has commit date 2021-06-11. The fix has been backported to RHEL-9 (1965147):
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1824746
but not to Fedora 34.
Fedora 34 is supposed to be maintained until 2022-05-17, according to Wikipedia, so this is definitely a Fedora bug. I guess I should update my workstation to Fedora 35 regardless; that should be faster.
(Fedora 35 has rpm-4.17.0-1.fc35, so it should have the fix.)
You might find you can just install the Fedora 35 package on F34, eg: dnf update rpm --releasever=35 Small possibility it could do Bad Stuff to your system -- since it is a rather fundamental package ... Rich.
Thanks Laszlo
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html