Bug 1310662 - missing pyp2rpm package
Summary: missing pyp2rpm package
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: epel-release
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Stahnke
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-22 12:46 UTC by clime
Modified: 2016-04-02 19:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-23 14:27:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description clime 2016-02-22 12:46:58 UTC
Hello, could you add package pyp2rpm (https://github.com/fedora-python/pyp2rpm) to epel7 repository? I am one of COPR guys (https://fedorahosted.org/copr/) and we have just implemented a new feature to perform building from PyPI. This feature needs the package to be present on one of the building machines (copr-dist-git) which runs on RHEL7. It would help if pyp2rpm was present in the official EPEL7 repository so that we do not need to maintain it in a separate COPR repository. Thank you.

Comment 1 Kevin Fenzi 2016-02-23 14:27:49 UTC
That package is already in Fedora, so I would file a bug against it requesting an EPEL7 branch: 

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=pyp2rpm

If you don't hear anything back from them in a week, let me know and I can just request the branch.

Comment 2 clime 2016-03-09 09:03:18 UTC
Hello, do you think it would be possible for you to request the EPEL branch? I have filed the bug against the package as you suggested (Bug 1312927 - Release for EPEL7) but there is still no response (about 10 days already:().

Comment 3 Fedora Update System 2016-04-02 19:08:05 UTC
pyp2rpm-2.0.0-3.el7 python-flexmock-0.10.2-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-4046bd9a65


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