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

VCS repo not install on Windows #58

Open
elliotblackburn opened this issue Feb 9, 2017 · 1 comment
Open

VCS repo not install on Windows #58

elliotblackburn opened this issue Feb 9, 2017 · 1 comment

Comments

@elliotblackburn
Copy link

I'm quite new to Puppet so still finding my feet, but I've been using this module for a while on OSX with no problems for a few vagrant boxes. I've been trying to run my same vagrant scripts and provisions on my Windows machine and I'm getting the same error that has been talked about here: rodjek/librarian-puppet#288 in the old librarian-puppet repo.

I'm not sure if this is better posted in the Vox Pupuli librarian-puppet issues so I thought I'd start here as I'm directly using this module.

Error message:

I've copied the error message from the linked issue here for history/archiving, my error is the same and with the same module but a few of my paths are different. I've not got access to my windows machine right now but will update this later today when I do with the error generated on my machine.

==> default: Installing Puppet modules in "puppet" with Librarian-Puppet...
C:/Users/user/.vagrant.d/gems/gems/librarian-puppet-1.4.1/lib/librarian/pup
pet/source/forge/repo.rb:65:in `install_version!': C:/chef/windows_vagrant_puppe
t/puppet/.tmp/librarian/cache/source/puppet/forge/forgeapi_puppetlabs_com/puppet
labs-vcsrepo/1.2.0/vcsrepo does not exist, something went wrong. Try removing it
manually (Librarian::Error)

I'm just at a bit of a loss of where to look or what might be causing it, if this is not the correct place to post this issue then I'd be happy to move it to the more relevant repo. Thanks for your time!

@diLLec
Copy link

diLLec commented Feb 17, 2017

Hi @BlueHatbRit,

got the same issue on windows 7. The reason seams to be, that the path over all is too long for windows to handle. Try to shorten the puppet.module_path a bit.

Greetings,
diLLec

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

2 participants