Source: ruby-psych Version: 3.1.0+really3.1.0-1 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > JRUBY_HOME=/usr/share/jruby jruby -S rake compile > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > jnr.posix.JavaLibCHelper$ReflectiveAccess to method > sun.nio.ch.SelChImpl.getFD() > WARNING: Please consider reporting this to the maintainers of > jnr.posix.JavaLibCHelper$ReflectiveAccess > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > NameError: undefined method `default_specifications_dir' for class > `#<Class:0x1cfd1875>' > singleton class at > /usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb:84 > <main> at > /usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb:58 > require at org/jruby/RubyKernel.java:956 > <main> at /usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1 > require at org/jruby/RubyKernel.java:956 > <main> at /usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1347 > load at org/jruby/RubyKernel.java:974 > <main> at uri:classloader:/jruby/kernel/gem_prelude.rb:1 > make[1]: *** [debian/rules:12: override_dh_auto_build-indep] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/12/05/ruby-psych_3.1.0+really3.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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. 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.