Distupgrade debian buster to bullseye - zammad still shows buster version

Technical assistance
1

Infos:

  • Used Zammad version: This is Zammad version 6.0.0-1692176490.0e2399eb.buster
  • Used Zammad installation type: package
  • Operating system: Debian 11
  • Browser + version: Firefox // any browser

Expected behavior:

  • This is Zammad version 6.0.0- [...] .bullseye should be shown instead of This is Zammad version 6.0.0-1692176490.0e2399eb.buster

Actual behavior:

  • This is Zammad version 6.0.0-1692176490.0e2399eb.buster is displayed.

Steps to reproduce the behavior:

  • upgraded debian 10 to latest version, updated zammad from 5.x to 6.0.0…buster
  • dist-upgrade from debian 10 to 11 while changing the /apt/sources.list
  • rebooted machine
  • changed zammad.list from deb https://dl.packager.io/srv/deb/zammad/zammad/stable/debian 10 main to deb https://dl.packager.io/srv/deb/zammad/zammad/stable/debian 11 main
  • tried several thingsto update or reinstall, but zammad still shows buster (but is running)

More things that I tried:

apt cache show zammad

root@ticket:/ apt-cache show zammad
Package: zammad
Status: install ok installed
Priority: optional
Section: default
Installed-Size: 521259
Maintainer: support@packager.io
Architecture: amd64
Version: 6.0.0-1692176490.0e2399eb.buster
Provides: zammad
Depends: libpq5, libsqlite3-0, openssl, libxml2, libxslt1.1, curl, elasticsearch | elasticsearch-oss, nginx | apache2, postgresql | mariadb-server, libimlib2, shared-mime-info, redis-server
Conffiles:
 /etc/default/zammad d97ce9ecd137d8b45d55278a5c2c9175
 /etc/logrotate.d/zammad f3670cdeb478391573b53db98a6bc0ff
Description: Zammad is a web based open source helpdesk/customer support system
Description-md5: a57c5e55d3ec7da3ef8af7f15126049d
License: unknown
Vendor: Packager.io <https://packager.io>
Homepage: https://zammad.org

Package: zammad
Filename: pool/main/zammad_6.0.0-1692176490.0e2399eb.bullseye_amd64.deb
Size: 152592704
MD5sum: 4dad3c3c5d3e57a41d904c2cd0dc0ca6
SHA1: 7ea00267a44952af843c20c7705db402a286f056
SHA256: 0aba9ef9c76f8c0214989a27064aac8b5f3755be7edf82a31d629346bd0c5d73
Version: 6.0.0-1692176490.0e2399eb.bullseye
License: unknown
Vendor: Packager.io <https://packager.io>
Architecture: amd64
Maintainer: support@packager.io
Installed-Size: 536622
Depends: libpq5, libsqlite3-0, openssl, libxml2, libxslt1.1, curl, elasticsearch|elasticsearch-oss, nginx|apache2, postgresql|mariadb-server, libimlib2, shared-mime-info, redis-server
Provides: zammad
Section: default
Priority: optional
Homepage: https://zammad.org
Description: Zammad is a web based open source helpdesk/customer support system
Description-md5: a57c5e55d3ec7da3ef8af7f15126049d

note: ther eis more output, cut this here…

root@ticket:/ apt update
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://security.debian.org/debian-security bullseye-security InRelease
Hit:5 https://artifacts.elastic.co/packages/7.x/apt stable InRelease
Hit:6 http://apt.postgresql.org/pub/repos/apt buster-pgdg InRelease
Get:7 https://dl.packager.io/srv/deb/zammad/zammad/stable/debian 11 InRelease [1,845 B]
Hit:8 http://apt.puppetlabs.com bullseye InRelease
Hit:9 https://apt.puppet.com buster InRelease
Fetched 4,957 B in 1s (6,089 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

root@ticket:/ sudo apt install --reinstall zammad
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Reinstallation of zammad is not possible, it cannot be downloaded.

Note: with that command I’m sticking to another community post:

What to do? Or is this just a bug and everyhing is fine?

2

I have fixed it by running apt remove zammad and apt install zammad. Zammad now shows the expected version This is Zammad version 6.0.0-1692176490.0e2399eb.bullseye
The sudo apt install --reinstall zammad did not work because it wanted to reinstall the buster version, whose line was not in the /etc/apt/sources.list.d/zammad.list file anymore, so that failed ofc.

The above commands just removed zammad, after the new installation zammad found the database file itself and “recovered” all settings and data. Nevertheless I always do snapshots of a VM before doing something like this, so I was safe.

maybe it helps someone else - but is this really “the way” to do it?

3

The “problem” is the update process during a dist upgrade itself.
You ensure all packages have the latest patch level on the current system (including Zammad).
Then you’re changing sources, upgrade them and then dist-upgrade.

And this is where the issue appears.
Within that short period of time there’s no new version of Zammad.

Due to the way our version numbers are generated, you end up in

6.0.0-1692176490.0e2399eb.buster
6.0.0-1692176490.0e2399eb.bullseye

those versions. Versioning is done alphabetical. So buster vs bullseye apart from the rest of the version string being the same is your issue. A forced reinstallation like you did is the correct way to do it. Technically, theoretically you could hold the Zammad package via package manager, stop and disable Zammad before upgrading and and change the repo file after rebooting.

That should allow you to upgrade to a newer Zammad version. That is, if there’s one available.

4

sounds good to me, thanks alot for clarifying! :slight_smile:

1 Like
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.