Arch Linux: Git migration completed(archlinux.org) |
Arch Linux: Git migration completed(archlinux.org) |
I think my draft is more detailed: https://wiki.archlinux.org/title/User:Foxboron/GitMigration
Runbook for the migration can be found here: https://md.archlinux.org/utjjQ-bQTsipIKntPrpf8g?both
pacman-6.0.2-6-x86_64.pkg.tar.zst 18-Mar-2023 15:24 944412
pacman-6.0.2-6-x86_64.pkg.tar.zst.sig 18-Mar-2023 15:24 119
pacman-6.0.2-7-x86_64.pkg.tar.zst 20-May-2023 14:17 56
pacman-6.0.2-7-x86_64.pkg.tar.zst.sig 20-May-2023 14:17 60I got some issues with all my mirrors: the size of the last pacman package is very (too) small (60 vs 944412 for previous version). e.g. https://archlinux.uk.mirror.allworldit.com/archlinux/core/os...
I picked a mirror that definitely has the 6.0.2-7 version on it[0], yet Pacman can't find it.
Does the server's core.db have to update before the new version is available? Because that one is dated 18-May-2023 05:21.
https://archlinux.org/mirrors/status
still seem unsynced on my arch systems.
The btrfs raid setup is standardized across all our infra and can be found on ansible.
https://gitlab.archlinux.org/archlinux/infrastructure/-/blob...
https://gitlab.archlinux.org/archlinux/infrastructure/-/blob...
From what I can tell it's been working fine and behaves nicely with failing disks.
I would try and generate a new mirrorlist for your locale: https://archlinux.org/mirrorlist/
Github usage predates the Gitlab instance and some projects haven't been migrated. We also keep some repositories on Github as a secondary mirror.
We've also had some performance issues on Gitlab for `svntogit` repository because of weird branch structures. However this repo is not deprecated so it doesn't matter anymore.