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
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
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
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
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
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
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.
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
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
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
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.
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
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
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
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,
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,
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
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
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
19 matches
Mail list logo
