Bug 963158 - Should we split off the python-storm-twisted?
Summary: Should we split off the python-storm-twisted?
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-storm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-15 09:38 UTC by Christopher Meng
Modified: 2013-07-20 09:46 UTC (History)
1 user (show)

Fixed In Version: python-storm-0.20-1.fc19
Clone Of:
Environment:
Last Closed: 2013-07-20 09:46:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Christopher Meng 2013-05-15 09:38:00 UTC 
I've checked opensuse, they make a subpackage named python-storm-twisted, but I find Fedora includes it into the main package.

Any idea?
Comment 1 Michel Lind 2013-06-18 03:25:22 UTC 
That's probably a good idea, will push an update to Rawhide first and see how that goes
Comment 2 Fedora Admin XMLRPC Client 2013-07-05 12:22:12 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Fedora Update System 2013-07-10 07:56:58 UTC 
python-storm-0.20-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-storm-0.20-1.fc19
Comment 4 Fedora Update System 2013-07-11 02:31:51 UTC 
Package python-storm-0.20-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-storm-0.20-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12728/python-storm-0.20-1.fc19
then log in and leave karma (feedback).
Comment 5 Fedora Update System 2013-07-20 09:46:17 UTC 
python-storm-0.20-1.fc19 has been pushed to the Fedora 19 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.