Your message dated Wed, 27 May 2026 11:49:19 +0000
with message-id <[email protected]>
and subject line Bug#1137783: fixed in rmysql 0.11.3-2
has caused the Debian Bug report #1137783,
regarding rmysql: 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.)
--
1137783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137783
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rmysql
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 rmysql in Debian!
[1] https://lists.debian.org/debian-devel/2026/05/msg00161.html
--- End Message ---
--- Begin Message ---
Source: rmysql
Source-Version: 0.11.3-2
Done: Dirk Eddelbuettel <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rmysql, 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.
Dirk Eddelbuettel <[email protected]> (supplier of updated rmysql 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: SHA256
Format: 1.8
Date: Wed, 27 May 2026 06:29:09 -0500
Source: rmysql
Architecture: source
Version: 0.11.3-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel <[email protected]>
Changed-By: Dirk Eddelbuettel <[email protected]>
Closes: 1137783
Changes:
rmysql (0.11.3-2) unstable; urgency=medium
.
* debian/control: As Debian switches from 'default-libmysqlclient-dev'
now use just libmariadb-dev-compat (Closes:
#1137783)
* debian/control: Set Build-Depends: to current R version
Checksums-Sha1:
0ef7d89d6c7dedfd00191c31e916b0aae00cdc36 1867 rmysql_0.11.3-2.dsc
f79908d190c0e8ad576422e50cc478432ae6aabb 4020 rmysql_0.11.3-2.debian.tar.xz
158816cd56daf77ae64b5e3940527253f29ad68b 10479 rmysql_0.11.3-2_amd64.buildinfo
Checksums-Sha256:
8462dcc17774dcfb79f0b7e6d1340ebe21ad6240d9d966ca072e4747e88fe403 1867
rmysql_0.11.3-2.dsc
dea1ab6a622a4522c1905ea473a0fc4212ecdedc5e28c13f07861cd983f6d087 4020
rmysql_0.11.3-2.debian.tar.xz
6cd4a2801668de74aae83ae8f5b9d6d113058ca9037ea14dc3f0ecc35737b41f 10479
rmysql_0.11.3-2_amd64.buildinfo
Files:
ba6ebeaea39a50325fa222b1e59721e1 1867 gnu-r optional rmysql_0.11.3-2.dsc
d1823c4286ad62cddcc1572e8269bfa0 4020 gnu-r optional
rmysql_0.11.3-2.debian.tar.xz
7799d2b508d3c14ad95a7caed3133112 10479 gnu-r optional
rmysql_0.11.3-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIVAwUBahbXgKFIn+KrmaIaAQg7WBAAsqdbdlmIQ2kbvAdv6Hjt03LVDfBeQEtu
zxw5wod/+HJzWmdPPkMEJ+f9htFz2RkY1+ojzOrHaXz1atcYIiefHq7YRJQBnzGb
5OWfP4ceBzIbOEOdjWuelNEFHhT22sZR/92gS4GNTtIb1WuyW5imTnRNTfzNttit
wIOXZzhRsW2FgZuwTPrtLp4OFiC1IUmWfarf4fI2EslNxxmrvpb5jqzr/u4OeeVO
a5/IxyL2+lAQ5rguxqluZN4AxyNv0gQ3Ii7PToM/mFVzJ2DyBpbxoAIy5hscaMsj
IuKxQ5nMKCD0SsQiF9Cy22XpHgzhcKx01DGxzGDTZuS/SQHo3CrrrNi41Ejv21pN
1ycRO4LevWyex84R8DObfgPMgL9ckE8f4KgcuwJwSfWr3AKk+rCAkrdQJ9kqDxf/
NZJGHL+K18qZ4m6YEDso19SpSAFLATHYxjCqRQHGbOlbHbdg/xeWliQgyhA64jx4
ZbBKTZjE/an1c/B+JDDXKw+HiaqMZbatkeQUtQ7o1COScSDsLkA1zHBBf+AthkIY
C134y/4MxwnXrk2z9HbSyWccaLA4JFJWOjQbm8HW3WRYPAm+WKBQ866ODUvlYAck
zx+2n/DFrII5JRDlz/BjsZRFpO8TcaiTCVMeCJcRfAmT2hV0eGca167RttUMs6yt
m8944lL5wT4=
=upUE
-----END PGP SIGNATURE-----
pgpdyZrgM0dty.pgp
Description: PGP signature
--- End Message ---
