FS#1642 - Patch libtiff to work with hylafax

Attached to Project: Arch Linux
Opened by Paul Mattal (paul) - Monday, 18 October 2004, 20:22 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Hylafax 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..)
(application/octet-stream)    PKGBUILD (1 KiB)
(application/octet-stream)    hylafax-libtiff-3.6.1.patch.b... (0.5 KiB)
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
Comment by Paul Mattal (paul) - Saturday, 23 October 2004, 02:13 GMT
In the category of "belay that order," nobody do anything on this just yet. Although hylafax actually suggests this fix on their website, anecdotal evidence of mine suggests that the use of this libtiff makes tiffs valid in some circumstances and invalid in others.. in short, I'm not 100% sure this is a good idea just yet. I'll report back in when I have more information.
Comment by Paul Mattal (paul) - Wednesday, 17 November 2004, 03:55 GMT
An update on this. This patch is reputedly included in v3.7.0, so this bug is now officially obsolete and can be closed.

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.

Loading...