On March 7th, 2015, Frescobaldi 2.18 has been released. Reproducible: Always Note : Frescobaldi is now dependent on the package 'python-ly' (https://github.com/wbsoft/python-ly)
This does according to https://github.com/wbsoft/frescobaldi/issues/439 also fix bug #519918.
Created attachment 402536 [details] Ebuild for python-ly
Created attachment 402538 [details] python-ly-0.9.1.ebuild Fix license and IUSE.
Created attachment 402708 [details] frescobaldi-2.18.ebuild
Created attachment 402710 [details, diff] frescobaldi-2.18-setup-py.patch Patch for https://github.com/wbsoft/frescobaldi/issues/638, needed only for 2.18 since it's fixed in the upcoming 2.18.1.
2.18.1 was released few days ago (2015-05-28) which supposedly (not listed in changelog) fixes the setup problem. At least, copying 2.0.16 ebuild to 2.18.1 installs fine as is (but doesn't actually work without python-ly). Also, 2.18 that was added to portage 2015-05-20 was added without python-ly. And so, it is broken and cannot be started: "The python-ly package is not available or too old. At least 0.9 is required to run Frescobaldi." Quick merge/test results: 2.18.1 works ok with copied 2.0.16 ebuild with added python-ly dependency (no extra patches). python-ly-0.9.1 posted here works fine for that matter.
Well, now a different frescobaldi-2.18 has been pushed into the tree, that is missing the python-ly dependency and is thus unusable. How did that happen?
Created attachment 404326 [details] frescobaldi-2.18.1.ebuild
Created attachment 404336 [details] frescobaldi-2.18.1.ebuild Use single-target mode, be strict about the portmidi dependency.
Pull request at: https://github.com/gentoo/gentoo/pull/312
This is fixed. Please close. commit 08f0618fc84f1d1c8b0011a7460d37fd1b1d924c Author: Karl Linden <karl.j.linden@gmail.com> Date: Sat Oct 31 15:07:20 2015 +0100 media-sound/frescobaldi: version bump to 2.18.1, depend on python-ly wrt #543052, #561022
