Bug 1767258 - Please build python-PyPDF2 for EPEL7 and EPEL8
Summary: Please build python-PyPDF2 for EPEL7 and EPEL8
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-PyPDF2
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ranjan Maitra
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1765572
TreeView+ depends on / blocked
 
Reported: 2019-10-31 02:21 UTC by Scott Talbert
Modified: 2023-02-24 17:06 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-02-24 17:06:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Scott Talbert 2019-10-31 02:21:22 UTC
Please build python-PyPDF2 for EPEL7 and EPEL8.  For EPEL7, it appears there is already a branch, but it has never been built.  I have prepared a pull request to update the EPEL7 version:

https://src.fedoraproject.org/rpms/python-PyPDF2/pull-request/2

If you're not interested in maintaining EPEL7 and EPEL8 branches, I'm willing to be a co-maintainer.  FAS: swt2c

Comment 1 Major Hayden 🤠 2019-11-05 17:30:53 UTC
Scott -- I orphaned that package a while back and 'aarem' picked it up: https://src.fedoraproject.org/user/aarem

Comment 2 Scott Talbert 2019-11-05 18:03:35 UTC
(In reply to Major Hayden from comment #1)
> Scott -- I orphaned that package a while back and 'aarem' picked it up:
> https://src.fedoraproject.org/user/aarem

You cancelled aarem's needinfo request too.  :P

Comment 3 Major Hayden 🤠 2019-11-05 18:04:34 UTC
Oof, sorry about that, Scott. :)

Comment 4 Ranjan Maitra 2023-02-24 16:55:02 UTC
Scott, I am no longer interested in supporting EPEL7 and EPEL8. Do you still want to do that? Or do you want to co-maintain for Fedora?

Comment 5 Scott Talbert 2023-02-24 17:01:37 UTC
(In reply to Ranjan Maitra from comment #4)
> Scott, I am no longer interested in supporting EPEL7 and EPEL8. Do you still
> want to do that? Or do you want to co-maintain for Fedora?

No, I'm no longer interested in this package.


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