Open sirinek opened 6 months ago
Hello Same issue for us, the additional dependency broke our installations. This breaking change should have been in a major version or highlighted in the changelog.
That's not a major issue and the workaround is easy to implement but it's always a pain to have regressions on a minor version.
Keep up the good work, thanks.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Using module defaults
What are you seeing
Switching from 7.0.1 to 7.0.2 has a dependency of systemd 6.3.0 or newer. 7.0.1 had no such dependency and did not complain about having puppet-systemd module version 3.2.0 installed.
What behaviour did you expect instead
I expected a point release to work on its own and not break. Or at least mention the new requirement in the changelog.
Output log
Any additional information you'd like to impart
Currently testing our modules for upgrade to newer PE that uses puppet7. Will upgrade to the newer systemd.