Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show why configuring dependencies failed #10273

Merged
merged 7 commits into from
Oct 1, 2024

Commits on Oct 1, 2024

  1. Show installed versions when configuring fails

    When `act-as-setup configure` fails, it doesn't indicate which
    dependencies are missing entirely and which ones don't satisfy the
    version constraints. The errors from `cabal build` are more informative,
    but aren't available in all contexts (nixpkgs Haskell builds, for
    example, use the `act-as-setup` interface). This makes it immediately
    clear what sort of dependency error has occurred.
    
    Before (cabal-install 3.12.1.0):
    
        Configuring test-pkg-0.1.0.0...
        Error: [Cabal-8010]
        Encountered missing or private dependencies:
            base <=4.18,
            foobar,
            test-pkg:{bar-internal, foo-internal}
    
    After:
    
        Configuring test-pkg-0.1.0.0...
        Error: [Cabal-8010]
        Encountered missing or private dependencies:
            base <=4.18 (installed: 4.19.1.0),
            foobar (missing),
            test-pkg:{bar-internal,foo-internal} (missing: :bar-internal)
    9999years authored and Mikolaj committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    27885d1 View commit details
    Browse the repository at this point in the history
  2. Add tests

    9999years authored and Mikolaj committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    d3d782e View commit details
    Browse the repository at this point in the history
  3. Reorder import

    9999years authored and Mikolaj committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    b7f2bb4 View commit details
    Browse the repository at this point in the history
  4. Add changelog entry

    9999years authored and Mikolaj committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    483ec37 View commit details
    Browse the repository at this point in the history
  5. Escape braces in changelog entry

    From @geekosaur on Matrix:
    
    > since changelog-d uses the cabal file parser to parse changelog files,
    > internal braces have to be escaped
    9999years authored and Mikolaj committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    e7d1560 View commit details
    Browse the repository at this point in the history
  6. Use Markdown changelog entry

    9999years authored and Mikolaj committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    940e02c View commit details
    Browse the repository at this point in the history
  7. packages needs to be an array

    9999years authored and Mikolaj committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    ec60185 View commit details
    Browse the repository at this point in the history