Hi Jochen, Am Samstag, dem 19.02.2022 um 21:21 +0100 schrieb Jochen Sprickerhof: > Hi Markus, > > thanks for your quick reply. > > * Markus Koschany <a...@debian.org> [2022-02-19 21:01]: > > That means only hibiscus/jameica require our attention. I would try to > > remove > > the obsolete connection setting mentioned in #1005838. > > Tried that already, did not solve the problem.
Ok. Did you file an upstream bug report already? > > > You could also try to > > dump the SQL database with the current version in stable and then try to > > re- > > import the SQL tables with H2 in unstable. That should actually work > > because > > the SQL syntax will not have changed. (See also the Upgrading paragraph > > here > > https://h2database.com/html/migration-to-v2.html) > > That would be the plan, yes. But for that we would need to provide both > versions to our users, thus I propose to upload the new version as a new > source and binary package. > > Also the SQL syntax did change. [...] > Can you explain how you want to implement this re-import feature then? I don't think the SQL syntax itself did change. SQL is a separate language and different SQL databases must be compatible in this regard. MySQL, MariaDB, hsqldb, H2, they all should be able to read and write SQL. If H2 changed some H2 specific commands, then all we have to do is to execute a command for the old H2 database to dump the old database and then use another command to re- import the database into H2 2.x. The old version of H2 is already present in Ubuntu or Debian stable. You could either ask users to execute all those commands manually (README.Debian, Debian.NEWS) or there could be some kind of pre/post hook script that does all that automatically. I would try to solve that problem on the package level though, and ask upstream to come up with a migration plan because sticking with 1.4.x forever is not a great plan. > I would really appreciate a quick solution here so users of the next > Ubuntu version would not be locked out of their homebanking system. > > I'm happy to help with uploading new versions and NEW is rather empty > currently so I don't see the point in not doing a proper transition > here. For a quick solution you could upload 1.4.197 again based on the version in Bullseye but this doesn't really solve the problem. As I said we don't need multiple H2 versions in Debian. You should only do that if you are willing to support an officially unsupported piece of software for the next Debian 12 LTS cycle until the year 2028. And that means taking care of all other libh2-java dependencies too, dealing with people who request an upgrade to 2.x because their use case depends on it, etc. And you and the rest of the users should be fine with the disabled H2 console and all the other bugs in that version.
signature.asc
Description: This is a digitally signed message part
