You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lack of dependency version constraints in old versions of Ginger can cause those versions to be selected for a build plan and fail.
I ran into this issue when I published queue-sheet-0.7.0.2 on Hackage. The build failed with a DependencyFailed error. The build report shows that GHC 8.10.2 was used, and it looks like ginger-0.8.2.0 was selected so that the latest versions of aeson and optparse-applicative could be used. This version of Ginger does not specify aeson version constraints, but it fails to build with the selected aeson-2.0.3.0.
Perhaps package revisions should be created for older versions of Ginger to add appropriate dependency version constraints and ensure that they are not selected with incompatible dependency versions?
The text was updated successfully, but these errors were encountered:
The lack of dependency version constraints in old versions of Ginger can cause those versions to be selected for a build plan and fail.
I ran into this issue when I published queue-sheet-0.7.0.2 on Hackage. The build failed with a
DependencyFailed
error. The build report shows that GHC 8.10.2 was used, and it looks like ginger-0.8.2.0 was selected so that the latest versions ofaeson
andoptparse-applicative
could be used. This version of Ginger does not specifyaeson
version constraints, but it fails to build with the selected aeson-2.0.3.0.Perhaps package revisions should be created for older versions of Ginger to add appropriate dependency version constraints and ensure that they are not selected with incompatible dependency versions?
The text was updated successfully, but these errors were encountered: