Bug 1269204 - Zabbix agent EPEL packages to 'provide' compatibility with vendor packages
Zabbix agent EPEL packages to 'provide' compatibility with vendor packages
Status: NEW
Product: Fedora EPEL
Classification: Fedora
Component: zabbix (Show other bugs)
epel7
All All
unspecified Severity medium
: ---
: ---
Assigned To: Volker Fröhlich
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-06 11:44 EDT by Ryan Armstrong
Modified: 2017-03-08 21:46 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ryan Armstrong 2015-10-06 11:44:30 EDT
Zabbix SIA publish their agent packages using the name `zabbix-agent` while they are listed in EPEL as `zabbix<ver>-agent`. It is also quite common for installers to repackage the agent with yet another name with their own custom scripts, plugins and configuration.

I write an agent module package (https://github.com/cavaliercoder/libzbxpgsql) which currently requires that `zabbix-agent` first be installed. Unfortunately, users who install the EPEL package fail to satisfy this requirement, despite the agent binaries being deployed in an appropriate way.

To reproduce this issue, install any version of the Zabbix agent from EPEL, and then attempt to install the libzbxpgsql package and it will fail with unresolved dependency `zabbix-agent`. If the Zabbix SIA provided package is used instead, the issue is resolved.

Could the package maintainers please consider adding a `Provides: zabbix-agent` declaration in the EPEL `zabbix*-agent` packages? This way, the EPEL packages will satisfy (via virtual package) the requirement from any 3rd party module package for `zabbix-agent` to be installed.

I considered using `Require: /usr/sbin/zabbix_agentd` instead, but this limits other packagers of `zabbix-agent` from installing binaries in other locations. For example in my case, the binary is deployed to `/opt/zabbix/sbin/zabbix_agentd`.

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