You are not logged in.
Pages: 1
Topic closed
# pacman -S python-sqlalchemy
resolving dependencies...
looking for inter-conflicts...
Targets: setuptools-0.6c7-1 python-sqlalchemy-0.4.2p3-1
Total Download Size: 0,00 MB
Total Installed Size: 3,17 MB
Proceed with installation? [Y/n] y
checking package integrity...
(2/2) checking for file conflicts [###############################################################################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
setuptools: /usr/bin/easy_install exists in filesystem
setuptools: /usr/bin/easy_install-2.5 exists in filesystem
setuptools: /usr/lib/python2.5/site-packages/setuptools.pth exists in filesystem
Errors occurred, no packages were upgraded.
I have no clue
Linux user #403491
"Men have called me mad; but the question is not yet settled, whether madness is or is not the loftiest intelligence– whether much that is glorious– whether all that is profound– does not spring from disease of thought– from moods of mind exalted at the expense of the general intellect." - E. A. Poe from Eleonora
Offline
try running pacman -Qo on the conflicting files to see if they belong to another package.
Offline
Ok, none of them are owned by any package. So then I can just delete them ?
Linux user #403491
"Men have called me mad; but the question is not yet settled, whether madness is or is not the loftiest intelligence– whether much that is glorious– whether all that is profound– does not spring from disease of thought– from moods of mind exalted at the expense of the general intellect." - E. A. Poe from Eleonora
Offline
I was getting those same messages, so for the heck of it (famous last words...) I moved all the conflicting files to backup versions including the date in the names, then pacman -Syu worked OK. Hope I didn't bust something that will haunt me down the road though... If terrible things ensue I'll post a message.
VincentV
Somewhere in J-Pop Heaven...
Offline
Either deelete them or rename them like VincentV did. I just realized I have them on my system and they belong to setuptools.
Offline
or you can just force install.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Oh, thought I'd chime back in, everything seems fine here after renaming the files then proceeding with pacman. So I'm guessing force installing as cactus said will be fine, now I guess I should delete the old files to make space.
VincentV
Somewhere in J-Pop Heaven...
Offline
So its a bug with setuptools then ?
Anyway I just deleted them and then installed fine
Linux user #403491
"Men have called me mad; but the question is not yet settled, whether madness is or is not the loftiest intelligence– whether much that is glorious– whether all that is profound– does not spring from disease of thought– from moods of mind exalted at the expense of the general intellect." - E. A. Poe from Eleonora
Offline
So its a bug with setuptools then ?
No. Either you previously installed setuptools manually (without using pacman) or some app created these files. There's nothing much we can do about that in regard to setuptools.
Offline
Had the same problem. Since I have pip, I decided to just remove setuptools using the following command:
sudo pip uninstall pip setuptools
Offline
Had the same problem. Since I have pip, I decided to just remove setuptools using the following command:
sudo pip uninstall pip setuptools
Do you really think the OP is still looking for information eight and a half years later?
Please, read the forum rules, especially https://wiki.archlinux.org/index.php/Co … bumping.22
Offline
Closing
Offline
Pages: 1
Topic closed