Are you having a Debian key issue?
I've had issues with expired Debian keys periodically, and I've posted on it before but am even too lazy to look up my own entries on the matter.
I did find Debian's Web page on how to get the "current" key set up.
I basically followed the instructions:
$ gpg --keyserver subkeys.pgp.net --recv-keys 55BE302B
The output in the terminal should look something like this:
gpg: requesting key 55BE302B from hkp server subkeys.pgp.net
gpg: key 55BE302B: public key "Debian Archive Automatic Signing Key (5.0/lenny)
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
Then I did the following (still using a regular, non-root terminal and using sudo for the rootly portion of the command)(:
$ gpg -a --export 55BE302B | sudo apt-key add -
Then I updated the package list:
$ sudo aptitude update
I stayed in the terminal and used sudo aptitude install to add my package.
This time I didn't get "WARNING: untrusted versions of the following packages will be installed," and that means problem solved regarding my Debian keys.
Note: Yep, I use Aptitude instead of apt. I've found that Aptitude adds more dependencies than apt does alone, and for me that works. I have yet to explore Aptitude in depth, but my respect and admiration for the Debian packaging tools continues.
5 Comments
Leave a comment
About this blog
My understanding after discussing this on irc is that the default aptitude configuration installs the "Recommends" packages, while the defaults for apt don't install the "Recommends" packages. I suspect this is configurable for both tools, but have not investigated. I found that when first setting up a box, the use of aptitude got me to the finish faster, because of this difference. Apt and Aptitude are great, and along with the careful attention the debian devs pay to package building, one gets a really strong system, very resistant to breakage.
This difference is one reason the sidux team strictly recommends using apt over aptitude for installing packages.
@gronk
I think you are correct about the "recommends."
While I'm running this particular Debian installation a lot leaner than I usually do (it's more stock GNOME than anything), I still appreciate the extra packages and the functionality they bring when I add an application with Aptitude.
Abiword, for instance, doesn't include the spell-check function (or didn't the last time I installed it, which was over a year ago) when you use apt but does when you use Aptitude.
Plus Aptitude saves all of your "work" using it in a database, which could theoretically be useful if you have a problem.
I've never "needed" to consult the Aptitude database, so this might not be the kind of thing that's a deal-breaker.
@gronk: apt-get used to differ the way you describe, but for some time now, both apt-get and aptitude will install recommended packages by default.
You can alter the default (for both) by adding this line to /etc/apt/apt.conf. (Note that the file may not exist before you go to edit it.)
APT::Install-Recommends "false";
I was looking at the documentation for Sidux, which is based on Debian Sid (and which I've used before successfully, not so much lately), and it recommends apt-get for periodic dist-upgrades, and specifically NOT Aptitude or Synaptic. The Sidux developers say that only apt-get can handle the sometimes complicated upgrades that happen when following Sid.
Well, I was getting the infamous "WARNING: untrusted versions of the following packages will be installed!" message. So I tried the recipe given here, using gpg and apt-key.
Didn't solve the problem.