You did not mention whether this an expert oder standard install.
All defaults so it was standard install. did not do anything more, booted without interacting with IPL.
I need to know as many details as possible as this particular bug has been seen before and it was fixed in debian-installer so I am very surprised to see it. We also don’t see it on the other ports architectures.
The keyrings files: # find / -name '*gpg*' /usr/share/keyrings/archive.gpg /usr/share/keyrings/debian-archive-stretch-stable.gpg /usr/share/keyrings/debian-archive-stretch-security-automatic.gpg /usr/share/keyrings/debian-archive-stretch-automatic.gpg /usr/share/keyrings/debian-archive-keyring.gpg /usr/share/keyrings/debian-archive-jessie-stable.gpg /usr/share/keyrings/debian-archive-jessie-security-automatic.gpg /usr/share/keyrings/debian-archive-jessie-automatic.gpg /usr/bin/gpgv /tmp/net-retriever-1225-Release.gpg /tmp/net-retriever-1168-Release.gpg /lib/libgpg-error.so.0.25.0 /lib/libgpg-error.so.0 ~ # ls -l /usr/share/keyrings/debian-archive-keyring.gpg -rw-r--r-- 1 root root 30142 Oct 28 17:22 /usr/share/keyrings/debian-archive-keyring.gpg Seems to come from debian-archive-keyring 2018.1 so I can look at it in working Debian... gpg --list-keys --keyring /usr/share/keyrings/debian-archive-keyring.gpg does not show the 66571731B5A71F91C501F3FDDA1B2CEA81DCBC61 key, nor is in the other keyring files there. What keyring should contain the debian-ports key and how should it get to the installer image? -- Meelis Roos <[email protected]>
