[debian-mysql] Bug#929707: Bug#929707: mariadb-client-10.1: import of "mysqldump --all-databases" fails with "ERROR 1062 (23000): Duplicate entry"

[Matija Nalis]

On Sun, Oct 04, 2020 at 12:40:48PM +0300, Otto Kekäläinen wrote:
> la 3. lokak. 2020 klo 18.17 Matija Nalis (mnalis-debianbug at voyager.hr)
> > Yes, I can write a shell test scripts which looks like
> > https://salsa.debian.org/mariadb-team/mariadb-10.5/-/blob/master/debian/tests/smoke
> 
> Yes, that seems like a sensible approach. You don't need much
> resources as you can use the resources of Salsa (Gitlab-CI) to run it
> for you. See https://wiki.debian.org/Teams/MySQL/patches "Using
> Salsa-CI".

Thanks for the pointers, Otto - they look interesting!

Unfortunately, I'm now failing even at this simple task of cleanly
reproducing the bug manually.  I've tried but I am unable to
recreate the problems when I install mariadb from scratch in Stretch. 
(our original machines had mysql/mariadb databases upgraded from
previous Debian versions, so something there might have done
something to databases to trigger that behavior).

As original machines which were exhibiting problem were in the
meantime updated to Buster (where the problem seems to be gone now),
and myself not being able to reproduce it in clean install of Scratch
mariadb-10.1 (even after importing few databases on which it was
failing on original machines) and myself lacking time to try some
deeper forensics, I propose this bug be closed unless someone else
chimes in that they can reproduce it.

-- 
Opinions above are GNU-copylefted.