Hi Pierre-Elliott,
On Thu, Jan 27, 2022 at 11:25:39PM +0100, Pierre-Elliott Bécue wrote:
> I've not put a close statement in my upload because I wanted to make
> sure that you are aware that uploading 4.0 in stable is probably not an
> option.
>
> Would you like me to backport this package?
I experienced this problem myself the last few months with mailman3
on bullseye. Regrettably I bothered mailman3 upstream about it and
they told me the same; that it was this known problem in
python3-flufl.bounce. I should've checked here first. 🙁
Anyway, I see this is fixed in 4.0-2 that is in testing but I don't
know the best way to have it fixed in bullseye. Should I just
install the package from testing since we are so close to the freeze
(I tested and this does work)?
Otherwise, a fixed package in bullseye-backports would be good.
Upstream patch that fixes this:
https://gitlab.com/warsaw/flufl.bounce/-/merge_requests/19
https://gitlab.com/warsaw/flufl.bounce/-/commit/ad700469c502f145ebfb4b62d8e23cd588fbf619
Thanks,
Andy
