Eric Helms

> We need some notes in the release process for this. Also, should we simply do this in our versions yaml config? And also update katello-repos.rpm Oh yea! That is...

I have raised this general thought and an open question on Discourse for debate (https://community.theforeman.org/t/candlepin-release-pipeline-and-release-process-changes/36528) to ensure I get it right.

> Lastly, it's not pretty to have Katello code in Foreman, but I don't see a cleaner way. It's so early in the boot process that we don't know about...

It could conflict, but I would expect that we can modify this or attempt to find ways to co-exist since no one version of it should be the source of...

This file has been removed.

For clarity sake, on EL 8, we get the following: ``` Installing: nodejs x86_64 1:16.18.1-3.module_el8.7.0+1234+1d8589d9 appstream 12 M Installing dependencies: brotli x86_64 1.0.6-3.el8 baseos 323 k openssl x86_64 1:1.1.1k-9.el8 baseos...

Glad to see this getting tackled, for both Ruby / Rails reasons and to fix a conflict we've had in packaging for a while now: ``` Found conflict for rubygem-fast_gettext:...

The question for me is -- what should trigger this pruning? An event? A timer?

> The very first step could be to replace the existing foreman-maintain code (https://github.com/theforeman/foreman_maintain/blob/master/definitions/checks/foreman_proxy/check_tftp_storage.rb) with invoking this rake task. From an end user perspective there wouldn't a difference, except that...

I think the overall idea is good, and the fallback makes sense to me as that is fairly reliable. What percentage of the known scanners already set origin? If they...