(In reply to Holger Weiß from comment #23)
> (In reply to Sam Kottler from comment #14)
> > I hope my comments above provide a reasonable route to resolving this issue.
> > What do the two parties involved think?
> 
> I'm sorry, but for the moment, I have no idea why a user would want to
> switch to tarballs provided by Nagios Enterprises.  This might change in the
> future, of course.  Therefore, my feeling is that it's too early for
> deciding on this issue.

I agree that it's too early to decide on the issue. These are the packages in EPEL that depend on nagios-plugins and what do we want to do about them? Create community-plugins-* alternatives?

nagios-plugins-apt-0:1.4.16-10.el6.x86_64
nagios-plugins-breeze-0:1.4.16-10.el6.x86_64
nagios-plugins-by_ssh-0:1.4.16-10.el6.x86_64
nagios-plugins-check-updates-0:1.6.3-1.el6.x86_64
nagios-plugins-check_sip-0:1.3-4.el6.x86_64
nagios-plugins-cluster-0:1.4.16-10.el6.x86_64
nagios-plugins-dhcp-0:1.4.16-10.el6.x86_64
nagios-plugins-dig-0:1.4.16-10.el6.x86_64
nagios-plugins-disk-0:1.4.16-10.el6.x86_64
nagios-plugins-disk_smb-0:1.4.16-10.el6.x86_64
nagios-plugins-dns-0:1.4.16-10.el6.x86_64
nagios-plugins-dummy-0:1.4.16-10.el6.x86_64
nagios-plugins-file_age-0:1.4.16-10.el6.x86_64
nagios-plugins-flexlm-0:1.4.16-10.el6.x86_64
nagios-plugins-fping-0:1.4.16-10.el6.x86_64
nagios-plugins-game-0:1.4.16-10.el6.x86_64
nagios-plugins-hpjd-0:1.4.16-10.el6.x86_64
nagios-plugins-http-0:1.4.16-10.el6.x86_64
nagios-plugins-icmp-0:1.4.16-10.el6.x86_64
nagios-plugins-ide_smart-0:1.4.16-10.el6.x86_64
nagios-plugins-ifoperstatus-0:1.4.16-10.el6.x86_64
nagios-plugins-ifstatus-0:1.4.16-10.el6.x86_64
nagios-plugins-ircd-0:1.4.16-10.el6.x86_64
nagios-plugins-lcgdm-common-0:0.9.5-1.el6.x86_64
nagios-plugins-ldap-0:1.4.16-10.el6.x86_64
nagios-plugins-linux_raid-0:1.4.16-10.el6.x86_64
nagios-plugins-load-0:1.4.16-10.el6.x86_64
nagios-plugins-log-0:1.4.16-10.el6.x86_64
nagios-plugins-mailq-0:1.4.16-10.el6.x86_64
nagios-plugins-mrtg-0:1.4.16-10.el6.x86_64
nagios-plugins-mrtgtraf-0:1.4.16-10.el6.x86_64
nagios-plugins-mysql-0:1.4.16-10.el6.x86_64
nagios-plugins-nagios-0:1.4.16-10.el6.x86_64
nagios-plugins-nrpe-0:2.14-5.el6.x86_64
nagios-plugins-nt-0:1.4.16-10.el6.x86_64
nagios-plugins-ntp-0:1.4.16-10.el6.x86_64
nagios-plugins-ntp-perl-0:1.4.16-10.el6.x86_64
nagios-plugins-nwstat-0:1.4.16-10.el6.x86_64
nagios-plugins-openmanage-0:3.7.11-1.el6.x86_64
nagios-plugins-oracle-0:1.4.16-10.el6.x86_64
nagios-plugins-overcr-0:1.4.16-10.el6.x86_64
nagios-plugins-perl-0:1.4.16-10.el6.x86_64
nagios-plugins-pgsql-0:1.4.16-10.el6.x86_64
nagios-plugins-ping-0:1.4.16-10.el6.x86_64
nagios-plugins-procs-0:1.4.16-10.el6.x86_64
nagios-plugins-radius-0:1.4.16-10.el6.x86_64
nagios-plugins-real-0:1.4.16-10.el6.x86_64
nagios-plugins-rhev-0:1.0.0-2.el6.noarch
nagios-plugins-rpc-0:1.4.16-10.el6.x86_64
nagios-plugins-sensors-0:1.4.16-10.el6.x86_64
nagios-plugins-smtp-0:1.4.16-10.el6.x86_64
nagios-plugins-snmp-0:1.4.16-10.el6.x86_64
nagios-plugins-ssh-0:1.4.16-10.el6.x86_64
nagios-plugins-swap-0:1.4.16-10.el6.x86_64
nagios-plugins-tcp-0:1.4.16-10.el6.x86_64
nagios-plugins-time-0:1.4.16-10.el6.x86_64
nagios-plugins-ups-0:1.4.16-10.el6.x86_64
nagios-plugins-users-0:1.4.16-10.el6.x86_64
nagios-plugins-wave-0:1.4.16-10.el6.x86_64

> 
> That said, my hope was simply that we were able to explain the current
> situation more or less accurately.  As long as you actually understood what
> happened and where the two upstreams are coming from, I'm (of course)
> totally fine with you deciding whatever you think is the best solution for
> RedHat/Fedora.
> 
> Thanks for taking the time to look into this mess.