It feels pretty good, as well as looks pretty good. YaST and the YaST installer have been basically in maintenance mode for a long time, without any active development for a number of years now, and it’s certainly time to move on.

Well, there’s already a discussion on the mailing lists, and while I can’t speak for the project, (nor am I an attorney, but I did stay at a Holiday Inn Express last night), the “Main” openSUSE Project logo is a registered trademark of SUSE Software Solutions Germany GmbH, so it’s highly unlikely that it’s going to change.

Well, I can say, with all certainty, that while I appreciate the submissions, and the community making themselves heard, that isn’t the new Kalpa logo.

Yes, Printer setup on openSUSE is still a clusterfuck, for reasons. You’re best off in openSUSE KDE to just point your webbrowser at http://localhost:631 and log directly into CUPS and setup your printers that way.

If you want all your web video and whatnot to work, you need to install the codecs from Packman, in their entirety, or use a flatpak’d web browser. openSUSE won’t ship patent encumbered codecs from the official repositories.

Unless you really know what you’re doing, with Leap, or Tumbleweed, stick with the OSS and non-OSS repos provided. They are the ones that have been through the openQA process, and are officially “supported”. If you enable a bunch of home: devel: or other repositories, just assume that they’re unstable, and use at your own risk. If you’re looking at a repository on OBS, and don’t see openSUSE_Tumbleweed as one of the build targets, then forcing the install with a Leap or SLE package, may, or may not break things.

Regarding zypper ref and autorefresh, I can’t recall exactly, but there is the chance that just running zypper dup and hoping that it refreshes everything on it’s own, with non-standard repositories may fail, which can lead to some weird edgecases.

Just in general, you’re going to want to run zypper ref && zypper dup (not the other way round) As far as YaST being targetted more at Leap than Tumbleweed, you’re exactly right. And there’s a reason that we don’t ship it with newer flavours of the distribution.

Well none of that sounds like sketchy behavior on the part of the Management Company.

Not at all.

Nobody panic.

https://queer.party/@Lyude/111089178374415532

Correct, SUSE, the corporation is no longer providing a traditional linux distribution, after the SLE-15 EOL.

openSUSE, which is a community project, and not controlled by SUSE, is currently debating as to whether we have the contributors interested in doing so, and in sufficient numbers, to continue to provide a traditional point release distribution.

Tumbleweed (the rolling release) is not going anywhere. The community has not yet decided if the interest and manpower is there to use the ALP sources provided by SUSE to create A) A traditional linux distribution, akin to what Leap currently is, B) a “Slowroll” version of Tumbleweed, that has a slower release cycle, or C) Nothing at all, because there isn’t the community there to support the development of it.

SUSE != openSUSE

That is indeed the big question, if there’s nobody willing to put in the work, then there’s nothing to release.

Maintaining something like Leap, with the contributor base that has historically existed, isn’t sustainable, long term, especially when the upstream is going in a different direction.

Then yes, there are all kinds of things in the repositories that are going to annoy you.

What “wishy-washy” policy are you on about?

I certainly don’t care what distribution you use, but Tumbleweed, aside from the occasional glitch on single updates, is stable as hell, and has been for a long time. It’s hardly “bleeding edge” and on Par with Fedora, for instance, as far as stability is concerned. I’d say a bit more stable than the Arch derivatives, due to openQA.

Its not perfect by any means, but no distribution is.

This pretty much backs up what I’ve been seeing. Everybody wants to use Leap, nobody wants to work on it.

The change listed in the upstream bug has been in Tumbleweed for months, I see you’re running Tumbleweed, So this is obviously a bug. Please file a bug at bugzilla.opensuse.org, as there currently isn’t one existing. (I’m not encountering this bug, just saying)

The change shown in the upstream bug has been made in the openSUSE Tumbleweed Packages, months ago. Are you using Leap, or Tumbleweed?

edit:
I actually read the whole post. Since you’re on Tumbleweed, this is indeed a bug, please file one at bugzilla.opensuse.org

I don’t care about beeper one way or another, but that bloody image with the post, it needs to die in a fire.

I will never claim they are authentic, or even great, but I will destroy the 2 for a buck tacos.

Packman is generally stable, and the only way to get the patent encumbered codecs for full AudioVideo decoding for Leap or Tumbleweed.

That’s XMMP different thing =P

It’s still around. I’m using it right now, in fact. Makes for a pretty damn good phone service as well, in conjunction with JMP

Uh. You just described Aeon and Kalpa.