RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 813925 - Requested upgrade of python-repoze-what-plugins-sql
Summary: Requested upgrade of python-repoze-what-plugins-sql
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python-repoze-what-plugins-sql
Version: 6.4
Hardware: noarch
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Python Maintainers
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 818293
TreeView+ depends on / blocked
 
Reported: 2012-04-18 19:05 UTC by Ralph Bean
Modified: 2016-07-14 15:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-14 15:05:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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