-
Problem report
-
Resolution: Fixed
-
Major
-
4.2.0, 4.2.1
-
None
-
Ubuntu 18.04 LTS
-
Sprint 56 (Sep 2019), Sprint 55 (Aug 2019), Sprint 52 (May 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019), Sprint 57 (Oct 2019), Sprint 58 (Nov 2019)
-
1
the version epoch number inside the metadata of the zabbix-release_4.2-1+bionic_all.deb deb package is not set, but it is set to 1 for all other zabbix packages, including older zabbix-release packages.
Steps to reproduce:
check package infos for any Zabbix package (Ubuntu) from repo.zabbix.com, i. e. the zabbix-release package for version 4.0:
dpkg --info /var/tmp/zabbix-release_4.0-2+bionic_all.deb | grep Version Version: 1:4.0-2+bionic
do the same with the 4.2 release package:
dpkg --info /var/tmp/zabbix-release_4.2-1+bionic_all.deb | grep Version Version: 4.2-1+bionic
The version for the 4.0 Zabbix-Release package, as for all other Zabbix packages including the 4.2 ones (except the zabbix-release one) is set to 1:4xxx (not the "1:" part at the beginning), but the zabbix-release_4.2 package has it set to only "4.2" with no version epoch defined. This means the epoch gets defaulted to "0:".
Result:
**
The above described error causes the package management to believe upgrading from an installed zabbix-release_4.0-2* to zabbix-release_4.2-0* to be a DOWNGRADE, as it recognizes the package with the lower epoch to be older:
dpkg -l| grep zabbix ii zabbix-agent 1:4.0.7-1+xenial amd64 Zabbix network monitoring solution - agent ii zabbix-frontend-php 1:4.0.7-1+xenial all Zabbix network monitoring solution - PHP front-end ii zabbix-get 1:4.0.7-1+xenial amd64 Zabbix network monitoring solution - get ii zabbix-release 1:4.0-2+xenial all Zabbix official repository configuration ii zabbix-sender 1:4.0.7-1+xenial amd64 Zabbix network monitoring solution - sender ii zabbix-server-mysql 1:4.0.7-1+xenial amd64 Zabbix network monitoring solution - server (MySQL)
dpkg -i zabbix-release_4.2-1+xenial_all.deb dpkg: warning: downgrading zabbix-release from 1:4.0-2+xenial to 4.2-1+xenial (Reading database ... 89649 files and directories currently installed.) Preparing to unpack zabbix-release_4.2-1+xenial_all.deb ... Unpacking zabbix-release (4.2-1+xenial) over (1:4.0-2+xenial) ... Setting up zabbix-release (4.2-1+xenial) ... Installing new version of config file /etc/apt/sources.list.d/zabbix.list ...
This appears to be a cosmetical problem only, but it's actually an issue when using Ansible, for example.
Expected:
An upgrade from a zabbix-release 4.0 to a zabbix-release 4.2 should be recognized as an UPGRADE by apt.
