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…
```auto
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.
```
```auto
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:
> [@Upgrading Zammad 3.6.0/Debian 9-Stretch to Zammad 5.0/Debian 10-Buster](https://community.zammad.org/t/upgrading-zammad-3-6-0-debian-9-stretch-to-zammad-5-0-debian-10-buster/7989):
>
> Infos: Used Zammad version: 3.6.0 Used Zammad installation type: package Operating system: Debian 9 Stretch Browser + version: Chrome 95.x Expected behavior: Clean package upgrade zammad 3.6.0/debian 9 to zammad 5.0/debian 10 Actual behavior: What things to check before upgrading the whole system ? Need a little advise before starting … Steps to reproduce the behavior: Is this the right way? Backup the complete system Upgrading debian 9 to latest debian 9 Upgrading zammad Debian dist…
What to do? Or is this just a bug and everyhing is fine?
---
### Author:  [@justeverything](https://community.zammad.org/u/justeverything)
#### Post date: [August 16, 2023, 12:01pm UTC](https://community.zammad.org/t/distupgrade-debian-buster-to-bullseye-zammad-still-shows-buster-version/11990/2 "2023-08-16T12:01:43Z")
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?
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [August 16, 2023, 12:10pm UTC](https://community.zammad.org/t/distupgrade-debian-buster-to-bullseye-zammad-still-shows-buster-version/11990/3 "2023-08-16T12:10:46Z")
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
```auto
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.
---
### Author:  [@justeverything](https://community.zammad.org/u/justeverything)
#### Post date: [August 16, 2023, 12:26pm UTC](https://community.zammad.org/t/distupgrade-debian-buster-to-bullseye-zammad-still-shows-buster-version/11990/4 "2023-08-16T12:26:07Z")
sounds good to me, thanks alot for clarifying! 🙂
---
### Author:  [@system](https://community.zammad.org/u/system)
#### Post date: [August 23, 2023, 12:26pm UTC](https://community.zammad.org/t/distupgrade-debian-buster-to-bullseye-zammad-still-shows-buster-version/11990/5 "2023-08-23T12:26:29Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.