Tag Info

Hot answers tagged


You should be able to reinstall the package with a simple: # pacman -S perl-libwww This will only remove perl-libwww: # pacman -Rdd perl-libwww Please notice the double -d in the command, if you use --nodeps you have to specify that twice too or combine it with a -d like: # pacman -R --nodeps --nodeps perl-libwww # pacman -Rd --nodeps perl-libwww ...


From the Pacman Rosetta, since you're looking for the equivalent to apt-file: pkgfile filename pkgfile used to be in the pkgtools package. In recent versions, it's in its own package. To install: pacman -S pkgfile


From man pacman: --noconfirm Bypass any and all “Are you sure?” messages. It’s not a good idea to do this unless you want to run pacman from a script. Note the qualification about using this with care... Arch is a rolling release, which means pacman has to, from time to time, manage some quite complex upgrades. At these times pacman will prompt ...


I found the answer on Arch Linux Forums Since pacman 3.4 you can use # pacman -D to modify only the database. So: # pacman -D --asexplicit <pkgs> will make <pkgs> explicitly installed.


Binaries have been moved to /usr/bin. You need to approach the upgrade in two phases, as per the news article. First remove or update any packages from non-official repos, then update your system in three distinct steps: pacman -Syu --ignore filesystem,bash pacman -S bash pacman -Su If you encounter any difficulties, there is a long thread on the Arch ...


Firstly, try running pacman -Syy, then try to install sudo again. Check that the repositories are uncommented in /etc/pacman.conf. Or your mirrorlist might be outdated: Generate a current list of mirrors and copy it to /etc/pacman.d/mirrorlist Quoting from this relevant forum thread: You can: pick another mirror try using an http mirror, not ...


IP Network Troubleshooting There are a few standard things you can look for when you are experiencing network connectivity issues. These are listed here from a top-down, or least fundamental to most fundamental issues. All the example ip commands shown here use a Linux-specific tool called iproute2. Many of the tasks can likely be done with ifconfig and ...


That's not a conflict, its a reflection of the fact that the new version of X (1.16) has hit the repos and, as the news makes clear, glamour-egl is deprecated. Follow pacman's advice and select Y.


Pacman's install command really means 'synchronize', so the command to install a new package and to upgrade a single package is the same. pacman -S packagename This will upgrade the package.


Pacman won't upgrade Apache using your customized PKGBUILD; you will have to do that manually using ABS. What you can do, is prevent pacman from overwriting your customized package. To expand on Renan's answer, if you have more than one package that you wish to prevent pacman updating, you can include a groups field in the respective PKGBUILDs and then, in ...


What this error actually says, is that the version of package-query that's installed depends on a lower version of pacman than the one you're trying to upgrade to. This can be solved by running pacman -Rs yaourt; pacman -Syu; and then rebuilding yaourt and package-query.


If you don't need the python packages for all users then you can install them in your home using pip install --user packagename. Installing in your home will not conflict with the package manager. See the pip manual for more information.


You delete files with the rm command, e.g.: rm /var/lib/pacman/db.lck I hate to be "that guy", but if you don't know how to delete a file from the Linux command line, Arch is not the Linux distribution for you. Try something easier, like Ubuntu or Linux Mint first.


From ArchWiki: $ pacman -Qo /path/to/file_name You can to see more arguments in Querying package databases.


In pacman, you can actually specify the cache directory: --cachedir <dir> set an alternate package cache location So if you plug a USB stick into your computer, you can do a full system upgrade the normal way and just toss the downloaded packages onto the stick, like so: pacman -Syu --cache /media/USB_STICK/pacman/ It doesn't take much space (a ...


Nothing is wrong. As the Arch Wiki notes: For this initialization entropy is required. Moving your mouse around, pressing random characters at the keyboard or running some disk-based activity (for example in another console running ls -R / or find / -name foo) should generate entropy. If your system does not already have sufficient entropy, this step may ...


From the Arch Wiki: To list all packages no longer required as dependencies (orphans): $ pacman -Qdt Or, to recursively remove orphans: orphans() { if [[ ! -n $(pacman -Qdt) ]]; then echo "No orphans to remove." else sudo pacman -Rs $(pacman -Qdtq) fi }


the google way: site:www.archlinux.org/packages/ bin/filename


If you're downloading packages manually, then it's easiest to install them with pacman: pacman -U curl-7.26.0-1-x86_64.pkg.tar.xz That way they'll also get tracked like any other package. If the reason for this mode of operation was a broken system, just run pacman afterwards (when you can) and the reinstallation will take care of tracking.


If there are updates to the kernel, glibc or systemd, you may want to restart so the updated versions are in use. If you have, say, updates to your desktop environment, a simple logout/login is enough.


You should compile your files with libs and cflags provided by python package: gcc py.c $(pkg-config --cflags --libs python2) -o py Besides, it should be #include <Python.h> instead.


No, pacman doesn't remove old packages from your cache (/var/cache/pacman/pkg) so, over time, it can fill up. You can adopt two approaches to clearing the cache: the brute force one with pacman -Sc: -c, --clean Remove packages that are no longer installed from the cache as well as currently unused sync databases to free up disk space. ...


I just use arch regularly since a few weeks and am no expert on the subject so this answer is by no means exhaustive, just a few points I have noted about the "flexibility/power": This is just an impression but pacman seems more modern and simple in its design/architecture. At least there is far less tools to deal with. While I don't know of apt source ...


There are two separate, but related, issues. First, package-query is an unsupported package (from the AUR) and it is your responsibility to rebuild it whenever other dependencies—in this case pacman—are updated. Uninstall it, update pacman and then rebuild package-query against the newer version. Second, in addition to Shawn's advice to force ...


just put your repository above [extra] in pacman.conf. Your file should look like: [core] Include = /etc/pacman.d/mirrorlist [<your custom repository>] Server = <your repository location> [extra] Include = /etc/pacman.d/mirrorlist In this way your haskell packages will automatically be preferred over the official packages from extra with the ...


The ARM package has only just been updated; it likely just hasn't propagated to your mirror yet. You can change your mirror in /etc/pacman.d/mirrorlist and then force a rsync of your local database with pacman -Syyu. Or you could just wait for the package to arrive on your current mirror.


I'd recommend that you use rvm to manage Ruby versioning. First install rvm: curl -L get.rvm.io | bash -s stable --autolibs=enabled . ~/.rvm/scripts/rvm rvm requirements You'll probably want to source that on shell startup as well, so add it to your ~/.bashrc: cat >> ~/.bashrc << 'EOF' [[ -r ~/.rvm/scripts/rvm ]] && . ...


First of all, the network persists even when you arch-chroot. But if you still want the answer, just use pacman --root /wherever/your/install/is/mounted. See also man pacstrap.


The option you are looking for is --noconfirm . It is available in pacman's 8 man page and is also available here however, it is best to avoid using it and is highly recommended to always read and understand pacman's output.


You shouldn't use the -c switch unless you really are sure of what you are doing. From man pacman: -c, --cascade Remove all target packages, as well as all packages that depend on one or more target packages. This operation is recursive, and must be used with care since it can remove many potentially needed packages. You have obviously ...

Only top voted, non community-wiki answers of a minimum length are eligible