Problem with TIF encoding or reading. http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=500 Reproducible: Always Steps to Reproduce:
I try emerge tiff-3.7.0 and all created tiff is correct.
There only two active Hylafax versions; 4.1.8 (x86) and 4.2.0 (~x86). Only the latter new release works with any tiff after 3.5 and only tiff 3.7.0 is fixed. Was there something unclear about the ewarn info in Hylafax 4.1.8: ewarn "Proper fax2tiff support now requires libtiff 3.5.5 until there" ewarn "is an upstream fix for bug #48077. You must use this version" ewarn "of fax2tiff if you need conversion of G3 files, however, you" ewarn "you must still build hylafax against tiff-3.5.7-r1 or better." ewarn "I repeat: do not try to build hylafax or anything else against" ewarn "tiff-3.5.5 because it won't work. You've been warned." If so I can try to re-write it, however, I suspect you'll be happier with the latest tiff 3.7.0 and Hylafax 4.2.0. Otherwise, please explain your need to use a broken tiff version with Hylafax.
Sorry, I didn't mean to sound rude, but this whole tiff thing has been a royal PITA and has gone on far too long (many subtle upstream bugs). The only fix I can offer is the one now in portage, i.e., Hylafax 4.2.0 and tiff 3.7.0, which actually works for the first time in recent memory. It seems the tiff bugs may be fixed at last... Since I have no adverse reports with this combo yet, please stick with the above versions. Thanks. PS. It's safe to add hylafax and tiff to /etc/portage/package.keywords and emerge as normal.
I'm running Hylafax 4.2.0 and tiff 3.7.0, and my tiff's are still corrupt. [ebuild R ] net-misc/hylafax-4.2.0-r1 -faxonly +jpeg +pam 0 kB [ebuild R ] media-libs/tiff-3.7.0 0 kB
Can someone past some older ebuilds that work maybe? I really need to get my fax working.
Created attachment 44258 [details] tiff-3.5.7-r2.ebuild (complete with old bugs) This ebuild should work with Hylafax at least through 4.1.8, however, it has all the old security risks, and still has a broken fax2tiff for G3 files.
Created attachment 44259 [details] config.site for 3.5.7 ebuild Put this in your portage overlay in media-libs/tiff/files for the 3.5.7 ebuild.
We need to find out why tiff 3.7.0 barfs for you. It's most likely an upstream bug, but at the very least I'd like to submit a bug there (depending on what we find). Also, if the above 3.5.7 doesn't fix it for you, then I might need to get the old 3.5.5 out of CVS. So let me know if this is a valid work-around for you, and I also need to know more about this new problem. Can you please post a new bug with all your info on the tiff 3.7.0 error? Thanks.
I run "emerge hylafax ncpfs" and I work in another console so I don't see ewarn message. I try find ewarn messages in the /var/log/emerge.log I don't find it there. Are this ewarn messages loging somewhere? I'm running: [ebuild U ] net-misc/hylafax-4.2.0-r1 [4.1.8-r4] -faxonly +jpeg +pam 1,320 kB [ebuild R ] media-libs/tiff-3.7.0 1,215 kB and my tiffs are OK. I try next week emerge hylafax-4.2.0-r1 into my server and I send report if are tiffs OK.
Sorry, comment #8 was for Steven Wagner. Thanks.
OK... You know ansver on this (from Comment #9): Are this ewarn messages loging somewhere? I'm now running: [ebuild R ] net-misc/hylafax-4.2.0-r1 -faxonly +jpeg +pam 0 kB [ebuild R ] media-libs/tiff-3.7.0 1,215 kB and my tiffs are OK. Find only one cosmetics problem in files name: fax000000883.tif fax000000885.tif fax000000886.tif fax000000888.tif fax000000890.tif fax000000891.tif fax000000892.tif fax00884.tif fax00887.tif fax00889.tif