You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Voxpupuli (Forge org: "puppet") has recently taken ownership of the herculesteam/augeasproviders_* family of Puppet modules. It has released re-namespaced updates to most―but not all―of the augeasproviders_* modules to the Forge.
Puppetfile.pinned has been updated to use herculesteam-augeasproviders_core 3.2.0. This causes several problems:
The checked-out module's metadata.json is puppet-augeasproviders_core 3.2.0 (cloned from GitHub redirect)
None of the other augeasproviders_* modules resolve with it
@op-ct Does this need to get resolved for 6.6.0 or can we drop back to the previous release until 6.7.0?
We have to drop back. The full resolving suite of the new modules has yet to be updated, tagged, and published.
It turns out that not all the puppet/augeasroviders_* modules have been updated and released to resolve with each other yet. I started chipping away at SIMP-relevant outliers with voxpupuli/puppet-augeasproviders_ssh#73, but everything will need to be tagged + published + confirmed to depsolve before SIMP can upgrade to them.
6.6.0 shouldn't wait for this; it will take sustained effort with voxpupuli to ensure that all puppet/augeasroviders_* modules are published and resolve with each otther.
Voxpupuli (Forge org: "puppet") has recently taken ownership of the herculesteam/augeasproviders_* family of Puppet modules. It has released re-namespaced updates to most―but not all―of the augeasproviders_* modules to the Forge.
Puppetfile.pinned
has been updated to use herculesteam-augeasproviders_core 3.2.0. This causes several problems:metadata.json
is puppet-augeasproviders_core 3.2.0 (cloned from GitHub redirect)The text was updated successfully, but these errors were encountered: