Arch Linux User Repository

It has errors in the test now

==================================================================================================================================================== test session starts =====================================================================================================================================================
platform linux -- Python 3.10.10, pytest-3.8.0, py-1.11.1.dev0+g447bac51.d20230131, pluggy-1.0.0
rootdir: /home/gregory112/.cache/yay/python-dlib-cuda/src/dlib-19.22, inifile:
plugins: cov-4.0.0
collected 0 items / 11 errors                                                                                                                                                                                                                                                                                                

=========================================================================================================================================================== ERRORS ===========================================================================================================================================================
______________________________________________________________________________________________________________________________________ ERROR collecting tools/python/test/test_array.py ______________________________________________________________________________________________________________________________________
<frozen importlib._bootstrap>:939: in _find_spec
    ???
E   AttributeError: 'AssertionRewritingHook' object has no attribute 'find_spec'

I think this is related to pytest: https://github.com/pytest-dev/pytest/issues/1888

makedepends should include python{,2}-setuptools instead of just python{,2}.

Also, there is no need to list all three cuda, cudnn and libx11 as separate dependencies, as the other two are already dependencies of cudnn.

@AbysmalBiscuit

1. Thanks for the tests on optional dependencies.

2. ccache-ext is available in AUR now.

3. You can set license=('Boost') to use /usr/share/licenses/common/Boost/license.txt in licenses.

4. I see your changes about using the NEON instructions. But I think you misunderstand that this NEON is a kind of ARM instruction technology, not the neon package in [extra] which is a HTTP and WebDAV client library with a C interface.
   I think neon can be only enabled ARM architectures like armv7h or aarch64 and it's useless to python{,2}-dlib-cuda.

5. I have updating the PKGBUILD of python-dlib to build python{,2}-dlib-cuda as well (currently disabled). So would you like to be a co-maintainer of python-dlib and merge these 2 packages to it?
   And I've disabled the detection of AVX, SSE2, SSE4 instructions and enabled all the optdepends because I'm providing binaries of python{,2}-dlib in my repositories with this PKGBUILD. If you don't agree with these, we can keep our packages separate.

@Kicer Thanks! That's a good suggestion; I have added it.

I think provides section should contain entry python-dlib=${pkgver} (version included). Otherwise pakages like python-face_recognition won't install due to insufficient version.

@Kicer You are correct about gcc6 not being needed. In the past dlib and cuda programs did need gcc6 to compile properly, but it seems that is no longer the case.

@flipflop97 I have added the provides and conflicts.

@petronny I have gone through all the optional dependencies. Only sqlite and neon can be removed and python-dlib will still work. If any of the others are removed it will fail to import due to missing libraries of the shared object: dlib.cpython-36m-x86_64-linux-gnu.so. Note: removing sqlite will likely break parts of your system. :p

Hi

Why is there gcc6 needed? I've modified PKBUILD to use system gcc and it works fine.

Hi,

I have a package that depends on either python-dlib or python-dlib-cuda. I'd like to let it depend on either of them.

Right now both packages are totally separate. Can you maybe add a provides/conflicts/replaces rule for python-dlib so that both packages are treated as the same?

@AbysmalBiscuit Thanks for your answers and I'm clear to my first question.

My second question, or the other questions are:

1. If I build and install python-dlib with sqlite, then remove sqlite with pacman -Rdd sqlite, will python-dlib run?
2. If I build and install python-dlib with lapack, then remove lapack with pacman -Rdd lapack, will python-dlib run?
3. If I build and install python-dlib with libpng, then remove libpng with pacman -Rdd libpng, will python-dlib run?

etc.

@petronny Sorry for the delay in answering your questions.

1. If you remove cuda or cudnn (since both are needed to compile and run dlib with cuda support) with pacman -Rdd cuda cudnn, python-dlib-cuda will not fallback to using only the cpu. In fact importing dlib will simply fail with an ImportError with not being able to open the shared object file(s) (either cuda or cudnn).

2. I do not fully understand your question, I will assume that you are asking if it is possible to replace cuda with another dependency and still have be capable of using dlib in python. You cannot replace cuda with something else, or only with cudnn. You need both cuda and cudnn, hence why they are not only make dependencies, but also dependencies.

The dependency issue and the need to recompile if you would want to switch from having cuda support to using cpu only are likely the reason why python dlib was originally split into a cuda and non-cuda version.

If you have any other questions please don't hesitate to ask.