Latest upstream release: 0.0.2 Current version/release in rawhide: 0.0.1-2.fc34 URL: https://github.com/eddelbuettel/rcppdate 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/123698/
FEDORA-2021-e472032270 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e472032270
FEDORA-2021-e472032270 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e472032270` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e472032270 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-5323a64d74 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-5323a64d74` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5323a64d74 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-e472032270 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-5323a64d74 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.