Used Zammad version: zammad-3.7.0-1612175851.c4a237a2.centos8.x86_64
Used Zammad installation source: RPM
Operating system: CentOS 8
Browser + version: Firefox
Hello!
have successfully installed and used the above version.
For a few weeks now I have been getting the following error messages when updating:
Fehler:
Problem: cannot install the best update candidate for package zammad-.7.0-1612175851.c4a237a2.centos8.x86_64
nothing provides elasticsearch|elasticsearch-oss needed by zammad-.7.0-1616475717.2e8415d5.centos8.x86_64
(try to add ‘–skip-broken’ to skip uninstallable packages or ‘–nobest’ to use not only best candidate packages)
Elasticsearch (elasticsearch-7.12.0-1.x86_64) is installed and works with the installed Zammad version!
[root@zammad ~]# yum update --skip-broken
Fehler:
Problem: cannot install the best update candidate for package zammad-3.7.0-1612175851.c4a237a2.centos8.x86_64
nothing provides elasticsearch|elasticsearch-oss needed by zammad-4.1.0-1616654558.c4ecbb75.centos8.x86_64
(try to add ‘–nobest’ to use not only best candidate packages)
[root@zammad ~]#
[root@zammad ~]# yum update --nobest
Abhängigkeiten sind aufgelöst.
Problem: cannot install the best update candidate for package zammad-3.7.0-1612175851.c4a237a2.centos8.x86_64
nothing provides elasticsearch|elasticsearch-oss needed by zammad-4.1.0-1616654558.c4ecbb75.centos8.x86_64
========================================================================================================================
Package Architecture Version Repository Size
========================================================================================================================
Pakete mit nicht auflösbaren Abhängigkeiten werden übersprungen:
zammad x86_64 4.1.0-1616654558.c4ecbb75.centos8 zammad-dev 253 M
Transaktionsübersicht
========================================================================================================================
Überspringen 1 Paket
Nichts zu tun.
Fertig.
I don’t know how Elasticsearch behaves then, does anyone have any experience?
Unfortunately you are right. We’re facing issues with our package build and distribution service packager.io. We’re working together with them to resolve the issue ASAP.