Hide Forgot
Latest upstream release: 4.7.0 Current version/release in rawhide: 4.6.0-3.fc33 URL: https://github.com/zeromq/cppzmq 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/18648/
Created attachment 1717958 [details] [patch] Update to 4.7.0 (#1884030)
the-new-hotness/release-monitoring.org's scratch build of cppzmq-4.7.0-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=52540977
Latest upstream release: 4.7.1 Current version/release in rawhide: 4.6.0-3.fc33 URL: https://github.com/zeromq/cppzmq 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/18648/
Created attachment 1719203 [details] [patch] Update to 4.7.1 (#1884030)
the-new-hotness/release-monitoring.org's scratch build of cppzmq-4.7.1-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=52843346
FEDORA-2020-72e70dc98c has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-72e70dc98c
FEDORA-2020-0d5f584416 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0d5f584416
FEDORA-2020-0d5f584416 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-0d5f584416` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0d5f584416 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-cf2739b1b0 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-cf2739b1b0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cf2739b1b0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-72e70dc98c 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-72e70dc98c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-72e70dc98c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-cf2739b1b0 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-72e70dc98c has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-0d5f584416 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.