Issue with Software Application Installation on openSUSE: Dependency Conflicts and Failures

I’m encountering significant issues with installing software applications on my openSUSE system due to dependency conflicts and failures, and I’m seeking assistance to resolve it.

Background: I use openSUSE as my primary operating system for development and daily tasks. While the package management system typically works well, I’ve recently encountered problems when trying to install certain software applications, particularly those with complex dependencies.

Issue: The main problem arises when attempting to install or update specific software applications using zypper or YaST. The installation process often fails with dependency conflict errors, stating that certain packages cannot be installed or updated due to version mismatches or missing dependencies. This issue affects my ability to install essential software and maintain an up-to-date system.

Troubleshooting: Here are the steps I’ve taken to troubleshoot the issue so far:

  1. Ran zypper refresh to ensure all repositories are up to date.
  2. Tried using zypper install --force to override conflicts, but this sometimes leads to broken packages or unstable software.
  3. Added additional repositories and tried installing the software from these sources, but the conflicts persist.
  4. Used zypper verify to check for any broken dependencies in the system and attempted to repair them.
  5. Reviewed the openSUSE forums and documentation for any known issues with the specific applications I’m trying to install.

Observations: Despite these efforts, the dependency conflicts and installation failures persist, preventing me from installing necessary software and maintaining a stable system. This problem is critical as it impacts my ability to use openSUSE effectively for my work and daily tasks.

Request for Assistance: If anyone has experience with resolving dependency conflicts and installation issues in openSUSE or has encountered similar problems, I would greatly appreciate your insights and assistance. Specifically, I’m looking for strategies to identify and resolve dependency issues, as well as best practices for managing software installations on openSUSE.

Thank you for your help and support!

Please do not tell that you have problems, show the problems by installing the packages with zypper.

And think of that:
Tumbleweed is rolling release with new packages, maybe your packages you want to install needs older dependencies?

This sounds like that a lot of arbitrary conflicting repos got added. So a good starting point to discuss the issues should be the output of zypper lr -d and an example of an upgrade attempt via zypper dup.

A start for a disaster?

But as already said, we can not give any other advice on your story telling then: Please SHOW!.

Not only the zypper command you use (with all output), but also your present repo list, because you seem to have messed with it

zypper lr -d

BTW, welcome to the openSUSE forums.
And please show your copied/past computer text using the Preformatted text button </> from the tool bar of the post editor.

1 Like

Without knowing which openSUSE variant (e.g. Tumbleweed, Slowroll, Leap 15.5, Leap 15.6, MicroOS, …) you are using it is hard to offer any advice.

And as already suggested in the other posts please show which repositories you are using

zypper lr -EPu

and tell which packages fail to install by showing the results of

zypper -v in -D PACKAGE

Sorry, but the tags list says: Tumbleweed.

Ooops!! My fault!

I always forget to look at the tags.

And please don’t add confusion! We don’t want a redacted repo list as with your command. As already mentioned by Henk and me, we need a full repolist, including disabled repos as these can also cause conflicts/dependency issues and more.
So the correct command (as already mentioned several times above) should be zypper lr -d

Who is “we”? Or are you using Pluralis Majestatis here?

I would like to see only those repositories which are actively used at the moment (and I don’t see how any non-active ones could be relevant).

Everybody who has basic experience in troubleshooting issues caused by a messed up repo list.

Could you explain for us mere mortals how is it possible?

And you are representing all those people? I’m not aware that I gave you permission to speak on my behalf …

I also think that showing all repos might be helpful, because those repos did not land there by magic. Apart from the Source and Debug ones, one can assume that they have been used for installing packages before being disabled and thus may have been instrumental in creating problems.

I also think that suggesting an increasing amount of slightly different commands to an apparent novice user may create more confusion then being useful.

I admit that I suggested the same as @hui did, but can defend that because we did create those posts at the same time without knowing from each other.

Jut my opinions.

1 Like

Package from repo A depends on a package from repo B but repo B is disabled.

As the TO stays vague about the real issue, it is important to ask for the full picture (aka full repo list) instead of limiting your and others view with a limited repo list.

1 Like

I agree.

Nevertheless I personally believe that a list of the repositories currently in use plus the complete result of a failing package installation attempt will provide a good starting point to analyse OPs problem.

That may be correct, but does it differ very much from what was asked for 15 hours ago?

The OP did not answer those questions that were suggested 14 hours ago. Maybe he is gone to sleep direct after his first post. Asking almost the same again isn’t very productive IMHO. Just wait and see what comes (if it comes) and then may refining the question for more information would be my approach.

Again, just my opinion.

Well, … it’s all a question of efficiency.

If zypper lr -d results in a long list (as OPs first post suggests) one needs to work out which repositories are active (and probably what priorities are set). This is extra work, takes time and is error prone (and as my post #4 shows I tend to make errors). The list I asked for shows fairly quick whether it needs more attention or not.

Sorry, but that is my personal approach. You, @hui and anyone else here might have a different one. Nevertheless should I be entitled to ask for the information which gives me the best chance to help.

But as you already said lets wait for the OP to show more details.

Thank you for your prompt response. Here is the information you requested:

  1. Output of zypper lr -d:
# | Alias                            | Name                                    | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                      | Service
--+----------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------------------------+--------
1 | repo-oss                         | Main Repository (OSS)                   | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.3/repo/oss/                             |        
2 | repo-non-oss                     | Main Repository (NON-OSS)               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/                         |        
3 | repo-update                      | Main Update Repository                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/oss/                                        |        
4 | repo-update-non-oss              | Update Repository (Non-Oss)             | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/non-oss/                                    |        
5 | repo-packman                     | Packman Repository                      | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/                             |        
6 | devel:gcc                        | GNU Compiler Collection (GCC)           | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | http://download.opensuse.org/repositories/devel:/gcc/openSUSE_Leap_15.3/                  |        
7 | openSUSE-Leap-15.3-Update        | openSUSE-Leap-15.3-Update               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/oss                                         |        
8 | openSUSE-Leap-15.3-Non-Oss-Update| openSUSE-Leap-15.3-Non-Oss-Update       | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.3/non-oss                                     |        
9 | openSUSE-Leap-15.3-Packman       | openSUSE-Leap-15.3-Packman              | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/                             |        
10| openSUSE-Leap-15.3-Devel-GCC     | openSUSE-Leap-15.3-Devel-GCC            | Yes     | (r ) Yes  | Yes     |   90     | rpm-md | http://download.opensuse.org/repositories/devel:/gcc/openSUSE_Leap_15.3/                  |
  1. Example of an upgrade attempt via zypper dup:
# zypper dup
Loading repository data...
Reading installed packages...
Computing distribution upgrade...

Problem: the installed libqt5-qtbase-5.15.2-lp153.3.10.1.x86_64 requires 'libqt5-qtbase-platformtheme = 5.15.2', but this requirement cannot be provided
  deleted providers: libqt5-qtbase-platformtheme-5.15.2-lp153.3.10.1.x86_64
 Solution 1: deinstallation of libqt5-qtbase-5.15.2-lp153.3.10.1.x86_64
 Solution 2: keep obsolete libqt5-qtbase-platformtheme-5.15.2-lp153.3.10.1.x86_64

Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c):

It appears that there are conflicts with the libqt5 packages among others. Based on your experience, could you advise on how to proceed with resolving these dependency conflicts? Are there specific repositories I should prioritize or disable to avoid these issues? :slightly_smiling_face: :slightly_smiling_face:

Thank you again for your help!

You started your post with the tag “openSUSE Tumbleweed” however your repository list shows repositories for openSUSE Leap 15.3 only.

If you are using openSUSE Leap 15.3 then you should be aware that this version is out of support since 31.12.2022 and you should upgrade to openSUSE Leap 15.6.

If you are using openSUSE Tumbleweed then you need to adjust your repositories to the Tumbleweed ones.

Sorry, I am a bit flabbergasted.

You started to tag this as a Tumbleweed system, but all your repos are Leap 15.3 (which is long out of support already).

I guess we expect an explanation from you about what you think you have and/or should have.

Updating a Leap system is NOT done using zypper dup , but with zypper up .

In any case updating this system is useless, there weren’t any updates shipped since 2022-12-31.