Test repo for the Atomic Desktops
d34e2ee500
We need to make it easier to update the bootloader on these variants because unlike on traditional systems, it's not updated automatically with the rest of the system. Add bootupd for that. This would allow fixing issues like: - https://github.com/coreos/rpm-ostree/issues/3715 - https://github.com/fedora-silverblue/issue-tracker/issues/120#issuecomment-979268679 It won't be enabled by default and as mentioned in that comment requires work in Anaconda to be seamless. But at least with this users should be able to adopt and update: https://github.com/coreos/bootupd/blob/main/README-design.md See also the tracker issue where we did this for Fedora CoreOS: https://github.com/coreos/fedora-coreos-tracker/issues/510 |
||
---|---|---|
comps-sync-exclude-list.yml | ||
comps-sync.py | ||
config.ini | ||
deepin-desktop-pkgs.yaml | ||
fedora-37-updates.repo | ||
fedora-37.repo | ||
fedora-base.yaml | ||
fedora-common-ostree-pkgs.yaml | ||
fedora-common-ostree.yaml | ||
fedora-deepin.yaml | ||
fedora-kinoite.yaml | ||
fedora-lxqt.yaml | ||
fedora-mate.yaml | ||
fedora-pantheon.yaml | ||
fedora-rawhide.repo | ||
fedora-silverblue.yaml | ||
fedora-vauxite.yaml | ||
gnome-desktop-pkgs.yaml | ||
group | ||
kde-desktop-pkgs.yaml | ||
LICENSE | ||
lxqt-desktop-pkgs.yaml | ||
mate-desktop-pkgs.yaml | ||
pantheon-desktop-pkgs.yaml | ||
passwd | ||
README.md | ||
xfce-desktop-pkgs.yaml |
Manifests for rpm-ostree based Fedora variants
This is the configuration needed to create rpm-ostree based variants of Fedora. Each variant is described in a YAML treefile which is then used by rpm-ostree to compose an ostree commit with the package requested.
In the Fedora infrastructure, this happens via pungi with Lorax (templates).
Fedora Silverblue
- Website: https://silverblue.fedoraproject.org/ (sources)
- Documentation: https://docs.fedoraproject.org/en-US/fedora-silverblue/ (sources)
- Issue tracker: https://github.com/fedora-silverblue/issue-tracker/issues
Fedora Kinoite
- Website: https://kinoite.fedoraproject.org/ (sources)
- Documentation: https://docs.fedoraproject.org/en-US/fedora-kinoite/ (sources)
- Issue tracker: https://pagure.io/fedora-kde/SIG/issues
Building
Instructions to perform a local build of Silverblue:
# Clone the config
git clone https://pagure.io/workstation-ostree-config && cd workstation-ostree-config
# Prepare repo & cache
mkdir -p repo cache && ostree --repo=repo init --mode=archive
# Build (compose) the variant of your choice
sudo rpm-ostree compose tree --repo=repo --cachedir=cache fedora-silverblue.yaml
# Update summary file
ostree summary --repo=repo --update
Testing
Instructions to test the resulting build:
- First, serve the ostree repo using an HTTP server.
- Then, on an already installed Silverblue system:
# Add an ostree remote
sudo ostree remote add testremote http://<IP_ADDRESS>/repo
# Pin the currently deployed (and probably working) version
sudo ostree admin pin 0
# List refs from variant remote
sudo ostree remote refs testremote
# Switch to your variant
sudo rpm-ostree rebase testremote:fedora/35/x86_64/silverblue
Historical references
Building and testing instructions:
- https://dustymabe.com/2017/10/05/setting-up-an-atomic-host-build-server/
- https://dustymabe.com/2017/08/08/how-do-we-create-ostree-repos-and-artifacts-in-fedora/
- https://www.projectatomic.io/blog/2017/12/compose-custom-ostree/
- https://www.projectatomic.io/docs/compose-your-own-tree/
For some background, see:
- https://fedoraproject.org/wiki/Workstation/AtomicWorkstation
- https://fedoraproject.org/wiki/Changes/WorkstationOstree
- https://fedoraproject.org/wiki/Changes/Silverblue
- https://fedoraproject.org/wiki/Changes/Fedora_Kinoite
Note also this repo obsoletes https://pagure.io/atomic-ws