Fedora

openSUSE Kernel cmdline INSECURE=1 to boot test ISO’s without signed repositories on the image Build ProductBuilder images outside of openSUSE:Factory Grab the following packages 000product installation-images skelcd-control-* Example repository configuration for building: <project name="home:sfalken:kalpa:images"> <title>Kalpa Images Devel Project</title> <description/> <person userid="sfalken" role="bugowner"/> <person userid="sfalken" role="maintainer"/> <build> <disable arch="i586"/> <disable arch="i586" repository="openSUSE_Tumbleweed"/> </build> <publish> <disable/> <enable repository="product"/> <enable repository="images"/> <enable arch="x86_64" repository="openSUSE_Factory"/> <enable arch="x86_64"/> <disable arch="i586" repository="openSUSE_Tumbleweed"/> <disable arch="i586" repository="images"/> </publish> <useforbuild> <disable arch="i586"/> <disable arch="i586" repository="openSUSE_Tumbleweed"/> </useforbuild> <repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Factory" repository="snapshot"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="images"> <path project="home:sfalken:kalpa:images" repository="openSUSE_Tumbleweed"/> <path project="openSUSE:Factory" repository="standard"/> <path project="openSUSE:Factory" repository="snapshot"/> <arch>x86_64</arch> </repository> </project> Grab prjconf from openSUSE:Factory ...

So you want to do fedora packaging in a Distrobox? It takes a couple of extra steps, particularly if you want to be able to do mockbuilds: $ distrobox create -i quay.io/fedora/fedora:latest -n fpkg --root --init --additional-packages 'systemd vim zsh fedora-packager copr-cli' If you happen to be on an openSUSE based system, such as MicroOS, Aeon, or Kalpa (and probably Leap, Tumbleweed, or anything else), you’ll need to do the following: ...

Pursuant to the presentation We’re all grown up: openSUSE is not SUSE (and it’s tim our name reflected that.), given by Richard Brown and Robert Sirchia at openSUSE Conference 2024, it is clear that the openSUSE Community has some thinking to do and questions to answer, about our Project Name, our Governance, and our very future. Discussion of this has largely been focused and documented on the openSUSE Project Mailing List and other adjunct conversations are happening in other threads, and in places like Matrix and the Forums. ...