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

wrong dependencies #65

Closed
simo9900 opened this issue Mar 17, 2021 · 2 comments
Closed

wrong dependencies #65

simo9900 opened this issue Mar 17, 2021 · 2 comments
Labels
T: Fix Type: :bug: Bug Fixes

Comments

@simo9900
Copy link

I am adding in my projects the timetable in my pubspec, and I got this error

Because no versions of firebase_picture_uploader match >1.2.2 <2.0.0 and firebase_picture_uploader 1.2.2 depends on image ^3.0.1, firebase_picture_uploader ^1.2.2 requires image ^3.0.1.
And because no versions of image match >3.0.1 <4.0.0, firebase_picture_uploader ^1.2.2 requires image 3.0.1.
And because image 3.0.1 depends on archive ^3.0.0 which depends on crypto ^3.0.0, firebase_picture_uploader ^1.2.2 requires crypto ^3.0.0.
And because timetable >=0.2.7 depends on dartx ^0.5.0 which depends on crypto ^2.1.0, firebase_picture_uploader ^1.2.2 is incompatible with timetable >=0.2.7.
So, because remote_students depends on both firebase_picture_uploader ^1.2.2 and timetable ^0.2.8, version solving failed.
pub get failed (1; So, because remote_students depends on both firebase_picture_uploader ^1.2.2 and timetable ^0.2.8, version solving failed.)

This is my pubspec.yaml

  firebase_picture_uploader: ^1.2.2

  timetable: ^0.2.8
  time_machine: ^0.9.16

dependency_overrides:
  time_machine:
    git:
      url: https://github.com/Dana-Ferguson/time_machine
      ref: 7753e0d

I can't use another package lower than firebase_picture_uploader ^1.2.2. Can anyone have an idea how can I solve it?

Thanks

@simo9900 simo9900 added the T: Fix Type: :bug: Bug Fixes label Mar 17, 2021
@JonasWanke
Copy link
Owner

dartx ^0.5.0 (a dependency of this package) depends on crypto ^2.1.0, which is now replaced by the null-safe crypto ^3.0.0. I'm working on a major refactor (#17) that drops the dependency on dartx and also migrates to null-safety, so this problem should be fixed when that refactor is complete.

In the meantime, you could try adding either dartx: ^0.6.0 or crypto: ^3.0.0 to your dependency_overrides.

@simo9900
Copy link
Author

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: Fix Type: :bug: Bug Fixes
Projects
None yet
Development

No branches or pull requests

2 participants