Latest upstream release: 2.7.0 Current version/release in rawhide: 2.6.1-4.fc33 URL: https://github.com/jekyll/jekyll-seo-tag 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/17332/
Created attachment 1722449 [details] [patch] Update to 2.7.0 (#1889137)
the-new-hotness/release-monitoring.org's scratch build of rubygem-jekyll-seo-tag-2.7.0-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=53686692
Latest upstream release: 2.7.1 Current version/release in rawhide: 2.6.1-4.fc33 URL: https://github.com/jekyll/jekyll-seo-tag 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/17332/
Created attachment 1722450 [details] [patch] Update to 2.7.1 (#1889137)
FEDORA-2020-47f3c9e568 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-47f3c9e568
FEDORA-2020-4f6222807b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4f6222807b
FEDORA-2020-d4f6925e00 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d4f6925e00
FEDORA-2020-d4f6925e00 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-d4f6925e00` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d4f6925e00 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-47f3c9e568 has been pushed to the Fedora 33 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-47f3c9e568` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-47f3c9e568 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-4f6222807b 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-4f6222807b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4f6222807b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-47f3c9e568 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-d4f6925e00 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4f6222807b has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.