The RDEPEND in the ebuilds reads like this: RDEPEND=">=media-libs/alsa-lib-${PV} <media-libs/alsa-lib-1.0.20-r1 fltk? ( =x11-libs/fltk-1.1* ) gtk? ( =x11-libs/gtk+-2* )" DEPEND="${RDEPEND}" As you can see, alsa-lib is in there *twice*. Which works, as long as both atoms result in the same version of the lib. But still is wrong. In the (still masked) version 1.0.20-r1, the ${PV} changed to 1.0.20-r1, now reading: RDEPEND=">=media-libs/alsa-lib-1.0.20-r1 <media-libs/alsa-lib-1.0.20-r1 fltk? ( =x11-libs/fltk-1.1* ) gtk? ( =x11-libs/gtk+-2* )" DEPEND="${RDEPEND}" Which of course can't work. ^^ I removed the second line, in my own local -r2 version (because r1 also has a bug with the envy24control config dir, which I fixed), and it seems to work fine. So I recommend, we throw the patch for the config dir, this change and the reason it is still masked, together, and when it works, release it as -r1, instead of adding another release. (If possible. Dunno the protocol around here.) Reproducible: Always Steps to Reproduce:
Created attachment 193850 [details] The fixed ebuild for this patch, which includes the patch for bug #273137. See in bug #273129 for more infos about the patch.
Now all that is to do, is put the files in Portage. (Which I can't do.) That's why it's not closed.
AWesome, thanks for the fix. Also, next time, can you do a diff instead of the full ebuild? Makes it much easier.
