Migrate tag2distrepo Repository from Pagure to Forgejo

jnsamyak commented

2025-11-18 09:10:09 +00:00

Owner

tag2distrepo is used to map tags to distrepos and is tied closely to Koji workflows. As part of the Sprint 5 plan for migrating RelEng sub-repositories, we need to evaluate and migrate this repository to Forgejo within two weeks.

Phase 1: Investigation (Week 1)

Tasks:
Identify all scripts and automation paths that depend on tag2distrepo.
Review integration points with Koji, especially any API calls or hooks.
List open issues, branches, or PRs that need to be accounted for.
Validate compatibility with Forgejo migration tooling.

Phase 2: Implementation (Week 2)
Tasks:

Execute migration to Forgejo.
Verify the following post-migration:
- All branches and commit history
- Working scripts & tag mapping functionality
- Koji workflows not broken by URL changes
Update references in Koji-related SOPs and scripts.
Close Pagure repository and replace with README redirect.

Acceptance Criteria

Repository migrated with no data loss.
Koji continues to correctly reference tag → distrepo mappings.
All tooling updated to use Forgejo URLs.
Pagure repository disabled and cleaned.

tag2distrepo is used to map tags to distrepos and is tied closely to Koji workflows. As part of the Sprint 5 plan for migrating RelEng sub-repositories, we need to evaluate and migrate this repository to Forgejo within two weeks. --- **Phase 1: Investigation (Week 1)** Tasks: Identify all scripts and automation paths that depend on tag2distrepo. Review integration points with Koji, especially any API calls or hooks. List open issues, branches, or PRs that need to be accounted for. Validate compatibility with Forgejo migration tooling. **Phase 2: Implementation (Week 2)** Tasks: - Execute migration to Forgejo. - Verify the following post-migration: - All branches and commit history - Working scripts & tag mapping functionality - Koji workflows not broken by URL changes - Update references in Koji-related SOPs and scripts. - Close Pagure repository and replace with README redirect. **Acceptance Criteria** - Repository migrated with no data loss. - Koji continues to correctly reference tag → distrepo mappings. - All tooling updated to use Forgejo URLs. - Pagure repository disabled and cleaned.

jnsamyak commented

2025-11-18 11:36:55 +00:00

Author

Owner

Forgot to add one item, please also make sure to look out for the mailing list if connected, always make sure to send out an annoucment for this before moving, once you start working on it, make sure to send out "when" it will be moved so community knows about it.

jnsamyak added this to the Fedora Releng Sprint 6 project

2025-12-01 12:20:40 +00:00

patrikp was assigned by jnsamyak

2025-12-01 12:20:46 +00:00

patrikp commented

2025-12-09 12:29:31 +00:00

Member

It seems that this is now integrated directly in Koji as a plugin, introduced by this commit [1] and promptly removed from Ansible in this commit [2].

My conclusion is that this repo is no longer needed, there is no need to migrate it, I think the best way to handle it would be to set it in read-only mode on Pagure and put a few words in the description.

[1] https://pagure.io/koji/c/7785be7758244016c860a84fa609acc6efb34eaf?branch=master
[2] https://pagure.io/fedora-infra/ansible/c/265d40b4f25157da79612fbdae3a4a90232c225f

It seems that this is now integrated directly in Koji as a plugin, introduced by this commit [1] and promptly removed from Ansible in this commit [2]. My conclusion is that this repo is no longer needed, there is no need to migrate it, I think the best way to handle it would be to set it in read-only mode on Pagure and put a few words in the description. [1] https://pagure.io/koji/c/7785be7758244016c860a84fa609acc6efb34eaf?branch=master [2] https://pagure.io/fedora-infra/ansible/c/265d40b4f25157da79612fbdae3a4a90232c225f

patrikp commented

2025-12-09 14:01:02 +00:00

Member

Repository is now in read-only mode and I made some changes to the README.

https://pagure.io/releng/tag2distrepo/pull-request/10

Repository is now in read-only mode and I made some changes to the README. https://pagure.io/releng/tag2distrepo/pull-request/10

patrikp closed this issue

2025-12-09 14:01:02 +00:00

jnsamyak reopened this issue

2025-12-10 14:49:33 +00:00

jnsamyak added

and removed

labels

2025-12-15 12:20:01 +00:00

patrikp commented

2025-12-15 16:03:30 +00:00

Member

I sent out an e-mail to devel-announce, devel and test-announce mailing list with my findings and the decision NOT to migrate it, and asking people to chime in here if they disagree.

If nobody replies within the foreseeable future I reckon we can close this.

I sent out an e-mail to `devel-announce`, `devel` and `test-announce` mailing list with my findings and the decision NOT to migrate it, and asking people to chime in here if they disagree. If nobody replies within the foreseeable future I reckon we can close this.

jnsamyak closed this issue

2025-12-17 10:07:33 +00:00

ngompa commented

2025-12-17 10:17:05 +00:00

Member

I did reply on list, I'd like these things migrated as archived repos.

patrikp reopened this issue

2026-01-12 08:41:48 +00:00

patrikp commented

2026-01-26 09:48:25 +00:00

Member

@ngompa This is supposed to be brought up in a FESCo meeting so that a decision may be reached about whether to migrate these repos for archival purposes or not.