OK with some help from Miro on the python team, I was able to use the scripts they use regularly to list what dependency problems they have with soon to be orphaned packages. I have included the entire report as an attachment as its big, but the following seem to be packages I could retire now without breaking current packages:

python-cryptography-vectors cheimes, jcline, noodles, npmccallum 229 weeks ago
python-hamcrest ignatenkobrain 238 weeks ago
python-hupper infra-sig, kevin 238 weeks ago
python-nose2 abompard 238 weeks ago
python-openid-cla puiterwijk 238 weeks ago
python-openid-teams puiterwijk 238 weeks ago
python-pytest-benchmark jorti 234 weeks ago
python-pytest-forked swt2c 236 weeks ago
python-pytest-xdist swt2c 238 weeks ago
python-sphinx-theme-py3doc-enhanced jujens 238 weeks ago
python-venusian infra-sig, lmacken, ralph, rossdylan, tdabasin 229 weeks ago

They don't seem to cause dependencies of other things in EPEL.

On Wed, 2 Mar 2022 at 16:35, Stephen John Smoogen <smooge@gmail.com> wrote:


On Wed, 2 Mar 2022 at 15:56, Stephen John Smoogen <smooge@gmail.com> wrote:


#####

I expect that


I clearly dropped the ball in that sentence. Let me finish it up:

I expect that we will need to converse in this thread about what should be done next. In the EPEL meeting Kevin mentioned that I should email the maintainers of each of the 108 packages and see if they want to maintain it or remove it from EPEL-8. Then see if we can remove those from the tree cleanly without affecting packages. Some packages like python-nose should be removed anyway and if there are any other upstream dead ones those can go too.


--
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren


--
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren