Bug#1005249: Sid debian-archive-keyring is missing key id E852514F5DF312F6

Jeffrey Walton

unread,

Feb 9, 2022, 3:40:03 PM2/9/22

to

Package: debian-archive-keyring
Version: 2021.1.1
X-Debbugs-CC: g...@debian.org
Tags: sid

Ah, the never ending problem of Debian keys... I'm trying to setup a
Qemu Chroot for testing Debian bug 1001995.

Key id E852514F5DF312F6 cannot be found in debian-archive-keyring, and
it cannot be found at https://ftp-master.debian.org/keys.html.

'apt-get update && apt-get upgrade && apt-get dist-upgrade' was run on
this Sid machine after changing sources.list. The machine is fully
patched, and nothing has been held back.

root@debian-unstable:~# qemu-debootstrap --arch=armhf --keyring
/usr/share/keyrings/debian-archive-keyring.gpg --variant=buildd
--exclude=debfoster unstable debian-armhf
http://ftp.ports.debian.org/debian-ports
W: qemu-debootstrap is deprecated. Please use regular debootstrap directly
I: Running command: debootstrap --arch=armhf --keyring
/usr/share/keyrings/debian-archive-keyring.gpg --variant=buildd
--exclude=debfoster unstable debian-armhf
http://ftp.ports.debian.org/debian-ports
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
E: Release signed by unknown key (key id E852514F5DF312F6)
The specified keyring
/usr/share/keyrings/debian-archive-keyring.gpg may be incorrect or out
of date.
You can find the latest Debian release key at
https://ftp-master.debian.org/keys.html

root@debian-unstable:~# debootstrap --arch=armhf --keyring
/usr/share/keyrings/debian-archive-keyring.gpg --variant=buildd
--exclude=debfoster unstable debian-armhf
http://ftp.ports.debian.org/debian-ports
I: Target architecture can be executed
I: Checking Release signature
E: Release signed by unknown key (key id E852514F5DF312F6)
The specified keyring
/usr/share/keyrings/debian-archive-keyring.gpg may be incorrect or out
of date.
You can find the latest Debian release key at
https://ftp-master.debian.org/keys.html

# cat /etc/apt/sources.list
deb http://deb.debian.org/debian/ unstable main
deb-src http://deb.debian.org/debian/ unstable main

# dpkg --list debian-archive-keyring
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-======================-============-============-==================================>
ii debian-archive-keyring 2021.1.1 all GnuPG archive
keys of the Debian a>

# apt-cache show debian-archive-keyring
Package: debian-archive-keyring
Version: 2021.1.1
Installed-Size: 234
Maintainer: Debian Release Team <pack...@release.debian.org>
Architecture: all
Description-en: GnuPG archive keys of the Debian archive
The Debian project digitally signs its Release files. This package
contains the archive keys used for that.
Description-md5: 4ee78d6fd2292b9893b8eb4f5d5dd91d
Multi-Arch: foreign
Tag: role::data, security::authentication, suite::debian
Section: misc
Priority: important
Filename: pool/main/d/debian-archive-keyring/debian-archive-keyring_2021.1.1_all.deb
Size: 93592
MD5sum: 250bbeab4b680dbc2c4da9b10ccd773f
SHA256: 56beca470dcd9b6d7e6c3c9e9d702101e01e9467e62810a8c357bd7b9c26251d

Adam D. Barratt

unread,

Feb 9, 2022, 5:00:04 PM2/9/22

to

On Wed, 2022-02-09 at 16:26 -0500, Jeffrey Walton wrote:
> On Wed, Feb 9, 2022 at 4:00 PM Adam D. Barratt <
> ad...@adam-barratt.org.uk> wrote:

> > On Wed, 2022-02-09 at 15:30 -0500, Jeffrey Walton wrote:
> > > Ah, the never ending problem of Debian keys... I'm trying to
> > > setup a
> > > Qemu Chroot for testing Debian bug 1001995.
> > >
> > > Key id E852514F5DF312F6 cannot be found in debian-archive-
> > > keyring,
> > > and
> > > it cannot be found at https://ftp-master.debian.org/keys.html.
> >

> > That's correct, and expected, in both cases.
>
> It's actually unexpected since the error message clearly states:
>
> <QUOTE>

> You can find the latest Debian release key at
> https://ftp-master.debian.org/keys.html

> </QOUTE>
>

I assume that message comes from debootstrap, which is trying to be
helpful. In any case, it's correct for the standard use-case, where the
mirror URL you've passed to debootstrap is for the Debian archive.

I have to admit that I'm slightly confused as to why you're attempting
to use the ports archive to build an armhf chroot in any case, when
it's been in the main archive for over a decade now.

Regards,

Adam

Jeffrey Walton

unread,

Feb 9, 2022, 5:10:03 PM2/9/22

to

On Wed, Feb 9, 2022 at 4:48 PM Adam D. Barratt <ad...@adam-barratt.org.uk> wrote:
> ...

> I have to admit that I'm slightly confused as to why you're attempting
> to use the ports archive to build an armhf chroot in any case, when
> it's been in the main archive for over a decade now.

I'm trying to reproduce a bug from Debian's builder (?) environment.
Years ago I was told to do the Qemu/Chroot thing when trying to
reproduce the bugs.

For ARM I am kind of following https://wiki.debian.org/ArmHardFloatChroot .

Jeff

Adam D. Barratt

unread,

Feb 9, 2022, 5:20:03 PM2/9/22

to

Right, that's the first page I found on Google as well. That doesn't
reference ports.debian.org though and even when it did never used
"debian-armhf" as part of the path.

If there's still documentation out there that suggests using the
ports.d.o archive for armhf then it's _very_ out of date and may well
have other issues.

Regards,

Adam

Jeffrey Walton

unread,

Feb 9, 2022, 10:00:03 PM2/9/22

to

https://www.debian.org/ports/

Jeff