-
Notifications
You must be signed in to change notification settings - Fork 520
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 remove nuget does also a general unwanted update #1652
Comments
can you please create a zip with a repro? |
Could not repro without our Artifactory instance and private packages with 2.63.2.0 |
paket runs install after remove and tries to keep versions as stable as possible. |
We do use prereleases: I have tried to repro with nuget.org and this prerelease, but it still does not repro on a dummy repo. What do you mean by unlisted versions? |
it's possible to "delete" versions by unlisting them. If a version is unlisted then paket will try to use a different version during install. |
Thanks for the explanation, as far as I know we never delete package versions in our private server |
the question is why install changes the dependencies for you, but without a repro it's really hard to say. |
I can only repro this with our big codebase and its 70 custom packages, including 2 prereleases, using exclusively Artifactory v2.7 as source. |
I had another case of this today where removing a prerelease paket did cause a full update in v2; but it worked fine in v3 without causing a full update. It looks like this issue has been fixed in v3, maybe as side effect of other changes in this area. |
Yeah we worked a bit in this and I hope it's fine when we finally go to v3 |
This issue still reproducible with latest Paket (3.19.8.0) and scoobadog/Paket-1652 repository. Here is the output from
|
Seeing this here too. |
thanks for repoting a repro sample |
Description
Given a repository with no Groups
and with several nuget package references
with some of them being outdated
When a paket remove nuget XXX is done to delete definitely a reference, paket also does a full update on every other package
Then everything is messed up
Repro steps
Expected behavior
The package XXX is removed from paket.dependencies and paket.lock
Actual behavior
The package XXX is removed from paket.dependencies and paket.lock
And outdated packages are updated to latest version
Known workarounds
Is deleting the given package lines in paket.dependencies and lock good enough? I don't think so.
Related information
The text was updated successfully, but these errors were encountered: