Fedora Account System
Red Hat Associate
Red Hat Customer
Releases retrieved: 16.0.0 Upstream release that is considered latest: 16.0.0 Current version/release in rawhide: 15.1.5-2.fc41 URL: https://wiki.gnome.org/Apps/Gucharmap 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://docs.fedoraproject.org/en-US/package-maintainers/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/1276/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gucharmap
Created attachment 2046172 [details] Update to 16.0.0 (#2311318)
the-new-hotness/release-monitoring.org's scratch build of gucharmap-16.0.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=123220152
The update will be coordinated with the unicode-ucd maintainer.
Releases retrieved: 16.0.1 Upstream release that is considered latest: 16.0.1 Current version/release in rawhide: 15.1.5-2.fc41 URL: https://wiki.gnome.org/Apps/Gucharmap 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://docs.fedoraproject.org/en-US/package-maintainers/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/1276/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gucharmap
Created attachment 2046895 [details] Update to 16.0.1 (#2311318)
the-new-hotness/release-monitoring.org's scratch build of gucharmap-16.0.1-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=123407589
FEDORA-2024-6a22685cb9 (gucharmap-16.0.1-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-6a22685cb9
FEDORA-2024-3a37b81166 (gucharmap-16.0.1-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3a37b81166
FEDORA-2024-6a22685cb9 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6a22685cb9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6a22685cb9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-3a37b81166 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3a37b81166` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3a37b81166 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-6a22685cb9 (gucharmap-16.0.1-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-3a37b81166 (gucharmap-16.0.1-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.