cabal upload behaves incorrect with -d flag

[OrenGitHub]

The bug details are describe in this stack overflow question.
cabal upload fails with -d flag, but cabal haddock works fine.
without the -d flag, it also works fine.

[ulysses4ever]

It looks like you made some progress? Do you want to close this ticket?

[OrenGitHub]

From what I understood - I think it's still a bug.
I only uploaded the package and not the documentation.
The cabal upload -d ... should also work, right? ( and currently it doesn't )

[ulysses4ever]

cabal upload -d will not work unless you build the documentation correctly first, unfortunately. Could you start from a clean state and try the instructions from the top post here: #8249 (comment) and show us all the output you get again?

Please, don't do any cabal install --lib as you show on SO -- this thing is meant for completely different use cases.

Also, there's no need to specify new as in cabal new-build because the new commands are the default these days.

[OrenGitHub]

Ohhh ... so this is what I was missing !
Here is what I ended up doing:

$ cabal haddock --haddock-for-hackage --haddock-option=--hyperlinked-source
# < ... omitted for brevity ... >
Documentation tarball created:
C:\Users\tuna_\GitHub\dhscanner.ast\dist-newstyle\dhscanner-ast-0.1.0.1-docs.tar.gz
$ cabal upload --publish C:\Users\tuna_\GitHub\dhscanner.ast\dist-newstyle\sdist\dhscanner-ast-0.1.0.0.tar.gz # the package comes *before* the documentation
$ cabal upload --publish -d C:\Users\tuna_\GitHub\dhscanner.ast\dist-newstyle\dhscanner-ast-0.1.0.0-docs.tar.gz

@ulysses4ever - should I answer my own question in SO ? or simply point to this thread ?

[ulysses4ever]

Great!

It would be great if you could add the answer on SO, yes: it'll be much more discoverable that way, I think. Hopefully, future cabal users will benefit from it.

Happy hacking!