Yes, unfortunately I’ve gotten no response from Dacentec regarding this. Unless there is any particular reason not to, I’ll remove the mirror from the list this week. That leaves us with only a single mirror in North America, and two in South America. I’ll reach out to a handful of potential providers and see what happens.
The mirror has been removed from the list due to remaining unsynchronized despite a reply from their customer support indicating that their mirror administrator(s) will be notified. A rebuild of
core/pacman-mirrorlist is pending.
Updating this reply as of 2018-12-15. The last release of Chakra to date was made on 2017-09-08.
On 2017-09-24, the Dacentec mirror was removed from our mirror list due to remaining unsynchronized for an extended period of time, as noted above.
This means that new installations may have the unsynchronized Dacentec mirror at the top of their
Server = http://mirror.dacentec.com/chakra/$repo/x86_64
If you do, remove it from your list and use a different mirror, followed by running
pacman -Syu to synchronize and upgrade your system.
View the mirror status page to learn the current status of all known mirrors.
On 2018-12-23 I set this as a global notice on this website:
Did you install Chakra recently and can’t get the latest updates? Read this before posting!
It should be displayed in a light blue rectangle at the top of every page, to inform any new users of the issue. The global notice will be removed upon the next #release.
As of 2019-02-17, the global notice set on community.chakralinux.org is now the following to inform users of this issue:
Did you install Chakra recently and/or can't get any updates dated later than December 2017, leaving you stuck with e.g. Linux 4.13.11 and Plasma 5.11.4? Read <a href="https://community.chakralinux.org/t/u-s-mirrors-out-of-sync/6488/5?u=totte">this</a> before posting - manual intervention is needed!
We are currently experiencing issues when logging in to this website. See <a href="https://code.chakralinux.org/websites/www.chakralinux.org/issues/19">this report</a> for more information.
Please see the following two issues for more information: