Source: ruby-redis-rack Version: 2.1.2-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210213 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > ArgumentError: unknown keywords: :path, :domain, :expire_after, :secure, > :httponly, :defer, :renew, :sidbits, :secure_random, :redis_server > /usr/share/rubygems-integration/all/gems/redis-4.2.5/lib/redis.rb:836:in > `set' > /usr/lib/ruby/vendor_ruby/redis/store/interface.rb:9:in `set' > /usr/lib/ruby/vendor_ruby/redis/store/ttl.rb:8:in `set' > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `block in set' > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:39:in `_marshal' > /usr/lib/ruby/vendor_ruby/redis/store/serialization.rb:5:in `set' > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `block in set' > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:84:in `namespace' > /usr/lib/ruby/vendor_ruby/redis/store/namespace.rb:7:in `set' > /<<PKGBUILDDIR>>/lib/rack/session/redis.rb:49:in `block (2 levels) in > write_session' > /<<PKGBUILDDIR>>/lib/redis/rack/connection.rb:22:in `with' > /<<PKGBUILDDIR>>/lib/rack/session/redis.rb:82:in `with' > /<<PKGBUILDDIR>>/lib/rack/session/redis.rb:49:in `block in write_session' > /<<PKGBUILDDIR>>/lib/rack/session/redis.rb:70:in `with_lock' > /<<PKGBUILDDIR>>/lib/rack/session/redis.rb:48:in `write_session' > /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:391:in > `commit_session' > /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:271:in `context' > /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:263:in `call' > /usr/lib/ruby/vendor_ruby/rack/mock.rb:77:in `request' > /usr/lib/ruby/vendor_ruby/rack/mock.rb:59:in `get' > /<<PKGBUILDDIR>>/test/rack/session/redis_test.rb:153:in `block (3 levels) > in <top (required)>' > /<<PKGBUILDDIR>>/test/rack/session/redis_test.rb:396:in > `with_pool_management' > /<<PKGBUILDDIR>>/test/rack/session/redis_test.rb:151:in `block (2 levels) > in <top (required)>' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98:in `block (3 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:270:in `time_it' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:1029:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:339:in `run_one_method' > /usr/lib/ruby/vendor_ruby/minitest.rb:326:in `block (2 levels) in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `each' > /usr/lib/ruby/vendor_ruby/minitest.rb:325:in `block in run' > /usr/lib/ruby/vendor_ruby/minitest.rb:365:in `on_signal' > /usr/lib/ruby/vendor_ruby/minitest.rb:352:in `with_info_handler' > /usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `block in __run' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `map' > /usr/lib/ruby/vendor_ruby/minitest.rb:164:in `__run' > /usr/lib/ruby/vendor_ruby/minitest.rb:141:in `run' > /usr/lib/ruby/vendor_ruby/minitest.rb:68:in `block in autorun' > > 34 runs, 78 assertions, 0 failures, 10 errors, 0 skips > pkill redis-server > rake aborted! > Tests failed > /<<PKGBUILDDIR>>/debian/ruby-tests.rake:12:in `block in <top (required)>' > /usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in `<top > (required)>' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2021/02/13/ruby-redis-rack_2.1.2-4_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.
