python3.14-vicinity-0.4.4
checks.aarch64-linux.pkgs-semble
· build #8280
· raw
1elastic-arm-5be5d98b: building aqv9147wppxhynmvw38ndmhbpplds8gn-python3.14-vicinity-0.4.4.drv2structuredAttrs is enabled3Sourcing python-remove-tests-dir-hook4Sourcing python-catch-conflicts-hook.sh5Sourcing python-remove-bin-bytecode-hook.sh6Sourcing pypa-build-hook7Using pypaBuildPhase8Sourcing python-runtime-deps-check-hook9Using pythonRuntimeDepsCheckHook10Sourcing pypa-install-hook11Using pypaInstallPhase12Sourcing python-imports-check-hook.sh13Using pythonImportsCheckPhase14Sourcing python-metadata-check-hook.sh15Using pythonMetadataCheckPhase16Sourcing python-namespaces-hook17Sourcing python-catch-conflicts-hook.sh18Using checkPhaseThreadLimitHook
unpackPhase
19unpacking source archive /nix/store/vcrp5i7fav7h0x98gqspihdrkwqb6710-vicinity-0.4.4.tar.gz20source root is vicinity-0.4.421setting SOURCE_DATE_EPOCH to timestamp 1776179318 of file "vicinity-0.4.4/setup.cfg"configurePhase
22no configure script, doing nothingbuildPhase
23Executing pypaBuildPhase24Including all tracked files automatically25Creating a wheel...26pypa build flags: --no-isolation --outdir dist/ --wheel27* Getting build dependencies for wheel...28/nix/store/naz6vc3grqf2hz945f4mqfn13zfbfkpa-python3.14-setuptools-scm-10.2.1/lib/python3.14/site-packages/setuptools_scm/_integration/deprecation.py:9: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]29version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set30When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.31Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.32 warnings.warn(33/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated34!!3536 ********************************************************************************37 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).3839 By 2027-Feb-18, you need to update your project and remove deprecated calls40 or your builds will no longer be supported.4142 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.43 ********************************************************************************4445!!46 corresp(dist, value, root_dir)47/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:55: SetuptoolsDeprecationWarning: 'tool.setuptools.license-files' is deprecated in favor of 'project.license-files' (available on setuptools>=77.0.0).48!!4950 ********************************************************************************5152 By 2027-Feb-18, you need to update your project and remove deprecated calls53 or your builds will no longer be supported.5455 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.56 ********************************************************************************5758!!59 _apply_tool_table(dist, config, filename)60/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.61!!6263 ********************************************************************************64 Please consider removing the following classifiers in favor of a SPDX license expression:6566 License :: OSI Approved :: MIT License6768 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.69 ********************************************************************************7071!!72 dist._finalize_license_expression()73/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.74!!7576 ********************************************************************************77 Please consider removing the following classifiers in favor of a SPDX license expression:7879 License :: OSI Approved :: MIT License8081 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.82 ********************************************************************************8384!!85 self._finalize_license_expression()86running egg_info87writing vicinity.egg-info/PKG-INFO88writing dependency_links to vicinity.egg-info/dependency_links.txt89writing requirements to vicinity.egg-info/requires.txt90writing top-level names to vicinity.egg-info/top_level.txt91reading manifest file 'vicinity.egg-info/SOURCES.txt'92reading manifest template 'MANIFEST.in'93writing manifest file 'vicinity.egg-info/SOURCES.txt'94* Building wheel...95/nix/store/naz6vc3grqf2hz945f4mqfn13zfbfkpa-python3.14-setuptools-scm-10.2.1/lib/python3.14/site-packages/setuptools_scm/_integration/deprecation.py:9: UserWarning: pyproject.toml: at [tool.setuptools.dynamic]96version = {attr = ...} is forcing setuptools to override the version setuptools-scm did already set97When using setuptools-scm it's invalid to use setuptools dynamic version as well, please remove it.98Setuptools-scm is responsible for setting the version, forcing setuptools to override creates errors.99 warnings.warn(100/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated101!!102103 ********************************************************************************104 Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).105106 By 2027-Feb-18, you need to update your project and remove deprecated calls107 or your builds will no longer be supported.108109 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.110 ********************************************************************************111112!!113 corresp(dist, value, root_dir)114/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:55: SetuptoolsDeprecationWarning: 'tool.setuptools.license-files' is deprecated in favor of 'project.license-files' (available on setuptools>=77.0.0).115!!116117 ********************************************************************************118119 By 2027-Feb-18, you need to update your project and remove deprecated calls120 or your builds will no longer be supported.121122 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license-files for details.123 ********************************************************************************124125!!126 _apply_tool_table(dist, config, filename)127/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.128!!129130 ********************************************************************************131 Please consider removing the following classifiers in favor of a SPDX license expression:132133 License :: OSI Approved :: MIT License134135 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.136 ********************************************************************************137138!!139 dist._finalize_license_expression()140/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.141!!142143 ********************************************************************************144 Please consider removing the following classifiers in favor of a SPDX license expression:145146 License :: OSI Approved :: MIT License147148 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.149 ********************************************************************************150151!!152 self._finalize_license_expression()153running bdist_wheel154running build155running build_py156creating build/lib/vicinity157copying vicinity/version.py -> build/lib/vicinity158copying vicinity/__init__.py -> build/lib/vicinity159copying vicinity/utils.py -> build/lib/vicinity160copying vicinity/datatypes.py -> build/lib/vicinity161copying vicinity/vicinity.py -> build/lib/vicinity162running egg_info163writing vicinity.egg-info/PKG-INFO164writing dependency_links to vicinity.egg-info/dependency_links.txt165writing requirements to vicinity.egg-info/requires.txt166writing top-level names to vicinity.egg-info/top_level.txt167reading manifest file 'vicinity.egg-info/SOURCES.txt'168reading manifest template 'MANIFEST.in'169writing manifest file 'vicinity.egg-info/SOURCES.txt'170/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'vicinity.__pycache__' is absent from the `packages` configuration.171!!172173 ********************************************************************************174 ############################175 # Package would be ignored #176 ############################177 Python recognizes 'vicinity.__pycache__' as an importable package[^1],178 but it is absent from setuptools' `packages` configuration.179180 This leads to an ambiguous overall configuration. If you want to distribute this181 package, please make sure that 'vicinity.__pycache__' is explicitly added182 to the `packages` configuration field.183184 Alternatively, you can also rely on setuptools' discovery methods185 (for example by using `find_namespace_packages(...)`/`find_namespace:`186 instead of `find_packages(...)`/`find:`).187188 You can read more about "package discovery" on setuptools documentation page:189190 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html191192 If you don't want 'vicinity.__pycache__' to be distributed and are193 already explicitly excluding 'vicinity.__pycache__' via194 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,195 you can try to use `exclude_package_data`, or `include-package-data=False` in196 combination with a more fine grained `package-data` configuration.197198 You can read more about "package data files" on setuptools documentation page:199200 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html201202203 [^1]: For Python, any directory (with suitable naming) can be imported,204 even if it does not contain any `.py` files.205 On the other hand, currently there is no concept of package data206 directory, all directories are treated like packages.207 ********************************************************************************208209!!210 check.warn(importable)211/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'vicinity.backends' is absent from the `packages` configuration.212!!213214 ********************************************************************************215 ############################216 # Package would be ignored #217 ############################218 Python recognizes 'vicinity.backends' as an importable package[^1],219 but it is absent from setuptools' `packages` configuration.220221 This leads to an ambiguous overall configuration. If you want to distribute this222 package, please make sure that 'vicinity.backends' is explicitly added223 to the `packages` configuration field.224225 Alternatively, you can also rely on setuptools' discovery methods226 (for example by using `find_namespace_packages(...)`/`find_namespace:`227 instead of `find_packages(...)`/`find:`).228229 You can read more about "package discovery" on setuptools documentation page:230231 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html232233 If you don't want 'vicinity.backends' to be distributed and are234 already explicitly excluding 'vicinity.backends' via235 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,236 you can try to use `exclude_package_data`, or `include-package-data=False` in237 combination with a more fine grained `package-data` configuration.238239 You can read more about "package data files" on setuptools documentation page:240241 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html242243244 [^1]: For Python, any directory (with suitable naming) can be imported,245 even if it does not contain any `.py` files.246 On the other hand, currently there is no concept of package data247 directory, all directories are treated like packages.248 ********************************************************************************249250!!251 check.warn(importable)252/nix/store/7wqmhkx1lp5j15m2p4mv6vfrw08nzd90-python3.14-setuptools-83.0.0/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'vicinity.integrations' is absent from the `packages` configuration.253!!254255 ********************************************************************************256 ############################257 # Package would be ignored #258 ############################259 Python recognizes 'vicinity.integrations' as an importable package[^1],260 but it is absent from setuptools' `packages` configuration.261262 This leads to an ambiguous overall configuration. If you want to distribute this263 package, please make sure that 'vicinity.integrations' is explicitly added264 to the `packages` configuration field.265266 Alternatively, you can also rely on setuptools' discovery methods267 (for example by using `find_namespace_packages(...)`/`find_namespace:`268 instead of `find_packages(...)`/`find:`).269270 You can read more about "package discovery" on setuptools documentation page:271272 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html273274 If you don't want 'vicinity.integrations' to be distributed and are275 already explicitly excluding 'vicinity.integrations' via276 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,277 you can try to use `exclude_package_data`, or `include-package-data=False` in278 combination with a more fine grained `package-data` configuration.279280 You can read more about "package data files" on setuptools documentation page:281282 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html283284285 [^1]: For Python, any directory (with suitable naming) can be imported,286 even if it does not contain any `.py` files.287 On the other hand, currently there is no concept of package data288 directory, all directories are treated like packages.289 ********************************************************************************290291!!292 check.warn(importable)293copying vicinity/py.typed -> build/lib/vicinity294creating build/lib/vicinity/__pycache__295copying vicinity/__pycache__/version.cpython-314.pyc -> build/lib/vicinity/__pycache__296creating build/lib/vicinity/backends297copying vicinity/backends/__init__.py -> build/lib/vicinity/backends298copying vicinity/backends/annoy.py -> build/lib/vicinity/backends299copying vicinity/backends/base.py -> build/lib/vicinity/backends300copying vicinity/backends/basic.py -> build/lib/vicinity/backends301copying vicinity/backends/faiss.py -> build/lib/vicinity/backends302copying vicinity/backends/hnsw.py -> build/lib/vicinity/backends303copying vicinity/backends/pynndescent.py -> build/lib/vicinity/backends304copying vicinity/backends/usearch.py -> build/lib/vicinity/backends305copying vicinity/backends/voyager.py -> build/lib/vicinity/backends306creating build/lib/vicinity/integrations307copying vicinity/integrations/dataset_card_template.md -> build/lib/vicinity/integrations308copying vicinity/integrations/huggingface.py -> build/lib/vicinity/integrations309installing to build/bdist.linux-aarch64/wheel310running install311running install_lib312creating build/bdist.linux-aarch64/wheel313creating build/bdist.linux-aarch64/wheel/vicinity314creating build/bdist.linux-aarch64/wheel/vicinity/backends315copying build/lib/vicinity/backends/base.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends316copying build/lib/vicinity/backends/__init__.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends317copying build/lib/vicinity/backends/hnsw.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends318copying build/lib/vicinity/backends/usearch.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends319copying build/lib/vicinity/backends/faiss.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends320copying build/lib/vicinity/backends/basic.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends321copying build/lib/vicinity/backends/annoy.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends322copying build/lib/vicinity/backends/pynndescent.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends323copying build/lib/vicinity/backends/voyager.py -> build/bdist.linux-aarch64/wheel/./vicinity/backends324creating build/bdist.linux-aarch64/wheel/vicinity/integrations325copying build/lib/vicinity/integrations/huggingface.py -> build/bdist.linux-aarch64/wheel/./vicinity/integrations326copying build/lib/vicinity/integrations/dataset_card_template.md -> build/bdist.linux-aarch64/wheel/./vicinity/integrations327copying build/lib/vicinity/version.py -> build/bdist.linux-aarch64/wheel/./vicinity328copying build/lib/vicinity/__init__.py -> build/bdist.linux-aarch64/wheel/./vicinity329copying build/lib/vicinity/utils.py -> build/bdist.linux-aarch64/wheel/./vicinity330creating build/bdist.linux-aarch64/wheel/vicinity/__pycache__331copying build/lib/vicinity/__pycache__/version.cpython-314.pyc -> build/bdist.linux-aarch64/wheel/./vicinity/__pycache__332copying build/lib/vicinity/datatypes.py -> build/bdist.linux-aarch64/wheel/./vicinity333copying build/lib/vicinity/vicinity.py -> build/bdist.linux-aarch64/wheel/./vicinity334copying build/lib/vicinity/py.typed -> build/bdist.linux-aarch64/wheel/./vicinity335running install_egg_info336Copying vicinity.egg-info to build/bdist.linux-aarch64/wheel/./vicinity-0.4.4-py3.14.egg-info337running install_scripts338creating build/bdist.linux-aarch64/wheel/vicinity-0.4.4.dist-info/WHEEL339creating '/build/vicinity-0.4.4/dist/.tmp-o9djmx83/vicinity-0.4.4-py3-none-any.whl' and adding 'build/bdist.linux-aarch64/wheel' to it340adding 'vicinity/__init__.py'341adding 'vicinity/datatypes.py'342adding 'vicinity/py.typed'343adding 'vicinity/utils.py'344adding 'vicinity/version.py'345adding 'vicinity/vicinity.py'346adding 'vicinity/__pycache__/version.cpython-314.pyc'347adding 'vicinity/backends/__init__.py'348adding 'vicinity/backends/annoy.py'349adding 'vicinity/backends/base.py'350adding 'vicinity/backends/basic.py'351adding 'vicinity/backends/faiss.py'352adding 'vicinity/backends/hnsw.py'353adding 'vicinity/backends/pynndescent.py'354adding 'vicinity/backends/usearch.py'355adding 'vicinity/backends/voyager.py'356adding 'vicinity/integrations/dataset_card_template.md'357adding 'vicinity/integrations/huggingface.py'358adding 'vicinity-0.4.4.dist-info/METADATA'359adding 'vicinity-0.4.4.dist-info/WHEEL'360adding 'vicinity-0.4.4.dist-info/top_level.txt'361adding 'vicinity-0.4.4.dist-info/RECORD'362removing build/bdist.linux-aarch64/wheel363Successfully built vicinity-0.4.4-py3-none-any.whl364Finished creating a wheel...365Finished executing pypaBuildPhasepythonRuntimeDepsCheckHook
366Executing pythonRuntimeDepsCheck367Checking runtime dependencies for vicinity-0.4.4-py3-none-any.whl368Finished executing pythonRuntimeDepsCheckinstallPhase
369Executing pypaInstallPhase370/nix/store/chkqxlfkbaq5yazm86av5z18paxbi3m3-python3.14-installer-1.0.1/lib/python3.14/site-packages/installer/__main__.py:118: RuntimeWarning: Skip installing vicinity/__pycache__/version.cpython-314.pyc from vicinity. Installing files in a __pycache__ directory poses a security risk. __pycache__ directories should not be included in wheels. This is probably an issue in the build process of 'vicinity'.371 installer.install(source, destination, {})372Successfully installed vicinity-0.4.4-py3-none-any.whl373Finished executing pypaInstallPhasepythonOutputDistPhase
374Executing pythonOutputDistPhase375Finished executing pythonOutputDistPhasefixupPhase
376shrinking RPATHs of ELF executables and libraries in /nix/store/if971js2kivkxqr7jmqp83wbx8ck1fsj-python3.14-vicinity-0.4.4-dist377checking for references to /build/ in /nix/store/if971js2kivkxqr7jmqp83wbx8ck1fsj-python3.14-vicinity-0.4.4-dist...378patching script interpreter paths in /nix/store/if971js2kivkxqr7jmqp83wbx8ck1fsj-python3.14-vicinity-0.4.4-dist379shrinking RPATHs of ELF executables and libraries in /nix/store/x7h4xdfjzdg0mp4qd68ddqinvhz4jk48-python3.14-vicinity-0.4.4380checking for references to /build/ in /nix/store/x7h4xdfjzdg0mp4qd68ddqinvhz4jk48-python3.14-vicinity-0.4.4...381patching script interpreter paths in /nix/store/x7h4xdfjzdg0mp4qd68ddqinvhz4jk48-python3.14-vicinity-0.4.4382stripping (with command strip and flags -S -p) in /nix/store/x7h4xdfjzdg0mp4qd68ddqinvhz4jk48-python3.14-vicinity-0.4.4/lib383Executing pythonRemoveTestsDir384Finished executing pythonRemoveTestsDirpythonImportsCheckPhase
385Executing pythonImportsCheckPhase386Check whether the following modules can be imported: vicinitypythonMetadataCheckPhase
387Executing pythonMetadataCheckPhase