On Fri, May 26, 2017 at 06:21:23PM +1000, Peter Miller wrote:
> 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.
Yeah, right. No. That's a lie.
>
> 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.
There is no Frank here, and nobody here gave you an advice to count
files.
>
> 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.
David gave you very clear instructions (and I quoted them twice for you)
1. run ls -lh on all files in trusted.gpg.d to figure out permissions
2. run file on all files to check that they are all valid GPG public
key files
3. And run a stat on /tmp to check if your system is not messed up there.
You have followed *none* of the instructions, so I get the feeling
you are just here to troll. So this is your last chance, after that
I'll ignore you and ask for you to be banned or something.
And one last time, the original quote from David:
> > > > > On 23 May 2017 at 21:35, David Kalnischkies <david@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…
--
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.