Julian,

I thought doing one update might fix the issue, since nothing else was
working, hence --allow-unauthenticated.

I did not install or update anything in /etc/apt/trusted.gpg.d, or anywhere
else similar, so how did it get corrupted? Is there a source issue? Are
there automated checks after download?

Sorry, I don't understand what "output of file(1)" (or any of your other
advice) means. Could I have it in plain English, please? How do I replace
the GPG files? The Release.gpg files on mirrors don't import as keys.

Thanks, Pete Miller

On 23 May 2017 at 16:57, Julian Andres Klode <j...@debian.org> wrote:

> On Tue, May 23, 2017 at 10:59:32AM +1000, Pete Miller wrote:
> > Package: apt
> > Version: 1.4.1
> > Severity: important
> > Tags: d-i
> >
> > Dear Maintainer,
> >
> > I installed Stretch from the CD image to new physical hardware, and then
> > updated the system. I can't remember if errors started straight away, or
> took a
> > while to manifest.
> >
> > See this thread for some background: https://lists.debian.org/debian-
> > user/2017/05/msg00311.html
> >
> > Subsequently, I have run "apt update --allow-insecure-repositories",
> which
> > worked, but a subsequent "apt-get update --allow-unauthenticated" and
> similar
> > failed to update any packages due to key errors as detailed in the
> thread.
>
> --allow-unathenticated is for install/upgrade, I think, not for update.
> Anyway,
> your system is broken, fix it, instead of doing dangerous stuff like this:
> One
> of your files in /etc/apt/trusted.gpg.d/ is probably in a wrong format.
>
> That's what you want for .gpg files (output of file(1)):
>
>         GPG key public ring, created Fri Nov 21 21:01:13 2014
>
> .asc files are valid too, containing armored public keys. Sometimes
> you get "GPG keybox database version 1" files (which gpg2 uses for
> keyrings) - these are not valid files.
>
> --
> Debian Developer - deb.li/jak | jak-linux.org - free software dev
>                   |  Ubuntu Core Developer |
> When replying, only quote what is necessary, and write each reply
> directly below the part(s) it pertains to ('inline').  Thank you.
>

Reply via email to