Hi

I noticed that mysql-8.0 is still in unstable with a quite ancient
version not having updated now for several Oracle CPU rounds.

Should mysql-8.0 be dropped completely from the archive or is there
still interest in keeping in in unstable?

There are in unstable two packages which will have broken
Build-Depends, thus CC'ing the interested parties as well.

myodbc: libmysqlclient-dev (>= 5.5.17)
pytest-services: mysql-testsuite-8.0

If you do agree on the removal, please reassign the bug against
ftp.debian.org (and asking as well for removing of the packages with
broken build-depends).

Regards,
Salvatore

Hi Salvatore,

I think this is a dupe of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004180? Was asking
again intentional?

My answer is the same - we'd like to keep mysql-8.0 in unstable and are
working on updating unstable and getting Ubuntu back into sync against
Debian.

At Canonical, I am onboarding a colleague who will be working on this.
Prompted again by you, we just set ourselves a goal of having this done
by the end of the month, if that's OK with you?

Thanks,

Robie

Hi Robie,

Ah, no sort of combination of a) human error, b) triggering the
question given there was no movement since some Oracle CPUs on the
version. Let's merge the both.

Okay. but then I hope this can happen soon. As said above I did forgot
I already asked, and did overlook we had already #1004180, but my
worry is still the same. Even if it's only in unstable, the current
list from
https://security-tracker.debian.org/tracker/source-package/mysql-8.0
is getting huge.

Thanks in any case if you pick it up and keep then unstable and get
back on track for the version.

Regards,
Salvatore

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.