openSUSE Developer/Maintainer/Member/Whatever.
I do things with openSUSE. Not that I’m particularly good at any of them =P
Well none of that sounds like sketchy behavior on the part of the Management Company.
Not at all.
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.
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
Bah. This is just a piece of clickbait nonsense, or somebody trying to be edgy. I’m actually mildly offended by their “review” of “On the Road”. Just makes me think that they probably haven’t ever read anything other than somebody elses review of it.
Well, RIP Simon & Schuster. I give em five years, tops.
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.
Mostly because they’re uneducated fools, that haven’t any actual idea what the hell they’re talking about.
Unless you’re pulling sources, and building everything yourself, everything you get from most major distributions is “pre-compiled”.
People hate anything new, they fear change, and they like drama, that’s all it is.
Fedora Silverblue or openSUSE Aeon, I’d probably say.
The dsektop environment really doesn’t have anything to do with it. That’s up to the video drivers and display server, be it X11 or Wayland. I haven’t any idea which desktop might offer you the best tools for configuring those things though. Just as a rough guess, I’d guess KDE Plasma, perhaps XFCE?
Packman is generally stable, and the only way to get the patent encumbered codecs for full AudioVideo decoding for Leap or Tumbleweed.
I’d probably drop openSUSE Tumbleweed with LXQt on it. But that’s my preference for low-spec machines. There’s any number of distros with “lightweight” GUI’s that you can use. XFCE/MATE/LXQt probably being the ones that will give you the least headaches.
I have no idea who signs his paychecks, but no, none of the announcement about the RHEL Sources affects Fedora in any way, unless Nobara is pulling sources from RHEL (which it isn’t) this doesn’t affect it at all. Nobara isn’t an official Fedora, or RedHat product or project.
No, nothing RedHat is doing affects Nobara. Nobara is based on Fedora, which is upstream of RedHat. Nothing is changing.
This is nice for Oracle to say. That being said, Oracle are not “The Good Guys™” and never have been. They might be legitimately honest about Oracle Linux and their commitment to being open and free, but they’re horrible about so many other things, and always have been.
Honestly, I wouldn’t make any specific recommendation. Because when you do, you instantly become most peoples personal support technician, when they can’t sort something out.
I’d probably make the general suggestions of Fedora/Silverblue/Kinoite, openSUSE Tumbleweed/Aeon/Kalpa, and maybe Pop!_OS if somebody put a gun to my head. But no recommendations.
That’s XMMP different thing =P
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 runningzypper 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.