Because ghc-filestore relies on (now deprecated) `git whatchanged` command, git history related functionality no longer works with git >=. v2.51.0 The problem was reported upstream as: https://github.com/jgm/filestore/issues/38 And is now fixed in ghc-filestore 0.6.5.1 released today: https://github.com/jgm/filestore/commit/ac50424a889a580535c3fd0aae63a377adb56762 Reproducible: Always
Thanks I asked about a proper release upload.
FEDORA-2025-3b22a6fb4a (ghc-filestore-0.6.5.1-1.fc42 and gitit-0.15.1.2-9.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-3b22a6fb4a
FEDORA-2025-f85b824b7c (ghc-filestore-0.6.5.1-1.fc41 and gitit-0.15.1.2-9.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-f85b824b7c
FEDORA-2025-3b22a6fb4a has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-3b22a6fb4a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-3b22a6fb4a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-f85b824b7c 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-2025-f85b824b7c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f85b824b7c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-f85b824b7c (ghc-filestore-0.6.5.1-1.fc41 and gitit-0.15.1.2-9.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-3b22a6fb4a (ghc-filestore-0.6.5.1-1.fc42 and gitit-0.15.1.2-9.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.