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

Incompatible with released version of puppetlabs-stdlib #130

Closed
tpdownes opened this issue May 22, 2019 · 2 comments
Closed

Incompatible with released version of puppetlabs-stdlib #130

tpdownes opened this issue May 22, 2019 · 2 comments

Comments

@tpdownes
Copy link

tpdownes commented May 22, 2019

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: puppet-agent-5.5.14-1.el7.x86_64
  • Ruby: ?
  • Distribution: CentOS
  • Module version: 2.2.0

How to reproduce (e.g Puppet code you use)

sudo -i puppet module install puppet-squid --version 2.2.0

What are you seeing

Failed installation of puppet-squid claiming dependency resolution cannot succeed.

What behaviour did you expect instead

puppet-squid installation should succeed.

Output log

Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...
Notice: Downloading from https://forgeapi.puppet.com ...
Error: Could not install module 'puppet-squid' (???)
  No version of 'puppet-squid' can satisfy all dependencies
    Use `puppet module install --ignore-dependencies` to install only this module

Any additional information you'd like to impart

puppetlabs-stdlib 6.0.0 was just released today so not surprising and will require testing. It does not appear to be a problem with the direct dependency claim in the puppet-squid metadata. It can be resolved by downgrading puppetlabs-stdlib to 5.2.0 and re-trying installation.

The release notes don't look scary but there are a number of commits behind the major version change.

@mmoll
Copy link
Contributor

mmoll commented May 31, 2019

GH-131 might fix this.

@bastelfreak
Copy link
Member

Hi. I'm doing a new release in #132 which fixes this.

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

4 participants