[debian-mysql] Bug#866983: Bug#866983: Bug #866983 Appears fixed in 10.1.25-1

Faustin Lammler faustin at fala.red
Thu Aug 9 13:34:30 BST 2018

Hi Otto,
I can not reproduce this.

Upgrade from:
	- 10.1.23-9+deb9u1 to 10.1.24-6 > OK
	- 10.1.23-9+deb9u1 to 10.1.34-1 > OK

This was added to my sources.list:
deb [check-valid-until=no] http://snapshot.debian.org/archive/debian/20170624T094211Z/ buster main non-free contrib
deb [check-valid-until=no] http://snapshot.debian.org/archive/debian/20171009T041837Z/ buster main non-free contrib

$ apt-cache policy mariadb-server-10.1
  Installed: 1:10.1.34-1
  Candidate: 1:10.1.34-1
  Version table:
 *** 1:10.1.34-1 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
        100 /var/lib/dpkg/status
     10.1.24-6 500
        500 http://snapshot.debian.org/archive/debian/20170826T093147Z buster/main amd64 Packages
     10.1.23-9+deb9u1 500
        500 http://snapshot.debian.org/archive/debian/20170624T094211Z buster/main amd64 Packages

Some questions that comes to my head:
- what was the content of the DB (size, number of tables)?
- does this append with an empty DB?
- in the case that the DB is huge, could it be related to this?
>	After that the retry of the postinst worked but took a while and
>	there wasn't any progress indicator and so some people might get
>	the false impression that the postinst hangs:


More information about the pkg-mysql-maint mailing list