You are not logged in.
Hello. I got this during update:
error: failed to commit transaction (conflicting files)
python-future: /usr/bin/futurize exists in filesystem
python-future: /usr/bin/pasteurize exists in filesystem
Errors occurred, no packages were upgraded.So I thought I probably don't need that and tried removing, but:
$ sudo pacman -R python-future
error: target not found: python-futureHow should I deal with that?
How is that even possible in pacman to have these records while package is missing?
Last edited by mkheaven (2020-07-24 08:38:06)
Offline
Pacman doesn't have the records, that's the point. It's *files* in the filesystem that are causing a problem.
Offline
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Well, I figured I can just delete (or more safely, rename) those files, which I did and updated successfully, yay!
However what I still don't get is how could these facts be happening at the same time:
1. pacman said these files belong to 'python-future'
So I expect pacman to be able to list these same files as belonging to 'python-future', but...
2.
$ pacman -Ql python-future
error: package 'python-future' was not found
$ sudo pacman -Rsu python-future
error: target not found: python-future
$ pacman -Qo /usr/bin/futurize
error: No package owns /usr/bin/futurize
$ pacman -Qo /usr/bin/pasteurize
error: No package owns /usr/bin/pasteurizeWhat does it all mean? I figured it was an optional dependency I think I never explicitly installed. Could it have been done by pip when it was resolving dependencies?
(I know it is wrong to use pip system-wide, but I had no choise because some package, I believe it was python-gtk, wouldn't install into venv and I didn't have time to resolve that...)
Offline
1. When trying to install "python-future", pacman detects a conflict between the (not yet installed) package and your filesystem
2. You did at no point install the "python-future" package. The existing files likely stem from some pip installation.
See the last sentence right above the purple "note" box: https://wiki.archlinux.org/index.php/Py … management
Offline
Oh. That was dumb. I thought it tells me to deal with that package's files.
Appreciate your time, guys!
> integrating pip with pacman by automatically generating PKGBUILDs
That's interesting, will give it a try! Thanks, seth!
Offline