Eric Helms
Eric Helms
Appears this may be needed at this level for non-RPM environments even: ``` /Stage[main]/Katello_devel::Setup/Katello_devel::Bundle[exec rake db:migrate]/Exec[bundle-exec rake db:migrate]/returns WARNING: File locale/bn/LC_MESSAGES/foreman_virt_who_configure.mo outdated, regenerate with 'make all-mo' WARNING: File locale/cs_CZ/LC_MESSAGES/foreman_virt_who_configure.mo outdated,...
> From @stejskalleos original comment I got that he wants to include the erb-linting rules into rubocop. Which IMO is not connected and does not make sense As I understand...
I think a PR is sufficient - let's double check whether @ekohl feels this rises to the level of an RFC
See https://github.com/theforeman/foreman-infra/pull/2016 for discussion that sparked this issue
Does stopping rsync affect how we get RPMs from Jenkins / Local into staging? and from staging to production?
`repo-01` works for me
Updated to only include EL 9 instructions going forward.
If I do the math correctly, that means with the 3.11 release we can take on this work.
What would you do with Pulpcore and Candlepin? For consistency, should we do by project and then version? e.g. ``` ├── candlepin │ ├── 4.1 │ └── 4.2 ├── foreman...
> Yes, that would be best. Though for candlepin aren't they essentially also tied to a Foreman release? Today they're for a Katello release and Katello is essentially for a...