Hello raf, On Thu, May 23, 2019 at 01:47:15PM +1000, m...@raf.org wrote: > This might not be the right place to report this but > I've just discovered that the mutt package on debian9 > stable (or rather NeoMutt 20170113 (1.7.2)) segfaults > if you ask it to write to a readonly mbox file. It > happened several times yesterday before I realised what > was wrong (and yes, I did have a reason for wanting > some mbox files to be temporarily read-only).
Indeed, the right place would be at Debian Bug Tracker. You should install the tool 'reportbug' (apt install) and follow the wizard, that's IMHO the easiest way to report a bug on Debian GNU/Linux. You can use bugs.debian.org to see if a similar was already reported, in this case: https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=mutt > I know it's an old version and it might have been fixed > (but I couldn't see that it has from the changelogs). > But if you use debian9 stable, this is the version you'd get. It's a little complicated, with the upcoming Debian 10 (buster) there will be two packages: mutt and neomutt. ;-) > If I can get past neomutt's configure script, I'll see if > it's still a problem. It seems that it can't find libncursesw > no matter how many ways I tell it where it is. Is the mutt mailing list the right place to discuss neomutt problems? (Serious question, I don't actually know.) Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
signature.asc
Description: PGP signature
