Bug 1797176 - git-annex-7.20191114 Production FTBFS on armv7hl: Assistant/WebApp/Types.hs:49:37: error: Identifier ‘String’ used as a type
Summary: git-annex-7.20191114 Production FTBFS on armv7hl: Assistant/WebApp/Types.hs:4...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: git-annex
Version: 31
Hardware: armv7hl
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-01 09:02 UTC by Jens Petersen
Modified: 2020-11-24 20:18 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-24 20:18:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jens Petersen 2020-02-01 09:02:56 UTC
Description of problem:

[566 of 629] Compiling Assistant.WebApp.Types ( Assistant/WebApp/Types.hs, dist/build/git-annex/git-annex-tmp/Assistant/WebApp/Types.o )
Assistant/WebApp/Types.hs:49:37: error:
    • Identifier ‘String’ used as a type
    • In the first argument of ‘IO’, namely ‘String’
      In the first argument of ‘Maybe’, namely ‘(IO String)’
      In the type ‘Maybe (IO String)’
   |
49 |         , postFirstRun :: Maybe (IO String)
   |                                     ^^^^^^

Version-Release number of selected component (if applicable):
git-annex-7.20191114

How reproducible:
100%

Steps to Reproduce:
1. Build recent git-annex on armv7hl with ghc-8.6.5 (F31+)

Actual results:
https://koji.fedoraproject.org/koji/taskinfo?taskID=41158351

see above for error.

Expected results:
No build error.

Additional info:
It builds okay with `-O1`: git-annex defaults to `-O2`
except on arm where it uses: `-O2 -optlo-O2`.

Comment 1 Jens Petersen 2020-02-02 00:30:45 UTC
For now I just disabled Production for armv7hl (in rawhide).

Comment 2 Jens Petersen 2020-02-02 05:48:50 UTC
I tried with git-annex-7.20191230 (which has a new dep on filepath-bytestring)
and it built okay on armv7hl with ghc-8.6.5 - so perhaps this is fixed?

It would be interesting to know if ghc:8.8 is any better here.

Comment 3 Jens Petersen 2020-02-02 13:22:10 UTC
scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=41325610

Comment 4 Ben Cotton 2020-11-03 16:17:00 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-11-24 20:18:17 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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