Bwaaahahahaha Fake News! -_-"
I'm trying to scare Eric...
Pfffffff
Oh well seriously though I must've gotten little sleep...
Yesterday I was testing the install script from my local system which still had 66-repo in pacman....
Sorry for the commotion. I do think a short News should be made on the site though. The announcement you quoted I remember but it says that it has been created, and that in some future it will get removed (with no approximation).
Existing installs will not be able to update because of the 404.
I mean it's obvious to most people what 404 means in this context but it may not be obvious why it is being thrown. Might as well be a server side fault.
I was looking at the latest news myself yesterday and couldn't find anything that says something along the lines:
"The transitioning phase from s6 to 66 has officially ended. Please remove 66-repo from your pacman.conf! As of [date] it has been removed from the obarun server and must be deleted from the configuration."
I even already used the latest ISOs when I said I was testing in VMs and they were perfectly fine lol sorry :P
As for the systemd pointer: Thank you Fungal!
I've had issues like yours before with pacman. Usually generating mirrors with
reflector helps me in that situation.
I personally like to use
# reflector --latest 50 --protocol https --sort rate --save /etc/pacman.d/mirrorlist