Web lists-archives.com

Re: Apt trusted.gpg file problems




On 3/26/17, Miltiades Vasiliades <miltosv@xxxxxxxxxxxxxx> wrote:
> I tried switching the mirrors through synaptic then synaptic as usual asked
> to refresh however the refresh ended with the following errors
>
> W: http://repo.steampowered.com/steam/dists/precise/InRelease: The key(s) in
> the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by
> user '_apt' executing apt-key.
> W:
> http://security.debian.org/…/dists/stretch/updates/InRelease<http://security.debian.org/debian-security/dists/stretch/updates/InRelease>:
> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
> W: http://ftp.de.debian.org/debian/dists/stretch/InRelease: The key(s) in
> the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by
> user '_apt' executing apt-key.
>
>
> Any ideas how to resolve that issue?


DISCLAIMER: This may be apples and oranges thus not even close, but am
writing anyway because I've seen something similar to that "not
readable by user '_apt'" part.

That said...

*heh!* That's the message I've had before. I referenced it somewhere
on here a while back. Do you have anything symlinked?

In my case, I had /var/cache/apt/archives symlinked because it's
massive k/t being on dialup yada-yada. I went through and looked at
permissions in my case. They didn't seem to change, but that
symlinking definitely borked/broked it somehow.

I thought maybe there was a permissions disintegration because my
symlinking traveled a few levels into a non-standard (homegrown
personalized) directory tree on an external hard drive.

As a test, I tried rsync copying over the directory tree from the
primary one that worked. Rsync very nicely properly preserves
permissions. I then symlinked to that new directory, but at that
moment it still did not work......

One thing I don't know is if it has always been like that, or if it is
something that became a new bug somehow. The error is new for me in
the last six months to a year or so.

An important detail that I can't remember is if I was symlinking in
this manner prior to that time. That would have shown if things used
to work and now don't... or not.

This is the deal that turned out to be the culprit in my MANY failed
debootstrap efforts. There would be an error message about _apt and
permissions before debootstrap finished. I'd run debootstrap again
because that works for apt-get (yeah, I know, apples, oranges, former
bleached blonde, but anyway).

There'd be no error message on that second run, and it missed my
consciousness that things didn't go all the way through to the normal
successful install message. I'd chroot in, and that's when root's "I
Have No Name!" identity crisis slash eventual debootstrap install fail
came into play.

Just thinking out loud..... :)

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *