[Solved] KDE 4.7: nepomukcontroller exists in filesystem

When upgrading, after downloading everything, I get the following:
checking for file conflicts [################################################################] 100%
error: failed to commit transaction (conflicting files)
kdebase-runtime: /usr/bin/nepomukcontroller exists in filesystem
kdebase-runtime: /usr/share/applications/kde4/nepomukcontroller.desktop exists in filesystem
Errors occurred, no packages were upgraded.
The only other reference I've found to this issue is this post on the Chackra forums, but without replies. I've also checked the public dev mailing list, but no mention of the issue there, either. Can anyone help? Thanks in advance.
Last edited by gauthma (2011-07-30 10:28:34)

sumski wrote:
pacman -Qo /usr/bin/nepomukcontroller
https://bbs.archlinux.org/viewtopic.php?id=56373
Yep, that's what I should have done. But I somehow convinced myself that this was a problem with the update itself, and so my perspective narrowed... Anyway problem solved now (thanks for the reply nonetheless!)

Similar Messages

[solved] mesa-dri: /etc/drirc exists in filesystem

EDIT: The following problem was solved by upgrading the system using `pacman -Suy` instead of `yaourt -Suy`
The problem was:
I'm trying to install mesa-dri, because my system refuses to upgrade. However, it gives me this error.
(1/1) checking for file conflicts [########################################################] 100%
error: failed to commit transaction (conflicting files)
mesa-dri: /etc/drirc exists in filesystem
mesa-dri: /usr/lib/xorg/modules/dri/swrast_dri.so exists in filesystem
Errors occurred, no packages were upgraded.
I tried to see what ows those files and install mesa, but
➜ ~ pacman -Qo /etc/drirc
/etc/drirc is owned by mesa 10.2.8-1
➜ ~ pacman -Qo /usr/lib/xorg/modules/dri/swrast_dri.so
/usr/lib/xorg/modules/dri/swrast_dri.so is owned by mesa 10.2.8-1
➜ ~ yaourt -S mesa
[sudo] password for steve:
resolving dependencies...
looking for inter-conflicts...
:: mesa-dri and ati-dri are in conflict. Remove ati-dri? [y/N] y
:: mesa-dri and intel-dri are in conflict. Remove intel-dri? [y/N] y
:: mesa-dri and nouveau-dri are in conflict. Remove nouveau-dri? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: mesa-libgl: requires mesa=10.2.8
I'm not sure where I should look for a solution to this problem and what should I do. I don't want to force anything if it can make my system unusable. Can anybody point me in the right direction to do this safely?
mesa-libgl is required by
➜ ~ pacman -Qi mesa-libgl
Required By : ati-dri bumblebee cairo compton-git freeglut glu intel-dri libva mesa-demos mplayer mpv nouveau-dri qt4 qt5-base sdl2
simplescreenrecorder webkitgtk2 xorg-server xorg-xdriinfo
Last edited by SteveSapolsky (2014-10-23 12:46:11)

WorMzy wrote:
Can you post the full output of
# pacman -Syu
A rookie mistake on my part. I was assuming that if `yaourt -Suy` gave this message then pacman would as well. I tried
pacman -Suy
And pacman upgraded my system without problems.
FTR, here is what `yaourt -Suy` was giving me:
➜ ~ yaourt -Suy
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: failed to prepare transaction (could not satisfy dependencies)
:: Starting full system upgrade...
:: ati-dri: requires mesa=10.2.8
:: intel-dri: requires mesa=10.2.8
:: lib32-intel-dri: requires lib32-mesa=10.2.8
:: nouveau-dri: requires mesa=10.2.8

[SOLVED] linux: /boot/vmlinuz-linux exists in filesystem

I have had this issue for a while now. I ignored it but now I'd like to be able to upgrade. Pacman throws this error:
error: failed to commit transaction (conflicting files)
linux: /boot/vmlinuz-linux exists in filesystem
Errors occurred, no packages were upgraded.
There are now news at archlinux.org, and I'm hesitant to use the --force flag. What do you suggest? Also, I have linux-ck-kernel, if that's relevant to the issue.
Last edited by rubik (2015-01-21 14:19:37)

I don't know how I installed linux-ck-kernel, it's been a while. I probably followed the wiki.
@a821: Here are the commands' outputs:
$ pacman -Qo /boot/vmlinuz-linux
error: No package owns /boot/vmlinuz-linux
$ uname -a
Linux miki-laptop 3.17.5-1-ck #1 SMP PREEMPT Sun Dec 7 07:23:18 EST 2014 x86_64 GNU/Linux
I'm puzzled! Why would pacman care about that file if no package owns it?! The wiki says that in this case I should rename it and update again. I'll try and see what happens.
Last edited by rubik (2015-01-21 13:24:47)

[SOLVED] Update fails ("/usr/lib64 exists in filesystem")

Hi,
today I wanted to update my arch linux. I selected all packages:
bash-4.2.042-2 filesystem-2013.01-1 gcc-4.7.2-4 gcc-libs-4.7.2-4 glibc-2.17-2 linux-api-headers-3.7.4-1 mkinitcpio-0.12.0-3 sudo-1.8.6.p5-1 transmission-gtk-2.76-2
But then I've got following error (translated from German to English)
Error: Could not complete procedure (conflicts in files)
filesystem: /usr/lib64 exists in filesystem
Any idea?
Best regards
Steffo
Last edited by Steffo (2013-01-27 12:42:45)

swordfish wrote:
Please have a look at this:
https://wiki.archlinux.org/index.php/De … i%3Ausrlib
This doesn't work:
sudo pacman -U -d http://pkgbuild.com/~allan/glibc-2.16.0-1-x86_64.pkg.tar.xz
I get following error:
error: failed to commit transaction (conflicting files)
glibc: /lib/ld-linux-x86-64.so.2 exists in filesystem
glibc: /lib/libBrokenLocale.so.1 exists in filesystem
glibc: /lib/libanl.so.1 exists in filesystem
glibc: /lib/libc.so.6 exists in filesystem
glibc: /lib/libcidn.so.1 exists in filesystem
glibc: /lib/libcrypt.so.1 exists in filesystem
glibc: /lib/libdl.so.2 exists in filesystem
glibc: /lib/libm.so.6 exists in filesystem
glibc: /lib/libnsl.so.1 exists in filesystem
glibc: /lib/libnss_compat.so.2 exists in filesystem
glibc: /lib/libnss_db.so.2 exists in filesystem
glibc: /lib/libnss_dns.so.2 exists in filesystem
glibc: /lib/libnss_files.so.2 exists in filesystem
glibc: /lib/libnss_hesiod.so.2 exists in filesystem
glibc: /lib/libnss_nis.so.2 exists in filesystem
glibc: /lib/libnss_nisplus.so.2 exists in filesystem
glibc: /lib/libpthread.so.0 exists in filesystem
glibc: /lib/libresolv.so.2 exists in filesystem
glibc: /lib/librt.so.1 exists in filesystem
glibc: /lib/libthread_db.so.1 exists in filesystem
glibc: /lib/libutil.so.1 exists in filesystem
Errors occurred, no packages were upgraded.

[SOLVED] libido3 preventing pacman update exists in filesystem

After running pacman -Syu, I receive the infamous .../exists in filesystem
I read the wiki and pacman -Qo on each of the trouble files results in the owner being libido3 12.10.2-100
I do have unity installed through the arch repositories.
If there was no owner, I would remove them, however since the files are owned by something, I don't know what to do next.
Thanks
Last edited by glenn69 (2013-01-29 23:48:42)

I can't seem to find much about the file online either. I'm not sure if ido is the same file as libido?
... but the result of pacman -Qo on a problem file results in
/usr/include/libido3-0.1/libido/idoentrymenuitem.h is owned by libido3 12.10.2-100
then I searched for libido with this result:
[root@Arch-Home_x86_64 ~]# find / -name libido3*
/var/cache/pacman/pkg/libido3-12.10.2-100-x86_64.pkg.tar.xz
/var/lib/pacman/local/libido3-12.10.2-100
/usr/include/libido3-0.1
/usr/lib/pkgconfig/libido3-0.1.pc
/usr/lib/libido3-0.1.so.0.0.0
/usr/lib/libido3-0.1.so
/usr/lib/libido3-0.1.so.0

[Solved] Error when updating: file exists in filesystem

Hello all,
While updating with pacman my laptop overheated and turned off.
After rebooting I removed /var/lib/pacman/db.lck.
When I resume pacman -Syu I get:
http://pastebin.com/7c1iTgWG
Is there any way to fix this or is a fresh install in order?
Thank you very much for your help
Last edited by vidar-mud (2012-11-21 18:50:29)

Welcome to the boards. Please read our Forum Etiquette https://wiki.archlinux.org/index.php/Forum_Etiquette
You should also read the stickies in Newbie Corner, notably the Common Problems and Issues one, where yours is described.

[SOLVED] /usr/share/aclocal/nspr.m4 exists in filesystem

pacman -Syu fails with this error:
error: failed to commit transaction (conflicting files)
nspr: /usr/share/aclocal/nspr.m4 exists in filesystem
Errors occurred, no packages were upgraded.
I found this thread, which suggested resyncing mirrors, but that didn't help.
Last edited by FreeAsInGimme (2013-08-03 14:21:14)

FYI: archlinux is widely known for our excellent wiki. Be sure to check there and search the forums before starting new threads. Many problems can be solved with a good search.
As a second FYI, I don't know if the use of the manjaro boards (linked in OP) was just a coincidence of what your previous search gave you or if you are using Manjaro. If it's the latter there are many differences between Manjaro and Archlinux. In this case they are similar enough to share a solution, but in other cases we would be unable to help you here. In short, if you are using Manjaro, be sure to ask on their forums if you have future problems.

[SOLVED] jdk7-openjdk exists in filesystem when it's not installed

I'm having a problem updating the jdk7-openjdk package (jdk7-openjdk-7.u21_2.3.9-4). When I went to update via pacman, pacman replied that files existed in the filesystem. I removed the jdk and reinstalled, only to be told that the package still exists in the filesystem.
$ sudo pacman -S jdk7-openjdk
resolving dependencies...
looking for inter-conflicts...
Packages (1): jdk7-openjdk-7.u21_2.3.9-4
Total Installed Size: 19.34 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [##########################] 100%
(1/1) checking package integrity [##########################] 100%
(1/1) loading package files [##########################] 100%
(1/1) checking for file conflicts [##########################] 100%
error: failed to commit transaction (conflicting files)
jdk7-openjdk: /usr/bin/appletviewer exists in filesystem
jdk7-openjdk: /usr/bin/apt exists in filesystem
jdk7-openjdk: /usr/bin/extcheck exists in filesystem
jdk7-openjdk: /usr/bin/idlj exists in filesystem
jdk7-openjdk: /usr/bin/jar exists in filesystem
jdk7-openjdk: /usr/bin/jarsigner exists in filesystem
jdk7-openjdk: /usr/bin/javac exists in filesystem
jdk7-openjdk: /usr/bin/javadoc exists in filesystem
jdk7-openjdk: /usr/bin/javah exists in filesystem
jdk7-openjdk: /usr/bin/javap exists in filesystem
jdk7-openjdk: /usr/bin/jcmd exists in filesystem
jdk7-openjdk: /usr/bin/jconsole exists in filesystem
jdk7-openjdk: /usr/bin/jdb exists in filesystem
jdk7-openjdk: /usr/bin/jhat exists in filesystem
jdk7-openjdk: /usr/bin/jinfo exists in filesystem
jdk7-openjdk: /usr/bin/jmap exists in filesystem
jdk7-openjdk: /usr/bin/jps exists in filesystem
jdk7-openjdk: /usr/bin/jrunscript exists in filesystem
jdk7-openjdk: /usr/bin/jsadebugd exists in filesystem
jdk7-openjdk: /usr/bin/jstack exists in filesystem
jdk7-openjdk: /usr/bin/jstat exists in filesystem
jdk7-openjdk: /usr/bin/jstatd exists in filesystem
jdk7-openjdk: /usr/bin/native2ascii exists in filesystem
jdk7-openjdk: /usr/bin/rmic exists in filesystem
jdk7-openjdk: /usr/bin/schemagen exists in filesystem
jdk7-openjdk: /usr/bin/serialver exists in filesystem
jdk7-openjdk: /usr/bin/wsgen exists in filesystem
jdk7-openjdk: /usr/bin/wsimport exists in filesystem
jdk7-openjdk: /usr/bin/xjc exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/appletviewer exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/apt exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/extcheck exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/idlj exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jar exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jarsigner exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/java exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/java-rmi.cgi exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/javac exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/javadoc exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/javah exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/javap exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jcmd exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jconsole exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jdb exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jhat exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jinfo exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jmap exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jps exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jrunscript exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jsadebugd exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jstack exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jstat exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/jstatd exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/keytool exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/native2ascii exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/orbd exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/pack200 exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/policytool exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/rmic exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/rmid exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/rmiregistry exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/schemagen exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/serialver exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/servertool exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/tnameserv exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/unpack200 exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/wsgen exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/wsimport exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/bin/xjc exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/lib/ct.sym exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/lib/jconsole.jar exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/lib/sa-jdi.jar exists in filesystem
jdk7-openjdk: /usr/lib/jvm/java-7-openjdk/lib/tools.jar exists in filesystem
jdk7-openjdk: /usr/share/applications/jconsole.desktop exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/appletviewer.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/apt.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/extcheck.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/idlj.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jar.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jarsigner.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/javac.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/javadoc.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/javah.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/javap.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jcmd.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jconsole.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jdb.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jhat.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jinfo.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jmap.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jps.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jrunscript.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jsadebugd.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jstack.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jstat.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/jstatd.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/native2ascii.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/rmic.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/schemagen.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/serialver.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/wsgen.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/wsimport.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/ja/man1/xjc.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/appletviewer.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/apt.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/extcheck.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/idlj.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jar.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jarsigner.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/javac.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/javadoc.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/javah.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/javap.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jcmd.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jconsole.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jdb.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jhat.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jinfo.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jmap.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jps.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jrunscript.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jsadebugd.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jstack.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jstat.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/jstatd.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/native2ascii.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/rmic.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/schemagen.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/serialver.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/wsgen.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/wsimport.1.gz exists in filesystem
jdk7-openjdk: /usr/share/man/man1/xjc.1.gz exists in filesystem
Errors occurred, no packages were upgraded.
$
But when I go to check if it's installed:
$ pacman -Q | grep jdk
jre7-openjdk 7.u21_2.3.9-4
jre7-openjdk-headless 7.u21_2.3.9-4
$
The JREs are there, but the JDK is not. So somehow it's installed and not installed at the same time. How do I tell pacman that the installed package is not installed when it says it's both installed and not installed? Pacman -Rdd does not work as it's not installed. Pacman -S doesn't work as it's installed.
Last edited by 12o (2013-05-20 17:06:08)

Thank you very much for your help. I greatly appreciate it. I only use pacman to upgrade, update, or remove anything. Even if the package is from the AUR; in which case I use the -U. In this case, I tried to install the JRE, JRE headless, and the JDK at the same time. All of the tanked, so I used the pacman -Rdd to remove the JDK package. That's when the trouble started.
If it's safe to use the --force command in this case, I'll try it.
**UPDATE**
Looks like using the --force option worked. When I run the previous command, I get:
$ pacman -Qo /usr/bin/appletviewer
/usr/bin/appletviewer is owned by jdk7-openjdk 7.u21_2.3.9-4
$
Thanks again for the help! I'll mark the thread 'solved'.
Last edited by 12o (2013-05-20 17:05:48)

[SOLVED] error pacman: /var/cache/pacman/pkg exists in filesystem

Hi guys, yesterday night I tried to update my system and I got the following error which seems weird:
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
core/pacman 4.2.0-5 4.2.0-6 0.00 MiB
Total Installed Size: 4.22 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [##########################################################] 100%
(1/1) checking package integrity [##########################################################] 100%
(1/1) loading package files [##########################################################] 100%
(1/1) checking for file conflicts [##########################################################] 100%
error: failed to commit transaction (conflicting files)
pacman: /var/cache/pacman/pkg exists in filesystem
Errors occurred, no packages were upgraded.
It seems weird to me because it conflicts to the whole folder and not to any specific package. Any clue, what is going on and how to solve it?
Last edited by theodore (2015-01-26 19:51:37)

clfarron4 wrote:
theodore wrote:
Allan wrote:Is your /var/cache/pacman/pkg a directory or a symlink?
yes I have it in a different partition and then I have symilinked it
I'd have thought it would have been better to set a different directory for the pacman cache, mounting the partition to that through /etc/fstab and using the CacheDir variable in /etc/pacman.conf, but I'll leave that to your judgement.
If you don't want to do that, then I'll leave someone else to put up a solution (my brain's screaming bind mounts for some unknown reason).
So, you are saying that I should enable the CacheDir in /etc/pacman.conf and point it to the partition where I have now the pacman cache.

Can't Update Because file "exists in filesystem" [SOLVED]

I am having the below problem:
$ sudo pacman -Suyy
:: Synchronizing package databases...
core 112.9 KiB 2.83M/s 00:00 [###############################################] 100%
extra 1763.2 KiB 845K/s 00:02 [###############################################] 100%
community 2.3 MiB 2.65M/s 00:01 [###############################################] 100%
archlinuxfr 19.7 KiB 160K/s 00:00 [###############################################] 100%
:: Starting full system upgrade...
error: could not open file /var/lib/pacman/local/ldb-1.1.16-1/desc: No such file or directory
:: Replace lzo2 with core/lzo? [Y/n]
resolving dependencies...
error: could not open file /var/lib/pacman/local/libgxps-0.2.2-3/desc: No such file or directory
looking for inter-conflicts...
Packages (43): cairo-1.12.16-3 cups-1.7.5-1 device-mapper-2.02.108-1 dhcpcd-6.4.3-1 e2fsprogs-1.42.11-1 epiphany-3.12.1-2
ffmpeg-1:2.3.1-1 gettext-0.19.2-1 git-2.0.4-1 kdelibs-4.13.3-2 ldb-1.1.17-1 libarchive-3.1.2-8 libcups-1.7.5-1
libkolab-0.5.2-1 libpeas-1.10.1-1 libutil-linux-2.25-3 libwbclient-4.1.11-1 linux-3.15.8-1 linux-headers-3.15.8-1
lvm2-2.02.108-1 lzo-2.08-3 lzo2-2.08-1 [removal] meld-3.11.2-3 mesa-10.2.5-1 mkinitcpio-18-1 parted-3.2-1
phpmyadmin-4.2.7-1 python-setuptools-1:5.4.2-1 python2-boto-2.32.1-1 s-nail-14.7.5-1 samba-4.1.11-1
smartmontools-6.3-1 smbclient-4.1.11-1 syslinux-6.03pre19-1 tar-1.28-1 tdb-1.3.0-2 traceroute-2.0.20-1
util-linux-2.25-3 virtualbox-4.3.14-3 xorg-server-1.16.0-6 xorg-server-common-1.16.0-6 xorg-xrandr-1.4.3-1
zenity-3.12.1-2
Total Installed Size: 450.30 MiB
Net Upgrade Size: 1.10 MiB
:: Proceed with installation? [Y/n]
(42/42) checking keys in keyring [###############################################] 100%
(42/42) checking package integrity [###############################################] 100%
(42/42) loading package files [###############################################] 100%
(42/42) checking for file conflicts [###############################################] 100%
error: failed to commit transaction (conflicting files)
ldb: /usr/bin/ldbadd exists in filesystem
ldb: /usr/bin/ldbdel exists in filesystem
ldb: /usr/bin/ldbedit exists in filesystem
ldb: /usr/bin/ldbmodify exists in filesystem
ldb: /usr/bin/ldbrename exists in filesystem
ldb: /usr/bin/ldbsearch exists in filesystem
ldb: /usr/include/ldb.h exists in filesystem
ldb: /usr/include/ldb_errors.h exists in filesystem
ldb: /usr/include/ldb_handlers.h exists in filesystem
ldb: /usr/include/ldb_module.h exists in filesystem
ldb: /usr/include/ldb_version.h exists in filesystem
ldb: /usr/include/pyldb.h exists in filesystem
ldb: /usr/lib/ldb/libldb-cmdline.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/asq.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/ldap.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/paged_results.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/paged_searches.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/rdn_name.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/sample.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/server_sort.so exists in filesystem
ldb: /usr/lib/ldb/modules/ldb/skel.so exists in filesystem
ldb: /usr/lib/libldb.so exists in filesystem
ldb: /usr/lib/libldb.so.1 exists in filesystem
ldb: /usr/lib/libpyldb-util.so exists in filesystem
ldb: /usr/lib/libpyldb-util.so.1 exists in filesystem
ldb: /usr/lib/pkgconfig/ldb.pc exists in filesystem
ldb: /usr/lib/pkgconfig/pyldb-util.pc exists in filesystem
ldb: /usr/lib/python2.7/site-packages/ldb.so exists in filesystem
Errors occurred, no packages were upgraded.
Recently I did have a problem with my pacman DB files over here but I fixed that. I also tried now making a new empty /var/lib/pacman/sync directory but the output is the same as above.
I tried Googling for this issue but I am not succeededing.
Can anyone advise what I can do to troubleshoot this?
Last edited by CaptainKirk (2014-08-07 11:28:01)

Thank you for that link.
I checked the first two /usr/bin/ldbadd and /usr/bin/ldbdel and no package owns them. So I ran:
sudo pacman -S --force lib32-libdbus
because now I got:
:: Replace lib32-dbus-core with multilib/lib32-libdbus? [Y/n]
because I just enabled multilib in order to upgrade skype (which worked). Anyhow, the install of lib32-libdbus worked fine, but
pacman -Syu
still gives all the errors above. Should I try to rename all those files?
Your title however is misleading - nothing says files are missing, the problem is those files are already there but pacman doesn't know why.
Well, I also see this:
error: could not open file /var/lib/pacman/local/ldb-1.1.16-1/desc: No such file or directory
as well as another. So something does appear to be missing to me.

[SOLVED] PKGBUILD /lib exists in filesystem

Apologies for the similar thread...
I know there's a lot of topics similar to this with particular files conflicting with various packages when installing, but I couldn't quite see the issue with my PKGBUILD.
PKGBUILD contents (without the vars):
package() {
# Unpack the vendor package
cd "${srcdir}"
tar -zxf data.tar.gz
cp -dpr "${srcdir}/usr" "${pkgdir}"
install -Dm0644 "${pkgdir}/usr/share/doc/vpn-unlimited/copyright" \
"${pkgdir}/usr/share/licenses/${pkgname}/copyright"
# Create a custom script that forces the older libcurl
cat > "${pkgdir}/usr/bin/vpnu" <<- EOF
#!/bin/sh
PID=$(pidof vpn-unlimited-daemon)
if [[ $EUID -ne 0 ]]; then
echo "Must be root to run VPN daemon" 1>&2
exit 1
else
if [ -z $PID]; then
vpn-unlimited-daemon &
sleep 2
fi
LD_PRELOAD=libcurl.so.3 vpn-unlimited
fi
EOF
# Change script permissions
chmod 0755 "${pkgdir}/usr/bin/vpnu"
# Alter the desktop file to launch our script instead
sed -i 's/Exec=vpn-unlimited/Exec=vpnu/g' "${pkgdir}/usr/share/applications/vpn-unlimited.desktop"
# Add our custom systemd unit
install -Dm0644 "${srcdir}/vpn-unlimited-daemon.service" "${pkgdir}/lib/systemd/system/vpn-unlimited-daemon.service"
# Save this original file
cp -p "${srcdir}/etc/init.d/vpn-unlimited-daemon" "${pkgdir}/usr/share/doc/vpn-unlimited/"
While building:
vpn-unlimited: /lib exists in filesystem
vpn-unlimited: /usr/sbin exists in filesystem
Errors occurred, no packages were upgraded.
I don't understand why the problem is the symbolic links at /lib and /usr/sbin. Doesn't cp -dpr follow the symlinks?
Last edited by adb (2015-01-11 22:37:32)

Can someone help me changing the PKGBUILD from tm_smapi-ck?
I am getting the same error message:
(1/1) checking for file conflicts [###########################] 100%
error: failed to commit transaction (conflicting files)
tp_smapi-ck: /lib exists in filesystem
Errors occurred, no packages were upgraded.
PKGBUILD:
# Maintainer: fackamato
# Contributor: Steven Davidovitz <steviedizzle Ã° gmail Ä‘ com>
# Contributor: Nick B <Shirakawasuna Ã° gmail Ä‘ com>
# Contributor: Christof Musik <christof Ã° senfdax Ä‘ de>
# Contributor: Stefan Rupp <archlinux Ã° stefanrupp Ä‘ de>
# Contributor: Ignas Anikevicius <anikevicius Ã° gmail Ä‘ com>
_pkgname=tp_smapi
# make the AUR parser think the following lines are comments
# to bypass the buggy parser check
[[ "#" ]] && _kernext=${_kernext:-}
[[ "#" ]] && _kernver=${_kernver:-$(uname -r)}
[[ "#" ]] && _extramodules=$(readlink -f "/usr/lib/modules/$_kernver/extramodules" | sed 's#^/usr/lib/modules/##')
[[ "#" ]] && _kernver=$(< /usr/lib/modules/$_extramodules/version)
pkgname=$_pkgname-ck$_kernext
pkgver=0.41
pkgrel=44
pkgdesc="Modules for ThinkPad's SMAPI functionality, for -ck kernels"
[[ -n $_kernext ]] && pkgdesc+=" (for linux$_kernext)"
arch=('i686' 'x86_64')
url="http://tpctl.sourceforge.net/"
license=('GPL')
depends=("linux$_kernext-ck")
makedepends=("linux$_kernext-headers")
install=$_pkgname-ck.install
source=(https://github.com/downloads/evgeni/tp_smapi/tp_smapi-$pkgver.tar.gz)
md5sums=('63c683415c764568f6bf17c7eabe4752')
sha256sums=('6aef02b92d10360ac9be0db29ae390636be55017990063a092a285c70b54e666')
build() {
cd "$srcdir/tp_smapi-$pkgver"
sed -ri "s/^(KVER\s*:=).*$/\1$_kernver/" Makefile
make HDAPS=1
package() {
make -C "/lib/modules/$_kernver/build" \
INSTALL_MOD_PATH="$pkgdir" M="$srcdir/$_pkgname-$pkgver" modules_install
cd "$pkgdir/lib/modules/"
mv "$_kernver/extra" "$_extramodules"
rmdir "$_kernver"
# compress kernel modules
find "$pkgdir" -name "*.ko" -exec gzip -9 {} +
# update kernel version in install file
sed -ri "s/^(extramodules=).*$/\1$_extramodules/" "$startdir/$_pkgname-ck.install"
Thanks in advance!

[SOLVED] Error "libpng12: /usr/lib/libpng.so.3 exists in filesystem".

I've just tried to install the stable "google-chrome" package from AUR with the command. I have all of the dependencies already installed except for these two:
- libjpeg6 (building from AUR)
- libpng12 (package found)
When the package manage tries to install "libpng12-1.2.43-1", I get the following error:
error: failed to commit transaction (conflicting files)
libpng12: /usr/lib/libpng.so.3 exists in filesystem
Errors occurred, no packages were upgraded.
According to the file manager (Thunar), the file /usr/lib/libpng.so.3 is a link to /usr/lib/libpng.so.
This is probably a silly question (as I'm a clueless newbie!) but... can I just delete this link and expect the installation of libpng12 to replace it so that everything will still work...?
Thanks in advance :-)
Last edited by esuhl (2011-01-21 02:46:19)

$ pacman -Ql libpng|grep /lib/
libpng /usr/lib/
libpng /usr/lib/libpng.a
libpng /usr/lib/libpng.so
libpng /usr/lib/libpng14.a
libpng /usr/lib/libpng14.so
libpng /usr/lib/libpng14.so.14
libpng /usr/lib/libpng14.so.14.5.0
libpng /usr/lib/pkgconfig/
libpng /usr/lib/pkgconfig/libpng.pc
libpng /usr/lib/pkgconfig/libpng14.pc
A tip: run pacman -Qo on the file in question, either you put that symlink there yourself or strange things are happening on your system.

[SOLVED] cannot install perf due to python2 ... exists in filesystem e

sudo pacman -S perf
resolving dependencies...
looking for inter-conflicts...
Packages (2): python2-2.7.5-2 perf-3.11-2
Total Installed Size: 68.71 MiB
:: Proceed with installation? [Y/n]
1 resolving dependencies...
2 looking for inter-conflicts...
3
4 Packages (2): python2-2.7.5-2 perf-3.11-2
5
6 Total Installed Size: 68.71 MiB
7
8 checking keyring...
9 checking package integrity...
10 loading package files...
11 checking for file conflicts...
12 python2: /usr/bin/2to3-2.7 exists in filesystem
13 python2: /usr/bin/idle2 exists in filesystem
14 python2: /usr/bin/pydoc2 exists in filesystem
15 python2: /usr/bin/python2 exists in filesystem
16 python2: /usr/bin/python2-config exists in filesystem
17 python2: /usr/bin/python2.7 exists in filesystem
18 python2: /usr/bin/python2.7-config exists in filesystem
19 python2: /usr/include/python2.7/Python-ast.h exists in filesystem
20 python2: /usr/include/python2.7/Python.h exists in filesystem
21 python2: /usr/include/python2.7/abstract.h exists in filesystem
22 python2: /usr/include/python2.7/asdl.h exists in filesystem
23 python2: /usr/include/python2.7/ast.h exists in filesystem
24 python2: /usr/include/python2.7/bitset.h exists in filesystem
25 python2: /usr/include/python2.7/boolobject.h exists in filesystem
26 python2: /usr/include/python2.7/bufferobject.h exists in filesystem
27 python2: /usr/include/python2.7/bytearrayobject.h exists in filesystem
28 python2: /usr/include/python2.7/bytes_methods.h exists in filesystem
29 python2: /usr/include/python2.7/bytesobject.h exists in filesystem
30 python2: /usr/include/python2.7/cStringIO.h exists in filesystem
31 python2: /usr/include/python2.7/cellobject.h exists in filesystem
32 python2: /usr/include/python2.7/ceval.h exists in filesystem
33 python2: /usr/include/python2.7/classobject.h exists in filesystem
34 python2: /usr/include/python2.7/cobject.h exists in filesystem
35 python2: /usr/include/python2.7/code.h exists in filesystem
36 python2: /usr/include/python2.7/codecs.h exists in filesystem
37 python2: /usr/include/python2.7/compile.h exists in filesystem
38 python2: /usr/include/python2.7/complexobject.h exists in filesystem
39 python2: /usr/include/python2.7/datetime.h exists in filesystem
40 python2: /usr/include/python2.7/descrobject.h exists in filesystem
41 python2: /usr/include/python2.7/dictobject.h exists in filesystem
42 python2: /usr/include/python2.7/dtoa.h exists in filesystem
43 python2: /usr/include/python2.7/enumobject.h exists in filesystem
44 python2: /usr/include/python2.7/errcode.h exists in filesystem
45 python2: /usr/include/python2.7/eval.h exists in filesystem
Errors occurred, no packages were upgraded.
(yes those are line numbers, sorry)
Any ideas?
Last edited by busey (2013-11-11 21:58:55)

There are a number of files on your system that a package wants to provide thus causing a conflict. Aborting with warnings is the expected behavior. Now the question is: what placed the files on your system? Did you manually compile and install python2 or other packages by chance?
Let's see if any package that pacman installed owns one of those files (I'm guessing now); post the output of:
pacman -Qo /usr/include/python2.7/abstract.h
As that was your 1st post, welcome to Arch. Plz use code tags in your posts --> https://bbs.archlinux.org/help.php#bbcode
Last edited by graysky (2013-11-11 20:50:01)

[SOLVED] freeimage: /usr/lib/libfreeimage.so.3 exists in filesystem

Issue:
I can't upgrade.
$ pacman -Syu
error: failed to commit transaction (conflicting files)
freeimage: /usr/lib/libfreeimage.so.3 exists in filesystem
Errors occurred, no packages were upgraded
I check whether a package, possibly from AUR, is responsible:
# pacman -Qo
error: No package owns /usr/lib/libfreeimage.so.3
No.
Apparently this happened to other users as well. I was recommended the following solution:
$ pacman -Sf freeimage
Thanks to jelly1, Hattara-pilvi and Tucos of #archlinux!
Last edited by qubodup (2012-03-22 15:07:46)

$ pacman -Ql libpng|grep /lib/
libpng /usr/lib/
libpng /usr/lib/libpng.a
libpng /usr/lib/libpng.so
libpng /usr/lib/libpng14.a
libpng /usr/lib/libpng14.so
libpng /usr/lib/libpng14.so.14
libpng /usr/lib/libpng14.so.14.5.0
libpng /usr/lib/pkgconfig/
libpng /usr/lib/pkgconfig/libpng.pc
libpng /usr/lib/pkgconfig/libpng14.pc
A tip: run pacman -Qo on the file in question, either you put that symlink there yourself or strange things are happening on your system.

[Solved] Pacman "filesystem: /etc/mtab exists in filesystem"

First of all I want to say hello, it's my first post here.
Well, I tried to update my system with pacman -Syu and I got this error.
[diego@snow ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (6): bluez-4.96-3 filesystem-2011.12-2 glibc-2.14.1-4
libldap-2.4.28-1 liboauth-0.9.6-1 xorg-xinit-1.3.1-2
Total Download Size: 0.00 MB
Total Installed Size: 36.11 MB
Proceed with installation? [Y/n]
(6/6) checking package integrity [######################] 100%
(6/6) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
filesystem: /etc/mtab exists in filesystem
Errors occurred, no packages were upgraded.
I already searched for this and I found out that this is common when using the testing repository, but I'm not using it.
Should i delete /etc/mtab? I also tried to reboot a couple of times and nothing changed.
I can still install new packages.
Last edited by tokoro (2011-12-21 03:47:53)

jasonwryan wrote:Read the news on the front page...
Well, that was easy
When upgrading to filesystem-2011.12 there will be a conflict with /etc/mtab.
Install the package as follows:
pacman -S filesystem --force
It is strongly advised to avoid the --force or -f switch as it is not safe. However, in this particular case it is needed as deleting /etc/mtab manually would break pacman.
The reason for the conflict is that the file used to be generated at boot and hence not owned by any package. Now it is a symlink to /proc/self/mounts owned by filesystem. This change means that initscripts no longer requires write access to the rootfs (though other packages might).
Last edited by tokoro (2011-12-21 03:50:21)

[Solved] KDE 4.7: nepomukcontroller exists in filesystem

Similar Messages

Maybe you are looking for