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

cpack path/to/nuspec not working #411

Closed
dhilgarth opened this issue Sep 18, 2015 · 5 comments
Closed

cpack path/to/nuspec not working #411

dhilgarth opened this issue Sep 18, 2015 · 5 comments

Comments

@dhilgarth
Copy link

Specifying the path to the nuspec file when calling cpack doesn't work.

cpack will report that it can't find the files specified in the nuspec file because it is looking in the current working directory and not in the folder the nuspec file is in.

Examples:

c:\packages\automatic\_output>cpack balsamiqmockups3\3.1.9\BalsamiqMockups3.nuspec
Chocolatey v0.9.9.2
Could not find a part of the path 'c:\packages\automatic\_output\tools'.

c:\packages\automatic\_output>cpack c:\packages\automatic\_output\balsamiqmockups3\3.1.9\BalsamiqMockups3.nuspec
Chocolatey v0.9.9.2
Could not find a part of the path 'c:\packages\automatic\_output\tools'.
@dhilgarth
Copy link
Author

Looks like it has been fixed in the meantime. Updating to 0.9.9.8 solved it.

@ferventcoder
Copy link
Member

Yes, this was fixed awhile ago. :)

@dhilgarth
Copy link
Author

Sorry about that. I just realized the version number after I posted the issue. Too many machines with Chocolatey... :-)
Is there some way for chocolatey to tell me periodically that there are updates to my installed applications?

@ferventcoder
Copy link
Member

Duplicate of #232

@aronovgj
Copy link

@dhilgarth there is choco outdated or cup all --noop. you could schedule one of those in a script to be performed regularly, intercepting the output and notifying you about updates.

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

No branches or pull requests

3 participants