Summary: | app-misc/mc-4.6.2_pre1: misc bugs and enhancements | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rafał Mużyło <galtgendo> |
Component: | Current packages | Assignee: | Samuli Suominen (RETIRED) <ssuominen> |
Status: | VERIFIED DUPLICATE | ||
Severity: | minor | CC: | desktop-misc |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch fixing etc moves in Makefiles |
Description
Rafał Mużyło
2008-09-09 15:54:50 UTC
For now, instead of attaching, I'll drop this url: http://www.filewatcher.com/p/mc-4.6.1-6.3mdv2007.1.src.rpm.2801623/mc-4.6.1.lzma.patch.html I'm doing it this way, cause that's the most complete patch. The other lack the mc.ext part (I've got to fix that in my ebuild too). I've switched to RedHat patches, cause they don't have problem 2 (they still need fix for problem 1). RedHat patches still suffer from problems I mentioned in bug 101522, but those fixes are still valid. Thanks for the report. Are you saying mc-4.6.1-utf8-r1.patch.bz2 includes code that fixes issue #1? I'm not sure. I was talking about bug 101522#c37 (for problem 1) and bug 101522#c48 (problem mentioned in that bug). I'm also using solution from bug 230832, as it's cleaner than the thing I was doing myself. Also bug 101522#c36. Created attachment 165056 [details, diff]
patch fixing etc moves in Makefiles
And just in case you try to use more patches from RedHat,
mc-etcmc.patch requires either some voodoo in the ebuild
or using eautoreconf and following patch.
One issue per bug, thanks. I'm not going to parse some bundled patch. Closing as duplicate of another mc+lzma bug we already had. We also have bug open for unicode probs. So when you get your issue(s) sorted out, one bug, one issue. *** This bug has been marked as a duplicate of bug 219412 *** IMHO, you've addressed the least significant problem here (a functionality enhancement, as opposed to real bugs). Granted, I can no longer reproduce problem 2 myself (I wonder how I could produce it in the first place), but problem 1 is still valid (and it probably affects other in-tree version, too). What's more, the problem I reported back in bug 101522 is still there: I'm talking about the extra dot appearing at the end of input for each double-width char (in normal and password boxes). (actually, problem 1 was reported in that bug too) And if by 'unicode problems' you mean bug 238974, it's completely unrelated. |