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

Paket conflicts with pinned prerelease version #1716

Closed
Stift opened this Issue Jun 3, 2016 · 7 comments

Comments

Projects
None yet
2 participants
@Stift
Contributor

Stift commented Jun 3, 2016

Description

When I want to update a dependency, paket stops with a version conflict. This seems to be introduced with 2.66.8

Repro steps

  1. The minimal dependency file
    nuget npgsql 2.2.5-custom
    nuget CustomPackage

The custom package has a dependency on npgsql >= 2.0 < 3.0 and npgsql is a custom build version by us.

  1. paket install works fine
  2. paket update works fine as well
  3. paket update nuget CustomPackage crashes with the following error message:
Paket failed with:
        There was a version conflict during package resolution.
  Resolved packages:
   - CustomPackage 1.0.10047
  Could not resolve package npgsql:
   - Dependencies file requested package npgsql: 2.2.5-custom
   - CustomPackage 1.0.10047 requested package npgsql: >= 2.0 < 3.0

  Please try to relax some conditions.

Expected behavior

the dependency resolution should end without any error message as the npgsql package is in the scope of the dependency constraint of the CustomPackage

Actual behavior

Error message as above.

Known workarounds

Downgrading to paket 2.66.7

Related information

  • Windows
  • stable
  • .NET Runtime
@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jun 3, 2016

Member

Can you please create an zip with the repro sample?

Member

forki commented Jun 3, 2016

Can you please create an zip with the repro sample?

@Stift

This comment has been minimized.

Show comment
Hide comment
@Stift

Stift Jun 3, 2016

Contributor

Ok. Sent it to you via email.

Contributor

Stift commented Jun 3, 2016

Ok. Sent it to you via email.

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jun 3, 2016

Member

mhm I did not get any mail

Member

forki commented Jun 3, 2016

mhm I did not get any mail

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jun 3, 2016

Member

can you upload it here?

Member

forki commented Jun 3, 2016

can you upload it here?

@Stift

This comment has been minimized.

Show comment
Hide comment
@Stift

Stift Jun 3, 2016

Contributor

security scan of gmail took the mail down. 😢
I'll send a link again. Cannot post it here, because it's partially internal.

Contributor

Stift commented Jun 3, 2016

security scan of gmail took the mail down. 😢
I'll send a link again. Cannot post it here, because it's partially internal.

@forki forki closed this in cf9b94a Jun 3, 2016

@forki forki added the bug label Jun 3, 2016

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki Jun 3, 2016

Member

please retry

Member

forki commented Jun 3, 2016

please retry

@Stift

This comment has been minimized.

Show comment
Hide comment
@Stift

Stift Jun 7, 2016

Contributor

seems to work for. thx

Contributor

Stift commented Jun 7, 2016

seems to work for. thx

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