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

On 09/04/2015 09:16 AM, Chris Coleman wrote:
> 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.

This is typically involved in converting text to postscript with 
textfmt.  You may want to examine the DEB package that the Debian 
package maintainer was using to see what they were doing to overcome 
this problem.

The real culprit is that recent Ghostscript changed (again) their font 
map files which make it impossible for us to now find the fonts as we 
did before.  Our usual tools to produce the map are not working... and 
we need to revisit it.

However, to remedy the problem take a look at whatever ended up as 
/var/spool/hylafax/etc/Fontmap.HylaFAX.  I can't remember right-away 
what I had to do to fix that manually, but I think I ended up just 
putting some lines in like this:

(NimbusMonL-Bold) (/usr/share/fonts/default/Type1/n022004l.pfb) ;
(NimbusMonL-BoldObli) (/usr/share/fonts/default/Type1/n022024l.pfb) ;
(NimbusMonL-Regu) (/usr/share/fonts/default/Type1/n022003l.pfb) ;
(NimbusMonL-ReguObli) (/usr/share/fonts/default/Type1/n022023l.pfb) ;
(NimbusRomNo9L-Medi) (/usr/share/fonts/default/Type1/n021004l.pfb) ;

It's not critical unless you're submitting text to sendfax and need it 
converted to postscript for submission to hfaxd.

> 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.

It seems like faxgetty is not running on your iaxmodem.  You should be 
able to see it from the Asterisk CLI or the syslog.

> 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?

I am the HylaFAX+ maintainer for Fedora and EPEL.  There never was a 
"hylafax" package in Fedora before I got it included (although there had 
been one in the really early RedHat versions before Fedora).  So 
producing a "hylafax" package would have been no problem and no 
conflict; however, various individuals objected in such a way that I was 
obliged to name the package "hylafax+".  However, yes, it is marked as 
"conflicts with: hylafax" or something to that effect.

> 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.

Who is this hylafax maintainer of whom you speak that would want to 
incorporate hylafax+ development?  If my moving HylaFAX+ to github would 
be beneficial in seeing HylaFAX+ developments get a broader audience, 
then I would certainly consider doing so.  However, I have serious 
doubts that it would.  I don't suspect that the lack of incorporation of 
HylaFAX+ development into hylafax.org code has much of anything to do 
with the ease of porting code around.  I'll just leave my comments at 
that so as to not ignite any flame war.

What you really seem to be getting at, though, is...

> 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?

... "Why isn't HylaFAX+ in Debian already to save me all of this effort 
of building from source?"

The answer is that the HylaFAX package maintainer at Debian has so far 
refused to do it, and I really haven't taken the time to make 
independent deb packages for a long time now.  I wasn't really 
interested in trying to become a Debian package maintainer as well as a 
Fedora package maintainer.

I'm going to leave my comments at that.  There is plenty of archived 
mud-slinging available in various places on the web for everyone to get 
the details of what happened and why things are the way they are.

Thanks,

Lee.


____________________ 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].*