Issue #14528 has been updated by Ken Barber. Status changed from Accepted to Duplicate
This is a duplicate of #13542. ---------------------------------------- Bug #14528: Modules must be published to the forge before they can be accurately installed https://projects.puppetlabs.com/issues/14528#change-65155 Author: Josh Cooper Status: Duplicate Priority: Normal Assignee: Category: module tool Target version: Affected Puppet version: 2.7.14 Keywords: module forge moduletool Branch: We're working on the registry module. It's never been published to the forge. I generated an archive: <pre> cd /work/modules/puppetlabs-registry $ puppet module build pkg Building /Users/josh/work/modules/puppetlabs-registry for release pkg/puppetlabs-registry-0.0.1.tar.gz </pre> I then tried to install the module (to verify it works before publishing to the forge). <pre> $ puppet module install ~/work/modules/puppetlabs-registry/pkg/puppetlabs-registry-0.0.1.tar.gz Preparing to install into /Users/josh/.puppet/modules ... Downloading from http://forge.puppetlabs.com ... Error: Could not find release information for this module (puppetlabs/registry) (HTTP 404) Error: Try 'puppet help module install' for usage </pre> This fails because we've never published this to the forge. This is surprising, because I've given the module tool a local archive to install. I would expect that it would use the dependency metadata in the local archive, and if there are dependencies, retrieve them from the forge. I can work-around the issue by specifying `--force` or `--ignore-dependencies`, but this means I'm not accurately testing that an end-user installing my module can resolve any dependencies my module may have. More subtle is that the dependency metadata on the forge may be different than the metadata in the local archive. Suppose the version (0.1) on the forge did not have any dependencies, but the local version (0.2) does have a dependency, and that dependency is not installed locally and is not on the forge. Running `puppet module install <local>` would "succeed". But as soon as you publish the local archive and try `puppet module install <forge>` it will fail. Which means you have to actually publish your module in order to accurately test it. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
