Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] Problems with synaptic in a clean stretch install

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
pagat
Posts: 32
Joined: 2014-04-17 14:03

[SOLVED] Problems with synaptic in a clean stretch install

#1 Post by pagat »

I do have this problem with clean install
https://lists.debian.org/debian-user/20 ... 00275.html

I guess this is the same problem
http://forums.debian.net/viewtopic.php?f=5&t=130558

I resolved problem - don't know exactly how. I just deliting and renaming trusted.gpg and trusted.gpg.d directory several times

I'm interested in what this inscription means if anyone knows:
Warning: 'apt-key update' is deprecated and should not be used anymore!
Note: In your distribution this command is a no-op and can therefore be removed safely.

What is no-op command?
Last edited by pagat on 2018-01-06 00:32, edited 1 time in total.

MALsPa
Posts: 678
Joined: 2007-12-07 19:20
Location: albuquerque
Been thanked: 2 times

Re: Problems with synaptic in a clean stretch install

#2 Post by MALsPa »

I had that issue come up with a new installation back in July and wrote about it in my notes:
Did a "Reload" in Synaptic. Got the following error message:

An error occurred - The following details are provided:

W: http://security.debian.org/debian-secur ... /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.us.debian.org/debian/dists/s ... /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.us.debian.org/debian/dists/s ... elease.gpg: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
To fix it, I got rid of the file like this:

Code: Select all

# cd /etc/apt
# mv trusted.gpg trusted.gpg.bak
I haven't noticed the error message since then. I see that the /etc/apt/trusted.gpg file has since been replaced on my system, though.

MALsPa
Posts: 678
Joined: 2007-12-07 19:20
Location: albuquerque
Been thanked: 2 times

Re: Problems with synaptic in a clean stretch install

#3 Post by MALsPa »

pagat wrote:I'm interested in what this inscription means if anyone knows:
Warning: 'apt-key update' is deprecated and should not be used anymore!
Note: In your distribution this command is a no-op and can therefore be removed safely.
Check out the apt-key manpage, where it says:

Code: Select all

update (deprecated)
           Update the local keyring with the archive keyring and remove from
           the local keyring the archive keys which are no longer valid. The
           archive keyring is shipped in the archive-keyring package of your
           distribution, e.g. the debian-archive-keyring package in Debian.

           Note that a distribution does not need to and in fact should not
           use this command any longer and instead ship keyring files in the
           /etc/apt/trusted.gpg.d/ directory directly as this avoids a dependency
           on gnupg and it is easier to manage keys by simply adding and
           removing files for maintainers and users alike.

pagat
Posts: 32
Joined: 2014-04-17 14:03

Re: Problems with synaptic in a clean stretch install

#4 Post by pagat »

I found solution

Mandatory must be installed package
apt-transport-https

Post Reply