Source: ruby-tins Version: 1.1.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': > cannot load such file -- sync (LoadError) > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from > /<<PKGBUILDDIR>>/debian/ruby-tins/usr/lib/ruby/vendor_ruby/tins/dslkit.rb:3:in > `<top (required)>' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from > /<<PKGBUILDDIR>>/debian/ruby-tins/usr/lib/ruby/vendor_ruby/tins.rb:51:in > `<module:Tins>' > from > /<<PKGBUILDDIR>>/debian/ruby-tins/usr/lib/ruby/vendor_ruby/tins.rb:1:in `<top > (required)>' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from > /<<PKGBUILDDIR>>/debian/ruby-tins/usr/lib/ruby/vendor_ruby/tins/xt.rb:1:in > `<top (required)>' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from /<<PKGBUILDDIR>>/tests/deep_dup_test.rb:2:in `<top (required)>' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in > `require' > from debian/ruby-tests.rb:2:in `block in <main>' > from debian/ruby-tests.rb:2:in `each' > from debian/ruby-tests.rb:2:in `<main>' > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/02/22/ruby-tins_1.1.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
