Bug 2065094 - EPEL7 - python36-certifi disappeared from repo
Summary: EPEL7 - python36-certifi disappeared from repo
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: distribution
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Troy Dawson
QA Contact:
URL:
Whiteboard:
: 2065498 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-17 10:59 UTC by sayf-eddine.hammemi
Modified: 2022-04-19 15:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-19 15:49:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description sayf-eddine.hammemi 2022-03-17 10:59:57 UTC
Description of problem:

The package python36-certifi disappeared from EPEL7


Version-Release number of selected component (if applicable):


How reproducible:

simple

Steps to Reproduce:
1. yum install -y epel-release (on a centos7)
2. yum install python36-certifi
3. --> Error

Actual results:

No package python36-certifi available.

Expected results:

```
Installed Packages
Name        : python36-certifi
Arch        : noarch
Version     : 2018.10.15
Release     : 5.el7
Size        : 9.6 k
Repo        : installed
From repo   : epel
```

Additional info:
https://src.fedoraproject.org/rpms/python-certifi
EPEL7 has no stable version

Comment 1 Miro Hrončok 2022-03-17 11:05:09 UTC
Seems like python-certifi was untagged from epel7 completely. No idea why.

Comment 2 Miro Hrončok 2022-03-17 11:09:45 UTC
The package is blocked in Koji:

$ koji list-pkgs --show-blocked  --tag epel7 --quiet --package python-certifi
python-certifi          epel7                                    churchyard      [BLOCKED]


But not retired in dist-git: https://src.fedoraproject.org/rpms/python-certifi/commits/epel7


PDC says "active": false -- https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=epel7&global_component=python-certifi

            "slas": [
                {
                    "id": 690861,
                    "sla": "stable_api",
                    "eol": "2022-03-14"
                },
                {
                    "id": 690862,
                    "sla": "security_fixes",
                    "eol": "2022-03-14"
                },
                {
                    "id": 690863,
                    "sla": "bug_fixes",
                    "eol": "2022-03-14"
                }
            ],

So apparently, something/somebody decided it is a good idea to stop supporting python-certifi in epel7 on 2022-03-14.

I guess when the package was imported to epel7, this was supposed to be the end date of epel7? This might actually impact more packages.

Comment 3 Miro Hrončok 2022-03-17 11:10:56 UTC
> I guess when the package was imported to epel7...

Imported to PDC actually.

Comment 4 Miro Hrončok 2022-03-17 11:22:18 UTC
I've curl+grep checked epel7 in PDC and found 1 other package that has EOL in 2022, but that one was actually retired in dist git.

So this appears to be specific for python-certifi.

I've opened https://pagure.io/releng/issue/10706 to get this sorted out, but I wish we didn't have to deal with PDC :(

Comment 5 sayf-eddine.hammemi 2022-03-17 11:31:37 UTC
> I've opened https://pagure.io/releng/issue/10706 to get this sorted out, but I wish we didn't have to deal with PDC :(

Thank you very much for the help

Comment 6 Miro Hrončok 2022-03-18 09:01:13 UTC
*** Bug 2065498 has been marked as a duplicate of this bug. ***

Comment 7 Miro Hrončok 2022-03-18 12:57:11 UTC
The package was unretired by releng. Waiting for the next EPEL7 compose.


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