Package: Missing backup files for files with the same content

[rolfschmidt]

Used Zammad Version

6.2

Environment

• Installation method: [e.g. source, package]
• Operating system (if you're unsure: cat /etc/os-release ): [e.g. debian 10.4, ubuntu 20.04]
• Database + version: [e.g. postgresql 9.3, mysql 5.7, mariadb 10.3]
• Elasticsearch version: [e.g. 7.17]
• Browser + version: [e.g. chrome 83, safari 14, firefox 105]

Actual behaviour

Currently, files with the same content will not create backup files.

This leads to an invalid state, especially when you have a backported feature which then get released and the system gets upgraded. The file already does exist with the same content, so there is no backup file. If then the developer decides to remove the file from the package because it is not necessary any more, then the core file will get deleted not restored by the backup file because there is none.

Expected behaviour

Always create backups for package files.

Steps to reproduce the behaviour

• Backport feature
• Update system after a couple of months
• Remove the backport of the file which now exists in the core from the package

Support Ticket

Ticket#10149686

I'm sure this is a bug and no feature request or a general question.

yes