kubernetes-client/haskell

Update to newer versions of GHC

Opened this issue · 2 comments

sigrdrifa commented

Hey, this is a great package but I'm struggling to run it on newer versions of GHC (tried with 9.4.8 or higher) and it cannot resolve the dependencies because of constraints on the http-api-data package:

[__1] trying: kubernetes-client-0.3.2.0 (dependency of hask-k8s)
[__2] trying: kubernetes-client-core-0.3.1.0 (dependency of kubernetes-client)
[__3] next goal: http-api-data (dependency of kubernetes-client-core)
[__3] rejecting: http-api-data-0.6 (conflict: kubernetes-client-core =>
http-api-data>=0.3.4 && <0.5)
[__3] skipping: http-api-data-0.5.1, http-api-data-0.5 (has the same
characteristics that caused the previous version to fail: excluded by
constraint '>=0.3.4 && <0.5' from 'kubernetes-client-core')
[__3] trying: http-api-data-0.4.3
[__4] next goal: base (dependency of hask-k8s)
[__4] rejecting: base-4.17.2.1/installed-4.17.2.1 (conflict: http-api-data =>
base>=4.7 && <4.17)

Has anyone had any luck using this package on GHC 9.4 or higher?

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten