Julian,
Sorry, but gmail does not allow me to reply inline, or to select what I
quote. I am using the only option I have.
I am not and did not ignore Frank's advice, which included a *count* of the
files in /etc/apt/trusted.gpg.d. That advice was followed and was a dead
end. Frank's advice was that the keys seem to be correct. There is a bug
somewhere in here, I just don't know where. I did not try to fix anything
from a clean install before this issue showed up.
I do appreciate you responding to me, but it's really not helping that we
seem to be talking at cross purposes. I am not a Debian dev, but do have a
technical background. So, I have tried my best to listen to advice, and to
do what research I can. I am happy to follow any clear instruction, and
would really like not to have to reinstall the operating system to fix what
appears to be a simple problem. I understand I am using Testing, but there
must be a way out of here.
Regards, Pete Miller
On 25 May 2017 at 21:33, Julian Andres Klode <j...@debian.org> wrote:
> On Thu, May 25, 2017 at 08:23:34PM +1000, Peter Miller wrote:
> > Julian,
> >
> > There is no such thing as perfect security. I was and am using a trusted
> > mirror, so I'm much more worried about the Windows machines I have to use
> > at work, and are necessarily linked to my linux boxes. So, please,
> > understand that I understand the (small) risk I have taken. I wouldn't
> even
> > take the time to verify my packages later, as it's not worth the
> > investment. I have good backups of all my important stuff, and I would
> > notice a bot eventually. So, could we please get back to my question?
> >
> > Is there any way to fix my keys?
>
> This is getting ridiculous. David told you precisely what to do and I
> quoted it for you in the previous email again, if you keep ignoring that,
> that's your problem. This is likely the last time I'll quote that for you:
>
> > On 25 May 2017 at 19:00, Julian Andres Klode <j...@debian.org> wrote:
> > > You know, that bit:
> > >
> > > > On 23 May 2017 at 21:35, David Kalnischkies <da...@kalnischkies.de>
> > > wrote:
> > > > > Julian was asking basically for running both:
> > > > > ls -l /etc/apt/trusted.gpg{,.d}
> > > > > file /etc/apt/trusted.gpg{,.d/*}
> > > > >
> > > > > As he thinks it might be a permission/wrong-file-in-there problem,
> > > which
> > > > > is the most likely cause… I would add a "stat /tmp" as I have seen
> it
> > > > > a few times by now that people had very strange permissions on /tmp
> > > > > – all of which usually caused by "fixing" some problem earlier…
>
> Also please reply properly, as explained below.
>
> --
> 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.
>
