News draft: Cleaning up old repositories
Hey all, in an earlier thread [0], I proposed cleaning up the unused repos from repos.archlinux.org. They've become unused and stagnant after the git migration almost two years ago. We kept them around so it wouldn't break setups of users that tried to get the repository sync databases with an outdated pacman.conf. The old repos are safe to remove. Originally I had planned to just remove them and leave it at that. However, some people mentioned that it might still confuse users who haven't updated their pacman.conf in a long time. In order to inform those users there should be a news post. [0] https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.or... --- # Cleaning up old repositories Around two years ago, we've merged the [community] repository into [extra] as part of the git migration. In order to not break user setups, we kept these repositories around in an unused and empty state. We're going to clean up these old repositories on *2025-03-01*. On systems where `/etc/pacman.conf` still references the old `[community]` repository, `pacman -Sy` will return an error on trying to sync repository metadata. The following deprecated repositories will be removed: `[community], `[community-testing]`, `[testing]`, `[testing-debug]`, `[staging]`, `[staging-debug]`. Please make sure to remove all use of the aforementioned repositories from your `/etc/pacman.conf`! --- Cheers, Sven
On 2/14/25 6:49 PM, Sven-Hendrik Haase wrote:
Hey all,
Yo Sven,
in an earlier thread [0], I proposed cleaning up the unused repos from repos.archlinux.org. They've become unused and stagnant after the git migration almost two years ago. We kept them around so it wouldn't break setups of users that tried to get the repository sync databases with an outdated pacman.conf. The old repos are safe to remove. Originally I had planned to just remove them and leave it at that. However, some people mentioned that it might still confuse users who haven't updated their pacman.conf in a long time. In order to inform those users there should be a news post.
[0] https://lists.archlinux.org/archives/list/arch-dev- public@lists.archlinux.org/thread/OWHVWRBOUDCW7BUQ2DLCENJ6QRPCTGQJ/
Thanks for taking care of this! Tiny suggestions below.
--- # Cleaning up old repositories
Around two years ago, we've merged the [community] repository into [extra] as part of the git migration. In order to not break user setups, we kept these repositories around in an unused and empty state. We're going to clean up these old repositories on *2025-03-01*.
Maybe link people to the related news, which already mentioned the merge of the [community] repo into [extra] (and the related `/etc/pacman.conf.pacnew`)?: "Around two years ago, we've merged the [community] repository into [extra] as part of the [git migration](https://archlinux.org/news/git-migration-completed/)"
On systems where `/etc/pacman.conf` still references the old `[community]` repository, `pacman -Sy` will return an error on trying to sync repository metadata.
The following deprecated repositories will be removed: `[community], `[community-testing]`, `[testing]`, `[testing-debug]`, `[staging]`, `[staging-debug]`.
Please make sure to remove all use of the aforementioned repositories from your `/etc/pacman.conf`!
Maybe a good occasion to remind that a pacnew was shipped for that (and that people should *not* ignore them :P): "Please make sure to remove all use of the aforementioned repositories from your `/etc/pacman.conf` (for which a pacnew was shipped with pacman>=6.0.2-7)!" Just details though, looks good to me overall! :)
---
Cheers, Sven
-- Regards, Robin Candau / Antiz
On 14.02.25 19:11, Robin Candau wrote:
On 2/14/25 6:49 PM, Sven-Hendrik Haase wrote:
Hey all,
Yo Sven,
in an earlier thread [0], I proposed cleaning up the unused repos from repos.archlinux.org. They've become unused and stagnant after the git migration almost two years ago. We kept them around so it wouldn't break setups of users that tried to get the repository sync databases with an outdated pacman.conf. The old repos are safe to remove. Originally I had planned to just remove them and leave it at that. However, some people mentioned that it might still confuse users who haven't updated their pacman.conf in a long time. In order to inform those users there should be a news post.
[0] https://lists.archlinux.org/archives/list/arch-dev- public@lists.archlinux.org/thread/OWHVWRBOUDCW7BUQ2DLCENJ6QRPCTGQJ/
Thanks for taking care of this! Tiny suggestions below.
--- # Cleaning up old repositories
Around two years ago, we've merged the [community] repository into [extra] as part of the git migration. In order to not break user setups, we kept these repositories around in an unused and empty state. We're going to clean up these old repositories on *2025-03-01*.
Maybe link people to the related news, which already mentioned the merge of the [community] repo into [extra] (and the related `/etc/ pacman.conf.pacnew`)?:
"Around two years ago, we've merged the [community] repository into [extra] as part of the [git migration](https://archlinux.org/news/git- migration-completed/)"
On systems where `/etc/pacman.conf` still references the old `[community]` repository, `pacman -Sy` will return an error on trying to sync repository metadata.
The following deprecated repositories will be removed: `[community], `[community-testing]`, `[testing]`, `[testing-debug]`, `[staging]`, `[staging-debug]`.
Please make sure to remove all use of the aforementioned repositories from your `/etc/pacman.conf`!
Maybe a good occasion to remind that a pacnew was shipped for that (and that people should *not* ignore them :P):
"Please make sure to remove all use of the aforementioned repositories from your `/etc/pacman.conf` (for which a pacnew was shipped with pacman>=6.0.2-7)!"
Just details though, looks good to me overall! :)
---
Cheers, Sven
Thanks, I updated my draft with your feedback, fixed some formatting, and sent it off.
participants (2)
-
Robin Candau
-
Sven-Hendrik Haase