Source: ruby-mail Version: 2.7.1+dfsg1-1.1 Severity: important 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 ruby-mail with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > expected NoMethodError with "Can not decode an entire message, try > calling #decoded on the various fields and body or parts if it is a multipart > message.", got #<NoMethodError: Can not decode an entire message, try calling > #decoded on the various fields and bod...lling #decoded on the various fields > and body or parts if it is a multipart message.' > ^^^^^> with backtrace: > # /<<PKGBUILDDIR>>/lib/mail/message.rb:1912:in `decoded' > # /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:1525:in `block (4 > levels) in <top (required)>' > # /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:1525:in `block (3 > levels) in <top (required)>' > # /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:1525:in `block (3 levels) > in <top (required)>' > > Finished in 1.49 seconds (files took 0.51284 seconds to load) > 1647 examples, 7 failures, 3 pending > > Failed examples: > > rspec /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:199 # Mail::Message > initialization YAML serialization should serialize the basic information to > YAML > rspec /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:210 # Mail::Message > initialization YAML serialization should deserialize after serializing > rspec /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:216 # Mail::Message > initialization YAML serialization should serialize a Message with a custom > delivery_handler > rspec /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:223 # Mail::Message > initialization YAML serialization should load a serialized delivery handler > rspec /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:229 # Mail::Message > initialization YAML serialization should not deserialize a delivery_handler > that does not exist > rspec /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:237 # Mail::Message > initialization YAML serialization should handle multipart mail > rspec /<<PKGBUILDDIR>>/spec/mail/message_spec.rb:1512 # Mail::Message output > should raise an error and message if you try and call decoded on a multipart > email > > /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 > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-mail/ruby-mail_2.7.1+dfsg1-1.1+rebuild1663007790_amd64-2022-09-12T18:36:31Z.build To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on when you try this, it might mean installing ruby-all-dev from experimental, or if the transition has already started, a normal build on unstable will be enough. 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
