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

haskell-src-exts-1.21.0 #4214

Closed
alexeyzab opened this Issue Dec 7, 2018 · 13 comments

Comments

Projects
None yet
7 participants
@alexeyzab
Copy link
Contributor

alexeyzab commented Dec 7, 2018

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

alexeyzab added a commit that referenced this issue Dec 7, 2018

@ndmitchell

This comment has been minimized.

Copy link
Contributor

ndmitchell commented Dec 10, 2018

HLint and Hoogle are both done.

@mvoidex

This comment has been minimized.

Copy link
Contributor

mvoidex commented Dec 12, 2018

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 comment has been minimized.

Copy link
Contributor

DanBurton commented Dec 18, 2018

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

This comment has been minimized.

Copy link
Contributor

judah commented Dec 19, 2018

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

@ndmitchell

This comment has been minimized.

Copy link
Contributor

ndmitchell commented Jan 10, 2019

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

@mvoidex

This comment has been minimized.

Copy link
Contributor

mvoidex commented Jan 10, 2019

Why hsdev is not checked? Version 0.3.2.3 should be fine

@ndmitchell

This comment has been minimized.

Copy link
Contributor

ndmitchell commented Jan 21, 2019

Any progress on kicking the derelict packages out of Stackage?

@DanBurton

This comment has been minimized.

Copy link
Contributor

DanBurton commented Jan 22, 2019

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:

@unclechu

This comment has been minimized.

Copy link
Contributor

unclechu commented Jan 22, 2019

@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

This comment has been minimized.

Copy link
Contributor

ndmitchell commented Jan 22, 2019

@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

This comment has been minimized.

Copy link

galenhuntington commented Jan 25, 2019

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

This comment has been minimized.

Copy link
Contributor

DanBurton commented Jan 25, 2019

@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.

@alexeyzab alexeyzab closed this in ce998a0 Jan 27, 2019

alexeyzab added a commit that referenced this issue Jan 27, 2019

@ndmitchell

This comment has been minimized.

Copy link
Contributor

ndmitchell commented Jan 27, 2019

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment