This is the last package requiring py2 gst-python, and therefore colliding with all other packages using gst-python (it's single-r1).
Apparently upstream master supports py3 these days. Might be in our release already.
4.1.0-alpha1 was released with initial py3 support; probably good idea to at least wait for a rc, if not final; I'd hope upstream does that soonish
that said, gst-python is NOT single-r1
Created attachment 652584 [details] exaile-4.1.0_alpha1.ebuild Minimal changes from exaile-4.0.0-r1.ebuild . Patch to follow. Needs a patch to the Makefile (to follow).
Created attachment 652586 [details] files/exaile-4.1.0_alpha1-metainfo.patch Patch to Makefile as referenced from exaile-4.1.0_alpha1.ebuild.
Created attachment 652588 [details, diff] Diff between exaile-4.0.0-r1.ebuild and exaile-4.1.0_alpha1.ebuild - Dropped PYTHON_REQ_USE="sqlite" - The Exaile music DB is of BerkeleyDB type. There is not a single .sqlite DB is in my ~/.local/share/exaile. That said, I haven't tested whether it'll work without sqlite support in python (who knows, perhaps it uses a :mem: in-memory sqlite database in some code path). Yet I think this might be in here since for a brief moment (years ago) exaile switched to a sqlite database backend, so this PYTHON_REQ_USE="sqlite" could be a vestigal remnant of that event. - remove cddb use flag; cddb-py is python2.7 only, someone who's very enthusiastic about CDs could make the effort of making all that work again. - add a patch to the Makefile; otherwise portage complains (warns) about XDG appdata -> metainfo nomenclature.
Created attachment 652590 [details] exaile-4.1.0_alpha1.ebuild
(In reply to Wicher Minnaard from comment #7) > Created attachment 652590 [details] > exaile-4.1.0_alpha1.ebuild ebuild works for me. Since the file https://github.com/exaile/exaile/blob/master/DEPS list python-3.6 as a minimum requirement, I'd prefer to include at least python-3.6 in PYTHON_COMPAT: PYTHON_COMPAT=( python3_{6,7} ) I don't expect any problems with python3_{8,9} either, but I haven't tested it.
Can the alpha ebuild be added to the portage tree, as the only version in there is marked for removal: !!! The following installed packages are masked: - media-sound/exaile-4.0.0-r1::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Aaron Bauman <bman@gentoo.org> (2020-08-01) # Py2 only. Last upstream release 2013. # Removal in 30 days. Last 2 have deps on cddb. Thanks!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=171803227f3ded10b76442406583c55e3b04c0ec commit 171803227f3ded10b76442406583c55e3b04c0ec Author: Miroslav Šulc <fordfrog@gentoo.org> AuthorDate: 2020-08-11 08:42:09 +0000 Commit: Miroslav Šulc <fordfrog@gentoo.org> CommitDate: 2020-08-11 08:45:24 +0000 media-sound/exile: bump to 4.1.0_alpha1 + added live + dropped py2 based on updated ebuild provided by Wicher Minnaard <wicher@gavagai.eu> Closes: https://bugs.gentoo.org/708966 Package-Manager: Portage-3.0.2, Repoman-2.3.23 Signed-off-by: Miroslav Šulc <fordfrog@gentoo.org> media-sound/exaile/Manifest | 2 +- ...-4.0.0-r1.ebuild => exaile-4.1.0_alpha1.ebuild} | 44 ++++++------- media-sound/exaile/exaile-9999.ebuild | 72 ++++++++++++++++++++++ .../files/exaile-4.1.0_alpha1-metainfo.patch | 29 +++++++++ 4 files changed, 120 insertions(+), 27 deletions(-)