Your message dated Thu, 21 Mar 2019 23:40:21 +0900 with message-id <20190321234021.c7dfc39d7cdc07105f2af...@iijmio-mail.jp> and subject line Re: debootstrap: --keyring= Release signed by unknown key (key id EF0F382A1A7B6500) has caused the Debian Bug report #925048, regarding debootstrap: --keyring= Release signed by unknown key (key id EF0F382A1A7B6500) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 925048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: debootstrap Version: 1.0.89 Severity: important Dear Maintainer, * What led up to the situation? dpkg-deb -R debian-archive-keyring_2017.5_all.deb /tmp/ ls *.gpg|xargs -I{} debootstrap --download-only --force-check-gpg --keyring={} --variant minbase --arch amd64 --make-tarball=debian_amd64 stable /root/dbs_debian_amd64 https://debian.ethz.ch/debian * What exactly did you do (or not do) that was effective (or ineffective)? E: Release signed by unknown key (key id EF0F382A1A7B6500) but debootstrap --download-only --force-check-gpg --variant minbase --arch amd64 --make-tarball=debian_amd64 stable /root/dbs_debian_amd64 https://debian.ethz.ch/debian works There's a problem with using --keyring=whatever.gpg -- System Information: Debian Release: 9.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debootstrap depends on: ii wget 1.18-5+deb9u2 Versions of packages debootstrap recommends: ii debian-archive-keyring 2017.5 ii gnupg 2.1.18-8~deb9u4 debootstrap suggests no packages. -- debconf-show failed
--- End Message ---
--- Begin Message ---On Tue, 19 Mar 2019 21:08:42 +0530 "Veek.M" <vek.m1...@gmail.com> wrote: > There's a problem with using --keyring=whatever.gpg No, it's just because you've specified wrong keyring... For example, when I use ubuntu-archive-keyring that's not appropriate for debian repository, debootstrap returns such error. > $ sudo debootstrap --download-only --force-check-gpg > --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg stable stretch > https://debian.ethz.ch/debian > I: Retrieving InRelease > I: Retrieving Release > I: Checking Release signature > E: Release signed by unknown key (key id EF0F382A1A7B6500) As I said in previous mail, it's not appropriate step. > It seems that your procedure of specifying gpg key is bit strange. > > > dpkg-deb -R debian-archive-keyring_2017.5_all.deb /tmp/ > > ls *.gpg|xargs -I{} debootstrap --download-only --force-check-gpg > > --keyring={} --variant minbase --arch amd64 --make-tarball=debian_amd64 > > stable /root/dbs_debian_amd64 https://debian.ethz.ch/debian debian-archive-keyring package has some gpg keys but you should specify debian-archive-keyring.gpg. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
--- End Message ---
