Bug 1625710 - python2-pytoml overrides python-pytoml from rhel-7-server-extras-rpms
Summary: python2-pytoml overrides python-pytoml from rhel-7-server-extras-rpms
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-pytoml
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Julien Enselme
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-05 15:37 UTC by Carl George 🤠
Modified: 2018-11-26 21:02 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-26 21:02:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carl George 🤠 2018-09-05 15:37:07 UTC
Description of problem:
The python2-pytoml subpackage overrides python-pytoml from rhel-7-server-extras-rpms.  This is a violation of EPEL policy.  Please remove it from the spec file.

Version-Release number of selected component (if applicable):
python-pytoml-0.1.18-1.el7

Additional info:
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy

Comment 1 none 2018-10-31 10:53:50 UTC
We can confirm this issue.

Please remove the package from EPEL.

Comment 2 Fedora Update System 2018-11-04 13:17:47 UTC
python-pytoml-0.1.18-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-6d311024d9

Comment 3 Julien Enselme 2018-11-04 13:18:37 UTC
It should be good soon in update testing. Thanks for pointing that out.

Comment 4 Fedora Update System 2018-11-05 00:10:06 UTC
python-pytoml-0.1.18-2.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-2018-6d311024d9

Comment 5 Carl George 🤠 2018-11-05 14:30:35 UTC
I'm sorry Julien, but that won't be sufficient.  The python-pytoml SRPM still conflicts with the RHEL python-pytoml SRPM.  The EPEL7 branch must be retired.

To continue to build python34-pytoml for EPEL7, you'll have to submit a new package review for python3-pytoml.spec that creates a python34-pytoml subpackage.  This naming is described in the EPEL7 Python3 proposal [0].

> If a python-<name> SRPM exists in base RHEL, python3-<name> must be created and used.

This would fall under the rename guidelines [1] and would be a straightforward review, which I can do for you once you submit it.

[0]: https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3
[1]: https://fedoraproject.org/wiki/Package_Renaming_Process

Comment 6 Carl George 🤠 2018-11-05 14:38:23 UTC
I also just noticed that the proposed update has python34-pytoml obsoleting the stock python-pytoml package due to this commit.

https://src.fedoraproject.org/rpms/python-pytoml/c/dd37a93bc8a2cfd7de6d8b3c6f8455fde4dee3d9

Please unpush that update from epel-testing.

Comment 7 Julien Enselme 2018-11-11 11:31:00 UTC
Can you confirm that I must follow this procedure to solve the issue: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life?

Comment 8 Carl George 🤠 2018-11-12 15:18:23 UTC
Yes, that's the procedure.  Just ensure you run `fedpkg retire` only in the epel7 branch.

Comment 9 Julien Enselme 2018-11-13 19:52:48 UTC
I just run `fedpkg retire` on epel https://src.fedoraproject.org/rpms/python-pytoml/c/c6c90ea77adb64752cc18f52e6562fa7fd6ec3fe?branch=epel7 It should be good soon. If not, ping me.

Comment 10 Carl George 🤠 2018-11-26 21:02:35 UTC
$ koji list-pkgs --show-blocked --tag epel7 --package python-pytoml
Package                 Tag                     Extra Arches     Owner          
----------------------- ----------------------- ---------------- ---------------
python-pytoml           epel7                                    releng          [BLOCKED]


Looks like we're good now.  Thanks!


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