After some discussion on Matrix, it turns out that the above "fix" is a
bad fix. The gist is that Debian uses mariadb, and Ubuntu uses mysql. My
fix forces GRASS to use mariadb, against the Ubuntu way!
Currently, mariadb and mysql are kinda-sorta-mostly compatible, but over
time they will become less compatible. GRASS' autopkgtests pass *now*
with the fix, but as time goes on the APIs may become incompatible in a
way that breaks the autopkgtests.
The real fix is to make libgdal use mysql instead of mariadb.
(libmariadb-dev-compat comes via libgdal.)
Thank you @lvoytek!
** Summary changed:
- Stonking migration FTBFS
+ GRASS Stonking migration FTBFS
** Also affects: gdal (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdal (Ubuntu)
Status: New => In Progress
** Changed in: gdal (Ubuntu)
Assignee: (unassigned) => Petrichor Park (petrakat)
** Changed in: gdal (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2164949
Title:
GRASS Stonking migration FTBFS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/2164949/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
