Bug 623319

Summary:	ibus-pinyin may need to be rebuilt against Python 2.7 in F14 and rawhide
Product:	[Fedora] Fedora	Reporter:	Dave Malcolm <dmalcolm>
Component:	ibus-pinyin	Assignee:	Peng Wu <pwu>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	i18n-bugs, pwu, shawn.p.huang
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ibus-pinyin-1.3.10-1.fc14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-01 03:26:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	623233, 624641
Bug Blocks:	619913

Description Dave Malcolm 2010-08-11 18:32:30 UTC

This is an automatically-filed bug.

ibus-pinyin-1.3.9-1.fc14 contains one or more .pyc files, but has not been rebuilt since Python 2.7 was built for Fedora, and thus the .pyc files presumably are for Python 2.6.  Python 2.7 changed the bytecode format, so usage of those files will typically fail (see e.g. bug 621726).

The package needs to be rebuilt against python 2.7 in both F14 and devel.

Information on the new "dist-git" system can be seen here:
  http://fedoraproject.org/wiki/Using_Fedora_GIT

Information on common difficulties with Python 2.7 rebuilds can be seen here:
  https://fedoraproject.org/wiki/Features/Python_2.7

Once it's been successfully rebuilt for F14, an update needs to be filed to get the rebuild into F14:
  https://admin.fedoraproject.org/updates/new/

Please add this bug to the update, to make it easy to track what's been done, and what's left to do.

I'm sorry that this component was not handled by the mass rebuild.  (This may be due to bug 623233)

Comment 1 Dave Malcolm 2010-08-12 00:31:01 UTC

I tried to rebuild this, but it failed:
http://koji.fedoraproject.org/koji/getfile?taskID=2394897&amp;name=build.log

checking for Boost headers version >= 103900... yes
checking for Boost's header version... 1_44
checking boost/signals2.hpp usability... no
checking boost/signals2.hpp presence... no
checking for boost/signals2.hpp... no
configure: error: cannot find boost/signals2.hpp
error: Bad exit status from /var/tmp/rpm-tmp.LYDpVp (%build)
    Bad exit status from /var/tmp/rpm-tmp.LYDpVp (%build)
RPM build errors:
Child returncode was: 1

Comment 2 Peng Wu 2010-08-20 05:41:27 UTC

ibus-pinyin's configure script fails on detection of boost/signals2.hpp.
Built in rawhide with updated boost-1.44.0-0.6, ibus-pinyin got compiled.
Currently wait for boost updates for Fedora 14.

A bug report is opened against boost:
Bug 624641 - Problems when compiling a package which uses boost::signals2
URL:https://bugzilla.redhat.com/show_bug.cgi?id=624641

Comment 3 Fedora Update System 2010-08-30 03:17:04 UTC

ibus-pinyin-1.3.10-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/ibus-pinyin-1.3.10-1.fc14

Comment 4 Fedora Update System 2010-08-30 03:17:08 UTC

ibus-pinyin-1.3.10-1.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/ibus-pinyin-1.3.10-1.fc13

Comment 5 Fedora Update System 2010-08-30 19:39:34 UTC

ibus-pinyin-1.3.10-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update ibus-pinyin'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/ibus-pinyin-1.3.10-1.fc14

Comment 6 Fedora Update System 2010-09-01 03:26:03 UTC

ibus-pinyin-1.3.10-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2010-09-01 05:45:42 UTC

ibus-pinyin-1.3.10-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.