Bug 813925

Summary: Requested upgrade of python-repoze-what-plugins-sql
Product: Red Hat Enterprise Linux 6 Reporter: Ralph Bean <rbean>
Component: python-repoze-what-plugins-sqlAssignee: Python Maintainers <python-maint>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: bkabrda, cstratak, lmacken, pviktori, tlavigne
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: noarch   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-14 15:05:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 818293    

Description Ralph Bean 2012-04-18 19:05:03 UTC
python-repoze-what-plugins-sql currently packages version 1.0.0 of repoze.what.plugins.sql.

Version 1.0.1 of the upstream was released about 1 year ago.  There were two changes made to the source, one which supports sqlalchemy (python-sqlalchemy) 0.7 and later.  We need this feature for current app development in the Fedora Infrastructure team.

Those commits are available here:
  https://github.com/repoze/repoze.what-sql/commits/master

It appears that the changes won't introduce any regressions.

We could:

  1) Just cherry-pick commits from github as patches.
  2) Bring the python-repoze-what-plugins-sql package from Fedora 17 over to RHEL as it already packages 1.0.1.

Comment 2 Dave Malcolm 2012-04-18 21:26:27 UTC
(In reply to comment #0)
> python-repoze-what-plugins-sql currently packages version 1.0.0 of
> repoze.what.plugins.sql.
> 
> Version 1.0.1 of the upstream was released about 1 year ago.  There were two
> changes made to the source, one which supports sqlalchemy (python-sqlalchemy)
> 0.7 and later.  We need this feature for current app development in the Fedora
> Infrastructure team.

Are you referring to this specific commit?
https://github.com/repoze/repoze.what-sql/commit/503ade229b3c8481158867de50de7a3af38584aa
^^^ this seems to be the commit fixing compatibility with SQLAlchemy 0.7.

There's also this commit:
https://github.com/repoze/repoze.what-sql/commit/435e0d32ad6e402b8d78d64108d767b48a6fffa2
but this seems to a new feature that uses SQLAlchemy 0.7, rather than a compatibility fix (albeit with a coverage #pragma).

Do you merely need the compat (503ade229b3c8481158867de50de7a3af38584aa), or are you looking for the new feature (435e0d32ad6e402b8d78d64108d767b48a6fffa2)?

Comment 3 Luke Macken 2012-04-18 21:46:06 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > python-repoze-what-plugins-sql currently packages version 1.0.0 of
> > repoze.what.plugins.sql.
> > 
> > Version 1.0.1 of the upstream was released about 1 year ago.  There were two
> > changes made to the source, one which supports sqlalchemy (python-sqlalchemy)
> > 0.7 and later.  We need this feature for current app development in the Fedora
> > Infrastructure team.
> 
> Are you referring to this specific commit?
> https://github.com/repoze/repoze.what-sql/commit/503ade229b3c8481158867de50de7a3af38584aa
> ^^^ this seems to be the commit fixing compatibility with SQLAlchemy 0.7.
 
Yup, that's the one.

> There's also this commit:
> https://github.com/repoze/repoze.what-sql/commit/435e0d32ad6e402b8d78d64108d767b48a6fffa2
> but this seems to a new feature that uses SQLAlchemy 0.7, rather than a
> compatibility fix (albeit with a coverage #pragma).

What new SA 0.7 feature does it use?

> Do you merely need the compat (503ade229b3c8481158867de50de7a3af38584aa), or
> are you looking for the new feature (435e0d32ad6e402b8d78d64108d767b48a6fffa2)?

We don't need the new feature, but it looked harmless at a first glance. We've been shipping this version since F16 as well. However, if it's easier to cherry-pick around it, that's fine.

Comment 4 Ralph Bean 2012-04-18 22:27:49 UTC
Yes.  This is the only commit we need:
https://github.com/repoze/repoze.what-sql/commit/503ade229b3c8481158867de50de7a3af38584aa

Luke covered it.

Comment 6 RHEL Program Management 2012-07-10 06:52:54 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2012-07-11 01:59:02 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 8 RHEL Program Management 2012-09-07 05:22:01 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 10 Petr Viktorin (pviktori) 2016-07-14 15:05:23 UTC
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.