Re: [Nmh-workers] new nmh broken?
So ... you read the release notes, right? --Ken Well, no. I did a yum update and things stopped working. I did not install from source. I would be unable to get any work done if I had to read the release notes on every package upgrade. Which is what 99% of the people that will have this problem will do. For this reason, I agree that the error message needs updating. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
[Nmh-workers] new nmh broken?
Just upgraded. Have a message that looks like this: To: gumby, djb cc: Fcc: ssc Subject: Mucho Chango X-MH-Attachment: /home/jon/cb/ssc/e2/embedded/io_board/ioboard.c OK, this still needs some inspection and testing but to use those famous last ... When I try to send it from whatnow I get: post: message has no From: header post: See default components files for examples post: re-format message and try again send: message not delivered to anyone Jon ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Jon wrote: Just upgraded. Have a message that looks like this: To: gumby, djb cc: Fcc: ssc Subject: Mucho Chango X-MH-Attachment: /home/jon/cb/ssc/e2/embedded/io_board/ioboard.c OK, this still needs some inspection and testing but to use those = famous last ... When I try to send it from whatnow I get: post: message has no From: header post: See default components files for examples post: re-format message and try again send: message not delivered to anyone Add a From: to each of your components files! See NEWS. And those error messages :-) Also, X-MH-Attachment works, but the default field name is now Nmh-Attachment. David ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
It's not broken, read the diagnostics and follow the directions provided. You have to supply a From now ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
When I try to send it from whatnow I get: post: message has no From: header post: See default components files for examples So ... you read the release notes, right? --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Jerrad Pierce writes: It's not broken, read the diagnostics and follow the directions provided. You have to supply a From now I would have expected the upgrade to install the appropriate components to not break things. Jon ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
I would have expected the upgrade to install the appropriate components to not break things. In which case it would likely break things in other ways, or not do the right thing for some individuals. Making specific changes to a template of unknown content is fraught with peril. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Ken Hornstein writes: When I try to send it from whatnow I get: post: message has no From: header post: See default components files for examples So ... you read the release notes, right? --Ken Well, no. I did a yum update and things stopped working. I did not install from source. I would be unable to get any work done if I had to read the release notes on every package upgrade. Jon ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Jerrad Pierce writes: It's not broken, read the diagnostics and follow the directions provided. You have to supply a From now I would have expected the upgrade to install the appropriate components to not break things. That should have happened, actually (and as far as I know, it does). Do you have your own custom components files? --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Ken Hornstein writes: Jerrad Pierce writes: It's not broken, read the diagnostics and follow the directions provided. You have to supply a From now I would have expected the upgrade to install the appropriate components to not break things. That should have happened, actually (and as far as I know, it does). Do you have your own custom components files? --Ken I have a slightly modified version that removes the default Fcc stuff that was added some time ago and drives me crazy as I don't want that. Jon ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Jon wrote: Well, no. I did a yum update and things stopped working. I did not install from source. I would be unable to get any work done if I had to read the release notes on every package upgrade. I sympathize, but the diagnostic message that you got seems sufficient to me. /usr/share/doc/nmh-1.5/NEWS David ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
David Levine writes: Jon wrote: Well, no. I did a yum update and things stopped working. I did not install from source. I would be unable to get any work done if I had to read the release notes on every package upgrade. I sympathize, but the diagnostic message that you got seems sufficient to me. /usr/share/doc/nmh-1.5/NEWS David I've been on vacation. There were about 400 packages upgraded today. Imagine if each one broke something. Jon ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
I have a slightly modified version that removes the default Fcc stuff that was added some time ago and drives me crazy as I don't want that. So, yeah, that's the reason. I don't think there was ever a chance we could ever hope to modify user's components files in a sane manner. The default ones shipped with nmh work. I kinda thought the error message you got was ... obvious? And told you what you needed to look at? What would have helped? --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Ken Hornstein writes: I have a slightly modified version that removes the default Fcc stuff that was added some time ago and drives me crazy as I don't want that. So, yeah, that's the reason. I don't think there was ever a chance we could ever hope to modify user's components files in a sane manner. The default ones shipped with nmh work. I kinda thought the error message you got was ... obvious? And told you what you needed to look at? What would have helped? --Ken This was obvious to someone paying attention to the guts of nmh. Which I haven't been recently. A more user-friendly diagnostic might be: Your components files are not compatible with this version of nmh. You have modified them so we were unable to automatically update them. You need to go to /etc/nmh and merge in the changes to the components, forwcomps, replcomps, and replgroupcomps files. If you're in a hurry you can add a From: header to this message so that it can be sent. Jon ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
A more user-friendly diagnostic might be: Your components files are not compatible with this version of nmh. You have modified them so we were unable to automatically update them. You need to go to /etc/nmh and merge in the changes to the components, forwcomps, replcomps, and replgroupcomps files. If you're in a hurry you can add a From: header to this message so that it can be sent. Noted. Although I think this message would have been longer than every other nmh error message combined :-) Not that there's anything wrong with that. I guess I was hoping the part about the missing From header and checking the components files would be enough. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Ken Hornstein writes: A more user-friendly diagnostic might be: Your components files are not compatible with this version of nmh. You have modified them so we were unable to automatically update them. You need to go to /etc/nmh and merge in the changes to the components, forwcomps, replcomps, and replgroupcomps files. If you're in a hurry you can add a From: header to this message so that it can be sent. Noted. Although I think this message would have been longer than every other nmh error message combined :-) Not that there's anything wrong with that. I guess I was hoping the part about the missing From header and checking the components files would be enough. --Ken Well, I agree that it's long, but this isn't a transient error, it's an upgrade issue and that's a place where at least one person (me) doesn't expect things to break. So giving explicit instructions seems OK to me even if they're long. Again, you have to keep in mind that a lot of people automatically update their systems to keep 'em current and do so without paying a lot of attention so it's a surprise when things stop working. Y'all worked pretty hard to get this release out (thanks!) and were building it from source and probably didn't think about the non-involved user. Jon ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Well, I agree that it's long, but this isn't a transient error, it's an upgrade issue and that's a place where at least one person (me) doesn't expect things to break. So giving explicit instructions seems OK to me even if they're long. Fair enough. Although technically the issue is more with the DRAFT rather than components file; you could always delete the From: header from the draft even if your components were correct. How about this text: Your draft file does not contain a From: header; this version of nmh requires that all draft messages contain one. See the default component templates for examples and insure that your draft contains a valid From: header. --Ken ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Ken Hornstein writes: Your draft file does not contain a From: header; this version of nmh requires that all draft messages contain one. See the default component templates for examples and insure that your draft contains a valid From: header. s/insure/ensure/ Tet ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [Nmh-workers] new nmh broken?
Ken Hornstein writes: Your draft file does not contain a From: header; this version of nmh requires that all draft messages contain one. See the default component templates for examples and insure that your draft contains a valid From: header. s/insure/ensure/ Insurance ensures you will receive the appropriate DSN. ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
