Skip to content
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

srtree 2.0.0.4 #7654

Open
2 tasks
alexeyzab opened this issue Jan 12, 2025 · 5 comments
Open
2 tasks

srtree 2.0.0.4 #7654

alexeyzab opened this issue Jan 12, 2025 · 5 comments

Comments

@alexeyzab
Copy link
Contributor

repline (Library and exe bounds failures, Stephen Diehl [email protected] @sdiehl) (not present) depended on by:

table-layout (not present) depended on by:

@folivetti
Copy link
Contributor

it suffices to put those on stack.yaml extra-deps?
I already had table-layout in there, it's odd that it gives some error.
Any advice?

@juhp
Copy link
Contributor

juhp commented Jan 27, 2025

There are some problems:

data-default-class-0.2.0.0 (changelog) (Grandfathered dependencies) is out of bounds for:

  • table-layout-1.0.0.1 (>=0.1.2 && < 0.2). Grandfathered dependencies. Used by: library

doclayout-0.5 (changelog) (John MacFarlane [email protected] @jgm) is out of bounds for:

  • table-layout-1.0.0.1 (>=0.3 && < 0.5). Grandfathered dependencies. Used by: library

repline (Library and exe bounds failures, Stephen Diehl [email protected] @sdiehl) (not present) depended on by:

@folivetti
Copy link
Contributor

Sorry, I'm a little lost here and don't know exactly what I can do to solve these issues (assuming there's something I can). Could you point me out to some guidelines or instructions on how to solve that myself? :-)

@juhp
Copy link
Contributor

juhp commented Jan 28, 2025

We are just informing you that newer srtree cannot build in current Stackage Nightly.
I think because you added new deps that don't currently build in Nightly because of bounds issues.

So either you could try to help those projects move forward or just wait for them, or eventually for yours to get dropped from future Stackage at some point. I suppose it would be okay to continue shipping the old version, but presumably you would want the newer one(s) there.

@folivetti
Copy link
Contributor

understood!! I'll try to help updating those projects! Thanks for letting me know!

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

No branches or pull requests

3 participants