I confirmed that when installing the libapt-pkg4.12 1.0 (from debian/unstable) prior to the upgrade the bug is no longer triggered.
I confirmed that when installing the libapt-pkg4.12 1.0 (from debian/unstable) prior to the upgrade the bug is no longer triggered.