Broken in nixpkgs

[int-index]

$ nix-shell -p haskellPackages.jenkinsPlugins2nix
error: Package ‘jenkinsPlugins2nix-0.5.0.0’ in /nix/store/al476r5q8bifinbrysh37yzm7mbryxvd-nixpkgs/nixpkgs/pkgs/development/haskell-modules/hackage-packages.nix:165065 is marked as broken, refusing to evaluate.

       a) To temporarily allow broken packages, you can use an environment variable
          for a single invocation of the nix tools.

            $ export NIXPKGS_ALLOW_BROKEN=1

        Note: For `nix shell`, `nix build`, `nix develop` or any other Nix 2.4+
        (Flake) command, `--impure` must be passed in order to read this
        environment variable.

       b) For `nixos-rebuild` you can set
         { nixpkgs.config.allowBroken = true; }
       in configuration.nix to override this.

       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
         { allowBroken = true; }
       to ~/.config/nixpkgs/config.nix.
(use '--show-trace' to show detailed location information)

This is due to the upper bounds on attoparsec and tasty. Trying to build with NIXPKGS_ALLOW_BROKEN=1 results in

Configuring jenkinsPlugins2nix-0.5.0.0...

Setup: Encountered missing or private dependencies:
attoparsec >=0.13 && <0.14, tasty-hspec >=1.1 && <1.2

However, just bumping the upper bound is not enough, as it results in another error in the test suite:

test/Nix/JenkinsPlugins2Nix/Tests/Parser.hs:16:9: error:
    Not in scope: type constructor or class ‘Hspec.Spec’
    Module ‘Test.Tasty.Hspec’ does not export ‘Spec’.
   |
16 | spec :: Hspec.Spec
   |         ^^^^^^^^^^

test/Nix/JenkinsPlugins2Nix/Tests/Parser.hs:17:8: error:
    Not in scope: ‘Hspec.describe’
    Module ‘Test.Tasty.Hspec’ does not export ‘describe’.
   |
17 | spec = Hspec.describe "parser spec" $ do
   |        ^^^^^^^^^^^^^^

test/Nix/JenkinsPlugins2Nix/Tests/Parser.hs:18:3: error:
    Not in scope: ‘Hspec.it’
    Module ‘Test.Tasty.Hspec’ does not export ‘it’.
   |
18 |   Hspec.it "parser github-pullrequest manifest" githubPr
   |   ^^^^^^^^

test/Nix/JenkinsPlugins2Nix/Tests/Parser.hs:20:13: error:
    Not in scope: type constructor or class ‘Hspec.Expectation’
    Module ‘Test.Tasty.Hspec’ does not export ‘Expectation’.
   |
20 | githubPr :: Hspec.Expectation
   |             ^^^^^^^^^^^^^^^^^

test/Nix/JenkinsPlugins2Nix/Tests/Parser.hs:21:27: error:
    Not in scope: ‘Hspec.shouldBe’
    Module ‘Test.Tasty.Hspec’ does not export ‘shouldBe’.
   |
21 | githubPr = Right expected `Hspec.shouldBe` runParseManifest githubPrManifestText
   |                           ^^^^^^^^^^^^^^^^

[con-f-use]

seems like this project is unmaintained :*(

[Fuuzetsu]

Yeah, basically. I completely forgot that there was a problem and even an MR, I can try to merge that in and publish a new version...

[Fuuzetsu]

By the way, as this is a binary application, you can just pin an old version of nixpkgs for it to keep it working in whatever project you want. You don't have to make sure it always works with latest nixpkgs.

[con-f-use]

Yeah sure, but on some level that is similar to saying "you can use my application on Windows 3.1, no problem".

And please don't get me wrong ,it's totally fine to move on from a project and not wanting to do free maintenance work for random people you owe absolutely nothing to. Just wanted to gently poke, in case it's just an awareness thing.

[Fuuzetsu]

Yeah sure, but on some level that is similar to saying "you can use my application on Windows 3.1, no problem".

Well, hardly. It's usually 1-2 lines change to use different nixpkgs version for something and it's very common to do so.

And please don't get me wrong ,it's totally fine to move on from a project and not wanting to do free maintenance work for random people you owe absolutely nothing to. Just wanted to gently poke, in case it's just an awareness thing.

Sure. It's minor part awareness, major part just being an abandoned project.