Yes, that dependency is solved with the puppetdb module upgrade to 3.0
Unfortunately, there are other interesting modules that still depend on
ripienaar, such as example42/sudo.
I guess I'll just have to wait for updates.

Thanks for your time.

On an unrelated issue (and since I'm still starting with modules), would
this list be a good place to present a new module for review?



On Mon, Oct 28, 2013 at 6:42 PM, Garrett Honeycutt
<[email protected]>wrote:

>
> On Monday, October 28, 2013 9:21:09 AM UTC+1, SAF wrote:
>>
>> Hi all,
>>
>> How do you manage different forge modules that require conflicting
>> versions for the same module?
>> The most common example is ripienaar/concat vs puppetlabs/concat:
>> puppetlabs/puppetdb requires puppetlabs/postgreql 2.x, which requires
>> ripienaar/concat
>> puppetlabs/apache requires puppetlabs/concat
>>
>> Thanks.
>>
>>
> Looks like you a hit that issue while they were transitioning from
> ripienaar to puppetlabs. The postgresql module now correctly refers to the
> new puppetlabs/concat module[1].
>
> As for managing modules that require conflicting versions for
> dependencies, there is not an easy solution; you have to resolve the
> dependencies. This usually entails upgrading something.
>
> For the specific issue you had above, I believe that would have been
> caught by librarian-puppet, since it does dependency checking, though it
> should have just worked if you used librarian-puppet-simple[2].
>
> [1] -
> https://github.com/puppetlabs/puppetlabs-postgresql/blob/master/Modulefile#L13
> [2] - https://github.com/bodepd/librarian-puppet-simple
>
> Cheers,
> -g
>



-- 
Beware of programmers who carry screwdrivers!

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANK4U2o1trzeh6vQ1etOoM0FqKwEvcpEVoKFMSUSNMdFH10%2B-A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to