How to Fix “You could try using –skip-broken to work around the problem” Error

When using package managers like yum or dnf on CentOS, Fedora, or RHEL-based systems, you may encounter an error suggesting the use of –skip-broken to work around the problem. This error usually occurs when there are broken or unresolvable dependencies between packages.

You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.

In this guide, we’ll provide step-by-step instructions on how to use –skip-broken and other methods to fix this issue.

Step 1: Use –skip-broken Option

As suggested in the error message, you can use the –skip-broken option to bypass the problematic packages and continue with the installation or update process. Run the following command:

sudo yum update --skip-broken


sudo dnf update --skip-broken

This command will skip the packages with broken dependencies and continue updating or installing the remaining packages.

See also  How to Install Yum on Red Hat Enterprise Linux 5 (RHEL)

Step 2: Update Your System

Sometimes, updating your system can resolve dependency issues. Run the following command to update all packages:

sudo yum update -y


sudo dnf update -y

Step 3: Clean Cache

Clearing the package manager cache may help resolve the problem. Run the following commands to clean the cache:

sudo yum clean all


sudo dnf clean all

After cleaning the cache, try updating or installing the packages again.

To install yum-utils, run the following command:

[root@server ~]# yum install yum-utils
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * addons:
 * base:
 * extras:
 * updates:
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package yum-utils.noarch 0:1.1.16-14.el5.centos.1 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

 Package            Arch            Version                           Repository     Size
 yum-utils          noarch          1.1.16-14.el5.centos.1            base           69 k

Transaction Summary
Install       1 Package(s)
Upgrade       0 Package(s)

Total download size: 69 k
Is this ok [y/N]: y
Downloading Packages:
yum-utils-1.1.16-14.el5.centos.1.noarch.rpm                        |  69 kB     00:04
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : yum-utils                                                          1/1

  yum-utils.noarch 0:1.1.16-14.el5.centos.1


Step 4: Disable Problematic Repositories (Optional)

If the issue persists, you can temporarily disable problematic repositories. To do this, edit the repository configuration file located in /etc/yum.repos.d/ or /etc/dnf/dnf.conf:

sudo vi /etc/yum.repos.d/example.repo


sudo vi /etc/dnf/dnf.conf

Replace example.repo with the name of the repository configuration file. In the file, look for the line starting with enabled= and set its value to 0. Save the changes and exit the editor.

See also  How to "Resolve Another app is currently holding the yum lock; waiting for it to exit"

Try updating or installing the packages again. Remember to enable the repository after resolving the issue by setting the enabled= value back to 1.

Commands and Their Functions:

  • sudo yum update –skip-broken / sudo dnf update –skip-broken – Update packages while skipping those with broken dependencies
  • sudo yum update -y / sudo dnf update -y – Update all packages on the system
  • sudo yum clean all / sudo dnf clean all – Clean the package manager cache
  • sudo vi /etc/yum.repos.d/example.repo / sudo vi /etc/dnf/dnf.conf – Edit the repository configuration file
See also  How to Install jnetmap on Ubuntu

The Outcome

By following these steps, you should be able to resolve the “You could try using –skip-broken to work around the problem” error. The package installation or update process should now proceed without issues related to broken dependencies.

We hope this guide has been helpful in fixing the “You could try using –skip-broken to work around the problem” error. If you have any suggestions or improvements, please feel free to leave a comment below.



Leave a Reply

Your email address will not be published. Required fields are marked *