Discovery rpm yast-software woes.

yast - not happy with no more pattern categories. Better change would be to have made a gui vs cli sun-class then to make a flat list. Now get plenty of errors that software dependencies are not met. Before 15.1 it listed what the dependencies were that were in question or selected what needs to be installed along with what was selected. Now you have to manually search and find the dependencies yourself and if your lucky you may get a new app but don’t hold your breathe.

rpm can’t check the system anymore to see if something was or wasn’t installed. If Discovery tries to install a package and fails (internal error) it’s too late it has already told rpm it is installed even if it isn’t. rpm then refuses to remove the offending entry because it isn’t there but then tells you it can’t be installed because it already exists.

zypper also can’t understand whether or not a package has been installed or not.

This brings us to discovery. A program so vial it should be uninstalled as fast as possible if that it even possible. You are in dolphin looking around your system and come to a folder looking for something and the folder has rpms, yums, gz etc and as you pass over them using the down arrow … Up pops discovery (checking for updates) and after 45 minutes it comes back to say no updates at this time. It then shows you the rpm and you may click install.

But Discovery is a very broken piece of software. When you try to install an rpm or yum file it stops with internal error. and a choice to remove the rpm or such. Choose remove and get another internal error. query rpm and it says it’s installed. Manually check and it is not installed. Tell rpm to remove the entry and rpm complains it isn’t installed. Manually try to install the rpm and rpm complains it can’t install because it is already installed.

Wishing I could go back to 15.0 download all needed repos local so I can restore everything without having to depend on online repo’s and live in the past because this new 15.1 isn’t so great.

I don’t know enough about what has all changed to even attempt to tackle things.

Can you share your currently configured repos…

zypper lr -d

What does the following report about your ‘broken/inconsistent’ system…

zypper ve --dry-run

Here is what that gave me:

#  | Alias                               | Name                              | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                  | Service
 1 | | home:ecsos:Backup                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |    |        
 2 | | home:syntron:patched              | No      | ----      | ----    |   99     | rpm-md | |        
 3 | | X11:XOrg                          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |              |        
 4 | | security:tls                      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |          |        
 5 | | openSUSE:Leap:15.1                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                        |        
 6 | | X11:FOX                           | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |               |        
 7 |    | libdvdcss repository              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                                   |        
 8 |      | Packman Repository                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                                     |        
 9 | repo-non-oss                        | openSUSE-Leap-15.1-Non-Oss        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                    |        
10 | repo-oss                            | openSUSE-Leap-15.1-Oss            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                        |        
11 | repo-source                         | openSUSE-Leap-15.1-Source         | No      | ----      | ----    |   99     | rpm-md |                 |        
12 | repo-source-non-oss                 | openSUSE-Leap-15.1-Source-Non-Oss | No      | ----      | ----    |   99     | rpm-md |             |        
13 | repo-update                         | openSUSE-Leap-15.1-Update         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                                   |        
14 | repo-update-non-oss                 | openSUSE-Leap-15.1-Update-Non-Oss | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |                               |        

Loading repository data...
Reading installed packages...

The following package is going to be REMOVED:

1 package to remove.
After the operation, 9.1 MiB will be freed.
214 dependencies broken
Some of the dependencies of installed packages are broken. In order to fix these dependencies, the following actions need to be taken:
Continue? [y/n/v/...? shows all options] (y):y

and rpm -qa generated a listing 6200 packages which is interesting because when I spent 14 hours doing the update to 15.1 it had 6197 packages to update so only 3 packages from 15.0 were kept.

it removed xbasic which is one of the packages that Discovery installed and failed to actually install.

A quick glance of the repos suggest all should be ok there.

Like other senior members here, I don’t use KDE Discover at all, can’t really offer any meaningful advice about using it. I would try to stay with using zypper while trying any recovery steps.

You could try completing the upgrade with

zypper clean
zypper dup

You’ll be prompted to make decisions around the dependencies though.

Was just about to re-install from usb leap 15.1 install over one of my old version partitions but then i read this?

Are you saying doing zypper clean will wipe old infor and zypper dup will rebuild all from repos hopefully clobbering any / all past errors??

“zypper clean” removes the package cache (any rpms), and I think it removes cached repo metadata.

“zypper dup” should bring your system into alignment with what is in the repos.

These won’t necessarily fix your problems. If your problem is in the settings in some configuration files, that might not be fixed.

Caches are lurking, try: zypper --verbose refresh --force; zypper verify. Refrain from using discover and GUIs when performing update, watch for new configuration files: run rpmconfigcheck. Consider temporarily disabling nonstandard repos.