haskell-src-exts-1.21.0

[alexeyzab]

haskell-src-exts-1.21.0 is out of bounds for:

• haskell-names-0.9.4 (==1.20.*). Alexandr Ruchkin [email protected] @mvoidex. @haskell-suite. Used by: library, test-suite
• haskell-src-meta-0.8.0.3 (>=1.18 && < 1.21). No maintainer. @bmillwood. Used by: library
• hlint-2.1.11 (==1.20.*). Neil Mitchell [email protected] @ndmitchell. @ndmitchell. Used by: library
• hoogle-5.0.17.3 (>=1.18 && < 1.21). Neil Mitchell [email protected] @ndmitchell. @ndmitchell. Used by: library
• hsdev-0.3.2.2 (>=1.19.1 && < 1.21.0). Alexandr Ruchkin [email protected] @mvoidex. @mvoidex. Used by: library
• proto-lens-protoc-0.4.0.1 (>=1.17 && < 1.21). Judah Jacobson [email protected] @judah. @google. Used by: library

[ndmitchell]

HLint and Hoogle are both done.

[mvoidex]

haskell-names-0.9.5 (haskell-src-exts >= 1.21 && < 1.22)
hsdev-0.3.2.3 (haskell-src-exts >= 1.19.1 && < 1.22.0)

[DanBurton]

This will likely be held back for lts 13 due to haskell-src-meta not yet supporting haskell-src-exts-1.21. There may be a good case for making a major version upgrade mid-lts for haskell-src-exts, if a compatible version is later released.

[judah]

I've released proto-lens-protoc-0.4.0.2 with a fix: haskell-src-exts (>=1.18 && <1.22).

[ndmitchell]

1 month later, 22 days with no messages. Do the other maintainers want to request more time, or be temporarily removed from Stackage?

[mvoidex]

Why hsdev is not checked? Version 0.3.2.3 should be fine

[ndmitchell]

Any progress on kicking the derelict packages out of Stackage?

[DanBurton]

haskell-src-meta may soon be removed from the nightly build plan. The following packages would, consequentially, also be removed. (Are there any downstream package maintainers interested in stepping up and taking ownership of haskell-src-meta?)

haskell-src-meta (not present) depended on by:

• QuasiText-0.1.2.6 (-any). Joey Eremondi [email protected] @JoeyEremondi. @mikeplus64. Used by: library
• aeson-qq-0.8.2 (>=0.1.0). Simon Hengel [email protected] @sol. @sol. Used by: library, test-suite
• codo-notation-0.5.2 (>=0.5.1). Dominic Orchard [email protected] @dorchard. @dorchard. Used by: library
• here-1.2.13 (>=0.6 && < 0.9). Emanuel Borsboom [email protected] @borsboom. @tmhedberg. Used by: library
• interpolate-0.2.0 (>=0.8). Simon Hengel [email protected] @sol. @sol. Used by: library, test-suite
• interpolatedstring-perl6-1.0.1 (>=0.3). Emanuel Borsboom [email protected] @borsboom. @audreyt. Used by: library
• invertible-0.2.0.5 (>=0.6 && < 0.9). Dylan Simon [email protected] @dylex. @dylex. Used by: library
• language-c-quote-0.12.2 (>=0.4 && < 0.9). Francesco Mazzoli [email protected] @bitonic. @mainland. Used by: library
• postgresql-typed-0.5.3.0 (-any). Dylan Simon [email protected] @dylex. @dylex. Used by: library
• qm-interpolated-string-0.3.0.0 (>=0.3 && < 0.9). Viacheslav Lotsmanov [email protected] @unclechu. @unclechu. Used by: library

[unclechu]

@DanBurton why is that happening? Did the maintainer of that package throw it away from their shoulders? Is there any replacement for that package?

[ndmitchell]

@unclechu the maintainer of the package hasn't fixed it to work with the latest haskell-src-exts. The release contract with Stackage is that you do that. You can fix haskell-src-meta if you want it to remain in Stackage, or you can find an alternative package, but there's nothing recommended by Stackage as such.

[galenhuntington]

I submitted a (simple) fix here: bmillwood/haskell-src-meta#86. Can this just be used for now? What is Stackage's policy for this?

I submitted that over a month ago with no response or acknowledgement, and I have to wonder if the project is abandoned and it will never be merged.

[DanBurton]

@galenhuntington stackage's policy has been to only use packages as published on hackage, in order to avoid fragmentation of the ecosystem. However, we may consider allowing patches (like yours), to alleviate certain problems (like this one). Such patches would ideally be only a temporary measure, and we would return to the properly released versions asap.

[ndmitchell]

@galenhuntington there is already a well defined process for taking over orphaned packages on Hackage - see https://wiki.haskell.org/Taking_over_a_package. I suggest you follow that. As such I don't see any reason to add a new mechanism in Stackage for patching upstream projects.