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

Groups with different sources resolves the wrong packages #1711

Closed
franknarf8 opened this Issue May 30, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@franknarf8

franknarf8 commented May 30, 2016

Description

We are working with multiple Nuget streams (Release, Debug, ...) and at one point we want to download a versions of the package from both feeds and put them in separate groups. They are named the same way and may have the same version number, but they have different content.

We have a paket.dependencies file that looks like this :

source TestA
nuget Test

group Cumulus.1.0
    source TestB
    nuget Test

Thing is, when we try to resolve this with 'paket update' it installs the same version in both groups. (the version from the TestB feed)

Repro steps

Just run 'paket update' on this repo at this point in time and you should see the problem. (One of the Test.nupkg contains a file 'a.txt' and the other one contains 'b.txt'; paket update resolves both packages to the one contianing 'a.txt') (I also tried it with different versions, and they still do not resolve properly)
https://github.com/franknarf8/paket-issue-repro/tree/Bug_GroupStreamResolving

Expected behavior

I would expect that each groups are resolved completely independently; feeds and all.

Actual behavior

If a package is found on another feed, another feed that has no versionning constraints may simply use that package even if the feed is different.

@forki forki added the bug label May 31, 2016

@forki forki closed this in 2c8c845 May 31, 2016

@forki

This comment has been minimized.

Show comment
Hide comment
@forki

forki May 31, 2016

Member

thanks for the excellent repro sample.
Should be fixed now.

Member

forki commented May 31, 2016

thanks for the excellent repro sample.
Should be fixed now.

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