Hi all, We are starting the migration to Git for packaging repositories and merging [community] to [extra] to prevent a weird state being synced to the mirrors we will leave our rsync endpoint disabled until the migration is complete. Greetings, Jelle van der Waa
Hello, Just want to wish all the developers and package maintainers luck during the transition, and please don't break Arch Linux, it would be a shame :P A question I asked a few time on IRC, but I either missed the response or nobody knew is where will the repository be hosted after the migration? gitlab.archlinux.org? Good luck, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
On 19-05-2023 11:39, Polarian wrote:
Hello,
Just want to wish all the developers and package maintainers luck during the transition, and please don't break Arch Linux, it would be a shame :P
A question I asked a few time on IRC, but I either missed the response or nobody knew is where will the repository be hosted after the migration? gitlab.archlinux.org?
Do we need to change something from sync on our side? On 2023-05-19 12:38, Jelle van der Waa wrote:
Hi all,
We are starting the migration to Git for packaging repositories and merging [community] to [extra] to prevent a weird state being synced to the mirrors we will leave our rsync endpoint disabled until the migration is complete.
Greetings,
Jelle van der Waa
-- Best regards, -------------------- MangoHost Network https://mangohost.net/ | hostmaster@mangohost.net
On 19-05-2023 11:42, Support wrote:
Do we need to change something from sync on our side?
No changes will be required, the only thing you should notice is that you won't be able to rsync from rsync.archlinux.org during the migration. Regards, Jelle van der Waa
Hello, Last question, we will need to update our pacman.conf to remove [community] otherwise you will get sync error after the migration where the repository can not be found, correct? Thanks, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
Le 19/05/2023 à 11:45, Polarian a écrit :
Hello,
Last question, we will need to update our pacman.conf to remove [community] otherwise you will get sync error after the migration where the repository can not be found, correct?
Thanks, Nop, as stated in the announcement [1], the [community] repo will stay up as empty for a moment after the migration's done. So the will have to be done at some point, but not necessarily right away after the migration is over.
For what it's worth, I assume a new pacman.conf will provided as a pacnew file. [1] https://archlinux.org/news/git-migration-announcement/ -- Regards, Robin Candau / Antiz
Le 19/05/2023 à 11:51, Robin Candau a écrit :
Le 19/05/2023 à 11:45, Polarian a écrit :
Hello,
Last question, we will need to update our pacman.conf to remove [community] otherwise you will get sync error after the migration where the repository can not be found, correct?
Thanks, Nop, as stated in the announcement [1], the [community] repo will stay up as empty for a moment after the migration's done. So the will have to be done at some point, but not necessarily right away after the migration is over. So the *above *will to be done [...]*
For what it's worth, I assume a new pacman.conf will provided as a pacnew file. [...] a new pacman.conf will *be *provided as a [...]*
Monday mornings... You know how it is... :P /j -- Regards, Robin Candau / Antiz
Hey Robin,
Monday mornings... You know how it is... :P /j
You do know its Friday right? :P and yes I forgot it was mentioned within the announcement by Jelle. I think you need to sync with NTP, your clock is 4 days desynchronised :P Have a good day, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev
participants (4)
-
Jelle van der Waa
-
Polarian
-
Robin Candau
-
Support