Package Details: hylafaxplus 7.0.7-3

Git Clone URL: https://aur.archlinux.org/hylafaxplus.git (read-only, click to copy)
Package Base: hylafaxplus
Description: Enterprise Fax Server
Upstream URL: http://hylafax.sourceforge.net/
Licenses: custom
Conflicts: hylafax
Provides: hylafax
Submitter: vicks
Maintainer: severach
Last Packager: severach
Votes: 0
Popularity: 0.000000
First Submitted: 2013-09-27 13:39 (UTC)
Last Updated: 2024-02-08 22:07 (UTC)

Latest Comments

Bad-Mad commented on 2024-02-13 05:31 (UTC)

In my case, sending faxes with TIFF v4.6 did not cause any problems. When sending, the files were already converted on the clients. There were problems when receiving. This is probably mainly due to the lack of the necessary binary files such as tiff2ps and tiff2pdf. The received faxes could no longer be converted into corresponding files.

severach commented on 2024-02-09 20:59 (UTC) (edited on 2024-02-09 21:11 (UTC) by severach)

I added in the old libtiff5 executables but Lee does not know if the rest of hylafaxplus works with libtiff6. To discover this I've set hylafaxplus to link to libtiff6. Send fax worked for me for over a month. If you find things that don't work, recompile with _opt_HF_System_LIBTIFF=0 and report back if this needs to be a permanent change. Eventually system libtiff support will break and it will need to be a permanent change.

I didn't want to make a duplicate of libtiff5 but I didn't get a response from the maintainers and IgnorePkg time is running out.

Also the name of tiffcp changed to tiffcp.hylafax. System scripts should already be updated. Custom scripts should be checked and fixed.

Bad-Mad commented on 2024-02-09 05:54 (UTC)

The problems of the new libtiff version were solved by directly including the necessary libtiff binaries in hylafax and the package "libtiff5-hylafaxplus", which can coexist with the current version.

But I had to build "libtiff5-hylafaxplus" without integrity check.

makepkg -srf --skipinteg

Everything works normally again.

Many thanks for the updates.

Bad-Mad commented on 2023-09-18 13:48 (UTC)

Hylafaxplus is not compatible with libtiff 4.6.

I had to install the last 4.5 version. (libtiff-4.5.1-2)

See https://libtiff.gitlab.io/libtiff/releases/v4.6.0.html

Changes in TIFF v4.6.0:

Tools changes Removed functionality:

The following tools are no longer compiled and have been moved to archive/tools:

fax2ps, fax2tiff, pal2rgb, ppm2tiff, raw2tiff, rgb2ycbcr, thumbnail, tiff2bw tiff2rgba, tiffcmp, tiffcrop, tiffdither, tiffgt, tiffmedian

The following tools are no longer compiled by default: tiff2ps and tiff2pdf. They have been moved to tools/unsupported. They can be built by setting --enable-tools-unsupported for autoconf, or -Dtiff-tools-unsupported for CMake, but as the name imply, they are no longer supported by upstream. Packagers are suggested not to enable those options.

tiffcp: remove -i option (ignore errors), because almost all fuzzer issues were consequential errors from ignored errors because of the "-i" option.

drankinatty commented on 2023-01-18 18:55 (UTC)

Moving from the last Arch package 6.0.7 to this hylafaxplus - how bad is the change going to break my current configuration -- and Avantfax configuration? The PKGBUILD contains a whole suite of options and sed changes not present in the original Arch package?

Bad-Mad commented on 2023-01-06 05:50 (UTC) (edited on 2023-01-06 05:51 (UTC) by Bad-Mad)

see also:

(This could also be a solution for hylafax standard.)

https://gitlab.com/libtiff/libtiff/-/issues/504#note_1229203232

bsdice @eisvogel · 13 hours ago
I guess people will stumble upon this ticket when their fax breaks...

To whom it may concern, I reworked my hylafax-plus-custom
Arch AUR package to pull a patched libtiff 4.5.0 straight
into the package. Available here:

https://seitics.de/files/hylafax-plus-custom/

...

Bad-Mad commented on 2023-01-05 10:14 (UTC) (edited on 2023-01-05 10:22 (UTC) by Bad-Mad)

FS#77012 - [libtiff] HylaFAX requires TIFFFaxBlackCodes, TIFFFaxBlackTable, TIFFFaxMainTable, TIFFFaxWhiteCodes

https://bugs.archlinux.org/task/77012

Closed by  Antonio Rojas (arojas)
Thursday, 05 January 2023, 10:16 GMT
Reason for closing:  Not a bug
Additional comments about closing:  AUR packages are not supported
It seems to be a libtiff problem.
HylaFAX requires TIFFFaxBlackCodes, TIFFFaxBlackTable, TIFFFaxMainTable, TIFFFaxWhiteCodes, TIFFFaxWhiteTable, and _TIFFFax3fillrun

libtiff v4.5.0 removed a lot of exports. HylaFAX requires TIFFFaxBlackCodes, TIFFFaxBlackTable, TIFFFaxMainTable, TIFFFaxWhiteCodes, TIFFFaxWhiteTable, and _TIFFFax3fillruns. These are no longer being exported by libtiff in the v4.5.0 release. So, unfortunately, HylaFAX fails to build against libtiff v4.5.0.

https://gitlab.com/libtiff/libtiff/-/issues/511

shmu26 commented on 2021-08-10 18:46 (UTC) (edited on 2021-08-10 18:47 (UTC) by shmu26)

It doesn't work with the current libtiff version in Arch. It can be fixed by adding the following to the file name "config"

4.[0123]) tiff_runlen_t="uint32_t" tiff_offset_t="uint64_t" echo '#define TIFFSTRIPBYTECOUNTS uint64_t' echo '#define TIFFVERSION TIFF_VERSION_CLASSIC' echo '#define TIFFHEADER TIFFHeaderClassic';;

delete the current code for 4. and use the above instead.

Bad-Mad commented on 2016-12-11 16:18 (UTC)

HYLAFAX+ no longer works after LIBTIFF update... Hello severach, Please see my posts in the hylafax+ mailing list. So I don't have do write it here again... ;-) https://sourceforge.net/p/hylafax/mailman/hylafax-users/?viewmonth=201612 Thank you!