Red Hat Bugzilla – Bug 892384
Update python-sqlalchemy0.7 to 0.7.4 or later
Last modified: 2016-01-04 09:41:37 EST
+++ This bug was initially created as a clone of Bug #838099 +++
Alembic fails to pass its unit tests against sqlalchemy-0.7.3
The author of sqlalchemy (zzzeek) thinks that an update to sqlalchemy-0.7.4 or later will fix the issue. https://twitter.com/zzzeek/status/221247697280180224
This is needed for python-alembic to build against epel6.
--- Additional comment from Toshio Ernie Kuratomi on 2012-08-30 12:27:10 EDT ---
pbrady, stevetraylen: any input here? If this sounds okay to you but you're busy, I can update. As I've been upgrading the main package (in Fedora, not in EPEL) the changelogs haven't shown any incompatible changes in the 0.7.x series. 0.7.8 is the latest.
--- Additional comment from Pádraig Brady on 2012-08-30 20:04:10 EDT ---
Thanks for the ping.
0.7.4 should be fine.
0.7.8 might be OK. That's the version used on Fedora 17.
I also scanned the changelog and noticed no obvious compat issues.
Lots of bugs fixed, and no new release since June.
OK I'll update to 0.7.8 so.
--- Additional comment from Fedora Update System on 2012-08-30 21:03:45 EDT ---
python-sqlalchemy0.7-0.7.8-1.el6 has been submitted as an update for Fedora EPEL 6.
--- Additional comment from Fedora Update System on 2012-08-31 14:31:49 EDT ---
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing python-sqlalchemy0.7-0.7.8-1.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
--- Additional comment from Fedora Update System on 2012-09-16 14:28:43 EDT ---
python-sqlalchemy0.7-0.7.8-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
sqlalchemy is low level infrastructure that would be tested implicitly through installation and use.
There is no pressing need for this update, apart form minimising the versions in use compared to epel etc.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.