Issue #3039
Updated by Ichimonji10 over 6 years ago
Uninstalling <code>pulp-rpm-handlers</code> removes <code>/etc/yum.repos.d/pulp.repo</code>. This is concerning, because: 1. This file isn't owned by the <code>pulp-rpm-handlers</code> package, as far as I can tell. A package shouldn't touch files it doesn't own. 2. It's unintuitive. I've never, ever heard of a package that blows away an entire repository file. At most, I would expect an entry from messes with a repository system-wide repository, especially in a file to be removed. that it doesn't own. 3. It can break the system. Any number of repositories might be listed in that file, and blowing away that file will make all of them unavailable. This third point is the one that's most problematic. Whenever a system is provisioned with the Ansible playbooks in the pulp_packaging repository, a repository is created in <code>/etc/yum.repos.d/pulp.repo</code>, where that file lists our nightly builds of Pulp 2.x. Uninstalling <code>pulp-rpm-handlers</code> blows away that file, which breaks the system, which makes it *much* harder to test pulp-consumer and pulp-agent. "Pulp Smash #611":https://github.com/PulpQE/pulp-smash/issues/611 is heavily affected.
.