Redmine

/home/redmine-6.0.0# rake generate_secret_token
WARN: Unresolved or ambiguous specs during Gem::Specification.reset:
      stringio (>= 0)
      Available/installed versions of this gem:
      - 3.1.2
      - 3.1.1
WARN: Clearing out unresolved specs. Try 'gem cleanup <gem>'
Please report a bug if this causes problems.
rake aborted!
LoadError: cannot load such file -- svg_sprite (LoadError)
/home/redmine-6.0.0/lib/tasks/icons.rake:19:in `<top (required)>'
/home/redmine-6.0.0/Rakefile:7:in `<top (required)>'
(See full trace by running task with --trace)

/home/redmine-6.0.0# rake --trace generate_secret_token
WARN: Unresolved or ambiguous specs during Gem::Specification.reset:
      stringio (>= 0)
      Available/installed versions of this gem:
      - 3.1.2
      - 3.1.1
WARN: Clearing out unresolved specs. Try 'gem cleanup <gem>'
Please report a bug if this causes problems.
rake aborted!
LoadError: cannot load such file -- svg_sprite (LoadError)
/usr/lib64/ruby/3.3.0/bundled_gems.rb:69:in `require'
/usr/lib64/ruby/3.3.0/bundled_gems.rb:69:in `block (2 levels) in replace_require'
/usr/lib64/ruby/gems/3.3.0/gems/zeitwerk-2.7.1/lib/zeitwerk/core_ext/kernel.rb:34:in `require'
/home/redmine-6.0.0/lib/tasks/icons.rake:19:in `<top (required)>'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/engine.rb:683:in `load'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/engine.rb:683:in `block in run_tasks_blocks'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/engine.rb:683:in `each'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/engine.rb:683:in `run_tasks_blocks'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/application.rb:554:in `run_tasks_blocks'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/engine.rb:470:in `load_tasks'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/railtie.rb:226:in `public_send'
/usr/lib64/ruby/gems/3.3.0/gems/railties-7.2.2/lib/rails/railtie.rb:226:in `method_missing'
/home/redmine-6.0.0/Rakefile:7:in `<top (required)>'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/rake_module.rb:29:in `load'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/rake_module.rb:29:in `load_rakefile'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/application.rb:740:in `raw_load_rakefile'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/application.rb:126:in `block in load_rakefile'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/application.rb:214:in `standard_exception_handling'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/application.rb:125:in `load_rakefile'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/application.rb:82:in `block in run'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/application.rb:214:in `standard_exception_handling'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/lib/rake/application.rb:80:in `run'
/usr/lib64/ruby/gems/3.3.0/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
/usr/bin/rake:25:in `load'
/usr/bin/rake:25:in `<main>'

# ruby --version
ruby 3.3.6 (2024-11-05 revision 75015d4c1f) [x86_64-linux]

# gem list | grep svg
svg_optimizer (0.3.0)
svg_sprite (1.0.3)

ruby 3.2.6 + redmine 5.1.4 is fine.
ruby 3.2.6 + redmine 6.0.0 is same error.

Marius BĂLTEANU wrote in #note-1:

Thanks for reporting the issue, but that is a warning and not an error.

The log shows the following error in addition to the warning.

LoadError: cannot load such file -- svg_sprite (LoadError)

Marius, could you review the patch and release Redmine 6.0.1?

Thank you for providing your patch.
I was running the below command.

# bundle config set without 'development test rmagick postgresql sqlite'
# bundle install

This patch solved the problem.

Go MAEDA wrote in #note-6:

Marius, could you review the patch and release Redmine 6.0.1?

Yes, we will do the release today!

The commit message for r23256 is 'Fixes "Unresolved or ambiguous specs during Gem::Specification.reset"', but please note that it does not address this warning. Instead, it fixes the issue "LoadError: cannot load such file -- svg_sprite (LoadError)".

Thanks for pointing this out. Do you prefer to revert and commit the fix again with the correct message?