Your message dated Mon, 05 Dec 2022 01:06:18 +0000 with message-id <e1p1zw2-004ujq...@fasolo.debian.org> and subject line Bug#1019635: fixed in ruby-mail 2.7.1+dfsg1-2 has caused the Debian Bug report #1019635, regarding ruby-mail: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 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.' 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.) -- 1019635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Source: ruby-mail Source-Version: 2.7.1+dfsg1-2 Done: Antonio Terceiro <terce...@debian.org> We believe that the bug you reported is fixed in the latest version of ruby-mail, 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. Antonio Terceiro <terce...@debian.org> (supplier of updated ruby-mail 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: SHA256 Format: 1.8 Date: Sun, 04 Dec 2022 15:21:19 -0300 Source: ruby-mail Architecture: source Version: 2.7.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team <pkg-ruby-extras-maintain...@lists.alioth.debian.org> Changed-By: Antonio Terceiro <terce...@debian.org> Closes: 1019635 Changes: ruby-mail (2.7.1+dfsg1-2) unstable; urgency=medium . * Team upload . [ Utkarsh Gupta ] * Add salsa-ci.yml . [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.4.1, no changes needed. * Update standards version to 4.5.0, no changes needed. . [ Cédric Boutillier ] * Update team name * Add .gitattributes to keep unwanted files out of the source package . [ Antonio Terceiro ] * Add patches to fix tests with ruby3.1 (Closes: #1019635) Checksums-Sha1: 766aba6fa685422c1a51b1339e3c4bb41a2af51f 2088 ruby-mail_2.7.1+dfsg1-2.dsc 8b4b2f59f8326da454b4d8b08040cae64a4c6d08 6024 ruby-mail_2.7.1+dfsg1-2.debian.tar.xz a6500cc772f73614b342db29b4512b629a04f206 9730 ruby-mail_2.7.1+dfsg1-2_amd64.buildinfo Checksums-Sha256: a42aa23c0648b8dc08849dccf93bb0bd3f0ae3d190f5dc9dccad94b967317d65 2088 ruby-mail_2.7.1+dfsg1-2.dsc 8400ef21cab9f4daeb85a4df3c0447f49a56596d6ccc6e528520f4b3cfb73119 6024 ruby-mail_2.7.1+dfsg1-2.debian.tar.xz 08560d5137359be4bfa4b1f7f97f3da6d35aab753b36bbc8677fce6607008ee5 9730 ruby-mail_2.7.1+dfsg1-2_amd64.buildinfo Files: 9677f07351649e5cc9fefceab03ea984 2088 ruby optional ruby-mail_2.7.1+dfsg1-2.dsc a1497d1787644e5e3a6ec7f6eb6820e2 6024 ruby optional ruby-mail_2.7.1+dfsg1-2.debian.tar.xz d6d9b9e1dc88667e83ac34cfbe2659ee 9730 ruby optional ruby-mail_2.7.1+dfsg1-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmONOAcACgkQ/A2xu81G C96fVA/8CLAGQVMkbMPJNb5pe+B+TgtguhURaiwAH+5cJ1ZGCaLmM/0FfcLo1Y/E T675FhhTqX5jaxUHuWVhYRsR4j5W90O1R1EWaZBSRD+YKnH0GWJY2vhw8pW22KxE sBEIN3m72eMUCXXsY1Fk1UHfFvxWkX0jP1aOkt3BBcq6gDyF7VNjMUKXhNcrJqOt lW6BNTzDywQqnpqhbx6tYWbrr2GRNvwvffYjeM22tPmESnCH2haF5uiitxMgHWg9 +GxLb3KnEIamO2xzfvV9DM3jrdrfeZ+LQe5LWNad1zMc2Oa2fC/DSH6c9BIgZqMM CDIjq298ZnQB0pIFgKif69NYP5LhQMwWToLHoCrWuKA5TeNpVDk26AzxSrMzMsud kviTe2Od26CXnxMPXx2F0u4Nd/lPlnLJ6ZnKKymRwVbvuccPxI5n8zLiRwNfRmBG /0aFH3XghV59TjTmITUINqp44YxDgtJZPOc4OkbPo4MA8wU4tWWajgL3sbj5N6dc EqTRIMfmZeP9BpRHqCrkhxvZKd5cq95pH+qYYbjrbaaWYbwoJ5wn9uqcdzscAfcD S/9xZ2CZoWPydpsjO360IuhpQujG65z7QY/QGaPIOwgPVeKLmFJDwzCnu8RkfxqD fNbZG0JUmXaGzNGuml3CnEYoXbgivpow+rEe4OOhjMTvFhC9irg= =5i0j -----END PGP SIGNATURE-----
--- End Message ---
