• 0 Posts
  • 5 Comments
Joined 3 months ago
cake
Cake day: June 6th, 2025

help-circle

  • reflector uses https://archlinux.org/mirrors/status/json/ to get mirror status info, and caches it under ~/.cache/Reflector/. So as long as that end-point works, reflector should work.

    I just grabbed a copy and pasted it at http://0x0.st/Ki3Y.json.

    Anyone can grab that JSON data and use file:// URLs so they are never out. e.g.

    curl -L https://archlinux.org/mirrors/status/json/ > /tmp/mirror_status.json
    # or if down, use pasted json
    curl -L http://0x0.st/Ki3Y.json > /tmp/mirror_status.json
    # and then
    reflector --url file:///tmp/mirror_status.json ...
    

    But, as you noted, this has been mostly a nothing-burger from a user perspective anyway. Other than the homepage being unavailable on occasion, everything else has been mostly available just fine as you can see from https://status.archlinux.org/.

    I didn’t notice https://gitlab.archlinux.org/ going down either.


    BTW, and as a general rule of thumb, NEVER take specific technical advice from these editors. They don’t actually know much, and this is me trying to be nice.

    Take for example:

    For AUR disruptions, it’s a bit of a pain if you’re not a regular git user, but you cloned packages directly from the GitHub Arch Linux mirror. To do this, use the command:

    See that link ;) At least he got the command below it correctly, somehow.


  • You are in a thread where a user is having a problem because of the push for flatpaks, and because of some distros like Fedora crippling their packages and providing objectively worse alternatives on purpose (because they don’t want to risk RH IBM getting sued). If the user was using some sane community distro like Arch, the user would have never come to realize that such unnecessary issues even exist.

    As for flatpak hate specifically, see my ramblings here.