specfile fix for EPEL users of zabbix #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
March 17, 2021 01:02
…now treated as an additional source
…ibzbxpgsql.conf file (pg_query. -> pg.query)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Zabbix comes from EPEL, the requirements won't work here. The EPEL team botched the 'provides' section, and instead of providing 'zabbix-agent' with a version number, it's 'zabbix-agentXX'. This work-around assumes that the package 'zabbix' will almost always also mean that 'zabbix-agent' is installed. (Exception could be a proxy server). The EPEL zabbixXX package by luck provides 'zabbix'. Note, I've only tested this with zabbix 3.0, not 2.2. Also note: this merge request includes the changes I made in the other pull request.