From: Debian Python Team <team+python@tracker.debian.org>
Date: Thu, 20 Mar 2025 12:56:44 +0000 (+0100)
Subject: patchbomb-ambiguous-address
X-Git-Tag: archive/raspbian/6.3.2-1+rpi1+deb12u1^2~1
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=6806e8d503e4449fcbc3ef08bc10b908fafbc440;p=mercurial.git

patchbomb-ambiguous-address

# HG changeset patch
# User Raphaël Gomès <rgomes@octobus.net>
# Date 1729684194 -7200
#      Wed Oct 23 13:49:54 2024 +0200
# Branch stable
# Node ID d906406658a947ab64b34302df15be21e928ba24
# Parent  e760a36a601336f75016e5c2bbc5a53da2ea7182
patchbomb: don't test ambiguous address

This is a bug in Python's `email` package and shouldn't be relied on.
Python 3.12 has fixed this problem¹ and raises an exception. We keep the
multiple `-t` because this is still relevant for testing.

[1] https://github.com/python/cpython/issues/102988
[2] https://docs.python.org/3/whatsnew/changelog.html


Gbp-Pq: Name patchbomb-ambiguous-address.patch
---

diff --git a/tests/test-patchbomb.t b/tests/test-patchbomb.t
index ddfd8e6..44a96ab 100644
--- a/tests/test-patchbomb.t
+++ b/tests/test-patchbomb.t
@@ -2377,7 +2377,7 @@ test multiple flags for multiple patches:
   
 
 test multi-address parsing:
-  $ hg email --date '1980-1-1 0:1' -m tmp.mbox -f quux -t 'spam<spam><eggs>' \
+  $ hg email --date '1980-1-1 0:1' -m tmp.mbox -f quux -t 'spam<spam>' \
   >  -t toast -c 'foo,bar@example.com' -c '"A, B <>" <a@example.com>' -s test -r 0 \
   >  --config email.bcc='"Quux, A." <quux>'
   this patch series consists of 1 patches.
@@ -2398,7 +2398,7 @@ test multi-address parsing:
   User-Agent: Mercurial-patchbomb/* (glob)
   Date: Tue, 01 Jan 1980 00:01:00 +0000
   From: quux
-  To: =?iso-8859-1?q?spam?= <spam>, eggs, toast (py3 !)
+  To: =?iso-8859-1?q?spam?= <spam>, toast (py3 !)
   Cc: foo, bar@example.com, =?iso-8859-1?q?A=2C_B_=3C=3E?= <a@example.com> (py3 !)
   Bcc: =?iso-8859-1?q?Quux=2C_A=2E?= <quux> (py3 !)