Skip to content

Pinned version of puppetlabs/reboot is too strict. #419

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

Closed
madelaney opened this issue Jan 24, 2019 · 2 comments · Fixed by #426
Closed

Pinned version of puppetlabs/reboot is too strict. #419

madelaney opened this issue Jan 24, 2019 · 2 comments · Fixed by #426

Comments

@madelaney
Copy link

What you expected to happen?

I'd expect the required version range of puppetlabs/reboot to be more forgiving given that the usage is very limiting.

What happened?

While trying to resolve dependencies in modules, the requirement of puppetlabs/reboot, causes an issue.

How to reproduce it?

Allow for a range vs. hard code version 2.0.0

Anything else we need to know?

Versions:

$ puppet --version
4.10.12

$ docker version
18.09.0, build 4d60db4

$ facter os
{"name"=>"Darwin", "family"=>"Darwin", "release"=>{"major"=>"18", "minor"=>"2", "full"=>"18.2.0"}}

$ puppet module list

Logs:

[Librarian] Conflict between puppetlabs-reboot (= 2.0.0) <https://forge.domain.com> and puppetlabs-reboot/2.1.2 <https://forge.domain.com>
@davejrt
Copy link
Contributor

davejrt commented Jan 25, 2019

We'll do some testing testing and if we don't find any issues, update and push out a small release with the fix.

@madelaney
Copy link
Author

Awesome, thank you @davejrt.

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

Successfully merging a pull request may close this issue.

2 participants