Bug 901448 - Add legacy libtiff.so.3 support to Fedora 18
Summary: Add legacy libtiff.so.3 support to Fedora 18
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libtiff
Version: 18
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-18 08:37 UTC by frank128
Modified: 2016-04-22 14:47 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-23 11:02:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
libtiff RPM as requested by Paul Lambert (143.58 KB, application/octet-stream)
2013-04-14 07:34 UTC, Gerard van der Veen
no flags Details
libtiff3 RPM for Fedora 19 (432.54 KB, application/x-rpm)
2013-07-20 12:49 UTC, Per Arnold Blåsmo
no flags Details
SRPM for libtiff3 for Fedora 19 (1.43 MB, application/x-rpm)
2013-07-20 12:50 UTC, Per Arnold Blåsmo
no flags Details

Description frank128 2013-01-18 08:37:45 UTC
Description of problem:
Issue 1: Unable to run third party software (binary only) which has dependency for libtiff.so.3 on Fedora 18 machine. There is not legacy libtiff RPM packages to install. Please help to add libtiff-3.9.7-1 to F18. Just like libpng11, libpng12 packages.

Issue 2: libtiff-4.0.3-1.fc18.i686.rpm is libtiff.so.5.2.0? Why bump up the number?

Version-Release number of selected component (if applicable):
libtiff-4.0.3-1.fc18.i686.rpm

Expected results:
Add legacy libtiff-3.9.7 to F18.

Comment 1 Tom Lane 2013-01-18 15:05:45 UTC
I've got basically zero interest in this personally.  Unlike libpng, libtiff is not so widely used as to justify carrying a compatibility library, nor is it required by any standard.  Also, libtiff 4.0 has been out for long enough now that software authors should not exactly be surprised to find it as the installed version --- if anything, Fedora is behind the curve on that.

If you can find somebody else who wants to maintain such a package, I won't stand in the way.  But I think you'd be better advised to press your third-party vendor for an up-to-date build.

Comment 2 Richard Chan 2013-01-22 01:50:49 UTC
frank128 - Is this for the Canon v3.30 binary package?

Here is a workaround for Fedora 18:

1. Create own legacy package by rebuilding the Fedora 17 src.rpm on F18 and changing the name of the package in the .spec file to libtiff3i686 
In spec file change:

Name: libtiff3

rpmbuild -ba --target i686 SPECS/libtiff.spec

2. This allows side-by-side install with libtiff 

Works with Canon 3.30 binary packages for Canon PIXMA 870 series.

Alternative: try the Canon 3.70 binary package dated 3/2012; it is more recent and might well support older printers. YMMV.

Comment 3 frank128 2013-01-22 10:37:41 UTC
I guess, my only option is to rpmbuild libtiff-3.9.7-1.fc17 for F18.

If Fedora project has no interest to add libtiff compatibility library to F18, then you may mark this as closed and won't fix.

Hi Richard Chan, it was not for Canon binary package. Thank you for your suggestion.

Comment 4 baby.buggy.bunny 2013-01-28 08:45:42 UTC
Hello everybody,

I've the same issue with the driver of my printer -> Canon MP640 (cnijfilter-mp640series-3.20-1-i386-rpm.tar.gz). Depends on libtiff.so.3. @Richard Chan : it seems to be the same kind of binary package from Canon...

@Tom Lane : Unfortunately, this driver has no longer evolved for a long time. I don't think Canon is still supporting it -> you know the famous planned obsolescence ...

I'm not asking to maintain some old libtiff package. But I'll be "interessted in" using my printer. And I'm not sure to be able to follow the workaround of Richard ...

Comment 5 tdcristian 2013-02-02 11:00:48 UTC
I have the same problem trying to use Sikuli (Sikuli-X-1.0rc3 (r905)-linux-x86_64.zip) on fedora 18.

Comment 6 tdcristian 2013-02-02 11:05:53 UTC
To install use Sikuli is required Opencv2.1
After I removed the latest opencv2.4.3 I tried to install the 2.1: 

sudo rpm -ivh opencv-2.1.0-6.fc14.x86_64.rpm 
warning: opencv-2.1.0-6.fc14.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 97a1071f: NOKEY
error: Failed dependencies:
	liblapack.so.3()(64bit) is needed by opencv-2.1.0-6.fc14.x86_64
	libtiff.so.3()(64bit) is needed by opencv-2.1.0-6.fc14.x86_64

Please can you give me a tip how to solve my problem.
Thanks
Daniel

Comment 7 nicolas.vieville 2013-02-06 13:19:49 UTC
(In reply to comment #2)
> frank128 - Is this for the Canon v3.30 binary package?
> 
> Here is a workaround for Fedora 18:
> 
> 1. Create own legacy package by rebuilding the Fedora 17 src.rpm on F18 and
> changing the name of the package in the .spec file to libtiff3i686 
> In spec file change:
> 
> Name: libtiff3
> 
> rpmbuild -ba --target i686 SPECS/libtiff.spec
> 
> 2. This allows side-by-side install with libtiff 
> 

Thank you for this workaround, libtiff3-3.9.7-1.fc18.x86_64.rpm (or libtiff3-3.9.7-1.fc18.i686.rpm) package is the one to install after rebuilt.

For my part, this was useful to make OpenDCP and Povray packages not to complain about the missing libtiff.so.3 library and to make user's experience "smoother".

Cordially,


-- 
NVieville

Comment 8 tdcristian 2013-02-06 14:15:03 UTC
Hi Nicolas Vieville,

Please can you post more precise steps to create: libtiff3-3.9.7-1.fc18.x86_64.rpm 
Unfortunately I was not able to create this package.

Regards,
Daniel

Comment 9 nicolas.vieville 2013-02-06 15:47:26 UTC
Hi Daniel,

(In reply to comment #8)
> Please can you post more precise steps to create:
> libtiff3-3.9.7-1.fc18.x86_64.rpm 
> Unfortunately I was not able to create this package.

In order to be able to rebuild a package you have to install some useful tools and their dependencies (in a root console):

yum install rpm-build rpmdevtools

Then set up a rpm build environment (in your user console):

rpmdev-setuptree

This will create a rpmbuild directory in your ${HOME} directory (with ${HOME} corresponding to your current user directory).

Then download the libtiff SRPMS for F-17 from http://download.fedoraproject.org/pub/fedora/linux/updates/17/SRPMS/libtiff-3.9.7-1.fc17.src.rpm for example (or any mirror available near you).

Extract this package in a clean and empty folder (file-roller may be helpful for that).

Edit the libtiff.spec file in order to replace the line:

Name: libtiff

by:

Name: libtiff3

Save this file. Copy this modified libtiff.spec file in your ${HOME}/rpmbuild/SPECS/ directory. Copy all the other files (libtiff*.patch and tiff-3.9.7.tar.gz) in your ${HOME}/rpmbuild/SOURCES/ directory.

Then in your user console type:

rpmbuild -ba ${HOME}/rpmbuild/SPECS/libtiff.spec

If everything goes well, you should see a message telling you that some RPMS files were written in your ${HOME}/rpmbuild/RPMS/your_current_arch/ directory (with your_current_arch equal to x86_64 or i386 or i586 or i686).

If some error messages show you that some building dependencies packages are missing, install them in the root console with yum.

Once the package built without error, in the root console type:

yum localinstall --nogpgcheck /path_to_your_user_home/rpmbuild/RPMS/your_current_arch/libtiff3-3.9.7-1.fc18.your_current_arch.rpm

This will install the newly built package you needed. Don't forget --nogpgcheck option as we don't sign the locally built packages.

Be careful, these explanations are only valid for this case because the package generated doesn't replace any F-18 installed library. Don't try to use it for other missing dependencies as they probably need other special workaround.

Regards,


-- 
NVieville

Comment 10 tdcristian 2013-02-06 16:41:55 UTC
Thanks for information.

Comment 11 Andrew 2013-03-12 23:10:28 UTC
I need the 64-bit version of this myself for the Canon PIXMA MX510 series drivers. In response to comment1 - fat chance of the vendor lifting a finger. Canon is notorious for deep-throating M$ to the point that the USA branch lies about any of part of their company supporting Linux and then when I called them out as liars by showing them the links to Canon Europe's linux drivers, they then outright admitted that they have no intentions of supporting Linux.

As for the Europe branch, at least they have drivers (using the latest ver 3.7 rpm package) and it asked for a lot of compatibility library such as libpng and libpangox. When it comes to Canon, people are lucky Linux drivers even exist and the odds them lifting a finger to help Linux is slim to none. (I got tricked by the damn Universal logo on the box only to realize that's a logo relative to Apple only)

I attempted softlinking the dependency to the current version of libtiff but no dice.

In short, please put this in the repos as I'd like to not have to buy another $100+ multi-function device over this non-sense.

Comment 12 Andrew 2013-03-13 00:25:13 UTC
(In reply to comment #9)
> Hi Daniel,
> 
> (In reply to comment #8)
> > Please can you post more precise steps to create:
> > libtiff3-3.9.7-1.fc18.x86_64.rpm 
> > Unfortunately I was not able to create this package.
> 
> In order to be able to rebuild a package you have to install some useful
> tools and their dependencies (in a root console):
> 
> yum install rpm-build rpmdevtools
> 
> Then set up a rpm build environment (in your user console):
> 
> rpmdev-setuptree
> 
> This will create a rpmbuild directory in your ${HOME} directory (with
> ${HOME} corresponding to your current user directory).
> 
> Then download the libtiff SRPMS for F-17 from
> http://download.fedoraproject.org/pub/fedora/linux/updates/17/SRPMS/libtiff-
> 3.9.7-1.fc17.src.rpm for example (or any mirror available near you).
> 
> Extract this package in a clean and empty folder (file-roller may be helpful
> for that).
> 
> Edit the libtiff.spec file in order to replace the line:
> 
> Name: libtiff
> 
> by:
> 
> Name: libtiff3
> 
> Save this file. Copy this modified libtiff.spec file in your
> ${HOME}/rpmbuild/SPECS/ directory. Copy all the other files (libtiff*.patch
> and tiff-3.9.7.tar.gz) in your ${HOME}/rpmbuild/SOURCES/ directory.
> 
> Then in your user console type:
> 
> rpmbuild -ba ${HOME}/rpmbuild/SPECS/libtiff.spec
> 
> If everything goes well, you should see a message telling you that some RPMS
> files were written in your ${HOME}/rpmbuild/RPMS/your_current_arch/
> directory (with your_current_arch equal to x86_64 or i386 or i586 or i686).
> 
> If some error messages show you that some building dependencies packages are
> missing, install them in the root console with yum.
> 
> Once the package built without error, in the root console type:
> 
> yum localinstall --nogpgcheck
> /path_to_your_user_home/rpmbuild/RPMS/your_current_arch/libtiff3-3.9.7-1.
> fc18.your_current_arch.rpm
> 
> This will install the newly built package you needed. Don't forget
> --nogpgcheck option as we don't sign the locally built packages.
> 
> Be careful, these explanations are only valid for this case because the
> package generated doesn't replace any F-18 installed library. Don't try to
> use it for other missing dependencies as they probably need other special
> workaround.
> 
> Regards,
> 
> 
> -- 
> NVieville

NVieville, THANK YOU!!!! Worked perfectly! Is there any way to get the .rpm this created added to the repo so no one else has to go through this?

Comment 13 Gerard van der Veen 2013-03-16 10:46:19 UTC
To produce the rebuild went perfectly: a good explanation, but my architecture is 64 and libtiff.so.3 is now in /usr/lib64 but not in /usr/lib

The current version libtiff.so.5 is in both lib and lib64 and indeed the libtiff package contains files for lib and for lib64

The package built following the instructions in this topic only has files for lib64

When I reinstall cnijfilter-ip2200-2.60-1.i386.rpm there is an unresolved dependency for libtiff.so.3

So how to obtain a rebuild with 32 bit compatibility?


Thanks for information.

Comment 14 nicolas.vieville 2013-03-16 15:59:12 UTC
(In reply to comment #13)
> So how to obtain a rebuild with 32 bit compatibility?

I'm afraid the way is a little bit less straight forward.

As the most common way using --target=i686 option of rpmbuild seems not working, your only option is to use mock.

First install mock (type in root console):

yum install mock

Then, when you reach the step where the rpmbuild command is used in my previous explanation, just use the commands below in replacement. 
In your user console type:

rpmbuild -bs --define "dist .fc18" --define "fedora 18" ${HOME}/rpmbuild/SPECS/libtiff.spec

This build the SRPM file containing everything needed to build the binary package. You can find it as ${HOME}/rpmbuild/SRPMS/libtiff3-3.9.7-1.fc18.src.rpm

Then build the binary package using this command in your user console (one line, maybe wrapped here in this thread):

mock -r fedora-18-i386 --installdeps --resultdir /var/lib/mock/fedora-18-i386/result rebuild ${HOME}/rpmbuild/SRPMS/libtiff3-3.9.7-1.fc18.src.rpm

If everything goes well you should find the corresponding package built in the /var/lib/mock/fedora-18-i386/result directory. You can then copy the libtiff3 packages from this directory in your user directory, but it's not mandatory.

Then proceed as explained above to install the needed package, for example if you didn't copy the file from the mock destination folder, type in a root console:

yum localinstall --nogpgcheck /var/lib/mock/fedora-18-i386/result/libtiff3-3.9.7-1.fc18.i686.rpm

Maybe you have too force the install as some documentation files are shared by the x86_64 package and the i686 one, if you want to keep the 2 versions of this package. As your need seems to be only for a 32bits tool (cnijfilter-ip2200-2.60-1.i386.rpm), maybe you should uninstall the x86_64 package before installing the i686 one.

Hope these explanation were clear enough and useful.

Cordially,


-- 
NVieville

Comment 15 Gerard van der Veen 2013-03-17 10:32:09 UTC
The advice is really clear and precise: expert!
Everything worked as expected and there was only one moment of doubt when yum installed for mock a 32 bit system of over 400M without displaying any progress.

Having installed libtiff3-3.9.7-1.fc18.i686.rpm, I re-installed the three canon rpm's and there was no longer the libtiff dependency problem, and the printer worked as before the fc18 update.

Thanks very much
Gerard van der Veen

Comment 16 Paul Lambert 2013-04-14 03:01:12 UTC
Gerard, 

Would it be possible for you to share you legacy libtiff RPM by posting it somewhere for all to download if needed?  Otherwise, using legacy printers such as Canons or many printers on linux it is much easier just to run a virtual Windows machine using VMware or VirtualBox.

Comment 17 Gerard van der Veen 2013-04-14 07:34:06 UTC
Created attachment 735548 [details]
libtiff RPM as requested by Paul Lambert

This is the libtiff3-3.9.7-1.fc18.i686.rpm created by the procedure NVieville outlined in comment 14

I do not see a way to put this in a repository so putting it here is all I can do.

Comment 18 Fedora Admin XMLRPC Client 2013-05-14 13:54:58 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 19 Petr Hracek 2013-06-26 10:47:47 UTC
Well, I will try to add that compatibility package into Fedora 19 and 18.

Is there any person who would like to be a co-maintainer?

Comment 20 Paul Lambert 2013-06-27 01:37:56 UTC
I would suggest dropping support for this package as Tom suggested in comment 1.  I attempted to install the libtiff3-3.9.7-1.fc18.i686.rpm but could not resolve all of the dependencies.  I have a Canon MX350 wifi printer driver that uses the libtiff3 library.  I switched to CUPS and it works better than it ever did with the Canon supplied driver.  I don't see many users needing this except to support old hardware.    

As for scanning, there are two alternate solutions.  1) just plugin a thumb driver and let the scanner store the documents there then move it to your computer and copy them off of the thumb drive.  Or, 2) use a smart phone app that interfaces with your (wifi) printer.  I have the Canon Apple app installed on my iPod and I can control scanning without ever hitting a button on the printer/scanner.  Any document I scan is sent back to the iPod.  I can move the document to my computer via a webDAV server, simply plugin the iPod into my computer or email the scanned documents to myself as attached docs from the iPod. (when it is connected to wifi)

Other than that, run a legacy system that supports libtiff3 as a virtual machine.  The reason that vendors stop supporting old software is that not many are using it.  Fedora (Linux) should do the same.  The more software that is included in a typical distro, the more chance for bugs. There are a lot of other bugs as well as features that need addressing in Fedora than this one.

Comment 21 Per Arnold Blåsmo 2013-07-20 12:49:12 UTC
Created attachment 776147 [details]
libtiff3 RPM for Fedora 19

I bought a Canon MG5450 and tried to connect it to Fedora 19. Found this and built libtiff3 for Fedora 19.

I upload the RPM i used to get it to work.

Comment 22 Per Arnold Blåsmo 2013-07-20 12:50:50 UTC
Created attachment 776148 [details]
SRPM for libtiff3 for Fedora 19

Here is the source RPM for the libtiff3 RPM I built for Fedora 19.

Comment 23 Petr Hracek 2013-07-23 10:59:50 UTC
Hi guys,

finally I have made a several packages as for F19 as for F18 (architectures x86_64 and i686)

As Tom suggested and Paul as well https://bugzilla.redhat.com/show_bug.cgi?id=901448#c1 https://bugzilla.redhat.com/show_bug.cgi?id=901448#c20

no compatibility package will be created.
Packages are available here:
http://phracek.fedorapeople.org/libtiff3/

It should be based on Package guidelines.

Comment 24 Mark Alford 2013-08-29 21:06:33 UTC
I managed to solve this problem by simply making a soft link

(as root)
cd /lib64
ln -s libtiff.so.5 libtiff.so.3

and you can do the same in /lib for the 32-bit binary.

Comment 25 Honza Horak 2013-08-30 07:17:46 UTC
(In reply to Mark Alford from comment #24)
> I managed to solve this problem by simply making a soft link
> 
> (as root)
> cd /lib64
> ln -s libtiff.so.5 libtiff.so.3
> 
> and you can do the same in /lib for the 32-bit binary.

Let me just point out for anybody else that this is not very safe way to solve such issues. Rebuilding the older package on yourself (or use the one from comment #21) should be much more safe.

Comment 26 Thank You 2013-09-15 15:21:04 UTC
(In reply to Petr Hracek from comment #23)

> Packages are available here:
> http://phracek.fedorapeople.org/libtiff3/
> 

Thank you so much for this page and all explanations. I could now re-use my printer Canon MP550 on F19.

Best regards,

Comment 27 Jiri Popelka 2015-12-28 17:27:47 UTC
(In reply to Petr Hracek from comment #23)
> Packages are available here:
> http://phracek.fedorapeople.org/libtiff3/

It's no longer there.

(In reply to Per Arnold Blåsmo from comment #22)
> Created attachment 776148 [details]
> SRPM for libtiff3 for Fedora 19

I took the SRPM and created a copr project 
https://copr.fedoraproject.org/coprs/jpopelka/libtiff3/
so installing libtiff3 should be as simple as
$ dnf copr enable jpopelka/libtiff3; dnf install libtiff3

enjoy ;-) (I need it too for old Canon inkjet)


Note You need to log in before you can comment on or make changes to this bug.