Last validated version in portage is 6.0.3. Here is the changes since this version : CHANGES for 6.0.4 ----------------------------------------------------------------------------- * Page sent protocol trace fixes (2009-07-24) * Don't duplicate any file in a release tarball (2009-08-07) * IPv6: Rework initial bind (2009-08-07) * Some CVS-GIT cleanups/release notes (2009-08-14) * pagesend: Fix broken switch statement (2009-08-14) * hfaxd: Cleanup uid initizliaztion and theoretical overflow (2009-08-14) * nls: Add German translation (2009-09-14) * PageHandling: Fix handling of large blank areas (2009-09-18) * Add support for libtiff 3.9 (2007-11-21) * faxq: Don't assert on bad FIFO messages (2009-09-21) * Updated RPM dependencies (2009-09-25) * Str::vformat() Don't reuse va_args (2009-10-07) * faxmail: Fix broken to address/name parsing (2009-10-29) * Update releasenotes and documentation re IPv6 support (2009-11-13) * hfaxd: log what address(es) we're listing on when starting (2009-11-13) * faxsend: Class1 1 ECM when skipping pages needs to be more careful (2009-11-13) * Class1: ECM page and block count should be sent as modulus. (2009-11-13) CHANGES for 6.0.5 ----------------------------------------------------------------------------- * Typo in CONFIG_UNIXTRANSPORT define checks (2009-11-06) * Allow "any" as answer method for FIFO messages (2010-01-22) * Updates LibTIFF homepage URLs (2010-02-05) * Updated ftp site address in setup error message (2010-03-05) * Correctly check for long lines when checking for the last match (2010-02-05) * Fix calls to pdf2fax/ps2fax in ConvertFile (2010-04-02) * notify: FaxMaster notifications wildcard fixups (2010-05-05) * manpages: Updates from debian (2010-05-05) * pdf2fax/ps2fax: Use -dMaxStripSize=0 (2010-05-05) * Bug 928: issues with installClient target of Hylafax (2010-05-05) * Fixes compilation on some platforms (2010-06-24) * faxq: better capturing of failed conversion output (2010-08-10) * Class2: Fix hangup cause handling (2010-08-30) * Compiler warning cleanup (2010-08-30) But the bug #297150 is always here and I don't know how to solve it. Reproducible: Always
Created attachment 267731 [details, diff] hylafax-6.0.5.ebuild.diff
Created attachment 268245 [details] hylafax-6.0.5.ebuild
any news?
... checking TIFF library version Found tiffio.h version 20111221 Found libtiff version 4.0 Incompatible TIFF Library. HylaFAX 6.0.5 requires TIFF software distribution versions 3.4 through 3.9. If you do not have up to date TIFF software on your system then you can retrieve it from the location where you obtained this software. The Home Page for version 3.5 and later is http://www.remotesensing.org/libtiff/ Unrecoverable error! Once you've corrected the problem rerun this script. ... checking PAM library version * ERROR: net-misc/hylafax-6.0.5 failed (configure phase):
Created attachment 300021 [details, diff] Adapt hylafax-6.0.5 to tiff-4.0.0-r1 I've found this posting: http://www.asmail.be/msg0054683776.html and wrote a patch to include necessary changes into hylafax-6.0.5. Since this patch forbids compiling with <media-libs/tiff-4.0 I've also patched configure to error on prior versions of media-libs/tiff. Next follows an ebuild to include this patch. It compiles and starts affected hfaxd on my hardened amd64 server. A simple test using two IAXmodems on the same box (same hfaxd) for send/receive showed a clean reception of a fax'd PDF.
Created attachment 300023 [details] Ebuild to include hylafax-6.0.5-tiff-4.0.patch into hylafax Compiles cleanly on hardened and non-hardened amd64 boxes and works in both sending and receiving.
What about Hylafax+ <http://hylafax.sourceforge.net/> ? IMHO it should be worth to open a new bug to create an ebuild as an alternative...
(In reply to comment #7) > What about Hylafax+ <http://hylafax.sourceforge.net/> ? > IMHO it should be worth to open a new bug to create an ebuild as an > alternative... Is this an 100% replacement?
Has someone spoke to hylafax upstream about this issue or posted on their mailing list? It's sad to see this helpful package masked...
Seem so... http://bugs.hylafax.org/show_bug.cgi?id=933
(In reply to comment #8) > (In reply to comment #7) > > What about Hylafax+ <http://hylafax.sourceforge.net/> ? > > IMHO it should be worth to open a new bug to create an ebuild as an > > alternative... > > Is this an 100% replacement? More or less... The creator of hylafax+ is the same as of iaxmodem. So maybe it's an interesting thing for users using a combination of asterisk, iaxmodem and hylafax. Site says: "HylaFAX™ is an enterprise-class open-source system for sending and receiving facsimiles as well as for sending alpha-numeric pages. This is the place where users can find HylaFAX+ support, work, and releases. The "+" means that it is better." and taken from http://hylafax.sourceforge.net/about.php : "Some HylaFAX+ changes were ported to the hylafax.org repository for the 4.3.1 release and then again some for the 4.4.0 release, but later releases did not include any additional HylaFAX+ work. So, for the most part, hylafax.org release 6.0.5 does not include many years' worth of work found in HylaFAX+ release 5.5.0. So, yes, HylaFAX+ should rightfully be considered more-advanced than hylafax.org releases despite the version numbering."
For a working ebuild of hylafax+ switch to bug #168890 as this old one is still under development.
*** Bug 400925 has been marked as a duplicate of this bug. ***
hylafax+ is now in the tree (although masked with no keywords and it might take a week or two for me to finish revising the ebuild into the shape I want). Unless there is a critical need to bring back the original hylafax(which I'm not aware of and which seems unlikely), I'd suggest this bug be closed.
Closing this bug -- all hylafax users should switch to hylafaxplus which has been in tree for a few months now.
