I'm trying to update my system via yaourt, but I'm getting an error due to a python package installed with pip instead of yaourt. I'm not succeeding in forcing yaourt to install the update, and I'd like to avoid to remove the package with pip and reinstall it with yaourt. These are the commands I tried : yaourt -Syu --aur yaourt -Suya yaourt -Susya --force This is the output I get all the times : :: Proceed with installation? [Y/n] y (39/39) checking keys in keyring [####################################################################] 100% (39/39) checking package integrity [####################################################################] 100% (39/39) loading package files [####################################################################] 100% (39/39) checking for file conflicts [####################################################################] 100% error: failed to commit transaction (conflicting files) mutagen: /usr/lib/python2.7/site-packages/mutagen-1.36-py2.7.egg-info exists in filesystem Errors occurred, no packages were upgraded. How can I force yaourt to update the all packages?

I'd like to list all meta packages that I installed. - Installed with pikaur or pacman - operating system is Arch Linux # Problem When I install plasma-meta and run pacman -Qg, I can only see plasma. This is, of course, the expected behavior given for the manual entry for the query Q parameter g. # Desired outcome plasma-meta

These are the instructions (https://manjaro.site/how-to-install-yaourt-on-arch-linux/) to install Yaourt: git clone https://aur.archlinux.org/package-query.git cd package-query makepkg -si cd .. git clone https://aur.archlinux.org/yaourt.git cd yaourt makepkg -si I successfully run the first two lines, but when running makepkg I get the error: => ERROR: You do not have write permission for the directory $BUILDDIR (/home/pietrom/package-query). Aborting... I try with: sudo makepkg -si and I get this error: ==> ERROR: Running makepkg as root is not allowed as it can cause permanent, catastrophic damage to your system. I change the file's owner: sudo chown pietrom ./PKGBUILD sudo chgrp users ./PKGBUILD and, again, I get: makepkg -si ==> ERROR: You do not have write permission for the directory $BUILDDIR (/home/pietrom/package-query). Aborting... What am I doing wrong? I havo to install Yaourt to install Google Chrome.

I keep getting this same error when trying to install various packages: make: error while loading shared libraries: libunistring.so.0: cannot open shared object file: No such file or directory It's occurred while trying to install the Ruby gem Gosu as well as some free Linux games like Alien Arena. I even tried re-installing libunistring with pacman to no avail.

I update my Arch-Linux system using yaourt. When updating packages from the AUR, yaourt doesn't allow itself to be run as root, so it instead asks for sudo privileges every time it installs / updates a package. I don't mind this too much, however if I don't notice my terminal asking for my sudo password, it might be a few minutes until I check and notice it. When this happens, even though I type my password in correctly, I get an authentication error message, and it asks for my password again a few times, even though it still wouldn't work. So my question is: how can I disable the sudo password prompt from timing out?

I'm new to arch so any help on this subject is much appreciated. I have been trying to install yaourt on manjaro, but this is the error message I receive. [manjaro@manjaro-pc ~]$ sudo pacman -S yaourt error: target not found: yaourt

I came across [this article](https://itsfoss.com/best-aur-helpers/) saying that yaourt is deprecated. I wanted to look up more information about that on Arch Wiki, but found that yaourt is not listed on the [list of AUR helpers](https://wiki.archlinux.org/index.php/AUR_helpers) , which is bewildering. Is yaourt really deprecated? If so, what are the reasons? Is there an official announcement on Arch Wiki? And what are some widely recognized alternatives to yaourt among those listed on the page just cited (if not all of them)?

I'm a bit of a newcomer to Arch Linux and still getting used to some of its paradigms. I come with a lot of habits from another distro that was quite a bit more structured and in some ways predictable. One thing I would like to do with a few systems¹ is enable a cron job to do automatic updates of all system packages. This seems like it would be pretty easy except I also want some meaningful feedback from the system telling me how things went that was not so verbose that I end up ignoring it until I discover the system is acting up. * The full output of pacman is unnecessary. I don't care how long the downloads took or that it is on update 46 of 53. * For the most part I don't care about successes. * I do care about errors. If an update run fails I want to know about it and any specific error messages should be patched through. * I do care about the "notices" given off during install. For example today's systemd update said: > :: coredumps are no longer sent to the journal by default. To re-enable: > echo >/etc/sysctl.d/50-coredump.conf \ > "kernel.core_pattern=|/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e" Or filesystem produced this: > warning: /etc/group installed as /etc/group.pacnew > warning: /etc/passwd installed as /etc/passwd.pacnew > warning: /etc/shadow installed as /etc/shadow.pacnew This last category is actually what prompted me to ask this question because it seems these are very inconsistent across the package set. Some of these seem to be generated by post_upgrade(), others by install(), etc. Sometimes they are written to stdout, sometimes to stderr. The format of the messages varies widely: sometimes a whole block is prefixed on indented in some way, other times there is just a bare echoed string. I want to know about things that may require my intervention on a system but not be bothered otherwise. Is there a tool out there that intelligently manages this data and simplifies the system administration? Is there any way to get the output generated by packages separately from the pacman process installing them? Or am I on my own to write some kind of parser that filters out benign stuff from the install log? ¹ Before you jump all over how stupid this is please note that I'm smart enough to not do this on production servers and not without snapshot based full system backups that would make recovery easy in the event of a catastrophe.

Is there a way to make yaourt does not reinstall when the package (from AUR) already installed $ yaourt -Q jruby local/jruby 1.7.3-1 but somehow $ yaourt --needed --noconfirm -S jruby keep redownload (even if it has been downloaded before) and reinstall jruby

I try to install rar using yaourt, problem is I get +5k results and can't filter out the package containing rar. Neither |grep helps nor |head, the first hundreds of lines are lib'rar'ies. What could I do to get around this?

At some point, I had an error with dependencies and had to remove some forcefully with pacman -Rdd libvpx libx264. I have since reinstalled them, however I get this error upon each yaourt -Syua: error: missing 'libvpx.so=4-64' dependency for 'ffmpeg0.10' error: missing 'libx264.so=148-64' dependency for 'ffmpeg0.10' Here is what I did to track down the problem ~ $ pacman -Qs libvpx local/libvpx 1.7.0-1 VP8 and VP9 codec ~ $ pacman -Qs libx264 local/libx264 2:152.20171224-1 Library for encoding H264/AVC video streams (8bit depth) I do not get the error when I run pacman -Syu.

When I was installing [code](https://aur.archlinux.org/packages/code/) with yaourt -S code, something like ctrl d was typed accidentally. Then I try to install yaourt -S code again: gyp: Call to 'pkg-config --libs-only-l libsecret-1' returned exit status 0 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:336:16) gyp ERR! stack at ChildProcess.emit (events.js:180:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12) gyp ERR! System Linux 4.14.21-1-MANJARO gyp ERR! command \"/usr/bin/node\" \"/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\" \"rebuild\" gyp ERR! cwd /tmp/yaourt-tmp-czxyl/aur-code/src/vscode/node_modules/keytar gyp ERR! node -v v9.8.0 [proxychains] DLL init: proxychains-ng 4.12 [proxychains] DLL init: proxychains-ng 4.12 ==> ERROR: A failure occurred in build(). [proxychains] DLL init: proxychains-ng 4.12 Aborting... [proxychains] DLL init: proxychains-ng 4.12 [proxychains] DLL init: proxychains-ng 4.12 ==> ERROR: Makepkg was unable to build code. [proxychains] DLL init: proxychains-ng 4.12 [proxychains] DLL init: proxychains-ng 4.12 ==> Restart building code ? [y/N] ==> ----------------------------- ==> n How can I fix it?

I am trying to install Gimp 2.9 in arch linux. Following instructions from [this site](http://www.taringa.net/post/linux/18536472/Instalar-GIMP-2-9-en-ArchLinux-Manjaro.html) (which I can hardly understand), I have attempted to install gimp-devel via yaourt. However, I receive an error reporting target not found: gimp-devel. If I attempt to install gimp-git, I receive a large number of errors: error: failed to commit transaction (conflicting files) python-markupsafe: /usr/lib/python3.6/site-packages/MarkupSafe-0.23-py3.6.egg-info/PKG-INFO exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/MarkupSafe-0.23-py3.6.egg-info/SOURCES.txt exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/MarkupSafe-0.23-py3.6.egg-info/dependency_links.txt exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/MarkupSafe-0.23-py3.6.egg-info/not-zip-safe exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/MarkupSafe-0.23-py3.6.egg-info/top_level.txt exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/__init__.py exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/__pycache__/__init__.cpython-36.pyc exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/__pycache__/_compat.cpython-36.pyc exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/__pycache__/_constants.cpython-36.pyc exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/__pycache__/_native.cpython-36.pyc exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/__pycache__/tests.cpython-36.pyc exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/_compat.py exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/_constants.py exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/_native.py exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/_speedups.c exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/_speedups.cpython-36m-x86_64-linux-gnu.so exists in filesystem python-markupsafe: /usr/lib/python3.6/site-packages/markupsafe/tests.py exists in filesystem Errors occurred, no packages were upgraded. Is there a better way to install Gimp 2.9 on arch? Or is there a way to fix my gimp-git errors? (I am presuming that removing the files specified will allow installation to continue.)

How do I install applications using yaourt under proxy network. For pacman I can simply use: export http_proxy=http://usernm:passwd@link:port sudo -E pacman -S application But how do I do this for yaourt as it is not used with sudo priveledges.

###Disclaimer: _This really is not a major issue critical to the stable operation of my system but I am asking this because I simply can't make any sense of it and I would really like to know what is going on here._ I am running an arch linux box and just did yaourt -Syua. Everything went fine. I did a reboot and checked systemctl list-units --state failed to see ntpd.service as a result. I journalctl -r -u ntpd and found the entry Apr 24 19:54:33 htpc ntpd: /usr/bin/ntpd: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory Running ldconfig -v | grep libcrypto yielded libcrypto.so.1.1 -> libcrypto.so.1.1 Which in turn belongs to openssl # yaourt -Ql | grep libcrypto openssl /usr/lib/libcrypto.so openssl /usr/lib/libcrypto.so.1.1 I then thought maybe something didn't upgrade the first time I ran yaourt -Syua so I tried a second time with no upgrade candidates. And the most likely candidate would be ntp anyway given that openssl was upgraded successfully # yaourt -Si openssl | grep Version && yaourt -Qi openssl | grep Version Version : 1.1.0.e-1 Version : 1.1.0.e-1 Checking ntpversion # yaourt -Si ntp | grep Version && yaourt -Qi ntp | grep Version Version : 4.2.8.p9-2 // in the offical Extra repo Version : 4.2.8.p10-1 // installed on my system?? Just to see what would happen I tried to (re-)install ntp # yaourt -Sy ntp :: Synchronising package databases... core is up to date extra is up to date archlinuxfr is up to date community is up to date multilib is up to date warning: downgrading package ntp (4.2.8.p10-1 => 4.2.8.p9-2) Packages (1) ntp-4.2.8.p9-2 Total Download Size: 1.71 MiB Total Installed Size: 4.09 MiB Net Upgrade Size: -0.10 MiB :: Proceed with installation? [Y/n] This then completely flustered me. It wants me to downgrade ntp when I just upgraded openssl in order to use the correct libcrypto.so? # cat /var/log/pacman.log | grep openssl [2017-04-24 19:23] [ALPM] upgraded openssl (1.0.2.k-1 -> 1.1.0.e-1) # cat /var/log/pacman.log | grep ntp [2017-04-13 18:08] [ALPM] upgraded ntp (4.2.8.p9-1 -> 4.2.8.p10-1) Also when looking at the official [Arch Linux]() site, it says for the ntppackage its outdated stating ntp 4.2.8.p9-2 as the current version. ###My Questions - How is it possible that I have a newer ntpversion than stated in the official Extra repository while I only have one other custom repository ([archlinuxfr] - for yaourt) that does not carry ntp? I checked. - Why is yaourt/pacman suggesting me to downgrade my package? - Will downgrading my package actually solve my ntp problem or should I rather downgrade openssl assuming there to be the right libcrypto.so version? ###Edit 1 I have a second arch linux box I also upgraded today where I dont have the issue. Here are the two pacman.log's in comparison. Might shed also some light on this: BoxRunningFine# cat /var/log/pacman.log | grep -e "upgraded openssl" -e "upgraded ntp" [2017-01-04 21:26] [ALPM] upgraded ntp (4.2.8.p8-1 -> 4.2.8.p9-1) [2017-02-28 19:05] [ALPM] upgraded openssl (1.0.2.j-1 -> 1.0.2.k-1) [2017-04-24 18:48] [ALPM] upgraded openssl (1.0.2.k-1 -> 1.1.0.e-1) [2017-04-24 18:49] [ALPM] upgraded ntp (4.2.8.p9-1 -> 4.2.8.p9-2) BoxWithIssue# cat /var/log/pacman.log | grep -e "upgraded ntp" -e "upgraded openssl" [2016-06-05 03:18] [ALPM] upgraded ntp (4.2.8.p7-1 -> 4.2.8.p8-1) [2016-10-21 18:17] [ALPM] upgraded openssl (1.0.2.h-1 -> 1.0.2.j-1) [2017-01-06 14:18] [ALPM] upgraded ntp (4.2.8.p8-1 -> 4.2.8.p9-1) [2017-02-08 22:54] [ALPM] upgraded openssl (1.0.2.j-1 -> 1.0.2.k-1) [2017-04-13 18:08] [ALPM] upgraded ntp (4.2.8.p9-1 -> 4.2.8.p10-1) [2017-04-24 19:23] [ALPM] upgraded openssl (1.0.2.k-1 -> 1.1.0.e-1) By the looks of it the upgrading timing on the box with the issues was just poor. Guess that would be a classic case of bad luck. So then I just downgrade to 4.2.8.p9-2 and it should be fine I reckon? ###Edit 2 # yaourt -Sy ntp warning: downgrading package ntp (4.2.8.p10-1 => 4.2.8.p9-2) Packages (1) ntp-4.2.8.p9-2 :: Proceed with installation? [Y/n] :: Retrieving packages... ntp-4.2.8.p9-2-x86_64 (1/1) downgrading ntp # systemctl start ntpd && systemctl status ntpd ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2017-04-24 21:14:41 CEST; 5s ago # yaourt -Qi ntp Name : ntp Version : 4.2.8.p9-2 # systemctl status | grep -m1 State: State: running Problem solved. Downgrading to _ntp-4.2.8.p9-**2**_ was the solution. Thanks for the help and providing the according resources.

I've installed my first Arch Linux setup, and loving it thus far, with the small exception of setting up my dev environment properly. My previous OS was Ubuntu 16.04 on which I ran Nginx, PHP5.6-FPM and PHP7.0-FPM for my local Magento and Drupal development. Adding the ppa:ondrej/php repo, I was able to install all the additional PHP extensions I needed. However now that I've migrated to Arch, things aren't that clear cut ... browsing the AUR, I don't see packages for things I would normally install, such as: php5.6-cli, php5.6-common, php5.6-json, php5.6-mysql, php5.6-mbstring, php5.6-curl, php5.6-sqlite3, php5.6-soap, php5.6-zip, php5.6-dev, etc. Similar thing goes for PHP7.0 extensions. So I proceeded with installing PHP5.6 and 7.0 by running: yaourt -S php56-fpm & yaourt -S php70-fpm Those package builds went along okay. I then opened the relevant php.ini files (/etc/php56/php.ini & /etc/php70/php.ini) to see that some of the extensions I required merely needed to be uncommented to be enabled. However, for something like php5.6-json, php5.6-common, php5.6-cli or php7.0-json for instance, I can't find a package. I then thought that perhaps I need to compile them from source. I did try googling this only to get confused among the results that I received. To start with I did download the php-5.6.30 tarball from php.net and extracted it on my machine. In the ext folder I do see most of the additional extensions I need (except php5.6-cli and php5.6-common). From this point I have no idea on how to proceed, but figure this is a great opportunity to learn more about my chosen OS for the future - no doubt I'll be needing it again! So my long-winded explanation finally comes to an end here, but I'm reaching out to anyone out there who can help me solve this or help me understand it better. Many many thanks!!

How can I list the dependencies for a given package? I thought this should be an easy task for Google, but I only found yaourt -Sq --depends , which lists all packages that depend on ``. I was not able to find the other way around: list all dependencies that need to be installed for ``.

Since yesterday, i have a problem and i can't install conky-lua. I have the errors belows and i have tried to install others package and change my pkgbuild but nothing change. When I try : yaourt -S conky-lua I get the following error: > -> ERROR : A failure occured in build() > Aborting ... > -> ERROR : Makepkg was unable to build conky lua.

When trying to install the package kodi-standalone-service however after I get prompted for editing the PKGBUILD then I get this error. makepkg: invalid option '--asroot' Unable to read PKGBUILD I can't seem to find anything on this with google. This also happens in the ISL package as well. (BTW I'm using Yaourt to install this)

I'm stuck in an archiso/chrooted environment (booting from a USB flash drive) because my Wi-Fi drivers are incompatible with Linux 4.8.7-1, and cause the system to hang at boot. I'm trying a few things right now: - First of all, I got rid of the b43-firmware via yaourt -R after chrooting into my mounted internal hard drive. The uninstall was successful as far as I know; no errors or warnings were raised. I can still access the internet via an Ethernet dongle at this point. - Unfortunately, this caused an error where, during boot, after the grub menu, I got the following error messages: b43-phy0 ERROR: Firmware file "b43/ucode29_mimo.fw" not found b43-phy0 ERROR: Firmware file "b43-open/ucode29_mimo.fw" not found b43-phy0 ERROR: You must go to http://wireless.kernel.org/users/Drivers/b43#devicefirmware and download the correct firmware... - I'm now trying to downgrade my kernel back to 4.8.6-1, but I'm having some trouble with that too. After chrooting into my mounted root partition (which is about 200GB; about 10GB used), I cd into /var/cache/pacman/pkg and try to pacman -U linux-4.8.6-1-x86_64.pkg.tar.xz linux-headers-4.8.6-1.pkg.tar.xz, but for some reason I get these errors: error: could not open file: /etc/mtab: No such file or directory error: could not determine filesystem mount points error: not enough free disk space Now, the first error is just plain wrong. /etc/mtab is available as a symlink to /proc/self/mounts; I'm not sure what the second error is even talking about; and the third error is also straight up wrong: a Linux kernel downgrade shouldn't use over 190GB of space. At this point, I've also tried to reinstall b43-firmware via yaourt in the chrooted environment, but no matter what package I try to install, I get something along the lines of target not found, even when the package shows up via yaourt -Ss. It's also worth noting that Yaourt's interactive environment doesn't actually work inside chroot. How can I either: - Resolve the issues preventing me from downgrading the kernel; or - Resolve the issues with the wireless drivers which are keeping me from booting?