On Sat, May 24, 2008 at 05:27:01PM -0400, Paul Cartwright wrote: > On Sat May 24 2008, Ron Johnson wrote: > > If apt can't find gnupg, your system is totally screwed up.
Did you verify with debsums as I said? $ debsums gnupg You claimed you did overwrite before. If that caused some problem, this may tell you. (For such confused system, I recommend you to do fresh reinstall, after careful data backup especially Gnupg keys.). If you need quick fix as stop gap, download binary package gnupg and probably gpgv and do "dpkg -i ..." to do reinstall over existing files. But this is not real cure for broken system ... > ok, so I should screw Debian and try SUSE.. > or do you have anything informative to say? I think it does not solve your problem no matter what distribution you try. Suse, redhat, Ubuntu, ... any distro, as long as you neglect basic rules to install external software to the system. Basically, you need to be cool headed to administer system. Guessing what went wrong is very difficult. Do not be discouraged. It is tedious thing ... What others can do is limited without having access to your system since we see problem through your eyes. Anyway, most distributions have package dependency feature these days. This means you must make very careful action to install alternative source compiled binary to the system. That is why someone suggested you slackare where you must do all the configuration by hand and no dependency as I suppose. Also, if you install with correct --prefix=/usr/local, then PATH for /usr/local/bin causes it to be executed over system default one. But when executed, it uses configuration in /etc probably created by the distribution. It is complicated situation. With your short and confusing description, it is impossible to diagnose exact problem. (I think your message with --prefic was typo ...) Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
