Bug #56863 libpython2.6.so.1.0 Dependency Error for Fedora >= 14
Submitted: 19 Sep 2010 22:33 Modified: 24 Nov 2010 15:51
Reporter: Andy Lawrence Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.28 OS:Linux (Fedora 14)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: fedora 14, libpython2.7.so.1.0, shared libraries

[19 Sep 2010 22:33] Andy Lawrence
Description:
Fedora 14 (currently in RC) ships with python-libs-2.7-8.fc14.1.x86_64 and libpython2.7.so.1.0.

mysql-workbench-gpl-5.2.28-1fc13.x86_64 fails to start with the following error:

[andy@ace ~]$ mysql-workbench
/usr/bin/mysql-workbench-bin: error while loading shared libraries: libpython2.6.so.1.0: cannot open shared object file: No such file or directory

Creating a symbolic link from libpython2.7.so.1.0 to libpython2.6.so.1.0 seems to work fine.

How to repeat:
Attempt to run mysql-workbench on any Fedora 14 box.

Suggested fix:
Require libpython2.6.so.1.0 or greater.
[19 Sep 2010 22:57] Alfredo Kojima
libpython is already required:

$ rpm -qp --requires mysql-workbench-gpl-5.2.28-1fc13.i386.rpm |grep libpython
libpython2.6.so.1.0  

How did you install the package? Also, fedora 14 is still in alpha and not yet supported.
[19 Sep 2010 23:02] Andy Lawrence
Yes, that is understood.  I am explaining that libpython2.6.so.1.0 does not exist in Fedora 14, libpython2.7.so.1.0 does.

Simply requiring libpython2.6.so.1.0 or libpython2.7.so.1.0 will prevent a dependency error when F14 final hits.
[23 Sep 2010 18:28] Alfredo Kojima
I meant that libpyton2.6 is already in the requires list, it is added automatically by RPM.
You were not supposed to be able to install it if that lib is not installed, unless you forced it to
ignore the dependencies list.
[23 Sep 2010 20:36] Andy Lawrence
I'm not sure where the mis communication is.  I fully understand that libpython2.6.so.1.0 is in the spec file and that is should not install on Fedora 14.

What I'm saying is the spec file needs modified to allow installation on Fedora 14.  I am warning the package maintainer a newer version has been included in Fedora 14 and when Fedora 14 is released (11-2-2010) it will not install.

If you are the package maintainer you should understand this concept.  If you are and don't understand please Email me and I'll show you how to properly modify the spec file.

dr.diesel@gmail.com
[23 Sep 2010 21:15] Andy Lawrence
My bad.  Downloaded the source, more than just a spec file change.

Same problem, different solution.
[24 Sep 2010 12:51] Alfredo Kojima
Ok, now I understand. You want fedora 14 packages. That is simply not currently supported. Once Fedora 14 final is out we will probably provide packages for it, but this is not really a bug.

How did the compilation from sources go?
[25 Sep 2010 12:55] Andy Lawrence
Compiling from source went fine, no issues.  I have not fully tested but it looks pretty good!

Maybe the best explanation is that I'm trying to file an upstream bug for Fedora 14 and the libpython 2.7 change!

Please close bug if you do not feel this path is correct, thanks!
[3 Nov 2010 18:53] Jeremey Hustman
I just installed the release version of Fedora 14 and ran into the same problem:

mysql-workbench-gpl-5.2.29-1fc13.i386 requires libpython2.6.so.1.0
[3 Nov 2010 20:35] Andy Lawrence
A dirty work-a-round:

ln -s /usr/lib64/libpython2.7.so.1.0 /usr/lib64/libpython2.6.so.1.0

Than you can then force the package install:

rpm -ivh --force --nodeps mysql-workbench-gpl-5.2.29-1fc13.x86_64.rpm

Thanks
Andy
[23 Nov 2010 10:59] Johannes Taxacher
Fedora 14 packages are available starting with 5.2.30
[24 Nov 2010 15:51] Tony Bedford
An entry has been added to the 5.2.30 changelog:

On Linux Fedora 14, MySQL Workbench generated an error on startup:

/usr/bin/mysql-workbench-bin: error while loading shared libraries: libpython2.6.so.1.0:
cannot open shared object file: No such file or directory