Description of problem: No problem, really; just wanted to fix some other stuff (that turned out to be a legacy (mis)configuration), and updated nmh as part of seaching for the problem. Seems to work fine here... It seems I'm the only remaining user of this one, perhaps I should take over maintainership for Fedora? ;-) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 145589 [details] SRPM for nmh-1.2
I've been meaning to do this for a while now. Honestly there have been several rather important bugs fixed in the nmh CVS since 1.2. It would probably make more sense to pull from CVS rather than let anyone suffer through 1.2.
Also, as a note to myself, the locking patch is no longer needed as the packages are now built using fcntl locking rather than dot locking.
Re #2: Never got to wrap my mind around CVS... and that after working /very/ confortably with RCS for some time. Go figure. I got the nmh repo into git here right now. There sure are a /lot/ of changes since 1.2. What would you propose doing? Add a (mega)patch from 1.2 -- present? Add each commit as a separate patch (easily doable, but I shudder)? Take this discussion to email? Buzz off??
I'll probably pull a new tarball from CVS. I think using a megapatch would be rather counterproductive.
Created attachment 145619 [details] nmh SRPM for CVS as of today Needed some tweaks, see the %changelog in the SRPM.
I've added nmh-1.2-20070115cvs.1.fc7 to CVS this evening. It's building now. Thanks for the help. I would suggest any effort you wish to invest in the development of nmh be spent working with the upstream project (we need all the help we can get): http://savannah.nongnu.org/projects/nmh/