[debian-mysql] Bug#1010372: Bug#1010372: mysql-8.0: Should mysql-8.0 be removed from unstable?

[Salvatore Bonaccorso]

Control: forcemerge 1004180 1010372

Hi Robie,

On Tue, May 03, 2022 at 04:51:54PM +0100, Robie Basak wrote:
> Hi Salvatore,
> 
> On Fri, Apr 29, 2022 at 09:52:04PM +0200, Salvatore Bonaccorso wrote:
> > Should mysql-8.0 be dropped completely from the archive or is there
> > still interest in keeping in in unstable?
> 
> I think this is a dupe of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004180? Was asking
> again intentional?

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.

> 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?

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