dependency.bad 68 net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome/systemd) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/gnome/systemd) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde/systemd) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/desktop/kde/systemd) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~amd64(default/linux/amd64/13.0/developer) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~amd64(default/linux/amd64/13.0/developer) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~ppc(default/linux/powerpc/ppc32/13.0) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: RDEPEND: ~ppc(default/linux/powerpc/ppc32/13.0) ['dev-lang/ruby:1.8'] net-irc/epic5/epic5-1.1.2.ebuild: DEPEND: ~ppc(default/linux/powerpc/ppc32/13.0/desktop) ['dev-lang/ruby:1.8']
I had a quick look at this, but the current 1.1.2 version doesn't seem to work with ruby19. Upstream has released 1.1.7, but the Gentoo patches for ruby support won't apply there and I'm not really sure what their intention is. I would hope that a maintainer picks this up and fixes things. My solution would be to remove the ruby support... Note that there is also bug 497080 which is effectively pointing to the same issue, already a couple of months old. @binki: ?
+*epic5-1.1.7 (25 Mar 2014) + + 25 Mar 2014; Nathan Phillip Brink <binki@gentoo.org> +epic5-1.1.7.ebuild, + +files/epic5-1.1.7-ruby-automagic-as-needed.patch, -epic5-1.1.2.ebuild, + -files/epic5-1.1.2-ruby-automagic-as-needed.patch: + Bump to epic5-1.1.7 which has ruby19 support for bug #505232. Fortunately, upstream added support for ruby19 in epic5-1.1.7 (epic5-1.1.6 still used STR2CSTR macro, for example). Bumped, hopefully this fixes things, albeit late.