I have a managed environment of Ubuntu 18.04, where package versions must stay pinned for compatibility.
I had our environment set to use zabbix agent
1:6.0.10-1+ubuntu18.04
However, this package was removed from the repository, and I my new host build processes failed due to missing this package.
I changed the environment to pin to version:
1:6.0.11-1+ubuntu18.04
Again, I see this package was removed from the repository and I have hosts failing to build. This seems different from how older major versions were managed, as I can specify any older version of the agent from the 5.0 repository.
Is this intentional? It seems unnecessary as those who want the latest, can just allow the default apt behavior to install the latest version. I was expecting the 6.0 repository to behave a similar way and allow me to reach any package version, so that I can update at my own pace. I could roll back to using agents in the 5.0 repository instead, but this seems like a very silly reason to do so.
I had our environment set to use zabbix agent
1:6.0.10-1+ubuntu18.04
However, this package was removed from the repository, and I my new host build processes failed due to missing this package.
I changed the environment to pin to version:
1:6.0.11-1+ubuntu18.04
Again, I see this package was removed from the repository and I have hosts failing to build. This seems different from how older major versions were managed, as I can specify any older version of the agent from the 5.0 repository.
Is this intentional? It seems unnecessary as those who want the latest, can just allow the default apt behavior to install the latest version. I was expecting the 6.0 repository to behave a similar way and allow me to reach any package version, so that I can update at my own pace. I could roll back to using agents in the 5.0 repository instead, but this seems like a very silly reason to do so.
Comment