Dear Maintainer,

Following a recent discussion on debian-devel@[1], there is a plan to dismantle
the default-mysql-* virtual package construct provided by the mysql-defaults
source package. With the recent releases of MySQL 9.7 and MariaDB 12.3, there is
now enough divergence between the two codebases to warrant dismantling this
metapackage in the Forky (Debian 14) cycle.

This is filed with severity 'normal' as this change is not urgent.

We are asking maintainers to drop any dependencies on these virtual packages:
* default-libmysqlclient-dev
* default-mysql-client
* default-mysql-client-core
* default-mysql-server
* default-mysql-server-core

However, how this is handled in is in your discretion based on the details of
how the package is maintained and tested in Debian. There are mainly three
options:

- Direct switch: The most straightforward approach is to switch defaut-mysql-*
  directly to the MariaDB equivalent (libmariadb-dev, libmariadb-dev-compat,
  mariadb-client, mariadb-server, etc). For example 'Recommends: mariadb-server'.

- Dual compatibility: If the package actively supports both engines and you wish
  to keep an alternative runtime path open for users drawing from third-party
  repositories, you can declare an OR dependency. For example
  'Depends: mariadb-client | mysql-client'.

- Specific constraint: If your package does not work with MariaDB, feel free to
  tailor the package relationships to match that constraint. This is however
  very unlikely as all Debian releases in past decade have only shipped with
  MariaDB, and the open source ecosystem has largely shifted to lean towards
  MariaDB.

This change is targeted specifically for the Forky cycle and does not affect any
existing stable releases.

Thank you for your time and your work maintaining motion in Debian!

[1] https://lists.debian.org/debian-devel/2026/05/msg00161.html

Hello,

This bug has been open for several months. Just wondering if there is any
particular reason it hasn't been done or if it is just in general due to lack of
maintainer time?

This is not urgent, just checking..

- Otto

Hello,

Thank you for the reminder, I thought it was already pushed...

I've prepared a new package motion 4.7.1-2, should be fixed soon

/Nicolas

We believe that the bug you reported is fixed in the latest version of
motion, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1137740@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Mora <babelouest@debian.org> (supplier of updated motion package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 17 Sep 2026 17:25:48 -0400
Source: motion
Architecture: source
Version: 4.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Mora <babelouest@debian.org>
Changed-By: Nicolas Mora <babelouest@debian.org>
Closes: 1127746 1137740
Changes:
 motion (4.7.1-2) unstable; urgency=medium
 .
   [Thadeu Lima de Souza Cascardo]
   * d/patches: Apply fix_file_leak.patch (Closes: #1127746)
 .
   [Nicolas Mora]
   * d/control: Remove Priority: Optional
   * d/control: Update standards version to 4.7.4
   * d/control: Update debhelper compat version to 14
   * d/control: use libmariadb-dev-compat instead of default-libmysqlclient-dev
     (Closes: #1137740)
   * d/motion.install: Add install file to comply with debhelper 14
   * d/patches: Add glibc-2.43.patch to fix glibc 2.43 warnings
   * d/rules: Update motion.conf rename path to comply with debhelper 14
Checksums-Sha1:
 b6bb5132fd8d82abc9b8c33e3d49f68092c81e7b 2088 motion_4.7.1-2.dsc
 f593875cfafd979ed37e30454eff790d7d7ba01b 822351 motion_4.7.1.orig.tar.gz
 a4391e399b13f0c71a6ab51a788ec7870ddc13c3 20024 motion_4.7.1-2.debian.tar.xz
 b78ed9f25dc10c78843218c243e32207ac285988 12011 motion_4.7.1-2_amd64.buildinfo
Checksums-Sha256:
 bc09dba42e0b8e87cb6af4df85dbea26af09e0f37889b4213aed91e72e0f87d8 2088 motion_4.7.1-2.dsc
 c11f68c7cea949227e57797b932f01432d8942ef5323c75063d19b951d0d4194 822351 motion_4.7.1.orig.tar.gz
 4cb07189b74e6689e765aadaeb5ac983e5f5b3c282e7ff207c3eecd1d110c279 20024 motion_4.7.1-2.debian.tar.xz
 7c10d005bc58553066f83762d0b9536d91ff94b316b0759320331103262eaf76 12011 motion_4.7.1-2_amd64.buildinfo
Files:
 fe6b5cdd46f3c61d91981df58f4eb669 2088 video optional motion_4.7.1-2.dsc
 e9ea9eecebd2f3f5919db14d06077016 822351 video optional motion_4.7.1.orig.tar.gz
 302517d350570f9d1c7efbe656484655 20024 video optional motion_4.7.1-2.debian.tar.xz
 961ca5f3305a3398359d5b51334ce1c8 12011 video optional motion_4.7.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEhAWwL8wo75dEyPJT/oITlEC9IrkFAmqv+F0ACgkQ/oITlEC9
IrnrqA//fYdNysUhtjKg2kudMjapEfs2mxMp8VaJazw3g+2JkHPJP1i7VffdwPU5
qj28RPeoqVUH1gr0UJceIhW8O3H2pe5wrdwI3vkoeCiDlsxNIv8ZKF4lMWdRDRlw
HQptFkK0WsyerPyI+NwB3GY9GNSt39NKrEuFLRwSmwKqR3b74HTqT4E9CHZiQxiE
cJRB1DtDVbKEKGaR5/IU77mQt0fCjiApr2vvdEBnTY0h2OBjOrhJj44Hu97suOcS
2DR4/0yjw/wV0RUyiGouGhyqG4ZSuYW4z6aVKUc+4Md1vhya8GsOfBSSv7TlGssQ
U+5HprhfjKUB7bH7b+FNPDnNVCyxI5FeXR2W6U8Pog8SQvVqW0kCiismK6sHn69y
4/VrbdJSetstcAImP8+ubyEm+u76bCisbdT5H8XpQL3aqkLxKkVwwgVHinUrdZIq
+yxkEkLGX3+0VhXLs5QylexLE/ptzwjYlsEIySdCBgGBq49xDMqXIcRSpIK19b+I
1tpZvP8QXRo0CIXvYxwqA7gHz+d43lOc5mCB6yvsEdF7x6XVtJo675k7Xj4ko3Lf
jcMfrD0Ix1/4O1noHY7Tz8m7EsrSwN3Zpc/MZXEUd2SQQZVjRfKEcmApHnNQRDNB
oZmtZHDf5mcTplzFrUlPMWuXo4+wh/AlHuReVUYIKAwBLjstz20=
=HlbJ
-----END PGP SIGNATURE-----