ps 5.7.37-40-1.buster install stucked

That's what I have done

Thank you for the information. This seems to be a regression, I wasn't able to reproduce the hang on 5.7.36-39. 

As a workaround can you please install the mailutils package after Percona Server.

Heelo,

Many thanks for your reply.

I didn't notice the mysql-common. thanks.

From the image, I've got these packages installed :

They are used by mailutils

If I delete theses packages, installation is OK

What's strange is the the 5.7.37.40-1 release does not work if this package is installed
when the 5.7.36.39-1 worked fine with this package installed
(as far as I remember, the previous 5.7.37 was also ok)

Thank you for more detailed report.

When you mentioned you installed some packages, can you tell which ones?

One of differences I've noticed is that mysql-common package has already been installed on your box. Comparing to list of packages from my install:

Was this installed before? Do you have any other (3rd party) repositories enabled?

I've set up a new debian 10 LXC container, then

• upgrade the system

• install basic packages

• download and install manually percona-release

• update

• install ps-5.7

Processes :

Journalctl information :

Logs

Only 3 files changed (except apt directory && lastlog)

• /var/log/mysql contains one empty file "error.log"

• /var/log/alternatives.log

• /var/log/dpkg.log

Looking a processes, the '[percona-server-] <defunct>' is quite suspicious...
(the process /usr/sbin/mysqld --log_error_verbosity=2 is still running)

Looking at /var/lib/dpkg/info/percona-server-server-5.7.postinst script :

• the command : my_print_defaults mysqld does not returns anything, but return code is 0

• mysql is running, connexion is OK

• The SQL command (UPDATE user SET plugin='auth_socket' WHERE user='root') is still not done :

• If I kill (SIGTERM) this mysqld process, then the dkpg will be unblocked, and finish with errors

• Then, if I run a "dpkg --configure -a"  configuration will be OK