Update Icinga Client from 2.6 to 2.10.x seems to be a new installation, not an update

Hello,

we are trying to update Icinga 2 Client from 2.6.1 to 2.10.x.

icinga2-libs-2.6.1-1.x86_64
icinga2-2.6.1-1.x86_64
cinga2-common-2.6.1-1.x86_64
icinga2-bin-2.6.1-1.x86_64

However, this seems to be more an new installaton of the 2.10* packages ( and deinstallition of the 2.6 packages) instead of an upgrade, as the old config eg. constants.conf gets overwritten and the old config file gets saved as .rpmsave.

Is this expected behaviour ?

We actually expected the old conf file to be not touched, new file saved as rpmnew…

Thanks

Frankie

I’m not very versed in the affairs of package managers but we did change up our build system, linkage and libraries over the time. 2.6.x to 2.10.x is a leap, did this lead to any other issues?