Skip to content

Generated kupo.cabal in latest release not valid. #199

@notunrandom

Description

@notunrandom

What Git revision / release tag are you using?

v2.11.0

Describe what the problem is?

When building from the source code .tar.gz, cabal install exe:kupo fails with the error:

Error: [Cabal-6661]
filepath wildcard './docs/api/v2.9.0.yaml' does not match any files.

The reason for this is that the kupo.cabal that has been committed to git is not the correct one, as it contains these lines:

kupo/kupo.cabal

Lines 32 to 35 in de9c527

data-files:
docs/api/nightly.yaml
docs/api/v2.10.0.yaml
docs/api/v2.9.0.yaml

The correct one (as generated by hpack) contains docs/api/v2.11.0.yaml and does not contain /docs/api/v2.9.0.yaml

What should be the expected behavior?

cabal install exe:kupo should succeed.

Suggestions

Either the kupo.cabal should not be in git (since it can be generated), or there should be a CI step to ensure that it works (including for install, not just build).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions