Bug#863179: apt: GPG errors on update and other operations
On 29 May 2017 at 09:53, Peter Miller <peterg.miller@gmail.com> wrote:
> Hi,
>
>
> If you'd like to show me how I can use the gmail web interface to respond
> inline and select what to quote, do go ahead. I really don't like to be
> called names, especially when there is no basis for it.
Oh, I wasn't name calling, I just stated facts. In the gmail web UI,
you click on the three dots and then move your cursor to the position
where you want to start writing (I actually forgot to add this to the
previous email...).
>
> Sorry, but I did miss the stuff from David. But, all files in that
> directory are -rw-r--r-- 1 root root and all files are GPG key files.
These look correct. Just to clarify: Running file shows you "GPG key
public ring" for each file? What about /etc/apt/trusted.gpg
>
> And:
>
> stat /tmp
> File: /tmp
> Size: 4096 Blocks: 8 IO Block: 4096 directory
> Device: 10302h/66306d Inode: 5373953 Links: 14
> Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root)
That looks correct.
What you can do is manually run apt-key verify for an InRelease file, e.g.:
/usr/bin/apt-key verify
/var/lib/apt/lists/deb.debian.org_debian_dists_unstable_InRelease
/usr/bin/apt-key verify
/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_Release{.gpg,}
(showing the two different invocations). If you don't have InRelease
(or Release.gpg and Release) files, you could download one manually.
This should error messages from gpgv.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Reply to: