SFaulken

joined 1 year ago
 

openSUSE maintainers received notification of a supply chain attack against the “xz” compression tool and “liblzma5” library. Background Security Researcher ...

 

Hi, the next TW snapshot 20240311 contains KDE Plasma 6.0.1, Gear 24.02.0 and Frameworks 6.0.0: https://kde.org/announcements/megarelease/6/ Plasma 5 will be replaced, it is no longer part of the ……

 

Just wanted to drop there here, in case anybody finds it useful. I started doing some blogging, mostly with the intention of archiving how in the hell I've done things on Linux, in the past, so I know where to find them the next time I need to do them. There will probably be other stuff there, with time, some of it not linux related, but I'll tag the relevant stuff, so it's easier to find.

1
submitted 9 months ago* (last edited 8 months ago) by [email protected] to c/[email protected]
 

For those of you that haven't played with, or find the online documentation for containerizing your workloads to be a bit intimidating, I wrote a blog post/How To on putting together a container, and setting up the systemd services to manage it. Hope it's helpful to folks.

https://sfalken.tech/posts/2024-02-23-quick-and-dirty-podman/

 

Explore the fundamentals of RPM packaging in Episode 2 of our openSUSE Community Workshops that starts with a simple 'Hello World' program. Guided by openSUS...

 

This week, Jonathan Bennett and Dan Lynch talk with Shawn W Dunn about openSUSE Kalpa, the atomic version of openSUSE Tumbleweed, with a KDE twist. What exactly do we mean by an Atomic desktop? Is …

[–] [email protected] 1 points 9 months ago (1 children)

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.

 

In this session, we will delve into the basics of utilizing the Open Build Service (OBS) and the osc command-line tool, using a practical example of a versio...

 

The openSUSE community is pleased to announce that it will have short sessions aimed at encouraging people on how to contribute to the project. A group of vo...

 

https://etherpad.opensuse.org/p/weeklymeeting20240206
https://etherpad.opensuse.org/p/weeklymeeting20240208

Community meetings happen most Tuesdays (14:30 UTC) and Thursdays (20:00 UTC) at https://meet-test.opensuse.org/meeting (No requirement to turn on your Microphone or Camera, if you just want to observe, or participate via text.)

2
The Year of Agama (yast.opensuse.org)
 

Take a look to the Agama roadmap for 2024

 

Dear openSUSE members, The openSUSE Board Election is now closed. 199 out of 552 eligible members have cast their vote in this election. The election result is as follows: Simon Lees ……

 

So the elections are happening now (1-January-2024) if you're an openSUSE Member, please check your e-mail for your voting link.

Mine ended up in my spam folder, so keep your eyes peeled

[–] [email protected] 1 points 11 months ago (1 children)

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.

[–] [email protected] 2 points 11 months ago

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.

[–] [email protected] 7 points 1 year ago (1 children)

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.

[–] [email protected] 6 points 1 year ago

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

Not at all.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

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

[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 3 points 1 year ago

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

[–] [email protected] 3 points 1 year ago (2 children)

What "wishy-washy" policy are you on about?

[–] [email protected] 1 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

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

view more: next ›