Releases retrieved: 1.38 Upstream release that is considered latest: 1.38 Current version/release in rawhide: 1.37-1.fc37 URL: https://tio.github.io/ 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/20587/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/tio
FEDORA-2022-21b91c8fc6 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-21b91c8fc6
FEDORA-EPEL-2022-419a953a1a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-419a953a1a
FEDORA-2022-b5d3eb9f8b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b5d3eb9f8b
FEDORA-EPEL-2022-a9dcbb8f45 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a9dcbb8f45
FEDORA-2022-5abec4d30b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5abec4d30b
FEDORA-2022-21b91c8fc6 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-21b91c8fc6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-21b91c8fc6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-5abec4d30b 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 --advisory=FEDORA-2022-5abec4d30b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5abec4d30b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-a9dcbb8f45 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-a9dcbb8f45 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-419a953a1a has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-419a953a1a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b5d3eb9f8b 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 --advisory=FEDORA-2022-b5d3eb9f8b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b5d3eb9f8b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-5abec4d30b has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-a9dcbb8f45 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-b5d3eb9f8b 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-419a953a1a has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.