[ANN] chk3ppdeps 2019.1128 (beta)
by phenixia2003 from LinuxQuestions.org on (#4VVXQ)
Hello,
chk3ppdeps is a command line tool designed to help user to identify 3rd-party packages :
To get the list of broken 3rd-party packages, run (as root) chk3ppdeps with option --list-breakage, as in example below :
Code:$ chk3ppdeps --list-breakage
Broken 3rd-party packages :
source-highlight-3.1.8-x86_64-1_SBo
Unsatisfied dependencies for :
/usr/bin/check-regexp: libboost_regex.so.1.70.0
/usr/bin/source-highlight: libboost_regex.so.1.70.0
/usr/bin/source-highlight-settings: libboost_regex.so.1.70.0
/usr/lib64/libsource-highlight.so.4.0.1: libboost_regex.so.1.70.0
Found 1 broken package(s).Notes:
Code:$ chk3ppdeps --predict-breakage
3rd-party packages that might be broken by next system update :
wmalauncher-2018.1002-x86_64-1_SBo, might be broken by update(s) :
librsvg-2.46.4-x86_64-1.txz
1 package(s) could break at the next system update.By default, this option only considers the 1st entry of the slackware changelog. To go beyond that, simply pass the TIMESTAMP (in whole or part) of the oldest changelog entry to consider, like in examples below :
Code:$ chk3ppdeps --predict-breakage "Mon Nov 25 19:17:07 UTC 2019"
$ chk3ppdeps --predict-breakage "Mon Nov 25"
$ chk3ppdeps --predict-breakage "Nov 25"The chk3ppdeps package can be downloaded here.
Cheers.
--
SeB


chk3ppdeps is a command line tool designed to help user to identify 3rd-party packages :
- which are broken (ie. with unsatisfied dependencies)
- which might be broken by next system update
To get the list of broken 3rd-party packages, run (as root) chk3ppdeps with option --list-breakage, as in example below :
Code:$ chk3ppdeps --list-breakage
Broken 3rd-party packages :
source-highlight-3.1.8-x86_64-1_SBo
Unsatisfied dependencies for :
/usr/bin/check-regexp: libboost_regex.so.1.70.0
/usr/bin/source-highlight: libboost_regex.so.1.70.0
/usr/bin/source-highlight-settings: libboost_regex.so.1.70.0
/usr/lib64/libsource-highlight.so.4.0.1: libboost_regex.so.1.70.0
Found 1 broken package(s).Notes:
chk3ppdeps can also be used to predict which 3rd-party packages could break at the next system update using option --predict-breakage :
- the 1st time chk3ppdeps is run, the sbbdep database is generated which can take some time.
- chk3ppdeps can be run as normal user. For that it is required to specify a configuration file in argument as in example below:
Code:$ chk3ppdeps --config /path/to/my/chk3ppdeps/config --chk3ppdepsA configuration file suitable for normal users is available in /usr/doc/chk3ppdeps-2019.1128 (chk3ppdeps-all-user.conf.sample).- some 3rd-party packages can be wrongly reported as broken (ex. package of any application with its own environment). To prevent this, it can be useful to add these packages onto the blacklist (/etc/chk3ppdeps/blacklist.3pp, by default), which supports same syntax as slackpkg's blacklist.
Code:$ chk3ppdeps --predict-breakage
3rd-party packages that might be broken by next system update :
wmalauncher-2018.1002-x86_64-1_SBo, might be broken by update(s) :
librsvg-2.46.4-x86_64-1.txz
1 package(s) could break at the next system update.By default, this option only considers the 1st entry of the slackware changelog. To go beyond that, simply pass the TIMESTAMP (in whole or part) of the oldest changelog entry to consider, like in examples below :
Code:$ chk3ppdeps --predict-breakage "Mon Nov 25 19:17:07 UTC 2019"
$ chk3ppdeps --predict-breakage "Mon Nov 25"
$ chk3ppdeps --predict-breakage "Nov 25"The chk3ppdeps package can be downloaded here.
Cheers.
--
SeB