Package: tango-db Severity: important X-Debbugs-Cc: pi...@debian.org Dear Maintainer,
I upgraded a computer from bullseye to bookwork. tango-db was installed with the bulleyes version before the upgrade. The upgrade went fine, so I installed the tango-starter (bookworm version). BUT the tango-starter could not register in the database. So I wipeout all of tango-xxx, remove the sql database. then I re-installed the tango-db and tango-starter. This time the starter worked out of the box. In fact I was affected by this https://gitlab.com/tango-controls/TangoDatabase/-/issues/69 the fresh install script of the sql databse and the upgrade scripts used by dbconfig-common, does not produce the same sql database at the end. the new create_db_tables was modified like this https://gitlab.com/tango-controls/TangoDatabase/-/merge_requests/82/diffs So during the upgrade the tables should be alter to take into account this modification. https://gitlab.com/tango-controls/TangoDatabase/-/issues/26 the bug is triggered only because mariadb changed it's behaviour between bullseye and bookworm. It would be great to fix bookworm. thanks Frederic -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tango-db depends on: pn dbconfig-mysql | dbconfig-no-thanks <none> ii debconf [debconf-2.0] 1.5.85 ii init-system-helpers 1.66 ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libmariadb3 1:10.11.6-2 pn libomniorb4-3 <none> pn libomnithread4 <none> ii libstdc++6 14-20240201-3 pn libtango-tools <none> pn libtango95 <none> Versions of packages tango-db recommends: pn default-mysql-client <none> tango-db suggests no packages.
