The RPM 4.0.2-6x updates just issued recently do not include the
rpm-python RPM. Thus, anything relying on the Python support for
rpm is likely to break; at the best it will be using old shared
I observe that RedHat could have seen this problem and others with
the rpm 4.0.2-6x upgrade if they (you) had bothered to version the RPM
shared libraries. If they had been versioned, RPM's dependancy checking
would have given you a nice list of things that depended on the old
libraries, so you would have had the list of 6.2 packages that needed
new versions of themselves made. Instead, you subverted the dependency
checking that is one of RPM's strong features, to the detriment of your
customers and users.
Yup. The root cause was a typo in a GUI window, so any gain from bumping the
soname wouldn't have helped. In fact, the rpm-python package already has an
dependency on the rpm package exactly the same as what would have happened if a
rpmlib soname had been auto-magically detected by find-requires.
This isn't an argument for not changing the rpmlib soname (that certainly needs
doing as well),
only an observation. Yes there will be an errata for gnorpm, rpmfind, et al to
lack of change in the rpmlib soname, that's a different issue.
rpm-python-4.0.2-6x is now available as part of the re-released errata.