Bug 2390540

Summary:	history functionality broken when git is used as a storage backend
Product:	[Fedora] Fedora	Reporter:	Martin B. <martin.bukatovic>
Component:	gitit	Assignee:	Jens Petersen <petersen>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	42	CC:	petersen
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gitit-0.15.1.2-9	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-10-06 11:32:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2390539
Bug Blocks:

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.