Bug 1235302 - Build python3-MySQL subpackage
Summary: Build python3-MySQL subpackage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: MySQL-python
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Dorňák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1235271
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-24 13:33 UTC by Jakub Dorňák
Modified: 2015-07-10 19:03 UTC (History)
4 users (show)

Fixed In Version: MySQL-python-1.3.6-3.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of: 1235271
Environment:
Last Closed: 2015-07-10 19:03:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jakub Dorňák 2015-06-24 13:33:03 UTC
+++ This bug was initially created as a clone of Bug #1235271 +++

MySQL-python is currently missing python3 subpackage.

Upstream claims that it supports python3 for this package, please build the python3 subpackage for MySQL-python (python3-MySQL).

Also please consider adding provides/renaming package to python-MySQL so it corresponds to python naming guidelines.

Comment 1 Fedora Update System 2015-06-24 13:51:28 UTC
MySQL-python-1.3.6-3.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/MySQL-python-1.3.6-3.fc22

Comment 2 Fedora Update System 2015-06-25 08:24:59 UTC
Package MySQL-python-1.3.6-3.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing MySQL-python-1.3.6-3.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-10715/MySQL-python-1.3.6-3.fc22
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2015-07-10 19:03:39 UTC
MySQL-python-1.3.6-3.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


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