Reconsider approval of https://fedoraproject.org/wiki/Changes/RelocateRpmRepoConfigsToUsr as a "self-contained Change" #3648

Closed
opened 2026-07-20 18:43:58 +00:00 by adamwill · 4 comments

I did not catch this Change when it was proposed, but I do not believe it was correct to approve https://fedoraproject.org/wiki/Changes/RelocateRpmRepoConfigsToUsr as a "self-contained change". Per the Changes policy, here is the definition of a "self-contained Change":

"A self-contained change is a change to isolated package(s), or a general change with limited scope and impact on the rest of the distribution/project. Examples include addition of a group of leaf packages, or a coordinated effort within a Special Interest Group (SIG) with limited impact outside the SIG’s functional area."

Moving core configuration files that have been where they are for literal decades somewhere else, without a symlink, seems very much not to meet this definition. Even within the Change proposal itself, it is admitted that this will break multiple older versions of package managers which are still in active use (we definitely still have things using python3-dnf).

I'm not saying the Change should be rejected, but it should be treated as a high-profile system-wide Change. It is not self-contained.

I did not catch this Change when it was proposed, but I do not believe it was correct to approve https://fedoraproject.org/wiki/Changes/RelocateRpmRepoConfigsToUsr as a "self-contained change". Per the [Changes policy](https://docs.fedoraproject.org/en-US/operations/changes_policy/), here is the definition of a "self-contained Change": "A self-contained change is a change to isolated package(s), or a general change with limited scope and impact on the rest of the distribution/project. Examples include addition of a group of leaf packages, or a coordinated effort within a Special Interest Group (SIG) with limited impact outside the SIG’s functional area." Moving core configuration files that have been where they are for literal decades somewhere else, without a symlink, seems very much *not* to meet this definition. Even within the Change proposal itself, it is admitted that this will break multiple older versions of package managers which are still in active use (we *definitely* still have things using python3-dnf). I'm not saying the Change should be rejected, but it should be treated as a high-profile system-wide Change. It is not self-contained.
Owner

+1 to reclassify as a system-wide Change

+1 to reclassify as a system-wide Change
Owner

+1, reasonable request indeed

+1, reasonable request indeed
Owner

+1 to recategorize.

+1 to recategorize.
Owner

This was discussed during the meeting today:
* AGREED: https://fedoraproject.org/wiki/Changes/RelocateRpmRepoConfigsToUsr is recategorized as a System Wide Change (+5, 0, 0)
* ACTION: Neal Gompa (Fedora) to fill in the Change Page with details required for a System Wide Change.
* ACTION: Announce the Change reclassification on devel-announce once the updates have been made

This was discussed during the meeting today: * AGREED: https://fedoraproject.org/wiki/Changes/RelocateRpmRepoConfigsToUsr is recategorized as a System Wide Change (+5, 0, 0) * ACTION: Neal Gompa (Fedora) to fill in the Change Page with details required for a System Wide Change. * ACTION: Announce the Change reclassification on devel-announce once the updates have been made
Sign in to join this conversation.
No milestone
No project
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fesco/tickets#3648
No description provided.