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

amazonka-s3-0.0.0 can get picked #915

Closed
ysangkok opened this issue Jun 24, 2023 · 3 comments
Closed

amazonka-s3-0.0.0 can get picked #915

ysangkok opened this issue Jun 24, 2023 · 3 comments
Milestone

Comments

@ysangkok
Copy link
Contributor

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?

@endgame endgame added this to the 2.0 milestone Jun 24, 2023
@endgame
Copy link
Collaborator

endgame commented Jun 24, 2023

We should probably do this for any amazonka-*-0.0.0:

amazonka-autoscaling
amazonka-cloudformation
amazonka-cloudfront
amazonka-cloudsearch
amazonka-cloudsearch-domains
amazonka-cloudtrail
amazonka-cloudwatch
amazonka-cloudwatch-logs
amazonka-codedeploy
amazonka-cognito-identity
amazonka-cognito-sync
amazonka-config
amazonka-datapipeline
amazonka-directconnect
amazonka-dynamodb
amazonka-ec2
amazonka-elasticache
amazonka-elasticbeanstalk
amazonka-elastictranscoder
amazonka-elb
amazonka-emr
amazonka-iam
amazonka-importexport
amazonka-kinesis
amazonka-kms
amazonka-lambda
amazonka-opsworks
amazonka-rds
amazonka-redshift
amazonka-route53
amazonka-route53-domains
amazonka-s3
amazonka-sdb
amazonka-ses
amazonka-sns
amazonka-sqs
amazonka-storagegateway
amazonka-sts
amazonka-support
amazonka-swf

@brendanhay If you're happy for me to do so, I can use Hackage Trustee powers to go through and add amazonka-core <0.0.1 bounds over all these packages.

@brendanhay
Copy link
Owner

@endgame, Yeah - makes sense, go ahead!

@endgame endgame mentioned this issue Jun 30, 2023
@endgame
Copy link
Collaborator

endgame commented Jul 4, 2023

As Hackage Trustee (jack), I have added amazonka-core <0.0.1 to the following packages:

amazonka-autoscaling
amazonka-cloudformation
amazonka-cloudfront
amazonka-cloudsearch
amazonka-cloudsearch-domains
amazonka-cloudtrail
amazonka-cloudwatch
amazonka-cloudwatch-logs
amazonka-codedeploy
amazonka-cognito-identity
amazonka-cognito-sync
amazonka-config
amazonka-datapipeline
amazonka-directconnect
amazonka-dynamodb
amazonka-ec2
amazonka-elasticache
amazonka-elasticbeanstalk
amazonka-elastictranscoder
amazonka-elb
amazonka-emr
amazonka-iam
amazonka-importexport
amazonka-kinesis
amazonka-kms
amazonka-lambda
amazonka-opsworks
amazonka-rds
amazonka-redshift
amazonka-route53
amazonka-route53-domains
amazonka-s3
amazonka-sdb
amazonka-ses
amazonka-sns
amazonka-sqs
amazonka-storagegateway
amazonka-sts
amazonka-support
amazonka-swf

@endgame endgame closed this as completed Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants