Package: mutt
Version: 2.0.2-1
Severity: normal
Tags: upstream fixed-upstream
X-Debbugs-Cc: r.schwe...@pengutronix.de
Control: forwarded -1 https://gitlab.com/muttmua/mutt/-/issues/396
Control: fixed -1 2.2.3-1
Hello,

mutt 2.x broke some workflow here, which is explained in detail in the
upstream bug report available at
https://gitlab.com/muttmua/mutt/-/issues/396. The gist is that the
edit-fcc and the save-to prompt use different histories.

This was also fixed upstream in commit
bce2c294b27808f9373afa1ada61719f57d20e59 for master and stable. So
upstream is fixed since 2.2.2 and the affected versions in Debian are
2.0.5-4.1 in bullseye/stable and 2.0.2-1~bpo10+1 in old-bpo.

I'd like to have that fixed in Debian---ideally in stable--- and wonder
what is the best way forward. The obvious options are

 a) apply the patch to 2.0.5-4.1 and upload to proposed updates
 b) add a backport or 2.2.3-1 to bpo

Given that upstream considered this change worth to be applied to
their stable branch, I would consider option a) justified.

What is your opionion here? I can prepare an nmudiff for option a) if
you're ok with that option and also offer to actually to nmu. (But
having you upload would be my preferred way.)

Best regards
Uwe

Reply via email to