Pacman "error: failed to commit transaction (conflicting files)"

jadacyrus · 2008-02-23 01:18:28

When I try to install some packages or do -Syu , I get this error:

cleaning up... done.
(7/7) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
gcc-libs: /usr/lib/libgcc_s.so exists in filesystem
gcc-libs: /usr/lib/libgcc_s.so.1 exists in filesystem
gcc-libs: /usr/lib/libgomp.a exists in filesystem
gcc-libs: /usr/lib/libgomp.so exists in filesystem
gcc-libs: /usr/lib/libgomp.so.1 exists in filesystem
gcc-libs: /usr/lib/libgomp.so.1.0.0 exists in filesystem
gcc-libs: /usr/lib/libgomp.spec exists in filesystem
gcc-libs: /usr/lib/libmudflap.a exists in filesystem
gcc-libs: /usr/lib/libmudflap.so exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.0 exists in filesystem
gcc-libs: /usr/lib/libmudflap.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libmudflapth.a exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.0 exists in filesystem
gcc-libs: /usr/lib/libmudflapth.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libobjc.a exists in filesystem
gcc-libs: /usr/lib/libobjc.so exists in filesystem
gcc-libs: /usr/lib/libobjc.so.2 exists in filesystem
gcc-libs: /usr/lib/libobjc.so.2.0.0 exists in filesystem
gcc-libs: /usr/lib/libssp.a exists in filesystem
gcc-libs: /usr/lib/libssp.so exists in filesystem
gcc-libs: /usr/lib/libssp.so.0 exists in filesystem
gcc-libs: /usr/lib/libssp.so.0.0.0 exists in filesystem
gcc-libs: /usr/lib/libssp_nonshared.a exists in filesystem
gcc-libs: /usr/lib/libstdc++.a exists in filesystem
gcc-libs: /usr/lib/libstdc++.so exists in filesystem
gcc-libs: /usr/lib/libstdc++.so.6 exists in filesystem
gcc-libs: /usr/lib/libstdc++.so.6.0.9 exists in filesystem
gcc-libs: /usr/lib/libsupc++.a exists in filesystem
gcc-libs: /usr/share/locale/de/LC_MESSAGES/libstdc++.mo exists in filesystem
gcc-libs: /usr/share/locale/fr/LC_MESSAGES/libstdc++.mo exists in filesystem
errors occurred, no packages were upgraded.

Not sure what to do! Thanks in advance for any help.

lilsirecho · 2008-02-23 02:06:46

Try pacman -Syuf...................
Or, pacman -Sc
Then:
Pacman -Syu

mcmillan · 2008-02-23 18:30:57

Since all of those seem to belong to the same package (gcc-libs), I'd think it would be a bit safer to do pacman -Sf gcc-libs rather than -Syuf. That way if something goes wrong with another package you'd at least know about it.

shining · 2008-02-23 19:16:45

mcmillan wrote:

Since all of those seem to belong to the same package (gcc-libs), I'd think it would be a bit safer to do pacman -Sf gcc-libs rather than -Syuf. That way if something goes wrong with another package you'd at least know about it.

That's right. I think -Suf shouldn't even be allowed. But arch is about letting the power to the user, right?

cb474 · 2009-05-21 22:13:42

I got a similar error trying to upgrade libdvdread:

checking package integrity...
(1/1) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
libdvdread: /usr/share/aclocal/dvdread.m4 exists in filesystem
Errors occurred, no packages were upgraded.

I'm just curious, what does it mean the files are conflicting? Why does it matter if dvdread.m4 already exists? Aren't files always been replaced that already exist when you're upgrading packages?

tdy · 2009-05-21 22:29:28

jadacyrus wrote:

Not sure what to do! Thanks in advance for any help.

cb474 wrote:

I'm just curious, what does it mean the files are conflicting? Why does it matter if dvdread.m4 already exists? Aren't files always been replaced that already exist when you're upgrading packages?

Sticky: pacman error: FILENAME exists in filesystem

Xabre · 2009-05-21 22:33:32

Aren't files always been replaced that already exist when you're upgrading packages?

Actually, it doesn't tell you that conflicting file belongs to package you're trying to upgrade, just that it already exist in filesystem.
You might wanna try pacman -Qo /usr/share/aclocal/dvdread.m4 to see which package it belongs to. If none, it's much safer to force install.

cb474 · 2009-05-22 02:46:20

Thanks for the reply. I guess I still don't understand what the problem is if the file already exists in the filesystem. Why does that cause pacman to refuse to install the package (without using the force option)? If two different packages need the same file, what does it matter which package installed the file or which package the file belongs to?

Unfortunately I already did the force install, so I won't be able to use the pacman -Qo command and see what package dvdread.m4 previously belonged to. I was having problems with building handbrake from AUR and this specific file, though, so I suspect it has something to do with that.

Allan · 2009-05-22 02:48:12

cb474 wrote:

Thanks for the reply. I guess I still don't understand what the problem is if the file already exists in the filesystem. Why does that cause pacman to refuse to install the package (without using the force option)? If two different packages need the same file, what does it matter which package installed the file or which package the file belongs to?

You are assuming that they are the same file, and not a different file with the same name...

cb474 · 2009-05-22 03:00:07

Ah, that makes sense. So if the file belonged to a different package, how would I know if it's the same file or not?

rtwair · 2012-08-03 10:23:58

So I followed lilsirecho's advice and now I'm screwed!

Proceed with installation? [Y/n] Y
(140/140) checking package integrity                                                                                                     [####################################################################################] 100%
(140/140) loading package files                                                                                                          [####################################################################################] 100%
(141/141) checking available disk space                                                                                                  [####################################################################################] 100%
(1/1) removing dbus-python                                                                                                               [####################################################################################] 100%
(  1/140) upgrading linux-api-headers                                                                                                    [####################################################################################] 100%
(  2/140) upgrading tzdata                                                                                                               [####################################################################################] 100%
(  3/140) upgrading glibc                                                                                                                [####################################################################################] 100%
error: extract: not overwriting dir with file lib
error: problem occurred while upgrading glibc
call to execv failed (No such file or directory)
error: command failed to execute correctly
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.

now when trying to run simple commands such as pacman or even ls I get the following:.

[rtwair@InteleRiyad PACS]$ ls
bash: /bin/ls: No such file or directory
[rtwair@InteleRiyad PACS]$ pacman
bash: /usr/bin/pacman: No such file or directory
[rtwair@InteleRiyad PACS]$ cd /usr/local/bin/
[rtwair@InteleRiyad bin]$ find .
bash: /usr/bin/find: No such file or directory
[rtwair@InteleRiyad bin]$ du
bash: /usr/bin/du: No such file or directory
[rtwair@InteleRiyad bin]$ df
bash: /bin/df: No such file or directory

I really should have really known better than blindly follow someones command first researching the flags.

Does anyone have anyone have suggestions for me at this point?

rtwair · 2012-08-03 10:28:24

I neglected to put my inital pacman command:.

[rtwair@InteleRiyad pkg]$ sudo pacman -Syuf

Barrucadu · 2012-08-03 11:22:38

rtwair wrote:

I neglected to put my inital pacman command:.
[rtwair@InteleRiyad pkg]$ sudo pacman -Syuf

Well done, you did exactly the wrong thing. Search the forums, fixing this has been covered extensively.

Trilby · 2012-08-03 11:29:54

Also I have no idea why you thought a 4 year old thread could be remotely relevant to your current situation.

bernarcher · 2012-08-03 12:50:31

Trilby wrote:

Also I have no idea why you thought a 4 year old thread could be remotely relevant to your current situation.

So it is.
Closing.

Inxsible · 2012-08-03 14:17:05

even within this thread, a pacman developer, no less, says that -Suf shouldn't be used !!!

I don't get why people have this affinity to the -f flag !

Arch Linux

#1 2008-02-23 01:18:28

Pacman "error: failed to commit transaction (conflicting files)"

#2 2008-02-23 02:06:46

Re: Pacman "error: failed to commit transaction (conflicting files)"

#3 2008-02-23 18:30:57

Re: Pacman "error: failed to commit transaction (conflicting files)"

#4 2008-02-23 19:16:45

Re: Pacman "error: failed to commit transaction (conflicting files)"

#5 2009-05-21 22:13:42

Re: Pacman "error: failed to commit transaction (conflicting files)"

#6 2009-05-21 22:29:28

Re: Pacman "error: failed to commit transaction (conflicting files)"

#7 2009-05-21 22:33:32

Re: Pacman "error: failed to commit transaction (conflicting files)"

#8 2009-05-22 02:46:20

Re: Pacman "error: failed to commit transaction (conflicting files)"

#9 2009-05-22 02:48:12

Re: Pacman "error: failed to commit transaction (conflicting files)"

#10 2009-05-22 03:00:07

Re: Pacman "error: failed to commit transaction (conflicting files)"

#11 2012-08-03 10:23:58

Re: Pacman "error: failed to commit transaction (conflicting files)"

#12 2012-08-03 10:28:24

Re: Pacman "error: failed to commit transaction (conflicting files)"

#13 2012-08-03 11:22:38

Re: Pacman "error: failed to commit transaction (conflicting files)"

#14 2012-08-03 11:29:54

Re: Pacman "error: failed to commit transaction (conflicting files)"

#15 2012-08-03 12:50:31

Re: Pacman "error: failed to commit transaction (conflicting files)"

#16 2012-08-03 14:17:05

Re: Pacman "error: failed to commit transaction (conflicting files)"

Board footer