Nightly ghc-9.2 disabled package report (mentioned maintainers are affected) #6486
Comments
|
ALUT-2.4.0.3: UNMAINTAINED |
|
benchpress-0.2.2.18: Will Sewell me@willsewell.com @WillSewell |
|
containers-unicode-symbols-0.3.1.3: Alexander Altman alexanderaltman@me.com @pthariensflame |
|
freckle-app-1.0.0.4: Freckle Engineering freckle-engineering@renaissance.com @pbrisbin @mjgpy3 @StevenXL |
|
gitlab-haskell-0.3.2.0: Rob Stewart robstewart57@gmail.com @robstewart57 |
|
hprotoc-2.4.17: Kostiantyn Rybnikov k-bx@k-bx.com @k-bx |
|
koji-0.0.2: Jens Petersen juhpetersen@gmail.com @juhp |
|
morpheus-graphql-tests-0.18.0: Davit Nalchevanidze d.nalchevanidze@gmail.com @nalchevanidze |
|
polysemy-vinyl-0.1.5.0: Dan Firth dan.firth@homotopic.tech @locallycompact |
|
sandwich-0.1.0.9: Tom McLaughlin tom@codedown.io @thomasjm |
|
servant-tracing-0.1.0.2: Chris Coffey chris@foldl.io @ChrisCoffey |
|
synthesizer-dimensional-0.8.1: Henning Thielemann stackage@henning-thielemann.de @thielema |
|
webgear-server-0.2.1: Raghu Kaippully rkaippully@gmail.com @rkaippully |
juhp
changed the title
|
Closed in favor of #7078 |
Trying something new here, we've historically had trouble notifying maintainers when we disable packages en masse. We've added some automation for this.
What follows is every package that has gotten disabled since the 2021-12-30 snapshot. Hopefully we can do this often to limit the number of packages in each post.
Notably we just finished the first GHC 9.2.2 snapshot, but we've had some other fairly impactful upgrades of libraries during the year.
If you would like to know why your package was disabled you can search for the package name in build-constraints.yaml (there can be multiple occurences). It should have a comment stating "compile fail", show what dependencies it needs to be updated for, or if one of its dependencies got removed.
< 0means the package is disabled.We've also added further automation to detect when packages get fixed so that we can re-enable them automatically. If the disabled package has a version number in its comment then it will get re-enabled eventually, but you can always file a PR (removing any
< 0bound) if you want to get the package back in sooner.This will ping a lot of people so I will lock the issue, please file a separate issue if you would like any clarification.
The text was updated successfully, but these errors were encountered: