Yast partitioner loads software repos everytime befroe a change is applied

KDE/Plasma

I was editing HDD partitioning on this box with a nvme SSD. The first time the partitioner loaded yast software manager automatically to install nvme-cli (or similar), although the nvme drive and partitions weren’t changed in any way.

Now every time I select NEXT after editing an HDD partition Yast update the repos before proceeding to the APPLY CHANGES dialog. Nothing gets installed, although the changes are applied as they should be.

A quick google search of this site didn’t find anything relevant.

Any idea what is happening?

If the first time the partitioner loaded yast software manager automatically to install nvme-cli (or similar), it does not surprise me next times it also checks if there is not a newer version of nvme-cli (or similar), what is more surprising is the fact that it did ask it the first time, AFAIK only new software is installed with the installation.

From /usr/share/YaST2/lib/y2partitioner/widgets/overview.rb:

      # Checks whether the needed packages are installed
      #
      # As a side effect, it will ask the user to install missing packages.
      #
      # @see Y2Storage::UsedStorageFeatures
      #
      # @return [Boolean]
      def packages_installed?
        return true if Yast::Mode.installation

        pkgs = device_graph.actiongraph.used_features.pkg_list
        Y2Storage::PackageHandler.new(pkgs).install
      end

I have seen that YaST behavior earlier (years ago). When using YaST to configure some hardware (may also software), it offered to install packages needed that weren’t installed. It did of course only once. Very handy and IMHO it is one of those helpful things that makes it a good system management tool.

The other way around, some packages (I think I can remember NFS server) install the appropriate YaST module as dependency.

I do not think it checked for newer version, but i can not really prove that because I normally am up-to-date.

In any case, something looks strange with what the OP sees now.

This is most likely simply repositories auto-refresh.

Yes, but why?

I do not expect auto-refresh of my software repositories when I am working with a complete different module of YaST (like the OP).

YaST - rewrite of the storage module

yast2-storage-ng is a reimplementation of the YaST storage module (yast2-storage) based on the also reimplemented library for storage manager libstorage-ng.

**i3-4130:~ #** zypper if yast2-storage-ng 
Loading repository data... 
Reading installed packages... 


Information for package yast2-storage-ng: 
----------------------------------------- 
Repository     : Haupt-Repository (OSS) 
Name           : yast2-storage-ng 
Version        : 4.4.7-1.1 
Arch           : x86_64 
Vendor         : openSUSE 
Installed Size : 2.5 MiB 
Installed      : Yes (automatically) 
Status         : up-to-date 
Source package : yast2-storage-ng-4.4.7-1.1.src 
Summary        : YaST2 - Storage Configuration 
Description    :  
    This package contains the files for YaST2 that handle access to disk 
    devices during installation and on an installed system. 
    This YaST2 module uses libstorage-ng. 

**i3-4130:~ #**

More at GitHub - yast/yast-storage-ng: Rewrite of https://github.com/yast/yast-storage