Comment 2 for bug 1819438

March 5 was the day the glibc 2.29 migration landed in the release pocket, bringing with it a large number of other dependent packages. This could be due to version skew of glibc itself between the d-i initrd and the image, or it could be a regression introduced by some other package updated in the image (merge of new upstream version partman-base migrated that day, so it's my second guess).

A rebuild of d-i against current glibc has just landed, so trying an image respin now to see if this alone is sufficient to fix the problem.