Learn more about these different git repos.
Other Git URLs
There is a severe bug in python-readme-renderer-26.0-2.fc33 and python-readme-renderer-26.0-1.fc33
https://bugzilla.redhat.com/show_bug.cgi?id=1836900
Please, untag them , make sure that python-readme-renderer-24.0-6.fc32 is tagged in f33.
When do you need this? ASAP
When is this no longer needed or useful? When the bugzilla is fixed.
If we cannot complete your request, what is the impact? twine and pipenv FTBFS
Fixed.
$ koji list-tagged f33 python-readme-renderer --latest Build Tag Built by ---------------------------------------- -------------------- ---------------- python-readme-renderer-24.0-6.fc32 f33 releng
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks. Running koji wait-repo f33-build --build python-readme-renderer-24.0-6.fc32 to verify the result.
koji wait-repo f33-build --build python-readme-renderer-24.0-6.fc32
Successfully waited 15:15 for python-readme-renderer-24.0-6.fc32 to appear in the f33-build repo
@churchyard, you are the maintainer of python-pygments. Thus the proper fix you have been to provide the latest release of python-pygments instead of reverting the update.
Also, if something is not installable then that hardly a severe bug.
For the record, I am working n updating pygments to fix this permanently, but there is a stack of 1130 source packages (+ 264 "binary" packages) this could potentially break, hence I need to proceed with caution (instead of just doing it right away). In the meantime, untagging python-readme-renderer-26.0 is the proper temporary workaround.
Followup https://pagure.io/releng/issue/9466
Login to comment on this ticket.