The master and f32 branches for these packages need to be properly retired by using fedpkg retire. Then PDC will be updated and the package will also be blocked in koji. Ideally, the packages should also contain an explanation in a dead.package file in their master/f32 branches.

They don't have such branches at all.

This command sequence worked for me to retire master for python-pip-epel:

fedpkg clone python-pip-epel
cd python-pip-epel
git checkout --orphan master
fedpkg retire "EPEL-only package"
git push --set-upstream origin master

Not sure if I have special privileges or if pagure just accepts new branches like this or if it only works because the branch is in PDC.

I wanted to avoid that dead branch. It was possible with python3-rpm.

I wanted to avoid that dead branch. It was possible with python3-rpm.

It is possible to create inconsistencies by blocking the package directly. According to PDC python3-rpm, still has an active master branch:
https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=python3-rpm

The current flow is AFAICS:

fedretire in the branch -triggers-> EOL in PDC -triggers-> package is blocked in koji

Since branches are not removed from PDC but their EOL date is updated, they should IMHO also have a corresponding branch in pagure. Otherwise this might lead to confusion again.

OK. Let me push the branches.

Pushed dead master and f31 branches to python-pip-epel, python2-wheel, python34-setuptools.

Pushed dead f31 branch to python3-rpm.

Let's see if this eventually blocks the packages.