Bug#1000333: gem2deb: ignore or find a way to make <= constraint in gemspec work
Control: tag -1 - wontfix > Sent from my Android device with K-9 Mail. Please excuse my brevity. On Tue, Nov 23, 2021 at 06:21:14AM +0530, Pirate Praveen wrote: > > > 2021, നവംബർ 22 11:12:36 PM IST, Antonio Terceiro ൽ എഴുതി > >Control: tag -1 + wontfix > > > >On Sun, Nov 21, 2021 at 11:51:22PM +0530, Pirate Praveen wrote: > >> Package: gem2deb > >> Version: 1.7 > >> Severity: wishlist > >> > >> should we really honor <= constraint in gemspecs? in ruby-google-fog > >> upstream wants fog-core <= 2.1.0 it will never be satisfied in debian > >> > >> because 2.1.0-1 >= 2.1.0 and we have 2.1.0-3.1 in archive > >> > >> we could either ignore or may be detect the current version in the archive > >> (it will require a rebuild if dependency change) > > > >In cases like this, IMO the gemspec needs to be patched to drop such > >dependency. Even if we did ignore it and didn't represent that with a > >corresponding << constraint in debian/control, the dependency check will > >still fail during the build unless the gemspec is patched. > > In this specific case the build did not fail, only installation during > autopkgtest that failed because of control file. > > fog-core version in its gemspec is 2.1.0 and it satisfies. > > This is to take care of debian revision only, for new upstream versions, we > still have to patch if update needed. Yes, now I understand what is the issue. I think we could fix that by translating <= x.y to <= x.y- ? <= is not handled in any special way at the moment. signature.asc Description: PGP signature
Bug#1000521: libpod: please provide podman-remote binary
Source: libpod Version: 3.4.1+ds1-2 Severity: wishlist Dear Maintainer, Recent podman upstream releases provide a new podman-remote binary, but the Debian package does not even build it. I'm used to packages providing binaries without a manpage, but this is the first time I have seen the opposite! :-) $ dpkg -S podman-remote podman: /usr/share/zsh/vendor-completions/_podman-remote podman: /usr/share/man/man1/podman-remote.1.gz -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#1000333: gem2deb: ignore or find a way to make <= constraint in gemspec work
Control: tag -1 + wontfix On Sun, Nov 21, 2021 at 11:51:22PM +0530, Pirate Praveen wrote: > Package: gem2deb > Version: 1.7 > Severity: wishlist > > should we really honor <= constraint in gemspecs? in ruby-google-fog > upstream wants fog-core <= 2.1.0 it will never be satisfied in debian > > because 2.1.0-1 >= 2.1.0 and we have 2.1.0-3.1 in archive > > we could either ignore or may be detect the current version in the archive > (it will require a rebuild if dependency change) In cases like this, IMO the gemspec needs to be patched to drop such dependency. Even if we did ignore it and didn't represent that with a corresponding << constraint in debian/control, the dependency check will still fail during the build unless the gemspec is patched. signature.asc Description: PGP signature
Bug#996584: (some kind of) transition: add python3.10 as a supported python3 version
On Thu, Nov 18, 2021 at 10:01:17AM +0100, Sebastiaan Couwenberg wrote: > On 11/18/21 09:49, Matthias Klose wrote: > > On 11/18/21 06:51, Sebastiaan Couwenberg wrote: > > > On 11/16/21 14:23, Matthias Klose wrote: > > > > I'm planning to upload python3-defaults later tonight, adding 3.10 as a > > > > supported Python version. Packages are able to migrate on their own, > > > > there are > > > > no blockages introduced on other transitions. > > > > > > numpy rdeps (e.g. pyproj) are a bit problematic, they fail with the 3.10 > > > as long > > > as numpy is not built with it yet. > > > > numpy is in stage6 of the transition. so please be a bit patient until all > > the > > binNMUs up to stage6 are built. > > There has been no communication about this transition outside this > bugreport, you should probably follow the example for perl transitions to > alert the developer base about the expected ImportError issues with the new > version until the rebuilds are completed. This Python transition is different from the Perl transitions. Python has multiple simultaneously supported versions, in this case 3.9 and 3.10. The transition involves rebuilding the packages with C extensions so that they carry the associated binary files compiled for both support Python versions. Any errors due to missing support in dependencies affect only people building Python packages. The default Python is still Python 3.9, so users using Python programs are not affected during this transition. Perl, on the other hand, has only a single version at the archive at any time. This is why during the Perl transition, it's possible that users running Perl programs are affected by missing C extensions during the time it takes to rebuild all packages for the new Perl version. signature.asc Description: PGP signature
Bug#1000155: O: pinpoint -- hacker-friendly presentation program
Package: wnpp Severity: normal Control: affects -1 src:pinpoint I'm orphaning the pinpoint package. The package description is: Pinpoint is a simple presentation tool that uses a plain text file as input. It supports specifying the text position, styling the text, using images or videos as background for slides, embedding commands to be run on specific slides, a speaker view window, and other nice features. There is no upstream development currently going on, and there are some pretty bag bugs that happen from time to time (it's not easy to reproduce them consistently). I no longer use pinpoint, and don't have the motivation to work on it anymore. I'm uploading the last bits I had done a long time ago, from the last time I tried to use it. signature.asc Description: PGP signature
Bug#1000154: ITP: ruby-rantly -- Ruby Imperative Random Data Generator and Quickcheck
Package: wnpp Severity: wishlist Owner: Antonio Terceiro X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: ruby-rantly Version : 2.0.0 Upstream Author : Ana María Martínez Gómez, Howard Yeh, Anthony Bargnesi, Eric Bischoff * URL : https://github.com/rantly-rb/rantly * License : MIT (Expat) Programming Lang: Ruby Description : Ruby Imperative Random Data Generator and Quickcheck You can use Rantly to generate random test data, and use its Test::Unit extension for property-based testing. Rantly is basically a recursive descent interpreter, each of its method returns a random value of some type (string, integer, float, etc.). debian/control I'm packaging this as a build dependency for a new version of ruby-moneta. It seems like a pretty useful library. signature.asc Description: PGP signature
Bug#1000140: Acknowledgement (ruby-moneta: FTBFS: mysqld fails to start)
Control: retitle -1 ruby-moneta: FTBFS: mysqld fails to start on tmpfs Control: severity -1 important I perceived that this is triggered by my sbuild/schroot setup building packages with a tmpfs overlay (union-overlay-directory=/dev/shm), so this does not happen always. I'm thus downgrading the severity of this bug. signature.asc Description: PGP signature
Bug#1000140: ruby-moneta: FTBFS: mysqld fails to start
Source: ruby-moneta Version: 1.0.0-9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs X-Debbugs-CC: debian-r...@lists.debian.org Hi, ruby-moneta fails to build from source. This is a recurring problem. We have a ton of scritps to start mysql for running tests, they are all slightly different, and they all break from time to time. :-/ Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rb > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-moneta/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-moneta/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 debian/ruby-tests.rb > 2021-11-18 14:48:53 0 [Warning] InnoDB: Retry attempts for writing partial > data failed. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Write to file ./ibdata1 failed at > offset 0, 1048576 bytes should have been written, only 0 were written. > Operating system error number 22. Check that your OS and file system support > files of this size. Check also that the disk is not full or a disk quota > exceeded. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Could not set the file size of > './ibdata1'. Probably out of disk space > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Database creation was aborted with > error Generic error. You may need to delete the ibdata1 file before trying to > start up again. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Operating system error number 22 in a > file operation. > 2021-11-18 14:48:53 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument' > 2021-11-18 14:48:53 0 [ERROR] InnoDB: File (unknown): 'close' returned OS > error 222. Cannot continue operation > 28 14:48:53 [ERROR] mysqld got signal 6 ; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > > To report this bug, see https://mariadb.com/kb/en/reporting-bugs > > We will try our best to scrape up some info that will hopefully help > diagnose the problem, but since we have already crashed, > something is definitely wrong and this may fail. > > Server version: 10.6.4-MariaDB-1+b1 > key_buffer_size=134217728 > read_buffer_size=131072 > max_used_connections=0 > max_threads=153 > thread_count=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467956 > K bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > Thread pointer: 0x0 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > stack_bottom = 0x0 thread_stack 0x49000 > ??:0(my_print_stacktrace)[0x55f65c52e8fe] > ??:0(handle_fatal_signal)[0x55f65c07d2f8] > ??:0(__restore_rt)[0x7ffa991ac8e0] > ??:0(gsignal)[0x7ffa98cb7e71] > ??:0(abort)[0x7ffa98ca1536] > ??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, > wsrep::ws_meta const&))[0x55f65bd31214] > ??:0(std::unique_lock::unlock())[0x55f65c38bc05] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c499e68] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c499ed1] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c49c530] > ??:0(void std::vector > >::_M_realloc_insert(__gnu_cxx::__normal_iterator long*, std::vector > >, unsigned > long&&))[0x55f65c49d651] > ??:0(void std::this_thread::sleep_for > >(std::chrono::duration > const&))[0x55f65c3fa717] > ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view > const*))[0x55f65c33aa95] > ??:0(ha_initialize_handlerton(st_plugin_int*))[0x55f65c08042e] > ??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*, > st_plugin_int*, st_mysql_sys_var*))[0x55f65be7ae06] > ??:0(plugin_init(int*, char**, int))[0x55f65be7bdc8] > ??:0(unireg_abort)[0x55f65bda783a] > ??:0(mysqld_main(int, char**))[0x55f65bdad3b2] > ??:0(__libc_start_main)[0x7ffa98ca2e4a] > ??:0(_start)[0x55f65bda29ca] > The manual page at > https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ > contains > information that should help you find out what is causing the crash. > Writing a
Bug#999726: ruby-omniauth-shibboleth: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: Failure/Error: expect(last_response.status).to eq(302)
Source: ruby-omniauth-shibboleth Version: 1.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-shibboleth was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > Failure/Error: expect(last_response.status).to eq(302) > >expected: 302 > got: 200 > >(compared using ==) > # ./spec/omniauth/strategies/shibboleth_spec.rb:42:in `block (3 levels) > in ' > > Finished in 0.06473 seconds (files took 0.14061 seconds to load) > 16 examples, 1 failure > > Failed examples: > > rspec ./spec/omniauth/strategies/shibboleth_spec.rb:41 # > OmniAuth::Strategies::Shibboleth request phase is expected to redirect to > callback_url > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-shibboleth.log signature.asc Description: PGP signature
Bug#999725: ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co
Source: ruby-omniauth-saml Version: 1.10.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-saml was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.3, >= 1.3.2) among > 77 total gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all/specifications/omniauth-saml-1.10.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.3, >= 1.3.2) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-saml/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > docile (1.1.5) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > macaddr (1.7.1) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > nokogiri (1.11.7) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > pkg-config (1.4.6) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby-saml (1.13.0) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > simplecov (0.19.1) > simplecov-html (0.12.3) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > systemu (2.6.5) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > uuid (2.3.9) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0)
Bug#999724: ruby-omniauth-salesforce: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencie
Source: ruby-omniauth-salesforce Version: 1.0.5-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-salesforce was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 85 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all/specifications/omniauth-salesforce-1.0.5.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-salesforce/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > docile (1.1.5) > etc (default: 1.1.0) > faraday (1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > multi_json (1.14.1) > multi_xml (0.6.0) > multipart-post (2.0.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth2 (1.4.4) > observer (default: 0.1.0) > omniauth (2.0.4) > omniauth-oauth2 (1.7.1) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby2_keywords (0.0.2) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > simplecov (0.19.1) > simplecov-html (0.12.3) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default:
Bug#999723: ruby-omniauth-remote-user: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependenci
Source: ruby-omniauth-remote-user Version: 0.1.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-remote-user was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 68 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all/specifications/omniauth-remote-user-0.1.3.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-remote-user/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at
Bug#999722: ruby-omniauth-openid: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies':
Source: ruby-omniauth-openid Version: 1.0.1-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-openid was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 77 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-openid/usr/share/rubygems-integration/all/specifications/omniauth-openid-1.0.1.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-openid (1.4.2) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby-hmac (0.4.0) > ruby-openid (2.9.2) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) >
Bug#999721: ruby-omniauth-openid-connect: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_depende
Source: ruby-omniauth-openid-connect Version: 0.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-openid-connect was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.9) among 106 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all/specifications/gitlab-omniauth-openid-connect-0.4.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.9) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-openid-connect/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > activemodel (6.0.3.7) > activesupport (6.0.3.7) > addressable (2.8.0) > aes_key_wrap (1.0.1) > atomic (1.1.16) > attr_required (1.0.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bindata (2.4.8) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > concurrent-ruby (1.1.6) > concurrent-ruby-edge (0.6.0) > coveralls (0.8.23) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > docile (1.1.5) > domain_name (0.5.20190701) > etc (default: 1.1.0) > faker (1.9.1) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > http-accept (1.7.0) > http-cookie (1.0.3) > httpclient (2.8.3) > i18n (1.8.11) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > json-jwt (1.11.0) > logger (default: 1.4.2) > mail (2.7.1) > matrix (default: 0.2.0) > metaclass (0.0.4) > mime-types (3.3.1) > mime-types-data (3.2015.1120) > mini_mime (1.1.1) > minitest (5.13.0) > mocha (1.7.0) > multi_json (1.14.1) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > netrc (0.11.0) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openid_connect (1.2.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-oauth2 (1.16.0) >
Bug#999712: ruby-omniauth-azure-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependenc
Source: ruby-omniauth-azure-oauth2 Version: 0.0.10-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-azure-oauth2 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all/specifications/omniauth-azure-oauth2-0.0.10.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-azure-oauth2/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > faraday (1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > multi_json (1.14.1) > multi_xml (0.6.0) > multipart-post (2.0.0) > mustermann (1.1.1) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth2 (1.4.4) > observer (default: 0.1.0) > omniauth (2.0.4) > omniauth-oauth2 (1.7.1) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby2_keywords (0.0.2) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > sinatra (2.0.8.1) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > tilt (2.0.10) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR:
Bug#999713: ruby-omniauth-cas3: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co
Source: ruby-omniauth-cas3 Version: 1.1.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-cas3 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.2) among 77 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all/specifications/omniauth-cas3-1.1.4.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.2) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-cas3/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > awesome_print (1.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > nokogiri (1.11.7) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > pkg-config (1.4.6) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at
Bug#999720: ruby-omniauth-oauth: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': C
Source: ruby-omniauth-oauth Version: 1.1.0-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-oauth was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 78 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all/specifications/omniauth-oauth-1.1.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-oauth/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > docile (1.1.5) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth (0.5.4) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > simplecov (0.19.1) > simplecov-html (0.12.3) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml
Bug#999719: ruby-omniauth-multipassword: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError:
Source: ruby-omniauth-multipassword Version: 0.4.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-multipassword was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. I would expect a new upstream version to work against the latest ruby-omniauth just fine. Relevant part (hopefully): > NoMethodError: >undefined method `[]' for nil:NilClass > # ./spec/omniauth/strategy/multi_password_spec.rb:32:in `block (4 > levels) in ' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:202:in > `call!' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:169:in > `call' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/test/phony_session.rb:11:in > `call' > # ./spec/omniauth/strategy/multi_password_spec.rb:37:in `block (2 > levels) in ' > > Finished in 0.03768 seconds (files took 0.14531 seconds to load) > 11 examples, 2 failures > > Failed examples: > > rspec ./spec/omniauth/multipassword/base_spec.rb:61 # > OmniAuth::MultiPassword::Base single strategy shows login FORM > rspec ./spec/omniauth/strategy/multi_password_spec.rb:36 # > OmniAuth::Strategies::MultiPassword shows login FORM > > Randomized with seed 13795 > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-multipassword.log signature.asc Description: PGP signature
Bug#999718: ruby-omniauth-ldap: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Co
Source: ruby-omniauth-ldap Version: 2.1.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-ldap was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.3) among 71 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all/specifications/gitlab_omniauth-ldap-2.1.1.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.3) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-ldap/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-ldap (0.16.3) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > pyu-ruby-sasl (0.0.3.3) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > rubyntlm (0.6.3) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-ldap.log signature.asc Description: PGP
Bug#999717: ruby-omniauth-jwt: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Cou
Source: ruby-omniauth-jwt Version: 0.0.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-jwt was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.1) among 68 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all/specifications/omniauth-jwt-0.0.2.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.1) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml (default: 0.1.0) > zlib (default: 1.1.0) > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-jwt.log signature.asc Description: PGP signature
Bug#999716: ruby-omniauth-google-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError:
Source: ruby-omniauth-google-oauth2 Version: 0.6.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-google-oauth2 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > NoMethodError: >undefined method `[]' for nil:NilClass > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:501:in > `script_name' > # > /usr/share/rubygems-integration/all/gems/omniauth-2.0.4/lib/omniauth/strategy.rb:450:in > `callback_path' > # ./spec/omniauth/strategies/google_oauth2_spec.rb:293:in `block (3 > levels) in ' > > Finished in 0.09861 seconds (files took 0.22631 seconds to load) > 102 examples, 1 failure > > Failed examples: > > rspec ./spec/omniauth/strategies/google_oauth2_spec.rb:292 # > OmniAuth::Strategies::GoogleOauth2#callback_path has the correct default > callback path > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available at https://people.debian.org/~terceiro/rebuilds/ruby-omniauth-2.0/ruby-omniauth-google-oauth2.log signature.asc Description: PGP signature
Bug#999715: ruby-omniauth-github: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies':
Source: ruby-omniauth-github Version: 1.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-github was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.5) among 82 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-github/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-github/usr/share/rubygems-integration/all/specifications/omniauth-github-1.4.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.5) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-github/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > addressable (2.8.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > faraday (1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > jwt (2.2.2) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > multi_json (1.14.1) > multi_xml (0.6.0) > multipart-post (2.0.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > oauth2 (1.4.4) > observer (default: 0.1.0) > omniauth (2.0.4) > omniauth-oauth2 (1.7.1) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > ruby2_keywords (0.0.2) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) > xmlrpc (0.3.2) > yaml
Bug#999714: ruby-omniauth-crowd: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': C
Source: ruby-omniauth-crowd Version: 2.4.0-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby-omniauth-2.0 Hi, I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test rebuild, ruby-omniauth-crowd was found to fail to build in that situation. To reproduce this locally, you need to install ruby-omniauth from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 84 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all/specifications/omniauth_crowd-2.4.0.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'omniauth' (~> 1.0) - did find: [omniauth-2.0.4] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > activesupport (6.0.3.7) > addressable (2.8.0) > atomic (1.1.16) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > concurrent-ruby (1.1.6) > concurrent-ruby-edge (0.6.0) > crack (0.4.4) > csv (default: 3.1.2) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > etc (default: 1.1.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > hashdiff (1.0.1) > hashie (3.5.5) > i18n (1.8.11) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > minitest (5.13.0) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-smtp (default: 0.1.0) > net-telnet (0.1.1) > nokogiri (1.11.7) > observer (default: 0.1.0) > omniauth (2.0.4) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > pkg-config (1.4.6) > power_assert (1.1.7) > prime (default: 0.1.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > public_suffix (4.0.6) > racc (default: 1.4.16) > rack (2.1.4) > rack-protection (2.0.8.1) > rack-test (0.7.0) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec (3.9.0) > rspec-core (3.9.2) > rspec-expectations (3.9.2) > rspec-mocks (3.9.1) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > safe_yaml (1.0.5) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > thread_safe (0.3.6) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > tzinfo (1.2.6) > uri (default: 0.10.0) > webmock (3.8.3) > webrick (default: 1.6.1) >
Bug#998638: ruby-localhost: spec/localhost/protocol_spec.rb fails on ci.debian.net and salsa
On Fri, Nov 05, 2021 at 09:10:32AM -0300, Antonio Terceiro wrote: > Source: ruby-localhost > Version: 1.1.8-2 > Severity: serious > Tags: bookworm sid ftbfs > User: debian-r...@lists.debian.org > Usertags: ruby3.0 > > I was looking at the testing migration excuses for puma, which brought > me to ruby-localhost. spec/localhost/protocol_spec.rb very often, but > not always, fails. This is currently blocking testing migration. > > Example of failed logs: > > on ci.debian.net: > https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-localhost/16388045/log.gz > > on salsa: > https://salsa.debian.org/ruby-team/ruby-localhost/-/jobs/2150375 (i386 build) > https://salsa.debian.org/ruby-team/ruby-localhost/-/jobs/2150382 (autopkgtest) > > I even tried a new upstream version 1.1.9 that is available to see if it > made things better, but it doesn't: > https://salsa.debian.org/ruby-team/ruby-localhost/-/commits/test > https://salsa.debian.org/ruby-team/ruby-localhost/-/pipelines/310716 Actually version 1.1.9 does fix this, by not trying an curl option that is now ignored by curl > 7.77; I don't know why this didn't fix it for me last week when I tried this. Anyway I'm uploading the new upstream version as fix for this. signature.asc Description: PGP signature
Bug#999479: mypy: please build-depend in python3-typeshed instead of individual python3-types-* packages
Control: tag -1 + patch
Control: forwarded https://salsa.debian.org/med-team/mypy/-/merge_requests/2
On Fri, Nov 12, 2021 at 09:25:57AM +0100, Andreas Tille wrote:
> Hi Antonio,
>
> Am Thu, Nov 11, 2021 at 02:14:21PM -0300 schrieb Antonio Terceiro:
> > typeshed is now in unstable. Please use python3-typeshed as build
> > dependency so we can remove the individual python3-types-* packages in
> > favor of typeshed.
>
> I tried to do so ...
>
> diff --git a/debian/control b/debian/control
> index e53840d0..10d17679 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -15,10 +15,7 @@ Build-Depends: debhelper-compat (= 13),
> python3-setuptools,
> python3-sphinx ,
> python3-sphinx-rtd-theme ,
> - python3-typed-ast (>= 1.4.0),
> - python3-typed-ast (<< 1.5.0),
> - python3-types-toml,
> - python3-types-typed-ast,
> + python3-typeshed,
> python3-psutil,
> python3-mypy-extensions,
> python3-typing-extensions,
you only want to drop python3-types-toml and python3-types-typed-ast,
but not python3-typed-ast (note "types" vs "typed").
> ... but I get:
>
> export TEST_MYPYC=1
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} -m mypy \
> --config-file {dir}/mypy_self_check.ini -p mypy" dh_auto_test
> pybuild --test -i python{version} -p 3.9
> I: pybuild base:237: python3.9 -m mypy --config-file
> /build/mypy-0.910/mypy_self_check.ini -p mypy
> mypy/dmypy_server.py:877: error: unused "type: ignore" comment
> import psutil # type: ignore # It's not in typeshed yet
> ^
> Found 1 error in 1 file (checked 162 source files)
> E: pybuild pybuild:354: test: plugin custom failed with: exit code=1:
> python3.9 -m mypy --config-file /build/mypy-0.910/mypy_self_check.ini
> -p mypy
> rm -fr -- /tmp/dh-xdg-rundir-ZEmBmRmU
> dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
> code 13
python3-typeshed *does* provide typing information for psutil, so that
`# type: ignore` comment is now unused; mypy_self_check.ini sets
`warn_unused_ignores` to `True`; and despite its name,
`warn_unused_ignores` actually produces errors.
You want a patch that `# type: ignore` out. I send a MR with the exact
changes I think should be done:
https://salsa.debian.org/med-team/mypy/-/merge_requests/2
signature.asc
Description: PGP signature
Bug#999479: mypy: please build-depend in python3-typeshed instead of individual python3-types-* packages
Source: mypy Version: 0.910-3 Severity: normal typeshed is now in unstable. Please use python3-typeshed as build dependency so we can remove the individual python3-types-* packages in favor of typeshed. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#998900: RM: django-restricted-resource -- ROM; deprecated, unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove src:django-restricted-resource. It used to be a lava dependency, but lava moved away to somethind else a while ago, and it's now unused and unmaintained. $ dak rm -Rn django-restricted-resource Will remove the following packages from unstable: django-restricted-resource | 2016.8-3 | source python3-django-restricted-resource | 2016.8-3 | all Maintainer: Debian LAVA team --- Reason --- -- Checking reverse dependencies... No dependency problem found. signature.asc Description: PGP signature
Bug#998638: ruby-localhost: spec/localhost/protocol_spec.rb fails on ci.debian.net and salsa
Source: ruby-localhost Version: 1.1.8-2 Severity: serious Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 I was looking at the testing migration excuses for puma, which brought me to ruby-localhost. spec/localhost/protocol_spec.rb very often, but not always, fails. This is currently blocking testing migration. Example of failed logs: on ci.debian.net: https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-localhost/16388045/log.gz on salsa: https://salsa.debian.org/ruby-team/ruby-localhost/-/jobs/2150375 (i386 build) https://salsa.debian.org/ruby-team/ruby-localhost/-/jobs/2150382 (autopkgtest) I even tried a new upstream version 1.1.9 that is available to see if it made things better, but it doesn't: https://salsa.debian.org/ruby-team/ruby-localhost/-/commits/test https://salsa.debian.org/ruby-team/ruby-localhost/-/pipelines/310716 One option is skipping this test, at least for now, with a patch like this: 8<8<8<- diff --git a/debian/ruby-tests.rake b/debian/ruby-tests.rake index cf1591e..6010dd7 100644 --- a/debian/ruby-tests.rake +++ b/debian/ruby-tests.rake @@ -2,4 +2,5 @@ require 'gem2deb/rake/spectask' Gem2Deb::Rake::RSpecTask.new do |spec| spec.pattern = './spec/**/*_spec.rb' + spec.exclude_pattern = './spec/localhost/protocol_spec.rb' end 8<8<8<- But ideally we would want to fix it. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#998636: libguestfs: incorrectly detects Ruby versions
Source: libguestfs Version: 1:1.44.2-1 Severity: important Tags: patch bookworm sid User: debian-r...@lists.debian.org Usertags: ruby3.0 Dear Maintainer, debian/rules currently employs a flawed way of detecting which ruby versions to build for: it looks for /usr/bin/ruby[12], what doesn't work now that we are moving to ruby3.0. Please apply the attached patch to make it future proof. This is currenly one of the last blockers in the transition to add support for ruby3.0, which blocks the subsequent transition to switch to ruby3.0 as default. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru libguestfs-1.44.2/debian/rules libguestfs-1.44.2/debian/rules --- libguestfs-1.44.2/debian/rules 2021-09-24 20:50:37.0 -0300 +++ libguestfs-1.44.2/debian/rules 2021-11-05 07:53:25.0 -0300 @@ -26,8 +26,7 @@ include /usr/share/dpkg/architecture.mk PYTHON_VERSIONS := $(shell py3versions --installed) -RUBY_VERSIONS := $(shell find /usr/bin/ -name 'ruby[12]*' \ - | xargs -n1 readlink -f | xargs -r -n1 basename) +RUBY_VERSIONS := $(shell dh_ruby --print-supported) LUA_VERSIONS:= $(shell find /usr/bin/ -name 'lua5.?' \ | xargs -n1 readlink -f | xargs -r -n1 basename) PHP_VERSIONS:= $(subst -config,,\ signature.asc Description: PGP signature
Bug#998449: autopkgtest: dh-golang-autopkgtest FAIL non-zero exit status 2
Source: libpod Version: 3.4.1+ds1-2 Severity: serious User: debian...@lists.debian.org Usertags: regression X-Debbugs-CC: debian...@lists.debian.org The libpod autopkgtest curently fails in unstable. I have seen #993532, but I don't know if it's the same issue. See the log below, slightly edited for brevity. Unfortunately there is zero diagnostics output, it just exits non-zero failing the test. Maybe this is something that could be improved in dh_golang_autopkgtest, I don't know. 8<8<8<- autopkgtest [08:39:48]: test dh-golang-autopkgtest: /usr/bin/dh_golang_autopkgtest autopkgtest [08:39:48]: test dh-golang-autopkgtest: [--- [info] Testing github.com/containers/podman... [info] Source code installed by binary package, overriding dh_auto_configure... dh build --buildsystem=golang --with=golang,bash-completion --builddirectory=_output dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_output dh_autoreconf -O--buildsystem=golang -O--builddirectory=_output debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' mkdir -p "_output" cp -a /usr/share/gocode/src "_output" make[1]: Leaving directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' debian/rules override_dh_auto_build make[1]: Entering directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' /usr/bin/make docs docker-docs make[2]: Entering directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' mkdir -p "/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/debian/tmp/go/src/github.com/containers" ln -sfn "/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp" "/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/debian/tmp/go/src/github.com/containers/podman" touch .gopathok if [ ! -x "/usr/bin/go-md2man" ]; then \ env GO111MODULE=off go get -u github.com/cpuguy83/go-md2man; \ fi mkdir -p docs/build/man (cd docs; ./dckrman.sh ./build/man/*.1) make[2]: Leaving directory '/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp' dh_auto_build -v --builddirectory=_output -- -tags "apparmor,ostree,seccomp,selinux,systemd" \ -ldflags "-X main.buildInfo=3.4.1+ds1-2" cd _output && go version go version go1.17.2 linux/amd64 cd _output && go env GO111MODULE="off" GOARCH="amd64" GOBIN="" GOCACHE="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/_output/go-build" GOENV="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/debian/.debhelper/generated/_source/home/.config/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE="" GOMODCACHE="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/_output/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp/_output" GOPRIVATE="" GOPROXY="off" GOROOT="/usr/lib/go-1.17" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/usr/lib/go-1.17/pkg/tool/linux_amd64" GOVCS="" GOVERSION="go1.17.2" GCCGO="gccgo" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="" CGO_CFLAGS="-g -O2 -ffile-prefix-map=/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp=. -fstack-protector-strong -Wformat -Werror=format-security" CGO_CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CGO_CXXFLAGS="-g -O2 -ffile-prefix-map=/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp=. -fstack-protector-strong -Wformat -Werror=format-security" CGO_FFLAGS="-g -O2 -ffile-prefix-map=/tmp/autopkgtest-lxc.yyi7s1c4/downtmp/autopkgtest_tmp=. -fstack-protector-strong" CGO_LDFLAGS="-Wl,-z,relro" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2850767338=/tmp/go-build -gno-record-gcc-switches" cd _output && go generate -v -tags apparmor,ostree,seccomp,selinux,systemd -ldflags "-X main.buildInfo=3.4.1+ds1-2" github.com/containers/podman/cmd/podman github.com/containers/podman/cmd/podman/common github.com/containers/podman/cmd/podman/completion github.com/containers/podman/cmd/podman/containers github.com/containers/podman/cmd/podman/diff github.com/containers/podman/cmd/podman/generate github.com/containers/podman/cmd/podman/healthcheck github.com/containers/podman/cmd/podman/images github.com/containers/podman/cmd/podman/inspect github.com/containers/podman/cmd/podman/machine github.com/containers/podman/cmd/podman/manifest github.com/containers/podman/cmd/podman/networks github.com/containers/podman/cmd/podman/parse github.com/containers/podman/cmd/podman/play github.com/containers/podman/cmd/podman/pods github.com/containers/podman/cmd/podman/registry github.com/containers/podman/cmd/podman/secrets github.com/containers/podman/cmd/podman/system github.com/containers/podman/cmd/podman/system/connection github.com/containers/podman/cmd/podman/utils github.com/containers/podman/cmd/podman/validate
Bug#998097: [DRE-maint] Bug#998097: ruby-eventmachine FTBFS on IPV6-only buildds and accesses the internet during the build
On Sat, Oct 30, 2021 at 11:53:46AM +0300, Adrian Bunk wrote: > Source: ruby-eventmachine > Severity: serious > Tags: ftbfs > > FTBFS on IPV6-only buildds: > > https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=amd64=1.3~pre20201020-b50c135-3=1633500476=0 > https://buildd.debian.org/status/fetch.php?pkg=ruby-eventmachine=i386=1.3~pre20201020-b50c135-4%2Bb1=1635578996=0 > > FTBFS due to attempted DNS: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-eventmachine.html > > ... > === > Failure: test_nameserver(TestResolver): >was expected to be kind_of? >but was > . > /build/1st/ruby-eventmachine-1.3~pre20201020-b50c135/tests/test_resolver.rb:19:in > `test_nameserver' > 16: end > 17: > 18: def test_nameserver > => 19: assert_kind_of(String, EM::DNS::Resolver.nameserver) > 20: end > 21: > 22: def test_nameservers > === > ... The ipv6-only thing is already worked around in 1.3~pre20201020-b50c135-4 by skipping the tests in those setups. Now, there is some type of weird issue with the test suite. It seems to fail randomly on some circumstances, which I could not pinpoint yet. e.g. I cannot reproduce the failures on a i386 chroot locally. signature.asc Description: PGP signature
Bug#998326: hub: git protocol not supported anymore
Package: hub Version: 2.14.2~ds1-1+b4 Severity: normal $ hub clone geemus/excon Cloning into 'excon'... fatal: remote error: The unauthenticated git protocol on port 9418 is no longer supported. Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information. The manpage mentions a way of switching to https, but using git:// as a default does not work anymore. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hub depends on: ii git1:2.33.0-1 ii libc6 2.32-4 Versions of packages hub recommends: ii xclip 0.13-2 ii xsel 1.2.0+git9bfc13d.20180109-3 hub suggests no packages. -- no debconf information signature.asc Description: PGP signature
Bug#995587: transition: ruby3.0-add
On Sat, Oct 30, 2021 at 11:43:35AM +0200, Sebastian Ramacher wrote: > Those have been scheduled. Note that a bunch of them have only built and > installed the extension for the default ruby version, e.g., > ruby-debug-inspector and libprelude. Yes. Please amend the ben file like this: is_affected = (.depends ~ /ruby2.7/ | .depends ~ /ruby3.0/) & ! .source ~ /^(ruby2\.7|ruby3\.0|ruby-defaults|dislocker|epic5|graphviz|hivex|kamailio|klayout|kross-interpreters|libprelude|marisa|ngraph-gtk|notmuch|obexftp|redland-bindings|rubyluabridge|ruby-standalone|subtle|subversion|uwsgi|vim-command-t|weechat|robot-testing-framework|treil|vim|nbdkit)$/ signature.asc Description: PGP signature
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
Control: reopen -1 Control: retitle -1 ruby3.0: Segmentation fault on ppc64el when compiled with gcc-11 Control: severity -1 important Hi, On Sat, Oct 30, 2021 at 08:50:10AM +0200, Lucas Nussbaum wrote: > Hi, > > On 30/10/21 at 00:13 +0200, Lucas Nussbaum wrote: > > Hi, > > > > ruby 3.0 3.0.2-4: > > - builds fine in Debian stable > > - fails in unstable > > - builds fine in unstable snapshotted on 20210930T210616Z > > - fails in unstable snapshotted on 20211014T215029Z > > I confirm that this is due to the switch from GCC 10 to GCC 11 in > gcc-defaults. > I wonder if this should be tracked separately and investigated, as it's > either a miscompilation issue in GCC 11, or a bug in Ruby 3.0... Yes. I think for now we can just reopen this bug. It would be nice to have a simpler/faster reproducer. but for now that is "revert the changes in 3.0.2-5 and do a build". signature.asc Description: PGP signature
Bug#961138: autodep8 uses host APT packages to generate dependencies for pkg-r-autopkgtest tests
On Fri, Oct 29, 2021 at 07:46:30AM +0200, Andreas Tille wrote: > Control: tags -1 help > > Hi, > > any hint from debian-ci list how to solve this? Quoting Paul from https://salsa.debian.org/ci-team/autodep8/-/merge_requests/10#note_279588, I think the right way to solve this is: > Maybe instead of querying, the code could just unconditionally add all > packages in the Suggests and for each add an alternative that's always > installed? I recall that apt will install the first alternative if it > easily can. signature.asc Description: PGP signature
Bug#991678: new upstream versions
On Fri, Oct 29, 2021 at 12:42:19AM +0200, Pierre-Elliott Bécue wrote: > reopen 991678 > notfixed 991678 1:4.0.10-1 > thanks > > Hi, > > Le vendredi 29 octobre 2021 à 00:31:06+0200, Diederik de Haas a écrit : > > Version: 1:4.0.10-1 > > > > On 30 Jul 2021 09:47:14 +0200 Harald Dunkel > > wrote: > > > Package: lxc > > > Version: 1:4.0.6-2 > > > Severity: wishlist > > > > > > Upstream provides a new version 4.0.10 and 4.0.9LTS, see > > > > Version 4.0.10-1 has been uploaded to the archives, thus closing this bug. > > Please before doing so, especially if you're not the bug submitter or a > maintainer of the package, consider carefully whether or not closing the > bug is appropriate. > > Here, the request is to provide lxc 4.0.10 in bullseye. While having it > in unstable is a requirement, this bug is not solved because it have > entered unstable. Yes, but are we really going to provide 4.0.10 _in bullseye_? signature.asc Description: PGP signature
Bug#995587: transition: ruby3.0-add
On Thu, Oct 28, 2021 at 11:34:28PM +0200, Sebastian Ramacher wrote: > Control: tags -1 confirmed > > On 2021-10-20 09:45:10 -0300, Antonio Terceiro wrote: > > Control: tag -1 - moreinfo > > > > On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote: > > > Control: tags -1 moreinfo > > > > > > On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote: > > > > Hi, > > > > > > > > On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote: > > > > > Package: release.debian.org > > > > > Severity: normal > > > > > User: release.debian@packages.debian.org > > > > > Usertags: transition > > > > > > > > > > We would like to add support for ruby3.0 in ruby-defaults. > > > > > > > > > > Ben file: > > > > > > > > > > title = "ruby3.0-add"; > > > > > is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source > > > > > ~ /^(ruby2.7|ruby3.0|ruby-defaults)$/); > > > > > is_good = .depends ~ /ruby3.0/; > > > > > is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/; > > > > > > > > > > We already did a mass rebuild some time ago, and the results don't > > > > > look > > > > > bad. We should be doing a new one soon, and will come up with a list > > > > > of > > > > > binNMUs > > > > > > > > This is a friendly ping. We would like to make the switch in unstable > > > > soon and start doing binNMUs. > > > > > > > > We have these bugs related to this transition: > > > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org > > > > > > > > Most of those bugs are for leaf libraries. We already started fixing the > > > > ones that block a lof of other (e.g. the ones with C extensions that > > > > FTBFS with ruby3.0) so they are ready to be binNMUed. > > > > > > ruby3.0 isn't in testing yet - it currently fails to build on ppc64el. > > > So let's at least wait until it migrated. > > > > ruby3.0 is now in testing. Can we go ahead with this? > > Yes, please go ahead Thanks, we will upload ruby-defaults shortly. Note that we do not necessarily want/need to block involved packages from migrating, as adding ruby3.0 support does not break anything since the default is still unchanged. signature.asc Description: PGP signature
Bug#998013: localslackirc: autopkgtest failure: Cannot find implementation or library stub for module named "typedload"
On Thu, Oct 28, 2021 at 03:39:25PM +0200, Paul Gevers wrote: > Source: localslackirc > Version: 1.13-1 > X-Debbugs-CC: debian...@lists.debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: fails-always > > Dear maintainer(s), > > You recently added an autopkgtest to your package localslackirc, great. > However, it fails. Currently this failure is blocking the migration to > testing [1]. Can you please investigate the situation and fix it? > > I copied some of the output at the bottom of this report. Seems your > missing some (test) dependencies? > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=localslackirc > > https://ci.debian.net/data/autopkgtest/testing/amd64/l/localslackirc/15955881/log.gz > > mypy --config-file mypy.conf *.py slackclient localslackirc > slackclient/client.py:28: error: Cannot find implementation or library > stub for module named "typedload" > slackclient/client.py:29: error: Cannot find implementation or library > stub for module named "websockets" > slackclient/client.py:30: error: Cannot find implementation or library > stub for module named "websockets.client" > slack.py:26: error: Cannot find implementation or library stub for > module named "typedload" > slack.py:26: note: See > https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports > Found 4 errors in 2 files (checked 9 source files) > make: *** [Makefile:6: lint] Error 1 > autopkgtest [15:36:30]: test command1 Also, this test is testing the source tree and not the installed package: | Test-Command: make test | Depends: mypy | Restrictions: allow-stderr signature.asc Description: PGP signature
Bug#996087: typeshed ready?
On Wed, Oct 27, 2021 at 02:52:53PM -0400, Antoine Beaupré wrote: > Hi! > > Update here, there's a package here made by terceiro: > > https://salsa.debian.org/terceiro/typeshed/ > > Reading this post: > > https://lists.debian.org/debian-python/2021/10/msg4.html > > it seems like the only concern remaining in this otherwise very useful > package is the question of licensing: > > https://github.com/typeshed-internal/stub_uploader/issues/31 > > ... which was just resolved upstream. > > So this is ready to go, I think. I'm using the package and it works > well! typeshed is waiting in NEW since the last Oct 16th. > lintian has the following complaints: > > E: python3-typeshed: python-package-missing-depends-on-python > E: typeshed source: python3-depends-but-no-python3-helper python3-typeshed > W: typeshed source: newer-standards-version 4.6.0.1 (current is 4.5.1) The first two are bogus, there is bug in lintian. signature.asc Description: PGP signature
Bug#997909: xapian-bindings: FTBFS with ruby3.0: diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or directory
Source: xapian-bindings Version: 1.4.18-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, xapian-bindings was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > make[7]: Entering directory '/<>/debian/build/ruby2.7/ruby' > rm -f > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.7.0/_xapian.la > make[7]: Leaving directory '/<>/debian/build/ruby2.7/ruby' > make[6]: Leaving directory '/<>/debian/build/ruby2.7/ruby' > make[5]: Leaving directory '/<>/debian/build/ruby2.7/ruby' > make[4]: Leaving directory '/<>/debian/build/ruby2.7/ruby' > make[3]: Leaving directory '/<>/debian/build/ruby2.7' > make[2]: Leaving directory '/<>/debian/build/ruby2.7' > # `created.rid` contains a timestamp making the build non-reproducible. > # It doesn't seem to be useful to install, so just delete it. > rm -f debian/tmp/usr/share/doc/xapian-bindings-ruby*/ruby/rdocs/created.rid > # We only need one xapian.rb for ruby-xapian, and it should be the same > # for all versions, so if present, check that the older versions are > # the same as the latest, then throw them away. Also, delete the older > # versions of the docs - the latest docs are installed by > # ruby-xapian.install. > rb=debian/tmp`/usr/bin/ruby3.0 -rrbconfig -e 'puts > RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \ > for v in 2.7; do \ > if [ "$v" != "3.0" ] ; then \ > set -e; \ > rb_old=debian/tmp`/usr/bin/ruby$v -rrbconfig -e 'puts > RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \ > diff "$rb_old" "$rb"; \ > rm -rf "$rb_old" debian/tmp/usr/share/doc/xapian-bindings-ruby$v; \ > fi; \ > done; \ > mv "$rb" debian/tmp/usr/lib/ruby/vendor_ruby > diff: debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or > directory > make[1]: *** [debian/rules:359: override_dh_auto_install] Error 2 The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/4/xapian-bindings/xapian-bindings_1.4.18-1+rebuild1635263761_amd64.build.txt signature.asc Description: PGP signature
Bug#997663: general: bullseye, system freezes completely when firefox freezes
On Sun, Oct 24, 2021 at 12:25:23PM +0200, jacobkoch...@gmail.com wrote: > Hello Stephan, > > > Possibly relevant: > > - Are you using X11 or Wayland? > Wayland > > > - Do you have proprietary graphics drivers installed? > $ lspci -v | grep -A 10 VGA > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 > (rev 02) (prog-if 00 [VGA controller]) > Subsystem: CLEVO/KAPOK Computer HD Graphics 620 > [...] > Kernel driver in use: i915 > Kernel modules: i915 > It seems to be the open source driver 'i915' in the package: > 'xserver-xorg-video-intel'. > > > - Does the freeze occur without those? > Does not apply. No proprietary graphics drivers installed. > > > - Can you SSH into the machine after the screen/input freezes > Interesting idea. I will install 'openssh-server' and try this the next > time. > > > - Do you have other indications that the machine is still working? > I'm not sure. Maybe I can try the keyboard backlight function? > Or the Fn+Special-Function-Keys like: Volume or Display-Brightness ? Does this only happen when on battery power? There is https://gitlab.freedesktop.org/drm/intel/-/issues/3510 which looks similar, and happens to me. signature.asc Description: PGP signature
Bug#996231: ruby-ftw: FTBFS: ERROR: Test "ruby2.7" failed: /<>/test/ftw/protocol.rb:19:in `test': wrong number of arguments (given 1, expected 2) (ArgumentError)
On Wed, Oct 20, 2021 at 06:28:09PM -0300, Lucas Kanashiro wrote: > I just uploaded version 0.0.44-2 to unstable and it built fine against both, > ruby2.7 and ruby3.0. Build log attached. did you forget to push to git? https://salsa.debian.org/ruby-team/ruby-ftw/-/commits/master does not have any recent commits. signature.asc Description: PGP signature
Bug#995587: transition: ruby3.0-add
On Wed, Oct 20, 2021 at 03:12:17PM +0200, Sebastiaan Couwenberg wrote: > On 10/20/21 2:45 PM, Antonio Terceiro wrote: > > On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote: > >> On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote: > >>> On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote: > >>>> Package: release.debian.org > >>>> Severity: normal > >>>> User: release.debian@packages.debian.org > >>>> Usertags: transition > >>>> > >>>> We would like to add support for ruby3.0 in ruby-defaults. > >>>> > >>>> Ben file: > >>>> > >>>> title = "ruby3.0-add"; > >>>> is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ > >>>> /^(ruby2.7|ruby3.0|ruby-defaults)$/); > >>>> is_good = .depends ~ /ruby3.0/; > >>>> is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/; > >>>> > >>>> We already did a mass rebuild some time ago, and the results don't look > >>>> bad. We should be doing a new one soon, and will come up with a list of > >>>> binNMUs > >>> > >>> This is a friendly ping. We would like to make the switch in unstable > >>> soon and start doing binNMUs. > >>> > >>> We have these bugs related to this transition: > >>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org > >>> > >>> Most of those bugs are for leaf libraries. We already started fixing the > >>> ones that block a lof of other (e.g. the ones with C extensions that > >>> FTBFS with ruby3.0) so they are ready to be binNMUed. > >> > >> ruby3.0 isn't in testing yet - it currently fails to build on ppc64el. > >> So let's at least wait until it migrated. > > > > ruby3.0 is now in testing. Can we go ahead with this? > > There are 169 packages affected by the transition according to the > tracker, the ruby3.0 usertag has 152 unresolved ftbfs bugreports. > > Does it really make sense to start this transition when most rdeps fail > to build? Yes. Those two sets of packages are more or less distinct. The only intersection is of packages that have C extensions (and thus a dependency on the specific ruby versions it was build against) *and* to build against ruby3.0. Most of the FTBFS bugs are against pure-Ruby packages that fail against ruby3.0, and are not even listed in the transition tracker. A good part of the packages that *are* listed in the transition will be good after a binNMU. To fix those we need to have ruby3.0 as a supported version in unstable in the first place. Also as we are "just" adding ruby3.0 support, this has little effect on users since ruby2.7 is still the default. signature.asc Description: PGP signature
Bug#995587: transition: ruby3.0-add
Control: tag -1 - moreinfo On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote: > Control: tags -1 moreinfo > > On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote: > > Hi, > > > > On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote: > > > Package: release.debian.org > > > Severity: normal > > > User: release.debian@packages.debian.org > > > Usertags: transition > > > > > > We would like to add support for ruby3.0 in ruby-defaults. > > > > > > Ben file: > > > > > > title = "ruby3.0-add"; > > > is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ > > > /^(ruby2.7|ruby3.0|ruby-defaults)$/); > > > is_good = .depends ~ /ruby3.0/; > > > is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/; > > > > > > We already did a mass rebuild some time ago, and the results don't look > > > bad. We should be doing a new one soon, and will come up with a list of > > > binNMUs > > > > This is a friendly ping. We would like to make the switch in unstable > > soon and start doing binNMUs. > > > > We have these bugs related to this transition: > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org > > > > Most of those bugs are for leaf libraries. We already started fixing the > > ones that block a lof of other (e.g. the ones with C extensions that > > FTBFS with ruby3.0) so they are ready to be binNMUed. > > ruby3.0 isn't in testing yet - it currently fails to build on ppc64el. > So let's at least wait until it migrated. ruby3.0 is now in testing. Can we go ahead with this? signature.asc Description: PGP signature
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
On Mon, Oct 18, 2021 at 01:22:25PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/18/21 13:16, Antonio Terceiro wrote:
> > I don't think we are on the right track here. I need to read the failing
> > test correctly. this "test case" alone is bogus, as
> >
> > ruby -e 'END {Process.kill :SEGV, $$}'
> >
> > is _expected_ to segfault, i.e. the process is sending a SEGV signal to
> > itself. This test case is not complete.
Those tests pass on the upstream master branch, but I couldn't really
bisect the issue due to other build failures in the intermediary
commits.
In the end I "solved" this particular issue by skipping the tests that
cause that failure. I'm not really happy about that, but the other 21k+
tests pass so I guess I will have to live with it.
> It might be an idea to look at the Fedora package:
>
> > https://src.fedoraproject.org/rpms/ruby/blob/rawhide/f/ruby.spec
>
> It has a number of patches against 3.x:
>
> > https://src.fedoraproject.org/rpms/ruby/tree/rawhide
>
> It builds fine on ppc64el:
>
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=1801321
The test run here runs less tests than we do so I assume there's also a
skip list somewhere.
> OTOH, ruby3.0 builds fine in openSUSE Factory on ppc64el, but they're still at
> version 3.0.1, so it might be an issue that will only show with 3.0.2?
>
> > https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/ruby3.0
the build log for ppc64el also has Segmentation faults, that I assume is
not being considered fatal.
Thanks for your help.
signature.asc
Description: PGP signature
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
On Mon, Oct 18, 2021 at 12:59:35PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/18/21 12:51, Antonio Terceiro wrote:
> >> So, we need a backtrace to see where the crash actually happens. I assume
> >> it's in one
> >> of the build dependencies.
> >
> > it happens in glibc:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x77a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6
>
> Hmm, both were built with glibc 2.32-4.
I don't think we are on the right track here. I need to read the failing
test correctly. this "test case" alone is bogus, as
ruby -e 'END {Process.kill :SEGV, $$}'
is _expected_ to segfault, i.e. the process is sending a SEGV signal to
itself. This test case is not complete.
signature.asc
Description: PGP signature
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
On Mon, Oct 18, 2021 at 10:00:42AM +0200, John Paul Adrian Glaubitz wrote: > Hello! > > On 10/17/21 21:50, John Paul Adrian Glaubitz wrote: > > Ah, so the last successful build was 3.0.2-2 and the first failure was in > > 3.0.2-3, > > the only difference being the mipsel patch to fix an unaligned access. > > > > However, 3.0.2-2 was built with gcc-10: > > > >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0=ppc64el=3.0.2-2=1633362713=0 > > > > while 3.0.2-3 was built with gcc-11: > > > >> https://buildd.debian.org/status/fetch.php?pkg=ruby3.0=ppc64el=3.0.2-3=1634169532=0 > > > > So, first we should try building with gcc-10 and see if that makes a > > difference. > > I have tested the build with gcc-10 but the problem remains, so it's not a > compiler > issue. Dropping the patch rand_init-fix-off-by-one-error.patch that was > introduced > with 3.0.2-3 doesn't help either. > > So, we need a backtrace to see where the crash actually happens. I assume > it's in one > of the build dependencies. it happens in glibc: Program received signal SIGSEGV, Segmentation fault. 0x77a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6 #0 0x77a48f04 in kill () from /lib/powerpc64le-linux-gnu/libc.so.6 #1 0x00010023a8ec in rb_f_kill (argc=, argv=) at signal.c:481 #2 0x0001001d0608 in proc_rb_f_kill (c=, v=, _=) at process.c:8605 #3 0x0001002bd848 in ractor_safe_call_cfunc_m1 (recv=, argc=, argv=, func=) at vm_insnhelper.c:2736 #4 0x0001002d2e6c in vm_call_cfunc_with_frame (ec=0x100453ad0, reg_cfp=0x779effa0, calling=) at vm_insnhelper.c:2926 #5 0x0001002d5bb4 in vm_sendish (ec=0x100453ad0, reg_cfp=0x779effa0, cd=0x1005a0960, block_handler=, method_explorer=) at vm_callinfo.h:336 #6 0x0001002da06c in vm_exec_core (ec=0x100453ad0, initial=, initial@entry=0) at insns.def:789 #7 0x0001002dfcb0 in rb_vm_exec (ec=0x100453ad0, mjit_enable_p=) at vm.c:2172 #8 0x0001002e5d7c in invoke_block (captured=, captured=, opt_pc=, type=, cref=0x0, self=4300276880, iseq=0x10046a478, ec=0x100453ad0) at vm.c:1263 #9 invoke_iseq_block_from_c (me=0x0, is_lambda=0, cref=0x0, passed_block_handler=0, kw_splat=0, argv=0x10046a280, argc=0, self=4300276880, captured=, ec=0x100453ad0) at vm.c:1335 #10 invoke_block_from_c_proc (me=0x0, is_lambda=, passed_block_handler=0, kw_splat=0, argv=0x10046a280, argc=0, self=4300276880, proc=, ec=0x100453ad0) at vm.c:1435 #11 vm_invoke_proc (ec=0x100453ad0, proc=, self=4300276880, argc=, argv=0x10046a280, kw_splat=, passed_block_handler=0) at vm.c:1464 #12 0x0001001c8ffc in rb_proc_call (self=, args=) at proc.c:986 #13 0x0001000c9cb0 in rb_call_end_proc (data=4299596440) at eval_jump.c:13 #14 0x0001000c9d64 in exec_end_procs_chain (procs=procs@entry=0x10043a750 , errp=errp@entry=0x100453b48) at eval_jump.c:105 #15 0x0001000cf9fc in rb_ec_exec_end_proc (ec=ec@entry=0x100453ad0) at eval_jump.c:120 #16 0x0001000cfd84 in rb_ec_teardown (ec=ec@entry=0x100453ad0) at eval.c:175 #17 0x0001000d0068 in rb_ec_cleanup (ec=ec@entry=0x100453ad0, ex=) at eval.c:243 #18 0x0001000d0598 in ruby_run_node (n=0x10046a5b8) at eval.c:375 #19 0x00010002aaa8 in main (argc=, argv=) at ./main.c:50 signature.asc Description: PGP signature
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
Source: ruby3.0
Version: 3.0.2-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
X-Debbugs-CC: debian-powe...@lists.debian.org
I'm copying the debian-powerpc list to see if anyone can help.
ruby3.0 fails to build on ppc64el. 4 test cases results in Segmentation
faults.
I was able to reproduce this on the porter box, and the minimal test
case, inside a build source tree, is this:
./miniruby -e 'END {Process.kill :SEGV, $$}'
The actual build failures are:
> 1) Failure:
> TestBugReporter#test_bug_reporter_add
> [/<>/test/-ext-/bug_reporter/test_bug_reporter.rb:24]:
> pid 111637 killed by SIGSEGV (signal 11)
> | -:1: [BUG] Segmentation fault at 0x0b880001b415
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> |
> | -- Control frame information ---
> | c:0003 p: s:0012 e:11 CFUNC :kill
> | c:0002 p:0021 s:0006 e:05 EVAL -:1 [FINISH]
> | c:0001 p: s:0003 E:c0 (none) [FINISH]
> |
> | -- Ruby level backtrace information
> | -:1:in `'
> | -:1:in `kill'
> |
> | -- C level backtrace information ---
> .
>
> 1. [2/2] Assertion for "stderr"
>| Expected /Sample bug reporter: 12345/
>| to match
>| "-- Control frame information
> ---\n"+
>| "c:0003 p: s:0012 e:11 CFUNC :kill\n"+
>| "c:0002 p:0021 s:0006 e:05 EVAL -:1 [FINISH]\n"+
>| "c:0001 p: s:0003 E:c0 (none) [FINISH]\n\n"+
>| "-- Ruby level backtrace information
> \n"+
>| "-:1:in `'\n"+
>| "-:1:in `kill'\n\n"+
>| "-- C level backtrace information
> ---\n"
>| after 4 patterns with 125 characters.
>
> 2) Failure:
> TestRubyOptions#test_segv_loaded_features
> [/<>/test/ruby/test_rubyoptions.rb:757]:
> pid 119318 killed by SIGSEGV (signal 11)
> | -e:1: [BUG] Segmentation fault at 0x0b880001d216
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> |
> | -- Control frame information ---
> | c:0003 p: s:0012 e:11 CFUNC :kill
> | c:0002 p:0016 s:0006 e:05 BLOCK -e:1 [FINISH]
> | c:0001 p: s:0003 E:001240 (none) [FINISH]
> |
> | -- Ruby level backtrace information
> | -e:1:in `block in '
> | -e:1:in `kill'
> |
> | -- C level backtrace information ---
> .
>
> 1. [2/2] Assertion for "stderr"
>| <""> expected but was
>| <"-- C level backtrace information
> ---\n">.
>
> 3) Failure:
> TestRubyOptions#test_segv_setproctitle
> [/<>/test/ruby/test_rubyoptions.rb:771]:
> pid 119319 killed by SIGSEGV (signal 11)
> | -e:1: [BUG] Segmentation fault at 0x0b880001d217
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> |
> | -- Control frame information ---
> | c:0003 p: s:0012 e:11 CFUNC :kill
> | c:0002 p:0029 s:0006 e:05 EVAL -e:1 [FINISH]
> | c:0001 p: s:0003 E:001a80 (none) [FINISH]
> |
> | -- Ruby level backtrace information
> | -e:1:in `'
> | -e:1:in `kill'
> |
> | -- C level backtrace information ---
> .
>
> 1. [2/2] Assertion for "stderr"
>| <""> expected but was
>| <"-- C level backtrace information
> ---\n">.
>
> 4) Failure:
> TestRubyOptions#test_segv_test
> [/<>/test/ruby/test_rubyoptions.rb:751]:
> pid 119320 killed by SIGSEGV (signal 11)
> | -e:1: [BUG] Segmentation fault at 0x0b880001d218
> | ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [powerpc64le-linux-gnu]
> |
> | -- Control frame information ---
> | c:0003 p: s:0012 e:11 CFUNC :kill
> | c:0002 p:0015 s:0006 e:05 EVAL -e:1 [FINISH]
> | c:0001 p: s:0003 E:001870 (none) [FINISH]
> |
> | -- Ruby level backtrace information
> | -e:1:in `'
> | -e:1:in `kill'
> |
> | -- C level backtrace information ---
> .
>
> 1. [2/2] Assertion for "stderr"
>| <""> expected but was
>| <"-- C level backtrace information
> ---\n">.
>
> Finished tests in 784.310094s, 26.8248 tests/s, 3410.9162 assertions/s.
> 21039 tests, 2675216 assertions, 4 failures, 0 errors, 107 skips
>
> ruby -v: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233)
> [powerpc64le-linux-gnu]
> make[2]: *** [uncommon.mk:800: yes-test-all] Error 4
The full build log is available from:
http://qa-logs.debian.net/2021/10/17/ruby3.0.log
A list of current common problems and possible solutions is available at
Bug#996621: ruby-enumerable-statistics: FTBFS on i386: ERROR: Test "ruby2.7" failed: Failure/Error: it { is_expected.to eq(x) }
Source: ruby-enumerable-statistics
Version: 2.0.7+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Forwarded: https://github.com/mrkn/enumerable-statistics/issues/31
This is caused by the test suite comparing floating point numbers for
equality, what is not really feasible. This has been forwarded upstream.
Relevant part (hopefully):
> Failure/Error: it { is_expected.to eq(x) }
>
>expected: 833.5
> got: 833.3
>
>(compared using ==)
> # /<>/spec/support/macros.rb:48:in `block in
> it_equals_with_type'
>
> Top 10 slowest examples (0.06033 seconds, 23.2% of total time):
> Array#histogram with 10,000 normal random values closed: :right is expected
> to eq false
> 0.01933 seconds /<>/spec/histogram/array_spec.rb:179
> Array#histogram with 10,000 normal random values default is expected to eq
> false
> 0.01272 seconds /<>/spec/histogram/array_spec.rb:164
> Enumerable#mean for [1.0e-09, (1/1), 1.0e-09, 1.0e-09, 1.0e-09,
> 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09].each is
> expected to eq 833.5
> 0.0115 seconds /<>/spec/support/macros.rb:48
> Array#histogram with 10,000 normal random values nbins: 5 is expected to eq
> false
> 0.01132 seconds /<>/spec/histogram/array_spec.rb:194
> Array#percentile for [1, nil, 3] is expected to match [(be nan), (be nan)]
> 0.00163 seconds /<>/spec/percentile/array_spec.rb:57
> Enumerable#variance for [].each with a conversion block does not call the
> block
> 0.00155 seconds /<>/spec/enum_spec.rb:80
> Array#percentile for [] is expected to raise ArgumentError
> 0.00093 seconds /<>/spec/percentile/array_spec.rb:10
> Hash#value_counts with normalize: false, sort: false, ascending: true,
> dropna: false pairs
> 0.00051 seconds /<>/spec/value_counts_spec.rb:60
> Array#value_counts with normalize: false, sort: false, ascending: false,
> dropna: true pairs
> 0.00046 seconds /<>/spec/value_counts_spec.rb:60
> Hash#sum for {:a=>3, :b=>(5/1), :c=>7.0} with conversion `(k, v) -> v` is
> expected to eq 15.0
> 0.00036 seconds /<>/spec/support/macros.rb:48
>
> Top 10 slowest example groups:
> Array#histogram
> 0.00333 seconds average (0.0533 seconds / 16 examples)
> /<>/spec/histogram/array_spec.rb:4
> Array#percentile
> 0.00088 seconds average (0.00706 seconds / 8 examples)
> /<>/spec/percentile/array_spec.rb:3
> Enumerable
> 0.00066 seconds average (0.02103 seconds / 32 examples)
> /<>/spec/value_counts_spec.rb:101
> Enumerable
> 0.00062 seconds average (0.05612 seconds / 90 examples)
> /<>/spec/enum_spec.rb:5
> Hash
> 0.00055 seconds average (0.02386 seconds / 43 examples)
> /<>/spec/hash_spec.rb:5
> Hash
> 0.00051 seconds average (0.0163 seconds / 32 examples)
> /<>/spec/value_counts_spec.rb:83
> Array
> 0.00048 seconds average (0.04351 seconds / 90 examples)
> /<>/spec/array_spec.rb:5
> Array
> 0.00048 seconds average (0.0154 seconds / 32 examples)
> /<>/spec/value_counts_spec.rb:69
> Enumerable
> 0.00046 seconds average (0.01423 seconds / 31 examples)
> /<>/spec/range_spec.rb:5
> Array#median
> 0.00044 seconds average (0.00701 seconds / 16 examples)
> /<>/spec/median/array_spec.rb:3
>
> Finished in 0.25997 seconds (files took 2.11 seconds to load)
> 390 examples, 2 failures
>
> Failed examples:
>
> rspec '/<>/spec/enum_spec.rb[1:1:8:2]' # Enumerable#mean for
> [1.0e-09, (1/1), 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09,
> 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09].each is expected to eq
> 833.5
> rspec '/<>/spec/array_spec.rb[1:1:8:2]' # Array#mean for
> [1.0e-09, (1/1), 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09,
> 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09, 1.0e-09] is expected to eq
> 833.5
>
> Randomized with seed 58835
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed:
signature.asc
Description: PGP signature
Bug#995587: transition: ruby3.0-add
Hi, On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > We would like to add support for ruby3.0 in ruby-defaults. > > Ben file: > > title = "ruby3.0-add"; > is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ > /^(ruby2.7|ruby3.0|ruby-defaults)$/); > is_good = .depends ~ /ruby3.0/; > is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/; > > We already did a mass rebuild some time ago, and the results don't look > bad. We should be doing a new one soon, and will come up with a list of > binNMUs This is a friendly ping. We would like to make the switch in unstable soon and start doing binNMUs. We have these bugs related to this transition: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org Most of those bugs are for leaf libraries. We already started fixing the ones that block a lof of other (e.g. the ones with C extensions that FTBFS with ruby3.0) so they are ready to be binNMUed. signature.asc Description: PGP signature
Bug#996530: yard: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick
Source: yard Version: 0.9.24-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, yard was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > cannot load such file -- webrick > # ./lib/yard/server/webrick_adapter.rb:2:in `' > # ./spec/server/webrick_servlet_spec.rb:4:in `' > > Top 0 slowest examples (0 seconds, 0.0% of total time): > > Finished in 0.0001 seconds (files took 0.90378 seconds to load) > 0 examples, 0 failures, 2 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit build dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/yard/yard_0.9.24-1+rebuild1633401329_amd64.build.txt signature.asc Description: PGP signature
Bug#996529: vagrant: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:
Source: vagrant
Version: 2.2.14+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, vagrant was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> RuntimeError:
>class variable access from toplevel
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:10:in
> `block (3 levels) in '
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `initialize'
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `new'
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:9:in
> `block (2 levels) in '
> #
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:34:in
> `block (4 levels) in '
>
> Finished in 14 minutes 32 seconds (files took 5.03 seconds to load)
> 2824 examples, 7 failures, 9 pending
>
> Failed examples:
>
> rspec
> /<>/test/unit/plugins/commands/cloud/provider/upload_test.rb:88
> #
> VagrantPlugins::CloudCommand::ProviderCommand::Command::Upload#upload_provider
> with direct option should use direct upload
> rspec /<>/test/unit/plugins/commands/cloud/search_test.rb:59 #
> VagrantPlugins::CloudCommand::Command::Search#search with valid options
> should use options when performing search
> rspec /<>/test/unit/plugins/commands/cloud/search_test.rb:72 #
> VagrantPlugins::CloudCommand::Command::Search#search with valid options with
> invalid options should only pass supported options to search
> rspec /<>/test/unit/plugins/kernel_v2/config/disk_test.rb:120 #
> VagrantPlugins::Kernel_V2::VagrantConfigDisk#add_provider_config normalizes
> provider config
> rspec
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:21
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with no
> override should split options into individual options
> rspec
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:28
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with
> overrides should merge all options
> rspec
> /<>/test/unit/plugins/synced_folders/unix_mount_helpers_test.rb:33
> # VagrantPlugins::SyncedFolder::UnixMountHelpers.merge_mount_options with
> overrides should override options defined in base
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern test/unit/\{plugins\}/\*\*/\*_test.rb --exclude-pattern
> \{test/unit/vagrant/action/builtin/box_add_test.rb,test/unit/plugins/communicators/winrm/\*_test.rb,test/unit/plugins/pushes/ftp/\*_test.rb\}
> -I/<>/debian/lib failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/vagrant/vagrant_2.2.14+dfsg-1+rebuild1633400150_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996528: test-kitchen: FTBFS: ERROR: Test "ruby2.7" failed: Could not find 'thor' (~> 0.19) among 87 total gem(s) (Gem::MissingSpecError)
Source: test-kitchen Version: 1.23.2-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, test-kitchen was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block > in activate_dependencies': Could not find 'thor' (~> 0.19) among 87 total > gem(s) (Gem::MissingSpecError) > Checked in > 'GEM_PATH=/<>/debian/test-kitchen/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > at: > /<>/debian/test-kitchen/usr/share/rubygems-integration/all/specifications/test-kitchen-1.23.2.gemspec, > execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not > find 'thor' (~> 0.19) - did find: [thor-1.0.1] (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/test-kitchen/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' > , execute `gem env` for more information > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block > in activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in > `activate_dependencies' > from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in > `activate' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `block in gem' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `synchronize' > from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in > `gem' > from -e:1:in `' > aruba (1.0.4) > bcrypt_pbkdf (1.1.0) > benchmark (default: 0.1.0) > bigdecimal (default: 2.0.0) > builder (3.2.4) > bundler (default: 2.1.4) > cgi (default: 0.1.0) > chef-utils (16.12.3) > childprocess (4.1.0) > coderay (1.1.3) > contracts (0.16.0) > csv (default: 3.1.2) > cucumber (2.4.0) > cucumber-core (1.5.0) > cucumber-wire (0.0.1) > date (default: 3.0.0) > dbm (default: 1.1.0) > delegate (default: 0.1.0) > did_you_mean (default: 1.4.0) > diff-lcs (1.4.4) > ed25519 (1.2.4) > etc (default: 1.1.0) > fakefs (1.2.0) > fcntl (default: 1.0.0) > ffi (1.12.2) > fiddle (default: 1.0.0) > fileutils (default: 1.4.1) > forwardable (default: 1.3.1) > gdbm (default: 2.1.0) > getoptlong (default: 0.1.0) > gherkin (4.0.0) > io-console (default: 0.5.6) > ipaddr (default: 1.2.2) > irb (default: 1.2.6) > json (default: 2.3.0) > logger (default: 1.4.2) > matrix (default: 0.2.0) > metaclass (0.0.4) > method_source (1.0.0) > minitest (5.13.0) > mixlib-install (3.11.7) > mixlib-shellout (3.2.5) > mixlib-versioning (1.1.0) > mocha (1.7.0) > multi_json (1.14.1) > multi_test (0.1.2) > mutex_m (default: 0.1.0) > net-pop (default: 0.1.0) > net-scp (3.0.0) > net-smtp (default: 0.1.0) > net-ssh (6.1.0) > net-ssh-gateway (2.0.0) > net-telnet (0.1.1) > observer (default: 0.1.0) > open3 (default: 0.1.0) > openssl (default: 2.1.2) > ostruct (default: 0.2.0) > power_assert (1.1.7) > prime (default: 0.1.1) > pry (0.13.1) > pstore (default: 0.1.0) > psych (default: 3.1.0) > racc (default: 1.4.16) > rake (13.0.3) > rdoc (default: 6.2.1.1) > readline (default: 0.0.2) > readline-ext (default: 0.1.0) > reline (default: 0.1.5) > rexml (default: 3.2.3.1) > rspec-expectations (3.9.2) > rspec-support (3.9.3) > rss (default: 0.2.8) > rubygems-update (3.2.27) > sdbm (default: 1.0.0) > singleton (default: 0.1.0) > stringio (default: 0.1.0) > strscan (default: 1.0.3) > test-unit (3.3.9) > thor (1.0.1) > timeout (default: 0.1.0) > tracer (default: 0.1.0) > uri (default: 0.10.0) > webrick
Bug#996527: sup-mail: FTBFS: ERROR: Test "ruby2.7" failed: NameError: uninitialized constant ActiveSupport
Source: sup-mail Version: 1.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, sup-mail was found to fail to build in that situation. This seems unrelated to ruby3.0, since the ruby2.7 tests already fail. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rb > │ > └──┘ > > RUBYLIB=/<>/debian/sup-mail/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/sup-mail/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 debian/ruby-tests.rb > tput: No value for $TERM and no -T specified > tput: No value for $TERM and no -T specified > Some YAML tests are skipped on Ruby 2.1.0 and newer. > Run options: --seed 8439 > > # Running: > > [2021-10-05 02:07:09 +] WARNING: URI.escape is obsolete > [2021-10-05 02:07:09 +] WARNING: found invalid date in potential mbox > split line, not splitting: "From sea to shining sea\n" > [2021-10-05 02:07:09 +] WARNING: found invalid date in potential mbox > split line, not splitting: "From b...@bob.com I get only spam.\n" > ..[2021-10-05 02:07:09 +] WARNING: URI.escape is obsolete > .[2021-10-05 02:07:09 +] WARNING: DEPRECATED: Use assert_nil if expecting > nil from /<>/test/test_header_parsing.rb:72. This will fail in > Minitest 6. > E/usr/bin/which: this version of `which' is deprecated; use `command -v' > in scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > ./usr/bin/which: this version of `which' is deprecated; use `command -v' in > scripts instead. > [2021-10-05 02:07:09 +] WARNING: No crypto set up, crypto will not be > tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent > running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] > .[2021-10-05 02:07:09 +] WARNING: problem reading message > sup-faked-df001467cbd7d1c987812838111e7731 > [2021-10-05 02:07:09 +] WARNING: Message is in sup-test://test_messages > at 0 > ..[2021-10-05 02:07:09 +] WARNING: problem reading message > sup-faked-b4f27f6a974091c7c1c67484b827eb61 > [2021-10-05 02:07:09 +] WARNING: Message is in sup-test://test_messages > at 0 > . > > Finished in 0.164684s, 176.0946 runs/s, 613.2951 assertions/s. > > 1) Error: > Redwood::TestYamlRegressions#test_yamling_hash: > NameError: uninitialized constant ActiveSupport > /usr/lib/ruby/vendor_ruby/rr/integrations/minitest_4.rb:48:in `block (2 > levels) in hook' > /usr/lib/ruby/vendor_ruby/rr/integrations/minitest_4.rb:56:in `block (2 > levels) in hook' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:96: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' >
Bug#996526: rubygems: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: rubygems Version: 3.2.27-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, rubygems was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"rubygems-update\" > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"bundler\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-bundler/usr/share/rubygems-integration/all:/<>/debian/ruby-rubygems/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > > File does not exist: webrick > > rake aborted! > Command failed with status (1) > > Tasks: TOP => default => test > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit build dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/rubygems/rubygems_3.2.27-1+rebuild1633399251_amd64.build.txt signature.asc Description: PGP signature
Bug#996525: ruby-xmlrpc: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-xmlrpc Version: 0.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-xmlrpc was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-xmlrpc/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"xmlrpc\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-xmlrpc/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-xmlrpc/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_client.rb" "test/test_cookie.rb" "test/test_datetime.rb" > "test/test_features.rb" "test/test_helper.rb" "test/test_marshal.rb" > "test/test_parser.rb" "test/test_webrick_server.rb" "test/test_xmlrpc.rb" -v > > File does not exist: webrick > > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_client.rb" "test/test_cookie.rb" "test/test_datetime.rb" > "test/test_features.rb" "test/test_helper.rb" "test/test_marshal.rb" > "test/test_parser.rb" "test/test_webrick_server.rb" "test/test_xmlrpc.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit build dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-xmlrpc/ruby-xmlrpc_0.3.0-2+rebuild1633399041_amd64.build.txt signature.asc Description: PGP signature
Bug#996524: ruby-whitequark-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-whitequark-parser Version: 2.7.1.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-whitequark-parser was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-whitequark-parser/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"parser\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-whitequark-parser/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_ast_processor.rb" "test/test_base.rb" "test/test_current.rb" > "test/test_diagnostic.rb" "test/test_diagnostic_engine.rb" > "test/test_encoding.rb" "test/test_lexer.rb" "test/test_lexer_stack_state.rb" > "test/test_meta.rb" "test/test_parse_helper.rb" "test/test_parser.rb" > "test/test_runner_parse.rb" "test/test_runner_rewrite.rb" > "test/test_source_buffer.rb" "test/test_source_comment.rb" > "test/test_source_comment_associator.rb" "test/test_source_map.rb" > "test/test_source_range.rb" "test/test_source_rewriter.rb" > "test/test_source_rewriter_action.rb" "test/test_source_tree_rewriter.rb" > "test/test_static_environment.rb" -v > warning: parser/current is loading parser/ruby27, which recognizes > warning: 2.7.x-compliant syntax, but you are running 3.0.2. > warning: please see > https://github.com/whitequark/parser#compatibility-with-ruby-mri. > Run options: -v --seed 1073 > > # Running: > > TestSourceTreeRewriter#test_empty = 0.00 s = . > TestSourceTreeRewriter#test_insert_after = 0.00 s = . > TestSourceTreeRewriter#test_inserts_on_empty_ranges = 0.07 s = . > TestSourceTreeRewriter#test_replace = 0.00 s = . > TestSourceTreeRewriter#test_ordered_replacements = 0.00 s = . > TestSourceTreeRewriter#test_swallowed_insertions = 0.00 s = . > TestSourceTreeRewriter#test_merge = 0.02 s = . > TestSourceTreeRewriter#test_nested_actions = 0.00 s = . > TestSourceTreeRewriter#test_insert_before = 0.00 s = . > TestSourceTreeRewriter#test_replace_same_range = 0.00 s = . > TestSourceTreeRewriter#test_crossing_non_deletions = 0.00 s = . > TestSourceTreeRewriter#test_multiple_actions = 0.00 s = . > TestSourceTreeRewriter#test_out_of_range_ranges = 0.00 s = . > TestSourceTreeRewriter#test_remove = 0.00 s = . > TestSourceTreeRewriter#test_crossing_deletions = 0.00 s = . > TestSourceTreeRewriter#test_wrap = 0.00 s = . > TestSourceTreeRewriter#test_wraps_same_range = 0.00 s = . > TestParser#test_beginless_range_before_27 = 0.00 s = . > TestParser#test_comments_before_leading_dot__27 = 0.00 s = . > TestParser#test_parser_bug_490 = 0.06 s = . > TestParser#test_asgn_cmd = 0.01 s = . > TestParser#test_bug_435 = 0.01 s = . > TestParser#test_hash_label_end = 0.02 s = . > TestParser#test_masgn_const = 0.02 s = . > TestParser#test_send_lambda_args_shadow = 0.01 s = . > TestParser#test_resbody_list = 0.01 s = . > TestParser#test_space_args_star = 0.00 s = . > TestParser#test_non_lvar_injecting_match = 0.01 s = . > TestParser#test_op_asgn = 0.02 s = . > TestParser#test_until = 0.02 s = . > TestParser#test_next_block = 0.01 s = . > TestParser#test_ruby_bug_11990 = 0.00 s = . > TestParser#test_cond_match_current_line = 0.02 s = . > TestParser#test_rescue_mod = 0.01 s = . > TestParser#test_array_words = 0.01 s = . > TestParser#test_emit_arg_inside_procarg0_legacy = 0.01 s = . > TestParser#test_send_plain_cmd_ambiguous_literal = 0.01 s = . > TestParser#test_numbered_and_ordinary_parameters = 0.03 s = . >
Bug#996523: ruby-websocket: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick
Source: ruby-websocket Version: 1.2.8-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-websocket was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > cannot load such file -- webrick > # ./spec/support/all_server_drafts.rb:3:in `' > # ./spec/spec_helper.rb:6:in `block in ' > # ./spec/spec_helper.rb:6:in `each' > # ./spec/spec_helper.rb:6:in `' > # ./spec/handshake/server_76_spec.rb:3:in `' > No examples found. > > Finished in 0.5 seconds (files took 1.11 seconds to load) > 0 examples, 0 failures, 20 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-websocket/ruby-websocket_1.2.8-2+rebuild1633398813_amd64.build.txt signature.asc Description: PGP signature
Bug#996522: ruby-vips: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-vips Version: 2.0.17-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-vips was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: >tried to create Proc object without a block > # ./lib/vips/object.rb:269:in `new' > # ./lib/vips/object.rb:269:in `signal_connect' > # ./lib/vips/targetcustom.rb:60:in `on_write' > # ./spec/connection_spec.rb:155:in `block (2 levels) in ' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:257:in > `instance_exec' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:257:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:503:in > `block in with_around_and_singleton_context_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:460:in > `block in with_around_example_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/hooks.rb:481:in > `block in run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/hooks.rb:619:in > `run_around_example_hooks_for' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/hooks.rb:481:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:460:in > `with_around_example_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:503:in > `with_around_and_singleton_context_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example.rb:254:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:644:in > `block in run_examples' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:640:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:640:in > `run_examples' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/example_group.rb:606:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:121:in > `block (3 levels) in run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:121:in > `map' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:121:in > `block (2 levels) in run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2058:in > `with_suite_hooks' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:116:in > `block in run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/reporter.rb:74:in > `report' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:115:in > `run_specs' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:89:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:71:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:45:in > `invoke' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec:4:in > `' > > Finished in 0.88878 seconds (files took 0.23373 seconds to load) > 91 examples, 3 failures > > Failed examples: > > rspec ./spec/connection_spec.rb:118 # Vips::SourceCustom can load a custom > source > rspec ./spec/connection_spec.rb:132 # Vips::SourceCustom on_seek is optional > rspec ./spec/connection_spec.rb:151 # Vips::SourceCustom can write an image > to a user output stream > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --backtrace -r ./spec/spec_helper.rb failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-vips/ruby-vips_2.0.17-1+rebuild1633398529_amd64.build.txt signature.asc Description: PGP signature
Bug#996521: ruby-vcr: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick
Source: ruby-vcr Version: 6.0.0+really5.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-vcr was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > cannot load such file -- webrick > # /<>/spec/support/vcr_localhost_server.rb:2:in ` (required)>' > # /<>/spec/spec_helper.rb:14:in `require_relative' > # /<>/spec/spec_helper.rb:14:in `' > # /<>/spec/lib/vcr_spec.rb:1:in `' > > Finished in 0.7 seconds (files took 2.17 seconds to load) > 0 examples, 0 failures, 22 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-vcr/ruby-vcr_6.0.0+really5.0.0-1+rebuild1633398432_amd64.build.txt signature.asc Description: PGP signature
Bug#996520: ruby-varia-model: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: expect(subject.to_json).to eql(JSON.dump(first_name: "brooke", nick: "leblanc"))
Source: ruby-varia-model
Version: 0.6.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-varia-model was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: expect(subject.to_json).to eql(JSON.dump(first_name:
> "brooke", nick: "leblanc"))
>
>expected: "{\"first_name\":\"brooke\",\"nick\":\"leblanc\"}"
> got:
> "{\"first_name\":\"brooke\",\"nick\":\"leblanc\",\"json_class\":\"Playa\"}"
>
>(compared using eql?)
> # ./spec/unit/varia_model_spec.rb:665:in `block (4 levels) in (required)>'
>
> Finished in 0.2 seconds (files took 0.81399 seconds to load)
> 68 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/unit/varia_model_spec.rb:661 # VariaModel#to_json when
> JSON.create_id is nil does not include a nil key
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-varia-model/ruby-varia-model_0.6.0-1+rebuild1633398422_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996519: ruby-vagrant-cloud: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-vagrant-cloud Version: 3.0.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-vagrant-cloud was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 1, expected 0) > # ./lib/vagrant_cloud/data.rb:217:in `initialize' > # ./lib/vagrant_cloud/box.rb:21:in `initialize' > # ./lib/vagrant_cloud/response/search.rb:57:in `new' > # ./lib/vagrant_cloud/response/search.rb:57:in `block in reload_boxes' > # ./lib/vagrant_cloud/response/search.rb:51:in `map' > # ./lib/vagrant_cloud/response/search.rb:51:in `reload_boxes' > # ./lib/vagrant_cloud/response/search.rb:18:in `initialize' > # ./spec/unit/vagrant_cloud/response/search_spec.rb:12:in `new' > # ./spec/unit/vagrant_cloud/response/search_spec.rb:12:in `block (2 > levels) in ' > # ./spec/unit/vagrant_cloud/response/search_spec.rb:101:in `block (3 > levels) in ' > > Finished in 0.47348 seconds (files took 0.61223 seconds to load) > 501 examples, 92 failures > > Failed examples: > > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:23 # > VagrantCloud::Box::Version#initialize should load providers > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:36 # > VagrantCloud::Box::Version#delete should not delete if version does not exist > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:41 # > VagrantCloud::Box::Version#delete should return nil > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:51 # > VagrantCloud::Box::Version#delete when version exists should make a version > deletion request > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:56 # > VagrantCloud::Box::Version#delete when version exists should include box > username and name > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:62 # > VagrantCloud::Box::Version#delete when version exists should include the > version > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:68 # > VagrantCloud::Box::Version#delete when version exists should delete the > version from the box versions > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:83 # > VagrantCloud::Box::Version#release when version is released should error > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:91 # > VagrantCloud::Box::Version#release when version has not been saved should > error > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:102 # > VagrantCloud::Box::Version#release when version is saved and not released > should send request to release version > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:108 # > VagrantCloud::Box::Version#release when version is saved and not released > should include box username, box name, and version > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:114 # > VagrantCloud::Box::Version#release when version is saved and not released > should update status with value provided in result > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:121 # > VagrantCloud::Box::Version#release when version is saved and not released > should return self > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:132 # > VagrantCloud::Box::Version#revoke when version is not released should error > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:140 # > VagrantCloud::Box::Version#revoke when version is released should send > request to revoke release > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:146 # > VagrantCloud::Box::Version#revoke when version is released should include the > box username, box name, and version > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:152 # > VagrantCloud::Box::Version#revoke when version is released should update > status with value provided in result > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:159 # > VagrantCloud::Box::Version#revoke when version is released should return self > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:168 # > VagrantCloud::Box::Version#add_provider should create a new provider > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:172 # > VagrantCloud::Box::Version#add_provider should add provider to providers > collection > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:177 # > VagrantCloud::Box::Version#add_provider should raise error when provider > exists > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:188 # > VagrantCloud::Box::Version#dirty? when version does not exist should be true > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:196 # > VagrantCloud::Box::Version#dirty? when version does exist should be false > rspec ./spec/unit/vagrant_cloud/box/version_spec.rb:203 # > VagrantCloud::Box::Version#dirty? when version does
Bug#996518: ruby-typhoeus: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: [31mFailure/Error: require 'rack/handler/webrick'[0m
Source: ruby-typhoeus Version: 1.4.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-typhoeus was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Failure/Error: require 'rack/handler/webrick' > > LoadError: > cannot load such file -- webrick > # > :85:in > `require' > # > :85:in > `require' > # /usr/lib/ruby/vendor_ruby/rack/handler/webrick.rb:3:in `' > # > :85:in > `require' > # > :85:in > `require' > # ./spec/support/localhost_server.rb:2:in `' > # > :85:in > `require' > # > :85:in > `require' > # ./spec/spec_helper.rb:9:in `block in ' > # ./spec/spec_helper.rb:9:in `each' > # ./spec/spec_helper.rb:9:in `' > # > :85:in > `require' > # > :85:in > `require' > # ./spec/typhoeus_spec.rb:1:in `' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in > `load' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:2103:in > `load_file_handling_errors' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1606:in > `block in load_spec_files' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in > `each' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/configuration.rb:1604:in > `load_spec_files' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:102:in > `setup' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:86:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:71:in > `run' > # > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib/rspec/core/runner.rb:45:in > `invoke' > # /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec:4:in > `' > No examples found. > > Finished in 0.6 seconds (files took 2.62 seconds to load) > 0 examples, 0 failures, 35 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-typhoeus/ruby-typhoeus_1.4.0-1+rebuild1633397810_amd64.build.txt signature.asc Description: PGP signature
Bug#996517: ruby-tty-command: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-tty-command Version: 0.9.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-tty-command was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 1, expected 0) > # ./lib/tty/command/cmd.rb:66:in `update' > # ./lib/tty/command.rb:177:in `command' > # ./lib/tty/command.rb:103:in `run' > # ./lib/tty/command.rb:159:in `ruby' > # ./spec/unit/ruby_spec.rb:7:in `block (2 levels) in ' > > Top 2 slowest examples (0.06033 seconds, 28.6% of total time): > TTY::Command::Printers::Pretty prints output on error when > only_output_on_error is true > 0.04233 seconds ./spec/unit/printers/pretty_spec.rb:144 > TTY::Command :pty logs phased output in pseudo terminal mode > 0.018 seconds ./spec/unit/pty_spec.rb:30 > > Top 2 slowest example groups: > TTY::Command::Printers::Null > 0.00645 seconds average (0.01934 seconds / 3 examples) > ./spec/unit/printers/null_spec.rb:3 > TTY::Command :pty > 0.00634 seconds average (0.01902 seconds / 3 examples) > ./spec/unit/pty_spec.rb:3 > > Finished in 0.21107 seconds (files took 0.50957 seconds to load) > 116 examples, 39 failures > > Failed examples: > > rspec ./spec/unit/pty_spec.rb:30 # TTY::Command :pty logs phased output in > pseudo terminal mode > rspec ./spec/unit/pty_spec.rb:4 # TTY::Command :pty executes command in > pseudo terminal mode as global option > rspec ./spec/unit/pty_spec.rb:17 # TTY::Command :pty executes command in > pseudo terminal mode as command option > rspec ./spec/unit/printers/pretty_spec.rb:120 # > TTY::Command::Printers::Pretty prints output on error & raises ExitError when > only_output_on_error is true > rspec ./spec/unit/printers/pretty_spec.rb:144 # > TTY::Command::Printers::Pretty prints output on error when > only_output_on_error is true > rspec ./spec/unit/printers/pretty_spec.rb:97 # TTY::Command::Printers::Pretty > doesn't print output on success when only_output_on_error is true > rspec ./spec/unit/redirect_spec.rb:92 # TTY::Command redirect redirects > multiple fds to a file > rspec ./spec/unit/redirect_spec.rb:24 # TTY::Command redirect redirects > :stdout -> :stderr > rspec ./spec/unit/redirect_spec.rb:44 # TTY::Command redirect redirects > STDOUT -> :err > rspec ./spec/unit/redirect_spec.rb:4 # TTY::Command redirect accepts standard > shell redirects > rspec ./spec/unit/redirect_spec.rb:54 # TTY::Command redirect redirects > STDOUT -> '/dev/null > rspec ./spec/unit/redirect_spec.rb:63 # TTY::Command redirect redirects to a > file > rspec ./spec/unit/redirect_spec.rb:34 # TTY::Command redirect redirects 1 -> 2 > rspec ./spec/unit/redirect_spec.rb:75 # TTY::Command redirect redirects to a > file as an array value > rspec ./spec/unit/redirect_spec.rb:14 # TTY::Command redirect redirects :out > -> :err > rspec ./spec/unit/printers/quiet_spec.rb:37 # TTY::Command::Printers::Quiet > doesn't print output on success when only_output_on_error is true > rspec ./spec/unit/printers/quiet_spec.rb:54 # TTY::Command::Printers::Quiet > prints output on error when only_output_on_error is true > rspec ./spec/unit/timeout_spec.rb:14 # TTY::Command#run times out an infite > process with constant output > rspec ./spec/unit/timeout_spec.rb:24 # TTY::Command#run times out an infinite > process with constant input data > rspec ./spec/unit/timeout_spec.rb:4 # TTY::Command#run times out infinite > process without input or output > rspec ./spec/unit/output_spec.rb:6 # TTY::Command :output runs command and > prints to a file > rspec ./spec/unit/dry_run_spec.rb:35 # TTY::Command dry run doesn't collect > printout to stdin or stderr > rspec ./spec/unit/dry_run_spec.rb:11 # TTY::Command dry run runs command in > dry run mode > rspec ./spec/unit/dry_run_spec.rb:23 # TTY::Command dry run allows to run > command in dry mode > rspec ./spec/unit/input_spec.rb:4 # TTY::Command input reads user input data > rspec ./spec/unit/binmode_spec.rb:4 # TTY::Command#run encodes output as > unicode by default > rspec ./spec/unit/binmode_spec.rb:22 # TTY::Command#run encodes all commands > output as binary > rspec ./spec/unit/binmode_spec.rb:13 # TTY::Command#run encodes output as > binary > rspec ./spec/unit/run_spec.rb:64 # TTY::Command#run runs command successfully > with logging without uuid set locally > rspec ./spec/unit/run_spec.rb:138 # TTY::Command#run logs phased output in > one line > rspec ./spec/unit/run_spec.rb:48 # TTY::Command#run runs command successfully > with logging without uuid set globally > rspec ./spec/unit/run_spec.rb:99 # TTY::Command#run raises ExitError on > command failure > rspec
Bug#996516: ruby-toml-rb: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Segmentation fault
Source: ruby-toml-rb Version: 2.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-toml-rb was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-toml-rb/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"toml-rb\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-toml-rb/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/dumper_test.rb" "test/errors_test.rb" "test/grammar_test.rb" > "test/toml_test.rb" -v > Run options: -v --seed 58529 > > # Running: > > TomlTest#test_file = 0.01 s = . > TomlTest#test_invalid_cases = 0.03 s = . > TomlTest#test_line_break = 0.00 s = . > TomlTest#test_symbolize_keys = 0.01 s = . > TomlTest#test_file_v_0_4_0 = 0.06 s = . > TomlTest#test_valid_cases = /usr/lib/ruby/vendor_ruby/citrus.rb:1286: [BUG] > Segmentation fault at 0x556770d23000 > ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu] > > -- Control frame information --- > c:0038 p: s:0225 e:000224 CFUNC :slice! > c:0037 p:0063 s:0219 e:000218 METHOD /usr/lib/ruby/vendor_ruby/citrus.rb:1286 > [FINISH] > c:0036 p: s:0210 e:000209 CFUNC :new > c:0035 p:0139 s:0203 e:000202 METHOD /usr/lib/ruby/vendor_ruby/citrus.rb:1470 > c:0034 p:0011 s:0188 e:000187 METHOD /usr/lib/ruby/vendor_ruby/citrus.rb:1330 > c:0033 p:0003 s:0183 e:000182 METHOD /usr/lib/ruby/vendor_ruby/citrus.rb:1336 > c:0032 p:0018 s:0178 e:000176 METHOD > /<>/debian/ruby-toml-rb/usr/share/rubygems-integration/all/gems/toml-rb-2.0.1/lib/tom > [FINISH] > c:0031 p: s:0173 e:000172 CFUNC :map > c:0030 p:0062 s:0169 e:000168 METHOD > /<>/debian/ruby-toml-rb/usr/share/rubygems-integration/all/gems/toml-rb-2.0.1/lib/tom > [FINISH] > c:0029 p: s:0161 e:000160 CFUNC :new > c:0028 p:0019 s:0155 e:000154 METHOD > /<>/debian/ruby-toml-rb/usr/share/rubygems-integration/all/gems/toml-rb-2.0.1/lib/tom > c:0027 p:0030 s:0149 e:000148 METHOD > /<>/debian/ruby-toml-rb/usr/share/rubygems-integration/all/gems/toml-rb-2.0.1/lib/tom > c:0026 p:0059 s:0143 e:000142 BLOCK /<>/test/toml_test.rb:121 > [FINISH] > c:0025 p: s:0135 e:000134 CFUNC :each > c:0024 p:0059 s:0131 e:000130 METHOD /<>/test/toml_test.rb:117 > c:0023 p:0006 s:0124 E:000510 METHOD /<>/test/toml_test.rb:131 > c:0022 p:0019 s:0120 e:000119 BLOCK > /usr/lib/ruby/vendor_ruby/minitest/test.rb:98 > c:0021 p:0002 s:0117 e:000116 METHOD > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195 > c:0020 p:0005 s:0112 e:000111 BLOCK > /usr/lib/ruby/vendor_ruby/minitest/test.rb:95 > c:0019 p:0015 s:0109 e:000108 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:270 > c:0018 p:0005 s:0104 e:000103 BLOCK > /usr/lib/ruby/vendor_ruby/minitest/test.rb:94 > c:0017 p:0030 s:0101 e:000100 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:365 > c:0016 p:0045 s:0093 E:001998 METHOD > /usr/lib/ruby/vendor_ruby/minitest/test.rb:211 > c:0015 p:0004 s:0086 E:001920 METHOD > /usr/lib/ruby/vendor_ruby/minitest/test.rb:93 > c:0014 p:0008 s:0082 e:81 METHOD > /usr/lib/ruby/vendor_ruby/minitest.rb:1029 > c:0013 p:0026 s:0075 e:73 METHOD /usr/lib/ruby/vendor_ruby/minitest.rb:339 > c:0012 p:0010 s:0067 e:66 BLOCK > /usr/lib/ruby/vendor_ruby/minitest.rb:326 [FINISH] > c:0011 p: s:0063 e:62 CFUNC :each > c:0010 p:0006 s:0059 e:58 BLOCK /usr/lib/ruby/vendor_ruby/minitest.rb:325 > c:0009 p:0030
Bug#996515: ruby-tilt: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: TypeError: no implicit conversion of Hash into String
Source: ruby-tilt Version: 2.0.10-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-tilt was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > TypeError: no implicit conversion of Hash into String > /usr/lib/ruby/3.0.0/csv.rb:1273:in `initialize' > /usr/lib/ruby/3.0.0/csv.rb:1273:in `new' > /usr/lib/ruby/3.0.0/csv.rb:1273:in `generate' > (__TEMPLATE__):in `__tilt_400' > > /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in > `call' > > /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in > `evaluate' > > /<>/debian/ruby-tilt/usr/lib/ruby/vendor_ruby/tilt/template.rb:109:in > `render' > /<>/test/tilt_csv_test.rb:32:in `block in > ' > /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' > > 237 runs, 433 assertions, 1 failures, 6 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/tilt_asciidoctor_test.rb" "test/tilt_blueclothtemplate_test.rb" > "test/tilt_buildertemplate_test.rb" "test/tilt_cache_test.rb" > "test/tilt_coffeescripttemplate_test.rb" > "test/tilt_commonmarkertemplate_test.rb" "test/tilt_compilesite_test.rb" > "test/tilt_creoletemplate_test.rb" "test/tilt_csv_test.rb" > "test/tilt_erbtemplate_test.rb" "test/tilt_erubistemplate_test.rb" > "test/tilt_erubitemplate_test.rb" "test/tilt_etannitemplate_test.rb" > "test/tilt_hamltemplate_test.rb" "test/tilt_kramdown_test.rb" > "test/tilt_lesstemplate_test.rb" "test/tilt_liquidtemplate_test.rb" > "test/tilt_livescripttemplate_test.rb" "test/tilt_mapping_test.rb" > "test/tilt_markaby_test.rb" "test/tilt_markdown_test.rb" > "test/tilt_marukutemplate_test.rb" "test/tilt_metadata_test.rb" > "test/tilt_nokogiritemplate_test.rb" "test/tilt_pandoctemplate_test.rb" > "test/tilt_prawntemplate_test.rb" "test/tilt_radiustemplate_test.rb" > "test/tilt_rdiscounttemplate_test.rb" "test/tilt_rdoctemplate_test.rb" > "test/tilt_redcarpettemplate_test.rb" "test/tilt_redclothtemplate_test.rb" > "test/tilt_rstpandoctemplate_test.rb" "test/tilt_sasstemplate_test.rb" > "test/tilt_sigil_test.rb" "test/tilt_stringtemplate_test.rb" > "test/tilt_template_test.rb" "test/tilt_test.rb" > "test/tilt_typescript_test.rb" "test/tilt_wikiclothtemplate_test.rb" > "test/tilt_yajltemplate_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-tilt/ruby-tilt_2.0.10-1+rebuild1633397153_amd64.build.txt signature.asc Description: PGP signature
Bug#996514: ruby-terrapin: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: undef_method :exitstatus
Source: ruby-terrapin
Version: 0.6.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-terrapin was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: undef_method :exitstatus
>
> FrozenError:
>can't modify frozen object: pid 1724074 exit 0
> # ./spec/support/unsetting_exitstatus.rb:4:in `undef_method'
> # ./spec/support/unsetting_exitstatus.rb:4:in `singleton class'
> # ./spec/support/unsetting_exitstatus.rb:3:in
> `assuming_no_processes_have_been_run'
> # ./spec/terrapin/errors_spec.rb:55:in `block (2 levels) in (required)>'
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/terrapin/command_line/runners/backticks_runner_spec.rb:19:in
> `block (2 levels) in '.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 1.4 seconds (files took 0.51763 seconds to load)
> 67 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/terrapin/errors_spec.rb:54 # When an error happens does not blow
> up if running the command errored before execution
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-terrapin/ruby-terrapin_0.6.0-2+rebuild1633396815_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996513: ruby-stackprof: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-stackprof Version: 0.2.15-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-stackprof was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-stackprof/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"stackprof\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-stackprof/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_middleware.rb" "test/test_report.rb" "test/test_stackprof.rb" -v > /<>/test/test_stackprof.rb:181: warning: assigned but unused > variable - raw > Run options: -v --seed 11397 > > # Running: > > StackProfTest#test_raw = 0.00 s = F > StackProfTest#test_info = 0.00 s = . > StackProfTest#test_out_to_path_string = 0.00 s = . > StackProfTest#test_custom = 0.00 s = F > StackProfTest#test_raises_if_metadata_is_not_a_hash = 0.00 s = . > StackProfTest#test_metadata = 0.04 s = . > StackProfTest#test_running = 0.00 s = . > StackProfTest#test_object_allocation = 0.00 s = F > StackProfTest#test_cputime = 0.04 s = F > StackProfTest#test_gc = 0.08 s = . > StackProfTest#test_empty_metadata = 0.03 s = . > StackProfTest#test_object_allocation_interval = 0.00 s = . > StackProfTest#test_recursive_total_samples = 0.00 s = . > StackProfTest#test_start_stop_results = 0.00 s = . > StackProfTest#test_fork = 0.00 s = . > StackProfTest#test_walltime = 0.20 s = F > StackProfTest#test_pathname_out = 0.00 s = . > StackProfTest#test_out = 0.00 s = . > StackProf::MiddlewareTest#test_enabled_should_use_a_proc_if_passed = 0.00 s = > . > StackProf::MiddlewareTest#test_raw = 0.00 s = . > StackProf::MiddlewareTest#test_path_custom = 0.00 s = . > StackProf::MiddlewareTest#test_save_custom = 0.00 s = . > StackProf::MiddlewareTest#test_save_default = 0.00 s = . > StackProf::MiddlewareTest#test_enabled_should_use_a_proc_if_passed_and_use_the_request_env > = 0.00 s = . > StackProf::MiddlewareTest#test_metadata = 0.00 s = . > StackProf::MiddlewareTest#test_path_default = 0.00 s = . > ReportDumpTest#test_dump_to_file = 0.02 s = . > ReportDumpTest#test_dump_to_stdout = 0.00 s = . > > Finished in 0.424334s, 65.9858 runs/s, 164.9644 assertions/s. > > 1) Failure: > StackProfTest#test_raw [/<>/test/test_stackprof.rb:108]: > Expected # encoding: ASCII-8BIT > #valid: true > "StackProf.sample" to include "StackProfTest#test_raw". > > 2) Failure: > StackProfTest#test_custom [/<>/test/test_stackprof.rb:93]: > Expected # encoding: ASCII-8BIT > #valid: true > "StackProf.sample" to include "StackProfTest#test_custom". > > 3) Failure: > StackProfTest#test_object_allocation > [/<>/test/test_stackprof.rb:42]: > Expected: 2 > Actual: 4 > > 4) Failure: > StackProfTest#test_cputime [/<>/test/test_stackprof.rb:68]: > Expected # encoding: ASCII-8BIT > #valid: true > "Integer#**" to include "StackProfTest#math". > > 5) Failure: > StackProfTest#test_walltime [/<>/test/test_stackprof.rb:77]: > --- expected > +++ actual > @@ -1 +1,3 @@ > -"StackProfTest#idle" > +# encoding: ASCII-8BIT > +#valid: true > +"IO.select" > > > 28 runs, 70 assertions, 5 failures, 0 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_middleware.rb" "test/test_report.rb" "test/test_stackprof.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. The full build log is available at
Bug#996512: ruby-spy: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: tried to create Proc object without a block
Source: ruby-spy Version: 0.4.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-spy was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: tried to create Proc object without a block > > /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:196:in > `new' > > /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:196:in > `has_been_called_with?' > > /<>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/api.rb:11:in > `assert_received_with' > /<>/test/integration/test_api.rb:19:in > `test_assert_received_with' > /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' > > 65 runs, 108 assertions, 0 failures, 5 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/integration/test_api.rb" "test/integration/test_constant_spying.rb" > "test/integration/test_instance_method.rb" "test/integration/test_mocking.rb" > "test/integration/test_subroutine_spying.rb" "test/spy/test_mock.rb" > "test/spy/test_subroutine.rb" "test/test_helper.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-spy/ruby-spy_0.4.3-1+rebuild1633396140_amd64.build.txt signature.asc Description: PGP signature
Bug#996511: ruby-sprockets: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1)
Source: ruby-sprockets Version: 3.7.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-sprockets was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 2, expected 1) > :14:in `open' > /<>/test/test_performance.rb:23:in `entries' > /<>/test/test_performance.rb:23:in `entries' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/path_utils.rb:56:in > `entries' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/cached_environment.rb:19:in > `block in initialize' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/cached_environment.rb:35:in > `entries' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/resolve.rb:179:in > `dirname_matches' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/resolve.rb:157:in > `path_matches' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/resolve.rb:125:in > `block in resolve_under_paths' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/resolve.rb:124:in > `each' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/resolve.rb:124:in > `resolve_under_paths' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/resolve.rb:108:in > `resolve_logical_path' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/resolve.rb:35:in > `resolve' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/legacy.rb:66:in > `resolve_with_compat' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/base.rb:64:in > `find_asset' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/environment.rb:30:in > `find_asset' > > /<>/debian/ruby-sprockets/usr/lib/ruby/vendor_ruby/sprockets/base.rb:92:in > `[]' > /<>/test/test_sprocketize.rb:58:in `block in > ' > /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/parallel.rb:33:in `block (2 levels) in > start' > > 773 runs, 1320 assertions, 26 failures, 422 errors, 2 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_asset.rb" "test/test_bundle.rb" "test/test_cache_store.rb" > "test/test_caching.rb" "test/test_coffee_script_processor.rb" > "test/test_context.rb" "test/test_digest_utils.rb" > "test/test_ejs_processor.rb" "test/test_encoding.rb" > "test/test_encoding_utils.rb" "test/test_engines.rb" > "test/test_environment.rb" "test/test_erb_processor.rb" > "test/test_http_utils.rb" "test/test_jst_processor.rb" "test/test_loader.rb" > "test/test_manifest.rb" "test/test_manifest_utils.rb" > "test/test_path_dependency_utils.rb" "test/test_path_digest_utils.rb" > "test/test_path_utils.rb" "test/test_performance.rb" > "test/test_processor_utils.rb" "test/test_rake_task.rb" > "test/test_require.rb" "test/test_resolve.rb" "test/test_sass.rb" > "test/test_server.rb" "test/test_source_maps.rb" "test/test_sprocketize.rb" > "test/test_transformers.rb" "test/test_uglifier_compressor.rb" > "test/test_uri_tar.rb" "test/test_uri_utils.rb" "test/test_utils.rb" > "--exclude=/eco|closure|yui/" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sprockets/ruby-sprockets_3.7.2-1+rebuild1633396062_amd64.build.txt signature.asc Description: PGP signature
Bug#996510: ruby-spring: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Errno::ENOENT: No such file or directory @ rb_check_realpath_internal - /tmp/d20211005-1582813-mce9ae
Source: ruby-spring Version: 2.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-spring was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Errno::ENOENT: No such file or directory @ rb_check_realpath_internal - > /tmp/d20211005-1582813-mce9ae > /<>/lib/spring/watcher/abstract.rb:20:in `realpath' > /<>/lib/spring/watcher/abstract.rb:20:in `initialize' > /<>/lib/spring/watcher/polling.rb:9:in `initialize' > /<>/test/support/watcher_test.rb:21:in `new' > /<>/test/support/watcher_test.rb:21:in `watcher' > /<>/test/support/watcher_test.rb:30:in `teardown' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block (4 levels) in > run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:195:in `capture_exceptions' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `block (3 levels) in > run' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:101:in `each' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:101: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' > > 32 runs, 31 assertions, 0 failures, 8 errors, 0 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/unit/client/help_test.rb" "test/unit/client/version_test.rb" > "test/unit/commands_test.rb" "test/unit/process_title_updater_test.rb" > "test/unit/watcher_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-spring/ruby-spring_2.1.0-2+rebuild1633395982_amd64.build.txt signature.asc Description: PGP signature
Bug#996509: ruby-slop: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 2, expected 1)
Source: ruby-slop Version: 4.6.2-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-slop was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 2, expected 1) > /<>/lib/slop/parser.rb:13:in `initialize' > /<>/lib/slop/options.rb:32:in `new' > /<>/lib/slop/options.rb:32:in `initialize' > /<>/test/result_test.rb:15:in `new' > /<>/test/result_test.rb:15:in `block (2 levels) in (required)>' > /usr/lib/ruby/vendor_ruby/minitest/spec.rb:187:in `instance_eval' > /usr/lib/ruby/vendor_ruby/minitest/spec.rb:187:in `block in before' > /usr/lib/ruby/vendor_ruby/minitest/test.rb:96: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' > > 79 runs, 7 assertions, 0 failures, 73 errors, 0 skips > rake aborted! > Command failed with status (1) > > Tasks: TOP => default => test > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-slop/ruby-slop_4.6.2-1.1+rebuild1633395769_amd64.build.txt signature.asc Description: PGP signature
Bug#995875: Stable also affected
On Thu, Oct 14, 2021 at 11:06:52AM +0200, Diederik de Haas wrote: > On 7 Oct 2021 18:35:18 +0200 Francesco Poli wrote: > > This seems to be exactly the same issue that was reported in #995448, > > which is marked as affecting package apt-listbugs. > > > > However, I see that you are using oldstable: I don't know whether a > > fixed version of ruby-httpclient will ever be backported to oldstable. > > Maybe it can enter oldstable as a security update... I am not sure > > whether it will be considered as a security issue worth a DSA, though... > > I just started to write to #995448 to mention that Stable is also affected. > Maybe that changes the equation? > The version of ruby-httpclient is the same for Stable and Oldstable btw. I have stable and oldstable updates lined up (#996026 and #996024). signature.asc Description: PGP signature
Bug#996404: ruby-sassc-rails: FTBFS: ERROR: Test "ruby3.0" failed.
Source: ruby-sassc-rails Version: 2.1.2-5+rebuild1633394876 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-sassc-rails/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"sassc-rails\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-sassc-rails/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-sassc-rails/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/sassc_rails_test.rb" "test/test_helper.rb" -v > /<>/test/sassc_rails_test.rb:125: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:126: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:127: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:128: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:129: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:130: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:131: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:132: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:133: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:134: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:135: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:136: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:137: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:138: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:139: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:140: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:144: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:145: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:147: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:149: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a space after `/' > operator > /<>/test/sassc_rails_test.rb:150: warning: ambiguity between > regexp and two divisions: wrap regexp in parentheses or add a
Bug#996403: ruby-rails-controller-testing: FTBFS: ERROR: Test "ruby3.0" failed.
Source: ruby-rails-controller-testing Version: 1.0.5-1+rebuild1633392495 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-rails-controller-testing/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"rails-controller-testing\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-rails-controller-testing/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/controllers/assigns_test.rb" > "test/controllers/template_assertions_test.rb" > "test/helpers/template_assertions_test.rb" > "test/integration/template_assertions_test.rb" "test/test_helper.rb" -v > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:496:in > `materialize': Could not find racc-1.4.16 in any of the sources > (Bundler::GemNotFound) > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:234:in > `specs_for' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/runtime.rb:18:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in > `setup' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in > `block in ' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:136:in > `with_level' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:88:in > `silence' > from > /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in > `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/dummy/config/boot.rb:4:in `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/dummy/config/application.rb:1:in ` (required)>' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/dummy/config/environment.rb:2:in ` (required)>' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/test_helper.rb:4:in `' > from > :85:in > `require' > from > :85:in > `require' > from /<>/test/controllers/assigns_test.rb:1:in ` (required)>' > from > :85:in > `require' > from > :85:in > `require' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:17:in > `block in ' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `select' > from > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb:5:in > `' > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/controllers/assigns_test.rb" > "test/controllers/template_assertions_test.rb" > "test/helpers/template_assertions_test.rb" > "test/integration/template_assertions_test.rb" "test/test_helper.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. The full build log is available from: http://qa-logs.debian.net/2021/10/13/ruby-rails-controller-testing_1.0.5-1+rebuild1633392495_amd64.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 mine so that we can identify if something relevant changed in the meantime. signature.asc
Bug#996387: ruby-sigar: FTBFS with ruby3.0: sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory
Source: ruby-sigar
Version: 0.7.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-sigar was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> gcc -fdebug-prefix-map=/<>=. -I.
> -I/usr/include/x86_64-linux-gnu/ruby-2.7.0
> -I/usr/include/ruby-2.7.0/ruby/backward -I/usr/include/ruby-2.7.0 -I.
> -Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src/os/linux
> -U_FILE_OFFSET_BITS -DRB_HAS_RE_ERROR -DRB_RUBY_19 -fPIC -g -O2
> -ffile-prefix-map=/build/ruby2.7-yGW2TI/ruby2.7-2.7.4=.
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -o
> sigar_util.o -c sigar_util.c
> sigar_util.c: In function ‘sigar_proc_list_procfs_get’:
> sigar_util.c:167:5: warning: ‘readdir_r’ is deprecated
> [-Wdeprecated-declarations]
> 167 | while (readdir_r(dirp, , ) == 0) {
> | ^
> In file included from sigar_util.c:31:
> /usr/include/dirent.h:183:12: note: declared here
> 183 | extern int readdir_r (DIR *__restrict __dirp,
> |^
> sigar_util.c: In function ‘sigar_proc_fd_count’:
> sigar_util.c:210:5: warning: ‘readdir_r’ is deprecated
> [-Wdeprecated-declarations]
> 210 | while (readdir_r(dirp, , ) == 0) {
> | ^
> In file included from sigar_util.c:31:
> /usr/include/dirent.h:183:12: note: declared here
> 183 | extern int readdir_r (DIR *__restrict __dirp,
> |^
> sigar_util.c: At top level:
> sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory
> 742 | #include
> | ^~~
> compilation terminated.
> make[1]: *** [Makefile:245: sigar_util.o] Error 1
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sigar/ruby-sigar_0.7.3-2+rebuild1633395509_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996385: ruby-shadow: FTBFS with ruby3.0: ld: cannot find -lshadow
Source: ruby-shadow Version: 2.5.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-shadow was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > "x86_64-linux-gnu-gcc -o conftest -I/usr/include/x86_64-linux-gnu/ruby-3.0.0 > -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I. > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=. > -fstack-protector-strong -Wformat -Werror=format-security -fPIC conftest.c > -L. -L/usr/lib/x86_64-linux-gnu -L. -Wl,-z,relro -Wl,-z,now > -fstack-protector-strong -rdynamic -Wl,-export-dynamic -lruby-3.0 > -lshadow -lm -lc" > /usr/bin/ld: cannot find -lshadow > collect2: error: ld returned 1 exit status The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-shadow/ruby-shadow_2.5.0-1+rebuild1633395333_amd64.build.txt signature.asc Description: PGP signature
Bug#996386: ruby-sham-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick/httputils
Source: ruby-sham-rack Version: 1.4.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-sham-rack was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > cannot load such file -- webrick/httputils > # ./spec/sham_rack_spec.rb:6:in `' > > > Finished in 0.8 seconds (files took 2.28 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sham-rack/ruby-sham-rack_1.4.1-2+rebuild1633395351_amd64.build.txt signature.asc Description: PGP signature
Bug#996384: ruby-serialport: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: :85:in `require': /<>/debian/ruby-se
Source: ruby-serialport Version: 1.3.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-serialport was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > :85:in > `require': > /<>/debian/ruby-serialport/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/serialport.so: > undefined symbol: rb_secure - > /<>/debian/ruby-serialport/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/serialport.so > (LoadError) > from > :85:in > `require' > from > /<>/debian/ruby-serialport/usr/lib/ruby/vendor_ruby/serialport.rb:1:in > `' > from > :85:in > `require' > from > :85:in > `require' > from debian/ruby-tests.rb:2:in `' > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-serialport/ruby-serialport_1.3.1-1+rebuild1633395250_amd64.build.txt signature.asc Description: PGP signature
Bug#996383: ruby-semantic-puppet: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:
Source: ruby-semantic-puppet Version: 1.0.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-semantic-puppet was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > RuntimeError: > The `SortedSet` class has been extracted from the `set` library.You > must use the `sorted_set` gem or other alternatives. > # ./lib/semantic_puppet/dependency/graph_node.rb:39:in `block in > dependencies' > # ./lib/semantic_puppet/dependency/graph_node.rb:47:in `add_dependency' > # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:14:in > `block in initialize' > # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:14:in `each' > # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:14:in > `initialize' > # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:26:in `new' > # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:26:in > `instance' > # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:54:in > `block (3 levels) in ' > # ./spec/unit/semantic_puppet/dependency/graph_node_spec.rb:57:in > `block (3 levels) in ' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- sorted_set > # ./lib/semantic_puppet/dependency/graph_node.rb:39:in `block in > dependencies' > > Finished in 1.03 seconds (files took 0.69167 seconds to load) > 985 examples, 53 failures [...] > Randomized with seed 9711 > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: Note that sorted_set has been removed from the standard library. It needs to be packaged separately, and when that's done this package will need an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-semantic-puppet/ruby-semantic-puppet_1.0.3-1+rebuild1633395095_amd64.build.txt signature.asc Description: PGP signature
Bug#996382: ruby-seamless-database-pool: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-seamless-database-pool Version: 1.0.20-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-seamless-database-pool was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: >wrong number of arguments (given 1, expected 0) > # > /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.7/lib/active_record/connection_adapters/abstract/database_statements.rb:273:in > `transaction' > # > ./lib/active_record/connection_adapters/seamless_database_pool_adapter.rb:187:in > `block in transaction' > # > ./lib/active_record/connection_adapters/seamless_database_pool_adapter.rb:260:in > `use_master_connection' > # > ./lib/active_record/connection_adapters/seamless_database_pool_adapter.rb:186:in > `transaction' > # ./spec/seamless_database_pool_adapter_spec.rb:146:in `block (4 levels) > in ' > # ./lib/seamless_database_pool.rb:51:in `block in > use_persistent_read_connection' > # ./lib/seamless_database_pool.rb:78:in `set_read_only_connection_type' > # ./lib/seamless_database_pool.rb:51:in `use_persistent_read_connection' > # ./spec/seamless_database_pool_adapter_spec.rb:144:in `block (3 levels) > in ' > > Finished in 0.75931 seconds (files took 0.97484 seconds to load) > 64 examples, 1 failure > > Failed examples: > > rspec ./spec/seamless_database_pool_adapter_spec.rb:135 # > SeamlessDatabasePoolAdapter selecting a connection from the pool should use > the master connection inside a transaction > > Randomized with seed 45692 > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-seamless-database-pool/ruby-seamless-database-pool_1.0.20-1.1+rebuild1633395012_amd64.build.txt signature.asc Description: PGP signature
Bug#996381: ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected 1..3)
Source: ruby-sanitize Version: 5.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-sanitize was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: wrong number of arguments (given 4, expected 1..3) > /usr/lib/ruby/vendor_ruby/nokogumbo/html5/document.rb:4:in `parse' > /usr/lib/ruby/vendor_ruby/nokogumbo/html5.rb:22:in `parse' > > /<>/debian/ruby-sanitize/usr/lib/ruby/vendor_ruby/sanitize.rb:126:in > `document' > > /<>/debian/ruby-sanitize/usr/lib/ruby/vendor_ruby/sanitize.rb:61:in > `document' > /<>/test/test_clean_element.rb:522:in `block (3 levels) in > ' > /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/parallel.rb:33:in `block (2 levels) in > start' > > 227 runs, 1483 assertions, 0 failures, 17 errors, 8 skips > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_clean_comment.rb" "test/test_clean_css.rb" > "test/test_clean_doctype.rb" "test/test_clean_element.rb" > "test/test_config.rb" "test/test_malicious_css.rb" > "test/test_malicious_html.rb" "test/test_parser.rb" "test/test_sanitize.rb" > "test/test_sanitize_css.rb" "test/test_transformers.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-sanitize/ruby-sanitize_5.2.1-2+rebuild1633394782_amd64.build.txt signature.asc Description: PGP signature
Bug#996379: ruby-rspec: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure }
Source: ruby-rspec
Version: 3.9.0c2e2m1s3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-rspec was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts|
> raise failure }
>expected /Warnings were generated:/ but nothing was raised
> # ./spec/rspec/support/spec/stderr_splitter_spec.rb:92:in `block (2
> levels) in '
> # ./spec/rspec/support/spec/stderr_splitter_spec.rb:19:in `block (2
> levels) in '
>
> Finished in 1.08 seconds (files took 0.2783 seconds to load)
> 538 examples, 1 failure, 1 pending
>
> Failed examples:
>
> rspec ./spec/rspec/support/spec/stderr_splitter_spec.rb:90 #
> RSpec::Support::StdErrSplitter will fail an example which generates a warning
>
> Randomized with seed 13098
>
> cd -
> Failed: rspec-support
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rspec/ruby-rspec_3.9.0c2e2m1s3-2+rebuild1633393939_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996380: ruby-safe-yaml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-safe-yaml Version: 1.0.5-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-safe-yaml was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 0, expected 2) > # ./lib/safe_yaml/safe_to_ruby_visitor.rb:14:in `initialize' > # ./lib/safe_yaml/psych_resolver.rb:25:in `new' > # ./lib/safe_yaml/psych_resolver.rb:25:in `native_resolve' > # ./lib/safe_yaml/resolver.rb:12:in `resolve_node' > # ./lib/safe_yaml/resolver.rb:55:in `block in resolve_seq' > # ./lib/safe_yaml/resolver.rb:55:in `each' > # ./lib/safe_yaml/resolver.rb:55:in `inject' > # ./lib/safe_yaml/resolver.rb:55:in `resolve_seq' > # ./lib/safe_yaml/psych_resolver.rb:17:in `resolve_root' > # ./lib/safe_yaml/resolver.rb:16:in `resolve_node' > # ./lib/safe_yaml/load.rb:151:in `load' > # ./lib/safe_yaml.rb:29:in `safe_load' > # ./spec/safe_yaml_spec.rb:7:in `safe_load_round_trip' > # ./spec/safe_yaml_spec.rb:725:in `block (4 levels) in ' > > Finished in 0.12951 seconds (files took 0.22092 seconds to load) > 134 examples, 11 failures > > Failed examples: > > rspec ./spec/safe_yaml_spec.rb:318 # Psych safe_load with special whitelisted > tags defined will allow objects to be deserialized for whitelisted tags > rspec ./spec/safe_yaml_spec.rb:330 # Psych safe_load with special whitelisted > tags defined will not allow non-whitelisted objects to be embedded within > objects with whitelisted tags > rspec ./spec/safe_yaml_spec.rb:372 # Psych safe_load with special whitelisted > tags defined with the :raise_on_unknown_tag option enabled does not raise an > exception as long as all tags are whitelisted > rspec ./spec/safe_yaml_spec.rb:415 # Psych safe_load with special whitelisted > tags defined with the :raise_on_unknown_tag option enabled with whitelisted > custom class does not raise an exception on the non-specific '!' tag > rspec ./spec/safe_yaml_spec.rb:458 # Psych safe_load when options are passed > direclty to #load which differ from the defaults (or, for example, when > certain tags are whitelisted) goes with the default option when it is not > overridden > rspec ./spec/safe_yaml_spec.rb:464 # Psych safe_load when options are passed > direclty to #load which differ from the defaults (or, for example, when > certain tags are whitelisted) allows the default option to be overridden on a > per-call basis > rspec ./spec/safe_yaml_spec.rb:688 # Psych whitelist! with a Class as its > argument successfully deserializes the specified class > rspec ./spec/safe_yaml_spec.rb:699 # Psych whitelist! with a Class as its > argument works for ranges > rspec ./spec/safe_yaml_spec.rb:704 # Psych whitelist! with a Class as its > argument works for regular expressions > rspec ./spec/safe_yaml_spec.rb:709 # Psych whitelist! with a Class as its > argument works for multiple classes > rspec ./spec/safe_yaml_spec.rb:714 # Psych whitelist! with a Class as its > argument works for arbitrary Exception subclasses > > debian/ruby-tests.rb:16:in `block in ': unhandled exception > from debian/ruby-tests.rb:14:in `each' > from debian/ruby-tests.rb:14:in `' > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-safe-yaml/ruby-safe-yaml_1.0.5-1+rebuild1633394716_amd64.build.txt signature.asc Description: PGP signature
Bug#996378: ruby-rspec-retry: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error:
Source: ruby-rspec-retry
Version: 0.6.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-rspec-retry was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error:
>expect(example_group.class_variable_get(:@@results)).to eq({
> 'without retry option' => [true, 1],
> 'with retry option' => [false, 3]
>})
>
> NameError:
>uninitialized class variable @@results in
> RSpec::ExampleGroups::Anonymous
> # ./spec/lib/rspec/retry_spec.rb:359:in `class_variable_get'
> # ./spec/lib/rspec/retry_spec.rb:359:in `block (3 levels) in (required)>'
> # ./spec/spec_helper.rb:13:in `block (3 levels) in '
> # ./spec/spec_helper.rb:11:in `block (2 levels) in '
> # ./lib/rspec/retry.rb:124:in `block in run'
> # ./lib/rspec/retry.rb:110:in `loop'
> # ./lib/rspec/retry.rb:110:in `run'
> # ./lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
> # ./lib/rspec/retry.rb:37:in `block (2 levels) in setup'
>
> Finished in 0.259 seconds (files took 0.35161 seconds to load)
> 29 examples, 3 failures, 5 pending, 1 error occurred outside of examples
>
> Failed examples:
>
> rspec ./spec/lib/rspec/retry_spec.rb:70 # RSpec::Retry with retry option with
> :retry => 0 should still run once
> rspec ./spec/lib/rspec/retry_spec.rb:74 # RSpec::Retry with retry option with
> :retry => 0 should run have run once
> rspec ./spec/lib/rspec/retry_spec.rb:357 # RSpec::Retry
> Example::Procsy#attempts should be exposed
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rspec-retry/ruby-rspec-retry_0.6.2-1+rebuild1633394189_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996377: ruby-rspec-rails: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: ArgumentError:
Source: ruby-rspec-rails Version: 4.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rspec-rails was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > ArgumentError: > wrong number of arguments (given 4, expected 3) > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `block in require' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:291:in > `load_dependency' > # > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/dependencies.rb:324:in > `require' > # ./spec/spec_helper.rb:18:in `' > No examples found. > No examples found. > > > Finished in 0.00825 seconds (files took 6.98 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > Finished in 0.00825 seconds (files took 6.98 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > ./spec/rspec/rails/active_model_spec.rb > ./spec/rspec/rails/active_record_spec.rb > ./spec/rspec/rails/assertion_adapter_spec.rb > ./spec/rspec/rails/assertion_delegator_spec.rb > ./spec/rspec/rails/configuration_spec.rb > ./spec/rspec/rails/example/channel_example_group_spec.rb > ./spec/rspec/rails/example/controller_example_group_spec.rb > ./spec/rspec/rails/example/feature_example_group_spec.rb > ./spec/rspec/rails/example/helper_example_group_spec.rb > ./spec/rspec/rails/example/job_example_group_spec.rb > ./spec/rspec/rails/example/mailbox_example_group_spec.rb > ./spec/rspec/rails/example/model_example_group_spec.rb > ./spec/rspec/rails/example/request_example_group_spec.rb > ./spec/rspec/rails/example/routing_example_group_spec.rb > ./spec/rspec/rails/example/system_example_group_spec.rb > ./spec/rspec/rails/example/view_example_group_spec.rb > ./spec/rspec/rails/fixture_file_upload_support_spec.rb > ./spec/rspec/rails/fixture_support_spec.rb > ./spec/rspec/rails/matchers/action_cable/have_broadcasted_to_spec.rb > ./spec/rspec/rails/matchers/action_cable/have_stream_spec.rb > ./spec/rspec/rails/matchers/action_mailbox_spec.rb > ./spec/rspec/rails/matchers/active_job_spec.rb > ./spec/rspec/rails/matchers/be_a_new_spec.rb > ./spec/rspec/rails/matchers/be_new_record_spec.rb > ./spec/rspec/rails/matchers/be_routable_spec.rb > ./spec/rspec/rails/matchers/be_valid_spec.rb > ./spec/rspec/rails/matchers/has_spec.rb > ./spec/rspec/rails/matchers/have_enqueued_mail_spec.rb >
Bug#996372: ruby-roxml: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:
Source: ruby-roxml Version: 4.0.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-roxml was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > NoMethodError: > undefined method `escape' for URI:Module > # ./lib/roxml/xml/references.rb:50:in `conventionize' > # ./lib/roxml/xml/references.rb:29:in `name' > # ./lib/roxml/xml/references.rb:33:in `xpath_name' > # ./lib/roxml/xml/references.rb:89:in `xpath' > # ./lib/roxml/xml/references.rb:121:in `nodes_in' > # ./lib/roxml/xml/references.rb:220:in `fetch_value' > # ./lib/roxml/xml/references.rb:38:in `value_in' > # ./lib/roxml.rb:557:in `block (2 levels) in from_xml' > # ./lib/roxml.rb:556:in `each' > # ./lib/roxml.rb:556:in `block in from_xml' > # :90:in `tap' > # ./lib/roxml.rb:553:in `from_xml' > # ./spec/examples/dashed_elements_spec.rb:6:in `block (2 levels) in > ' > > Finished in 0.44762 seconds (files took 1.15 seconds to load) > 212 examples, 15 failures, 18 pending > > Failed examples: > > rspec ./spec/examples/amazon_spec.rb:10 # > PITA::ItemSearchResponse#total_results should be parsed as a number > rspec ./spec/examples/amazon_spec.rb:16 # > PITA::ItemSearchResponse#total_pages should be parsed as a number > rspec ./spec/examples/amazon_spec.rb:22 # PITA::ItemSearchResponse#items > should return a collection of items > rspec ./spec/examples/amazon_spec.rb:28 # PITA::ItemSearchResponse#items > should have the some number less than or equal to #total_results > rspec ./spec/examples/amazon_spec.rb:40 # PITA::Item should extract asin > rspec ./spec/examples/amazon_spec.rb:45 # PITA::Item should extract > detail_page_url > rspec ./spec/examples/amazon_spec.rb:50 # PITA::Item should extract > manufacturer > rspec ./spec/examples/current_weather_spec.rb:9 # Weather should extract > observations > rspec ./spec/examples/current_weather_spec.rb:19 # WeatherObservation should > extract temperature > rspec ./spec/examples/current_weather_spec.rb:23 # WeatherObservation should > extract feels_like > rspec ./spec/examples/current_weather_spec.rb:28 # > WeatherObservation#current_condition should extract current_condition > rspec ./spec/examples/current_weather_spec.rb:32 # > WeatherObservation#current_condition should extract icon attribute > rspec ./spec/examples/dashed_elements_spec.rb:9 # GitHub::Commit should > extract committed date > rspec ./spec/examples/dashed_elements_spec.rb:13 # GitHub::Commit should > extract url > rspec ./spec/examples/dashed_elements_spec.rb:17 # GitHub::Commit should > extract id > > /usr/bin/ruby3.0 -Iexamples > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > ./spec/definition_spec.rb ./spec/examples/active_record_spec.rb > ./spec/examples/amazon_spec.rb ./spec/examples/current_weather_spec.rb > ./spec/examples/dashed_elements_spec.rb ./spec/examples/library_spec.rb > ./spec/examples/library_with_fines_spec.rb ./spec/examples/person_spec.rb > ./spec/examples/post_spec.rb ./spec/examples/search_query_spec.rb > ./spec/examples/twitter_spec.rb ./spec/reference_spec.rb ./spec/roxml_spec.rb > ./spec/xml/array_spec.rb ./spec/xml/attributes_spec.rb > ./spec/xml/encoding_spec.rb ./spec/xml/namespace_spec.rb > ./spec/xml/namespaces_spec.rb ./spec/xml/object_spec.rb > ./spec/xml/parser_spec.rb ./spec/xml/text_spec.rb failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-roxml/ruby-roxml_4.0.0-2+rebuild1633393804_amd64.build.txt signature.asc Description: PGP signature
Bug#996371: ruby-roo: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:
Source: ruby-roo Version: 2.8.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-roo was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > NoMethodError: >undefined method `encode' for URI:Module > # ./lib/roo/spreadsheet.rb:27:in `extension_for' > # ./lib/roo/spreadsheet.rb:8:in `open' > # ./spec/lib/roo/spreadsheet_spec.rb:39:in `block (5 levels) in (required)>' > > Finished in 4.28 seconds (files took 1.82 seconds to load) > 239 examples, 3 failures > > Failed examples: > > rspec ./spec/lib/roo/csv_spec.rb:27 # Roo::CSV#parse with headers: true > doesn't blow up > rspec ./spec/lib/roo/csv_spec.rb:41 # Roo::CSV#parse_with_clean_option with > clean: true doesn't blow up > rspec ./spec/lib/roo/spreadsheet_spec.rb:37 # Roo::Spreadsheet.open for a url > that is csv treats the url as CSV > > Coverage report generated for RSpec to /<>/coverage. 1395 / 1885 > LOC (74.01%) covered. > Stopped processing SimpleCov as a previous error not related to SimpleCov has > been detected > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-roo/ruby-roo_2.8.3-1+rebuild1633393685_amd64.build.txt signature.asc Description: PGP signature
Bug#996370: ruby-rgen: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-rgen Version: 0.8.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rgen was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rb > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-rgen/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-rgen/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 debian/ruby-tests.rb > Run options: --seed 22447 > > # Running: > > F..F..F...F.. > > Finished in 3.114809s, 83.7933 runs/s, 561.8322 assertions/s. > > 1) Failure: > MetamodelFromEcoreTest#test_many_to_many > [/<>/test/metamodel_builder_test.rb:619]: > Expected /In (\w+::)+BClassMM : Can not use a Symbol\(:notaaclass\) where a > (\w+::)+AClassMM is expected/ to match "In > MetamodelFromEcoreTest::MetamodelFromEcore::BClassMM : Can not use a > Symbol(notaaclass)(:notaaclass) where a > MetamodelFromEcoreTest::MetamodelFromEcore::AClassMM is expected". > > 2) Failure: > MetamodelFromEcoreTest#test_has_attr > [/<>/test/metamodel_builder_test.rb:229]: > Expected /In (\w+::)+SimpleClass : Can not use a Symbol\(:someSymbol\) where > a \[true,false\] is expected/ to match "In > MetamodelFromEcoreTest::MetamodelFromEcore::SimpleClass : Can not use a > Symbol(someSymbol)(:someSymbol) where a [true,false] is expected". > > 3) Failure: > MetamodelBuilderTest#test_many_to_many > [/<>/test/metamodel_builder_test.rb:619]: > Expected /In (\w+::)+BClassMM : Can not use a Symbol\(:notaaclass\) where a > (\w+::)+AClassMM is expected/ to match "In > MetamodelBuilderTest::TestMetamodel::BClassMM : Can not use a > Symbol(notaaclass)(:notaaclass) where a > MetamodelBuilderTest::TestMetamodel::AClassMM is expected". > > 4) Failure: > MetamodelBuilderTest#test_has_attr > [/<>/test/metamodel_builder_test.rb:229]: > Expected /In (\w+::)+SimpleClass : Can not use a Symbol\(:someSymbol\) where > a \[true,false\] is expected/ to match "In > MetamodelBuilderTest::TestMetamodel::SimpleClass : Can not use a > Symbol(someSymbol)(:someSymbol) where a [true,false] is expected". > > 261 runs, 1750 assertions, 4 failures, 0 errors, 0 skips > ERROR: Test "ruby3.0" failed. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rgen/ruby-rgen_0.8.4-1+rebuild1633393340_amd64.build.txt signature.asc Description: PGP signature
Bug#996369: ruby-responders: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-responders Version: 3.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-responders was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-responders/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"responders\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-responders/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test:." > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/action_controller/respond_with_api_test.rb" > "test/action_controller/respond_with_test.rb" > "test/action_controller/verify_requested_format_test.rb" > "test/responders/collection_responder_test.rb" > "test/responders/controller_method_test.rb" > "test/responders/flash_responder_test.rb" > "test/responders/http_cache_responder_test.rb" "test/test_helper.rb" -v > /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.7/lib/active_support/core_ext/hash/except.rb:12: > warning: method redefined; discarding old except > /usr/lib/ruby/vendor_ruby/tzinfo/ruby_core_support.rb:163: warning: > Object#taint is deprecated and will be removed in Ruby 3.2 > /usr/lib/ruby/vendor_ruby/tzinfo/ruby_core_support.rb:163: warning: > Object#tainted? is deprecated and will be removed in Ruby 3.2 > Run options: -v --seed 34640 > > # Running: > > ControllerMethodTest#test_foo_responder_gets_added = 0.04 s = . > ControllerMethodTest#test_bar_responder_gets_added = 0.00 s = . > NamespacedFlashResponderTest#test_sets_the_flash_message_based_on_the_current_controller > = 0.04 s = . > NamespacedFlashResponderTest#test_does_not_fallbacks_to_non_namespaced_controller_flash_message_if_disabled > = 0.01 s = . > NamespacedFlashResponderTest#test_fallbacks_to_non_namespaced_controller_flash_message > = 0.00 s = . > NamespacedFlashResponderTest#test_sets_the_flash_message_based_on_namespace_actions > = 0.00 s = . > NamespacedFlashResponderTest#test_does_not_fallbacks_to_namespaced_actions_if_disabled > = 0.00 s = . > VerifyRequestedFormatTest#test_strict_mode_calls_action_with_right_format = > 0.01 s = . > VerifyRequestedFormatTest#test_strict_mode_respects_only_option = 0.00 s = . > VerifyRequestedFormatTest#test_strict_mode_shouldnt_call_action = 0.00 s = . > HttpCacheResponderTest#test_does_not_set_cache_for_new_records = 0.00 s = . > HttpCacheResponderTest#test_does_not_use_cache_if_http_cache_is_false = 0.01 > s = . > HttpCacheResponderTest#test_work_with_an_empty_array = 0.02 s = . > HttpCacheResponderTest#test_works_for_nested_resources = 0.00 s = . > HttpCacheResponderTest#test_does_not_use_cache_unless_get_requests = 0.00 s = > . > HttpCacheResponderTest#test_returns_not_modified_if_return_is_cache_is_still_valid > = 0.00 s = . > HttpCacheResponderTest#test_does_not_set_cache_unless_get_requests = 0.01 s = > . > HttpCacheResponderTest#test_it_does_not_set_body_etag_for_single_resource = > 0.00 s = . > HttpCacheResponderTest#test_does_not_set_cache_if_http_cache_is_false = 0.00 > s = . > HttpCacheResponderTest#test_last_modified_at_is_set_with_single_resource_on_get > = 0.00 s = . > HttpCacheResponderTest#test_does_not_set_cache_for_collection = 0.00 s = . > HttpCacheResponderTest#test_refreshes_last_modified_if_cache_is_expired = > 0.01 s = . > CollectionResponderTest#test_collection_with_single_resource = 0.00 s = . > CollectionResponderTest#test_collection_respects_only_symbols = 0.00 s = . > CollectionResponderTest#test_collection_respects_isolated_namespace = 0.00 s > = . > CollectionResponderTest#test_collection_with_namespaced_resource = 0.00 s = . >
Bug#996368: ruby-remcached: FTBFS with ruby3.0: build blocks until timeout if tests fail
Source: ruby-remcached Version: 0.4.1-3 Severity: important Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-remcached was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > No examples found. > > > Finished in 0.5 seconds (files took 0.17408 seconds to load) > 0 examples, 0 failures, 3 errors occurred outside of examples > > rake aborted! > Command failed with status (1): [./debian/start_memcached_and_run.sh > ruby3] > /<>/debian/ruby-tests.rake:5:in `block in ' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Exiting. > dh_auto_install: error: dh_ruby --install > /<>/debian/ruby-remcached returned exit code 1 > make: *** [debian/rules:15: binary] Error 25 > dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned > exit status 2 > E: Build killed with signal TERM after 150 minutes of inactivity The tests for ruby3.0 failed because eventmachine was not rebuilt for ruby3.0 yet, but the dpkg-buildpackage process stayed stuck, because the memcached that is started for the tests was never really killed. I could easily reproduce this locally. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-remcached/ruby-remcached_0.4.1-3+rebuild1633393197_amd64.build.txt signature.asc Description: PGP signature
Bug#996366: ruby-regexp-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: (min..max).tap { |r| r.define_singleton_method(:minmax) { [min, max] } }
Source: ruby-regexp-parser
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-regexp-parser was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: (min..max).tap { |r| r.define_singleton_method(:minmax)
> { [min, max] } }
>
> FrozenError:
> can't modify frozen object: 2..4
> # ./lib/regexp_parser/expression.rb:84:in `define_singleton_method'
> # ./lib/regexp_parser/expression.rb:84:in `block in repetitions'
> # :90:in `tap'
> # ./lib/regexp_parser/expression.rb:84:in `repetitions'
> # ./lib/regexp_parser/expression/methods/match_length.rb:11:in
> `initialize'
> # ./lib/regexp_parser/expression/methods/match_length.rb:102:in `new'
> # ./lib/regexp_parser/expression/methods/match_length.rb:102:in
> `match_length'
> # ./spec/expression/methods/match_length_spec.rb:157:in `block (3
> levels) in '
>
> Finished in 5.25 seconds (files took 1.46 seconds to load)
> 1498 examples, 23 failures
>
> Failed examples:
>
> rspec ./spec/expression/base_spec.rb:88 # Regexp::Expression::Base
> #repetitions
> rspec ./spec/expression/methods/match_length_spec.rb:15 # Regexp::MatchLength
> fixed quantified
> rspec ./spec/expression/methods/match_length_spec.rb:16 # Regexp::MatchLength
> range quantified
> rspec ./spec/expression/methods/match_length_spec.rb:17 # Regexp::MatchLength
> nested quantified
> rspec ./spec/expression/methods/match_length_spec.rb:18 # Regexp::MatchLength
> open-end quantified
> rspec ./spec/expression/methods/match_length_spec.rb:24 # Regexp::MatchLength
> backreference
> rspec ./spec/expression/methods/match_length_spec.rb:25 # Regexp::MatchLength
> subexp call
> rspec ./spec/expression/methods/match_length_spec.rb:28 # Regexp::MatchLength
> quantified alternation
> rspec ./spec/expression/methods/match_length_spec.rb:65 #
> Regexp::MatchLength#include? fixed quantified
> rspec ./spec/expression/methods/match_length_spec.rb:72 #
> Regexp::MatchLength#include? variably quantified
> rspec ./spec/expression/methods/match_length_spec.rb:78 #
> Regexp::MatchLength#include? nested quantified
> rspec ./spec/expression/methods/match_length_spec.rb:95 #
> Regexp::MatchLength#include? called on leaf node
> rspec ./spec/expression/methods/match_length_spec.rb:105 #
> Regexp::MatchLength#fixed? fixed quantified
> rspec ./spec/expression/methods/match_length_spec.rb:106 #
> Regexp::MatchLength#fixed? variably quantified
> rspec ./spec/expression/methods/match_length_spec.rb:109 #
> Regexp::MatchLength#fixed? equal quantified branches
> rspec ./spec/expression/methods/match_length_spec.rb:110 #
> Regexp::MatchLength#fixed? unequal quantified branches
> rspec ./spec/expression/methods/match_length_spec.rb:115 #
> Regexp::MatchLength#each returns an Enumerator if called without a block
> rspec ./spec/expression/methods/match_length_spec.rb:123 #
> Regexp::MatchLength#each is aware of limit option even if called without a
> block
> rspec ./spec/expression/methods/match_length_spec.rb:130 #
> Regexp::MatchLength#each is limited to 1000 iterations in case there are
> infinite match lengths
> rspec ./spec/expression/methods/match_length_spec.rb:134 #
> Regexp::MatchLength#each scaffolds the Enumerable interface
> rspec ./spec/expression/methods/match_length_spec.rb:142 #
> Regexp::MatchLength#endless_each returns an Enumerator if called without a
> block
> rspec ./spec/expression/methods/match_length_spec.rb:150 #
> Regexp::MatchLength#endless_each never stops iterating for infinite match
> lengths
> rspec ./spec/expression/methods/match_length_spec.rb:156 #
> Regexp::MatchLength#inspect is nice
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-regexp-parser/ruby-regexp-parser_1.7.1-1+rebuild1633393116_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996364: ruby-recursive-open-struct: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: alias_method :modifiable?, :modifiable
Source: ruby-recursive-open-struct
Version: 1.1.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-recursive-open-struct was found to fail to build in that
situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Failure/Error: alias_method :modifiable?, :modifiable
>
> NameError:
> undefined method `modifiable' for class `RecursiveOpenStruct'
> Did you mean? module
> # ./lib/recursive_open_struct.rb:84:in `alias_method'
> # ./lib/recursive_open_struct.rb:84:in `'
> # ./lib/recursive_open_struct.rb:16:in `'
> # ./spec/recursive_open_struct/recursion_spec.rb:2:in `'
> Run options: include {:focus=>true}
>
> All examples were filtered out; ignoring {:focus=>true}
> No examples found.
>
> Finished in 0.00011 seconds (files took 0.40327 seconds to load)
> 0 examples, 0 failures, 7 errors occurred outside of examples
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-recursive-open-struct/ruby-recursive-open-struct_1.1.1-1+rebuild1633392915_amd64.build.txt
signature.asc
Description: PGP signature
Bug#996363: ruby-rbpdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test: Image get image file test(RbpdfHttpTest): NoMethodError: undefined method `shutdown' for nil:NilClass
Source: ruby-rbpdf Version: 1.20.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rbpdf was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Error: test: Image get image file test(RbpdfHttpTest): NoMethodError: > undefined method `shutdown' for nil:NilClass > /<>/test/rbpdf_http_test.rb:73:in `teardown' > === > : (0.076125) > RbpdfPageTest: > test: Basic Page content test: .: (0.016013) > test: circle content: .: (0.002147) > test: viewerpreferences test: .: (0.009738) > test: write English and Persian Sunday content test:.: (0.040401) > test: write Persian Sunday content test:.: (0.018405) > test: write content RTL test: .: (0.014958) > test: write content back slash test:.: (0.010998) > test: write content test: .: (0.002775) > RbpdfTest: > test: Bidi: .: (0.003737) > test: Bidi English and Persian test:.: (0.016793) > test: Bidi Japanese test: .: (0.002068) > test: Bidi Persian Monday forcertl test:.: (0.026487) > test: Bidi Persian Monday test: .: (0.002678) > test: Bidi Persian Sunday forcertl test:.: (0.002213) > test: Bidi Persian Sunday test: .: (0.020082) > test: Bidi Persian and English test:.: (0.002842) > test: Bidi arabic test: .: (0.002191) > test: Bidi ascii colon test:.: (0.015445) > test: Bidi ascii numeric space test:.: (0.002643) > test: Bidi ascii space test:.: (0.002923) > test: Bidi date test: .: (0.018149) > test: Bidi subset font test:.: (0.001524) > test: Cell link with Close and output PDF document test:.: (0.024133) > test: Dom Basic test[Simple Text]: .: (0.010209) > test: Dom Basic test[Back Slash Text]: .: (0.001992) > test: Dom Basic test[Simple Tag]: .: (0.010288) > test: Dom Basic test[pre Tag]: .: (0.011303) > test: Dom Basic test[pre code Tag]: .: (0.002410) > test: Dom Basic test[pre code span Tag]:.: (0.010691) > test: Dom Basic test[Error Tag (doble colse tag)]: .: (0.001804) > test: Dom Basic test[Attribute]:.: (0.010585) > test: Dom Basic test[Table border]: .: (0.002507) > test: Dom Basic test[Table td Width]: .: (0.014737) > test: Dom Basic test[Dom open angled bracket "<"]: .: (0.014486) > test: Dom Basic test[Dom self close tag]: .: (0.017457) > test: Dom HTMLTagHandler Basic test:.: (0.015236) > test: Dom HTMLTagHandler DIR test[LTR]: .: (0.016512) > test: Dom HTMLTagHandler DIR test[RTL]: .: (0.016407) > test: Dom HTMLTagHandler img y position with height attribute test: E, > [2021-10-05T00:14:46.580331 #990090] ERROR -- : pdf: Image: error: RBPDF > error: Image file is not found. : /public/ng.png > .: (0.004269) > test: Dom HTMLTagHandler img y position without height attribute test:E, > [2021-10-05T00:14:46.601847 #990090] ERROR -- : pdf: Image: error: RBPDF > error: Image file is not found. : /public/ng.png > .: (0.021489) > test: Dom pre tag test: .: (0.054893) > test: Dom self close tag test: .: (0.005654) > test: Examples test[001 : Default Header and Footer]: .: (1.407423) > test: Examples test[002 : Removing Header and Footer]:.: (0.052677) > test: Examples test[003 : Custom Header and Footer]:.: (0.106227) > test: Examples test[004 : Cell stretching]: .: (0.102724) > test: Examples test[005 : Multicell]: .: (0.432354) > test: Examples test[006 : write_html and RTL support]:E, > [2021-10-05T00:14:49.246850 #990090] ERROR -- : pdf: Image: error: RBPDF > error: Image file is not found. : > /<>/example/rails/app/controllers/../../public/tiger.ai > .: (4.710111) > test: Examples test[007 : Two independent columns with write_htmlcell()]: > .: (2.698085) > test: Examples test[008 : Include external UTF-8 text file]:.: > (1.142124) > test: Examples test[009 : Test Image]: E, >
Bug#996362: ruby-raindrops: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-raindrops Version: 0.19.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-raindrops was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-raindrops/usr/share/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"raindrops\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-raindrops/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0:/<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby:. > > GEM_PATH=/<>/debian/ruby-raindrops/usr/share/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/test_aggregate_pmq.rb" "test/test_last_data_recv_unicorn.rb" > "test/test_linux.rb" "test/test_linux_all_tcp_listen_stats_leak.rb" > "test/test_linux_middleware.rb" "test/test_middleware.rb" > "test/test_middleware_unicorn.rb" "test/test_middleware_unicorn_ipv6.rb" > "test/test_raindrops.rb" "test/test_raindrops_gc.rb" "test/test_struct.rb" > "test/test_tcp_info.rb" -v > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/aggregate/pmq.rb:145: > warning: mismatched indentations at 'ensure' with 'def' at 123 > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/aggregate/pmq.rb:178: > warning: mismatched indentations at 'rescue' with 'def' at 176 > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/aggregate/pmq.rb:184: > warning: mismatched indentations at 'rescue' with 'def' at 182 > /usr/lib/ruby/vendor_ruby/aggregate.rb:29: warning: parentheses after method > name is interpreted as an argument list, not a decomposed argument > /usr/lib/ruby/vendor_ruby/aggregate.rb:207: warning: parentheses after method > name is interpreted as an argument list, not a decomposed argument > /usr/lib/ruby/vendor_ruby/aggregate.rb:265: warning: parentheses after method > name is interpreted as an argument list, not a decomposed argument > W: cannot load such file -- posix_mq skipping > /<>/test/test_aggregate_pmq.rb > W: cannot load such file -- unicorn skipping test since Rack or Unicorn was > not found > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/aggregate/pmq.rb:145: > warning: mismatched indentations at 'ensure' with 'def' at 123 > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/aggregate/pmq.rb:178: > warning: mismatched indentations at 'rescue' with 'def' at 176 > /<>/debian/ruby-raindrops/usr/lib/ruby/vendor_ruby/raindrops/aggregate/pmq.rb:184: > warning: mismatched indentations at 'rescue' with 'def' at 182 > W: cannot load such file -- posix_mq skipping > /<>/test/test_last_data_recv_unicorn.rb > /<>/test/test_linux.rb:73: warning: assigned but unused variable > - us > /<>/test/test_linux.rb:154: warning: mismatched indentations at > 'ensure' with 'def' at 132 > /<>/test/test_linux_all_tcp_listen_stats_leak.rb:40: warning: > mismatched indentations at 'ensure' with 'def' at 16 > /<>/test/ipv6_enabled.rb:5: warning: mismatched indentations at > 'rescue' with 'def' at 1 > /<>/test/test_raindrops.rb:137: warning: mismatched indentations > at 'rescue' with 'def' at 123 > /<>/test/test_struct.rb:30: warning: method redefined; > discarding old test_dup > /<>/test/test_raindrops.rb:80: warning: previous definition of > test_dup was here > /<>/test/test_tcp_info.rb:63: warning: mismatched indentations > at 'ensure' with 'def' at 53 > Loaded suite > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader > Started > TestLinux: > test_unix: E > === > Error:
Bug#996353: ruby-rack: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-rack Version: 2.2.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rack was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.0 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-rack/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -e gem\ \"rack\" > > ┌──┐ > │ Run tests for ruby3.0 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=/<>/debian/ruby-rack/usr/lib/ruby/vendor_ruby:. > GEM_PATH=/<>/debian/ruby-rack/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0 > ruby3.0 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.0 -I"lib:test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/spec_auth_basic.rb" "test/spec_auth_digest.rb" > "test/spec_body_proxy.rb" "test/spec_builder.rb" "test/spec_cascade.rb" > "test/spec_chunked.rb" "test/spec_common_logger.rb" > "test/spec_conditional_get.rb" "test/spec_config.rb" > "test/spec_content_length.rb" "test/spec_content_type.rb" > "test/spec_deflater.rb" "test/spec_directory.rb" "test/spec_etag.rb" > "test/spec_events.rb" "test/spec_files.rb" "test/spec_handler.rb" > "test/spec_head.rb" "test/spec_lint.rb" "test/spec_lobster.rb" > "test/spec_lock.rb" "test/spec_logger.rb" "test/spec_media_type.rb" > "test/spec_method_override.rb" "test/spec_mime.rb" "test/spec_mock.rb" > "test/spec_multipart.rb" "test/spec_null_logger.rb" "test/spec_recursive.rb" > "test/spec_request.rb" "test/spec_response.rb" > "test/spec_rewindable_input.rb" "test/spec_runtime.rb" > "test/spec_sendfile.rb" "test/spec_server.rb" > "test/spec_session_abstract_id.rb" "test/spec_session_abstract_persisted.rb" > "test/spec_session_abstract_persisted_secure_secure_session_hash.rb" > "test/spec_session_abstract_session_hash.rb" "test/spec_session_cookie.rb" > "test/spec_session_pool.rb" "test/spec_show_exceptions.rb" > "test/spec_show_status.rb" "test/spec_static.rb" > "test/spec_tempfile_reaper.rb" "test/spec_thin.rb" "test/spec_urlmap.rb" > "test/spec_utils.rb" "test/spec_version.rb" "test/spec_webrick.rb" > "test/gemloader.rb" > > File does not exist: webrick > > rake aborted! > Command failed with status (1): [ruby -I"lib:test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/spec_auth_basic.rb" "test/spec_auth_digest.rb" > "test/spec_body_proxy.rb" "test/spec_builder.rb" "test/spec_cascade.rb" > "test/spec_chunked.rb" "test/spec_common_logger.rb" > "test/spec_conditional_get.rb" "test/spec_config.rb" > "test/spec_content_length.rb" "test/spec_content_type.rb" > "test/spec_deflater.rb" "test/spec_directory.rb" "test/spec_etag.rb" > "test/spec_events.rb" "test/spec_files.rb" "test/spec_handler.rb" > "test/spec_head.rb" "test/spec_lint.rb" "test/spec_lobster.rb" > "test/spec_lock.rb" "test/spec_logger.rb" "test/spec_media_type.rb" > "test/spec_method_override.rb" "test/spec_mime.rb" "test/spec_mock.rb" > "test/spec_multipart.rb" "test/spec_null_logger.rb" "test/spec_recursive.rb" > "test/spec_request.rb" "test/spec_response.rb" > "test/spec_rewindable_input.rb" "test/spec_runtime.rb" > "test/spec_sendfile.rb" "test/spec_server.rb" > "test/spec_session_abstract_id.rb" "test/spec_session_abstract_persisted.rb" > "test/spec_session_abstract_persisted_secure_secure_session_hash.rb" > "test/spec_session_abstract_session_hash.rb" "test/spec_session_cookie.rb" > "test/spec_session_pool.rb" "test/spec_show_exceptions.rb" > "test/spec_show_status.rb" "test/spec_static.rb" > "test/spec_tempfile_reaper.rb" "test/spec_thin.rb" "test/spec_urlmap.rb" > "test/spec_utils.rb" "test/spec_version.rb" "test/spec_webrick.rb" > "test/gemloader.rb" ] > > Tasks: TOP => default => test > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Note that webrick
Bug#996352: ruby-rack-timeout: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number of arguments (given 2, expected 1)
Source: ruby-rack-timeout Version: 0.5.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rack-timeout was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > Error: test_zero_wait_timeout(EnvSettingsTest): ArgumentError: wrong number > of arguments (given 2, expected 1) > /<>/debian/ruby-rack-timeout/usr/lib/ruby/vendor_ruby/rack/timeout/core.rb:67:in > `initialize' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:102:in `new' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:102:in `block in use' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `block in to_app' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `each' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `inject' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:171:in `to_app' > /usr/lib/ruby/vendor_ruby/rack/builder.rb:177:in `call' > /usr/lib/ruby/vendor_ruby/rack/mock_session.rb:30:in `request' > /usr/lib/ruby/vendor_ruby/rack/test.rb:249:in `process_request' > /usr/lib/ruby/vendor_ruby/rack/test.rb:59:in `get' > /usr/lib/ruby/3.0.0/forwardable.rb:238:in `get' > /<>/test/env_settings_test.rb:15:in `block in > test_zero_wait_timeout' > 12: > 13: def test_zero_wait_timeout > 14: with_env(RACK_TIMEOUT_WAIT_TIMEOUT: 0) do > => 15: get "/", "", 'HTTP_X_REQUEST_START' => time_in_msec(Time.now - > 100) > 16: assert last_response.ok? > 17: end > 18: end > /<>/test/test_helper.rb:36:in `with_env' > /<>/test/env_settings_test.rb:14:in `test_zero_wait_timeout' > === > : (0.001047) > > Finished in 0.032033303 seconds. > --- > 5 tests, 3 assertions, 3 failures, 2 errors, 0 pendings, 0 omissions, 0 > notifications > 0% passed > --- > 156.09 tests/s, 93.65 assertions/s > rake aborted! > Command failed with status (1): [ruby -w -I"test" > /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb > "test/basic_test.rb" "test/env_settings_test.rb" -v] > > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rack-timeout/ruby-rack-timeout_0.5.1-2+rebuild1633391987_amd64.build.txt signature.asc Description: PGP signature
Bug#996350: ruby-rabl: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
Source: ruby-rabl
Version: 0.13.1-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-rabl was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
>
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0
> │
> └──┘
>
> GEM_PATH=/<>/debian/ruby-rabl/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
> ruby3.0 -e gem\ \"rabl\"
>
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-test-files.yaml
> │
> └──┘
>
> RUBYLIB=/<>/debian/ruby-rabl/usr/lib/ruby/vendor_ruby:.
> GEM_PATH=/<>/debian/ruby-rabl/usr/share/rubygems-integration/all:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
> ruby3.0 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\
> \{\ \|f\|\ require\ f\ \}
> ...E.E.E
> ERROR
> Rabl::Builder #glue asserts that it generates the glue attributes => On
> subject #,
> unexpected method invocation:
> object_to_engine(# @name="rabl", @first="bob", @float=1234.56,
> @hobbies=[#],
> @twitter="rablgem">, root: false)
> expected invocations:
> - object_to_engine(# @name="rabl", @first="bob", @float=1234.56,
> @hobbies=[#],
> @twitter="rablgem">, {:root=>false}) occured
> at /usr/lib/ruby/vendor_ruby/riot.rb:129:in `block in '
> at /usr/lib/ruby/vendor_ruby/riot.rb:38:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/reporter.rb:46:in `summarize'
> at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block in run'
> at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `each'
> at /usr/lib/ruby/vendor_ruby/riot.rb:39:in `block (2 levels) in run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:98:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `run_sub_contexts'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `each'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:146:in `block in
> run_sub_contexts'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:97:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `local_run'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:108:in `each'
> at /usr/lib/ruby/vendor_ruby/riot/context.rb:109:in `block in local_run'
> at /usr/lib/ruby/vendor_ruby/riot/rr.rb:33:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/assertion.rb:51:in `run'
> at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `evaluate'
> at /usr/lib/ruby/vendor_ruby/riot/situation.rb:61:in `instance_eval'
> at /<>/test/builder_test.rb:233:in `block (3 levels) in (required)>'
> at /<>/lib/rabl/builder.rb:49:in `to_hash'
> at /<>/lib/rabl/builder.rb:248:in `cache_results'
> at /<>/lib/rabl/builder.rb:55:in `block in to_hash'
> at /<>/lib/rabl/builder.rb:119:in `merge_engines_into_result'
> at /<>/lib/rabl/builder.rb:35:in `engines'
> at /<>/lib/rabl/builder.rb:113:in `compile_settings'
> at /<>/lib/rabl/builder.rb:113:in `each'
> at /<>/lib/rabl/builder.rb:114:in `block in compile_settings'
> at /<>/lib/rabl/builder.rb:186:in `glue'
> at /usr/lib/ruby/vendor_ruby/rr/injections/double_injection.rb:161:in
> `object_to_engine'
> at /usr/lib/ruby/vendor_ruby/rr/injections/double_injection.rb:45:in
> `dispatch_method'
> at /usr/lib/ruby/vendor_ruby/rr/injections/double_injection.rb:226:in
> `dispatch_method'
> at /usr/lib/ruby/vendor_ruby/rr/method_dispatches/method_dispatch.rb:28:in
> `call'
> at
> /usr/lib/ruby/vendor_ruby/rr/method_dispatches/base_method_dispatch.rb:93:in
> `double_not_found_error'
>
> ERROR
> Rabl::Builder #glue asserts that it does not generate new attributes if no
> glue attributes are present => On subject #,
> unexpected method invocation:
> object_to_engine(# @name="rabl", @first="bob", @float=1234.56,
> @hobbies=[#],
> @twitter="rablgem">, root:
Bug#996351: ruby-rack-oauth2: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:
Source: ruby-rack-oauth2 Version: 1.16.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-rack-oauth2 was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > NoMethodError: >undefined method `encode' for URI:Module > # ./lib/rack/oauth2/util.rb:8:in `rfc3986_encode' > # ./spec/rack/oauth2/util_spec.rb:13:in `block (3 levels) in (required)>' > # ./spec/rack/oauth2/util_spec.rb:14:in `block (3 levels) in (required)>' > > Finished in 3.62 seconds (files took 5.24 seconds to load) > 379 examples, 1 failure > > Failed examples: > > rspec ./spec/rack/oauth2/util_spec.rb:14 # Rack::OAuth2::Util.rfc3986_encode > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-rack-oauth2/ruby-rack-oauth2_1.16.0-1+rebuild1633391818_amd64.build.txt signature.asc Description: PGP signature
Bug#996348: ruby-process-daemon: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick
Source: ruby-process-daemon Version: 1.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-process-daemon was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > cannot load such file -- webrick > # ./spec/process/daemon/daemonize_spec.rb:23:in `' > > Finished in 0.6 seconds (files took 0.99452 seconds to load) > 0 examples, 0 failures, 3 errors occurred outside of examples > > /usr/bin/ruby3.0 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.0" failed: Note that webrick has been removed from the standard library. It's already been packaged and is currently in NEW, but this package now needs an explicit dependency on it. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-process-daemon/ruby-process-daemon_1.0.1-2+rebuild1633391208_amd64.build.txt signature.asc Description: PGP signature
