@carlosal1015 Test error is known. Upstream development appears to be discontinued, so unlikely to be fixed. Does not appear to affect general function.
Update: Patches added to fix currently known test errors.
Git Clone URL: | https://aur.archlinux.org/python-ffmpeg-python.git (read-only, click to copy) |
---|---|
Package Base: | python-ffmpeg-python |
Description: | (old) Python bindings for FFmpeg with complex filtering support |
Upstream URL: | https://github.com/kkroening/ffmpeg-python |
Licenses: | Apache-2.0 |
Conflicts: | python-python-ffmpeg |
Submitter: | xiota |
Maintainer: | xiota |
Last Packager: | xiota |
Votes: | 14 |
Popularity: | 0.39 |
First Submitted: | 2023-06-17 21:59 (UTC) |
Last Updated: | 2024-12-24 18:23 (UTC) |
@carlosal1015 Test error is known. Upstream development appears to be discontinued, so unlikely to be fixed. Does not appear to affect general function.
Update: Patches added to fix currently known test errors.
Hi, I have the following error message
==> Making package: python-ffmpeg-python 0.2.0-6 (Mon Aug 5 19:09:49 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting check()...
=================================================================================== test session starts ====================================================================================
platform linux -- Python 3.12.4, pytest-8.3.2, pluggy-1.5.0
rootdir: /tmp/makepkg/python-ffmpeg-python/src/ffmpeg-python-0.2.0
configfile: pytest.ini
testpaths: ffmpeg/tests
plugins: anyio-4.4.0, cov-5.0.0, mock-3.14.0
collected 60 items
ffmpeg/tests/test_ffmpeg.py .....................................................FF..... [100%]
========================================================================================= FAILURES =========================================================================================
ffmpeg/tests/test_ffmpeg.py:699: AssertionError
_______________________________________________________________________________________ test__probe ________________________________________________________________________________________
def test__probe():
data = ffmpeg.probe(TEST_INPUT_FILE1)
assert set(data.keys()) == {'format', 'streams'}
> assert data['format']['duration'] == '7.036000'
E AssertionError: assert '7.035646' == '7.036000'
E
E - 7.036000
E + 7.035646
ffmpeg/tests/test_ffmpeg.py:706: AssertionError
================================================================================= short test summary info ==================================================================================
FAILED ffmpeg/tests/test_ffmpeg.py::test_pipe - AssertionError: assert 30720 == (3072 * (10 - 2))
FAILED ffmpeg/tests/test_ffmpeg.py::test__probe - AssertionError: assert '7.035646' == '7.036000'
========================================================================= 2 failed, 58 passed, 4 warnings in 2.53s =========================================================================
==> Entering fakeroot environment...
@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.
@MarsSeed I decided to retain the github url because this package does use the source tarball from github. The PyPI tarball is missing components.
@xiota, I suggest you change the Upstream URL to the official PyPI page of this package:
https://pypi.org/project/ffmpeg-python/
Git repo URLs / repo names can be misleading. They are not always the same as the PyPI name. And also the repo names and URLs can change.
PyPI names are therefore much more authoritative. And they correspond with what gets installed via pip install
and other official Python package manager tools.
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
pypi/python-ffmpeg - New implementation. Not fully compatible with the old module. May have fewer features.
aur/python-python-ffmpeg
aur/python-python-ffmpeg-git
Pinned Comments
xiota commented on 2023-06-17 22:09 (UTC) (edited on 2024-12-24 19:01 (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
pypi/python-ffmpeg - New implementation. Not fully compatible with the old module. May have fewer features.
aur/python-python-ffmpeg
aur/python-python-ffmpeg-git