Re: Status of receiving color JPEG fax (sent by HP OfficeJet 8600)

Lee,

Am encountering several issues after trying to upgrade from hylafax 
6.0.6 to hylafax+ 5.5.6, so would like to get your input!

In no particular order,

1. Build from source is able to locate LittleCMS once I've installed the 
packages from the repo, and completes the build, but complains about not 
being able to find any Courier fonts on the system in the expected paths 
for fonts and font metrics. Presumably the font is needed for printing 
the sender's number and ID name at the top of the fax page.  No idea 
which package provides the Courier fonts it's expecting, after having 
tried installing many of the font packages in the typical ubuntu apt 
repo.  Is there a package that provides Courier in a place that the 
build script will expect.  Is this a serious issue or will it soft fail 
and fall back at runtime to any basic compatible monotype typewriter 
style serif font.

2. When doing a "make install" over the existing hylafax 6.0.6, that 
succeeds however it mangles the existing config in a way that is not 
immediately obvious.  To be more specific, I have an installation of 
asterisk, and asterisk is able to detect the fax tones on the incoming 
call, and when it detects the tones, it automatically transfers the call 
to hylafax as an asterisk  "custom destination". The previous hylafax 
6.0.6 had been answering the calls and receiving the faxes.  The new 
hylafax+ is not taking answering those calls they ring forever. Does 
something come to mind as the most likely cause of this?  Figured you 
might have an immediate sense due to your long time experience with the 
architecture of how hylafax, iaxmodem, faxgetty, vgetty, etc., fit together.

3. Just the general topic of source code and hylafax and hylafax+ and 
rpm/deb packages. I read the history there and it seems interesting.  
Just for fun, I built a .deb package of hylafax+ 5.5.6, not sure if it 
is correct, almost certain that some requires and provides are missing, 
named it hylafax-server.  Apt actually installed it, called it a 
"downgrade" due to version number (even though features are greater and 
it was released more recently). It seemed to overwrite the existing 
hylafax 6.0.6, however, and an apt upgrade immediately wanted to install 
over it the older hylafax 6.0.6 from the distro repo.  Therefore, it 
seems the package needs to be named something different, such as 
hylafax+ and marked as "conflicts with: hylafax-server".  Is that how 
you built the hylafax+ rpm ?  Presuming it was you who built the rpm?

More on the topic of source, any thoughts of moving the hylafax+ code 
and project to github?  If you and the hylafax maintainer were to both 
move to github, then incorporating your hylafax+ improvements into 
hylafax would be a simple matter of making pull requests. It's much 
easier than posting code to the list and manually copy-pasting and 
comparing.  Issues are also somewhat more convenient to take up on 
github vs. email list, it'd be worth a try I'd imagine.

Any interest in building a deb package, or providing the 
requires/provides/other bits of information necessary to build deb 
packages, of hylafax+ 5.5.6?

-Chris


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe [email protected] < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*