Bug 770828

Summary: pycairo needs to be properly renamed to python-cairo and built as per Fedora packaging guidelines
Product: [Fedora] Fedora Reporter: Peter Robinson <pbrobinson>
Component: pycairoAssignee: John (J5) Palmieri <johnp>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: i, jkeck, johnp, mbarnes, robatino
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-07 07:34:49 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:

Description Peter Robinson 2011-12-29 11:32:14 UTC 
Version 1.8.10 was released and updated in the package but due to not going through the proper packaging process for a rename it doesn't actually build in koji.

From the spec commit:
# With version 1.8.10, the upstream pycairo project began releasing multiple
# tarballs for different Python versions: py2cairo for Python 2, and pycairo
# for Python 3.  In order to provide a smooth upgrade path for users wishing
# to stay on the Python 2 version, this package was renamed to python-cairo
# and a python3-cairo package was introduced for Python 3.

The process to do this properly is listed here
http://fedoraproject.org/wiki/Upgrade_paths_%E2%80%94_renaming_or_splitting_packages
Comment 1 Peter Robinson 2012-06-06 09:48:07 UTC 
Rename rolled back as maintainer is unresponsive
Comment 2 Christopher Meng 2013-09-07 07:28:48 UTC 
*** Bug 731891 has been marked as a duplicate of this bug. ***
Comment 3 Christopher Meng 2013-09-07 07:32:40 UTC 
Reopen.

This package needs update and rename so we can continue another package.
Comment 4 Christopher Meng 2013-09-07 07:34:49 UTC 
Sorry for the mess.

*** This bug has been marked as a duplicate of bug 731891 ***