A repository is a logical collection of packages, which are physically stored on one or more servers: for this reason each server is called a mirror for the repository.
Repositories are distinguished between official and unofficial. The order of repositories in the configuration file matters; repositories listed first will take precedence over those listed later in the file when packages in two repositories have identical names, regardless of version number. In order to use a repository after adding it, you will need to upgrade the whole system first.
See the Mirrors article for mirror configuration. Pacman stores downloaded package files in cache, in a directory denoted by CacheDir in [options] section of pacman. Cache directory may grow over time, even if keeping just the freshest versions of installed packages.
Pacman supports package signatures, which add an extra layer of security to the packages. This can be overridden by per-repository SigLevel lines. For more details on package signing and signature verification, take a look at pacman-key. If you see the following error: [1].
This is happening because pacman has detected a file conflict, and by design, will not overwrite files for you. This is by design, not a flaw. The problem is usually trivial to solve. If the file is owned by another package, file a bug report. If the file is not owned by another package, rename the file which 'exists in filesystem' and re-issue the update command. If all goes well, the file may then be removed.
See also Pacman tips Identify files not owned by any package. If this file gets corrupted, is empty or goes missing, it results in file exists in filesystem errors when trying to update the package. Such an error usually concerns only one package.
Instead of manually renaming and later removing all the files that belong to the package in question, you may explicitly run pacman -S --overwrite glob package to force pacman to overwrite files that match glob.
Look for. This prevents another instance of pacman from trying to alter the package database at the same time. If pacman is interrupted while changing the database, this stale lock file can remain. If you are certain that no instances of pacman are running then delete the lock file:. This error manifests as Not found in sync db , Target not found or Failed retrieving file.
Firstly, ensure the package actually exists. If certain the package exists, your package list may be out-of-date. Try running pacman -Syu to force a refresh of all package lists and upgrade.
Also make sure the selected mirrors are up-to-date and repositories are correctly configured. It could also be that the repository containing the package is not enabled on your system, e.
See also FAQ Why is there only a single version of each shared library in the official repositories? In the case that pacman crashes with a "database write" error while removing packages, and reinstalling or upgrading packages fails thereafter, do the following:. This will cause the update to fail. Use the CacheDir option or a bind mount instead; see Package cache directory. This can also come in handy when a partial upgrade was performed and pacman can not run anymore. The pinned comment and the PKGBUILD provides a way to directly download the binary, which can be used to reinstall pacman or to upgrade the entire system in case of partial upgrades.
If even pacman-static does not work, it is possible to recover using an external pacman. One of the easiest methods to do so is by using the archiso and simply using --sysroot or --root to specify the mount point.
See Chroot Using chroot on how to mount the necessary filesystems required by --sysroot. Even if pacman is terribly broken, you can fix it manually by downloading the latest packages and extracting them to the correct locations.
The rough steps to perform are:. But you may only need to update a few of them depending on your issue. An example of extracting a package is. Note the use of the w flag for interactive mode. Running non-interactively is very risky since you might end up overwriting an important file.
Also take care to extract packages in the correct order i. This forum post contains an example of this process where only a couple pacman dependencies are broken. Most likely the initramfs became corrupted during a kernel update improper use of pacman' s --overwrite option can be a cause.
There are two options; first, try the Fallback entry. Once the system starts, run this command for the stock linux kernel either from the console or from a terminal to rebuild the initramfs image:. Then chroot using arch-chroot :. Reinstalling the kernel the linux package will automatically re-generate the initramfs image with mkinitcpio -p linux. There is no need to do this separately. As the error message says, your locale is not correctly configured.
See Locale. If you use pacman with sudo , you need to configure sudo to pass these environment variables to pacman. You will then need to reinstall all the foreign packages, which can be listed with pacman -Qmq. It looks like previous pacman transaction removed or corrupted shared libraries needed for pacman itself.
To recover from this situation you need to unpack required libraries to your filesystem manually. Unpack required shared library to the filesystem. This will allow to run pacman. Now you need to reinstall the broken package.
Note that you need to use --overwrite flag as you just unpacked system files and pacman does not know about it. Pacman will correctly replace our shared library file with one from package. If you receive this error message with correct mirrors , try setting a different name server.
This can be done on any Arch Linux machine which has up-to-date repository data bases see above for links to database files ; to create the list of links to the required packages, use:.
The file nvidia. Unless you have cleared your cache the packages you have installed will be in your cache location. Then copy the dependencies you have already installed from the cache. This can be done on either 'Al' or 'Bob' using the repo-add command which comes with pacman from version 3? Now all the packages have been downloaded, you do not need 'Al' anymore. Next, pacman must be made aware of this new repository of packages. First copy your current pacman. You may also need to comment out the other repositories so stale defaults do not cause failed attempts to download from online Now, instruct pacman to synchronize with the dedicated NVIDIA repository we created:.
You can use packer to install, upgrade and display information about installed packages. In this article, We took you through how you can install packages in Arch Linux using Yaourt and Packer. Keep tuned in for more informative articles. Finally, update the repository database and install Yaourt using the command below sudo pacman -Sy yaourt Installing Yaourt using AUR This method is a bit longer and a bit tedious. About James Hey there!
This is James, a Linux administrator and a tech enthusiast.
0コメント