Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1695218 - Rebuild jpype with python2 support
Summary: Rebuild jpype with python2 support
Keywords:
Status: CLOSED DUPLICATE of bug 1760983
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-jaydebeapi
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jedelsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-02 16:36 UTC by Tuomo Soini
Modified: 2019-11-29 21:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-29 21:44:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Proposed patch (2.89 KB, patch)
2019-04-02 16:36 UTC, Tuomo Soini
no flags Details | Diff

Description Tuomo Soini 2019-04-02 16:36:56 UTC
Created attachment 1551083 [details]
Proposed patch

Latest versions of jpype on epel7 remove python2 support. Unfortunately there is still python2-jaydebeapi-1.1.1-2.el7.noarch which depends on python2-jpype. Please rebuild with python2 support. Attached patch restores python2 support on epel7.

Comment 1 Raphael Groner 2019-04-08 22:10:43 UTC
Thanks for your report.
Personally, I'm not interested in python2 because of announced EOL in favor of python3. Please delegate this bug to python-jaydebeapi and ask to drop python2 there as well.
See also: https://pythonclock.org/

Comment 2 Jakub Jedelsky 2019-11-29 21:44:13 UTC
I totally missed that issue. There is another request to get rid of python2 version of jaydebeapi, thus closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1760983 ***


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