Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: T6776: use the official Zabbix repo for zabbix-agent2 #813

Merged
merged 1 commit into from
Oct 18, 2024

Conversation

dmbaturin
Copy link
Member

Change Summary

Use the official repo for installing zabbix-agent2 to keep it up to date.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes)
  • Migration from an old Vyatta component to vyos-1x, please link to related PR inside obsoleted component
  • Other (please describe):

Related Task(s)

Component(s) name

Build configuration.

Proposed changes

Debian maintainers, oddly enough, are not updating the zabbix-agent2 6.x package in Bookworm, despite known vulnerabilities. There's zabbix-agent2 7.x in bookworm-backports, but 6.x is the current LTS version, and 7.x may not work with older Zabbix servers, so we cannot "just" upgrade to 7.x.

Using the official repo solves that problem, since they include the latest versions there. One peculiarity is that they have separate repos for x86-64 and aarch64, which is why URLs in files for different architectures are different.

How to test

Checklist:

  • I have read the CONTRIBUTING document
  • I have linked this PR to one or more Phabricator Task(s)
  • My commit headlines contain a valid Task id
  • My change requires a change to the documentation
  • I have updated the documentation accordingly

Copy link

👍
No issues in PR Title / Commit Title

@sever-sever sever-sever merged commit 167cba6 into vyos:current Oct 18, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

3 participants