Ubuntu: Questions and Answers (2014)
Packages
Questions
Q: How do I deal with "unauthenticated sources" errors in the Software Center?
Tags: packages (Next Q)
Any install that I'm trying through the Software Center is telling me:
Requires installation of untrusted packages: The action would require the installation of packages from not authenticated sources.
I did an apt-get update from the command line, then removed the software sources that the keys were bad from (PPAs I added myself), and unchecked them in the software sources for software center, but to no avail. I can't install anything from software center anymore - only> from the command line with apt-get.
Is uninstalling/installing the only option? I don't want to break other PPAs that I have.
Additional information:
Here's a paste from apt-get update:
Reading package lists... Done
W: GPG error: http://ppa.launchpad.net oneiric Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B725097B3ACC3965
W: GPG error: http://us.archive.ubuntu.com oneiric Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
I've tried apt-key update, and there was no effect (two keys unchanged).
The output of apt-get update and apt-get upgrade, and the contents of /etc/apt/sources.list, can be found in this pastebin post.
Tags: packages (Next Q)
User: b.-e.-hollenbeck
Answer by sadi
Open the Terminal and enter the commands below one by one:
sudo apt-get clean
cd /var/lib/apt
sudo mv lists lists.old
sudo mkdir -p lists/partial
sudo apt-get clean
sudo apt-get update
Answer by tom-brossman
This is a common problem with Launchpad PPAs. Common enough that I've copied these commands to use when I reinstall or add new Launchpad PPAs.
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
Then,
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys YOURKEYNUMBERHERE
Substitute YOURKEYNUMBERHERE with the problem keys, like this:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys B725097B3ACC3965
And
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5
The first line is almost the same, minus the keys. It might even be optional, I honestly don't know. All I am sure of is that this method always fixes the problem immediately.
If anyone finds the original answer that I copied these from let me know and I'll link to it and give them the attribution.
**EDIT It's almost certainly karthik87's answer here or here I got this from. This can probably be closed as a duplicate.
Either way, don't forget to do a
sudo apt-get update
after, to fix everything.
Tags: packages (Next Q)
Q: If I build a package from source how can I uninstall or remove completely?
Tags: packages uninstall (Next Q)
I used source code to build one package such as below:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib --with-package-name="Myplugin" --with-package-origin="http://www.ubuntu.org/" --enable-gtk-doc --disable-static
make
make install
But unfortunately, i discovered that its the latest version, and has lot of bugs, so i need to remove it/uninstall it. But how can i do so? I tried make clean; make uninstall but still i see it exist:
# pkg-config --list-all | grep Myplugin
myplugin-....
$ ls /usr/lib/myplugin/libXYZ.so
exist....
How do you remove this now?
Tags: packages uninstall (Next Q)
User: yumyumyum
Answer by javier-rivera
Usually you can just use:
make uninstall
or
sudo make uninstall
if the app was installed as root.
But this will work only if the developer of the package has taken care of making a good uninstall rule.
In the future to avoid that kind of problems try to use checkinstall instead of make install whenever possible (AFAIK always unless you want to keep both the compiled and a packaged version at the same time). It will create and install a deb file that you can then uninstall using your favorite package manager.
make clean usually cleans the building directories, it doesn't uninstall the package. It's used when you want to be sure that the whole thing is compiled, not just the changed files.
Answer by sabacon
I do not think this is a bug, it would be a good idea to read about and learn to use checkinstall when installing from source.
you can install checkinstall from the repositories, a short description of the package;
CheckInstall keeps track of all the files created or modified by your installation script ("make install" "make install_modules", "setup", etc), builds a standard binary package and installs it in your system giving you the ability to uninstall it with your distribution's standard package management utilities.
These links below may be helpful to get a better understanding. http://en.wikipedia.org/wiki/CheckInstall
http://checkinstall.izto.org/
Answer by dv3500ea
This is not a bug - compiling from source is an unsupported method of installing software that bypasses the package management system (which is used by the Software Centre) completely.
There is no standard way that software compiled from source is installed or uninstalled so no way Ubuntu can know what to do. The software is not even listed as an installed program.
You should follow the distributor's instructions for installation and removal of such custom software. You could also contact the developer to ask for them to create a Debian package so that the package management system can be used.
Tags: packages uninstall (Next Q)
Q: How to list all installed packages?
Q: How do I deal with "unauthenticated sources" errors in the Software Center?
Q: If I build a package from source how can I uninstall or remove completely?
Q: How to Downgrade a Package via apt-get?
Q: Requires installation of untrusted packages?