Your message dated Tue, 22 Apr 2025 17:17:42 +0000 with message-id <e1u7hfe-008n9b...@fasolo.debian.org> and subject line Bug#1103605: Removed package(s) from unstable has caused the Debian Bug report #1090877, regarding ruby-redis-rails: FTBFS with ruby-mocha 2: ERROR: Test "ruby3.1" failed: <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:86:in `require': cannot load such file -- mocha/setup (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.) -- 1090877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-redis-rails Version: 5.0.2-3 Severity: important Justification: FTBFS Tags: trixie sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-mocha-2 Hi, We are trying to update ruby-mocha to version 2, currently available in experimental. During a test rebuild, ruby-redis-rails was found to fail to build in that situation. To reproduce this locally, you need to install ruby-mocha from experimental on an unstable system or build chroot. Relevant part (hopefully): > <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:86:in > `require': cannot load such file -- mocha/setup (LoadError) > from > <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:86:in > `require' > from > /build/reproducible-path/ruby-redis-rails-5.0.2/test/test_helper.rb:2:in > `<top (required)>' > from > <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:86:in > `require' > from > <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:86:in > `require' > from > /build/reproducible-path/ruby-redis-rails-5.0.2/test/redis_rails_test.rb:1:in > `<top (required)>' > from > <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:86:in > `require' > from > <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:86:in > `require' > from > /usr/share/rubygems-integration/all/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:21:in > `block in <main>' > from > /usr/share/rubygems-integration/all/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:6:in > `select' > from > /usr/share/rubygems-integration/all/gems/rake-13.2.1/lib/rake/rake_test_loader.rb:6:in > `<main>' > rake aborted! > Command failed with status (1) > /usr/share/rubygems-integration/all/gems/rake-13.2.1/exe/rake:27:in `<top > (required)>' > Tasks: TOP => default => test > (See full trace by running task with --trace) > ERROR: Test "ruby3.1" failed: The full build log is available at https://people.debian.org/~terceiro/ruby-mocha-2/ruby-redis-rails_arm64-2024-12-20T10:19:16Z.build This bug report is being filed as severity important, but will be raised to serious once ruby-mocha is updated in unstable.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Version: 5.0.2-3+rm Dear submitter, as the package ruby-redis-rails has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1103605 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---