Source: ruby-mini-magick
Version: 4.9.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>      NoMethodError:
>        undefined method `<<' for #<Hash:0x000055d2a8dcf0e8>
>        Did you mean?  <
>      # ./lib/mini_magick/image/info.rb:139:in `block in details'
>      # ./lib/mini_magick/image/info.rb:128:in `each'
>      # ./lib/mini_magick/image/info.rb:128:in `each_with_object'
>      # ./lib/mini_magick/image/info.rb:128:in `details'
>      # ./lib/mini_magick/image/info.rb:31:in `[]'
>      # ./lib/mini_magick/image.rb:141:in `block in attribute'
>      # ./spec/lib/mini_magick/image_spec.rb:478:in `block (7 levels) in <top 
> (required)>'
>      # ./spec/lib/mini_magick/image_spec.rb:477:in `block (6 levels) in <top 
> (required)>'
>      # ./spec/spec_helper.rb:19:in `block (3 levels) in <top (required)>'
> 
> Finished in 1.67 seconds (files took 0.47683 seconds to load)
> 76 examples, 1 failure
> 
> Failed examples:
> 
> rspec './spec/lib/mini_magick/image_spec.rb[1:1:19:3:1]' # With ImageMagick 
> MiniMagick::Image#details when verbose information includes a clipping path 
> does not hang when parsing verbose data
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/ruby-mini-magick_4.9.5-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to