Bug 680039 - smolt-server and python-sqlalchemy issues
Summary: smolt-server and python-sqlalchemy issues
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: smolt
Version: el5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-24 07:11 UTC by Chris Petersen
Modified: 2017-04-06 10:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-06 10:07:42 UTC
Type: ---


Attachments (Terms of Use)

Description Chris Petersen 2011-02-24 07:11:20 UTC
smolt-server seems to require OperationalError, which was introduced in a version of python-sqlalchemy more recent than the currently exists in epel.  I'm unsure of the specific version that introduced OperationalError, but the python-sqlalchemy0.5 package works.

This may mean that it's merely a dependency issue, but I had to use `rpm -e --nodeps python-sqlalchemy` before yum would let me install the 0.5 variant, because turbogears (also required by smolt) needs one variant or another.  This may mean that python-sqlalchemy0.5 should probably also be modified so that it provides python-sqlalchemy (though this may cause other issues).

Anyway, thought I should at least report something.

Comment 1 Fedora End Of Life 2017-04-06 10:07:42 UTC
Fedora EPEL 5 changed to end-of-life (EOL) status on 2017-03-31. Fedora EPEL 5
is no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora
or Fedora EPEL, please feel free to reopen this bug against that version. If
you are unable to reopen this bug, please file a new report against the current
release. If you experience problems, please add a comment to this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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