Eric Helms
Eric Helms
I think this will need a rebase to pass tests.
[test foreman-installer]
That blog post is unclear to me if it translates runtime dependencies into the buildroot dependencies. Or if it translates buildroot dependencies that same way when using `copr://` -- have...
> Note that https://github.com/Shopify/bootsnap says it can work in production: > > > All Bootsnap features are enabled in development, test, production, and all other environments according to the configuration...
> Not sure if test failure is related.. 😕 Looks like minitar 1.0.0 was released today and we made need to pin it for the time being -- https://rubygems.org/gems/minitar/versions/1.0.0
Why do we want to put this behind a setting? As in, should we just remove the version from the API response all together?
Tested and I see the proper error message: ``` 2024-10-24 13:55:54 [NOTICE] [root] Loading installer configuration. This will take some time. 2024-10-24 13:55:56 [NOTICE] [root] Running installer with log based...
From discussion with @ianballou, a check that evr extension will be added to this hook since for fresh installations the EVR extension would not be expected to have been installed.
@ianballou Can you fix up the rubocop issue?
We should also add a similar check to foreman-maintain to test the ownership before upgrading for the best user experience.