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

Hi,

This is on me. I've been working on getting updates ready, but let
myself get bogged down with more long-running updates to the packaging
(which is pretty outdated with regards to things like the standards
version).

I'd like to make a better effort to keep it up-to-date (just focusing on
keeping MySQL itself updated for now, I think).

Hi Lars,

Alright, thank you! In this case please feel free to close this
bugreport.

Regards,
Salvatore

FWIW, we started a renewed effort to catch up and stay caught up - for
example I cherry-picked a fix to the master branch in Salsa recently,
and further picks from Ubuntu to catch up security-wise should be coming
soon.

So hopefully we'll be doing much better soon.

#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.