forked from suse-edge/Factory
Rhys Oxenham
27aa096244
Previously, the default model for aarch64 raw disk images assumes that you're deploying on Raspberry Pi, and not standard aarch64 systems. This meant that all raw disk images were built with RPi firmware, and an MBR boot record, which made it incompatible with systems that require uEFI/GPT compatibility, especially with Edge Image Builder and Metal3/CAPI deployment usage. This PR introduces the following changes: * Introduces new `Default-RPi` and `Base-RPi` profiles for compatibility with RPi users * Forces `Base` and `Base-RT` profiles to use GPT based images (not MBR) * Introduces a new `Base-RT-RPi` profile for kernel-rt on RPi (with MBR) * Removes Raspberry Pi firmware packages from anything other than RPi profiles * Modifies the `editbootinstall_rpi.sh` script to support container builds * Adds policycoreutils-python-utils to the list of packages (for semanage) See: https://bugzilla.suse.com/show_bug.cgi?id=1240619
Factory
Contains the definition of the packages built on OBS for the SUSE Edge Solution (WIP)
This repository is linked to an OBS project: https://build.opensuse.org/project/show/isv:SUSE:Edge:Factory Every directory in this repository represents a package in that OBS project, those should be synced automatically from this repository.
Testing a fork or a development branch
You can create a project in your home space in OBS, use the same prjconf as the one of "isv:SUSE:Edge:Factory", and copy the repositories part of the metadata (adjust self references). Then add a scmsync stanza to your metadata like this (adjust repository path and branch):
<scmsync>https://src.opensuse.org/suse-edge/Factory#main</scmsync>
This is done automatically for any PR filed against this repository.
Cutting a release version branch
- Do the appropriate git branch command
- Change the project path in
.obs/common.pyfile (e.g. fromisv:SUSE:Edge:Factorytoisv:SUSE:Edge:3.2) - Change the branch reference in
.obs/common.pyfile (e.g. frommainto3.2) - Commit those changes to the new branch and push the new branch
- Go take a few cups of coffee/tea/mate/... while waiting for OBS to build everything
- Once built do an
osc releaseof the project for it to be copied over in theToTestsection - Hand over to QA to test whatever is in
ToTest. (You can continue to work on the base branch if needed meanwhile)