Your message dated Fri, 1 Jul 2022 17:04:29 +0100
with message-id <[email protected]>
and subject line Re: [debian-mysql] Bug#1004180: mysql-8.0: should mysql-8.0 be
removed from unstable?
has caused the Debian Bug report #1004180,
regarding mysql-8.0: should mysql-8.0 be removed from unstable?
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.)
--
1004180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004180
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mysql-8.0
Version: 8.0.23-3
Severity: normal
X-Debbugs-Cc: [email protected],
[email protected],[email protected], [email protected]
Hi
While mysql-8.0 itself won't enter testing, the version in unstable is
as well only from february 2021, lacking behind several updates for
fixes in the Oracle CPUs.
Should mysql-8.0 be removed as well from unstable?
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
On Fri, Jul 01, 2022 at 05:53:31PM +0200, Bastian Germann wrote:
> #853008 blocks mysql-8.0 from migrating to testing.
> If you want to stay true to your promise you might want to have a look at
> that.
I don't think it's reasonable to consider this to be the responsibility
of MySQL packaging maintainers alone. The problem was introduced when
MariaDB packaging was added to Debian (and caused by it), prior to my
involvement.
I hope that over time we will be able to improve the situation described
in that bug, but it's not part of any promise I have made or intend to
make.
In the meantime, we are now reasonably caught up with mysql-8.0 in
unstable, so I'm closing this bug as done.
signature.asc
Description: PGP signature
--- End Message ---
