From 9a178619b934f7dca245c7cebd63dbebc4039c3b Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Fri, 23 Apr 2021 01:38:47 +0800 Subject: add a paragraph for "downgrading issue" in package management page --- chapter08/pkgmgt.xml | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-) (limited to 'chapter08') diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml index e898416d8..6c628c3d6 100644 --- a/chapter08/pkgmgt.xml +++ b/chapter08/pkgmgt.xml @@ -71,7 +71,27 @@ against libfoo.so.2 in order to use the new library version. You should not remove the previous libraries unless all the dependent packages are recompiled. - + + + If a package containing a shared library is updated, + and the name of library doesn't change, but the version number of the + library file decreases (for example, + the name of the library is kept named + libfoo.so.1, + but the name of library file is changed from + libfoo.so.1.25 to + libfoo.so.1.24), + you should remove the library file from the previously installed version + (libfoo.so.1.25 in the case). + Or, a ldconfig run (by yourself using a command + line, or by the installation of some package) will reset the symlink + libfoo.so.1 to point to + the old library file because it seems having a newer + version, as its version number is larger. This situation may happen if + you have to downgrade a package, or the package changes the versioning + scheme of library files suddenly. + + -- cgit v1.2.3-54-g00ecf