Ewoud Kohl van Wijngaarden
Ewoud Kohl van Wijngaarden
True, but the idea I have is to and up with less logic in `gem2rpm/foreman_plugin.spec.erb` anyway. Combined with https://github.com/theforeman/foreman-packaging/pull/8414 I'd like to get rid of a lot of templating. Perhaps...
https://github.com/theforeman/forklift/pull/1866 & https://github.com/theforeman/forklift/pull/1888 work towards fixing the `foreman_provisioning_infrastructure` role and making it easier to maintain.
I haven't checked, but it sounds like it either ships nokogiri >= 1.16 or no nokogiri at all.
ok to test
It broke all of fog-libvirt's test suite. I opened https://github.com/fog/fog-libvirt/pull/140 but I'm tempted to release a new bugfix version that pins to < 0.8.3 in the short term. Then merge...
We've updated to fog-libvirt 0.13 which is compatible with this so I've manually updated this to remove files.
Or taking a step back: a warning is only useful if someone ends up acting on it, but with a deprecation there is no immediate need. So which ways are...
> > So you need tooling (likely in rspec-puppet) to force deprecations to be fatal. > > Yes I completely agree. > > I'd also add that "force deprecations to...
If/When this is merged, we should submit a docs update to simplify the procedure.
My thought was to fork the COPR repo that was created for this PR and build a plugin there.