Schedule for a resolution of #406, #410 and #437
I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It seems that it would not be far, as !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to be merged.
On another note, why doesn't mailman3.org seem to be affected by these problems, with so many members wide spread across the world, when I have at least three lists with only 1794, 646 and 317 members affected by it.
-- Henrik Rasmussen <her@adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark
On Wed, Dec 13, 2017, at 12:11 AM, Henrik Rasmussen wrote:
I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It seems that it would not be far, as !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to be merged.
Merged right now! :)
On another note, why doesn't mailman3.org seem to be affected by these problems, with so many members wide spread across the world, when I have at least three lists with only 1794, 646 and 317 members affected by it.
-- Henrik Rasmussen <her@adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in
On 12/14/2017 02:14 PM, Abhilash Raj wrote:
On Wed, Dec 13, 2017, at 12:11 AM, Henrik Rasmussen wrote:
I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, #410<https://gitlab.com/mailman/mailman/issues/410> and #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It seems that it would not be far, as !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to be merged.
Merged right now! :)
And I have updated lists.mailman3.org and mail.python.org.
Note however that <https://gitlab.com/mailman/mailman/merge_requests/322> does not fix <https://gitlab.com/mailman/mailman/issues/437> as noted at <https://gitlab.com/mailman/mailman/issues/437#note_46539617>.
It also doesn't fix <https://gitlab.com/mailman/mailman/issues/441>. That appears due to a new bug related to <https://bugs.python.org/issue27321>, but which is a different message defect that causes UnicodeEncodeError to be thrown instead of KeyError. I have reported this at <https://bugs.python.org/issue32330>.
I have created <https://gitlab.com/mailman/mailman/merge_requests/350> and <https://gitlab.com/mailman/mailman/merge_requests/351> to fix these issues.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 12/13/2017 12:11 AM, Henrik Rasmussen wrote:
On another note, why doesn't mailman3.org seem to be affected by these problems, with so many members wide spread across the world, when I have at least three lists with only 1794, 646 and 317 members affected by it.
At least in part because the Python3 email package on both lists.mailman3.org and mail.python.org contains a patch to fix <https://bugs.python.org/issue27321>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Abhilash Raj -
Henrik Rasmussen -
Mark Sapiro