infra/tickets

Fork 1

Obsolete fedora-docs-l10n repositories in Pagure #13428

New issue

Closed

opened 2026-06-22 16:41:01 +00:00 by rffontenelle · 8 comments

rffontenelle commented

2026-06-22 16:41:01 +00:00

Description of request

The localization team migrated Pagure fedora-docs-l10n repositories to Forge (localization-docs), so we would like to have the repositories under https://pagure.io/projects/fedora-docs-l10n/* removed. Archiving is an acceptable alternative.

Can sysadmins do this in batch?

### Description of request The localization team migrated Pagure [fedora-docs-l10n](https://pagure.io/projects/fedora-docs-l10n/*) repositories to Forge ([localization-docs](https://forge.fedoraproject.org/localization-docs/project)), so we would like to have the repositories under https://pagure.io/projects/fedora-docs-l10n/* removed. Archiving is an acceptable alternative. Can sysadmins do this in batch?

rffontenelle referenced this issue from localization/tickets

2026-06-22 16:43:30 +00:00

Docs localization migration from pagure.io to forge.fedoraproject.org #52

smoliicek added the

points

Priority

Low

labels

2026-06-22 19:15:21 +00:00

kevin commented

2026-06-22 21:35:39 +00:00

Owner

Yes, we can delete them in mass if you so desire... but wouldn't it be nicer to keep them and just mark them read-only ?
That way existing old links go there and could see that the repos moved?

Yes, we can delete them in mass if you so desire... but wouldn't it be nicer to keep them and just mark them read-only ? That way existing old links go there and could see that the repos moved?

rffontenelle commented

2026-06-25 23:13:05 +00:00

Author

Are you able to mark them all as read-only? If yes, then feel free to do it?

I was considering to add note of the new repository + archive manually each one, but I feel that would be an unnecessary work considering pagure may sunset soon.

Are you able to mark them all as read-only? If yes, then feel free to do it? I was considering to add note of the new repository + archive manually each one, but I feel that would be an unnecessary work considering pagure may sunset soon.

zlopez commented

2026-06-26 12:02:26 +00:00

Owner

That is exactly what we did, when moving over our repositories to forge.fedoraproject.org. Just disable pull requests mark them as read only and add note to README pointing to new repository.

The pagure will be in read-only mode for some time after sunset, so it's good to point people to new place.

That is exactly what we did, when moving over our repositories to forge.fedoraproject.org. Just disable pull requests mark them as read only and add note to README pointing to new repository. The pagure will be in read-only mode for some time after sunset, so it's good to point people to new place.

kevin commented

2026-06-26 17:09:23 +00:00

Owner

Do note there's not a global 'read-only' in pagure, and also pagure has no concept of 'archiving' a project.
You can set the issue tracker to read-only.
You can set 'commits require a pull request'.

IMHO, I'd just suggest updating README and possibly set issue trackers read-only. I don't think we have any way to do that on a bunch of repos off hand.

I think the current plan for the end of july deadline is that pagure will be moved to be just a static set of pages, so read-only in the sense that the application isn't there anymore, just the static data for historical purposes. So you could also just leave things as is and they will be forced read-only in that way at the end of july.

Do note there's not a global 'read-only' in pagure, and also pagure has no concept of 'archiving' a project. You can set the issue tracker to read-only. You can set 'commits require a pull request'. IMHO, I'd just suggest updating README and possibly set issue trackers read-only. I don't think we have any way to do that on a bunch of repos off hand. I think the current plan for the end of july deadline is that pagure will be moved to be just a static set of pages, so read-only in the sense that the application isn't there anymore, just the static data for historical purposes. So you could also just leave things as is and they will be forced read-only in that way at the end of july.

rffontenelle commented

2026-06-26 17:18:10 +00:00

Author

How can I have access to Pagure fedora-docs-l10n group? I was granted access to the respective repositories in Forge during the migration, but I still don't have in Pagure to update the READMEs with the URL of the migrated repository.

How can I have access to Pagure [fedora-docs-l10n](https://pagure.io/group/fedora-docs-l10n) group? I was granted access to the respective repositories in Forge during the migration, but I still don't have in Pagure to update the READMEs with the URL of the migrated repository.

kevin commented

2026-06-26 17:36:50 +00:00

Owner

@jibecfed should be able to add you to the group. If thats not workable, we can probibly add you via some admin path...