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

Allow Chocolatey to search LiGet #16

Open
ALINRUISU opened this issue May 14, 2019 · 3 comments
Open

Allow Chocolatey to search LiGet #16

ALINRUISU opened this issue May 14, 2019 · 3 comments

Comments

@ALINRUISU
Copy link

ALINRUISU commented May 14, 2019

Chocolatey client unable to search LiGet to install chocolatey packages

Steps to reproduce the issue

Added LiGET as source

C:\admin\projects\chocolatey\awscli>choco source add -n=poc -s="http://liget:9011"
Chocolatey v0.10.13
2 validations performed. 1 success(es), 1 warning(s), and 0 error(s).
Added poc - http://liget:9011 (Priority 0)

Failure 0 package found

C:\admin\projects\chocolatey\awscli>choco search
Chocolatey v0.10.13
2 validations performed. 1 success(es), 1 warning(s), and 0 error(s).

Validation Warnings:
 - A pending system reboot request has been detected, however, this is
   being ignored due to the current command being used 'search'.
   It is recommended that you reboot at your earliest convenience.

[NuGet] Not able to contact source 'http://liget:9011'. Error was Invalid URI: Invalid port specified.
[NuGet] Not able to contact source 'http://liget:9011'. Error was Invalid URI: Invalid port specified.
0 packages found.

I have no problems pushing to Repo, only searching

C:\admin\projects\chocolatey\awscli>choco push cwrsync.5.4.1.nupkg --source="http://liget:9011" --api-key="test123" --force
Chocolatey v0.10.13
2 validations performed. 1 success(es), 1 warning(s), and 0 error(s).

Attempting to push cwrsync.5.4.1.nupkg to http://liget:9011
cwrsync 5.4.1 was pushed successfully to http://liget:9011
@ALINRUISU ALINRUISU reopened this May 14, 2019
@ALINRUISU
Copy link
Author

Ops accidentally closed the issue

@mschnecke
Copy link

+1

1 similar comment
@rrittsteiger
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants