RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I need group4 decode in the Python Imaging Library, but in order to build it, I need to get some changes put into the distros libtiff-dev packages.

Currently the following files are added /usr/include or /usr/local/include

/usr/include/tiffconf.h  
/usr/include/tiff.h  
/usr/include/tiffio.h  
/usr/include/tiffio.hxx  
/usr/include/tiffvers.h

I also need:

/usr/include/tif_config.h  
/usr/include/tif_dir.h
/usr/include/tiffiop.h

The patch in PIL I had to use to get all this going is from 2006 and is made against the 1.1.6 PIL library (PIL is now at 1.1.7), but I'm pretty sure I can't get these patches for PIL into pyPI distribution if it won't build in the distros.

After this is done here, I can push to get the fix into PIL.

Version-Release number of selected component (if applicable):
All back to 2006 (at least)

How reproducible:
Very
https://www.kuro5hin.org/story/2010/4/15/133252/616

Steps to Reproduce:
1. install libtiff-dev
2.
3.
  
Actual results:
Those 3 files are not present

Expected results:
Those 3 files are present

Additional info:
I also have to get debian to add those files too.

Uh ... the reason tiffiop.h isn't exported is that it's *private*.  Any application depending on its contents is not supportable because it will break with foreseeable library changes.  Not sure about the other two offhand, but I will not export that one.

As near as I can tell, the link you provide is to somebody's crude hack, not a supportable fix for PIL.  It should not be necessary to look into the library's private definitions in order to have G4 support.

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.