[solved] Update Zammad 2.9 Via Deb not working (Ubuntu 18.04)

Good Day,

To All,

If I may, may I know if there is someone successfully update the zammad from 2.8 to 2.9 via Deb,
Is not working when i tried to update via Deb.

Thank you

Right. I also can’t update via Deb.

I’m getting this on Debian 9… everything else is up to date…

The following packages have been kept back:
  zammad

@MrGeneration Hi Sir, requesting your kind assistance cant update zammad from 2.8 to 2.9 via Deb.

Thank you

What’s the exact issue/error message?

Sir @thorsteneckel here the output from the terminal after that nothing happens.

Thank You

root@erver:~# sudo systemctl stop zammad
root@erver:~# apt-get update
Hit:1 http://ph.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://ph.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://ph.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Ign:4 https://artifacts.elastic.co/packages/5.x/apt stable InRelease
Hit:5 https://artifacts.elastic.co/packages/5.x/apt stable Release
Get:7 http://ph.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [523 kB]
Get:8 http://ph.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [450 kB]
Get:9 http://ph.archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB]
Get:10 http://ph.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66.7 kB]
Get:11 http://ph.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB]
Get:12 http://ph.archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [7,024 B]
Get:13 http://ph.archive.ubuntu.com/ubuntu bionic-updates/restricted i386 Packages [6,984 B]
Ign:14 https://dl.packager.io/srv/deb/zammad/zammad/stable/ubuntu 18.04 InRelease
Get:15 http://ph.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [721 kB]
Get:16 https://dl.packager.io/srv/deb/zammad/zammad/stable/ubuntu 18.04 Release
Get:17 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:18 http://ph.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [731 kB]
Get:19 http://ph.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [202 kB]
Get:20 http://ph.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [189 kB]
Get:21 http://ph.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [350 kB]
Get:22 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B]
Get:23 http://ph.archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages [6,572 B]
Get:24 http://ph.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [6,408 B]
Get:25 http://ph.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2,464 B]
Get:26 http://ph.archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7,352 B]
Get:27 https://dl.packager.io/srv/deb/zammad/zammad/stable/ubuntu 18.04 Release.gpg
Get:28 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20.8 kB]
Get:29 https://dl.packager.io/srv/deb/zammad/zammad/stable/ubuntu 18.04/main amd64 Packages [8,227 B]
Get:30 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12.2 kB]
Get:31 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [45.2 kB]
Get:32 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2,464 B]
Fetched 4,013 kB in 4s (1,121 kB/s)
Reading package lists… Done
root@erver:~# apt-get upgrade
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
The following packages have been kept back:
gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libgl1-mesa-dri
libgnome-desktop-3-17 libjavascriptcoregtk-4.0-18 libwayland-egl1-mesa
libwebkit2gtk-4.0-37 libxatracker2 linux-generic linux-headers-generic
linux-image-generic mesa-va-drivers mesa-vdpau-drivers netplan.io zammad
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.

Sorry I guess I can’t help here - maybe @MrGeneration can?

Thank You Sir, waiting for Sir @MrGeneration reply.

Before from 2.7 to 2.8 updae via deb is no problem, now nothing happens when i try to update from 2.8 to 2.9

Thank you

I guess you should use apt-get dist-upgrade to install the kept back packages (and all others). Best regards, Uli

Thank you sir , but sir if its safe o use the dist-upgrade for zammad?, my worried is also updated some system in ubuntu and upgrade to new version and can conflict to zammad?

No risk based on my experiences. I use “dist-upgrade” for years.

already tried Sir, dist-upgrade still cant update zammad…

Sir @uli-heller but Sir you successfully upgraded zammad to 2.9 via Deb?

When i do a “apt-get upgrade”, apt says that the zammad package will be reserved. But why?

We will wait Sir @MrGeneration reply regarding the update of zammad via deb.

I don’t use the deb packages of zammad.

apt-get dist-upgrade supposedly fixes the issues about these “not upgraded” packages.
I guess you get other error messages…

zammadadmin@zammad:~$ sudo apt-get dist-upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

and then:

zammadadmin@zammad:~$ sudo apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete sind zurĂĽckgehalten worden:
  zammad
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
zammadadmin@zammad:~$

@MrGeneration your kind assistance please…

long story short, resolution:

Please do a friendly apt-get update && apt-get install zammad and accept the new dependencies.
This will resolve your issue, this is needed once to install new dependencies.

Detailed explanation:

You should be fine afterwards.

Sorry I have been absent from Friday to Sunday (Dreamhack ftw) and focussed on paying customers yesterday, as they pay my bills. :-X So sorry for the wait!
I could verify this, but this seems not to be Zammad related.

Interestingly my debian says (even though it wants to hold back Zammad), that it’s upgradable:

root@rikka:/home/mrgeneration# apt list --upgradable
Listing... Done
base-files/stable 9.9+deb9u8 amd64 [upgradable from: 9.9+deb9u7]
ca-certificates-java/stable 20170929~deb9u1 all [upgradable from: 20170531+nmu1]
curl/stable,stable 7.52.1-5+deb9u9 amd64 [upgradable from: 7.52.1-5+deb9u8]
gnupg/stable 2.1.18-8~deb9u4 amd64 [upgradable from: 2.1.18-8~deb9u3]
gnupg-agent/stable 2.1.18-8~deb9u4 amd64 [upgradable from: 2.1.18-8~deb9u3]
gpgv/stable 2.1.18-8~deb9u4 amd64 [upgradable from: 2.1.18-8~deb9u3]
libc-bin/stable 2.24-11+deb9u4 amd64 [upgradable from: 2.24-11+deb9u3]
libc-l10n/stable 2.24-11+deb9u4 all [upgradable from: 2.24-11+deb9u3]
libc6/stable 2.24-11+deb9u4 amd64 [upgradable from: 2.24-11+deb9u3]
libcups2/stable 2.2.1-8+deb9u3 amd64 [upgradable from: 2.2.1-8+deb9u2]
libcurl3/stable,stable 7.52.1-5+deb9u9 amd64 [upgradable from: 7.52.1-5+deb9u8]
libcurl3-gnutls/stable,stable 7.52.1-5+deb9u9 amd64 [upgradable from: 7.52.1-5+deb9u8]
libpam-systemd/stable 232-25+deb9u9 amd64 [upgradable from: 232-25+deb9u8]
libpq5/stable 9.6.11-0+deb9u1 amd64 [upgradable from: 9.6.10-0+deb9u1]
libsystemd0/stable 232-25+deb9u9 amd64 [upgradable from: 232-25+deb9u8]
libudev1/stable 232-25+deb9u9 amd64 [upgradable from: 232-25+deb9u8]
libwayland-client0/stable 1.12.0-1+deb9u1 amd64 [upgradable from: 1.12.0-1]
libwayland-cursor0/stable 1.12.0-1+deb9u1 amd64 [upgradable from: 1.12.0-1]
libwayland-server0/stable 1.12.0-1+deb9u1 amd64 [upgradable from: 1.12.0-1]
libxapian30/stable 1.4.3-2+deb9u3 amd64 [upgradable from: 1.4.3-2+deb9u2]
linux-image-4.9.0-8-amd64/stable 4.9.144-3 amd64 [upgradable from: 4.9.130-2]
locales/stable 2.24-11+deb9u4 all [upgradable from: 2.24-11+deb9u3]
multiarch-support/stable 2.24-11+deb9u4 amd64 [upgradable from: 2.24-11+deb9u3]
openssh-client/stable,stable 1:7.4p1-10+deb9u5 amd64 [upgradable from: 1:7.4p1-10+deb9u4]
openssh-server/stable,stable 1:7.4p1-10+deb9u5 amd64 [upgradable from: 1:7.4p1-10+deb9u4]
openssh-sftp-server/stable,stable 1:7.4p1-10+deb9u5 amd64 [upgradable from: 1:7.4p1-10+deb9u4]
postgresql-9.6/stable 9.6.11-0+deb9u1 amd64 [upgradable from: 9.6.10-0+deb9u1]
postgresql-client-9.6/stable 9.6.11-0+deb9u1 amd64 [upgradable from: 9.6.10-0+deb9u1]
postgresql-contrib-9.6/stable 9.6.11-0+deb9u1 amd64 [upgradable from: 9.6.10-0+deb9u1]
systemd/stable 232-25+deb9u9 amd64 [upgradable from: 232-25+deb9u8]
systemd-sysv/stable 232-25+deb9u9 amd64 [upgradable from: 232-25+deb9u8]
udev/stable 232-25+deb9u9 amd64 [upgradable from: 232-25+deb9u8]
zammad/unknown 2.9.0-1550483988.7f4899e0.stretch amd64 [upgradable from: 2.8.0-1549301377.48c6e6fe.stretch]

(side note: opensuse works just fine)

The reason why debian / apt-get holds back zammad is, that we introduced new needed packages for some image magic that we introduced with 2.9. The new dependencies can be found here: https://github.com/zammad/zammad/commit/5dedd6ecfc2afa4ba791c2b1f3415821cfed655b#diff-910c125a21f77d24b3ef81398ce824fe

The above is a default behaviour of apt-get btw and in my opinion legit - zypper on suse is a bit less restrictive and just solves the dependencies.

This get’s clearer with the following command (a dist-upgrade works / “Solves” the issue, as it works dependency aware and tries to solve them):

root@rikka:/home/mrgeneration# apt-get install zammad
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  autotools-dev binutils bzip2-doc cpp cpp-6 gcc gcc-6 libasan3 libatomic1 libbz2-dev libc-dev-bin libc6 libc6-dev libcc1-0 libcilkrts5 libdpkg-perl libfile-fcntllock-perl libfreetype6-dev libgcc-6-dev libgif-dev libgomp1 libid3tag0 libid3tag0-dev libimlib2 libimlib2-dev libisl15 libitm1 libjbig-dev libjpeg-dev libjpeg62-turbo-dev liblsan0 libltdl-dev
  libltdl7 liblzma-dev libmpc3 libmpfr4 libmpx2 libpng-dev libpng-tools libpthread-stubs0-dev libquadmath0 libtiff5-dev libtiffxx5 libtool libtsan0 libubsan0 libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev libxext-dev linux-libc-dev manpages manpages-dev pkg-config x11proto-core-dev x11proto-input-dev x11proto-kb-dev x11proto-xext-dev
  xorg-sgml-doctools xtrans-dev zlib1g-dev
Suggested packages:
  binutils-doc cpp-doc gcc-6-locales gcc-multilib make autoconf automake flex bison gdb gcc-doc gcc-6-multilib gcc-6-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan3-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx2-dbg libquadmath0-dbg glibc-doc debian-keyring patch libtool-doc liblzma-doc automaken gfortran
  | fortran95-compiler gcj-jdk libxcb-doc libxext-doc man-browser
The following NEW packages will be installed:
  autotools-dev binutils bzip2-doc cpp cpp-6 gcc gcc-6 libasan3 libatomic1 libbz2-dev libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libdpkg-perl libfile-fcntllock-perl libfreetype6-dev libgcc-6-dev libgif-dev libgomp1 libid3tag0 libid3tag0-dev libimlib2 libimlib2-dev libisl15 libitm1 libjbig-dev libjpeg-dev libjpeg62-turbo-dev liblsan0 libltdl-dev libltdl7
  liblzma-dev libmpc3 libmpfr4 libmpx2 libpng-dev libpng-tools libpthread-stubs0-dev libquadmath0 libtiff5-dev libtiffxx5 libtool libtsan0 libubsan0 libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev libxext-dev linux-libc-dev manpages manpages-dev pkg-config x11proto-core-dev x11proto-input-dev x11proto-kb-dev x11proto-xext-dev xorg-sgml-doctools
  xtrans-dev zlib1g-dev
The following packages will be upgraded:
  libc6 zammad
2 upgraded, 62 newly installed, 0 to remove and 31 not upgraded.
Need to get 147 MB of archives.
After this operation, 157 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
1 Like

The long story short doesn’t work:

zammadadmin@zammad:~$ sudo apt-get install zammad
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 zammad : Hängt ab von: libimlib2 ist aber nicht installierbar
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.