Latest upstream release: 0.9.5 Current version/release in rawhide: 0.9.4-1.fc32 URL: https://github.com/INCF/pybids Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/19874/
Created attachment 1634991 [details] [patch] Update to 0.9.5 (#1771068)
Latest upstream release: 0.10.0 Current version/release in rawhide: 0.9.4-1.fc32 URL: https://github.com/INCF/pybids Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/19874/
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!
Updated for rawhide. Updates for F31, F30 will be pushed as soon as python-sphinx 2.2+ is available.
I see that churchyard built 2.2 only for F32. Maybe there are no plans to update sphinx in F31 and this should be closed too?
That's what my concern was. Let me ask churchyard the same, and I will take action on this ticket as per their decision.
No, there are no plans to update sphinx to 2.2 in Fedora 31 or 30. See https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ Can you disable documentation build to workaround the problem?
Thanks a lot for the update, Miro. :D I guess we will have to look into what needs to be done. Maybe we will have to drop the documentation build, and use a pre-built documentation, or drop the docs completely. I'll look into building the docs locally and then use it as a custom source for the package.
FEDORA-2019-38e895da02 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-38e895da02
FEDORA-2019-7049453962 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7049453962
FEDORA-2019-8698b41d0e has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-8698b41d0e
FEDORA-2019-882828fcc7 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-882828fcc7
python-pybids-0.10.0-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-882828fcc7
python-pybids-0.10.0-3.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8698b41d0e
python-pybids-0.10.0-3.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
python-pybids-0.10.0-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.