OpenSUSE

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: ...

We currently have a breakage in Tumbleweed with the Budgie Desktop. This is a temporary workaround, so you can stay up and running, and still get updates. This is just a repackaging, from scratch, back to the 10.9.2 stable branch of the Budgie Desktop Existing Installations sudo zypper ar http://download.opensuse.org/repositories/home:/sfalken:/BuddiesofBudgie/openSUSE_Tumbleweed home:sfalken:BuddiesofBudgie sudo zypper ref sudo zypper dup --from home:sfalken:BuddiesofBudgie When zypper asks you to resolve conflicts, you’re going to want to select option 1 in each case, which will switch your packages from openSUSE:Tumbleweed to home:sfalken:BuddiesofBudgie ...

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. ...

openSUSE {Aeon,Kalpa,MicroOS}? So I was made aware of a thread on reddit where it’s brought up that folks don’t understand the relationship between openSUSE MicroOS, openSUSE Aeon, and openSUSE Kalpa. This blog post will attempt to clear up some misunderstandings and misconceptions about the relationship between the three “Distributions”. Timeline MicroOS In 2019, openSUSE released MicroOS to the community, which is a minimalist, “immutable” linux distribution, that is intended to do “one job”, deploying containers, or other workloads, while staying out of your way. ...

What prompted this blog post? So if like myself, you’ve got a large number of openSUSE machines on your network, it can be advantageous to run a local mirror, for updates. And it just so happens that one of the openSUSE developers, firstyear, has put together a nifty caching server that really speeds all this up, the proxy-cache itself isn’t the point of this blog post, but if you want to know more, you can find it at: opensuse-proxy-cache ...