Summary: | new package mail-client/mahogany-0.67 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Róbert Čerňanský <openhs> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | maintainer-wanted, net-mail+disabled, rhill, vz-gentoo, wxwidgets |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://mahogany.sourceforge.net/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
mahogany-0.67 ebuild
patch to compile with <gcc-4.x patch to compile with <wxGTK-2.7 mahogany-0.67 ebuild with upstream fixes Patch for upstream fixes. 010-cvs20060903.patch 020-wx26.patch 030-utf8warn.patch Third version of mahogany-0.67 ebuild 010-cvs20060903.patch 020-utf8warn.patch 030-buildfix.patch |
Description
Róbert Čerňanský
2006-08-14 09:42:21 UTC
Created attachment 94250 [details]
mahogany-0.67 ebuild
Created attachment 94251 [details, diff]
patch to compile with <gcc-4.x
This goes to files/ directory.
Created attachment 94252 [details, diff]
patch to compile with <wxGTK-2.7
This goes to files/ directory.
Created attachment 96190 [details]
mahogany-0.67 ebuild with upstream fixes
New ebuild that contains patch for several fixes found after 0.67 release.
wxGTK dependecy was changed to >=wxGTK-2.6.3 because there are font encoding issues with lower wx versions.
Created attachment 96191 [details, diff]
Patch for upstream fixes.
Thi patch updates Mahogany to CVS version from 3. 9. 2006.
Comment on attachment 96191 [details, diff]
Patch for upstream fixes.
Err, this is wrong one.
Created attachment 96192 [details, diff]
010-cvs20060903.patch
This patch updates Mahogany to CVS version from 3. 9. 2006.
Created attachment 96193 [details, diff]
020-wx26.patch
Patch to compile with <wxGTK-2.7.
Created attachment 96195 [details, diff]
030-utf8warn.patch
Warn users which do not have UTF8 locale. Normally, warning works only with >=wxGTK-2.6.4 (not yet released). This patch enables it also for 2.6.3.
ping? mahogany-0.65 has been package.masked for security reasons since 07/06 and needs to be removed. we're also removing wxGTK-2.4 very soon. I'm the author of Mahogany and I'm curious about "security issues" -- where can I find more details about it? FWIW latest Mahogany 0.68 requires wxWidgets 2.8.x. hmm, it looks like it was actually <python-2.3.5-r2 that was masked. mahogany-0.65 has a RDEPEND on ( >=dev-lang/python-1.5 <dev-lang/python-2.2 ). # Alastair Tse <liquidx@gentoo.org> (15 Jul 2006) # Python 2.1 and 2.2 have reported vunerabilities. Masked pending # removal, along with net-zope/zope-2.6. (GLSA: 200509-08, 200502-09, # 200510-20) <dev-lang/python-2.3 =net-zope/zope-2.6* mail-client/mahogany As this is masked, it doesn't block the 2.4 removal. Once 2.8 is in the tree I'll bump mahogany to the latest version. New build issues appeared. Attaching new ebuild of mahogany-0.67 with new set of patches that fixes recently discovered build errors. Created attachment 118556 [details]
Third version of mahogany-0.67 ebuild
Created attachment 118557 [details, diff]
010-cvs20060903.patch
Created attachment 118558 [details, diff]
020-utf8warn.patch
Created attachment 118560 [details, diff]
030-buildfix.patch
Removed from the tree. FFS. unless mahogany is updated to work with unicode builds we won't be able to re-add it. we've dropped ansi as of 2.8. The current Mahogany svn trunk does build in Unicode mode but requires wxWidgets 2.9 (which will become wx 3), 2.8 is still only supported in ANSI. So Mahogany could be readded when you update wx package to 3.0 -- coul you please leave this bug open until then? sure why not. waiting on UTF-8 in wxGTK-3.0. Vadim, are you still working on Mahogany? Does it build against wxWidgets-2.9.1? I did work for it during summer a bit and there are quite a few changes which I'll try to package as a new release a.s.a.p. (which means I hope to do it before the end of the year). It does build with and actually requires wx 2.9.1 now. BTW, if you look for the latest sources, they're in Git repository on SF, not in the old svn one. Thanks! |