UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been unable to do any upgrade to one of our servers running the Ubuntu 14.04.3 distribution. The initial attempt was made through the Webmin utility. The packages in question, 212 in total, were selected and while the download appeared to be successful, the following error message appeared on-screen:
Quote:
Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
I then went to the command line, and as root, I ran the following:
Quote:
apt-get update --fix-missing
The error messages that I encountered were as follows:
Quote:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://free.nchc.org.tw drbl Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 667857D045599AFD
The "Duplicate sources.list" errors should be ignorable
The "NO_PUBKEY 667857D045599AFD" is preventing you from using the NCHC repo, at least. There are at least 50,000 Google results for "NO_PUBKEY", but here's another:
Assuming you trust that key 667857D045599AFD is owned by NCHC (their web site should really securely provide you with these directions), run:
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
You added some kind of PPA or another repository. I think synaptic allows selection of repositories? Otherwise, look in the Ubuntu Software Shop for the ability to select repositories.
Looks like you've a rogue repository you added for "some cool app" but it's inm the apt.d scheme.
Thank-you for your reply. I ran the apt-key command, and the output was the following:
Quote:
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.uO7HI0LVsT --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv-keys 667857D045599AFD
gpg: requesting key 45599AFD from hkp server keyserver.ubuntu.com
gpg: key 45599AFD: "DRBL Project (Diskless Remote Boot in Linux) <drbl@nchc.org.tw>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
I then ran the apt-get update command, and the following error messages appeared on-screen:
Quote:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://free.nchc.org.tw drbl Release: The following signatures were invalid: BADSIG 667857D045599AFD DRBL Project (Diskless Remote Boot in Linux) <drbl@nchc.org.tw>
I checked the /var/lib/apt/lists directory, and there is folder with the name 'partial' at that location. The files listed below were listed in this folder:
Since the nchc site appears to be the culprit, can I simply removed the two references to the site from the partial folder, or should I remove the folder entirely?
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I think your best bet really is firing up synaptic. Failing that edit sources.list and anything under /etc/apt and ensure they only contain what they ought.
Thank-you for the feedback. I went to the /etc/apt/sources.list file, and commented out the references to the drbl webpages. Once that was done, the upgrade completed successfully.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.