Created attachment 505256 [details] build log The last successfully merge is from six weeks ago, there have been quit a few updates since then, such as glibc/gcc/binutils - anyone else has this breakage? make -j4 rm -rf ./gtk-3.0/.sass-cache test -z "gtk-3.0/gtk.gresource gtk-3.0/gtk-contained.css gtk-3.0/gtk-contained-dark.css" || rm -f gtk-3.0/gtk.gresource gtk-3.0/gtk-contained.css gtk-3.0/gtk-contained-dark.css sass --update --sourcemap=none ./gtk-3.0 /usr/lib64/ruby/gems/2.2.0/gems/sass-3.4.25/lib/sass/version.rb:50:in `read': No such file or directory @ rb_sysopen - /usr/lib64/ruby/gems/2.2.0/gems/sass-3.4.25/VERSION (Errno::ENOENT) from /usr/lib64/ruby/gems/2.2.0/gems/sass-3.4.25/lib/sass/version.rb:50:in `version' from /usr/lib64/ruby/gems/2.2.0/gems/sass-3.4.25/lib/sass/version.rb:123:in `<module:Sass>' from /usr/lib64/ruby/gems/2.2.0/gems/sass-3.4.25/lib/sass/version.rb:4:in `<top (required)>' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib64/ruby/gems/2.2.0/gems/sass-3.4.25/lib/sass.rb:4:in `<top (required)>' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib64/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib64/ruby/gems/2.2.0/gems/sass-3.4.25/bin/sass:6:in `<top (required)>' from /usr/bin/sass:9:in `load' from /usr/bin/sass:9:in `<main>' make: *** [Makefile:559: compile] Error 1
Created attachment 505258 [details] emerge --info the breakage happened as I did an emerge -e world after upgrade to gcc-6.4.0 yesterday, but binutils and glibc updates also had been pulled in a few days before this.
output of emerge -pv greybird for useflags $ emerge -pv greybird These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ~] x11-themes/greybird-3.22.3::gentoo USE="-ayatana -gnome" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB
I ran into this too with greybird 3.22.3. To succesfully emerge, I did exactly what the error says: I created empty files called "VERSION" and "VERSION_NAME" under /usr/lib/ruby/gems/2.2.0/gems/sass-3.4.24/ --> successful emerge So why they aren't there or why they are searched for? I don't know. I looked into the different dev-ruby/sass ebuilds and there is one line with this content: RUBY_FAKEGEM_EXTRAINSTALL="rails init.rb VERSION VERSION_NAME" Seems to me (I am no programmer), it should generate something related and what's missing here. But why is it missing or should it be there, I don't know.
Maybe one could try to put that into the greybird ebuild with "inherit ruby-fakegem"?
*** This bug has been marked as a duplicate of bug 638466 ***
Please close #638466 instead as duplicated. (and asign to ruby team)
(In reply to Machredsch from comment #4) > Maybe one could try to put that into the greybird ebuild with "inherit > ruby-fakegem"? Sadly, this doesn't work because there is some error in the synthax of the ebuild if you only inherit that eclass to the greybird and do nothing else. (In reply to Machredsch from comment #3) > I ran into this too with greybird 3.22.3. > To succesfully emerge, I did exactly what the error says: > I created empty files called "VERSION" and "VERSION_NAME" under > /usr/lib/ruby/gems/2.2.0/gems/sass-3.4.24/ > --> successful emerge > > So why they aren't there or why they are searched for? > I don't know. > I looked into the different dev-ruby/sass ebuilds and there is one line with > this content: > RUBY_FAKEGEM_EXTRAINSTALL="rails init.rb VERSION VERSION_NAME" > Seems to me (I am no programmer), it should generate something related and > what's missing here. But why is it missing or should it be there, I don't > know. Indeed, if you drop empty files with the name VERSION and VERSION_NAME into the gemes/sass-x folder the ebuild passes up to src_install. I'll do some runtime testing by tomorrow. And before I forget it, I don't know why this bug was closed for being a duplicate, if there is another bug hitting this which is newer, and where there is no talking and no basic informations.
