Latest upstream release: 1.11.1 Current version/release in rawhide: 1.11-1.fc34 URL: https://github.com/zeux/pugixml 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/3728/
Created attachment 1736608 [details] [patch] Update to 1.11.1 (#1904641)
the-new-hotness/release-monitoring.org's scratch build of pugixml-1.11.1-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=56817723
Latest upstream release: 1.11.2 Current version/release in rawhide: 1.11-1.fc34 URL: https://github.com/zeux/pugixml 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/3728/
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!
Latest upstream release: 1.11.3 Current version/release in rawhide: 1.11-1.fc34 URL: https://github.com/zeux/pugixml 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/3728/
Created attachment 1740361 [details] [patch] Update to 1.11.3 (#1904641)
FEDORA-2020-5dfdfd68ed has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5dfdfd68ed
FEDORA-2020-95d0d22ea4 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-95d0d22ea4
FEDORA-2020-5dfdfd68ed 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-2020-5dfdfd68ed` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-5dfdfd68ed See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-cac4a76358 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-cac4a76358 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-95d0d22ea4 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-2020-95d0d22ea4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-95d0d22ea4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-1a0fccb8ef has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-1a0fccb8ef
FEDORA-2020-23b8d15c0d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-23b8d15c0d
FEDORA-2020-1a0fccb8ef 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-2020-1a0fccb8ef` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1a0fccb8ef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-65a90713ae 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-65a90713ae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-23b8d15c0d 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-2020-23b8d15c0d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-23b8d15c0d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-1a0fccb8ef has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-23b8d15c0d has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-65a90713ae has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.