mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

add bug and update comment

Browse source
This commit is contained in:
Joey Hess 2022-08-29 14:49:44 -04:00
parent 248cf6b151
commit faefab5e65
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 20 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/Webapp_won__180__t_start_on_MacOS/comment_4_1e944c517796ca29f8870fcf76c9a0d4._comment
View file

@ -4,14 +4,17 @@
date="2022-08-29T17:56:55Z"
content="""
git-annex can be built without support for `git-annex webapp`,
and it seems that your updated build was configured that way.
and it seems that your updated build ended up with that turned off.
This might be a mistake in the homebrew git-annex build,
or they might have disabled building with the webapp for some reason.
It would be good to contact the homebrew developers and file a bug report
about this. From what I can see, their formula for git-annex does not
explicitly disable the webapp, but some problem may have caused it to get
disabled.
But, I suspect what caused this is a problem with a new version of cabal.
I suspect what caused this is a problem with a new version of cabal.
When I build git-annex (on linux) with cabal 3.4.1.0 and ghc 9.0.2,
it builds without the webapp. This is even though the webapp is supposed
to be build by default. Even `cabal configure -fWebapp`
does not cause it to build the webapp.
does not cause it to build the webapp. Made a bug for that at
[[cabal_builds_without_assistant]].
"""]]

12
doc/bugs/cabal_builds_without_assistant.mdwn Normal file
View file

@ -0,0 +1,12 @@
With cabal 3.4.1.0, `cabal build` does not build the assistant, even though
all dependencies are there. Even after `cabal configure -fAssistant`, it
silently skips installing the deps for the assistant and does not enable the
CPP for the flag. Same for webapp.
Earlier versions of cabal did not behave this way. Perhaps it is a cabal
bug?
I tried moving the build-depends out of the `if flag(Assistant)` section
to the main build-depends section. It was able to install all the build
depends, so it's not some dependency issue making it decide to turn off
that build flag. --[[Joey]]