Releases retrieved: 0.13.10.0 Upstream release that is considered latest: 0.13.10.0 Current version/release in rawhide: 0.13.8.3-3.fc38 URL: http://hackage.haskell.org/package/gtk2hs-buildtools 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/1273/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gtk2hs-buildtools
Created attachment 1964251 [details] Update to 0.13.10.0 (#2203405)
the-new-hotness/release-monitoring.org's scratch build of gtk2hs-buildtools-0.13.10.0-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=101051694
Releases retrieved: 0.13.11.0 Upstream release that is considered latest: 0.13.11.0 Current version/release in rawhide: 0.13.10.0-3.fc40 URL: http://hackage.haskell.org/package/gtk2hs-buildtools 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/1273/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gtk2hs-buildtools
Created attachment 2039635 [details] Update to 0.13.11.0 (#2203405)
the-new-hotness/release-monitoring.org's scratch build of gtk2hs-buildtools-0.13.11.0-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=120517012
Releases retrieved: 0.13.12.0 Upstream release that is considered latest: 0.13.12.0 Current version/release in rawhide: 0.13.11.0-2.fc42 URL: http://hackage.haskell.org/package/gtk2hs-buildtools 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/1273/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gtk2hs-buildtools
Created attachment 2081022 [details] Update to 0.13.12.0 (#2203405)
the-new-hotness/release-monitoring.org's scratch build of gtk2hs-buildtools-0.13.12.0-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=130517541
FEDORA-2025-8c24ced850 (GHC 9.8 and Stackage 23 for F43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8c24ced850
FEDORA-2025-8c24ced850 (GHC 9.8 and Stackage 23 for F43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.