You are not logged in.
Pages: 1
A few days ago some (crucial) packages linked against glibc 2.28 were falsely moved to [core] [extra] [community], while glibc-2.28 was still in [testing].
This resulted in all kinds of serious errors.
glibc-2.28 is now in [core], so these issues should be fixable by running
pacman -SyuI'm sorry for any caused troubles.
Offline
Pages: 1