Closed josepedrocorreia closed 10 years ago
Thanks for the simple example and detailed output.
Looks like this was introduced in Version 0.3.0, where queries to proxies started being passed more directly through to the proxied servers (to improve performance and internal APIs). Unfortunately, the download paths from the the proxied server (/system/releases/d/domcleal/domcleal-augeasproviders-1.0.2.tar.gz
in your example) were being passed back to the client, which resulted in puppet-library attempting to download modules using the wrong paths on the proxy (it should have been /modules/domcleal-augeasproviders-1.0.2.tar.gz
in your example).
A fix just went in to 438399c0054ca731e136fa64b1b8401d16d2bbb7, and I just released Version 0.7.0, which contains the fix.
Feel free to reopen if you still find the issue with 0.7.0.
This seems to work, thanks.
Hi,
I'm using this in conjunction with
librarian-puppet
. My aim is to have a server that both proxies the Puppet Forge and serves some additional modules from a directory.I'm running into a problem though.
librarian-puppet
seems to be able to retrieve meta information from the server (like dependencies and such) but there seems to be a problem when the Puppet command to install the module is fired. Here's the log fromlibrarian-puppet
:It looks to me like the original problem is that
librarian-puppet
cannot download the archive. This seems to be confirmed by the log frompuppet-library
:My
Puppetfile
is simply:Any clues what might be going wrong?