* ERROR: dev-python/python-musicbrainz-ngs-0.6::gentoo failed (install phase): * EXAMPLES are banned in EAPI 7 * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-20190719-201908 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.1.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Rust versions: [1] rust-1.36.0 * emerge -qpvO dev-python/python-musicbrainz-ngs [ebuild N ] dev-python/python-musicbrainz-ngs-0.6 USE="examples -doc -test" PYTHON_TARGETS="python2_7 python3_6 -python3_5 -python3_7"
Created attachment 584046 [details] emerge-info.txt
Created attachment 584048 [details] dev-python:python-musicbrainz-ngs-0.6:20190722-120621.log
Created attachment 584050 [details] emerge-history.txt
Created attachment 584052 [details] environment
Created attachment 584054 [details] etc.portage.tbz2
Created attachment 584056 [details] temp.tbz2
What is the replacement? I did not find anything in the comments of distutils-r1 and the ultimate guides to EAPI 6 or 7 and https://devmanual.gentoo.org/ebuild-writing/eapi/ except that EXAMPLES are deprecated. Additional question: Is there a simple way for me to test all possible flag combinations? Since there are only 7 flags and the package doesn't need to be compiled, I can test it all.
Package removed.
> Package removed. No. The package is still there and I appreciate it as proxy maintainer: https://packages.gentoo.org/packages/dev-python/python-musicbrainz-ngs python-musicbrainz was removed correctly, but python-musicbrainz was really obsolete. python-musicbrainz-ngs is still active (and had a release recently). However, I cannot fix this bug, since I do not understand it. Where can I find the documentation for it or should I just remove the examples?
Just use dodoc. use examples && dodoc -r examples/ (docompress -x if you want them in plain format)
Thank you. This bug seems closed in the meantime by David Seifert via e5e71cace6a6e6bdbd2761afe5f52ae1442278bc