On Tue, Jul 6, 2021 at 1:19 AM Otto Kekäläinen <o...@debian.org> wrote:
>
> On Mon, Jul 5, 2021 at 1:12 PM Olaf van der Spek <m...@vdspek.org> wrote:
> >
> > On Mon, Jul 5, 2021 at 9:24 PM Otto Kekäläinen <o...@debian.org> wrote:
> > > I wish somebody could contribute with exact steps on how to reproduce
> > > the issue. So far I've gotten some half attempts at that but they
> > > haven't been actionable for me.
> >
> > Hi Otto,
> >
> > I'd point to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988089
> > Not sure why it's not reproducible with those steps.
>
> I don't see *the* steps, but I see a lot of messages about many
> different steps. If you have them, why not copy-paste the steps here
> in email so I can copy-paste them into a Debian Buster Docker
> container and run the upgrade to isolate the regression?
Docker might be the problem, I'd try a real VM.
I do have this in a VM so I think we can easily repro this.
// Fresh VM install from debian-10.9.0-i386-netinst.iso
# history
1 visudo
2 rm /etc/motd
3 poweroff
4 apt install mariadb-server
5 dpkg -l|grep mariadb
6 sed -i 's/buster/bullseye/g' /etc/apt/sources.list
7 apt update
8 apt upgrade
9 apt dist-upgrade // output below
10 dpkg -l|grep mariadb // output below
11 apt dist-upgrade // output below
12 history
--
Olaf
