Closed sshedi closed 11 months ago
I think that 14.5-1.ph4
is greater than 14.5-1
, thus your obsoletes postgresql <= 14.5-1
does not match it.
A fix would be to obsolete postgresql <= 14.5
, as this matches all release numbers.
Thanks @mlschroe this solved the problem.
Sorry, I'm reopening this. I have another query.
Why does solv consider %{dist}
tag while comparing versions? Is there a way to ignore the dist tag while comparing versions?
Please let me know if there is any rpm or solv setting I can modify.
The solver needs to match exactly what rpm does. The %dist tag is most likely used in the version/release specification in the spec file, thus is part of the version/release. There's nothing you can do on the rpm/libsolv side, you need to change the specfile.
Hi,
We are seeing something unusual while updating our postgresql rpms. Here is the link to our spec: https://github.com/vmware/photon/blob/4.0/SPECS/postgresql/postgresql14.spec#L54
But after installing
pgsql-14.5-1
and doingtdnf update -y postgresql
,pgsql-14.8-1
is not coming in.And
rpm -Uvh postgresql-14*.rpm
also doesn't yield in removing the older14.5-1
version.Here is a sample program showing solver checking the version:
It's recognized properly but, tdnf and rpm are not doing the expected.
tdnf github link:
https://github.com/sshedi/tdnfhttps://github.com/vmware/tdnflibsolv version:
libsolv-0.7.19
rpm version:rpm-4.16.1.3