dev-python/librosa: new package
For now I'm waiting for https://github.com/librosa/librosa/commit/7eb0a09e703a72a5979049ec546a522c70285aff to hit release.
Where to put nanobind? BDEPEND or RDEPEND? As I understand it needs to be executed during compilation. And what did I do wrong?
I see. nanobind ebuild does not declare pypy3 support.
- [x] gentoo/gentoo#40480 for pypy3 in nanobind
- [x] librosa/librosa#1908 for failed test
- [x] librosa/librosa#1906 for new release
Test data repository is not tagged. It means I will need to somehow download it from git in release ebuild. Not sure how. Related issue:
- [ ] https://github.com/librosa/librosa/issues/1845 git test data + network test data
If worst case I plan to disable tests on release ebuild.
Test data repository is not tagged. It means I will need to somehow download it from git in release ebuild.
Usually it is possible to do some patching and add a snapshot from the git to the SRC_URI.
Should typing-extensions in soxr go to BDEPEND or IDEPEND or stay in DEPEND? Moving to BDEPEND for now.
I added things for docs generation. Works in soxr. Still broken in librosa, so I did not inherit docs there.
Should typing-extensions in soxr go to BDEPEND or IDEPEND or stay in DEPEND? Moving to BDEPEND for now.
RDEPEND if it is in the dependency list, BDEPEND if it is imported during the build.
Might I suggest to omit the pypy3 target here so this is no longer blocked by the failures in nanobind?
After https://github.com/tuxu/python-samplerate/issues/24 gets resolved I should be able to enable all non-network tests for librosa. I already made ebuild for resampy.
I'm back and hope to finish it