Hi Jered, > This issue was raised by another user yesterday -- Peter Eckel suggested > reviewing the upgrading notes regarding sysconfig at > https://www.icinga.com/docs/icinga2/latest/doc/16-upgrading-icinga-2/
I don't thing this is the same issue. Usman's problem seems to be related to a missing library libmysql_shim.so.2.9.0. In RHEL/CentOS that library is part of the icinga2-ido-mysql-2.9.0-1 package. As we don't know whether this is a new install or an update it's difficult to tell, but I would suspect it's a new installation and he missed installing the icinga2-ido-mysql package. > This all creates a wishlist for me regarding package managers -- on Debian > it's never apparent when an upgrade should require careful review of > documentation due to the potential for breaking changes. I wish there was a > flag so that apt-get would say "no, dummy, go read the notes first!" > Creating new dummy package dependencies can have this effect, but it's > definitely not the right way to do it. At least with RPM you can implement OS commands to be executed on installation, deinstallation, or update, which makes it easily possible to point the user at important information such as upgrade notes or clean up stuff that might have accumulated from older versions and is no longer needed or would breaking an upgrade. I would assume that this is also the case for the Debian package manager (I haven't packages stuff for Debian yet, so I can't tell for sure). The package maintainer "just" has to do it. This can, however, be quite a pain in the backside if you want to cater for all versions a user might upgrade from, so I understand fully that most maintainers don't bother. Peter. _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
