Cleaning up old [community*] repos
Hey, The git/community-to-extra migration was almost two years ago. Back then, we left the [community] repository and friends ([community-staging], [community-testing]) in place (though empty) so that users would have an easier time migrating. They've sat there unused for a long time now and I think users have had enough time to migrate. I would like to suggest removing the empty [community] repos from repos.archlinux.org. This could break update workflows for users who haven't updated their /etc/pacman.conf in a long time but apart from that I don't expect any drawbacks. Opinions? Sven
On 2/7/25 4:11 PM, Sven-Hendrik Haase wrote:
Hey,
Hey Sven,
The git/community-to-extra migration was almost two years ago. Back then, we left the [community] repository and friends ([community- staging], [community-testing]) in place (though empty) so that users would have an easier time migrating.
They've sat there unused for a long time now and I think users have had enough time to migrate. I would like to suggest removing the empty [community] repos from repos.archlinux.org.
Thanks for raising this. I also think two years was a reasonable amount time for people to migrate.
This could break update workflows for users who haven't updated their / etc/pacman.conf in a long time but apart from that I don't expect any drawbacks.
There's, hopefully, not a lot of people still having [community] (and friends) referenced in their /etc/pacman.conf anymore 0:)
Opinions?
+1 on my side!
Sven
-- Regards, Robin Candau / Antiz
On 07.02.25 16:11, Sven-Hendrik Haase wrote:
Hey,
The git/community-to-extra migration was almost two years ago. Back then, we left the [community] repository and friends ([community- staging], [community-testing]) in place (though empty) so that users would have an easier time migrating.
They've sat there unused for a long time now and I think users have had enough time to migrate. I would like to suggest removing the empty [community] repos from repos.archlinux.org.
This could break update workflows for users who haven't updated their / etc/pacman.conf in a long time but apart from that I don't expect any drawbacks.
Opinions?
Sven
On that note, I would also like to nuke the other old repos: - testing (it's now extra-testing) - testing-debug (it's now extra-testing-debug) - staging (it's now extra-staging) - staging-debug (it's now extra-staging-debug)
Nuke em!
On 07.02.25 16:23, Sven-Hendrik Haase wrote:
On 07.02.25 16:11, Sven-Hendrik Haase wrote:
Hey,
The git/community-to-extra migration was almost two years ago. Back then, we left the [community] repository and friends ([community- staging], [community-testing]) in place (though empty) so that users would have an easier time migrating.
They've sat there unused for a long time now and I think users have had enough time to migrate. I would like to suggest removing the empty [community] repos from repos.archlinux.org.
This could break update workflows for users who haven't updated their / etc/pacman.conf in a long time but apart from that I don't expect any drawbacks.
Opinions?
Sven
On that note, I would also like to nuke the other old repos: - testing (it's now extra-testing) - testing-debug (it's now extra-testing-debug) - staging (it's now extra-staging) - staging-debug (it's now extra-staging-debug)
All old repos have been moved. Sven
On 2/7/25 4:11 PM, Sven-Hendrik Haase wrote:
Hey,
The git/community-to-extra migration was almost two years ago. Back then, we left the [community] repository and friends ([community- staging], [community-testing]) in place (though empty) so that users would have an easier time migrating.
They've sat there unused for a long time now and I think users have had enough time to migrate. I would like to suggest removing the empty [community] repos from repos.archlinux.org.
This could break update workflows for users who haven't updated their / etc/pacman.conf in a long time but apart from that I don't expect any drawbacks.
Opinions?
Sven
+1 for removing them, it's been a while. But after checking our previous announcements, I believe we should do a news announcement as this may lead to soft breakage. During our previous git migration announcements, we explained that the configs need to be merged and [community] is going away. But we also were quite soft in the wording and explained we keep compatibility to ease users. [0][1] Hence, I believe a small news post is justified and won't hurt. Cheers, Levente [0]: https://archlinux.org/news/git-migration-announcement/ [1]: https://archlinux.org/news/git-migration-completed/
participants (4)
-
Brett Cornwall
-
Levente Polyak
-
Robin Candau
-
Sven-Hendrik Haase