Guide: Switch to new repo (rolling unstable) #53
Pinned
NomadicCore
started this conversation in
General
Replies: 1 comment 1 reply
-
Is it possible to switch to the new |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I have written up a short post on how to migrate over to the new repo for anyone eager to make the transition.
Scripted migration to the new unstable repository
Open a terminal emulator like GNOME terminal or similar, and run the following one-liner:
curl -fsS https://raw.githubusercontent.com/AerynOS/recipes/refs/heads/2025-05-repo-rebuild/m/moss/pkg/moss-update-repos.bash | sudo bash -
Example output:
If the automated script worked as intended, please follow the instructions in the following link to begin using our new pkgsets:
Guide: Update to new pkgsets (breaking change)
If the automated script did not work as you expected, you can find instructions for how to manually update to the new unstable repo in the section below.
Steps to manually migrate to the new unstable repository
For those of you who wish to use AerynOS without doing any packaging work, this guide will serve as a manual way for you to update your system to point to the new AerynOS CDN accelerated repo.
Step 1: Sync your system to the latest package versions available
sudo moss sync -u
If there are any updates available, press y to confirm the update and wait for the process to finish.
Step 2: Check what repos you're currently using
moss repo list
First, list what repo(s) you are currently using on your system. Depending on when you originally installed either SerpentOS or AerynOS, you will likely have one of the following repos:
If you have more than one repo, you will have added this yourself at some point, likely for packaging purposes.
Step 3: Add the new repo
sudo moss repo add unstable https://cdn.aerynos.dev/unstable/x86_64/stone.index -p 0
Some points to note:
Step 4: Validate your repo list again
moss repo list
The output you're looking for is:
If you have the correct output, you then want to sync to the repo to upgrade to the latest packages by following this guide:
Guide: Update to new pkgsets (breaking change)
Step 5: If you have multiple repos (or your repo was not called unstable)
If you want to continue packaging work, you can ignore the following steps as we have a separate guide on how to set up your repo list in our Github Discussions.
If however you do not plan on doing any packaging work and you have multiple repos (including if your original repo was not called unstable), you can remove any additional repos you have in your repo list. You will do this by using the following command:
sudo moss repo remove "name"
Replace the name with whatever the name is in your repo list
By way of example, if your original repo was called volatile, the command would be:
sudo moss repo remove volatile
Once you have removed your additional repos, make sure you follow the guide:
Guide: Update to new pkgsets (breaking change)
That should be all that there is to it. If you have any challenges or issues, please reach out with your questions under this post. Please provide the output you have from
moss repo list
to help us diagnose the issue in one go.Beta Was this translation helpful? Give feedback.
All reactions