Dependency issue with the augeasproviders ecosystem after adoption

[timdeluxe]

Sorry that i ditched the template here, but this issue is more general.

It is nice, that this module experiences better maintenance under the voxpupuli umbrella, but it is the base for a whole ecosystem of "addon"-modules (https://forge.puppetlabs.com/modules/herculesteam), these "addon"-modules have the previous herculesteam-augeasproviders_core as dependency, which is now broken.
Technically it still works, if you use those addons with this adopted core module, but it is not a clean depencency management. If you do proper dependency resolution (like we do) it is broken.

Is it planned to adopt the other modules as well, or will the original author update them to fix the dependency?

[ekohl]

Various other modules have been transferred already and I know @bastelfreak is going through the conversions. See https://github.com/voxpupuli?q=puppet-augeasproviders&type=all&language=&sort= as well.

Looking at it, these are still open:

• modulesync 5.4.0; drop Puppet 5 support & require 6.1 or newer puppet-augeasproviders_base#5
• modulesync 5.4.0; Drop Puppet 5, add Puppet 7 puppet-augeasproviders_mounttab#10
• modulesync 7.3.0 puppet-augeasproviders_nagios#5
• modulesync 7.3.0 puppet-augeasproviders_puppet#6
• modulesync 5.5.0 puppet-augeasproviders_sysctl#65
• modulesync 7.3.0 puppet-augeasproviders_syslog#13

Any help would be appreciated.

It also looks like some approved module statuses need to be transferred to VP's modules.

[bastelfreak]

If someone can take a look at the open PrRs, the sysctl one in particular, that would be amazing.