sbocheck

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXIT CODES
BUGS
SEE ALSO
AUTHORS
MAINTAINER

NAME

sbocheck - update a local SlackBuilds.org tree and check for updates

SYNOPSIS

sbocheck [-h|-v]

sbocheck [-OXgn]

sbocheck [-c] package [package]

sbocheck [--color|--nocolor] \...

DESCRIPTION

sbocheck updates or fetches a copy of the SlackBuilds.org tree, checks for available upgrades, and reports what it finds. If OBSOLETE_CHECK is TRUE, an updated copy of the script list at /etc/sbotools/obsolete is downloaded from https://pghvlaans.github.io/sbotools when running Slackware -current (see sboconfig(1) or sbotools.conf(5)).

SlackBuilds with differing build numbers are reported separately, as are any SlackBuilds marked _SBo that are not found in the repository or local overrides (see sboconfig(1) or sbotools.conf(5)). Except in CLASSIC mode, scripts in the report that would not be upgraded by sboupgrade(1) are marked with = (equals sign).

The three output categories are logged separately to /var/log/sbocheck.log, /var/log/sbocheck-bumps.log and /var/log/sbocheck-out-of-tree.log. The out-of-tree and build number increment checks are disabled when CLASSIC is TRUE; if STRICT_UPGRADES is TRUE, apparent downgrades are reported with “differs”, but are not acted on by sboupgrade(1) (see sboconfig(1) or sbotools.conf(5)).

Upgrades to Slackware and third-party packages occasionally cause breakage due to *.so version differences. To check for missing first-order shared object (solib) dependencies among all installed in-tree _SBo packages, use the --so-check option. Each affected package is logged to /var/log/sbocheck-solibs.log with a list of missing shared objects. This can be done automatically on every sbocheck run by setting SO_CHECK to TRUE. Use the --check-package option to check only a list of packages. Please note that scripts repackaging from binary packages occasionally trigger false positives. Such packages generally do not require rebuilds.

To check for updated SlackBuilds without updating the SlackBuilds tree, pass the --nopull option. sbocheck performs gpg(1) verification upon pulling the tree if GPG_VERIFY is TRUE (see sboconfig(1) or sbotools.conf(5)). The --gpg-verify option has the same effect. Passing both --gpg-verify and --nopull verifies the repo in-place without fetching. Only rsync repositories can be verified on Slackware 14.0 and Slackware 14.1.

Please note that sbosnap, which was removed as an independent script in sbotools-3.3, is a compatibility symlink to sbocheck.

Non-root users can only call sbocheck with the --nopull, --so-check, --help and --version flags. sbocheck issues a warning if the directory specified with LOCAL_OVERRIDES does not exist (see sboconfig(1) or sbotools.conf(5)). If an invalid configuration is detected in /etc/sbotools/sbotools.conf, the script exits with a diagnostic message.

OPTIONS

-c|--check-package

Check one or more package names for missing shared objects; the packages need not be tagged with _SBo. Incompatible with --so-check.

-g|--gpg-verify

Use gpg(1) to verify the fetched repository, even if GPG_VERIFY is FALSE. When called with --nopull, verify the repo without fetching. Only rsync repositories can be verified on Slackware 14.0 and Slackware 14.1.

-O|--obsolete-check

If running Slackware -current, download a copy of the obsolete script list from https://pghvlaans.github.io/sbotools and verify with gpg(1) if GPG_VERIFY is TRUE or --gpg-verify is passed. Incompatible with --nopull.

-n|--nopull

Check for updated SlackBuilds without updating the SlackBuilds tree. The --nopull flag can be used without root privileges, but no log is kept.

-X|--so-check

Check all installed _SBo packages for missing shared object dependencies; no other operations are performed. To do this automatically every time sbocheck is run, set SO_CHECK to TRUE (see sboconfig(1) or sbotools.conf(5)). Incompatible with --check-package.

-h|--help

Show help information.

-v|--version

Show version information.

--color

Turn on sbotools color output. See also sbotools.colors(5).

--nocolor

Turn off sbotools color output.

EXIT CODES

sbocheck can exit with the following codes:

0: all operations were successful.
1: a usage error occurred.
2: a script or module error occurred.
5: failed to download the tree.
6: failed to open a required file handle.
12: interrupt signal received.
15: GPG verification failed.

BUGS

None known. If found, Issues and Pull Requests to https://github.com/pghvlaans/sbotools/ are always welcome.

AUTHORS

Jacob Pipkin <j (at) dawnrazor (dot) net>

Luke Williams <xocel (at) iquidus (dot) org>

Andreas Guldstrand <andreas (dot) guldstrand (at) gmail (dot) com>

MAINTAINER

K. Eugene Carlson <kvngncrlsn (at) gmail (dot) com>