Closed seederp2p closed 1 month ago
Sorry, but this seems to be a technical question. Please note that this repository is the wrong place for technical questions. Instead, please refer the Zammad community over at: https://community.zammad.org .
In case this turns out the be a bug and no technical question, we'll transfer the relevant information to this repo!
If you require commercial grade support and are no hosted or support contract customer, you can check out our support contracts here: https://zammad.com/pricing#selfhosted If you're paying customer already, please consult your Zammad support for assistance! :-)
Used Zammad Version
6.3.1
Environment
Actual behaviour
I had upgrades pending for zammad but also:
postgresql-16/noble-updates 16.4-0ubuntu0.24.04.2 amd64 postgresql-client-16/noble-updates 16.4-0ubuntu0.24.04.2 amd64
Doing a apt-get dist-upgrade -y gave this error:
As this was a VM, I just reverted to a previous snapshot and did:
sudo apt-mark hold postgresql-16 postgresql-client-16
so this packaged wouldn't upgrade. After that I went:
And zammad upgraded successfully.
After that I did:
sudo apt-mark unhold postgresql-16 postgresql-client-16
and
And everything went fine.
I don't know if this is documented and can be somehow improved in terms of the upgrade process via apt-get
Expected behaviour
apt-get dist-upgrade -y shouldn't break the current install
Steps to reproduce the behaviour
As described
Support Ticket
No response
I'm sure this is a bug and no feature request or a general question.
yes