Releases retrieved: 8.2.2 Upstream release that is considered latest: 8.2.2 Current version/release in rawhide: 8.2.1-4.fc37 URL: https://github.com/khaledhosny/ots Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/201891/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/opentype-sanitizer
https://src.fedoraproject.org/rpms/opentype-sanitizer/pull-request/2 Blocked on https://github.com/googlefonts/ots-python/pull/19.
FEDORA-2022-e526092f88 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e526092f88
FEDORA-2022-f68793a79c has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f68793a79c
FEDORA-2022-f68793a79c has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-081348800b has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-081348800b
FEDORA-2022-081348800b has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-081348800b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-081348800b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e526092f88 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e526092f88` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e526092f88 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-82e74b510f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-82e74b510f
FEDORA-EPEL-2022-b8b5734319 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b8b5734319
FEDORA-2022-82e74b510f has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-82e74b510f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-82e74b510f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-b8b5734319 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-b8b5734319 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-081348800b has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-e526092f88 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-82e74b510f has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-b8b5734319 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.