On 15.01.25 13:59, Damyan Ivanov wrote:
Control: tags -1 +confirmed
-=| Matthias Klose, 15.01.2025 12:10:44 +0100 |=-
Package: src:firebird4.0
Version: 4.0.5.3140.ds6-6
Is the firebird4.0-common breaking firebird3.0-common necessary?
Not really. Thanks for finding that out.
firebirdXX-common packages contain only files in version-specific
directories, so co-installing them should be possible.
I'm just asking how people are supposed to upgrade databases, if
those packages are not installable in parallel.
Note that the Breaks: is versioned. One would need the experimental
firebird3.0 packages to get both installed at the same time.
The option to install more than Firebird version is new and not
available in unstable.
During previous migrations, one had to create backups of all databases
with old firebird tools, upgrade, then restore all the backups with
the new tools. And hope everitying goes well. Alternatively, get
another box/VM with the new version and do the
backup/restore/fix/repeat until success.
We found, that migrating the package to the release/testing pockets
needs
the breaks removed. See
http://launchpadlibrarian.net/770673070/firebird4.0_4.0.5.3140.ds6-6_4.0.5.3140.ds6-6ubuntu1.diff.gz
I'll remove the -common Breaks, but that still won't allow firebird3.0
from Debian/unstable and firebird4.0 from Debian/experimental to
co-exist because the unstable's firebird3.0 is simply not prepared for
it.
The major drawback is, that you probably would need to package both icu
74 and 76 to be in the distro, or make fb3.0 building with C++17.
