Your message dated Mon, 21 Sep 2026 13:43:07 +0000
with message-id <[email protected]>
and subject line Bug#1116680: Removed package(s) from unstable
has caused the Debian Bug report #1137776,
regarding trafficserver: 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.)


-- 
1137776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137776
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: trafficserver
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 trafficserver in Debian!

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

--- End Message ---
--- Begin Message ---
Version: 9.2.5+ds-1+rm

Dear submitter,

as the package trafficserver has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1116680

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to