Difference between revisions of "Pacman troubleshooting"

no edit summary
imported>Verityproductions
imported>Verityproductions
Line 19: Line 19:
We all have our own unique signatures which are used to authenticate who we are and to prevent fraudulent or even malicious activities by others. This is also the case with software packages available from the software repositories. They all contain an encrypted codes (signature keys) unique to their developers to ensure that they are authentic and not malicious in nature.  
We all have our own unique signatures which are used to authenticate who we are and to prevent fraudulent or even malicious activities by others. This is also the case with software packages available from the software repositories. They all contain an encrypted codes (signature keys) unique to their developers to ensure that they are authentic and not malicious in nature.  


During the installation process, once any software packages have been downloaded, your system will first check its database against their signatures to ensure that they are authentic prior to actually installing them. If a signature cannot be verified for any reason, then the installation process will be aborted. This problem will usually occur due to:
During the installation process, once any software packages have been downloaded, your system will first check their signature keys to ensure that they are authentic prior to actually installing them. If a signature key cannot be verified for any reason, then the installation process will be aborted. This problem will usually occur due to:


* your system's signature key database being corrupted or out of date  
* One or more signature keys being revoked, changed, corrupted, or out of date  
* one or more software packages not having been signed off properly when placed in a repository
* one or more software packages not having been signed off properly when placed in a repository


Where a package has not been signed off properly, it will be the responsibility of the developer(s) to correct this. However, as this problem will be more than likely due to a problem with your system's signature key database, this can be solved in three easy steps. Once you have opened your terminal:
Where a package has not been signed off properly, it will be the responsibility of the developer(s) to correct this. However, as this problem will be more than likely due to a problem with your system's verification of a signiture key, this can be solved in three easy steps. Once you have opened your terminal:




'''1.''' Refresh and update you system's signature key database by entering the command:
'''1.''' Refresh and update the signature keys by entering the command:


  sudo pacman-key --refresh-keys
  sudo pacman-key --refresh-keys


'''2.''' Reload the signatures contained in your system's signature key database by entering the command:
'''2.''' Reload the signature keys by entering the command:


  sudo pacman-key --populate
  sudo pacman-key --populate