[setup][upgrade] Use Arch Linux archive

[LukeShortCloud]

For a more stable experience. This will help make sure the first-time setup and upgrade processes work as expected. Otherwise, they will break after a few months of Arch Linux upstream updates.

https://archive.archlinux.org/repos/

[LukeShortCloud]

There are about 40 packages that could potentially be installed during the first-time setup.

[LukeShortCloud]

https://archive.archlinux.org/repos/

[LukeShortCloud]

We cannot implement this until this upstream bug is fixed: #802

[LukeShortCloud]

For Manjaro, there is this repository but (1) it does not have time stamped repositories only individual packages and (2) it only keeps the last 10 packages.

https://unix.stackexchange.com/questions/746362/manjaro-equivalent-for-the-arch-linux-archive-repository
https://manjaro.tuxboy.eu/

[GuestSneezeOSDev]

if manjaro repositories don't work you could use endeavor os repository

[LukeShortCloud]

Hey @GuestSneezeOSDev , there are two large repositories we use for winesapOS outside of Arch Linux:

• Chaotic AUR = This contains thousands of pre-built AUR packages.
  • https://aur.chaotic.cx/
• winesapOS = We maintain this and have automated builds that get pushed out on the 15th of every month. If you're interested in how any of that works, here are all of the relevant links:
  • https://github.com/LukeShortCloud/winesapOS/tree/4.1.0-beta.0?tab=readme-ov-file#winesapos-repository
  • https://github.com/LukeShortCloud/winesapOS/blob/4.1.0-beta.0/CONTRIBUTING.md#build-packages-for-winesapos-repository
  • https://github.com/LukeShortCloud/winesapOS/blob/4.1.0-beta.0/scripts/repo/winesapos-build-repo.sh
  • https://github.com/LukeShortCloud/winesapOS/blob/4.1.0-beta.0/.github/workflows/repo-testing.yml

Thanks for linking the EndeavourOS repository! I had a quick look at it. We already provide some of those packages and don't need the rest.

---

This GitHub Issue is specifically to track using old/archived packages. Basically, we can pin Arch Linux to a specific date to guarantee that builds are reproducible. One problem I see a lot is that users will go through the first-time setup and some packages will fail to install due to upstream changes (for example: package conflicts, new dependencies, etc.). I've seen this problem happen as soon as 1 week after a new stable winesapOS release.

winesapOS supports builds based on Arch Linux and Manjaro. I recently added an additional GitHub Actions workflow for Manjaro which previously only received manual testing. You can find that at the top of our README.md file today. From over the years, I've found the Manjaro builds are much more stable than Arch Linux. However, in relation to this exact GitHub Issue, Arch Linux provides an official archive and Manjaro does not which is disappointing.