Latest upstream release: 1.0.7 Current version/release in rawhide: 1.0.6-2.fc32 URL: https://github.com/r-lib/pkgbuild 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/18590/
Created attachment 1681708 [details] [patch] Update to 1.0.7 (#1827928)
the-new-hotness/release-monitoring.org's scratch build of R-pkgbuild-1.0.7-1.fc30.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=43775461
Latest upstream release: 1.0.8 Current version/release in rawhide: 1.0.6-2.fc32 URL: https://github.com/r-lib/pkgbuild 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/18590/
Created attachment 1686134 [details] [patch] Update to 1.0.8 (#1827928)
the-new-hotness/release-monitoring.org's scratch build of R-pkgbuild-1.0.8-1.fc30.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=44190863
FEDORA-2020-a317f71cc2 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a317f71cc2
FEDORA-2020-2d6604338f has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d6604338f
FEDORA-2020-e66cef79c6 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e66cef79c6
FEDORA-2020-2d6604338f has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2d6604338f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d6604338f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-a317f71cc2 has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a317f71cc2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a317f71cc2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-e66cef79c6 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e66cef79c6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e66cef79c6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-e66cef79c6 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-2d6604338f has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.