The sass package was updated to version 3.1.19, yet portage only goes up to 3.1.17. Renaming the ebuild is enough because version 3.1.18 and 3.1.19 are just bug fix releases; I am using sass-3.1.19 (installed by overlay) on a couple of Gentoo/Linux servers (hardened profile) serving both ruby18 and ruby19 applications and they are working flawless. Reproducible: Always
Created attachment 315967 [details] dev-ruby/sass-3.1.9 build log with FEATURES="test"
Created attachment 316125 [details] dev-ruby/sass-3.1.9 build log with FEATURES="test" for unknown reasons, bugzilla has corrupted my previous build log file during the upload process; I am submitting a new one and without compression.
(In reply to comment #2) > Created attachment 316125 [details] > dev-ruby/sass-3.1.9 build log with FEATURES="test" > Your log lacks ree18 and jruby which are also targets in the ebuild, and in this case jruby had failing tests. I've added sass 3.1.19 anyway since these failures are due to particulars of the CRuby implementation so we now avoid these tests for jruby.