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

Extension package title collides with OS packages #320

Open
jonhattan opened this issue Mar 6, 2017 · 2 comments
Open

Extension package title collides with OS packages #320

jonhattan opened this issue Mar 6, 2017 · 2 comments
Projects

Comments

@jonhattan
Copy link
Contributor

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.x
  • Ruby: 2.1.5p273
  • Distribution: Debian
  • Module version: 5.x.x, 4.x.x

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

package {['curl', 'memcache']: }

class {'php':
  'extensions' => {
    'curl' => {},
    'memcache' => {
      'provider' => 'pecl',
    }
  }
}

What are you seeing

Error because the package title used for the pecl extension is the same as an OS package we want to install in the same node.

What behaviour did you expect instead

Correct installation of both debian and pecl packages with the same name.

Output log

Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Package[curl] is already declared in file ...
Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Package[memcache] is already declared in file ...

@jonhattan
Copy link
Contributor Author

Same error is present in puppet3/4.x.x. It was introduced in some refactoring because it worked in old mayflower/php.

@roll4life
Copy link

@jonhattan
I Can confirm the behavior in puppet3/4.x.x on ubuntu 16.04 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Cleanup
will be solved by rewrite
Development

Successfully merging a pull request may close this issue.

2 participants