#12975 Implement Scripts Directory Restructuring — Part 2/2 (per #12935)
Closed: Fixed by jnsamyak. Opened by jnsamyak.

Describe the issue

Implement the moves/renames and cleanups for the Part 2/2 set: package lifecycle/maintenance, QA/FTBFS tools, sync utilities, and infra utilities as finalized in #12935. Apply all external updates (Ansible, timers, docs) and ensure dependent repos are updated/merged in the right order.

Context

  • Overall target tree: see restructuring initiative (#12925).
  • Broader script inventory for Part 2 also includes sync, QA/FTBFS, and misc folders per the investigation’s scope and directories list.

Scope (Part 2/2 set)

Replace with the exact list from the final sheet resolution of #12935.
For each item, we will:
- Move to the new path; rename as per the convention file if required.
- Update imports/calls between scripts.
- Update systemd timers/cron/Ansible roles.
- Update docs/SOPs.

Dependencies (PR chain)

  • Create these PRs and paste links before starting merges.
  • releng (this repo): Moves/renames + internal references (PR-A).
  • Ansible/infra (PR-B) → must merge before any timers trigger new paths.
  • Docs/SOPs (PR-C) → can merge alongside PR-A but publish after deploy.
  • Any other repos referencing these scripts (PR-D…).

The scripts listed under Part 1/2 (#12934) are out of scope unless explicitly shared/dependent. As mentioned in our calls, we will move the paths now and URLs for Forgejo separately at the time of migration.

Acceptance criteria

  • All review comments in #12935 acknowledged/addressed.
  • New paths/names match the directory schema from #12925.
  • All internal and external invocations/imports/callers updated.
  • Docs/SOPs reflect the new paths.
  • Monitor the scripts timely in error messages, IRCs, tickets, etc for any relevant issues.

  • When do you need this? (YYYY/MM/DD)

Ideally, the work is being done for this since, start of this week (September 22/23), but I decided to have this merged by next Wednesday. If there are any blockers, please communicate.

  • When is this no longer needed or useful? (YYYY/MM/DD)

When will we not release Fedora anymore!

  • If we cannot complete your request, what is the impact?

Migration for forgejo will be affected.

Please check https://www.fedorastatus.org/ for any known
outages before filing issues on an outage.


Metadata Update from @jnsamyak:
- Issue assigned to amedvede
- Issue tagged with: high-gain, medium-trouble

Metadata Update from @jnsamyak:
- Custom field blocking adjusted to 12925
- Issue marked as blocking: #12925

PR for refactoring is available on the following URL: https://pagure.io/releng/pull-request/12978#

It is done, when all PRs would be merged, and nothing will happen after that during some time, ticket can be closed

Closing this as fixed, make sure to monitor the changes.

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata