Dropping the pyp2rpm support from Copr

[Jakub Kadlcik]

Hello,

TL;DR: You can still build directly from PyPI using pyp2spec, we are only
dropping the pyp2rpm support.

It always sucks when existing features get removed, but this one hopefully
shouldn't hurt that much. For a long time, Copr supports submitting new
builds directly from PyPI.

https://docs.copr.fedorainfracloud.org/user_documentation.html#pypi

For these builds, Copr generates a specfile on the fly using pyp2rpm or
pyp2spec, users' choice. The pyp2rpm is the older of the two and has been
on life support for some time, while pyp2spec is the successor and has been
the default option in Copr since 2023.

Recently the Fedora package for pyp2rpm got retired, which forced our hand
and made us drop the pyp2rpm support from Copr. The change will go live
with the next Copr release, so please make sure you are not relying on this
feature.

You are probably fine, though. This is the number of builds that used
pyp2rpm in all of 2026:

coprdb=# select count(*) from build where source_type=5 and
source_json::jsonb ->> 'spec_generator' = 'pyp2rpm' and submitted_on >
1767222000;
    ┌───────┐
    │ count │
    ├───────┤
    │     9 │
    └───────┘

In comparison pyp2spec:

coprdb=# select count(*) from build where source_type=5 and
source_json::jsonb ->> 'spec_generator' = 'pyp2spec' and submitted_on >
1767222000;
    ┌────────┐
    │ count  │
    ├────────┤
    │ 114329 │
    └────────┘

I will ping the remaining pyp2rpm users off-list to make sure they know.

Jakub