Latest upstream release: 0.6.1 Current version/release in rawhide: 0.6.0-1.fc35 URL: https://github.com/Cloudef/bemenu 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/21789/
FEDORA-2021-14ced73e6a has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-14ced73e6a
FEDORA-2021-14ced73e6a has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-14ced73e6a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-14ced73e6a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-2441cac9c8 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-2021-2441cac9c8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2441cac9c8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-14ced73e6a has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-2441cac9c8 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.