I tried to reproduce the issue in a podman container, but was unable to do so. This makes sense: After do-release-upgrade -d, obviously apt upgrade will not have any pending upgrades.
Marking this as incomplete, as we'd need to see a clean reproducer to get anywhere.
Looking at the postinst, it fails because the dpkg database in /var/lib/dpkg contains an unexpected "dpkg" directory. Please investigate how this directory was created / what it contains, it should not be there.
I tried to reproduce the issue in a podman container, but was unable to do so. This makes sense: After do-release-upgrade -d, obviously apt upgrade will not have any pending upgrades.
Marking this as incomplete, as we'd need to see a clean reproducer to get anywhere.
Looking at the postinst, it fails because the dpkg database in /var/lib/dpkg contains an unexpected "dpkg" directory. Please investigate how this directory was created / what it contains, it should not be there.