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

Upgrade shouldn't run if package constraints resolve to the installed version #3404

Open
6 tasks done
iki opened this issue Mar 9, 2024 · 4 comments
Open
6 tasks done
Labels

Comments

@iki
Copy link

iki commented Mar 9, 2024

Checklist

  • I confirm there are no unresolved issues reported on the Chocolatey Status page.
  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my problem.
  • I have verified this is not an issue for a specific package.
  • I have verified this issue is not security related.
  • I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

>>> choco upgrade --yes --skip-if-not-installed dart-sdk

You have dart-sdk v3.3.0 installed. Version 3.3.1 is available based on your source(s).
[NuGet] One or more unresolved package dependency constraints detected in the Chocolatey lib folder. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'sass 1.71.1 constraint: dart-sdk (= 3.3.0)'
Re-attempting package dependency resolution using additional available package information...
[NuGet] One or more unresolved package dependency constraints detected in the Chocolatey lib folder. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'sass 1.71.1 constraint: dart-sdk (= 3.3.0)'
Progress: Downloading dart-sdk 3.3.0... 100%

dart-sdk v3.3.0 [Approved]
dart-sdk package files upgrade completed. Performing other installation steps.

What is Expected?

>>> choco upgrade --yes --skip-if-not-installed dart-sdk

You have dart-sdk v3.3.0 installed. Version 3.3.1 is available based on your source(s).
[NuGet] One or more unresolved package dependency constraints detected in the Chocolatey lib folder. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'sass 1.71.1 constraint: dart-sdk (= 3.3.0)'
Re-attempting package dependency resolution using additional available package information...
[NuGet] One or more unresolved package dependency constraints detected in the Chocolatey lib folder. All dependency constraints must be resolved to add or update packages. If these packages are being updated this message may be ignored, if not the following error(s) may be blocking the current package operation: 'sass 1.71.1 constraint: dart-sdk (= 3.3.0)'

You already have dart-sdk v3.3.0 installed.

How Did You Get This To Happen?

Installed sass package, that has fixed version of dart-sdk dependency.

Later, dart-sdk was updated, so my choco outdated --ignore-pinned -r listed it and passed to choco upgrade --yes --skip-if-not-installed [packages]. The same would happen with choco upgrade --all --yes.

The same happens when upgrading any package with newer available version, but constraints restricting it to the currently installed version.

System Details

  • Operating System: 10.0.22635.0
  • Windows PowerShell version: 5.1.22621.2706
  • Chocolatey CLI Version: 2.2.2
  • Chocolatey Licensed Extension version: -
  • Chocolatey License type: -
  • Terminal/Emulator: cmder

Installed Packages

sass
dart-sdk

Output Log

https://gist.github.com/iki/7b10b95c0671c325f2c890355f39e739

Additional Context

No response

@iki iki added the Bug label Mar 9, 2024
@pauby
Copy link
Member

pauby commented Mar 9, 2024

Please add the log as gist and add a link to it in the comment above.

@iki
Copy link
Author

iki commented Mar 23, 2024

Copy link

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue will be closed in 14 days if it continues to be inactive.

@github-actions github-actions bot added the Pending Closure This issue has been marked as having no response or is stale and will soon be closed. label Apr 23, 2024
Copy link

github-actions bot commented May 7, 2024

Dear contributor,

As this issue seems to have been inactive for quite some time now, it has been automatically closed.
If you feel this is a valid issue, please feel free to re-open the issue if / when a pull request
has been added.
Thank you for your contribution.

@github-actions github-actions bot closed this as completed May 7, 2024
@pauby pauby removed 0 - Waiting on User No Response / Stale Pending Closure This issue has been marked as having no response or is stale and will soon be closed. labels May 7, 2024
@pauby pauby reopened this May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants