Latest upstream release: 1.2.0 Current version/release in rawhide: 1.1.0-4.fc33 URL: https://github.com/cdown/psi-notify 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/98361/
Created attachment 1694981 [details] [patch] Update to 1.2.0 (#1843785)
the-new-hotness/release-monitoring.org's scratch build of psi-notify-1.2.0-1.fc30.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=45400412
Latest upstream release: 1.2.1 Current version/release in rawhide: 1.1.0-4.fc33 URL: https://github.com/cdown/psi-notify 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/98361/
Created attachment 1695945 [details] [patch] Update to 1.2.1 (#1843785)
the-new-hotness/release-monitoring.org's scratch build of psi-notify-1.2.1-1.fc30.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=45530703
FEDORA-EPEL-2020-d2da0eb238 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d2da0eb238
FEDORA-2020-ba1463ee7c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ba1463ee7c
FEDORA-2020-d057d22b84 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d057d22b84
FEDORA-EPEL-2020-d2da0eb238 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d2da0eb238 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-d057d22b84 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-d057d22b84` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d057d22b84 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-ba1463ee7c 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-ba1463ee7c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ba1463ee7c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-d057d22b84 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-ba1463ee7c has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-d2da0eb238 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.