Bug 1760983 - EPEL7 - python2-jaydebeapi won't install on RHEL 7.7
Summary: EPEL7 - python2-jaydebeapi won't install on RHEL 7.7
Keywords:
Status: CLOSED CURRENTRELEASE
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:
: 1695218 (view as bug list)
Depends On:
Blocks: EPEL7FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2019-10-11 20:57 UTC by Troy Dawson
Modified: 2019-12-16 14:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-16 14:33:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Troy Dawson 2019-10-11 20:57:30 UTC
Current python2-jaydebeapi for EPEL7 (python2-jaydebeapi-1.1.1-2.el7) requires
  python2-jpype
EPEL7 only has
  python36-jpype

Please fix this package so that it can be installed in RHEL 7.7.
If you have not responded in a week, we will have a proven packager fix it.
If you know you will not be able to get to it and would like it fixed sooner, please let us know in this bug.
If you feel this package should no longer be in EPEL7, please let us know in this bug.

Comment 1 jakub.jedelsky 2019-10-23 12:49:50 UTC
Thanks for info, Troy. I found #1639324, where python2-jpype was removed. I'll try to solve the issue asap (by removing it as well / discussing python2 with jpype maintainer).

Comment 2 Troy Dawson 2019-11-08 21:04:38 UTC
Any news on this?

My opinion is that python-jaydebeapi should be rebuilt in EPEL7 without python2.
I have checked and there is nothing that depends on python2-jaydebeapi, so it's going away will not break anything.

Comment 3 Fedora Update System 2019-11-29 21:33:42 UTC
FEDORA-EPEL-2019-1cc43d3a46 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1cc43d3a46

Comment 4 jakub.jedelsky 2019-11-29 21:39:47 UTC
Hi Troy,

sorry for such long delay. I just build new version of the package to support just python36, thus python2 version won't build anymore, see update above.
But ... I'm not sure with next step. I guess there is (and will stay) python2 package in epel repository, right? Am I able to drop it somehow or should I ask to get rid of it somewhere? I never did anything like that as far as I remember and can't find relevant docs.

Thanks.

Comment 5 jakub.jedelsky 2019-11-29 21:44:13 UTC
*** Bug 1695218 has been marked as a duplicate of this bug. ***

Comment 6 Fedora Update System 2019-11-30 01:35:07 UTC
python-jaydebeapi-1.1.1-8.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1cc43d3a46

Comment 7 Troy Dawson 2019-12-02 14:49:07 UTC
When the update, that is currently in epel-testing, get's pushed to stable, so that it's in epel, then python2-jaydebeapi will automatically go away.
This is because epel only keeps the latest builds.  Since python2-jaydebeapi was built from python-jaydebeapi, when you update python-jaydebeapi all of the old python-jaydebeapi packages go away, and only the new ones are left.  Since python2-jaydebeapi is no longer part of the new python-jaydebeapi, it automatically goes away.

Thank you for getting this updated.

Comment 8 jakub.jedelsky 2019-12-08 20:27:40 UTC
Many thanks for explanation, Troy!
I will keep the issue open until will be closed by bodhi's update.

Comment 9 Fedora Update System 2019-12-15 07:51:22 UTC
python-jaydebeapi-1.1.1-8.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Troy Dawson 2019-12-16 14:33:05 UTC
I have verified that python2-jaydebeapi is no longer in epel7.
Closing ticket.


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