@xiota, you can now add back the conflicts=(python-ffmpeg)
entry.
And please remove the replaces
field. It should not be used on AUR at any time, as per Arch guidelines.
I've never actually seen yay or paru or pacman take the replaces field into account when an AUR package is built locally and installed from local source.
This field might only have effect when a pacman package is hosted in an Arch-type binary repo and when pacman grabs the package from there.
But this is again a reason for you not to have this replaces field: if it were taken into account, it would intrude upon users who have the new python-python-ffmpeg installed - then pacman would want to replace even that with this package.
Pinned Comments
xiota commented on 2023-06-17 22:09 (UTC) (edited on 2023-06-17 23:13 (UTC) by xiota)
There are currently two conflicting ffmpeg modules for python. This package provides the old implementation.
pypi/ffmpeg-python - Old implementation. Development has apparently been abandoned.
aur/python-ffmpeg-python
aur/python-ffmpeg-python-git
pypi/python-ffmpeg - New implementation. May not be compatible with the old module. May have fewer features.
aur/python-python-ffmpeg
aur/python-python-ffmpeg-git