"David Wright" [email protected] – 8. März 2026 05:00 > I don't understand why, when you upgraded to trixie, installing the > new version of debian-archive-keyring didn't ensure that there > was a .gpg file for every .pgp file in /usr/share/keyrings. > After all, debian-archive-keyring is a dependency of apt. If you are in the process of upgrading bookworm to trixie then your current system obviously is not trixie, it's probably bookworm. With bookworm the file extension was .gpg and no .pgp-file is present. So if you change the apt sources file to check the keyring file with a .pgp-extension, there is no such file (as only the .gpg-file is present). Therefore no package installation is possible, as no signatures can be checkt, hence you cannot update to the new debian-archive-keyring from trixie where the .pgp-files are present. A deadlock.
> (I still don't follow why you need two extensions for the same > format.) There is no technical reason to do so, it is politics. But this is quite normal and hopefully will calm down anytime soon... Traditionally within Debian the filename extension was .gpg and technically the .gpg extension could be used forever. But there is some controversy in the PGP/OpenPGP/GnuPG-World. The IETF changes the OpenPGP standard in a way the GnuPG-guys, primarily the main developer, does not like. The result is some kind of a schism in the community with some of them on the one and some of them on other side. Quite typical. The gnupg guys even forked the OpenPGP standard to librePGP. And the Debian maintainers, which are responsible here, are changing the filename extention from .gpg to .pgp. This obviously reflects that they are on the OpenPGP-side. Like I said, this is politics and quite normal in our world. hede
