So, saw that in 16 Yast is retired, and replaced with a couple different tools for different parts of it. I currently have a Tumbleweed install on my EliteBook that I’d like to update to the current management apps just to start using on real hardware (I do have a VM of 16 also that I’m testing). I haven’t been able to find anything that gives proper instructions about how to do this (I know usually Yast is impossible to remove), is there instructions that I’m not finding, or does this actually require a reinstall to accomplish? Thanks for any direction.
Yea, personally, I don’t understand the “change.”
The new package (software) manager is named “Myrlyn”. To me, it’s a carbon copy of the Yast Software tool. To me, it’s a name change.
The other tool is “Cockpit”. I’ve got it running in Leap 16 Alpha, obviously… and, in addition, I’ve got Cockpit installed and running in Leap 15.6
So I assume you can install it on TW. Just look up “Cockpit” in Software … I’d have to boot the laptop to remind me how I installed it on 15.6.
I’m sure @malcolmlewis explained how to install it (I seem to remember they posted a reply )
.
.
EDIT: okay, I booted my laptop … I installed Cockpit on 15.6 via the Flatpak version… using the Discover tool
@myswtest yes, the flatpak version (I install as my user) is best as it contains all the plugins etc. I have it installed on my primary desktop and can use it to manage all my systems without the need to install any cockpit components on those systems.
Now if those systems are using SELinux then I do install the setroubleshoot-server
to give some visibility of any issues.
Edit: On a side note, there is also a file browser so those that need a GUI to move files around… it’s there, no need for opening Dolphin/Nautilus/Thunar etc…
From a functional point of view it is sort of a carbon copy, but it is a standalone application with no Ruby code and no dependencies from other YaST parts, so possibly easier to maintain and with a longer life cycle if or when Ruby and YaST are phased out.
I asked about it on Reddit, and it seems that SUSE thinks YaST is outdated and not very useful.
Do not use it on TW, it has the same shortcomings as YaST in it’s current state, i.e. cannot handle dup
“Answers” from people inside openSUSE are not on reddit. Sorry to say so, but as a mod I mostly see “opinions” by consumers
You can do the equivalent of zypper dup with Myrlyn. That’s what the new users complain about…they say, going back to the 80’s?
I’ve been using Myrlyn for a while and it’s nice. It also has a read only mode that’s very handy. You can look for packages or check dependencies with more than one Myrlyn running.
I haven’t checked out Cockpit yet.
Myrlyn absolutely can handle dup. I’ve been doing it most of this year.
On the Updates Tab you have “Package Update” and “Dist-Upgrade”. Hit Dist-Upgrade and then go (Accept)!
Admitted: it’s been a while since I looked at it. Won’t use it though. Even though I spent a lot of time on comparing what Discover (and GNOME Software I suppose since both are PackageKit front-ends), I still prefer sudo zypper dup
. Shows what it is going to do.
Looking at the Leap 16.0 Beta release announcement – <openSUSE Leap 16 Enters Beta> – also available via the News feed – <openSUSE Leap 16 Enters Beta> – the following may well be interesting –
If someone is interested in the maintanece of YaST for further development and bugfixes, the source are available on github.
In other words, also for Tumbleweed, YaST may well disappear if, nobody is prepared to pick up the maintenance of the thing …
And, there’s also this statement regarding Tumbleweed on another Leap 16 issue in this Forum – <Does anyone know if OpenSUSE TW will require the x86_64-v2 architecture?>
Tumbleweed still supports ancient hardware. It is only Leap which requires v2
> ld.so --help
.
.
Subdirectories of glibc-hwcaps directories, in priority order:
x86-64-v4
x86-64-v3 (supported, searched)
x86-64-v2 (supported, searched)
>
This Leap 15.6 system supports “x86-64-v2” (and v3) but, not “x86-64-v4” …
I read about Myrlyn back in November or December 2024 and my first thought was “we’ll have that by Christmas 2029 or 2030”.
Then I read someone talking about using it. I assumed some guy was trying to figure it out and it’d take a lot of time. It turned out that he knows exactly what he’s doing and previously worked on libzypp.
I tried it, someone has to test it……but everything was ok. I’d sure hate to lose all of the work that I’ve put into this installation and a trashed database is at the top of the list of how to destroy a good running system.
So you can use Cockpit without removing Yast?
I’m getting ready to try it.
Yes, YaST doesn’t need to be removed.
How will users be able to remove it in TW when the deprecation is “official”?
@yikerman It won’t get installed, or removed on a dup.
Edit: Just to clarify it will likely get removed on a dup if it gets deleted… But one can always lock…
I’ve been using org.cockpit_project.CockpitClient for awhile now (again I only install flatpaks as my user, not system) and connect to any system over ssh (including localhost) and use…
Thanks all for your comments. I was able to get the new apps installed, and was able to do a zypper rm --clean-deps yast2* to get rid of Yast. Also had to remove a few patterns that would have pulled yast back in, and manually install apparmor after removing the pattern for it, but system seems stable, yast is gone.
I looked for myrlyn with both discover and flatpak
windeath:/home/dart/Downloads # flatpak search myrlyn No matches found
Must be old age and failing memory kicking in … I installed myrlyn from repos but want the equivalent system modules … WTH am I doing wrong?
@dart364 myrlyn only does package management, nothing more… for other key things org.cockpit_project.CockpitClient flatpak or the cockpit packages…
Ok … pkg management only … that’s what I wanted to know … seems nice … fast but is oversized for my display … have to click <upper right – fullsize> to see the buttons properly … setting “application settings” for that window doesn’t help … just saying … not a big deal … we here to squash bugs right? …