https://bugzilla.redhat.com/show_bug.cgi?id=2431166
Miro Hrončok <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |fedora-review+ --- Comment #2 from Miro Hrončok <[email protected]> --- Technically, we could choose not to provide/obsolete and instead keep the old one packaged as upstream does, with a versioned requirement on the new one (see the metadata of https://pypi.org/project/roman-numerals-py/4.1.0/ -- but that would be a pain to keep forever. In Fedora, it's only sphinx that requires this, so if this is firstly built together with the sphinx update, it should be fine. Note that if you ship this right before the Sphinx update, to allow CI testing the Sphinx update itself, it should be fine, as this does not provide python3dist(roman-numerals-py), python3.14dist(roman-numerals-py). Or you can do it properly via a side tag, but then you cannot really CI test Sphinx. Up to you. Package APPROVED. Consider keeping the git history of python-roman-numerals-py when you request the repo (fedpkg request-repo --no-initial-commit). -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2431166 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202431166%23c2 -- _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
