From: Antonio Terceiro <terceiro@debian.org>
Date: Sun, 4 Dec 2022 14:28:26 -0300
Subject: message_spec: fix test to pass under ruby3.1

For some reason, the test is failing like this:

>       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.'

It seems like the exception message is being duplicated?  However I
cannot reproduce this outside of RSpec even with ruby3.1, or with
ruby3.1 in an upstream-like environment (ruby-standalone + bundle
install).

For now this will stay as a local patch.

Debian-Bug: https://bugs.debian.org/1019635
Forwarded: not-needed
---
 spec/mail/message_spec.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/spec/mail/message_spec.rb
+++ b/spec/mail/message_spec.rb
@@ -1606,7 +1606,7 @@
           body '<h1>This is HTML</h1>'
         end
       end
-      expect { mail.decoded }.to raise_error(NoMethodError, 'Can not decode an entire message, try calling #decoded on the various fields and body or parts if it is a multipart message.')
+      expect { mail.decoded }.to raise_error(NoMethodError, /Can not decode an entire message, try calling #decoded on the various fields and body or parts if it is a multipart message./)
     end
 
     it "should return the decoded body if you call decode and the message is not multipart" do
