Hello! Seems this libcrypt1 change not only affects upgrades from Stretch, but in some cases even upgrades from Buster: - https://salsa.debian.org/mariadb-team/galera-4/-/jobs/2008098 - https://salsa.debian.org/mariadb-team/galera-4/-/jobs/2008103
I wonder if there is some workaround? Could we somehow force the new librcypt1 to install before libc upgrades?
