Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1642 - Patch libtiff to work with hylafax
|
DetailsHylafax requires a bugfix patch to libtiff 3.6.1 in order to work properly. Otherwise, it will sometimes produce bad tiffs without any warning, and smoke will begin to come out of your ears until you figure out why.
Attached find the updated PKGBUILD and the patch, downloaded from the hylafax site and fixed so as to work. (It was originally a patch for "file.c.orig" to "file.c" and thus broken with the normal patch syntax. Maybe there's some flag that makes it work that way, I don't know..) |
This task depends upon
Closed by dorphell (dorphell)
Thursday, 06 January 2005, 07:04 GMT
Reason for closing: Not a bug
Additional comments about closing: Outdated bug, already been fixed
Thursday, 06 January 2005, 07:04 GMT
Reason for closing: Not a bug
Additional comments about closing: Outdated bug, already been fixed
PKGBUILD
HOWEVER: Note that if you're using hylafax, it seems that on the whole, the patched 3.6.1 libtiff is still more reliable on the whole than v3.7.0, at least from what I've seen so far. Version 3.7.0 seems to break fax *sending* in certain circumstances which I haven't exactly pinned down yet.