A universal solution that relies on conflicts when installing software

Well, maybe it's a headline party.

But if you can't solve the conflict of dependencies, then I don't know what to do now.

However, in general, this method can be used to fix the problem.

The foundation of the solution

If you're just experiencing a dependency conflict, you can start by referring to the basic solution here.

SOURCE problem: The following packages have dependencies that are not satisfied
Various solutions: The package is not fully installed or uninstalled.

Get to the point.

Let's talk about the background first.

It's not possible to use the underlying solution, and more seriously, you want to reload the software, but not unload it, prompting for a dependency conflict.

This time I want to reload the system, but I have configured this many things, installed this software and other reasons, not to the last step I do not want to choose a reload system this method, after all, the reload system does not necessarily solve the conflict problem.

However, I finally found the solution.

This is to share out, to help you one more choice of solutions, of course, do not have to choose this method.

Now let's take a look at this problem of dependency conflict.

What is the error message that prompts you when you install the software?

The software installed relies on a low version of the software.

First, how does the system know about the dependency conflict?

It should be that every software has a clear picture of which software you depend on and the minimum version of the software.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/soft/tools/

Can we manually modify the version of the dependent software?

If you know where the information is stored, you can modify it.

Where is this information stored?

Looks like it's in the/var/lib/dpkg/status file.

Like my Vim-common information.

Package:vim-common status:install OK installed priority:important section:editors installed-size:296 Maintainer:ubu NTU developers <ubuntu-devel-discuss@lists.ubuntu.com> architecture:i386 Source:vim Version: 2:7.3.547-6ubuntu3~blueyed1~precise Depends:libc6 (>= 2.3.4) Recommends:vim | Vim-gnome | VIM-GTK | Vim-athena | Vim-nox | Vim-tiny conffiles:/ETC/VIM/VIMRC 682aa2a07693cc27756eee9751db3903 description:vi Improved-common files Vim is a al
 Most compatible version of the UNIX editor Vi.
 . Many new features have been added:multi level undo, syntax highlighting, command line history, on-line help, filename c
 Ompletion, block operations, folding, Unicode support, etc.
 .
 This package contains files are shared by the non gui-enabled VIM variants (VIM and vim-tiny currently) available in Debian.
Examples of such shared files are:manpages, common executables like xxd, and configuration files. Homepage:http://www.vim.org/original-maintainer:debian Vim MaintAiners pkg-vim-maintainers@lists.alioth.debian.org 

You can see two of the data that are important to us.

Version:2:7.3.547-6ubuntu3~blueyed1~precise
Depends:libc6 (>= 2.3.4)

Assuming that our LIBC6 version is 2.3.2, installing Vim-common will prompt for a dependency conflict, saying that the LIBC6 version is at least 2.3.4.

What happens when we can modify the minimum dependent version?

Like what

Version:2:7.3.547-6ubuntu3~blueyed1~precise
Depends:libc6 (>= 2.3.2)

This is once again repaired unexpectedly succeeded, also can uninstall.

Well, the solution is this: change the version of the dependent software to the currently installed version.