Your message dated Wed, 27 May 2026 07:38:38 +0000
with message-id <[email protected]>
and subject line Bug#1137775: fixed in rtpengine 26.0.1.10-1
has caused the Debian Bug report #1137775,
regarding rtpengine: Please drop dependencies on virtual packages from
mysql-defaults
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1137775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137775
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rtpengine
Severity: normal
Control: affects -1 + src:mysql-defaults
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 rtpengine in Debian!
[1] https://lists.debian.org/debian-devel/2026/05/msg00161.html
--- End Message ---
--- Begin Message ---
Source: rtpengine
Source-Version: 26.0.1.10-1
Done: Victor Seva <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rtpengine, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Victor Seva <[email protected]> (supplier of updated rtpengine 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 27 May 2026 08:58:49 +0200
Source: rtpengine
Architecture: source
Version: 26.0.1.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team <[email protected]>
Changed-By: Victor Seva <[email protected]>
Closes: 1137775
Changes:
rtpengine (26.0.1.10-1) unstable; urgency=medium
.
* d/watch: version 5, switch to mr26.0 LTS series
* New upstream version 26.0.1.10
* switch to libmariadb-dev-compat (Closes: #1137775)
Checksums-Sha1:
02d6d390b9ef7e9db7f954b77b8c47caafd4e238 3194 rtpengine_26.0.1.10-1.dsc
74fdf1dab4e51c0d4399beee32c8b14b094801c6 6987707
rtpengine_26.0.1.10.orig.tar.gz
6dff41880249f703352c5ab9571ba73ea9a427f5 15108
rtpengine_26.0.1.10-1.debian.tar.xz
0249441691e7570495af9f5a16dbd72b05dbd133 19164
rtpengine_26.0.1.10-1_amd64.buildinfo
Checksums-Sha256:
3dde4aa54b1fce52d94fad2eb9d673849d0c7e3410bf4df0360dacbf82c5d64e 3194
rtpengine_26.0.1.10-1.dsc
bb2fabfee15ecdb4a375fa8b9d20425ae6568e4ed413eac3dadf5df37b4f2f3b 6987707
rtpengine_26.0.1.10.orig.tar.gz
76870f99ea83628f1739e87d29d12c70f09362aff26fc534a2a99b32ced6aebf 15108
rtpengine_26.0.1.10-1.debian.tar.xz
d014db31f2ab4c0b1a908be40f0545929f93b81a16ec062cd775b15180f7ffda 19164
rtpengine_26.0.1.10-1_amd64.buildinfo
Files:
63fd979a5ba7b79aca3c27e8769a5b64 3194 net optional rtpengine_26.0.1.10-1.dsc
cb169e143dc0d6244a63afaeb6f58046 6987707 net optional
rtpengine_26.0.1.10.orig.tar.gz
b562afbf1a4c96a5dd7c8152885c620f 15108 net optional
rtpengine_26.0.1.10-1.debian.tar.xz
acce23b9de6585db145591309dd15ec5 19164 net optional
rtpengine_26.0.1.10-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iIcEARYKAC8WIQQq6AO8RS0zF4SC1vh9e2XEKg7IsgUCahaXuREcdnNldmFAZGVi
aWFuLm9yZwAKCRB9e2XEKg7Issm8AP94LBJqKwcCMVv0eJBrvOTGfxAEnMRsdBN1
+cqvbPvQjgEA+FBmXyRYeODLG/J5WecJiL8jKAR3nUpYZOAa0r/wXQo=
=EmX8
-----END PGP SIGNATURE-----
pgpVWIjob8DDJ.pgp
Description: PGP signature
--- End Message ---
