This is the second time that Nagios in EPEL7 was updated to another major version, introducing a lot of disruptive changes. The update to 4.0.8 already broke several things (e.g. PNP4Nagios plugin), this update also changes the directory layout and location of several files, rendering existing 4.0.8 installations in a broken state during update.
This is in violation of the package policies for EPEL - https://fedoraproject.org/wiki/EPEL_Updates_Policy
"All updates should strive to avoid situations that require manual intervention to keep the package functioning after update."
"Major updates with changes to user experience are to be avoided."
As the member of a project that depends on a stable version of Nagios in EPEL,
this repeated breaking of Nagios causes a lot of confusion and headache on our end and for our users.

It's kind of a catch 22. It needs to be stable, but there also needs to be an upgrade path or at the very least, somebody needs to backport security fixes. If given between an upgrade breaking Nagios or having a major security hole due to a bug in an older release, I tend to lean towards at least having an option to apply a possibly breaking update to resolve the security issue.

Note

You need to
log in
before you can comment on or make changes to this bug.