Bug 698656 – media-sound/whipper-0.8.0: dependency on dev-python/ruamel-yaml[python_targets_python2_7(-)? -python_single_target_python2_7(-)]

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Quentin Retornaz 2019-10-27 14:53:11 UTC]

I maintain media-sound/whipper on portage tree.
whipper released today a new version 0.8.0 and is now depending on dev-python/ruamel-yaml.
however whipper still only support python 2 (python 3 support will come on 0.9.0) and dev-python/ruamel-yaml on portage tree only support python 3.
I don’t know how to handle this situation.
I’ve attached my actual draft of v0.8.0 ebuild.

Reproducible: Always

[Comment 1 Quentin Retornaz 2019-10-27 14:53:38 UTC]

Created attachment 594150 [details]
whipper-0.8.0.ebuild

[Comment 2 Hadrien Lacour 2019-11-30 15:49:15 UTC]

I found myself in the same spot and had to:
- locally fork ruamel-yaml and ruamel-std-pathlib
- remove the file deletions from ruamel-yaml, otherwise the module isn't found by python2
- revert af748c to make whipper compile, otherwise it needs setuptools_scm and a network access just to get the whipper version
- add some sed to compiler accuraterip-checksum with CFLAGS/LDFLAGS since it's a python extension now

See
https://git.sr.ht/~q3cpma/portage-overlay/tree/master/media-sound/whipper/whipper-0.8.0.ebuild
and
https://git.sr.ht/~q3cpma/portage-overlay/tree/master/dev-python/ruamel-yaml/ruamel-yaml-0.15.97.ebuild

Thanks for your ebuild, by the way. It helped me catch some issues with mine.

[Comment 3 Quentin Retornaz 2019-12-04 13:56:35 UTC]

whipper project has released v0.9.0 with full Python 3 support just now.
Closing this bug report.