You are not logged in.

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

jadacyrus
Member
Registered: 2007-02-14
Posts: 10

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

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.

Offline

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

lilsirecho
Veteran
Registered: 2003-10-24
Posts: 5,000

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

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


Sign of the times: Navajo blanket..made in China
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

Offline

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

mcmillan
Member
Registered: 2006-04-06
Posts: 684

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

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.

Offline

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

shining
Pacman Developer
Registered: 2006-05-10
Posts: 2,043

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

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? tongue


pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))

Offline

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

cb474
Member
Registered: 2009-04-04
Posts: 465

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

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?

Offline

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

tdy
Member
From: Sacremende
Registered: 2008-12-14
Posts: 438

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

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


dots (or just the awesomewm config)

$ whatis this?
this?: nothing appropriate.

Offline

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

Xabre
Member
From: Serbia
Registered: 2009-03-19
Posts: 567

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

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.

Offline

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

cb474
Member
Registered: 2009-04-04
Posts: 465

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

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.

Offline

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

Allan
Developer
From: Brisbane, AU
Registered: 2007-06-09
Posts: 10,328
Website

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

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...

Offline

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

cb474
Member
Registered: 2009-04-04
Posts: 465

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

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?

Offline

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

rtwair
Member
Registered: 2012-08-03
Posts: 2

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

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?

Offline

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

rtwair
Member
Registered: 2012-08-03
Posts: 2

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

I neglected to put my inital pacman command:.

[rtwair@InteleRiyad pkg]$ sudo pacman -Syuf

Offline

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

Barrucadu
Member
From: York, England
Registered: 2008-03-30
Posts: 1,158
Website

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

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.

Offline

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

Trilby
Forum Moderator
From: Massachusetts, USA
Registered: 2011-11-29
Posts: 13,374
Website

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

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


InterrobangSlider
• How's my coding? See this page.
• How's my moderating? Feel free to email any concerns, complaints, or objections.

Offline

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

bernarcher
Forum Fellow
From: Germany
Registered: 2009-02-17
Posts: 2,271

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

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.


To know or not to know ...
... the questions remain forever.

Offline

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

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,059

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

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 !


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

Board footer

Powered by FluxBB