Concerned about upgradeing icinga2 packages

Icinga 2
1

I upgraded several Icinga-Packages on my debian-stretch server today. However, some packages have been held back and I’m a little concerned that sudo apt-get dist-upgrade wants to remove some neccessary packages. At least it seems like that to me. There is no mention of reinstalling said packages and I’m wondering if in fact I somehow misconfigured my icinga2 installation.

Keep in mind: The monitoring system is a HA-Setup and otherwise is working fine.

user@machine:~# uname -srvmo
Linux 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64 GNU/Linux

user@machine:~# dpkg -l | grep icinga2
ii  icinga2                              2.11.3-1.stretch                   amd64        host and network monitoring system
ii  icinga2-bin                          2.11.3-1.stretch                   amd64        host and network monitoring system - daemon
ii  icinga2-common                       2.11.3-1.stretch                   all          host and network monitoring system - common files
ii  icinga2-ido-pgsql                    2.11.3-1.stretch                   amd64        host and network monitoring system - PostgreSQL support
ii  vim-icinga2                          2.12.3-1.stretch                   all          syntax highlighting for Icinga 2 config files in VIM



user@machine:~# apt-get dist-upgrade --dry-run
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  dbconfig-common icinga2-common libboost-atomic1.67.0 libboost-chrono1.67.0 libboost-context1.67.0 libboost-coroutine1.67.0 libboost-date-time1.67.0 libboost-filesystem1.67.0 libboost-program-options1.67.0 libboost-regex1.67.0 libboost-system1.67.0
  libboost-thread1.67.0
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  icinga2 icinga2-bin icinga2-ido-pgsql
The following packages will be upgraded:
  icinga2-common
1 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
Remv icinga2 [2.11.3-1.stretch]
Remv icinga2-ido-pgsql [2.11.3-1.stretch]
Remv icinga2-bin [2.11.3-1.stretch]
Inst icinga2-common [2.11.3-1.stretch] (2.12.3-1.stretch debian icinga-stretch:icinga-stretch [all])
Conf icinga2-common (2.12.3-1.stretch debian icinga-stretch:icinga-stretch [all])

That can’t be safe, can it? Or will everyhing be fine if I (re-)install the missing packages after the upgrade. I’m a bit lost here ¯\(ツ)/¯

2

I upgraded several Icinga-Packages on my debian-stretch server today.

So, it is running stretch and you want it to continue running stretch?

You are not trying to upgrade it to buster?

user@machine:~# apt-get dist-upgrade --dry-run

Why, then are you using “dist-upgrade”?

Remv icinga2 [2.11.3-1.stretch]
Remv icinga2-ido-pgsql [2.11.3-1.stretch]
Remv icinga2-bin [2.11.3-1.stretch]
Inst icinga2-common [2.11.3-1.stretch] (2.12.3-1.stretch debian

Which Icinga repository are you pointing at?

Regards,

Antony.

3

Yes, I’m running stretch and will continue to do so. dist-upgrade has nothing to do with “Upgrade my distro”. This paramter name has been confusing for a loooooong time. Here’s the excerpt of the manpage:

dist-upgrade
           dist-upgrade in addition to performing the function of upgrade, also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages
           at the expense of less important ones if necessary. The dist-upgrade command may therefore remove some packages. The /etc/apt/sources.list file contains a list of locations from which to retrieve desired package files. See also apt_preferences(5) for a
           mechanism for overriding the general settings for individual packages.