Your message dated Fri, 21 Oct 2022 13:19:28 +0000
with message-id <e1olrvs-0094zo...@fasolo.debian.org>
and subject line Bug#1019606: fixed in roodi 5.0.0-5
has caused the Debian Bug report #1019606,
regarding roodi: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: YAML.load_file config_file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1019606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: roodi
Version: 5.0.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild roodi with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> Failure/Error: YAML.load_file config_file
>
> Psych::DisallowedClass:
> Tried to load unspecified class: Regexp
> # (eval):2:in `regexp'
> # ./lib/roodi/core/runner.rb:135:in `load_config'
> # ./lib/roodi/core/runner.rb:126:in `load_checks'
> # ./lib/roodi/core/runner.rb:72:in `check'
> # ./lib/roodi/core/runner.rb:81:in `check_content'
> # ./spec/roodi/core/runner_spec.rb:52:in `block (4 levels) in <top
> (required)>'
>
> Deprecation Warnings:
>
> Using `should_not` 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
> /<<PKGBUILDDIR>>/spec/roodi/checks/abc_metric_method_check_spec.rb:12:in
> `verify_content_score'.
>
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly
> enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly
> enable `:should` instead. Called from
> /<<PKGBUILDDIR>>/spec/roodi/core/runner_spec.rb:58:in `block (3 levels) in
> <top (required)>'.
>
>
> 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.
>
> 2 deprecation warnings total
>
> Finished in 0.09081 seconds (files took 0.39761 seconds to load)
> 115 examples, 5 failures
>
> Failed examples:
>
> rspec ./spec/roodi/core/runner_spec.rb:7 # Roodi::Core::Runner running
> against a file adds an error if file is not valid ruby
> rspec ./spec/roodi/core/runner_spec.rb:17 # Roodi::Core::Runner running
> against a file checks that one file
> rspec ./spec/roodi/core/runner_spec.rb:24 # Roodi::Core::Runner running
> against a directory checks all files in that directory recursively
> rspec ./spec/roodi/core/runner_spec.rb:31 # Roodi::Core::Runner running
> without specifying files or directory checks all files in that directory
> recursively
> rspec ./spec/roodi/core/runner_spec.rb:43 # Roodi::Core::Runner configuration
> given a custom config file uses check from it
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> spec/roodi/checks/abc_metric_method_check_spec.rb
> spec/roodi/checks/assignment_in_conditional_check_spec.rb
> spec/roodi/checks/case_missing_else_check_spec.rb
> spec/roodi/checks/class_line_count_check_spec.rb
> spec/roodi/checks/class_name_check_spec.rb
> spec/roodi/checks/class_variable_check_spec.rb
> spec/roodi/checks/control_coupling_check_spec.rb
> spec/roodi/checks/core_method_override_check_spec.rb
> spec/roodi/checks/cyclomatic_complexity_block_check_spec.rb
> spec/roodi/checks/cyclomatic_complexity_method_check_spec.rb
> spec/roodi/checks/empty_rescue_body_check_spec.rb
> spec/roodi/checks/for_loop_check_spec.rb
> spec/roodi/checks/method_line_count_check_spec.rb
> spec/roodi/checks/method_name_check_spec.rb
> spec/roodi/checks/module_line_count_check_spec.rb
> spec/roodi/checks/module_name_check_spec.rb
> spec/roodi/checks/npath_complexity_method_check_spec.rb
> spec/roodi/checks/parameter_number_check_spec.rb
> spec/roodi/core/runner_spec.rb spec/roodi_task_spec.rb failed
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/roodi/roodi_5.0.0-4+rebuild1663007308_amd64-2022-09-12T18:28:29Z.build
To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
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
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: roodi
Source-Version: 5.0.0-5
Done: Cédric Boutillier <bou...@debian.org>
We believe that the bug you reported is fixed in the latest version of
roodi, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Cédric Boutillier <bou...@debian.org> (supplier of updated roodi package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 19 Oct 2022 17:12:39 +0200
Source: roodi
Architecture: source
Version: 5.0.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Cédric Boutillier <bou...@debian.org>
Closes: 1019606
Changes:
roodi (5.0.0-5) unstable; urgency=medium
.
* Team upload
.
[ Debian Janitor ]
* Remove constraints unnecessary since buster
.
[ Cédric Boutillier ]
* Change homepage from (dead) rubyforge to github.
* Bump Standards-Version to 4.6.1 (no changes needed)
* Add yaml_unsafe_load.patch to load unsafely YAML configuration also with
ruby3.1 (Closes: #1019606)
* Drop deprecated alternative dependency on ruby-interpreter
* Set Rules-Requires-Root to no
Checksums-Sha1:
f606c025ff31b53a8dcfd99745762fe611e317d4 1378 roodi_5.0.0-5.dsc
17d1511dc918a119b29e31dafed01562456fc0e0 5696 roodi_5.0.0-5.debian.tar.xz
a66822f3ce72bb0445eae7b016792378580848c2 9342 roodi_5.0.0-5_amd64.buildinfo
Checksums-Sha256:
1e2bb859e091066a0eb1c95cff806a4d0575cd4920bd3dab04c93beb5516b9af 1378
roodi_5.0.0-5.dsc
9f9a59bec7505515c4624479251344cb61c510e7199348a80b68d13448b67dcb 5696
roodi_5.0.0-5.debian.tar.xz
58789ae291dbf1ebc87a343b31343f167853349a67679f7523aa492e2a2fdc49 9342
roodi_5.0.0-5_amd64.buildinfo
Files:
8d24f627ba68a597249d650e13576d03 1378 ruby optional roodi_5.0.0-5.dsc
2263015f620103ccdab4ea71a0087629 5696 ruby optional roodi_5.0.0-5.debian.tar.xz
78420f3185987b76800e99971fc01295 9342 ruby optional
roodi_5.0.0-5_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCY1KXxQAKCRBSaZq2P58r
w3n0AQCe2XULPknv3lIGrnAshYTY8STVTK2DKC8HGNItzVDZUwD/T94w69CTqmP+
2XrZ0X1ba1nSvwwRoOoPfPle7G6BwwY=
=BYar
-----END PGP SIGNATURE-----
--- End Message ---
