Your message dated Tue, 1 Mar 2016 13:04:04 +0100 with message-id <20160301120404.gb23...@percival.namespace.at> and subject line #816256 - fixed in unstable has caused the Debian Bug report #816256, regarding ruby-versionomy: FTBFS: `require': cannot load such file -- blockenspiel/unmixer_mri (LoadError) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 816256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-versionomy Version: 0.4.4-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ruby-versionomy fails to build from source in unstable/amd64: [..] RUBYLIB=/home/lamby/temp/cdt.20160229080839.yx3VvECwEf/ruby-versionomy-0.4.4/debian/ruby-versionomy/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-versionomy/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\ \|f\|\ require\ f\ \} /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- blockenspiel/unmixer_mri (LoadError) from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/blockenspiel.rb:48:in `<top (required)>' from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /home/lamby/temp/cdt.20160229080839.yx3VvECwEf/ruby-versionomy-0.4.4/debian/ruby-versionomy/usr/lib/ruby/vendor_ruby/versionomy.rb:37:in `<top (required)>' from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /home/lamby/temp/cdt.20160229080839.yx3VvECwEf/ruby-versionomy-0.4.4/test/tc_custom_format.rb:39:in `<top (required)>' from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require' from -e:1:in `block in <main>' from -e:1:in `each' from -e:1:in `<main>' ERROR: Test "ruby2.3" failed. Exiting. dh_auto_install: dh_ruby --install /home/lamby/temp/cdt.20160229080839.yx3VvECwEf/ruby-versionomy-0.4.4/debian/ruby-versionomy returned exit code 1 debian/rules:19: recipe for target 'override_dh_auto_install' failed make[1]: *** [override_dh_auto_install] Error 1 make[1]: Leaving directory '/home/lamby/temp/cdt.20160229080839.yx3VvECwEf/ruby-versionomy-0.4.4' debian/rules:15: recipe for target 'binary' failed make: *** [binary] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
ruby-versionomy.0.4.4-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---As indicated, this has been fixed in unstable. -- ,''`. Christian Hofstaedtler <z...@debian.org> : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `-
--- End Message ---
