Myrlyn just appeared. Now what?

[Prexy]

When I opened my start menu, I noticed a green dot on the system link. Clicking on it, I found 3 entries for Myrlyn. I tried the zypper dup equivalent and it asked for root password, as I would expect. It did a graphical version of what I see in the terminal. I had to leave before it was finished. When I came back, Myrlyn was gone. I tried the other two entries and they came up with no updates. Oddly, when I tried the zypper dup equivalent, it asked not for the root password but the user password. Is this normal? The graphical version looks nice. Is yast no longer needed?

BTW I see cockpit is available but I’m afraid to try another new thing!

[myswtest]

If you’ve been “active” out here (or even passive, but watching), it would be known Myrlyn is the “new” YaST Software tool.

Cockpit is “everything else”. Might do a search for more details

(sidenote: we have Leap 16 Beta running in a VM, on our Leap 15.6, to see what’s coming up. There is zero evidence of YaST )

https://www.reddit.com/r/openSUSE/comments/1lpbvo8/opensuse_tumbleweed_snapshot_20250630_now/

… more, among many more

Remove Yast and install the new management tools without a reinstall?

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 actuall…

[aggie]

Slightly long article, but predicts the future of YaST for TW (will no doubt go away later this year, due to lack of interest in maintaining it).

And yes Agama is the new installer

The last of YaST?

[Prexy]

Lots of information in these articles. I will gladly use Myrlyn now. Don’t seem to have a use for cockpit…yet!

[pawanyadav]

Myrlyn dont support import export (package list) yet…

[susejunky]

@myswtest

Cockpit is “everything else”.

Cockpit can do package- and repository-management as well.

[aggie]

from @susejunky:

@myswtest

Cockpit is “everything else”.

Cockpit can do package- and repository-management as well.

interesting.

Running Leap 16 (in a VM) … to me, Myrlyn is the preferred sodtware management system (replacing YaST Software mgt).

In default Cockpit install, there is no “software management” component.

Maybe it’s something additional that has to be added?

I would think Myrlyn would not had been created if Cockpit would have a comprehensive “zypper up / dup” functionality for Leap and TW (?).

If yes to “add a module” , you should have provided that info

[malcolmlewis]

@aggie So, I run the flatpak Cockpit client, can access all machines on the network. I just did a software update here on my test system for Leap 16.0 Beta…

[arvidjaar]

@susejunky

Cockpit can do package- and repository-management as well.

Can it do interactive conflicts resolution like zypper?

[susejunky]

@aggie

If yes to “add a module” , you should have provided that info

Then let me give you the whole picture:

I run openSUSE Tumbleweed and use zypper to do package- and repository-management (have not used any YaST for a long time).

When I heard about cockpit (from the openSUSE Leap 16 Beta announcement and from some threads in this forum) I got curious and did zypper se cockpit to see what packages were available.

Then I just installed what looked interesting to me

# zypper se -si cockpit 
Loading repository data...
Reading installed packages...

S  | Name                   | Type    | Version | Arch   | Repository
---+------------------------+---------+---------+--------+------------------------
i+ | cockpit                | package | 340-1.1 | x86_64 | openSUSE Tumbleweed Oss
i  | cockpit-bridge         | package | 340-1.1 | noarch | openSUSE Tumbleweed Oss
i+ | cockpit-networkmanager | package | 340-1.1 | noarch | openSUSE Tumbleweed Oss
i+ | cockpit-packages       | package | 3-1.1   | noarch | openSUSE Tumbleweed Oss
i+ | cockpit-repos          | package | 4.3-1.1 | noarch | openSUSE Tumbleweed Oss
i+ | cockpit-selinux        | package | 340-1.1 | noarch | openSUSE Tumbleweed Oss
i+ | cockpit-storaged       | package | 340-1.1 | noarch | openSUSE Tumbleweed Oss
i+ | cockpit-subscriptions  | package | 12-1.1  | noarch | openSUSE Tumbleweed Oss
i  | cockpit-system         | package | 340-1.1 | noarch | openSUSE Tumbleweed Oss
i  | cockpit-ws             | package | 340-1.1 | x86_64 | openSUSE Tumbleweed Oss
i+ | cockpit-ws-selinux     | package | 340-1.1 | x86_64 | openSUSE Tumbleweed Oss

    Note: For an extended search including not yet activated remote resources please use 'zypper
    search-packages'.
#

After that

[susejunky]

@arvidjaar

Can it do interactive conflicts resolution like zypper?

Why not give it yourself a try?

# zypper info --requires cockpit-packages
Loading repository data...
Reading installed packages...


Information for package cockpit-packages:
-----------------------------------------
Repository     : openSUSE Tumbleweed Oss
Name           : cockpit-packages
Version        : 3-1.1
Arch           : noarch
Vendor         : openSUSE
Installed Size : 3.5 MiB
Installed      : Yes
Status         : up-to-date
Source package : cockpit-packages-3-1.1.src
Summary        : A cockpit module for (un)installing packages
Description    : 
    A cockpit module for (un)installing packages
Requires       : [2]
    PackageKit
    cockpit-bridge
#

As I only use zypper to do package- and repository-management the only thing I did for testing so far was installing and uninstalling a few packages with cockpit. That went fine for me.

And I did some changes to my repository setup which also worked out well.

[Prexy]

Update on odd situation. Discover runs in my taskbar. It always shows updates that have already been updated through zypper dup. Now that I have begun to use Myrlyn, I checked to see if the Discover updates were legitimate. They were not. But there is an oddity. Discover said to update Chrome to 139. I checked Myrlyn and Chrome is not listed as being installed at all. So, I checked yast. Similarly, Chrome is not listed as installed. even though I am posting this via Chrome. Just to see what happens, I tried zypper dup and it said nothing to do. Any ideas?

[arvidjaar]

@Prexy

Any ideas?

Yes, flatpak.

[hui]

You installed Chrome via flatpack obviously…

[Prexy]

I don’t remember using flatpak for Chrome. I don’t want to argue with people that know more than me but I am certain that yast updated Chrome for me many times. Offhand, I don’t know how to update flatpak packages or even what packages I might have installed that way. Is there command or other way to check flatpak installs?

[hui]

@Prexy

I checked Myrlyn and Chrome is not listed as being installed at all.

You also need to check that you have proper search filters in Myrlyn. Instead of “Auto” you need to set it to “Contains”.

[malcolmlewis]

@Prexy flatpak list and flatpak update or maybe flatpak --user update depends on how they were installed…

[sfalken]

flatpak list in a terminal

[Prexy]

Well, I learned something today. Two things actually. Chrome WAS installed via flatpak, as is shown in flatpak list. There were about a dozen other packages too., mostly gnome (which I don’t use) and something called freedesktop. I also learned that Discover is showing me the flatpak updates for these packages. No wonder that Myrlyn didn’t make the notice go away. I also learned to update flatpaks. Thanks for the info!

[Prexy]

After I realized I had some packages installed via flatpak, I switched the filter in Myrlyn to Contains. That didn’t bring the flatpak installs into view. So, I know I now have to do two things to update. I must have installed Chrome via flatpak some time back to solve a problem with yast.