Latest upstream release: 68.0.0 Current version/release in rawhide: 67.0.0-1.fc37 URL: https://mkvtoolnix.download/ 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/1991/
FEDORA-2022-dede4e9c40 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-dede4e9c40
FEDORA-2022-dd49bc5522 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-dd49bc5522` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-dd49bc5522 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-dede4e9c40 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-dede4e9c40` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-dede4e9c40 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-dd49bc5522 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-dede4e9c40 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.