Bug 2390540 - history functionality broken when git is used as a storage backend
Summary: history functionality broken when git is used as a storage backend
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gitit
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2390539
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-08-23 19:47 UTC by Martin B.
Modified: 2025-10-06 11:32 UTC (History)
1 user (show)

Fixed In Version: gitit-0.15.1.2-9
Clone Of:
Environment:
Last Closed: 2025-10-06 11:32:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin B. 2025-08-23 19:47:28 UTC
When I try to get history of a page, I get an error complaining that git whatchanged' is nominated for removal.


Reproducible
============

Always

Steps to Reproduce
==================

1. Open gitit in a browser
2. Navitage to "history" tab of any page (or use "recent activity" feature)

Actual Results
==============

I get an error page:

```
Happstack 7.8.0.2

Something went wrong here
Internal server error
Everything has stopped

The error was "UnknownError: git whatchanged returned error status. 'git whatchanged' is nominated for removal. If you still use this command, please add an extra option, '--i-still-use-this', on the command line and let us know you still use it by sending an e-mail to <git.org>. Thanks. fatal: refusing to run without --i-still-use-this "
```

Expected Results
================

History page is shown.

Additional Information
======================

This is a bug in ghc-filestore already fixed upstream,
and tracked downstream in fedora as bz 2390539.

I assume we just need to rebuild gitit when the bz 2390539 is fixed.

Comment 1 Jens Petersen 2025-08-26 06:40:01 UTC
Thanks for the report

Comment 2 Jens Petersen 2025-10-06 11:32:01 UTC
I guess I missed this additional report when fixing/pushing

Please comment if you still see a problem.


Note You need to log in before you can comment on or make changes to this bug.