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

install - Unable to resolve dependencies on INTERNAL Azure DevOps Server using v2 feeds #130

Closed
steviecoaster opened this issue Mar 16, 2020 · 2 comments
Labels
Not An Issue / Invalid Invalid or are unable to be reproduced. Orange Labels are "closing with no work completed" labels.

Comments

@steviecoaster
Copy link

steviecoaster commented Mar 16, 2020

NOTE: This works fine when using Azure DevOps online repositories, it seems to be an issue with an internally deployed Azure DevOps Server only.

What You Are Seeing?

Attempting to install a package which has dependencies is unable to resolve them

What is Expected?

Dependencies are found and installed prior to the package

How Did You Get This To Happen? (Steps to Reproduce)

choco install git -y against an internal Azure DevOps Server source is unable to find git.install and subsequent dependencies

Internal Issue

@steviecoaster steviecoaster added Bug Tickets that represent defects/bugs. Priority_HIGH Represents high priority tickets - things that must be addressed soon. 0 - Backlog Where tickets start after being triaged. This means the ticket has targeted milestone/labels. 0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. Edition - Business labels Mar 16, 2020
@ferventcoder
Copy link
Member

Does this happen all the time? What makes it reproducible?

Do you see any workarounds?

@ferventcoder ferventcoder changed the title Chocolatey - Issues with dependencies on internal Azure DevOps Server install - Unable to resolve dependencies on INTERNAL Azure DevOps Server using v2 feeds Mar 16, 2020
@ferventcoder ferventcoder removed 0 - Backlog Where tickets start after being triaged. This means the ticket has targeted milestone/labels. Edition - Business Priority_HIGH Represents high priority tickets - things that must be addressed soon. labels Mar 16, 2020
@ferventcoder
Copy link
Member

ferventcoder commented Mar 30, 2020

chocolatey/choco#1871

It looks like doing the following should work: choco feature disable -n usepackagerepositoryoptimizations

@ferventcoder ferventcoder added Not An Issue / Invalid Invalid or are unable to be reproduced. Orange Labels are "closing with no work completed" labels. and removed 0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. Bug Tickets that represent defects/bugs. labels Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Not An Issue / Invalid Invalid or are unable to be reproduced. Orange Labels are "closing with no work completed" labels.
Projects
None yet
Development

No branches or pull requests

2 participants