Since at least 1.5.6, the nntp patch has been breaking mixmaster support (--with-mixmaster added manually). Attached are: 1) an updated ebuild that introduces a "mixmaster" use flag so I and however many other mixmaster users don't have to keep overlaying mutt ebuilds, and 2) a patch which backs out three lines of the nntp patch responsible for breaking mixmaster support. The patch is applied whenever nntp is enabled (without checking the mixmaster use flag) because the three lines in question are a NOP without mixmaster support. Could someone with nntp access please compile with both mixmaster and nntp and see if anything related to the nntp support fails? I categorized this as an enhancement rather than a minor bug only because mixmaster isn't enabled by the current ebuilds. Nevertheless, someone beginning to experiment with mixmaster may try adding --with-mixmaster to the mutt ebuild, and the potential compile failure with USE=nntp is not good. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 51358 [details] Test mutt ebuild with mixmaster USE flag and nntp fix
Created attachment 51359 [details, diff] patch to back out three lines of the nntp patch that break mixmaster support
Fixed in mutt-1.5.8-r1
This is not true anymore. I just tried and both patch concurrently applied do not keep the sources from compiling and running (so not fully tested). Could you please repoen thos bug so that the ebuild can be fixed by removing this kind of lines from the current ebuilds : $(use_with !nntp mixmaster) thx
please file a new bug for this issue to keep things clear
