-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
amazonka-s3-0.0.0 can get picked #915
Milestone
Comments
We should probably do this for any
@brendanhay If you're happy for me to do so, I can use Hackage Trustee powers to go through and add |
@endgame, Yeah - makes sense, go ahead! |
Closed
As Hackage Trustee (
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating the subdir list for source-repository-package, I noticed that if you leave out amazonka-s3, it might pick one from hackage. The solver could pick amazonka-s3-0.0.0 since it has really lax bounds. This will cause a confusing error message, since the user might not know they forgot this subdir.
Could we tighten the bounds of amazonka-s3-0.0.0 on hackage to prevent it from getting chosen so easily?
The text was updated successfully, but these errors were encountered: