Sync protections on our main repository

[ikeycode]

Hello all!

In preparation for our yuge upcoming release, we've added some sync protections on the binary repository.
Basically, users should stay on the repo they are on now, and do nothing.. :)

Our active infrastructure works against https://packages.serpentos.com, which is also a staging area for the upcoming versioned repositories support. Until ready, we will sync the repository to the existing location for current users (https://dev.serpentos.com)

In a future update to moss, we will handle the transition from the dev domain to packages automatically for you, also introducing the versioned repository/release support. Until that point, the new split has allowed us to control when updates from the automatic builds reach client systems, affording a level of protection against borkage =)

Users

Seriously, your repo config is fine and we've actively taken this step to permit stability, explicit syncs, and enable the upcoming versioned repository support. The build status page (ent builds or https://dash.serpentos.com) will reflect the status of true volatile, and will be synced back for daily users when deemed stable enough.

Packagers

Please re-create your repo configuration in boulder. Check boulder profile list and remove any that refer to dev.serpentos.com, as it is not the live build target. Typically this is the local-x86_64 profile, not the one we ship in packaging.

rm ~/.config/boulder/profile.d/local-x86_64.yaml
boulder profile add local-x86_64 --repo name=volatile,uri=https://packages.serpentos.com/volatile/x86_64/stone.index,priority=0 --repo name=local,uri=file://${HOME}/.cache/local_repo/x86_64/stone.index,priority=10

Note the fallback built-in volatile profile will be fixed by updating to the latest boulder package (synced today)

After, your profile configuration should look like this: